After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 596554 - Gnometris crashes when closing preferences if Theme tab has been selected
Gnometris crashes when closing preferences if Theme tab has been selected
Status: RESOLVED OBSOLETE
Product: quadrapassel
Classification: Applications
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: Jason Clinton
GNOME Games maintainers
: 603963 605896 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-09-28 00:55 UTC by Robert Ancell
Modified: 2013-08-17 07:21 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Robert Ancell 2009-09-28 00:55:47 UTC
When running Gnometris and changing preferences, Gnometris will crash when closing the preferences window if the Themes tab has been selected.

Steps to reproduce:

1. Start Gnometris
2. Click on Settings -> Preferences
3. Click on the Theme tab
4. Close the preferences window (i.e. the X button)

I don't get the crash if selecting the "Close" button.
Comment 1 Jason Clinton 2009-09-29 18:09:04 UTC
This is happening for me now to but it's not a segfault; it's an async X error. I'll look in to it but I suspect drivers. What driver are you using, Robert?
Comment 2 Thomas Andersen 2009-09-29 18:44:46 UTC
I see this too on nvidia (185.18.16-0ubuntu3)
Comment 3 Robert Ancell 2009-09-29 22:38:43 UTC
I'm using the ATI driver (6.12.99+git20090825.fc74e119-0ubuntu2).  I couldn't track down where the error was being triggered.
Comment 4 Thomas Winwood 2009-10-27 06:35:22 UTC
It doesn't appear to be linked to whether the preferences panel is closed via the Close button or the X on the title bar. Both cause Gnometris to quit for me (Ubuntu 9.10, gnometris 2.28.0).

Here's the result of running gnometris from a terminal window, in case it's useful to anyone.

thomas@ketsuban:~$ gnometris
do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working correctly.
Try adjusting the vblank_mode configuration parameter.

(gnometris:24629): ClutterGLX-CRITICAL **: Unable to make the stage window 0x4200026 the current GLX drawable

(gnometris:24629): ClutterGLX-CRITICAL **: Unable to make the stage window 0x4200041 the current GLX drawable

(gnometris:24629): ClutterGLX-CRITICAL **: Unable to make the stage window 0x42001ae the current GLX drawable
The program 'gnometris' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 149 error_code 3 request_code 10 minor_code 0)
  (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.)

The first two ClutterGLX-CRITICAL messages are both associated with the main Gnometris window itself. The third appears when I click the Theme tab.
Comment 5 Jason Clinton 2009-12-08 02:34:56 UTC
*** Bug 603963 has been marked as a duplicate of this bug. ***
Comment 6 Martin Olsson 2010-01-02 14:18:17 UTC
I get this using the intel driver as well. I'm 98% sure it's not a driver issue.

If you start using "quadrapassel --sync" it's 100% reproducible.
Comment 7 Martin Olsson 2010-01-02 14:22:56 UTC
*** Bug 605896 has been marked as a duplicate of this bug. ***
Comment 8 Ivan 2010-01-18 18:02:51 UTC
I too experienced this bug. I'm using intel g45 video card. It's everything like Thomas Winwood reported. This is a critical bug and need to be fixed very soon!
Comment 9 Robert Roth 2012-02-03 17:20:41 UTC
This doesn't happen anymore with quadrapassel 3.3.4.1 on an Intel card, so this can be set to OBSOLETE or FIX RELEASED.
Comment 10 Mario Wenzel 2013-08-17 07:21:56 UTC
This bug was filed against gnometris and seems to be fixed.