fx is a terminal JSON viewer (strict, core24). Users open files under /mnt,
/media and /run/media (mounted volumes, external drives). Without auto-connect
the first run fails with “open file: no such file or directory” and users
assume the snap is broken. Read-only use; fx writes only when the user
explicitly saves (:w). Classic request 53394 was declined in favour of
home + removable-media.
This request has been added to the queue for review by the @reviewers team.
Hello @antonmedv 
As also mentioned by @Lin-Buo-Ren in the classic confinement request topic:
the removable-media interface spec defines a narrow set of application types that may be granted an exception
- major browsers,
- media editors,
- media players/viewers, and
- media recorders
all of which refer to multimedia applications that handle audio, video, or image files on external devices. As fx is a JSON viewer, it does not fall within the exception categories that justify auto-connecting removable-media.
Hence this is a -1 from my side for granting auto-connection of removable-media to the fx snap.
The strict-confinement setup with home (auto-connected) and removable-media (manually connected) is the correct architecture. We encourage documenting the snap connect step in the snap’s store listing or README so users know how to enable external-media access when they need it.
1 Like
Hello,
I agree with @yomonokio’s reasoning above, this is a -1 from me for granting removable-media auto-connection.
I see you already have instructions in your description for manually connecting the interface. To assist users who want use the snap with removable-media, you could also check if the interface is connected programmatically in your application using: snapctl is-connected <plug-name> and prompt the user to run sudo snap connect fx:removable-media. This could help avoid user’s confusing this for a bug.
Thank you.
1 Like