[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory
1) user_name@computer:~$ stat /home/department/user_name/ File: /home/department/user_name/ Size: 267 Blocks: 289IO Block: 16384 directory Device: 27h/39d Inode: 9542Links: 146 Access: (0755/drwxr-xr-x) Uid: (X/user_name) Gid: (/default_group) Access: 2024-03-20 14:50:40.921533172 +0100 Modify: 2024-04-17 18:20:30.872510781 +0200 Change: 2024-04-17 18:20:30.872510781 +0200 Birth: 2019-06-03 16:14:43.032386913 +0200 2) as far as I know, no apparmor specific denials. The non-standard home directory is added to the apparmor ${HOMEDIRS} paramater (see https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/comments/3) The only error message I get is: user_name@computer:~$ 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 "/home/department/user_name": permission denied snap-update-ns failed with code 1 -- 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 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-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 : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory
Reverting snapd fixes it for me too on multiple computers. -- 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 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-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 : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory
I don't have an encrypted home directory (though it is on a ZFS filesystem, but that one is also NOT encrypted). W. -- 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: chromium 123.0.6312.122 2821 latest/stablecanonical 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 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-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 : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory
PS: Can't revert as I uninstalled and reinstalled chromium yesterday when I first encountered the problem. user_name@computer:~$ sudo snap revert chromium error: cannot revert "chromium": no revision to revert to -- 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: chromium 123.0.6312.122 2821 latest/stablecanonical 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 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-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 : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory
user_name@computer:~$ snap connections chromium | grep personal-files personal-fileschromium:chromium-config :personal-files - personal-fileschromium:dot-local-share-applications :personal-files - personal-fileschromium:dot-local-share-icons :personal-files - disconnecting "chromium:dot-local-share-applications" and "chromium:dot-local-share-icons" seems to fix the problem. Thanks! W;-) -- 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: New Bug description: chromium 123.0.6312.122 2821 latest/stablecanonical 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 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-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 : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory
*** This bug is a duplicate of bug 1620771 *** https://bugs.launchpad.net/bugs/1620771 As far as I can tell, snap and apparmor home directories are set correctly: user_name@computer:~$ sudo snap get system homedirs [sudo] password for user_name: /home/department/ user_name@computer:/home$ sudo grep -R department /etc/apparmor.d/ [sudo] password for user_name: /etc/apparmor.d/tunables/home:@{HOMEDIRS}=/home/ /home/department/ /etc/apparmor.d/tunables/home.d/snapd:@{HOMEDIRS}+="/home/department/" /etc/apparmor.d/tunables/home.d/ubuntu:@{HOMEDIRS}+=/home/department/ -- 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: New Bug description: chromium 123.0.6312.122 2821 latest/stablecanonical 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 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-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 : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory
*** This bug is a duplicate of bug 1620771 *** https://bugs.launchpad.net/bugs/1620771 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: https://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 -- 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: New Bug description: chromium 123.0.6312.122 2821 latest/stablecanonical 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 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-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 : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061981] [NEW] chromium fails to start with non-standard home directory
Public bug reported: chromium 123.0.6312.122 2821 latest/stablecanonical 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 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-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) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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: New Bug description: chromium 123.0.6312.122 2821 latest/stablecanonical 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 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-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 : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017762] Re: GLX apps fail to run in X2Go remote desktop
** Also affects: mesa (Debian) Importance: Undecided Status: New ** Also affects: mesa (Fedora) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2017762 Title: GLX apps fail to run in X2Go remote desktop Status in mesa package in Ubuntu: New Status in mesa package in Debian: New Status in mesa package in Fedora: New Bug description: GLX apps fail to run on Ubuntu LTS 22.04. They used to run fine on Ubuntu LTS 20.04 USER@COMPUTER:~$ glxgears X Error of failed request: GLXUnsupportedPrivateRequest Major opcode of failed request: 143 (GLX) Minor opcode of failed request: 17 (X_GLXVendorPrivateWithReply) Serial number of failed request: 32 Current serial number in output stream: 32 USER@COMPUTER:~$ glxinfo name of display: :50.0 X Error of failed request: GLXUnsupportedPrivateRequest Major opcode of failed request: 143 (GLX) Minor opcode of failed request: 17 (X_GLXVendorPrivateWithReply) Serial number of failed request: 27 Current serial number in output stream: 27 Manually downgrading to mesa-21.x from the Ubuntu 20.04 repository solves the problem: sudo apt purge libgl1-amber-dri sudo dpkg -i \ libegl-mesa0_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libgbm1_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libglapi-mesa_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libglx-mesa0_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libxatracker2_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ mesa-va-drivers_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ mesa-vdpau-drivers_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ mesa-vulkan-drivers_21.2.6-0ubuntu0.1~20.04.2_amd64.deb sudo apt-mark hold \ libegl-mesa0 \ libgl1-mesa-dri \ libglapi-mesa \ libglx-mesa0 \ mesa-va-drivers \ mesa-vdpau-drivers \ mesa-vulkan-drivers \ libgbm1 \ libxatracker2 There's also a discussion about this on the X2Go user list, but no solution so far (just the workaround to downgrade to mesa 21.x): https://lists.x2go.org/pipermail/x2go-user/2022-June/006825.html Similar problems on Ubuntu 23.-04 with mesa 23.x, although there the error message is different. Tested on several computers with connections from different Linux, Windows and Mac clients. All show the same behaviour: no go with mesa-22.x on Ubuntu-22.04. Success with downgraded mesa. How to replicate: - install ubuntu 22.04 on real hardware or on a VM (tested with QEMU/virt-manager) - apt-get install x2goserver-xsession mesa-utils - make X2Go connection from another client to new install - run 'glxinfo' -> GLX error - downgrade mesa to v. 21.x -> no GLX error ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.108.03 Thu Oct 20 05:10:45 UTC 2022 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: XFCE Date: Wed Apr 26 10:41:42 2023 DistUpgraded: 2022-05-12 16:08:31,041 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/510.108.03, 5.19.0-38-generic, x86_64: installed nvidia/510.108.03, 5.19.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204GL [Quadro M4000] [10de:13f1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM204GL [Quadro M4000] [10de:1153] InstallationDate: Installed on 2017-03-24 (2223 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Precision WorkStation 690 ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=UUID=a6888b05-975d-4ffe-9cf1-a37038661267 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to jammy on 2022-05-12 (348 days ago)
[Desktop-packages] [Bug 2017762] [NEW] GLX apps fail to run in X2Go remote desktop
Public bug reported: GLX apps fail to run on Ubuntu LTS 22.04. They used to run fine on Ubuntu LTS 20.04 USER@COMPUTER:~$ glxgears X Error of failed request: GLXUnsupportedPrivateRequest Major opcode of failed request: 143 (GLX) Minor opcode of failed request: 17 (X_GLXVendorPrivateWithReply) Serial number of failed request: 32 Current serial number in output stream: 32 USER@COMPUTER:~$ glxinfo name of display: :50.0 X Error of failed request: GLXUnsupportedPrivateRequest Major opcode of failed request: 143 (GLX) Minor opcode of failed request: 17 (X_GLXVendorPrivateWithReply) Serial number of failed request: 27 Current serial number in output stream: 27 Manually downgrading to mesa-21.x from the Ubuntu 20.04 repository solves the problem: sudo apt purge libgl1-amber-dri sudo dpkg -i \ libegl-mesa0_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libgbm1_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libglapi-mesa_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libglx-mesa0_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libxatracker2_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ mesa-va-drivers_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ mesa-vdpau-drivers_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ mesa-vulkan-drivers_21.2.6-0ubuntu0.1~20.04.2_amd64.deb sudo apt-mark hold \ libegl-mesa0 \ libgl1-mesa-dri \ libglapi-mesa \ libglx-mesa0 \ mesa-va-drivers \ mesa-vdpau-drivers \ mesa-vulkan-drivers \ libgbm1 \ libxatracker2 There's also a discussion about this on the X2Go user list, but no solution so far (just the workaround to downgrade to mesa 21.x): https://lists.x2go.org/pipermail/x2go-user/2022-June/006825.html Similar problems on Ubuntu 23.-04 with mesa 23.x, although there the error message is different. Tested on several computers with connections from different Linux, Windows and Mac clients. All show the same behaviour: no go with mesa-22.x on Ubuntu-22.04. Success with downgraded mesa. How to replicate: - install ubuntu 22.04 on real hardware or on a VM (tested with QEMU/virt-manager) - apt-get install x2goserver-xsession mesa-utils - make X2Go connection from another client to new install - run 'glxinfo' -> GLX error - downgrade mesa to v. 21.x -> no GLX error ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.108.03 Thu Oct 20 05:10:45 UTC 2022 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: XFCE Date: Wed Apr 26 10:41:42 2023 DistUpgraded: 2022-05-12 16:08:31,041 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/510.108.03, 5.19.0-38-generic, x86_64: installed nvidia/510.108.03, 5.19.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204GL [Quadro M4000] [10de:13f1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM204GL [Quadro M4000] [10de:1153] InstallationDate: Installed on 2017-03-24 (2223 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Precision WorkStation 690 ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=UUID=a6888b05-975d-4ffe-9cf1-a37038661267 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to jammy on 2022-05-12 (348 days ago) dmi.bios.date: 04/25/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0MY171 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/25/2008:svnDellInc.:pnPrecisionWorkStation690:pvr:rvnDellInc.:rn0MY171:rvrA01:cvnDellInc.:ct7:cvr:sku: dmi.product.name: Precision WorkStation 690 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.nvidia-graphics-drivers:
[Desktop-packages] [Bug 1976389] [NEW] package chromium-browser 101.0.4951.64-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error
Public bug reported: do-release-upgrade from bionic (18.04) to focal (20.04) crashes on chromium snap installation ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 101.0.4951.64-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.4.0-113.127~18.04.1-generic 5.4.181 Uname: Linux 5.4.0-113-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 Date: Tue May 31 17:07:50 2022 Desktop-Session: 'None' 'None' 'None' Env: 'None' 'None' ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2014-02-14 (3027 days ago) InstallationMedia: Xubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130822) InstalledPlugins: /usr/lib/mozilla/plugins: => npwrapper.nppdf.so (size: 142552 bytes, mtime: Fri Feb 14 16:37:40 2014) Load-Avg-1min: 0.79 Load-Processes-Running-Percent: 0.2% MachineType: Dell Inc. Precision T7610 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-113-generic root=UUID=101706f9-25ad-41c2-865a-d4c215ce639f ro quiet splash nomdmonddf nomdmonisw vt.handoff=1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 101.0.4951.64-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2022-05-31 (0 days ago) dmi.bios.date: 09/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0NK70N dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd09/05/2013:svnDellInc.:pnPrecisionT7610:pvr01:rvnDellInc.:rn0NK70N:rvrA03:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T7610 dmi.product.sku: Precision T7610 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.chromium-browser: [deleted] ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check third-party-packages -- 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/1976389 Title: package chromium-browser 101.0.4951.64-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: New Bug description: do-release-upgrade from bionic (18.04) to focal (20.04) crashes on chromium snap installation ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 101.0.4951.64-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.4.0-113.127~18.04.1-generic 5.4.181 Uname: Linux 5.4.0-113-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 Date: Tue May 31 17:07:50 2022 Desktop-Session: 'None' 'None' 'None' Env: 'None' 'None' ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2014-02-14 (3027 days ago) InstallationMedia: Xubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130822) InstalledPlugins: /usr/lib/mozilla/plugins: => npwrapper.nppdf.so (size: 142552 bytes, mtime: Fri Feb 14 16:37:40 2014) Load-Avg-1min: 0.79 Load-Processes-Running-Percent: 0.2% MachineType: Dell Inc. Precision T7610 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-113-generic root=UUID=101706f9-25ad-41c2-865a-d4c215ce639f ro quiet splash nomdmonddf nomdmonisw vt.handoff=1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 101.0.4951.64-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2022-05-31 (0 days ago) dmi.bios.date: 09/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0NK70N dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd09/05/2013:svnDellInc.:pnPrecisionT7610:pvr01:rvnDellInc.:rn0NK70N:rvrA03:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T7610 dmi.product.sku: Precision T7610 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to:
[Desktop-packages] [Bug 1973070] [NEW] package libreoffice-common 1:7.3.2-0ubuntu2 failed to install/upgrade: installed libreoffice-common package post-installation script subprocess returned error ex
Public bug reported: do-release-upgrade from 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libreoffice-common 1:7.3.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-110.124-generic 5.4.181 Uname: Linux 5.4.0-110-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed May 11 20:59:29 2022 ErrorMessage: installed libreoffice-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-03-24 (1874 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2 apt 2.4.5 SourcePackage: libreoffice Title: package libreoffice-common 1:7.3.2-0ubuntu2 failed to install/upgrade: installed libreoffice-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-05-11 (0 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1973070 Title: package libreoffice-common 1:7.3.2-0ubuntu2 failed to install/upgrade: installed libreoffice-common package post-installation script subprocess returned error exit status 1 Status in libreoffice package in Ubuntu: New Bug description: do-release-upgrade from 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libreoffice-common 1:7.3.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-110.124-generic 5.4.181 Uname: Linux 5.4.0-110-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed May 11 20:59:29 2022 ErrorMessage: installed libreoffice-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-03-24 (1874 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2 apt 2.4.5 SourcePackage: libreoffice Title: package libreoffice-common 1:7.3.2-0ubuntu2 failed to install/upgrade: installed libreoffice-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-05-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1973070/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737750] Re: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2 [error: implicit declaration of function ‘init_timer’]
A 'backport' of "nvidia-340_340.106-0ubuntu3_amd64.deb" from Bionic should do the trick as this is fixed by NVidia in nvidia-340.106: http://www.nvidia.com/Download/driverResults.aspx/130042/en-us "Release Highlights: Fixed a compatibility problem between the nvidia.ko's Page Attribute Table (PAT) support and the kernel Page Table Isolation (PTI) patches." Forcing the installation of "nvidia-340_340.106-0ubuntu3_amd64.deb" from Bionic on Xenial seems to work: sudo dpkg -i --force-depends nvidia-340_340.106-0ubuntu3_amd64.deb This then needs a little massaging: sudo ln -s /usr/lib/nvidia-340/xorg /etc/alternatives/x86_64-linux-gnu_xorg_extra_modules sudo ln -s /etc/alternatives/x86_64-linux-gnu_xorg_extra_modules /usr/lib/x86_64-linux-gnu/xorg/extra-modules And commenting out ModulePath "/usr/lib/nvidia-340/xorg" in /usr/share/X11/xorg.conf.d/nvidia-drm-outputclass-ubuntu.conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1737750 Title: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2 [error: implicit declaration of function ‘init_timer’] Status in nvidia-graphics-drivers-304 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/n/nvidia-graphics-drivers-304/20171212_030744_5105c@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/n/nvidia-graphics-drivers-304/20171212_014232_5105c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1737750/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp