I've been using Firefox since 2020 (Kubuntu 20.04 LTS) with a bit of a custom setup:
Since I like moving Data between my Windows and my Linux a lot, I've got a NTFS part… (lire la suite)
I've been using Firefox since 2020 (Kubuntu 20.04 LTS) with a bit of a custom setup:
Since I like moving Data between my Windows and my Linux a lot, I've got a NTFS partition that mounts into my user in Linux.
So /home/user/Desktop or /home/user/Downloads, or [...] is a bind mount that mounts the NTFS user directory there. And since it's Linux and NTFS, this means all files have 777 root root permissions.
This worked fine back in the day. Moving to 22.04 LTS and then 24.04 LTS, I had the problem that Firefox came as a snap. And for snap to allow it to write to the Download directory, I needed to install it in development-mode. And because of my weird setup, I also ran into issues when uploading files.
So I moved to the version of Firefox provided by the mozilla ppa. And this worked.
However the nasty surprise came with version 138.0. First off, it was installed with snap. It ignored my pinned ppa and it did so without warning. I found it weird that once I launched Firefox, all my tabs and bookmarks had disappeared. And once I got the glitchy Downloads again where it would create 10'000 files per download with size 0 I put two and two together and checked the install source. And wouldn't you know it - snap.
Just as a general PSA:
If I go through the effort of adding the ppa, pinning it as the prioritized one I wish for that package to fucking respect that. What else would you expect? A Laptop just happens to have the mozilla ppa pinned. And that just so happens to also be a Laptop that has Firefox installed from said ppa. Of course that's a mistake. Because it's less secure so it needs to be fixed for the user of said laptop. Mozilla you can stop pretending to know better how I want my laptop setup.
However with that not enough - the new Sandbox for Firefox (or whatever new feature this is I'm fighting) now also prevents it from downloading to my Downloads folder with the same 10'000 file issue. And even worse, I cannot edit the target directories for Downloads. It doesn't open the directory selection dialog.
So my question: How do I bypass the write protection for mounts with Firefox 138.0?
And if that doesn't work how do I "unsandbox" Firefox?
PS: Mozilla and your Dev Team, get back to your roots. You're an open source project stop doing this corporate bullshit. First the TOS now this shit. You're starting to rival Microsoft treating user settings as suggestions.