Skip to content
This repository has been archived by the owner on Jun 2, 2022. It is now read-only.

gvfsd-fuse process and mounted filesystem leftover after exiting #718

Open
suckatrash opened this issue Feb 6, 2020 · 1 comment
Open
Labels
bug Something isn't working

Comments

@suckatrash
Copy link

Describe the Bug

In Ubuntu 18.04.4 after exiting the shell there is a gvfsd-fuse process and mounted filesystem left mounted. Normally this is fine and if a new instance of wash starts it will re-use the process / mount. However if wash exits abnormally this can create multiple zombie processes / mounts and an inability to start the shell.

Expected Behavior

Wash should cleanup these resources when it exits, or check for their existence when starting.

Steps to Reproduce

Steps to reproduce the behavior:

  1. Start wash
  2. Run pkill wash or similar
  3. The shell fails to initialize, if you kill the process again you will see multiple mounts left over:
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/dev/fuse on /home/user/.cache/wash/mnt014415005 type fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/dev/fuse on /home/user/.cache/wash/mnt454964253 type fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

Environment

  • Version 0.20.1
  • Ubuntu 18.04
@suckatrash suckatrash added the bug Something isn't working label Feb 6, 2020
@welcome
Copy link

welcome bot commented Feb 6, 2020

Thanks for opening your first issue here! We will follow up as soon as we can.

@MikaelSmith MikaelSmith added bug Something isn't working and removed bug Something isn't working labels Mar 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants