GNOME Bugzilla – Bug 421418
Nautilus crash when trying to browse a fresh unmounted volume
Last modified: 2014-01-20 19:31:17 UTC
Distribution: Debian 4.0 Package: nautilus Severity: Normal Version: GNOME2.14.3 2.14.3 Gnome-Distributor: Debian Synopsis: Nautilus crash when trying to browse a fresh unmounted volume Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.14.3 BugBuddy-GnomeVersion: 2.0 (2.14.1) Description: Description of the crash: When i unmounted a volume from /home with a terminal window, the directory still appears in nautilus tree (but not in reality). So i try to go in it (i know it is unmounted but just for a try) and then nautilus crash (what i can understand...) Steps to reproduce the crash: 1. unmount a filesystem with terminal command 2. try to go in the directory freshly unmounted 3. Expected Results: nautilus crash How often does this happen? each time i do the steps described higher Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225631360 (LWP 3352)] [New Thread -1227596880 (LWP 3383)] (no debugging symbols found) 0xb7f2e410 in ?? ()
+ Trace 121081
___________________________________________________________________________ Yahoo! Mail r\xE9invente le mail ! D\xE9couvrez le nouveau Yahoo! Mail et son interface r\xE9volutionnaire. http://fr.mail.yahoo.com ------- Bug created by bug-buddy at 2007-03-22 10:30 ------- Unknown version 2.14.3 in product nautilus. Setting version to "2.14.x".
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!
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
*** Bug 721572 has been marked as a duplicate of this bug. ***