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 snap-update-ns template. 


(1) fixed 
https://github.com/snapcore/snapd/pull/13853

(2) and similar issue prevented in the future
https://github.com/snapcore/snapd/pull/13854

Please re-test on snapd edge tomorrow (after the nightly build that will 
include the fix).
It will be available in 2.63 which we are building today and releasing in 
approx 3 weeks.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061981

Title:
  chromium fails to start with non-standard home directory

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to