GNOME Bugzilla – Bug 597914
Crash in gnome-panel, with accessibility symbols in stack trace
Last modified: 2014-11-14 22:36:12 UTC
Version: 2.28.0 What were you doing when the application crashed? Distribution: Debian squeeze/sid Gnome Release: 2.28.0 2009-09-27 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.30-2-amd64 #1 SMP Fri Sep 25 22:16:56 UTC 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10604000 Selinux: No Accessibility: Enabled GTK+ Theme: Lush Icon Theme: Lush GTK+ Modules: gail:atk-bridge, gnomebreakpad, canberra-gtk-module Memory status: size: 370298880 vsize: 370298880 resident: 25288704 share: 17559552 rss: 25288704 rss_rlim: 18446744073709551615 CPU usage: start_time: 1255102654 rtime: 95 utime: 86 stime: 9 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found) [Thread debugging using libthread_db enabled] 0x00007f01228ec255 in waitpid () from /lib/libpthread.so.0
+ Trace 218181
Thread 1 (Thread 0x7f01259797d0 (LWP 2411))
The program is running. Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** Gdk **: gdk_x11_colormap_foreign_new: assertion `GDK_IS_VISUAL (visual)' failed ----------- .xsession-errors --------------------- QObject::connect: (sender name: 'unnamed') QObject::connect: (receiver name: 'problemReporterWidget') (gnome-panel:2411): Gdk-CRITICAL **: gdk_x11_colormap_foreign_new: assertion `GDK_IS_VISUAL (visual)' failed The program 'gnome-panel' received an X Window System error. This probably reflects a bug in the program. The error was 'BadPixmap (invalid Pixmap parameter)'. (Details: serial 20164 error_code 4 request_code 54 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.) ** ERROR:poa.c:1028:ORBit_POA_activate_object_T: assertion failed: ((poa->life_flags & ORBit_LifeF_DeactivateDo) == 0) --------------------------------------------------
*** Bug 598919 has been marked as a duplicate of this bug. ***
*** Bug 598945 has been marked as a duplicate of this bug. ***
*** Bug 599307 has been marked as a duplicate of this bug. ***
*** Bug 599295 has been marked as a duplicate of this bug. ***
*** Bug 599362 has been marked as a duplicate of this bug. ***
*** Bug 599581 has been marked as a duplicate of this bug. ***
*** Bug 599457 has been marked as a duplicate of this bug. ***
*** Bug 600006 has been marked as a duplicate of this bug. ***
*** Bug 600106 has been marked as a duplicate of this bug. ***
*** Bug 599851 has been marked as a duplicate of this bug. ***
*** Bug 602446 has been marked as a duplicate of this bug. ***
*** Bug 602700 has been marked as a duplicate of this bug. ***
*** Bug 602822 has been marked as a duplicate of this bug. ***
*** Bug 603264 has been marked as a duplicate of this bug. ***
*** Bug 603287 has been marked as a duplicate of this bug. ***
*** Bug 603962 has been marked as a duplicate of this bug. ***
*** Bug 604010 has been marked as a duplicate of this bug. ***
*** Bug 604081 has been marked as a duplicate of this bug. ***
*** Bug 604190 has been marked as a duplicate of this bug. ***
*** Bug 604356 has been marked as a duplicate of this bug. ***
*** Bug 604387 has been marked as a duplicate of this bug. ***
*** Bug 604511 has been marked as a duplicate of this bug. ***
*** Bug 604593 has been marked as a duplicate of this bug. ***
*** Bug 604605 has been marked as a duplicate of this bug. ***
*** Bug 605420 has been marked as a duplicate of this bug. ***
*** Bug 605714 has been marked as a duplicate of this bug. ***
*** Bug 606486 has been marked as a duplicate of this bug. ***
I'm moving the bug to at-spi because of the a11y symbols in the stack trace -- I'm not completely sure I'm right, but at least having someone from the a11y team look at it might help :-)
*** Bug 606773 has been marked as a duplicate of this bug. ***
*** Bug 607213 has been marked as a duplicate of this bug. ***
*** Bug 607450 has been marked as a duplicate of this bug. ***
Should be an accessibility bug. I cannot reproduce the bug, so I don't have a full trace with full symbols. Will try to find one.
*** Bug 608271 has been marked as a duplicate of this bug. ***
*** Bug 608490 has been marked as a duplicate of this bug. ***
*** Bug 608522 has been marked as a duplicate of this bug. ***
*** Bug 608653 has been marked as a duplicate of this bug. ***
*** Bug 608769 has been marked as a duplicate of this bug. ***
*** Bug 606700 has been marked as a duplicate of this bug. ***
*** Bug 612243 has been marked as a duplicate of this bug. ***
*** Bug 614338 has been marked as a duplicate of this bug. ***
No duplicates for 2.30 yet, it seems. Might be obsolete.
No recent duplicates, removing the GNOME Target flag.
Take a look at Bug 606700. This has lots of recent duplicates, including one I just added (#644129). I'm not sure that 606700 is actually a duplicate of this one, since there are significant differences in the stack trace, but someone should take a look at it.
[Resetting QA Contact to newly introduced "at-spi-maint@gnome.bugs". Reason: So far it was impossible to watch changes in at-spi bug reports without following all the specific persons (Li Yuan, Bill Haneman, Jeff Wai, ...) and also their activity outside of at-spi reports. IMPORTANT: Anyone interested in following all bug activity (including all maintainers) must watch the "at-spi-maint@gnome.bugs" dummy user by adding it to the 'Users to watch' list under Preferences->Email preferences. This is also the default procedure nowadays in GNOME when setting up new products.]
[Mass-resetting default assignee, see bug 705890. Please reclaim this bug report by setting the assignee to yourself if you still plan to work on this. Thanks!]
I'm going to go ahead and close this because it concerns a very old version. Feel free to open a new bug if the problem persists.