GNOME Bugzilla – Bug 443379
crash in System Log: rebooting the machine
Last modified: 2007-06-03 01:18:53 UTC
Version: 2.18.0 What were you doing when the application crashed? rebooting the machine Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 50823168 vsize: 50823168 resident: 26804224 share: 9199616 rss: 26804224 rss_rlim: 4294967295 CPU usage: start_time: 1180828869 rtime: 2345 utime: 2301 stime: 44 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 -1209137440 (LWP 15870)] (no debugging symbols found) 0x00886402 in __kernel_vsyscall ()
+ Trace 137648
Thread 1 (Thread -1209137440 (LWP 15870))
----------- .xsession-errors (6 sec old) --------------------- BackupPC BackupPC is stopped vncserver Xvnc is stopped vncserver Xvnc is stopped vncserver Xvnc is stopped vncserver Xvnc is stopped 1180809260.270232 Session manager: gsm-remote-desktop.c:107: remote desktop server died, restarting Loading "installonlyn" plugin warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 4f2a6fd2 Importing GPG key 0x4F2A6FD2 "Fedora Project <fedora@redhat.com>" from /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-2792--1914145808-1180702477 --title root@fc7-jim:/etc/httpd/conf.d --working-directory /et --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 443359 ***