Closed Bug 1517171 Opened 5 years ago Closed 2 years ago

[snap] firefox cant open /var folder where my torrent client is

Categories

(Release Engineering :: Release Automation: Snap, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: keharuan, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [snap])

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:64.0) Gecko/20100101 Firefox/64.0

Steps to reproduce:

mentioned below


Actual results:

 ive seen a lot of answers about opening magnet links in firefox. a lot of them tell you to go to about:config and change network protocol handler ........ to false etc. ive done that.

now i get an option to choose which application to open the magnet link with. Now here is where my problem lies. i Have firefox installed as a snap package and qbittorrent as a flatpak. when prompted,i try to choose from firefox which app to use for magnet links. the thing is the executable for qbittorrent lies in my /var/lib/flatpak/apps folder. when i try this from the prompt window within firefox it tells me i dont have permission to open /var

ive been advised from stackoverflow to file this as an apparmor bug to mozilla( i dont know what that means)



Expected results:

i should be able to navigate to the executable file for qbittorrent in /var/lib/flatpak/   and thus add it as the default option
Component: Untriaged → File Handling
Component: File Handling → Security: Process Sandboxing
Product: Firefox → Core
Summary: firefox cant open /var folder where my torrent client is → [snap] firefox cant open /var folder where my torrent client is
Whiteboard: [snap]
Blocks: snappy

This is about Snap's sandbox, not ours.

Component: Security: Process Sandboxing → Release Automation: Snap
Product: Core → Release Engineering
QA Contact: jlorenzo
Version: 64 Branch → unspecified

I would suggest closing.
It is a very good thing that Firefox in a snap has no access to the root file system.

This is a limitation from Snap's sandbox and I dont see how we can change and why it would be a good idea.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.