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
isPlausibleHome() is an early check (does not result in termination itself) to determine if the calling user have access to its supposed home directory, as a basic way to verify that unintended user cannot exploit the mechanism. In the reported case the personal-files interface connection results in a special type of mount entry that instructs creation of missing parent directories between $HOME and $HOME/.local/share. none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0 Because this entry exists (when the interface is connected), the result from isPlausibleHome() informs if directory creation within $HOME should be allowed or not. This is way disconnecting the interface would solve the problem. (1) Please `stat /home/department/user_name` (2) Does the "permission denied" result in any AppArmor denials? -- 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 directory Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: CURRENT WORKAROUND ------------------ snap disconnect chromium:dot-local-share-applications snap disconnect chromium:dot-local-share-icons 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.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown 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-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done 2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done 2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done 2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
