Nautilus window closes when unmounting currently explored filesystem

[Aleksander Śmierciak]

What happens:
In Nautilus, when exploring a mountable filesystem of a device (having it open in the active window/tab), unmounting this device by the unmount icon on the side panel causes whole window to close, having immediately followed unmounting. If the currently explored folder isn't the one on the filesystem that we unmount, then nothing happens to Nautilus window.

Steps to reproduce:
1. Mount a filesystem.
2. Open Nautilus and explore the content of said filesystem.
3. Unmount said filesystem, for example using the unmount icon on the side panel.
4. In the current state of things, Nautilus window will close immediately due to unmount.

What should happen:
After unmounting an actively explored filesystem, the window/tab should change its focus to a default element, such as computer:/// - like it was before, or perhaps /media, /home?

Alternatively:
Because some consider the desired behaviour as a bug (https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/23293), there should be a possibility to change this behaviour to the way the end user wants it to be - either closing the Nautilus window/tab or changing address to a default element.

It is similar to how Windows 7 explorer.exe works. I personally find this annoying - I have close to twenty partitions total and I like to unmount those on which work I have currently finished without fear of closing the program itself.

It is only a matter of the last few days/weeks that I experienced this behaviour. Some time ago it used to work as described in "What should happen" section.

Description: Ubuntu 11.10
Release: 11.10

nautilus:
  Installed: 1:3.2.1-0ubuntu2
  Candidate: 1:3.2.1-0ubuntu2

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Harry (harry33)]

Yes same here.
Nautilus has been working like this for a while now.
I am using Precise prealfa1 with nautilus_3.2.1-0ubuntu2

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

[Aleksander Śmierciak (aleksander-smierciak)]

Thank you for your input.
I browsed through GNOME Bugzilla bugs and found that Bug no. 530542 (https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/530542) was sent to the developers through GNOME Bugzilla. It got their attention and, according to comments posted under Launchpad bug (the Bugzilla entry was somewhat abandoned), was fixed:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/530542/comments/7
" - Don't auto-close the window you initiated an unmount in (lp: #530542)"

Unfortunately, this is no longer true, since after unmounting, the window auto-closes - and now it doesn't matter if you mount through Nautilus window or any other means, the behaviour is still the same. Nautilus somehow lost its mechanism which redirects window focus to computer:///.

One year ago someone filed a bug at both Launchpad and GNOME Bugzilla which was confirmed and also connected to similar (the same?) bad program behaviour. This issue was to be fixed in nautilus (1:2.29.92-0ubuntu1) (Lucid Lynx timeline) and I do remember Nautilus working correctly back then. But since few weeks the behaviour changed back to the state from before the bugfix.

I am still a newbie when it comes to how Launchpad and Bugtrackers work. I would like someone to tell me if this phenomenon shouldn't be labeled as regression? And should I file a new bug entry at GNOME Bugzilla - or rather post a comment under the bug from year ago?

[NoOp (glgxg)]

Two years and still "UNCONFIRMED"?
 Bug 611569 - Nautilus window quits on unmounting [when partition is launched from places menu]
Product: nautilus
Component: general
Version: 3.2.x
Status: UNCONFIRMED
Priority: Normal
Severity: normal
Description Vish [reporter] 2010-03-02 09:08:49 UTC

Really?

Just upgraded several systems to 12.04 and ran across this bug.

$ apt-cache policy nautilus
nautilus:
  Installed: 1:3.4.2-0ubuntu3
  Candidate: 1:3.4.2-0ubuntu3
  Version table:
 *** 1:3.4.2-0ubuntu3 0
        500 http://archive.ubuntu.com/ubuntu/ precise-updates/main i386 Packages
        100 /var/lib/dpkg/status
     1:3.4.1-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ precise/main i386 Packages

Multiple mounts, multiple tabs, multiple shares & all go 'poof' if I unmount a single mount (including a mount on the same drive/machine).

[Sebastien Bacher (seb128)]

"Two years and still "UNCONFIRMED"?

Did you mean to comment on the bugzilla page? The bug is set to "Triaged" on launchpad, which is a confirmed status

[NoOp (glgxg)]

Actually no - I didn't mean to comment of the bugzilla page. The related upstream is "Two years and still "UNCONFIRMED", however it appears that Ubuntu are awaiting for "upstream" to resolve rather than spending any resource/time on the bug. The "Triaged" tag that you added " was nearly 7 months ago (2011-11-30.

The bug is also tagged "Wishlist" (tagged by you on 2011-11-08). The upstream isn't tagged as 'Wishlist" and is instead tagged as 'Normal". What gives you the impression that this action with Nautilus should be a "Wishlist"?

[Sebastien Bacher (seb128)]

> however it appears that Ubuntu are awaiting for "upstream" to resolve rather than spending any resource/time on the bug

right, we have over 10 000 desktop bugs open and less than 10 people working on the corresponding set, let's say we fix a bug a day including working the weekends, it would take 3 years to get to the bottom of that list ... of course that's considering that no new bug is coming and we would work every single day of the year, neither of those are true.

short version: we don't have enough manpower to fix every single bug

[Sebastien Bacher (seb128)]

> What gives you the impression that this action with Nautilus should be a "Wishlist"?

it's sort of a feature request, but agree you can see it as a long priority bug, the bottom line is that if the location you browse is going away you can't keep browsing it, there are 3 ways out of it, close the folder, display an error, or browser back somewhere else, they are all valid solutions even if the closing can be confusing...

[NoOp (glgxg)]

I think that you've missed:

<quote>
What happens:
In Nautilus, when exploring a mountable filesystem of a device (having it open in the active window/tab), unmounting this device by the unmount icon on the side panel causes whole window to close, having immediately followed unmounting. If the currently explored
</quote>

If you have a USB flash drive, etc., mounted, and right click within nautilus and close this *causes whole window to close* - meaning that nautilus dismisses & you will have lost any *all* work (tabs etc) within that nautilus session and have to start over. Please reconsider. How can this remain a 'Low' priority when work is lost simply by performing an action that worked perfectly fine in 11.04.

Is there anyway to pin down what caused the change in nautilus from (1:2.32.2.1-0ubuntu13) between (1:3.2.1-0ubuntu4.2)
 or nautilus (1:3.2.0-0ubuntu5)?

[NoOp (glgxg)]

Upstream isn't "expired":
https://bugzilla.gnome.org/show_bug.cgi?id=611569
Product: nautilus
Component: general
Version: 3.2.x
Status: RESOLVED
Resolution: OBSOLETE
Priority: Normal
Severity: normal
It was "resolved".

When do Ubuntu plan to do the same?

[NoOp (glgxg)]

re comment #9: It's a *regression*, PLEASE FIX. Unmounting a USB stick, etc, & having Nautilus close as a result is nuts. None of your 'valid solutions' are vaild. Here, try this:

1. Open Nautilus in the morning.
2. Add a few tabs. Spend about half of the day using Nautilus & associated tabs.
3. Insert a USB stick. Do whatever you need to do with the device.
4. Now unmount that USB stick. Poof! your Nautilus session and work is now gone. Everything that you'd been working on in Nautilus is gone.
5. Reopen Nautilus & spend the next 10 minutes (or more) resetting Nautilus to the same working state.

 It's a *regression* *not* a wish listissue.

[Sebastian Geiger (lanoxx)]

Seems this is fixed upstream starting from 3.6

[Ben (pumrum)]

Confirmed in:

Ubuntu 12.04.2 fresh install
Unity 2d
Nautilus 3.4.2