1. Forum
  2. DOVE-Net
  3. Hardware-Software Help

  • SyncTerm Linux

    From Chai@VERT/AMIGAC to All on Tue Sep 11 02:03:09 2018
    Has anyone noticed errors with SyncTerm in Linux with the latest updates to the system? Every distro I try, I get an error when I run SyncTerm. It compiles just fine, as it always has, but it will not run unless I run it in xterm. All other terminals, it's a no go. MultiMail is being affected as well. The colors are off and unreadable in MultiMail, unless I run it in a specific terminal.

    SyncTerm runs sort of in Terminator, but the menu colors are off there as well.

    This is pretty much running in stock Elementary OS. I tried Ubuntu Budgie, and I got the same results.

    ---
    þ Synchronet þ Amiga City - The BBS for the Amiga - more than 2,500+ files
  • From Digital Man@VERT to Chai on Mon Sep 10 20:00:57 2018
    Re: SyncTerm Linux
    By: Chai to All on Tue Sep 11 2018 02:03 am

    Has anyone noticed errors with SyncTerm in Linux with the latest updates to the system? Every distro I try, I get an error when I run SyncTerm.

    What error?

    This is pretty much running in stock Elementary OS. I tried Ubuntu Budgie, and I got the same results.

    Which are ... ?

    digital man

    This Is Spinal Tap quote #20:
    Well, I'm sure I'd feel much worse if I weren't under such heavy sedation. Norco, CA WX: 70.2øF, 75.0% humidity, 6 mph E wind, 0.00 inches rain/24hrs
    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Chai@VERT/ECBBS to Digital Man on Tue Sep 11 00:29:00 2018
    Digital Man wrote to Chai <=-

    What error?

    X Error of failed request:
    BadValue (integer parameter out of range for operation)
    Major opcode of failed request: 12 (X_ConfigureWindow)
    Value in failed request: 0x0
    Serial number of failed request: 26
    Current serial number in output stream: 26

    and I got the same results.

    Which are ... ?

    Syncterm runs in some terminals, does nothing but return to the bash prompt
    in others, or issues the above error. I have the current source (1.1b),
    as well as the pre-compiled binary you submitted to the SyncTerm web site.

    Terminator - Your compiled binary runs with garbled background on startup,
    but displays ANSI graphics correctly. The version I compiled
    displays incorrect ANSI, # signs instead of block characters.

    Evilvte - Same as Terminator

    eOS Stock Terminal - Upon execution, I get returned to the prompt.

    Ubuntu Budgie Stock Terminal - I receive the error mentioned at the
    beginning of this message.

    I checked my codepage, and it is set to 437. Your compiled binary is running in X11 mode, and my binary is running in curses mode. Here's the interesting part. I reverted my binary back to version 0.9.5b (X11), and the problem disappeared. 0.9.5b works perfectly.

    MultiMail is just using oddball colors that make the screen unreadable in most terminals, however it works as it is supposed to in evilvte terminal.
    I'm using the stock (unchanged) color template for multimail (v0.51 Linux). I've never had this issue in either program in Linux before.

    At any rate, I'm OK with running SyncTerm 0.9.5b, so I have a workaround for that issue.

    --- MultiMail/Linux v0.51
    þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com
  • From Digital Man@VERT to Chai on Tue Sep 11 15:07:01 2018
    Re: Re: SyncTerm Linux
    By: Chai to Digital Man on Tue Sep 11 2018 12:29 am

    Digital Man wrote to Chai <=-

    What error?

    X Error of failed request:
    BadValue (integer parameter out of range for operation)
    Major opcode of failed request: 12 (X_ConfigureWindow)
    Value in failed request: 0x0
    Serial number of failed request: 26
    Current serial number in output stream: 26

    Looks like it's having a problem with X mode. Try different '-i' option combinations (e.g. '-ic', '-is') and see if/how those work for you. 'syncterm -?' to display the command-line help.

    I checked my codepage, and it is set to 437. Your compiled binary is running in X11 mode, and my binary is running in curses mode. Here's the interesting part. I reverted my binary back to version 0.9.5b (X11), and the problem disappeared. 0.9.5b works perfectly.

    Which version showed the problem, 1.0 or 1.1b?

    digital man

    This Is Spinal Tap quote #26:
    David St. Hubbins: They were still booing him when we came on stage.
    Norco, CA WX: 85.2øF, 41.0% humidity, 10 mph ENE wind, 0.00 inches rain/24hrs ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Chai@VERT/ECBBS to Digital Man on Wed Sep 12 19:22:00 2018
    Digital Man wrote to Chai <=-

    Looks like it's having a problem with X mode. Try different '-i' option combinations (e.g. '-ic', '-is') and see if/how those work for you. 'syncterm -?' to display the command-line help.

    -ic is the one that shows me # signs on both versions, 0.9.5b and 1.1b.
    -is fails on both versions (CIOLIB initialization failed).
    -ix works flawlessly on 0.9.5b, but fails to draw the menu background on 1.1b.

    Once you get past the main menu on 1.1b, the rendering is fine, however.
    As for examples, https://photos.app.goo.gl/YGgqKM8N9ZUuMMJo7
    The commands rendered are listed in each photos info toggle.

    Which version showed the problem, 1.0 or 1.1b?

    1.1b. I just now tried compiling v1.0, and it works flawlessly, except
    curses (-ic), which must be due to how my system is configured. v1.0 works with -is and -ix. I use SDL, so this works for me.

    Thanks for fixing my issue. :)


    ... MultiMail, the new multi-platform, multi-format offline reader!
    --- MultiMail/Linux v0.51
    þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com