GNOME Bugzilla – Bug 599307
crash in Panel:
Last modified: 2009-10-22 14:08:52 UTC
Version: 2.26.3 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-1-686-bigmem #1 SMP Sat Aug 15 20:10:47 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10604000 Selinux: No Accessibility: Enabled GTK+ Theme: Simple Icon Theme: gnome GTK+ Modules: gail:atk-bridge, gnomebreakpad, canberra-gtk-module Memory status: size: 82558976 vsize: 82558976 resident: 23724032 share: 7344128 rss: 23724032 rss_rlim: 18446744073709551615 CPU usage: start_time: 1256124344 rtime: 10030 utime: 8665 stime: 1365 cutime:0 cstime: 8 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' [Thread debugging using libthread_db enabled] 0xb7f17424 in __kernel_vsyscall ()
+ Trace 218486
Thread 1 (Thread 0xb6bff970 (LWP 3845))
----------- .xsession-errors (27 sec old) --------------------- ** (soffice:24347): WARNING **: Focused object has invalid index in parent ** (soffice:24347): WARNING **: Focused object has invalid index in parent 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 884891 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 ***