GNOME Bugzilla – Bug 477241
crash in Panel: My system was idle at th...
Last modified: 2007-09-16 08:48:44 UTC
Version: 2.18.3 What were you doing when the application crashed? My system was idle at the Fedora login screen for approximately 1.5 hours, I clicked my username, entered my password and pressed <ENTER>. Then Gnome launched and I received this bug notification popup. 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.5-76.fc7 #1 SMP Thu Aug 30 13:08:59 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 294723584 vsize: 294723584 resident: 21225472 share: 17313792 rss: 21225472 rss_rlim: 18446744073709551615 CPU usage: start_time: 1189870952 rtime: 15 utime: 11 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496376240 (LWP 24637)] (no debugging symbols found) 0x0000003ba800d945 in waitpid () from /lib64/libpthread.so.0
+ Trace 163128
Thread 1 (Thread 46912496376240 (LWP 24637))
----------- .xsession-errors --------------------- localuser:avoelcker being added to access control list SESSION_MANAGER=local/linuxbox.sitescripting.com:/tmp/.ICE-unix/24523 ** (gnome-session:24523): WARNING **: Host name lookup failure on localhost. 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. (gnome-panel:24637): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed beryl: Failed to load slide: /home/robb/hotcorners_racarr.svg beryl: Failed to load slide: /home/robb/hotcorners_racarr.svg --------------------------------------------------
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 446183 ***