[go: up one dir, main page]
Menu ▾ ▴

#47 Golly doesn't open on ArchLinux/XFCE: X Window System error

v1.0 (example)
open
nobody
X (1) X Window System (1)
7
2019-04-07
2019-03-24
Anonymous
No

Recent versions of golly, from 2.8 to 3.2, do not work on my system due to an X Window System error. I'm on Arch Linux (5.0.2-arch1-1-ARCH) with desktop environment XFCE (Xfce 4.12). It doesn't matter if you get it from the AUR or from source; running golly yields the same error:

The program 'golly' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
​  (Details: serial 39232 error_code 2 request_code 151 minor_code 24)
​  (Note to programmers: normally, X errors are reported asynchronously;
​   that is, you will receive the error a while after causing it.
​   To debug your program, run it with the --sync command line
​   option to change this behavior. You can then get a meaningful
​   backtrace from your debugger if you break on the gdk_x_error() function.)

I tried building prior versions from source; they spit out the same error back to 2.8. Version 2.7 works fine. I haven't checked versions beneath that.

Discussion

  • Adam P. Goucher

    Adam P. Goucher - 2019-03-24
    I can confirm this happens occasionally on Ubuntu with the XFCE desktop environment. It often fixes itself eventually (maybe after a reboot or apt-get dist-upgrade?), though.
     
    -- APG.
     
    Sent: Sunday, March 24, 2019 at 2:40 PM
    From: "Ticket #47: Golly doesn't open on ArchLinux/XFCE: X Window System error" <47@bugs.golly.p.re.sourceforge.net>
    To: "Ticket #47: Golly doesn't open on ArchLinux/XFCE: X Window System error" <47@bugs.golly.p.re.sourceforge.net>
    Subject: [golly:bugs] #47 Golly doesn't open on ArchLinux/XFCE: X Window System error

    [bugs:#47] Golly doesn't open on ArchLinux/XFCE: X Window System error

    Status: open
    Group: v1.0 (example)
    Labels: X X Window System
    Created: Sun Mar 24, 2019 02:40 PM UTC by Anonymous
    Last Updated: Sun Mar 24, 2019 02:40 PM UTC
    Owner: nobody

    Recent versions of golly, from 2.8 to 3.2, do not work on my system due to an X Window System error. I'm on Arch Linux (5.0.2-arch1-1-ARCH) with desktop environment XFCE (Xfce 4.12). It doesn't matter if you get it from the AUR or from source; running golly yields the same error:

    The program 'golly' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
​  (Details: serial 39232 error_code 2 request_code 151 minor_code 24)
​  (Note to programmers: normally, X errors are reported asynchronously;
​   that is, you will receive the error a while after causing it.
​   To debug your program, run it with the --sync command line
​   option to change this behavior. You can then get a meaningful
​   backtrace from your debugger if you break on the gdk_x_error() function.)

    I tried building prior versions from source; they spit out the same error back to 2.8. Version 2.7 works fine. I haven't checked versions beneath that.

    Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/golly/bugs/47/

    To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

     
     

    • Chris Rowett

      Chris Rowett - 2019-03-25

      The main change that might be relevant in 2.8 was a switch to OpenGL for
      rendering.

       
      alternate

  • Andrew Trevorrow

    Andrew Trevorrow - 2019-03-25

    Which version of wxWidgets are you using? Try the latest stable release (3.0.4) and if that still doesn't work try the latest development release (3.1.2). Make sure you can build and run the opengl samples included with wxGTK. If they work then Golly should work.

     

  • Maks Verver

    Maks Verver - 2019-04-07

    As another datapoint: I can run Golly on Arch Linux using XFCE as the window manager just fine; both the AUR package and the binary distribution work (using wxgtk2,which is wxWidgets 3.0.4 built with GTK 2).

    If this is related to OpenGL, perhaps the problem is specific to the display drivers used? For refenence, I'm using the intel xorg driver with i965 mesa driver. (If you're unsure: the xdriinfo and glxinfo commands may be useful.)

    Adam/reporter: which display drivers are you using?