GNOME Bugzilla – Bug 604593
crash in Panel: Logging in. Then started...
Last modified: 2009-12-15 04:00:46 UTC
Version: 2.28.0 What were you doing when the application crashed? Logging in. Then started Iceweasel browser. We have 3 different log ins for the family and this is the only one that works anymore. Distribution: Debian squeeze/sid Gnome Release: 2.28.0 2009-11-21 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.31-trunk-686 #1 SMP Tue Oct 13 22:34:42 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10605000 Selinux: No Accessibility: Enabled GTK+ Theme: Crux Icon Theme: Crux GTK+ Modules: gnomebreakpad, gail:atk-bridge, canberra-gtk-module Memory status: size: 46940160 vsize: 46940160 resident: 18206720 share: 14389248 rss: 18206720 rss_rlim: 18446744073709551615 CPU usage: start_time: 1260848371 rtime: 108 utime: 90 stime: 18 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] 0xb78be424 in __kernel_vsyscall ()
+ Trace 219605
Thread 1 (Thread 0xb6523ad0 (LWP 2428))
Inferior 1 [process 2428] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** GWeather **: gweather_prefs_parse_temperature: assertion `str != NULL' failed ** GWeather **: gweather_prefs_parse_speed: assertion `str != NULL' failed ** Gdk **: gdk_x11_colormap_foreign_new: assertion `GDK_IS_VISUAL (visual)' failed ----------- .xsession-errors (10 sec old) --------------------- (firefox-bin:2605): GLib-WARNING **: g_set_prgname() called multiple times (gnome-panel:2428): 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 6274 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 ***