Files can't be opened after disconnecting from network

Bug #1677467 reported by Max Mustermann on 2017-03-30
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Files
In Progress
High
Jeremy Wootten

Bug Description

I mount two shared network folders to two folders in my home directory automatically during boot, if I got connection to my home network. Each using cifs in an fstab entry. When those are mounted and later I disconnect from my network, I cannot start Files any more.
It works fine when I remember to sudo umount -a before trying to open Files.
Often I figure that I forgot to unmount the drives after trying to launch Files and then I quickly try to unmount them using the console - sometimes that works, sometimes I cannot unmount them because they're being kept busy by Files.
Apparently, Files doesn't check if previously mounted network drives are still available and always just assumes that they are?

Related branches

Jeremy Wootten (jeremywootten) wrote :

Does Files start eventually if you wait? I find that when a remote samba mount is established (as the only tab) then Files closed then the network connection broken then Files will eventually open after a wait of about 60 seconds.

Changed in pantheon-files:
status: New → Confirmed
importance: Undecided → High
Changed in pantheon-files:
status: Confirmed → In Progress
Max Mustermann (mustermann-23) wrote :

No, it doesn't, I just tried it.

Jeremy Wootten (jeremywootten) wrote :

OK, thanks Max. It looks as if I have not reproduced the bug exactly in that case. Could you let me know the relevant lines in fstab that refer to the mounts (with any personal info redacted)? Also whether when Files closes, which mounts (if any) are being displayed in tabs.

If you are able to build the linked branch to see whether it fixes your problem that would be helpful (make sure any existing Files processes are ended).

If you change the setting org.pantheon.files.preferences.restore-tabs to "false" using dconf-editor (or the command line 'gsettings set org.pantheon.files.preferences restore-tabs false') does it enable Files to open?

Cody Garver (codygarver) on 2017-04-11
Changed in pantheon-files:
milestone: none → juno-beta1
assignee: nobody → Jeremy Wootten (jeremywootten)
Daniel Fore (danrabbit) on 2017-04-11
Changed in pantheon-files:
status: In Progress → Fix Committed
Jeremy Wootten (jeremywootten) wrote :

It has been reported that this bug is not fixed by the linked branch so it is being re-opened.

Changed in pantheon-files:
status: Fix Committed → In Progress
Jeremy Wootten (jeremywootten) wrote :

Part of the problem seems to be that a location mounted this way does not appear to Files to need a network connection to be accessed - it is just part of the local file system. Moreover the location remains mounted by the system when the network connection is broken. So Files will attempt to load it. I find that the tab eventually times out and Files interface is not blocked meanwhile (which is the expected behaviour). However, I also find that trying to load a home folder tab is also blocked until the mount tab times out and then the home folder tab also times out, which is unexpected. Other locations, not below the home folder can be displayed normally.

I'll see if anything can be done to mitigate this.

Jeremy Wootten (jeremywootten) wrote :

I have linked a second experimental branch that you may like to try out.

Jeremy Wootten (jeremywootten) wrote :

I do recommend, however, that you do not mount, in fstab, remote folders at as a child of your home folder. You should use /mnt or another folder you do not normally display directly and use the bookmark to view the folder.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers