GNOME Bugzilla – Bug 603287
crash in Panel: I was reading mail with ...
Last modified: 2009-11-29 14:36:26 UTC
Version: 2.26.3 What were you doing when the application crashed? I was reading mail with evolution THE PANNEL CRASH OCCURED WHEN THE UPDATE NOTIFICATION WAS AUTOMATICALY ACCTIVATED Distribution: Debian squeeze/sid Gnome Release: 2.28.0 2009-10-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: 10605000 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: gnomebreakpad, gail:atk-bridge, canberra-gtk-module Memory status: size: 379052032 vsize: 379052032 resident: 35360768 share: 17182720 rss: 35360768 rss_rlim: 18446744073709551615 CPU usage: start_time: 1259488436 rtime: 170 utime: 150 stime: 20 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' [Thread debugging using libthread_db enabled] 0x00007f2b379484de in waitpid () from /lib/libpthread.so.0
+ Trace 219351
Thread 1 (Thread 0x7f2b3abed7d0 (LWP 9769))
Inferior 1 [process 9769] will be detached. Quit anyway? (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 (6 sec old) --------------------- ** (evolution:9848): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed (gnome-panel:9769): 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 11678 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) --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 597914 ***