I’m seeing programs freeze when I start any operation that would open a ‘save as’ dialogue box. The behavior is happening with all programs and started suddenly last week.

I’ve been able to trace the problem to a mounted SMB network drive that I access through a VPN. I have the mount specified in /etc/fstab. If I manually unmount (sudo umount -l /path/to/mount/) then all of these ‘save as’ freezes go away, and programs which appeared frozen suddenly come back to life. But if I remount (sudo mount -a) then the freezes return when I try to save anything.

So I have a workaround solution (unmount whenever saving, remount to continue working), but I’m at a loss for how to fix this more permanently. Weird that it began all of a sudden like this, everything used to be fine. I’ve tried updating and that hasn’t helped. Any thoughts are much appreciated!

OS: Ubuntu 22.04.3 LTS x86_64

Kernel: 6.2.0-36-generic

DE: GNOME 42.9

WM: Mutter

  • MrAlternateTape@lemm.eeEnglish
    2·
    1 year ago

    Looks like the network mount is the problem.

    Now you need to find out more. You can try setting up a mount outside the VPN network and check if that causes the same problem.

    If it does, there is something going wrong with mounting over a network.

    If it does not, you can try mounting a different location on the same drive through VPN. If a different folder or location does not cause problems, you know you have to look at the specific location that is causing problems.

    If a different location on the same drive still causes problems, it could be your VPN connection causing problems or maybe the drive is failing. Check the drive for errors, and check if your VPN does work properly overall.

    This should be a decent start to figuring out where the problem is.

    Also make sure to check permissions, since it sounds like the Save as screen is trying to access the location but it does not get the proper response. See if you can access the location in a file explorer.

    • GrappleHatOPEnglish
      1·
      1 year ago

      Thanks for those suggestions! I’ll try them all systematically & report back!

      You mention one possibility that the network drive might be failing. That’s very interesting, because two similar network drives had hardware failures over the weekend & my work’s IT took >3 days to bring them back. That’s pretty unusual, I wonder if those events could be connected to my issue?