GNOME Bugzilla – Bug 500133
crash in System Log: powering down while wish...
Last modified: 2007-11-28 22:50:23 UTC
Version: 2.18.1 What were you doing when the application crashed? powering down while wishing the automount and autofs worked together so i could see the other drives on my machines-but no Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 40935424 vsize: 40935424 resident: 22003712 share: 15806464 rss: 22003712 rss_rlim: 4294967295 CPU usage: start_time: 1196226963 rtime: 58 utime: 51 stime: 7 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/sbin/gnome-system-log' (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 -1208826144 (LWP 4705)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 179912
Thread 1 (Thread -1208826144 (LWP 4705))
----------- .xsession-errors --------------------- automount is stopped autofs automount is stopped autofs automount (pid 4670) is running... --- Hash table keys for warning below: --> file:///root (nautilus:4782): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. closing gnome-mount 0.6 Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-5042--1210625370-1196221660 --active --geometry 80x24+274+97 --title root@localhost:~ --wo --------------------------------------------------
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 442846 ***