GNOME Bugzilla – Bug 454276
crash in Open Folder: rebooted after running s...
Last modified: 2007-09-11 13:55:45 UTC
Version: 2.18.1 What were you doing when the application crashed? rebooted after running software updater Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 37232640 vsize: 37232640 resident: 7880704 share: 6647808 rss: 7880704 rss_rlim: 4294967295 CPU usage: start_time: 1183729815 rtime: 6 utime: 4 stime: 2 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (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 -1208092960 (LWP 3164)] (no debugging symbols found) 0x00b74402 in __kernel_vsyscall ()
+ Trace 146124
Thread 1 (Thread -1208092960 (LWP 3164))
----------- .xsession-errors --------------------- localuser:carrbc being added to access control list SESSION_MANAGER=local/D41QM441.auxvlandata.uthscsa.edu:/tmp/.ICE-unix/3050 ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name Error while mapping shared library sections: "/usr/lib/libpanel-applet-2.so.0": not in executable format: File format not recognized. Error while reading shared library symbols: "/usr/lib/libpanel-applet-2.so.0": can't read symbols: File format not recognized. Error while reading shared library symbols: "/usr/lib/libpanel-applet-2.so.0": can't read symbols: File format not recognized. --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, the 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. Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] Please install the following debug packages provided by Fedora: nautilus-debuginfo, glib2-debuginfo, gtk2-debuginfo, pango-debuginfo, gnome-vfs2-debuginfo, libgnome-debuginfo, and libgnomeui-debuginfo. More details can be found here: http://live.gnome.org/GettingTraces
*** Bug 461666 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 449488 ***