[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
No longer affects openlp 2.4.0 and 2.4.6, which OpenLP at GitLab has declared a WontFix. Awaiting 2.9.1 (unreleased as of 29 January 2021) for focal-proposed, groovy-proposed, and hirsute-proposed. I's able to get the EL1210-09 fully up by cherrypicking packages appropriate for nVIDIA 390.nn from the focal Repository, post-installation with nouveau. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: In Progress Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. We have two changes that help address this: * The first one stops immediately configuring multi-arch siblings (e.g. libc6:i386 when it's configuring libc6:amd64). This was not necessary, and caused all the libc6:i386 failures here. * The second change sort of also supersedes the first one: It just ignores any errors from immediate configuration, relying on the fact that it's checked and rectified at a later point if there are unconfigured packages (which is what made all those failures happen spuriously after having successfully installed everything). [Test case] We have one test case in EIPP format in the Debian bug 973305 which was only helped by the second change, not the first one. Run /usr/lib/apt/planners < eipp.log and check there are no errors. TODO: It's unclear if the APT from proposed installed in the live session will fix the installer, needs investigation, but would make a useful test case. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
I confirm this problem still active in the latest Release ISO images for 20.04.1-LTS. Obviously a regression consistent with the ~vorlon observation(s) -- didn't happen in 19.04 or 19.10. Involves PluginInstall.py failing to find exact versions of several packages, although I's unable to screen-shot prior to Installer terminating. Even with the ~qd0t workaround, openlp crashes on open, which didn't happen on 18.04.4-LTS. Attempted clean install on four partitions: /boot (ext2), 4 GiB swap, /home (ext4), / (ext4) emachines/acer EL1210-09 (Acer DA078L) Advance Micro Devices Athlon 64 LE-1620 (P/N AD1620IAA5DH) nVIDIA nForce 780a MCP (C77 64-bit geForce GPU in northbridge) msi GT610-1GD3-LP (nVIDIA GF119 64-bit GPU, 1 GiB DDR3 VRAM) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: In Progress Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. We have two changes that help address this: * The first one stops immediately configuring multi-arch siblings (e.g. libc6:i386 when it's configuring libc6:amd64). This was not necessary, and caused all the libc6:i386 failures here. * The second change sort of also supersedes the first one: It just ignores any errors from immediate configuration, relying on the fact that it's checked and rectified at a later point if there are unconfigured packages (which is what made all those failures happen spuriously after having successfully installed everything). [Test case] We have one test case in EIPP format in the Debian bug 973305 which was only helped by the second change, not the first one. Run /usr/lib/apt/planners < eipp.log and check there are no errors. TODO: It's unclear if the APT from proposed installed in the live session will fix the installer, needs investigation, but would make a useful test case. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find
[Touch-packages] [Bug 1773476] Re: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.img-4.8.0 when no corresponding vmlinuz present
Actually would have been a bug against either apt or dpkg, which failed to clean up /var after Kernel package removal. Since upgraded to ubuntu Focal, closing Bug. ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1773476 Title: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.img-4.8.0 when no corresponding vmlinuz present Status in initramfs-tools package in Ubuntu: Invalid Bug description: With LinUX Images/-Extras 4.15.0-22-generic, 4.13.0-43-generic, 4.8.0-58-generic, 4.8.0-56-generic, and 4.4.0-127-generic installed, sudo dpkg-reconfigure linux-firmware returns the following to Console: update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic update-initramfs: Generating /boot/initrd.img-4.13.0-43-generic update-initramfs: Generating /boot/initrd.img-4.8.0-58-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.4.0-127-generic Same configuration report for "Setting up linux-firmware..." with sudo apt(-get) install (--reinstall) linux-firmware and sudo apt-get upgrade linux-firmware. Therefore: Reproducible: Always Steps to reproduce: sudo apt install (--reinstall) linux-firmware or sudo dpkg-reconfigure linux-firmware. Actual results, excepting actually installed Kernel Image packages: update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory Expected results, excepting actually installed Kernel Image packages: No attempt to generate /boot/initrd.img for missing kernels, thus no warnings, errors or fatals. UPDATE: Solved via sudo rm -rf /var/lib/initramfs-tools/4.8.0 && sudo rm -rf /var/lib/initramfs-tools/4.8.0-56. Recommend check for bug(s) in apt and dpkg of which this Bug may be a depend, as automatic housecleaning failed me in this specific case. --- ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: Unity Dependencies: DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-05-17 (373 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: linux-firmware 1.157.19 [origin: unknown] PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-22.24~16.04.1-generic 4.15.17 Tags: xenial third-party-packages Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip
[Touch-packages] [Bug 1897369] Re: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)
On my system, I have a consistent Deny on cups-browsed --capable, one example from 281300Z November 2020 being: Nov 28 13:00:24 hotrodgpc-desktop kernel: [ 52.928672] audit: type=1400 audit(1606597224.111:54): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=1496 comm ="cups-browsed" capability=23 capname="sys_nice" I have set cups-browsed to complain mode in AppArmor pending the bugfix. --- ubuntu® 20.04.1-LTS AMD64 AuthenticAMD® Athlon64® 3500+ / 3.3 GiB memory AuthenticAMD® RS780 GPU GNOME 3.36.3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1897369 Title: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE) Status in cups package in Ubuntu: Confirmed Bug description: In Ubuntu 20.04.1 with *cups-browsed* 1.27.4-1, apparmor prevents `/usr/sbin/cups-browsed` to change its nice value. $ sudo dmesg | grep apparmor [541870.509461] audit: type=1400 audit(1600898428.089:60): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=62030 comm="cups-browsed" capability=23 capname="sys_nice" [628298.779668] audit: type=1400 audit(1600984854.115:61): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=66850 comm="cups-browsed" capability=23 capname="sys_nice" [714667.424963] audit: type=1400 audit(1601071220.527:62): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=76828 comm="cups-browsed" capability=23 capname="sys_nice" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1897369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773476] Re: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.img-4.8.0 when no corresponding vmlinuz present
** Description changed: With LinUX Images/-Extras 4.15.0-22-generic, 4.13.0-43-generic, 4.8.0-58-generic, 4.8.0-56-generic, and 4.4.0-127-generic installed, sudo dpkg-reconfigure linux-firmware returns the following to Console: update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic update-initramfs: Generating /boot/initrd.img-4.13.0-43-generic update-initramfs: Generating /boot/initrd.img-4.8.0-58-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.4.0-127-generic Same configuration report for "Setting up linux-firmware..." with sudo apt(-get) install (--reinstall) linux-firmware and sudo apt-get upgrade linux-firmware. Therefore: Reproducible: Always Steps to reproduce: sudo apt install (--reinstall) linux-firmware or sudo dpkg-reconfigure linux-firmware. Actual results, excepting actually installed Kernel Image packages: update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory Expected results, excepting actually installed Kernel Image packages: No attempt to generate /boot/initrd.img for missing kernels, thus no warnings, errors or fatals. - UPDATE: Solved via sudo rm -rf /var/lib/initramfs-tools-4/8/0 && sudo + UPDATE: Solved via sudo rm -rf /var/lib/initramfs-tools-4.8.0 && sudo rm -rf /var/lib/initramfs-tools/4.8.0-56. Recommend check for bug(s) in apt and dpkg of which this Bug may be a depend, as automatic housecleaning failed me in this specific case. --- ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: Unity Dependencies: DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-05-17 (373 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: linux-firmware 1.157.19 [origin: unknown] PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-22.24~16.04.1-generic 4.15.17 Tags: xenial third-party-packages Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True ** Description changed: With LinUX Images/-Extras 4.15.0-22-generic, 4.13.0-43-generic, 4.8.0-58-generic, 4.8.0-56-generic, and 4.4.0-127-generic installed, sudo dpkg-reconfigure linux-firmware returns the following to Console: update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic update-initramfs: Generating /boot/initrd.img-4.13.0-43-generic update-initramfs: Generating /boot/initrd.img-4.8.0-58-generic update-initramfs: Generating
[Touch-packages] [Bug 1773476] Re: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.img-4.8.0 when no corresponding vmlinuz present
SOLVED via sudo rm -rf /var/lib/initramfs-tools/4.8.0 && sudo rm -rf /var/lib/initramfs-tools/4.8.0-56! Recommend check for bug(s) in apt and dpkg, as automatic housecleaning faile me in this specific case. ** Description changed: With LinUX Images/-Extras 4.15.0-22-generic, 4.13.0-43-generic, 4.8.0-58-generic, 4.8.0-56-generic, and 4.4.0-127-generic installed, sudo dpkg-reconfigure linux-firmware returns the following to Console: update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic update-initramfs: Generating /boot/initrd.img-4.13.0-43-generic update-initramfs: Generating /boot/initrd.img-4.8.0-58-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.4.0-127-generic Same configuration report for "Setting up linux-firmware..." with sudo apt(-get) install (--reinstall) linux-firmware and sudo apt-get upgrade linux-firmware. Therefore: Reproducible: Always Steps to reproduce: sudo apt install (--reinstall) linux-firmware or sudo dpkg-reconfigure linux-firmware. Actual results, excepting actually installed Kernel Image packages: update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory Expected results, excepting actually installed Kernel Image packages: No attempt to generate /boot/initrd.img for missing kernels, thus no warnings, errors or fatals. + UPDATE: Solved via sudo rm -rf /var/lib/initramfs-tools-4/8/0 && sudo + rm -rf /var/lib/initramfs-tools/4.8.0-56. Recommend check for bug(s) in + apt and dpkg of which this Bug may be a depend, as automatic + housecleaning failed me in this specific case. + --- ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: Unity Dependencies: DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-05-17 (373 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: linux-firmware 1.157.19 [origin: unknown] PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-22.24~16.04.1-generic 4.15.17 Tags: xenial third-party-packages Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1773476 Title: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.img-4.8.0 when no corresponding vmlinuz present Status in
[Touch-packages] [Bug 1773476] Re: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.img-4.8.0 when no corresponding vmlinuz present
VERIFIED. Found a /var/lib/initramfs-tools/4.8.0 and a /var/lib /initramfs-tools/4.8.0-56 that shoudn't be there. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1773476 Title: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.img-4.8.0 when no corresponding vmlinuz present Status in initramfs-tools package in Ubuntu: Confirmed Bug description: With LinUX Images/-Extras 4.15.0-22-generic, 4.13.0-43-generic, 4.8.0-58-generic, 4.8.0-56-generic, and 4.4.0-127-generic installed, sudo dpkg-reconfigure linux-firmware returns the following to Console: update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic update-initramfs: Generating /boot/initrd.img-4.13.0-43-generic update-initramfs: Generating /boot/initrd.img-4.8.0-58-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.4.0-127-generic Same configuration report for "Setting up linux-firmware..." with sudo apt(-get) install (--reinstall) linux-firmware and sudo apt-get upgrade linux-firmware. Therefore: Reproducible: Always Steps to reproduce: sudo apt install (--reinstall) linux-firmware or sudo dpkg-reconfigure linux-firmware. Actual results, excepting actually installed Kernel Image packages: update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory Expected results, excepting actually installed Kernel Image packages: No attempt to generate /boot/initrd.img for missing kernels, thus no warnings, errors or fatals. --- ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: Unity Dependencies: DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-05-17 (373 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: linux-firmware 1.157.19 [origin: unknown] PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-22.24~16.04.1-generic 4.15.17 Tags: xenial third-party-packages Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1773476/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1594035] Re: unable to shut down the system after suspend / resume
I have a similar issue with ubuntu® 16.04.1: My own system recently hung attempting to initialize not more than two of five swap partitions ("[<>] A start job is running for dev-mapper-cryptswap?.device (??m??s / No limit)") on several attempts and subsequently hung on unattended-upgrades on attempted reboot. Disabling cryptswap worked around the problem. The hang-on-startup problem initially appeared to be centered on hit-and-miss automatic key generation for ecryptfs; but the unattended-upgrades problem is simultaneous. Don't yet know if I've this Bug (viz., #1594035) in specific, or have to file a new Bug, as of 6 December 2016; the answer depends on replies to Question #404663, opened 5 December. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1594035 Title: unable to shut down the system after suspend / resume Status in systemd package in Ubuntu: Confirmed Bug description: In the case of a system that has gone through a suspend / resume cycle, the "shutdown now" command fails with the following output: $ shutdown now Failed to power off system via logind: Transaction is destructive. Failed to start poweroff.target: Interactive authentication required. See system logs and 'systemctl status poweroff.target' for details. Failed to open /dev/initctl: Permission denied Failed to talk to init daemon. --- $ systemctl status poweroff.target ● poweroff.target - Power-Off Loaded: loaded (/lib/systemd/system/poweroff.target; disabled; vendor preset: Active: inactive (dead) Docs: man:systemd.special(7) --- $ systemctl list-jobs JOB UNIT TYPE STATE 438 dev-mapper-cryptswap1.device start running 439 dev-mapper-cryptswap1.swapstart waiting 436 systemd-cryptsetup@cryptswap1.service start running 3 jobs listed. --- Steps to reproduce: 1. Boot system 2. User login to graphical session 3. Close lid while on battery power triggering a suspend 4. Open lid while on battery power triggering a resume 5. Run "shutdown now" from a terminal. Note that the command must be run from the terminal to see output. Selecting "Shut Down..." from the system menu in the menu bar will hide the error output. 6. Observe that the system fails to shut down Expected behavior: At step 6, the system should shut down gracefully. Note that the shutdown process works as expected if steps 3 and 4 are skipped. I suspect that something about the suspend / resume cycle during the session has an interaction effect with the shutdown process, preventing it from executing correctly. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jun 18 18:04:26 2016 EcryptfsInUse: Yes Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b550 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76, Inc. Lemur ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=7aecd352-8a3f-4ce9-88b8-0fc048dc9660 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.06RS76 dmi.board.asset.tag: Tag 12345 dmi.board.name: Lemur dmi.board.vendor: System76, Inc. dmi.board.version: lemu6 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.06RS76:bd11/29/2015:svnSystem76,Inc.:pnLemur:pvrlemu6:rvnSystem76,Inc.:rnLemur:rvrlemu6:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.name: Lemur dmi.product.version: lemu6 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1594035/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp