GNOME Bugzilla – Bug 599362
crash in Panel: Quit AMSN
Last modified: 2009-10-23 12:59:06 UTC
Version: 2.26.3 What were you doing when the application crashed? Quit AMSN Distribution: Debian squeeze/sid Gnome Release: 2.28.0 2009-09-27 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.30-1-amd64 #1 SMP Sat Aug 15 18:09:19 UTC 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10604000 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: gail:atk-bridge, gnomebreakpad, canberra-gtk-module Memory status: size: 383479808 vsize: 383479808 resident: 39383040 share: 19292160 rss: 39383040 rss_rlim: 18446744073709551615 CPU usage: start_time: 1256256949 rtime: 641 utime: 547 stime: 94 cutime:0 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' [Thread debugging using libthread_db enabled] 0x00007fd1b64f5255 in waitpid () from /lib/libpthread.so.0
+ Trace 218503
Thread 1 (Thread 0x7fd1b979a7d0 (LWP 4008))
----------- .xsession-errors --------------------- (firefox-bin:12297): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed (gnome-www-browser:7069): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' 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 47900 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 ***