You are not logged in.
I found reproducible crash of Firefox, probably since glycin gdk-pixbuf2 dependency (so Firefox version 143 and 144).
How to do it:
1. Start Firefox.
2. Go to settings.
3. Select option "Ask where to save every file" (translation is mine, so it may be a bit different).
4. Go to any site where you can download and save any file to disk (when window to select directory where to save downloaded file is trying to open, you get instant crash).
5. You get Firefox report window and you can close Firefox or restart it. No coredump in coredumpctl is created.
Notice:
I start Firefox in firejail, so maybe it would be related with this or not.
No icons are displayed in settings > general > applications > content type.
Someone confirm or deny this.
Last edited by xerxes_ (2026-03-11 22:55:47)
Offline
Tested on firefox 144.0-1 without firejail:
no crashes, icons are displayed
Offline
https://gitlab.gnome.org/GNOME/glycin/-/issues/203
obvious answer is that confining apps from the outside […] is doomed to fail.
"You're running it wrongly"…
Next to firejail, the file dialog might go through the xdg-desktop portals where the specific implementation might matter.
nb, that FF itself does not depend on glycin, gdk-pixbuf2 does and there're various threads about that and there's https://aur.archlinux.org/packages/gdk-pixbuf2-noglycin
Offline
I done some tests and find out that I can simplify FF crash procedure:
1. Run Firefox with firejail.
2. Do some operation to open file manage window, like: Open file, Save web as, Print, Import from other browser, etc.
Thunderbrid may also crash.
And chromium (and probably other chromium based browsers) don't crash, because they doesn't have gdk-pixbuf2 dependency.
UPDATE:
Print, import from other browser and send link don't crash FF because they open FF windows, not foreign file manager window; I write earlier that they crash, because I didn't check earlier it.
Last edited by xerxes_ (2025-10-17 10:59:42)
Offline
glycin not working w/ outer sandboxes is a known issue (see the upstream bug and several existing other threads)
Offline
For now the fix is, as far as I can tell, downgrading gdk-pixbuf2 to 2.44.1-3, or relaxing firejail rules as stated here:
https://github.com/netblue30/firejail/issues/6906
Glycin was supposed to have it fixed on version 2.0.1? But we are on 2.0.3 and it still happens... fun stuff.
Last edited by LuxFerre (2025-10-16 21:47:49)
Offline
Afaiu what was fixed was the general leaking of stale processes but nothing around the problems reg. outer sandboxing?
https://gitlab.gnome.org/GNOME/glycin/- … type=HEADS
Offline
After many updates the issue has solved itself, so I mark it as solved.
Offline