← Back to team overview

linux-traipu team mailing list archive

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

 

Just to be sure you didn't miss a few facts here as you really like to
rub it under people's noses:

* Snap mangles Chromium's configuration directory

* Snap-mangled Chromium configuration directory is not backupable

* Snap-mangled Chromium configuration directory is not compliant with
the de facto interpretation of XDG-BD specification

* Snap-mangled Chromium configuration directory is not compliant with
the spirit of the XDG-BD specification

* Snap-mangled Chromium configuration directory is unnecessarily not
portable between distributions because it assumes the existence of snap


I see a common denominator here - snap's mangling that should really not be done.

-- 
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:
  New
Status in chromium-browser package in Ubuntu:
  New

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