For (1), I do have encrypted home directory. Although this is probably
less relevant, I also use the second user I created (i.e. I'm UID 1001
and I don't really use the UID 1000 user)
For (2) and (3) (i.e. system-packages-doc) I'm not sure how to gather
the info you need. Do I need to revert
Is chromium interface `system-packages-doc` connected?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062330
Title:
Chromium fails to start with "invalid home directory"
To manage notifications
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
This is fixed by https://github.com/snapcore/snapd/pull/13857
** Changed in: chromium-browser (Ubuntu)
Status: New => In Progress
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Invalid
** Changed in: snapd (Ubuntu)
Status: New => In Progress
--
You
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Zygmunt Krynicki (zyga)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062330
Title:
Chromium fails to start with "invalid home
Re: #3 above: it no longer shows, though I have a variety of other error
messages, in case of interest (see below).
Thanks again.
$ chromium
update.go:85: cannot change mount namespace according to change mount
(/var/lib/snapd/hostfs/usr/local/share/doc /usr/local/share/doc none bind,ro 0
0):
I think the same fix[1] that was committed to address the related bug
will apply here. Quoting from there:
> Please re-test on snapd edge tomorrow
[1] https://github.com/snapcore/snapd/pull/13853
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
