GNOME Bugzilla – Bug 602446
crash in Panel: Closing applications (I ...
Last modified: 2009-11-19 20:35:12 UTC
Version: 2.28.0 What were you doing when the application crashed? Closing applications (I didn't noticed anything special... ?!?) Distribution: Debian squeeze/sid Gnome Release: 2.28.0 2009-10-27 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.31.5 #3 SMP Sun Oct 25 17:21:15 CET 2009 i686 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 Memory status: size: 53141504 vsize: 53141504 resident: 24133632 share: 15224832 rss: 24133632 rss_rlim: 18446744073709551615 CPU usage: start_time: 1258571701 rtime: 1807 utime: 1592 stime: 215 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' [Thread debugging using libthread_db enabled] 0xb6f6597e in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 219192
Thread 1 (Thread 0xb6446750 (LWP 18722))
Inferior 1 [process 18722] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (8 sec old) --------------------- (xchat-gnome:19652): Gtk-WARNING **: Ran out of links (xchat-gnome:19652): Gtk-WARNING **: Ran out of links 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 449501 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) --------------------------------------------------
*** This bug has been marked as a duplicate of bug 597914 ***