search

igo95862 / bubblejail

Bubblewrap based sandboxing for desktop applications
254 stars 17 forks source link

Firefox Wayland terminating #137

Open boredsquirrel opened 2 weeks ago

boredsquirrel commented 2 weeks ago

Output of bubblejail --version

0.9.3

Your distro name and version

Fedora Kinoite 40

Description

I created a jail for firefox_wayland and also enabled pipewire, v4l and .mozilla access.

running it it seems fine but then fail. I can acces all files without using the portal, from within firefox

bubblejail run firefox firefox
Sandboxed PID: 5048
Bubblewrap started. PID: <Process 5047>
Started unix server
No children found. Terminating.
Terminated
Bubblewrap terminated
igo95862 commented 2 weeks ago

Hello @boredsquirrel

running it it seems fine but then fail. No children found. Terminating.

Looks like Firefox crashes and exits? After there are not more processes in the sandbox the sandbox terminates.

boredsquirrel commented 2 weeks ago

hi, so you mean you can only run

when closing all non-bubblejail instances, it seems to work! (because the kde filepicker portal doesnt work, lol)

igo95862 commented 2 weeks ago

when closing all non-bubblejail instances, it seems to work!

This is because the Firefox acquires the global D-Bus name to do the IPC. If you have some Firefox already using the D-Bus name then launching it again will simply call the already running instance.

There are ways around this.