You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
System-hang when browsing unconnected network share #1378
I have Nemo bookmarks for shares on my local network. Those shares are controller, on the Linux side (they point to a Windows computer) by systemd and Samba and my fstab. Relevant part of the latter:
When I am away from home, naturally I cannot connect to the local network. Yet, if I try to - via a Nemo bookmark - the whole system hangs. I have to press the reset button on the laptop computer.
What should happen
I should get an error mesage and the system should not hang. I hope the problem is with my particular setup. Otherwise, this is a serious bug - though, even if the problem is with my setup, surely it should be easier to create network shares (or at least ones that, unlike normal Samba shares, do not temporarily freeze the system when they are unavailable - though note that such a temporary freeze would be better than the hard-reset-necessitating situation that I am experiencing).
Can confirm I have the same issue, as well as same system. Although using SSHFS.
I've setup a custom shortcut in the keyboard settings menu, to force a cinnamon restart using Super+Shift+R and binding it to cinnamon --replace which seems to be fixing the issue on hanging without needing a full restart.
I too have had this same issue using SSHFS. I have shoddy internet so i'd often lose my connection nemo would completely freeze if I tried to navigate back to my network share after a connection loss.
I've since moved to using filezilla but I would love to see a fix to this issue.
@leigh123linux I pasted what you typed and followed your methods, as well as tried logging the output to the console, but cant seem to get it to print anything at all ever. Not quite sure why.
I can properly replicate the freeze by starting an sshfs on the microserver next to me, and then after opening a folder in it, ie(Browsing to /var inside my mount point)
Then unplugging the cord from the server with nemo open.
Once the server is unplugged browse to /var/www and nemo (or at least its window) will hang.
(Upon additional testing, I dont seem to be able to open any new nemo windows whilst said window has been hung, but other already open windows appear to be working, and the desktop appears to be working in that I can copy to and from working windows, but cant open folders)
I am using a plain old sshfs command as follows for mounting: sshfs /media/nackloose/Server/ [redacted server info]:/
I should also note that pkilling sshfs, and manually disconnecting my network adapter seems to boot me back to my home folder.
Double checked the location of gvfs to make sure it was correct, and it is, just to be safe as noted in your comment.
I'm a bit swamped with everything, but I'll try to answer a bit.
I'm interested if you or others try gid=users,vers=1.0
Why "users"?
I'm not really interested in using a very old, insecure, and IF my memory serves me right, slower version of cifs/smb. I don't use version in my fstab mount because Mint automatically forces the newest (3.1.1) version (from journalctl):
No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
BTW. I'm using Linux Mint Cinnamon 20.3.
Basically my suggestion boils down to this : Try to do a manual CIFS mount that integrates well with gtk apps, while never using gio / udisks / gvfs mounts.
I'm not a linux expert so bear with me; is mounting with fstab ok regarding what you wrote above?
I have a samba NAS mounted through FSTAB and opening Nemo when I'm not connected to my network causes Nemo to take an unreasonable amount of time to open.
Strange why does Nautilus handle this problem as intended...?
Yes Nautilus seems to work, i also tried Thunar and Dolphin. Same issue.
But Nautilus shows it is not some impossibility. Maybe they use threads and don't have to wait 60s for some timeout on a networkshare before doing something else and then immediately hammer it again and have to wait 60s again.
Nautilus doesn't have a dual list though :/
dopus: command not found
Literally the only thing i miss from windows.
May 2026 in LM 22.3 and I can verify the same issue still is not solved. Nemo hangs if the connection to the remote server is cutted, and you cannot stop the process! A window comes up
but nemo is not closing even if you press Force Quit
By default gvfs ignores mounts in /mnt, so Nemo treats them like local folders. x-gvfs-show makes gvfs mark them as network shares, so Nemo skips some of the checks that hung and froze it.
31. By default gvfs ignores mounts in /mnt, so Nemo treats them like local folders. x-gvfs-show makes gvfs mark them as network shares, so Nemo skips some of the checks that hung and froze it.
Activity
Nackloose commentedon Jan 21, 2017
Can confirm I have the same issue, as well as same system. Although using SSHFS.
I've setup a custom shortcut in the keyboard settings menu, to force a cinnamon restart using Super+Shift+R and binding it to
cinnamon --replacewhich seems to be fixing the issue on hanging without needing a full restart.Inphiltration commentedon Jan 21, 2017
I too have had this same issue using SSHFS. I have shoddy internet so i'd often lose my connection nemo would completely freeze if I tried to navigate back to my network share after a connection loss.
I've since moved to using filezilla but I would love to see a fix to this issue.
Mint 18 64-bit cinnamon version 3.0.7 nemo 3.0.6
leigh123linux commentedon Jan 26, 2017
@ACinnamonUserInUK
Can you prove it's a nemo bug (it could equally be a gvfs-smb issue!!), you haven't provided any logs to help debug this issue.
That attitude isn't going to get the issue fixed any quicker, in fact you probably got it pushed to the bottom of the list!
leigh123linux commentedon Jan 26, 2017
@DarthShekels
@Nackloose
Can you provide some error logs for the issue as all my sftp remote shares are working fine
leigh123linux commentedon Jan 27, 2017
@ACinnamonUserInUK
To capture gvfs, try
You might need to alter the gvfsd path to suit
Nackloose commentedon Feb 4, 2017
@leigh123linux I pasted what you typed and followed your methods, as well as tried logging the output to the console, but cant seem to get it to print anything at all ever. Not quite sure why.
I can properly replicate the freeze by starting an sshfs on the microserver next to me, and then after opening a folder in it, ie(Browsing to /var inside my mount point)
Then unplugging the cord from the server with nemo open.
Once the server is unplugged browse to /var/www and nemo (or at least its window) will hang.
(Upon additional testing, I dont seem to be able to open any new nemo windows whilst said window has been hung, but other already open windows appear to be working, and the desktop appears to be working in that I can copy to and from working windows, but cant open folders)
I am using a plain old sshfs command as follows for mounting:
sshfs /media/nackloose/Server/ [redacted server info]:/I should also note that pkilling sshfs, and manually disconnecting my network adapter seems to boot me back to my home folder.
Double checked the location of gvfs to make sure it was correct, and it is, just to be safe as noted in your comment.
leigh123linux commentedon Feb 4, 2017
@Nackloose Try running 'killall nemo' first before
alter the /usr/lib/gvfs/gvfsd to suit the true path location
25 remaining items
Perkolator commentedon May 28, 2023
I'm a bit swamped with everything, but I'll try to answer a bit.
Why "users"?
I'm not really interested in using a very old, insecure, and IF my memory serves me right, slower version of cifs/smb. I don't use version in my fstab mount because Mint automatically forces the newest (3.1.1) version (from journalctl):
No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.BTW. I'm using Linux Mint Cinnamon 20.3.
I'm not a linux expert so bear with me; is mounting with fstab ok regarding what you wrote above?
henr7381 commentedon Jun 4, 2024
I have a samba NAS mounted through FSTAB and opening Nemo when I'm not connected to my network causes Nemo to take an unreasonable amount of time to open.
Perkolator commentedon Jun 4, 2024
Unfortunately it seems that no one that would have the knowledge to try to fix this is interested. :(
martin3000 commentedon Jun 5, 2024
You can use nautilus.
GekoCH commentedon Jul 13, 2024
Strange why does Nautilus handle this problem as intended...?
somenewaccountthen commentedon Jul 24, 2024
Yes Nautilus seems to work, i also tried Thunar and Dolphin. Same issue.
But Nautilus shows it is not some impossibility. Maybe they use threads and don't have to wait 60s for some timeout on a networkshare before doing something else and then immediately hammer it again and have to wait 60s again.
Nautilus doesn't have a dual list though :/
dopus: command not found
Literally the only thing i miss from windows.
Fix blocking when listing or entering a network location with an
taltamir commentedon Nov 10, 2024
I tested the latest versions. This is still an issue on both:
LMDE6
Mint 22
Nautilus does not have this issue.

It smoothly works in all accessible locations.
If you try to go somewhere inaccessible it pops up:
cptX commentedon May 8, 2026
May 2026 in LM 22.3 and I can verify the same issue still is not solved. Nemo hangs if the connection to the remote server is cutted, and you cannot stop the process! A window comes up
but nemo is not closing even if you press Force Quit
Fix blocking when listing or entering a network location with an
bf2lul commentedon Oct 20, 2026
Adding x-gvfs-show to your fstab line might help. For example if the line ends with
noauto 0 0
change it to
noauto,x-gvfs-show 0 0
Then reboot
Perkolator commentedon Oct 20, 2026
Why?
bf2lul commentedon Oct 20, 2026
By default gvfs ignores mounts in /mnt, so Nemo treats them like local folders. x-gvfs-show makes gvfs mark them as network shares, so Nemo skips some of the checks that hung and froze it.
OcBuddy commentedon Oct 21, 2026
It should not hang and freeze though.