Is chromium interface `system-packages-doc` connected?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2062330
Title:
Chromium fails to start with "invalid home directory"
Macho, just some questions to gain more certainty around your case:
(1) Do you have encrypted home directory (or anything out of the
ordinary)?
(2) Does the below issue (same version of chromium) not happen on snapd
before 2.62?
update.go:85: cannot change mount namespace according to change
Root cause was identified:
In the case of non-deb install (re-exec), Apparmor tunables from host
/etc/apparmor.d/tunables/home.d/...
was not included in the profile for snap-update-ns. The a snapd 2.60 PR that
aimed to fix home directories outside of /home/. missed adding it for the case
of
I will do some tests myself for non-standard home directory.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2061981
Title:
chromium fails to start with non-standard home
As Nathan correctly suggest, this behaviour relates to a snapd 2.62 new
ability introduced for the personal files interface, to create missing
parent directories of write paths/files indicated in the plug
declaration. Release notes: https://forum.snapcraft.io/t/the-snapd-
roadmap/1973
Nathan, thanks for the snapd contribution, it is merged and will be
available in snapd 2.63 that will be available in beta by Monday 15
April.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Test feedback on snapd 2.62 beta would be appreciated.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2032992
Title:
[snap] chromium snap does not allow to read symlinks to
7 matches
Mail list logo