chromium fails to start with non-standard home directory
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
Invalid
|
High
|
Nathan Teodosio | ||
snapd (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
CURRENT WORKAROUND
------------------
snap disconnect chromium:
snap disconnect chromium:
Those are just "quality of life" interfaces (c.f. LP:1732482) that most users probably do not even use, disconnecting them will cause no breakage. (Of course, a proper diagnosis and fix is due.)
ORIGINAL REPORT
---------------
cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.
Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/departmen
Used to work fine up to last week.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.
ProcVersionSign
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: XFCE
Date: Wed Apr 17 10:32:18 2024
InstallationDate: Installed on 2017-03-24 (2580 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Snap.Changes:
ID Status Spawn Ready Summary
206 Error 2024-04-
207 Done 2024-04-
208 Done 2024-04-
209 Done 2024-04-
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in chromium-browser (Ubuntu): | |
status: | New → Confirmed |
Changed in chromium-browser (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in snapd (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in snapd (Ubuntu Noble): | |
milestone: | none → noble-updates |
Changed in snapd (Ubuntu): | |
status: | Triaged → Fix Released |
Changed in snapd (Ubuntu Noble): | |
status: | Triaged → Fix Released |
status: | Fix Released → Fix Committed |
Changed in snapd (Ubuntu): | |
status: | Fix Released → Fix Committed |
Changed in snapd (Ubuntu): | |
status: | Fix Committed → Fix Released |
no longer affects: | snapd (Ubuntu Noble) |
no longer affects: | chromium-browser (Ubuntu Noble) |
Changed in snapd (Ubuntu): | |
status: | Fix Released → Confirmed |
Not a duplicate
It's specific to the latest chromium snap update: it worked fine last week. (using chromium only for specific sites. The firefox-esr PPA is my daily driver).
Other snaps don't have this problem. They're still working as they did last week.
And I'm not the only one, See also: /forum. snapcraft. io/t/chromium- cannot- update- snap-namespace- cannot- expand- mount-entry- none-home- local-share- none-x- snapd-kind- ensure- dir-x-snapd- must-exist- dir-home- 0-0-cannot- use-invalid- home-directory/ 39764
https:/