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 723613 - pressing the eject button causes the location to be navigated to
pressing the eject button causes the location to be navigated to
Status: RESOLVED DUPLICATE of bug 699183
Product: nautilus
Classification: Core
Component: Sidebar
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-02-04 15:09 UTC by Reece H. Dunn
Modified: 2014-02-04 16:35 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Reece H. Dunn 2014-02-04 15:09:51 UTC
STEPS TO REPRODUCE:

1.  Insert removable media (e.g. a media player).
2.  Dismiss the notifications.
3.  Open nautilus (not via the notifications).
4.  Navigate to the Home > Downloads location.
5.  Press the eject button on the removable media device.

OBSERVED BEHAVIOUR:

After Step 5, the user sees the following behaviour:
1.  The folder switches from the Downloads folder to the removable media folder.
2.  The user sees the message:
    | Volume is busy
    | One or more applications is keeping this volume busy
3.  The message goes away after a few seconds.
4.  The folder switches to the Home folder.
5.  The device disappears from the Devices list.

EXPECTED BEHAVIOUR:

1.  The device disappears from the Devices list.

ADDITIONAL NOTES:

It looks like the eject button is causing the "user has selected to go to the selected location/place" event to trigger before the "user has pressed the eject button" event. The selected location event should not trigger.
Comment 1 António Fernandes 2014-02-04 16:35:26 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 version 3.10.

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