I can only second much what has been said. My Java IDE wants to open local Java API doc with my browser (Firefox in that case), and instead of opening the local doc, it shows me an error message because "file://" is pointing to a Snap sandbox or something alike and not to the root filesystem. This seems to indicate a major design flaw of the Firefox snap.
I assume there was a good reason for the Firefox team to switch to snap. However, a huge disadvantage of using Snap for Firefox is that it captured my Firefox profile from my home folder, stored it in the snap directory, and the removal of the snap package (because of the above reason) now all of a sudden also removes my profile, even without using --purge. This is dangerous! Overall, snap or the Firefox snap seems to do a bad job in keeping apps and settings separated. Isn't the latter a really useful best practice in many Linuxes? I wonder why this important principle or useful tradition has been broken here. -- You received this bug notification because you are a member of UBUNTU - AL - BR, which is subscribed to Chromium Browser. https://bugs.launchpad.net/bugs/1972762 Title: Firefox and Chromium snaps preventing apps and devices from working correctly. Status in Chromium Browser: New Status in Mozilla Firefox: New Status in snapd: New Bug description: Many apps put files in /tmp or ~/.cache to then open those files with other apps. Files won't open from those locations with the Firefox snap. Just within a few days of using, I've found quite a few apps that don't work as they should or seem broken as a result. * Any archive manager (xarchive uses /tmp, file-roller and engrampa use ~/.cache, peazip uses ~/.ptmp) * Catfish (uses /tmp also for opening files in archives) * fish (fish_config uses an html file in /tmp and uses a browser for configuration) Other things not working: * WebUSB (Used in Chromium for securely interacting with USB devices, installing and updating Android devices, etc) * USBMidi (Used in Chromium and Firefox for using Midi instruments) To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1972762/+subscriptions -- Mailing list: https://launchpad.net/~linux-traipu Post to : linux-traipu@lists.launchpad.net Unsubscribe : https://launchpad.net/~linux-traipu More help : https://help.launchpad.net/ListHelp
