nibbles game fails to start

[Brian Herrick]

No other games fail to load except Nibbles.

The program 'gnibbles' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
  (Details: serial 338 error_code 9 request_code 14 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.)

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: gnibbles 1:2.32.1-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-10.44-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic i686
Architecture: i386
CheckboxSubmission: d80cb4cc278138fae7ee7aad927ab2ff
CheckboxSystem: abf102d6ef41328208f5c1554651535a
Date: Tue Jun 28 19:02:35 2011
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-games
UpgradeStatus: Upgraded to natty on 2011-06-19 (9 days ago)

[Pedro Villavicencio (pedro)]

Thanks for the report, could you get a backtrace? you need to use gdb and break on gdk_x_error as in:

gdb gnibbles
$ set logggin on crash-game.txt
$ break gdk_x_error
$ run --sync

reproduce the crash and:
$ thread apply al bt full
then just quit gdb and attach that resulting log file to the report, thanks in advance.

[Brian Herrick (brianherrick)]

I think this is what you're after. The last command wasn't copying all of the ouput of gdb so I just copied it from the terminal.

[Pedro Villavicencio (pedro)]

could you please try again? the log file is showing the same information you pasted early. thanks.

[Brian Herrick (brianherrick)]

What I posted earlier doesn't contain the clutter critical messages. When you say reproduce the crash do you mean to open it through the gnome menu or through the terminal?

[Josh Milthorpe (josh-milthorpe)]

I have the same problem (Nibbles fails to start after upgrade to Natty), although possibly a different bug. Crash was:

$ gnibbles
The program 'gnibbles' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadLength (poly request too large or internal Xlib length erro'.
  (Details: serial 137 error_code 16 request_code 65 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.)

GDB log (using above commands, modulo some typos) was:

Function "gdk_x_error" not defined.
Make breakpoint pending on future shared library load? (y or [n]) Breakpoint 1 (gdk_x_error) pending.
Starting program: /usr/games/gnibbles --sync
[Thread debugging using libthread_db enabled]

Program received signal SIGSEGV, Segmentation fault.
0x05ff2824 in XF86DRIQueryExtension () from /usr/lib/fglrx/libGL.so.1

Thread 1 (Thread 0xb77cd840 (LWP 2532)):
#0 0x05ff2824 in XF86DRIQueryExtension () from /usr/lib/fglrx/libGL.so.1
No symbol table info available.
#1 0x00f89ae6 in ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
No symbol table info available.
A debugging session is active.

 Inferior 1 [process 2532] will be killed.

[Launchpad Janitor (janitor)]

[Expired for gnome-games (Ubuntu) because there has been no activity for 60 days.]