That makes sense, are they intended to persist indefinitely, only while the subject application is running, or do they go away after a period of time? Thanks for your help!
Oh okay, so do they go away on their own or do they persist potentially indefinitely? I have used snap in the past but had never noticed these until now. I guess I was just paranoid after the plex vulnerability news haha. Thanks.
I don’t know for certain that these unexpected devices in my disk manager are causing the issue, but I noticed them at the same time as the issue with libation being unable to access the directory it normally uses and so I may be conflating 2 unrelated issues
Okay, I have used snap to install things before but it never generated these faux disks that I can’t seem to delete. Would you guess that it is a temporary issue and a restart should resolve? (haven’t restarted yet because I have been using the audiobookshelf and plex and haven’t scheduled a maintenance window yet)
Oh hooray another mandatory ID checkpoint! Don’t resist, it’s only for your safety and convenience, no other reasons!
/s
Awesome! That was going to be the next thing I looked up was how to do the snap list. It shouldn’t be impacting my libation as that is running in a docker instance managed by portainer. Though now that I think back I had initially installed libation using snap, but couldn’t get it to work, so perhaps I have both instances running and am trying to use the snap one on accident when I need to be opening the docker instance.