GNOME Bugzilla – Bug 479104
crash in System Log: Rebooting the machine be...
Last modified: 2007-09-25 18:49:01 UTC
Version: 2.18.1 What were you doing when the application crashed? Rebooting the machine because vmware workstation had hung with an open VM. I had tried to kill the vm from with syslog but it would not close. 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.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 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: 285392896 vsize: 285392896 resident: 29626368 share: 13701120 rss: 29626368 rss_rlim: 18446744073709551615 CPU usage: start_time: 1190408351 rtime: 254 utime: 235 stime: 19 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496347984 (LWP 4330)] (no debugging symbols found) 0x0000003a2ae0d945 in waitpid () from /lib64/libpthread.so.0
+ Trace 164523
Thread 1 (Thread 46912496347984 (LWP 4330))
----------- .xsession-errors --------------------- /usr/bin/vmware-config.pl. ** (gnome-system-monitor:4260): WARNING **: SELinux was found but is not enabled. vmware is installed, but it has not been (correctly) configured for this system. To (re-)configure it, invoke the following command: /usr/bin/vmware-config.pl. --- Hash table keys for warning below: --> file:///root (nautilus:5577): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-5645--783391368-1190408813 --active --geometry 80x24+0+49 --title root@localhost:~/vmware/ --------------------------------------------------
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 ***