GNOME Bugzilla – Bug 451179
crash in System Log: rebooting fedora
Last modified: 2007-11-15 15:00:03 UTC
Version: 2.18.0 What were you doing when the application crashed? rebooting fedora 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: Fedora Memory status: size: 37208064 vsize: 37208064 resident: 13549568 share: 9314304 rss: 13549568 rss_rlim: 4294967295 CPU usage: start_time: 1182844569 rtime: 424 utime: 401 stime: 23 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 -1208809760 (LWP 3237)] (no debugging symbols found) 0x006d5402 in __kernel_vsyscall ()
+ Trace 143796
Thread 1 (Thread -1208809760 (LWP 3237))
----------- .xsession-errors --------------------- NetworkManagerDispatcher NetworkManagerDispatcher (pid 3053) is running... NetworkManager NetworkManager is stopped NetworkManager NetworkManager is stopped NetworkManager NetworkManager (pid 3086) is running... 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 Importing GPG key 0xDB42A60E "Red Hat, Inc <security@redhat.com>" from /etc/pki/rpm-gpg/RPM-GPG-KEY ** (nautilus:2879): WARNING **: No description found for mime type "x-directory/smb-share" (file is "matvei"), please tell the gnome-vfs mailing list. Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-3146-1571071221-1182829990 --active --geometry 80x25+537+49 --title root@localhost:~ --wor --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
(In reply to comment #1) > Thanks for taking the time to report this bug. > Unfortunately, that stack trace is missing some elements that will help a lot > to solve the problem, so it will be hard for the developers to fix that crash. > Can you get us a stack trace with debugging symbols? Please see > http://live.gnome.org/GettingTraces for more information on how to do so and > reopen this bug or report a new one. Thanks in advance! > Hi, I followed on the link: http://live.gnome.org/GettingTraces But being a Fedora newbie, the directions there are too general for me. I installed *devel* & debug packages and headers as suggested (don't know if I did it right) but BugBuddy's report is still without debug info. If you could give detailed instructions on what to install I'll be happy to oblige. Also, you might want to try to recreate this bug on your system by opening System Log (Sysyem->Administration->System Log) and then System->Shutdown...->Restart Maybe it'll be easier for you this way. Otherwise, please let me know what I need to do in more detail.
*** Bug 453308 has been marked as a duplicate of this bug. ***
*** Bug 453348 has been marked as a duplicate of this bug. ***
*** Bug 454076 has been marked as a duplicate of this bug. ***
*** Bug 461553 has been marked as a duplicate of this bug. ***
*** Bug 467352 has been marked as a duplicate of this bug. ***
*** Bug 467418 has been marked as a duplicate of this bug. ***
*** Bug 467428 has been marked as a duplicate of this bug. ***
*** Bug 467562 has been marked as a duplicate of this bug. ***
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 442846 ***
*** Bug 469017 has been marked as a duplicate of this bug. ***
*** Bug 471817 has been marked as a duplicate of this bug. ***
*** Bug 473808 has been marked as a duplicate of this bug. ***
*** Bug 491066 has been marked as a duplicate of this bug. ***
*** Bug 491251 has been marked as a duplicate of this bug. ***
*** Bug 493796 has been marked as a duplicate of this bug. ***
*** Bug 494775 has been marked as a duplicate of this bug. ***
*** Bug 495033 has been marked as a duplicate of this bug. ***
*** Bug 497040 has been marked as a duplicate of this bug. ***