GNOME Bugzilla – Bug 564894
nautilus exits on removing media
Last modified: 2009-01-22 13:37:19 UTC
Steps to reproduce: 1. insert removable media (cd or usb flash drive) 2. unmount mounted volume (if /apps/nautilus/preferences/media_automount gconf key is set) 3. remove media (press eject button on cdrom or detach usb flash drive) 4. at this moment all nautilus windows disappear, taskbar entry "Starting File Browser" appears, it disappears after a while (~5 sec) without any effect. also all desktop icons disappear for about 3 sec. Stack trace: Other information: even if automount option is off, just inserting and removing media causes the same effect. i think, related bug is described here: http://ubuntuforums.org/showthread.php?p=6380641
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
(In reply to comment #1) > Thanks for taking the time to report this bug. > Without a stack trace from the crash it's very hard to determine what caused > it. > Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces > for more information on how to do so. Thanks in advance! > when I run nautilus from console, it starts and goes background. can you tell me, what process should I strace?
What's happening is that when you run nautilus, it detects the existing nautilus process and quits. Run "gnome-session-remove nautilus" and then follow the instructions at http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running to get a stacktrace. Also, please follow http://live.gnome.org/GettingTraces/DistroSpecificInstructions in order to get the debug packages for nautilus so we can have a stacktrace with good debugging symbols. Thanks!
seems that I don't have gnome-session-remove tool in my system (i'm using gentoo with gnome overlay) where can I obtain it? it isn't in gnome-session-2.24.2 sources.
can anyone respond to my previous comment?
Sorry, major chunk of the delay was a bit of confusion on my part. Specifically, Debian appears to have stuck with gnome-session 2.22 (even when upgrading the rest of the Gnome packages), and that version has gnome-session-remove, but 2.24 doesn't, and I'm not sure what the replacement program is offhand. However, there's another route :-) If you follow the instructions at http://live.gnome.org/GettingTraces/Details#gdb-already-running for nautilus we should be able to finally get this sorted out...
here's a backtrace of a crash: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ff975002780 (LWP 30767)] 0x00000000007ee840 in ?? () (gdb) thread apply all bt
+ Trace 211307
Thread 1 (Thread 0x7ff975002780 (LWP 30767))
Continuing. Program received signal SIGCONT, Continued. 0x00007ff96f78d55f in waitpid () from /lib/libpthread.so.0 (gdb)
(In reply to comment #7) > here's a backtrace of a crash: Ok, that's a lot of an improvement getting that trace, but unfortunately there's not quite enough information there yet for me to be able to narrow down exactly what's going on. Looks like probably a crash in hal, so we need the debug symbols for libhal, libdbus and libdbus-glib. http://live.gnome.org/GettingTraces/DistroSpecificInstructions has the information on getting those symbols. Alternately, if there's a more recent version of hal available to you, you might want to try upgrading that and see if it fixes the bug. Thanks for all your help here, hopefully we can figure out what's going wrong here soon...
here you go: a backtrace from bug buddy, which began working after installing debug versions of libraries my package versions are (gentoo): hal-0.5.11-r5 dbus-1.2.3-r1 dbus-glib-0.78 ----------------------------- Distribution: Gentoo Base System release 2.0.0 Gnome Release: 2.24.2 2009-01-04 (Gentoo) BugBuddy Version: 2.24.2 System: Linux 2.6.28-gentoo #1 SMP PREEMPT Fri Dec 26 10:21:35 MSK 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10503000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 399908864 vsize: 399908864 resident: 38236160 share: 22286336 rss: 38236160 rss_rlim: 18446744073709551615 CPU usage: start_time: 1231241552 rtime: 150 utime: 131 stime: 19 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [New Thread 0x7f1831744780 (LWP 14751)] [New Thread 0x7f181f514950 (LWP 14772)] 0x00007f182becf55f in waitpid () from /lib/libpthread.so.0
+ Trace 211311
Thread 1 (Thread 0x7f1831744780 (LWP 14751))
Thanks for taking the time to report this bug. However, this application does not track its bugs in the GNOME Bugzilla. We kindly ask you to report the bug to the application authors. For a selective list of other bug tracking systems please consult http://live.gnome.org/Bugsquad/TriageGuide/NonGnome. If the affected third party application has a bug tracking system you should investigate whether a bug for the reported issue is already filed in this system. If it has not been filed yet please do so. Also ensure that both bug reports contain a link to each other. Thanks in advance! Crash is coming out of HAL, and should be reported to the Bugzilla at FreeDesktop.Org.
here's bug I reported to the Bugzilla at FreeDesktop.Org: http://bugs.freedesktop.org/show_bug.cgi?id=19678 I was told there to report the bug to Gnome bugzilla.
It's definitely not our bug. We can't fix libhal in Nautilus.