I can not figure out why this happens. I tried to play around with all the permissions, reset printer settings on Firefox, created new profiles, all had the same problem. But when I used those same profiles on the apt installation it printed just fine. Is there some weird Flatpak sandboxing happening because I can print fine from the Ungoogled Chromium Flatpak but not Firefox Flatpak.
can you launch it from the command line and see if it spits out any useful info before the crash?
At launch it says
Failed to load module "xapp-gtk3-module"
/home/MyUsername/.mozilla/firefox/htzenoyk.Default User/user.js:1: prefs parse error: unexpected character
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
When I go to print and it crashes it says
ExceptionHandler::GenerateDump cloned child 797
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
I will try that once I am back home
Just curious but why would you even want to use a flatpack version when there’s obviously a better (and working) choice?
I value flatpaks sandboxing and permissions.
Install Flatseal, give all the hardware access to Firefox, print, success.
I already did that, no success
Did you try older Firefox flatpack versions?
This is one of the reasons I hate this non native packaging crap.
Iirc there’s a seperate flatpak permission for printing
Already enabled
I had the same issue. I don’t currently have access to my computer to find logs, but I’ll try when I do.
I would report a bug to Mozilla on that one if you can consistently reproduce with a new profile.
I needs 3 times to start ff from flatpak. It crashrs after login twice.
And ff from flatpak also loses its window-borders on wayland.
Something is wrong with your system. That’s not normal.
You use it with wayland?
Here i have Debian stable on 2 computers. Behaviour is the same.
Yes. I’m on Fedora 38 with GNOME on Wayland.
Today i faced the same Problem with Libreoffice… but on X…