← Back to team overview

linux-traipu team mailing list archive

[Bug 1887804] Re: chromium-browser does not follow XDG base directory specification

 

> Bug reports should stick to fact, using wording like 'Snap-mangled'

I'm sorry, that's factually what happened. Should I have worded it Snap-
disfigured, Snap-distorted, Snap-impaired or Snap-wrecked instead?

> isn't appropriate and not a basis for any discussion.

I have **never** had any software on Linux in the past ten years that
has caused this many issues because of the stuff it does, how that
behaviour is forced on me and which's developers are **this** dismissive
and inappropriate. Issues, some major, have been open for years.

You should have enough empathy to understand that users don't take that
behaviour very kindly for any significant period of time.

-- 
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/1887804

Title:
  chromium-browser does not follow XDG base directory specification

Status in Chromium Browser:
  Invalid
Status in chromium-browser package in Ubuntu:
  Opinion

Bug description:
  Currently Chromium does not follow the XDG base directory
  specification which means that the cache and configuration folder
  aren't properly used.

  This causes the issue that it's nearly impossible to properly migrate
  or back up Chromium configuration (between computers) and it makes for
  example mounting cache as tmpfs or wiping it very very difficult.

  I felt those both immensely when trying to migrate my home folder,
  gigabytes of cache in ~/snap/chromium/[id]/.config/chromium/[folder]
  (and ~/snap itself is also not XDG base directory specification
  compliant, shame!).

  There's also the issue that the previous configuration that is located
  properly, isn't migrated by the migrational package.

  In order to fix this bug, it would require making the snap package
  follow the XDG base directory specification.

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