[Touch-packages] [Bug 1897747] Re: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
looking further at the space I have available and the compression options, it appears /etc/initramfs-tools/initramfs.conf COMPRESS=gzip update-initramfs -u -k all may be a better work around in my case, until I can resize the boot partition - using gzip appears to allow me to have 3 kernels installed, which should reduce the need for manual intervention. https://askubuntu.com/questions/299396/how-to-reduce-the-size-of-initrd- img-on-ubuntu-13-04 -- 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/1897747 Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: do-rleasae-upgrade from 18.04 to 20.04 today. upgrade from 16.04 to 18.04 performed last Sunday on 5 machines. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.3 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Sep 29 11:56:41 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2013-11-28 (2496 days ago) InstallationMedia: Ubuntu-Server 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.2) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-09-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1897747/+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 1897747] Re: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
I believe I experienced the same, with root cause a lack of free space in /boot. After the upgrade failed with errors, but _before_ attempting a reboot, my workaround was: apt autoremove mkdir /boot_moved_20201011 mv initrd.img-4.15.0-118-generic /boot_moved_20201011/ apt-get upgrade mv /boot_moved_20201011/initrd.img-4.15.0-118-generic . #reboot -- 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/1897747 Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: do-rleasae-upgrade from 18.04 to 20.04 today. upgrade from 16.04 to 18.04 performed last Sunday on 5 machines. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.3 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Sep 29 11:56:41 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2013-11-28 (2496 days ago) InstallationMedia: Ubuntu-Server 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.2) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-09-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1897747/+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 1797282] Re: fsck not running at all on reboot
In my case, Ubuntu 18.04 running on AWS, the problem was as follows: 1. /etc/fstab had 0 in the 6th (passno) field. I presume this is the default that AWS places there, or maybe this is determined by the Ubuntu template on AWS. 2. According to a comment that I found on Stack Overflow, this is used by mkinitramfs to decide not to put fsck in the initrd. This is *in no way* obvious. 3. Without fsck in the initrd, it can't run the fsck, so it just prints a message instead. This message tells you that a fsck is recommended, but it doesn't tell you why it hasn't done one. To fix this: 1. I changed /etc/fstab to have a "1" in the passno field 2. update-initramfs -u 3. reboot, and the check runs as expected. I think the following changes should be made: 1. There should be a console warning during startup if the root volume cannot be checked because fsck is not available. 2. If /etc/fstab is coming from an Ubuntu-controlled template, then passno for the root volume should be set to 1. I know that AWS will fail to boot the instance if the fsck goes interactive, necessitating manual repairs, but surely failing to boot the instance is better than silently running on a corrupt root filesystem. 3. This should be in some documentation somewhere. The fact that mkinitramfs will exclude fsck from the initrd if it thinks you don't need it is particularly obscure. If there is some kind of "getting started with Ubuntu on AWS" then this should be in there. -- 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/1797282 Title: fsck not running at all on reboot Status in systemd package in Ubuntu: Confirmed Bug description: After upgrading some servers from 16.04 to 18.04 I'm met with a MOTD that says: *** /dev/xvda1 should be checked for errors *** I added "fsck.mode=force" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub before running 'sudo update-grub'. I also verified that fsck was present in /boot/grub/grub.cfg afterwards, before rebooting the server. Surprisingly I was met with the same error message in MOTD when logging in. I then ran tune2fs to see when the last check was performed and this is the output: $ sudo tune2fs -l /dev/xvda1 | grep checked Last checked: Wed Sep 12 16:17:00 2018 I then tried to change mount count to 1 with tune2fs -c 1 /dev/xvda1, but after another reboot I was still met with the same error message and the timestamp for last checked was unchanged. I have the same problem on all the servers that was upgraded from 16.04 to 18.04, but also on a new server installed directly with 18.04. In should be mentioned that the servers are AWS EC2 instances, so I have no way of trying to run fsck from a liveusb. Another user has reported the same issue here: https://ubuntuforums.org/showthread.php?t=2403368 I'm not quite sure what information is needed, but attached are some basic information about the system. Please let me know if you need any any other outputs or logs. Edit1: I tested fsck.mode=force on my laptop running Ubuntu 18.04.1 LTS (Xubuntu) and it works fine. Seems to be related to the server edition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1797282/+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 1797282] Re: fsck not running at all on reboot
** Changed in: systemd (Ubuntu) Status: Expired => Confirmed -- 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/1797282 Title: fsck not running at all on reboot Status in systemd package in Ubuntu: Confirmed Bug description: After upgrading some servers from 16.04 to 18.04 I'm met with a MOTD that says: *** /dev/xvda1 should be checked for errors *** I added "fsck.mode=force" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub before running 'sudo update-grub'. I also verified that fsck was present in /boot/grub/grub.cfg afterwards, before rebooting the server. Surprisingly I was met with the same error message in MOTD when logging in. I then ran tune2fs to see when the last check was performed and this is the output: $ sudo tune2fs -l /dev/xvda1 | grep checked Last checked: Wed Sep 12 16:17:00 2018 I then tried to change mount count to 1 with tune2fs -c 1 /dev/xvda1, but after another reboot I was still met with the same error message and the timestamp for last checked was unchanged. I have the same problem on all the servers that was upgraded from 16.04 to 18.04, but also on a new server installed directly with 18.04. In should be mentioned that the servers are AWS EC2 instances, so I have no way of trying to run fsck from a liveusb. Another user has reported the same issue here: https://ubuntuforums.org/showthread.php?t=2403368 I'm not quite sure what information is needed, but attached are some basic information about the system. Please let me know if you need any any other outputs or logs. Edit1: I tested fsck.mode=force on my laptop running Ubuntu 18.04.1 LTS (Xubuntu) and it works fine. Seems to be related to the server edition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1797282/+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 1627769] Re: limits.conf not applied
I've found that editting /etc/systemd/user.conf and inserting lines such as DefaultLimitNOFILE=4 changes the ulimit for the graphical user sessions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1627769 Title: limits.conf not applied Status in lightdm package in Ubuntu: Confirmed Bug description: Since upgraded to 16.10 Yakkety, modifications in /etc/security/limits.conf are not taken into consideration when logging in the graphical interface. /etc/security/limits.conf: @audio - rtprio 99 @audio - memlockunlimited I tried the same settings in /etc/security/limits.d/audio.conf, to the same results. After logging in Unity, opening a console, the limits are not set: blablack@ideaon:~$ ulimit -l -r max locked memory (kbytes, -l) 64 real-time priority (-r) 0 Reloging to my user via bash DOES apply the limits: blablack@ideaon:~$ ulimit -l -r max locked memory (kbytes, -l) 64 real-time priority (-r) 0 blablack@ideaon:~$ su blablack Password: blablack@ideaon:~$ ulimit -l -r max locked memory (kbytes, -l) unlimited real-time priority (-r) 95 Switching to a console (ctrl+alt+f1) and logging in would apply the limits as well. The exact same setup used to work fine on Xenial 16.04 before upgrade. If you need any more information, please let me know. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 26 17:27:10 2016 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1627769/+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 1627769] Re: limits.conf not applied
Still seems to be an issue for me, logging into the terminal I have the modified ulimit values, but not in a lightdm session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1627769 Title: limits.conf not applied Status in lightdm package in Ubuntu: Confirmed Bug description: Since upgraded to 16.10 Yakkety, modifications in /etc/security/limits.conf are not taken into consideration when logging in the graphical interface. /etc/security/limits.conf: @audio - rtprio 99 @audio - memlockunlimited I tried the same settings in /etc/security/limits.d/audio.conf, to the same results. After logging in Unity, opening a console, the limits are not set: blablack@ideaon:~$ ulimit -l -r max locked memory (kbytes, -l) 64 real-time priority (-r) 0 Reloging to my user via bash DOES apply the limits: blablack@ideaon:~$ ulimit -l -r max locked memory (kbytes, -l) 64 real-time priority (-r) 0 blablack@ideaon:~$ su blablack Password: blablack@ideaon:~$ ulimit -l -r max locked memory (kbytes, -l) unlimited real-time priority (-r) 95 Switching to a console (ctrl+alt+f1) and logging in would apply the limits as well. The exact same setup used to work fine on Xenial 16.04 before upgrade. If you need any more information, please let me know. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 26 17:27:10 2016 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1627769/+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 1559731] Re: Battery indicator turns red at 30% on desktop
In my test indicator still turns red at 29% after this proposed update installed: apt list indicator-power -a Listing... Done indicator-power/xenial-proposed,now 12.10.6+16.04.20160708-0ubuntu1 amd64 [installed,automatic] indicator-power/xenial 12.10.6+16.04.20160105-0ubuntu1 amd64 If you would like additional info please list out what is useful. ** Tags removed: verification-needed ** Tags added: verification-failed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1559731 Title: Battery indicator turns red at 30% on desktop Status in Canonical System Image: Fix Released Status in indicator-power package in Ubuntu: Fix Released Status in indicator-power source package in Xenial: Fix Committed Bug description: The indicator turns red as soon as battery goes 30% Please refer to the attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: indicator-power 12.10.6+16.04.20160105-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 20 20:43:32 2016 InstallationDate: Installed on 2016-03-18 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160313) SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1559731/+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 1475945] [NEW] blacklisting i2c_i801 breaks trackpad detection on Acer C710, plus other hardware
Public bug reported: file: /etc/modprobe.d/blacklist.conf contains the text: # causes failure to suspend on HP compaq nc6000 (Ubuntu: #10306) blacklist i2c_i801 note: actually the correct LP id appears to be https://bugs.launchpad.net/bugs/16602 after short discussion at https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329 I'm raising this as a bug as well as preventing trackpad detection in the case of Acer C710, there is an older bug open at https://bugs.launchpad.net/bugs/857175. Here this same blacklist entry breaks some functionality for a Thinkpad T41. In turn, that bug includes a reference to another source (http://permalink.gmane.org/gmane.linux.drivers.i2c/9120) where the blacklist entry has required support effort. lsb_release -rd Description:Ubuntu 15.04 Release:15.04 apt-cache policy kmod kmod: Installed: 18-3ubuntu1 Candidate: 18-3ubuntu1 Version table: *** 18-3ubuntu1 0 500 http://au.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: kmod (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1475945 Title: blacklisting i2c_i801 breaks trackpad detection on Acer C710, plus other hardware Status in kmod package in Ubuntu: New Bug description: file: /etc/modprobe.d/blacklist.conf contains the text: # causes failure to suspend on HP compaq nc6000 (Ubuntu: #10306) blacklist i2c_i801 note: actually the correct LP id appears to be https://bugs.launchpad.net/bugs/16602 after short discussion at https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329 I'm raising this as a bug as well as preventing trackpad detection in the case of Acer C710, there is an older bug open at https://bugs.launchpad.net/bugs/857175. Here this same blacklist entry breaks some functionality for a Thinkpad T41. In turn, that bug includes a reference to another source (http://permalink.gmane.org/gmane.linux.drivers.i2c/9120) where the blacklist entry has required support effort. lsb_release -rd Description: Ubuntu 15.04 Release: 15.04 apt-cache policy kmod kmod: Installed: 18-3ubuntu1 Candidate: 18-3ubuntu1 Version table: *** 18-3ubuntu1 0 500 http://au.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1475945/+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
