GNOME Bugzilla – Bug 443994
crash in System Log: Restarting PC
Last modified: 2007-06-04 23:56:43 UTC
Version: 2.18.0 What were you doing when the application crashed? Restarting PC 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 71213056 vsize: 71213056 resident: 15966208 share: 8929280 rss: 15966208 rss_rlim: 4294967295 CPU usage: start_time: 1180972001 rtime: 465 utime: 449 stime: 16 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 -1208932640 (LWP 3309)] (no debugging symbols found) 0x0065e402 in __kernel_vsyscall ()
+ Trace 138161
Thread 1 (Thread -1208932640 (LWP 3309))
----------- .xsession-errors --------------------- No wireless interfaces found. Exiting. Launched ok, pid = 3236 Application options saved. Kernel socket closed. ICE default IO error handler doing an exit(), pid = 3233, errno = 0 kbuildsycoca running... DCOP Cleaning up dead connections. Loaded application options. All interfaces: eth0, virbr0 No wireless interfaces found. Exiting. Application options saved. Kernel socket closed. ICE default IO error handler doing an exit(), pid = 3332, errno = 0 Loading "installonlyn" plugin Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-3189-1081603749-1180971870 --active --geometry 80x24+5+49 --title root@localhost:~ --worki --------------------------------------------------
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 ***