GNOME Bugzilla – Bug 503978
crash in Panel: just i have wait
Last modified: 2007-12-23 21:30:29 UTC
Version: 2.20.2 What were you doing when the application crashed? just i have wait Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.23-1-amd64 #1 SMP Fri Nov 30 12:19:15 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: SphereCrystal Icon Theme: SphereCrystal Memory status: size: 272277504 vsize: 272277504 resident: 28659712 share: 14671872 rss: 28659712 rss_rlim: 18446744073709551615 CPU usage: start_time: 1197714355 rtime: 1032 utime: 958 stime: 74 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2b3fc2847f90 (LWP 3460)] (no debugging symbols found) 0x00002b3fbc233315 in waitpid () from /lib/libpthread.so.0
+ Trace 182084
Thread 1 (Thread 0x2b3fc2847f90 (LWP 3460))
----------- .xsession-errors --------------------- THE STARTUP WILL BE CANCELLED NOW! ** (gnome-cups-icon:3485): WARNING **: Could not start the printer tray icon, because the CUPS server could not be contacted. ** (gnome-panel:3460): WARNING **: Failed to establish a connection with GDM: No such file or directory (gnome-panel:3460): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -23 and height 25 ** (gnome-panel:3460): WARNING **: Failed to establish a connection with GDM: No such file or directory ** ERROR **: file orbit-object.c: line 149 (do_unref): assertion failed: (robj->refs < ORBIT_REFCOUNT_MAX && robj->refs > 0) aborting... warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7ffff14a0000 --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 452428 ***