FUSE mount points still exists without any AppImage running

Hi
Thanks for appimaged.
I recently upgraded to latest appimaged .
It was working fine for a week and then I started getting FUSE notifications that app can’t be mounted.

After some search on forums, I found out that I have exceeded the max number of fuse mounts allowed in config which is 1000.

So I manually unmounted all of those.

Today I went to check the mounts in /tmp and found these even though no AppImage is running.

d?????????  ? ?    ?       ?            ? .mount_appima8jkqZd
d?????????  ? ?    ?       ?            ? .mount_appimaAvVQco
d?????????  ? ?    ?       ?            ? .mount_appimaBUnVP4
d?????????  ? ?    ?       ?            ? .mount_appimaDEKSKT
d?????????  ? ?    ?       ?            ? .mount_appimaesHBoS
d?????????  ? ?    ?       ?            ? .mount_appimaFTViJB
drwxrwxr-x  3 root root    0 Apr 28 07:24 .mount_appimagdUt5M
drwxrwxr-x  3 root root    0 Apr 28 07:24 .mount_appimaO9GCYI
drwxrwxr-x  3 root root    0 Apr 28 07:24 .mount_appimapjW797
drwxrwxr-x  3 root root    0 Apr 28 07:24 .mount_appimavtMbFM
drwxr-xr-x  6 root root    0 Aug 16 19:28 .mount_draw.iPiKXB4
drwxr-xr-x  6 root root    0 Aug 17 16:24 .mount_joplinurShB9
drwxrwxr-x  3 root root    0 Feb 17  2021 .mount_pencilE7CTu8

What is with ? and why some are root. service is runnig at user level.

Shouldn’t these be mounted by my username?

I tried to unmount and obviously it failed because they were not mounted by my user.

I followed the guide at github

Thanks

1 Like

Seems like you are running into a bug.
Can you please retry with one of the supported Live systems (e.g., the Ubuntu bionic Live ISO) and see if the issue can be reproduced there?

I know this is an old thread, but I have been running into similar behavior. My systems are RHEL 7 where we have created a python AppImage to provide a newer environment for our infrastructure devs.

I’m trying to figure out if it’s snmpd or some other similar service that walks mounts periodically. The other potential culprit I’ve seen is systemd-tmpfiles.

I’d be curious if you found anything on this. I’m still digging into it, and we’re holding off a full roll-out until we’re sure this will not present an issue.

Hello @kincerb, can you reproduce the issue when running on a Ubuntu bionic Live ISO?