Files can't be opened after disconnecting from network
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
- elementary Apps team: Pending requested
-
Diff: 74 lines (+12/-10)3 files modifiedlibcore/gof-directory-async.vala (+2/-4)
src/View/ViewContainer.vala (+3/-2)
src/View/Window.vala (+7/-4)
Changed in pantheon-files: | |
status: | Confirmed → In Progress |
Changed in pantheon-files: | |
milestone: | none → juno-beta1 |
assignee: | nobody → Jeremy Wootten (jeremywootten) |
Changed in pantheon-files: | |
status: | In Progress → Fix Committed |
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.