GNOME Bugzilla – Bug 602700
crash in Panel: using ximian evolution a...
Last modified: 2009-11-23 12:13:49 UTC
Version: 2.26.3 What were you doing when the application crashed? using ximian evolution and preferences/remove the buttons for 'bord swiping' 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: 472076288 vsize: 472076288 resident: 36945920 share: 18165760 rss: 36945920 rss_rlim: 18446744073709551615 CPU usage: start_time: 1258969073 rtime: 335 utime: 277 stime: 58 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] [New Thread 0x7fed97849910 (LWP 3616)] 0x00007fedaad7051d in waitpid () from /lib/libpthread.so.0
+ Trace 219242
Thread 1 (Thread 0x7fedae0157d0 (LWP 3374))
Inferior 1 [process 3374] 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 --------------------- ** (evolution:3493): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed (gnome-panel:3374): 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 27600 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 ***