Firefox the flatpak version crashed and decided to remove itself from the system, is this common on Linux??
I checked thru Discover and terminal using whereis firefox and all I got is user/lib64/firefox
I should be mad, but I find this too hilarious to be mad… lol… files disappear not entire apps
Did it really uninstall itself? Run this command and check whether you can see Firefox’s ID or not:
flatpak listIf firefox is still in /usr/lib64/firefox, then it should still be there. Maybe just the .desktop file is removed?
OP mentioned that it was the Flatpak version, which doesnt add anything to root owned parts of the filesystem.
what distro?
deleted by creator
No, because it doesn’t happen. Guaranteed your storage device or some other hardware component is having problems that is corrupting your drive.
deleted by creator
It’s… weird, did you do something that accidentally deleted firefox?
deleted by creator
Damn, that’s tough. Have you heard about our lord and savior Ubuntu and it’s blessed snap version of Firefox?
deleted by creator
i avoid using flatpaks if i can. recently had to migrate mine from the root partition to home partition cuz they had filled my root partition space.
As someone formerly involved in security at the enterprise OS development scope, I consider one less Flatpak to be an improvement in security and consistency.
Well done!
deleted by creator
people say this all the time but the reasons they give are always nonsense in my experience, sandboxing alone makes flatpak better
It would be nice if @corsicanguppy@lemmy.ca clarified
I would be interested in knowing why. Isn’t the sandboxing supposed to make security better?
And that’s why I don’t use flatpaks. Nothing like that has ever happened to me.
deleted by creator
Actually, in the case of a web browser, Flatpak weakens both Firefox’s and Chromium’s internal sandboxing, possibly allowing for breaking of cross-site or site-host boundaries. Firefox is even weaker then Chromium as a Flatpak because it can’t use the zypak fork server. Both are weakened, best to avoid.
For basically any other app, Flatpak can be beneficial as a sandbox.
Basically, don’t sandbox browsers because its like wearing 2 condoms. The only sandboxing tool I know that doesn’t interfere with the browser’s sandbox (and also doesnt allow for the possibility of privilege escalation, like Firejail) is Bubblejail
PS: Since you mentioned you are on Fedora, Bubblejail is offered through this COPR repo from the Secureblue team. It provides a sandbox without interfering with the browser’s sandbox. It comes with profiles for Firefox and Chromium. Only issue ive experienced is that the sandbox works, aka it means I can’t access files from my home directory unless explicitly given permission to a folder.
deleted by creator
You still have the binary then. Type
firefoxinto the terminal.deleted by creator
What this person told you was wrong, you need to use
flatpak run [package id]to run flatpak apps. You can doflatpak listto see all installed flatpaks with their ids. An id looks something likeorg.example.appand you’d run it withflatpak run org.example.app.Also, is it shown as being installed in Discover? If it’s not you could try just installing it again and if it is, you can try uninstalling it first. The user data for Firefox should stay intact.
And if ever unsure, look up Firefox on flathub; every app page shows the command line instructions for installing and for running it.
Bash will cache command locations so it doesn’t need to scan your path too frequently. You can clear it with “hash -r”.
See the other comment about running flatpaks - it’s their fatal flaw imho.
its
flatpak run org.mozilla.firefox
