GNOME Bugzilla – Bug 467173
crash in Panel: Gnome desktop was starti...
Last modified: 2007-09-02 13:06:29 UTC
Version: 2.18.3 What were you doing when the application crashed? Gnome desktop was starting up during login. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 40144896 vsize: 40144896 resident: 21094400 share: 17104896 rss: 21094400 rss_rlim: 4294967295 CPU usage: start_time: 1187232471 rtime: 19 utime: 15 stime: 4 cutime:0 cstime: 0 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 -1208760608 (LWP 2888)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 155549
Thread 1 (Thread -1208760608 (LWP 2888))
----------- .xsession-errors --------------------- throttle level is 0 Initializing nautilus-search-tool extension ** (process:2913): WARNING **: can't lock memory: Cannot allocate memory WARNING: not using secure memory for passwords Initializing nautilus-flac-converter extension Initializing nautilus-image-converter extension seahorse nautilus module initialized Window manager warning: Lost connection to the display ':0.0'; most likely the X server was shut down or you killed/destroyed the window manager. Initializing nautilus-open-terminal extension ** ERROR **: file orbit-object.c: line 159 (do_unref): assertion failed: (robj->refs < ORBIT_REFCOUNT_MAX && robj->refs > 0) aborting... --------------------------------------------------
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 ***