← Back to team overview

linux-traipu team mailing list archive

[Bug 1972762] Re: Firefox snap won't open files in /tmp or ~/.cache -- affects many apps

 

I have been a loyal user of Xubuntu for quite many years, and intend to
remain one for many years to come. Ubuntu decides to use snap for
Firefox, fine. But I agree with an earlier poster that its current state
qualifies for the adjective "broken". I, the user, not the Firefox
packager, should be the one to decide whether or not Firefox should be
allowed to read my hidden files and directories. That there is no easy
way (or any way at all?) to fix that is just not reasonable.

I have just downloaded the Linux Firefox binary from Mozilla, in order
to be able to use Firefox like I always have done. This is sad. I should
really not have to do that for such a cornerstone of my OS-installation.

-- 
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 snap won't open files in /tmp or ~/.cache -- affects many apps

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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1972762/+subscriptions