GNOME Bugzilla – Bug 608271
crash in Panel: I just logged into gdm _...
Last modified: 2010-01-27 18:10:53 UTC
Version: 2.28.0 What were you doing when the application crashed? I just logged into gdm _after_ an xorg-upgrade Distribution: Debian squeeze/sid Gnome Release: 2.28.2 2009-12-18 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.32-trunk-686 #1 SMP Sun Jan 10 06:32:16 UTC 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10704000 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: gnomebreakpad, gail:atk-bridge, canberra-gtk-module Memory status: size: 68747264 vsize: 68747264 resident: 20189184 share: 15183872 rss: 20189184 rss_rlim: 18446744073709551615 CPU usage: start_time: 1264611759 rtime: 126 utime: 115 stime: 11 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] 0xb7866424 in __kernel_vsyscall ()
+ Trace 220273
Thread 1 (Thread 0xb64d2ad0 (LWP 3349))
Inferior 1 [process 3349] 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 (8 sec old) --------------------- (gnome-panel:3349): Gdk-WARNING **: /build/buildd-gtk+2.0_2.18.3-1-i386-YrT8XN/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window (gnome-panel:3349): 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 8488 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 ***