After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 719866 - Issue at unmount
Issue at unmount
Status: RESOLVED DUPLICATE of bug 699183
Product: nautilus
Classification: Core
Component: File and Folder Operations
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-12-04 20:52 UTC by ccomp
Modified: 2013-12-04 21:08 UTC
See Also:
GNOME target: ---
GNOME version: 3.7/3.8

Attachments
Attached device (5.01 KB, image/png)
2013-12-04 20:52 UTC, ccomp 		Details
Directory before unmount (11.68 KB, image/png)
2013-12-04 20:53 UTC, ccomp 		Details
error message when detaching (12.73 KB, image/png)
2013-12-04 20:54 UTC, ccomp 		Details
Directory after unmont (14.14 KB, image/png)
2013-12-04 20:55 UTC, ccomp 		Details

Description ccomp 2013-12-04 20:52:39 UTC 
Created attachment 263533 [details]
Attached device

When I unmount a device (as USB key), Nautilus switch automaticaly on the attached device location ant cuases an error :
Unable to find ...

The previous version (3.6) stays on the place I defined.
Comment 1 ccomp 2013-12-04 20:53:52 UTC 
Created attachment 263534 [details]
Directory before unmount
Comment 2 ccomp 2013-12-04 20:54:27 UTC 
Created attachment 263535 [details]
error message when detaching
Comment 3 ccomp 2013-12-04 20:55:32 UTC 
Created attachment 263536 [details]
Directory after unmont

Nautilus swich automatically to the unmount directory and occurs an error (of course)
Comment 4 António Fernandes 2013-12-04 21:08:50 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 699183 ***