GNOME Bugzilla – Bug 610390
crash in Panel:
Last modified: 2010-02-18 19:44:11 UTC
Version: 2.28.0 What were you doing when the application crashed? Distribution: Debian squeeze/sid Gnome Release: 2.28.0 2009-11-21 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.30-2-686 #1 SMP Fri Dec 4 00:53:20 UTC 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, canberra-gtk-module Memory status: size: 104751104 vsize: 104751104 resident: 62087168 share: 15134720 rss: 62087168 rss_rlim: 18446744073709551615 CPU usage: start_time: 1266413004 rtime: 82508 utime: 74507 stime: 8001 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] 0xb7efb424 in __kernel_vsyscall ()
+ Trace 220629
Thread 1 (Thread 0xb6b4fad0 (LWP 21715))
A debugging session is active. Inferior 1 [process 21715] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors --------------------- (gnome-panel:21715): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x874d530 (firefox-bin:21735): GLib-WARNING **: g_set_prgname() called multiple times 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 2533016 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 608490 ***