GNOME Bugzilla – Bug 466203
crash in Open Folder: Menu
Last modified: 2007-08-14 12:06:07 UTC
Version: 2.18.1 What were you doing when the application crashed? Menu "System" > "Administration" > "Login Window" complained about needing root rights. As I didn't want to log into GNOME as root, I right-clicked the menu entry and chose "Add this Launcher to Desktop". Then I right-clicked on the new launcher on the Desktop and chose "Open as Administrator" Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.18.2 2007-08-12 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.20-suspend2-r6-ati-fb #1 SMP Fri Jun 22 14:14:27 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Lush Icon Theme: Nuvola Memory status: size: 75759616 vsize: 75759616 resident: 26759168 share: 21499904 rss: 26759168 rss_rlim: 4294967295 CPU usage: start_time: 1187000732 rtime: 196 utime: 185 stime: 11 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 -1227172176 (LWP 16713)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 154841
Thread 1 (Thread -1227172176 (LWP 16713))
----------- .xsession-errors --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 --------------------------------------------------
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!
Created attachment 93586 [details] backtraces as reported by Bug Buddy (now with debug symbols) Thanks for the quick answer :-) Compiled (re-emerged) nautilus, glib, gtk+ and gnome-vfs with FEATURES="${FEATURES} splitdebug" and CFLAGS="${CFLAGS} -ggdb" in /etc/make.conf (see http://live.gnome.org/GettingTraces/DistroSpecificInstructions#head-48a730f2a3b1cc4497e8507a87ecc55320bdb493) The backtraces don't look much different to me, though. They don't complain about missing debug symbols anymore, so I guess they're "good" now, anyway.
Unfortunately, the trace still has issues. Can you reproduce this while running nautilus under gdb? See http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running for details how to do this. That might help with getting a better trace. Thanks!
Created attachment 93641 [details] gdb session as logged by 'script' command using http://live.gnome.org/GettingTraces/Details#gdb-already-running instead of http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running as a Launcher on the Desktop is involved.
Bingo.
+ Trace 155117
Thread 1 (Thread -1227041104 (LWP 9198))
The crash is in the gksu extensions to nautilus, which is in the x11-libs/gksu package on Gentoo. It's not however directly part of the gnome project, and its bugs are reported to http://savannah.nongnu.org/bugs/?group=gksu Removing /usr/lib/nautilus/extensions-1.0/libnautilus-gksu.so and restarting Nautilus should stop the crash. I think there's also a way to make gksu to compile with the "gnome" flag switched off (Gentoo docs should help you, I don't know how offhand), which should stop this reoccuring if you upgrade gksu.
Thanks, reported there: http://savannah.nongnu.org/bugs/?20781