[Touch-packages] [Bug 1948498] Re: Bluetooth Headset not working when Lenovo P14s AMD Gen1 is connected to Lenovo USB Dock 40AY0090EU
Seems to be fixed with linux-image-5.13.0-39-generic ** Changed in: pulseaudio (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1948498 Title: Bluetooth Headset not working when Lenovo P14s AMD Gen1 is connected to Lenovo USB Dock 40AY0090EU Status in pulseaudio package in Ubuntu: Fix Released Bug description: When the Laptop is not connected to it's dock, the bluethooth headset works. As soon as it is connected to a Lenovo 40AY0090EU Dock, sound stops on the headsets and plays via the display connected via DisplayPort. The headset is still available in sound settings, but even if selected, no sound plays on the headset. If I change the configuration (HSP/A2DP), a short "click" sound can be heard on the headset, so apparently there's still something going on between the laptop and the headsets. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 22 22:04:27 2021 InstallationDate: Installed on 2021-09-29 (23 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1000MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1000MGE:pvrThinkPadP14sGen1:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1:rvnLENOVO:rn20Y1000MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1000MGE dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1948498/+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 1948498] [NEW] Bluetooth Headset not working when Lenovo P14s AMD Gen1 is connected to Lenovo USB Dock 40AY0090EU
Public bug reported: When the Laptop is not connected to it's dock, the bluethooth headset works. As soon as it is connected to a Lenovo 40AY0090EU Dock, sound stops on the headsets and plays via the display connected via DisplayPort. The headset is still available in sound settings, but even if selected, no sound plays on the headset. If I change the configuration (HSP/A2DP), a short "click" sound can be heard on the headset, so apparently there's still something going on between the laptop and the headsets. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 22 22:04:27 2021 InstallationDate: Installed on 2021-09-29 (23 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1000MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1000MGE:pvrThinkPadP14sGen1:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1:rvnLENOVO:rn20Y1000MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1000MGE dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1948498 Title: Bluetooth Headset not working when Lenovo P14s AMD Gen1 is connected to Lenovo USB Dock 40AY0090EU Status in pulseaudio package in Ubuntu: New Bug description: When the Laptop is not connected to it's dock, the bluethooth headset works. As soon as it is connected to a Lenovo 40AY0090EU Dock, sound stops on the headsets and plays via the display connected via DisplayPort. The headset is still available in sound settings, but even if selected, no sound plays on the headset. If I change the configuration (HSP/A2DP), a short "click" sound can be heard on the headset, so apparently there's still something going on between the laptop and the headsets. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 22 22:04:27 2021 InstallationDate: Installed on 2021-09-29 (23 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1000MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1000MGE:pvrThinkPadP14sGen1:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1:rvnLENOVO:rn20Y1000MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1000MGE dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1948498/+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 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full
alias remove-old-kernels='dpkg -l linux-{image,headers}-* | awk
'\''/^ii/{print }'\'' | egrep '\''[0-9]+\.[0-9]+\.[0-9]+'\'' | grep -v
4.4.0-79 | xargs sudo apt-get -y purge'
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1357093
Title:
Kernels not autoremoving, causing out of space error on LVM or
Encrypted installation or on any installation, when /boot partition
gets full
Status in unattended-upgrades:
New
Status in unattended-upgrades package in Ubuntu:
Fix Released
Bug description:
Currently if one chooses to use LVM or encrypted install, a /boot
partition is created of 236Mb
Once kernel updates start being released this partition soon fills
until people are left unable to upgrade.
While you and I might know that we need to watch partition space, many
of the people we have installing think that a windows disk is a disk
and not a partition, education is probably the key - but in the
meantime support venues keep needing to deal with the fact the
partition is too small and/or old kernels are not purged as new ones
install.
For workaround and sytem repair, see
https://help.ubuntu.com/community/RemoveOldKernels
To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1357093/+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 1705813] Re: systemd upgrade to 229-4ubuntu19 fails
I even can't reboot the system: $ sudo reboot [sudo] password for sebastian: Failed to start reboot.target: Failed to activate service 'org.freedesktop.systemd1': timed out See system logs and 'systemctl status reboot.target' for details. Failed to open /dev/initctl: No such device or address Failed to talk to init daemon. -- 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/1705813 Title: systemd upgrade to 229-4ubuntu19 fails Status in systemd package in Ubuntu: New Bug description: systemd upgrade to 229-4ubuntu19 fails: Calculating upgrade... Done The following packages will be upgraded: libmysqlclient20 libnss-myhostname libpam-systemd libsystemd0 libudev1 mysql-client-5.7 mysql-client-core-5.7 mysql-common mysql-server mysql-server-5.7 mysql-server-core-5.7 systemd systemd-sysv udev 14 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 23.8 MB of archives. After this operation, 106 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 systemd-sysv amd64 229-4ubuntu19 [12.4 kB] Get:2 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 libpam-systemd amd64 229-4ubuntu19 [115 kB] Get:3 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 libsystemd0 amd64 229-4ubuntu19 [205 kB] Get:4 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 libnss-myhostname amd64 229-4ubuntu19 [36.4 kB] Get:5 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 systemd amd64 229-4ubuntu19 [3,811 kB] Get:6 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 udev amd64 229-4ubuntu19 [992 kB] Get:7 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 libudev1 amd64 229-4ubuntu19 [55.0 kB] Get:8 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 mysql-client-core-5.7 amd64 5.7.19-0ubuntu0.16.04.1 [6,020 kB] Get:9 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 mysql-common all 5.7.19-0ubuntu0.16.04.1 [15.7 kB] Get:10 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 mysql-client-5.7 amd64 5.7.19-0ubuntu0.16.04.1 [1,654 kB] Get:11 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 mysql-server-5.7 amd64 5.7.19-0ubuntu0.16.04.1 [2,463 kB] Get:12 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 mysql-server-core-5.7 amd64 5.7.19-0ubuntu0.16.04.1 [7,588 kB] Get:13 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 libmysqlclient20 amd64 5.7.19-0ubuntu0.16.04.1 [809 kB] Get:14 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 mysql-server all 5.7.19-0ubuntu0.16.04.1 [10.8 kB] Fetched 23.8 MB in 0s (32.4 MB/s) Preconfiguring packages ... (Reading database ... 112119 files and directories currently installed.) Preparing to unpack .../systemd-sysv_229-4ubuntu19_amd64.deb ... Unpacking systemd-sysv (229-4ubuntu19) over (229-4ubuntu17) ... Processing triggers for man-db (2.7.5-1) ... Setting up systemd-sysv (229-4ubuntu19) ... (Reading database ... 112119 files and directories currently installed.) Preparing to unpack .../libpam-systemd_229-4ubuntu19_amd64.deb ... Unpacking libpam-systemd:amd64 (229-4ubuntu19) over (229-4ubuntu17) ... Preparing to unpack .../libsystemd0_229-4ubuntu19_amd64.deb ... Unpacking libsystemd0:amd64 (229-4ubuntu19) over (229-4ubuntu17) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for libc-bin (2.23-0ubuntu9) ... Setting up libsystemd0:amd64 (229-4ubuntu19) ... Processing triggers for libc-bin (2.23-0ubuntu9) ... (Reading database ... 112119 files and directories currently installed.) Preparing to unpack .../libnss-myhostname_229-4ubuntu19_amd64.deb ... Unpacking libnss-myhostname:amd64 (229-4ubuntu19) over (229-4ubuntu17) ... Preparing to unpack .../systemd_229-4ubuntu19_amd64.deb ... Unpacking systemd (229-4ubuntu19) over (229-4ubuntu17) ... Processing triggers for libc-bin (2.23-0ubuntu9) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for dbus (1.10.6-1ubuntu3.3) ... Processing triggers for ureadahead (0.100.0-19) ... Setting up systemd (229-4ubuntu19) ... addgroup: The group `systemd-journal' already exists as a system group. Exiting. Broadcast message from systemd-journ...@web01.fra.de.nohn.net (Sat 2017-07-22 09:07:52 UTC): systemd[1]: Freezing execution. Failed to try-restart systemd-networkd.service: Failed to activate service 'org.freedesktop.systemd1': timed out See system logs and 'systemctl status systemd-networkd.service' for details. Failed to try-restart systemd-resolved.service: Failed to activate service 'org.freedesktop.systemd1': timed out See system logs and 'systemctl status systemd-resolve
[Touch-packages] [Bug 1705813] [NEW] systemd upgrade to 229-4ubuntu19 fails
Public bug reported: systemd upgrade to 229-4ubuntu19 fails: Calculating upgrade... Done The following packages will be upgraded: libmysqlclient20 libnss-myhostname libpam-systemd libsystemd0 libudev1 mysql-client-5.7 mysql-client-core-5.7 mysql-common mysql-server mysql-server-5.7 mysql-server-core-5.7 systemd systemd-sysv udev 14 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 23.8 MB of archives. After this operation, 106 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 systemd-sysv amd64 229-4ubuntu19 [12.4 kB] Get:2 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 libpam-systemd amd64 229-4ubuntu19 [115 kB] Get:3 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 libsystemd0 amd64 229-4ubuntu19 [205 kB] Get:4 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 libnss-myhostname amd64 229-4ubuntu19 [36.4 kB] Get:5 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 systemd amd64 229-4ubuntu19 [3,811 kB] Get:6 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 udev amd64 229-4ubuntu19 [992 kB] Get:7 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 libudev1 amd64 229-4ubuntu19 [55.0 kB] Get:8 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 mysql-client-core-5.7 amd64 5.7.19-0ubuntu0.16.04.1 [6,020 kB] Get:9 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 mysql-common all 5.7.19-0ubuntu0.16.04.1 [15.7 kB] Get:10 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 mysql-client-5.7 amd64 5.7.19-0ubuntu0.16.04.1 [1,654 kB] Get:11 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 mysql-server-5.7 amd64 5.7.19-0ubuntu0.16.04.1 [2,463 kB] Get:12 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 mysql-server-core-5.7 amd64 5.7.19-0ubuntu0.16.04.1 [7,588 kB] Get:13 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 libmysqlclient20 amd64 5.7.19-0ubuntu0.16.04.1 [809 kB] Get:14 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 mysql-server all 5.7.19-0ubuntu0.16.04.1 [10.8 kB] Fetched 23.8 MB in 0s (32.4 MB/s) Preconfiguring packages ... (Reading database ... 112119 files and directories currently installed.) Preparing to unpack .../systemd-sysv_229-4ubuntu19_amd64.deb ... Unpacking systemd-sysv (229-4ubuntu19) over (229-4ubuntu17) ... Processing triggers for man-db (2.7.5-1) ... Setting up systemd-sysv (229-4ubuntu19) ... (Reading database ... 112119 files and directories currently installed.) Preparing to unpack .../libpam-systemd_229-4ubuntu19_amd64.deb ... Unpacking libpam-systemd:amd64 (229-4ubuntu19) over (229-4ubuntu17) ... Preparing to unpack .../libsystemd0_229-4ubuntu19_amd64.deb ... Unpacking libsystemd0:amd64 (229-4ubuntu19) over (229-4ubuntu17) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for libc-bin (2.23-0ubuntu9) ... Setting up libsystemd0:amd64 (229-4ubuntu19) ... Processing triggers for libc-bin (2.23-0ubuntu9) ... (Reading database ... 112119 files and directories currently installed.) Preparing to unpack .../libnss-myhostname_229-4ubuntu19_amd64.deb ... Unpacking libnss-myhostname:amd64 (229-4ubuntu19) over (229-4ubuntu17) ... Preparing to unpack .../systemd_229-4ubuntu19_amd64.deb ... Unpacking systemd (229-4ubuntu19) over (229-4ubuntu17) ... Processing triggers for libc-bin (2.23-0ubuntu9) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for dbus (1.10.6-1ubuntu3.3) ... Processing triggers for ureadahead (0.100.0-19) ... Setting up systemd (229-4ubuntu19) ... addgroup: The group `systemd-journal' already exists as a system group. Exiting. Broadcast message from systemd-journ...@web01.fra.de.nohn.net (Sat 2017-07-22 09:07:52 UTC): systemd[1]: Freezing execution. Failed to try-restart systemd-networkd.service: Failed to activate service 'org.freedesktop.systemd1': timed out See system logs and 'systemctl status systemd-networkd.service' for details. Failed to try-restart systemd-resolved.service: Failed to activate service 'org.freedesktop.systemd1': timed out See system logs and 'systemctl status systemd-resolved.service' for details. Failed to try-restart systemd-timesyncd.service: Failed to activate service 'org.freedesktop.systemd1': timed out See system logs and 'systemctl status systemd-timesyncd.service' for details. Failed to retrieve unit: Failed to activate service 'org.freedesktop.systemd1': timed out (Reading database ... 112121 files and directories currently installed.) Preparing to unpack .../udev_229-4ubuntu19_amd64.deb ... Unpacking udev (229-4ubuntu19) over (229-4ubuntu17) ... Failed to execute operation: Failed to activate service 'org.freedesktop.systemd1': timed out Preparing to unpack .../libudev1_229-4ubuntu19_amd64.deb ... Unpacking libudev1:amd64 (229-4ubuntu19) over (229-4ubuntu17) ..
[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space
dpkg -l linux-{image,headers}-* | awk '/^ii/{print $2}' | egrep
'[0-9]+\.[0-9]+\.[0-9]+' | grep -v $(uname -r | cut -d- -f-2) | xargs
sudo apt-get -y purge
--
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/798414
Title:
update-initramfs should produce a more helpful error message when
there isn't enough free space
Status in initramfs-tools:
Confirmed
Status in Software Updater:
New
Status in dpkg package in Ubuntu:
Invalid
Status in initramfs-tools package in Ubuntu:
In Progress
Bug description:
Binary package hint: initramfs-tools
When installing a kernel, /boot may become full during execution of
post-installation script typically when update-initramfs is creating
or updating an initrd.img file. This is resulting in kernel
installation error. For example:
Setting up initramfs-tools (0.98.8ubuntu3) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic
gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
dpkg: error processing initramfs-tools (--configure):
subprocess installed post-installation script returned error exit status 1
Ideal behavior:
Give a more helpful error message when this unfortunate situation
occurs so that user can fix the broken system and keep it going.
Workaround:
As the bug reporting system forwards user to this bug report, such
instructions can be given here:
https://help.ubuntu.com/community/RemoveOldKernels
To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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 1626987] Re: openssl update may have broken puppet cert sign
See #1626883 ** Changed in: openssl (Ubuntu) Status: Confirmed => Fix Released ** Changed in: puppet (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1626987 Title: openssl update may have broken puppet cert sign Status in openssl package in Ubuntu: Fix Released Status in puppet package in Ubuntu: Invalid Bug description: After tonight's openssl update on our puppet CA server, we can no longer sign puppet certificates: root@sistemes:~# puppet cert sign vm-host-14.ac.upc.es Notice: Signed certificate request for vm-host-14.ac.upc.es Error: root@sistemes:~# puppet ca sign vm-host-14.ac.upc.es Notice: Signed certificate request for vm-host-14.ac.upc.es Error: Error: Try 'puppet help ca sign' for usage AFAICT, no other changes on the puppet CA have been performed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: openssl 1.0.1f-1ubuntu2.20 ProcVersionSignature: Ubuntu 3.13.0-96.143-generic 3.13.11-ckt39 Uname: Linux 3.13.0-96-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Fri Sep 23 13:41:12 2016 InstallationDate: Installed on 2010-05-25 (2313 days ago) InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openssl UpgradeStatus: Upgraded to trusty on 2015-02-05 (596 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1626987/+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 1626987] Re: openssl update may have broken puppet cert sign
** Changed in: openssl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1626987 Title: openssl update may have broken puppet cert sign Status in openssl package in Ubuntu: Confirmed Status in puppet package in Ubuntu: New Bug description: After tonight's openssl update on our puppet CA server, we can no longer sign puppet certificates: root@sistemes:~# puppet cert sign vm-host-14.ac.upc.es Notice: Signed certificate request for vm-host-14.ac.upc.es Error: root@sistemes:~# puppet ca sign vm-host-14.ac.upc.es Notice: Signed certificate request for vm-host-14.ac.upc.es Error: Error: Try 'puppet help ca sign' for usage AFAICT, no other changes on the puppet CA have been performed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: openssl 1.0.1f-1ubuntu2.20 ProcVersionSignature: Ubuntu 3.13.0-96.143-generic 3.13.11-ckt39 Uname: Linux 3.13.0-96-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Fri Sep 23 13:41:12 2016 InstallationDate: Installed on 2010-05-25 (2313 days ago) InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openssl UpgradeStatus: Upgraded to trusty on 2015-02-05 (596 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1626987/+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 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
Interpolating the number of bugs to the number of users affected, looking into Google searches for users looking for help solving the problems caused by this, my guess is these are amongst the most annoying open bugs in Ubuntu out there. Is there any chance that any of these bugs will be fixed in the current LTS releases? -- 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/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space Status in initramfs-tools: Confirmed Status in initramfs-tools package in Ubuntu: Triaged Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 WORKAROUND: Remove unused kernels using computer janitor (not in repositories for 14.04 or later) or manually free space on your partition containing the /boot file system. To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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 1054927] Re: Autoupdater fills /boot and crashes because old kernel images are never removed
Jarno Suni, OK. Too bad. My interpretation was, this is also fixed in 14.04. For some reason I don't know more header packages were installed than image packages. My guess is this is because of some incomplete manual kernel removal, I executed in the past. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1054927 Title: Autoupdater fills /boot and crashes because old kernel images are never removed Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-manager package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) Install Ubuntu with the default LVM encryption recipe 2) Set Ubuntu to automatically install security updates on the background 3) Use ubuntu for 5 months Actual results: The system automatically installs security updates for the kernel under /boot. It's never removes previous kernel images. After about five months, the /boot partition created by the install recipe (i.e. sized according to the judgment of Ubuntu developers—not me) fills up and the unattended updater crashes during the next kernel update. Expected results: Expected the unattended updater to leave the nearest kernel and the previous one on /boot and to automatically remove older kernel images. Expected the system installer to set up /boot such that it never runs out of space when the system updater operates automatically. For workaround and sytem repair, see https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.9 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Sun Sep 23 12:53:52 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1054927/+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 1054927] Re: Autoupdater fills /boot and crashes because old kernel images are never removed
$ sudo apt-get remove --purge linux-headers-3.16.0-57 linux-headers-3.16.0-57-generic linux-headers-3.16.0-59 linux-headers-3.16.0-59-generic linux-headers-3.16.0-60 linux-headers-3.16.0-60-generic linux-headers-3.16.0-62 linux-headers-3.16.0-62-generic linux-image-3.16.0-62-generic linux-image-extra-3.16.0-62-generic linux-signed-image-3.16.0-62-generic [sudo] password for sebastian: Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED linux-headers-3.16.0-57* linux-headers-3.16.0-57-generic* linux-headers-3.16.0-59* linux-headers-3.16.0-59-generic* linux-headers-3.16.0-60* linux-headers-3.16.0-60-generic* linux-headers-3.16.0-62* linux-headers-3.16.0-62-generic* linux-image-3.16.0-62-generic* linux-image-extra-3.16.0-62-generic* linux-signed-image-3.16.0-62-generic* 0 to upgrade, 0 to newly install, 11 to remove and 9 not to upgrade. After this operation, 515 MB disk space will be freed. Do you want to continue? [Y/n] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1054927 Title: Autoupdater fills /boot and crashes because old kernel images are never removed Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-manager package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) Install Ubuntu with the default LVM encryption recipe 2) Set Ubuntu to automatically install security updates on the background 3) Use ubuntu for 5 months Actual results: The system automatically installs security updates for the kernel under /boot. It's never removes previous kernel images. After about five months, the /boot partition created by the install recipe (i.e. sized according to the judgment of Ubuntu developers—not me) fills up and the unattended updater crashes during the next kernel update. Expected results: Expected the unattended updater to leave the nearest kernel and the previous one on /boot and to automatically remove older kernel images. Expected the system installer to set up /boot such that it never runs out of space when the system updater operates automatically. For workaround and sytem repair, see https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.9 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Sun Sep 23 12:53:52 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1054927/+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 1054927] Re: Autoupdater fills /boot and crashes because old kernel images are never removed
Fix seems not released. My disk is again cluttered with old kernels. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1054927 Title: Autoupdater fills /boot and crashes because old kernel images are never removed Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-manager package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) Install Ubuntu with the default LVM encryption recipe 2) Set Ubuntu to automatically install security updates on the background 3) Use ubuntu for 5 months Actual results: The system automatically installs security updates for the kernel under /boot. It's never removes previous kernel images. After about five months, the /boot partition created by the install recipe (i.e. sized according to the judgment of Ubuntu developers—not me) fills up and the unattended updater crashes during the next kernel update. Expected results: Expected the unattended updater to leave the nearest kernel and the previous one on /boot and to automatically remove older kernel images. Expected the system installer to set up /boot such that it never runs out of space when the system updater operates automatically. For workaround and sytem repair, see https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.9 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Sun Sep 23 12:53:52 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1054927/+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 1559924] Re: rsyslog shuts down too early, preventing logging of the other jobs shutting down
Sorry, I thought, systemd was default in Ubuntu 14.04, but it seems, upstart is still taking care of most init related things in Ubuntu 14.04. ** Description changed: - systemd kills rsyslog as one of the first jobs. So after that no other + upstart kills rsyslog as one of the first jobs. So after that no other jobs are logging that they are shutting down and what they are doing during shutdown. The default should be shutting down logging at the latest possible point in time when shutting down a machine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1559924 Title: rsyslog shuts down too early, preventing logging of the other jobs shutting down Status in rsyslog package in Ubuntu: Triaged Bug description: upstart kills rsyslog as one of the first jobs. So after that no other jobs are logging that they are shutting down and what they are doing during shutdown. The default should be shutting down logging at the latest possible point in time when shutting down a machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1559924/+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 1559924] [NEW] systemd kills rsyslog as one of the first jobs, preventing logging of the other jobs shutting down
Public bug reported: systemd kills rsyslog as one of the first jobs. So after that no other jobs are logging that they are shutting down and what they are doing during shutdown. The default should be shutting down logging at the latest possible point in time when shutting down a machine. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1559924 Title: systemd kills rsyslog as one of the first jobs, preventing logging of the other jobs shutting down Status in systemd package in Ubuntu: New Bug description: systemd kills rsyslog as one of the first jobs. So after that no other jobs are logging that they are shutting down and what they are doing during shutdown. The default should be shutting down logging at the latest possible point in time when shutting down a machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1559924/+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 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full
Will the fix, that has been merged in the meantime make it into 14.04 LTS or do we have to wait for some future Ubuntu release? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full Status in unattended-upgrades package in Ubuntu: In Progress Bug description: Currently if one chooses to use LVM or encrypted install, a /boot partition is created of 236Mb Once kernel updates start being released this partition soon fills until people are left unable to upgrade. While you and I might know that we need to watch partition space, many of the people we have installing think that a windows disk is a disk and not a partition, education is probably the key - but in the meantime support venues keep needing to deal with the fact the partition is too small and/or old kernels are not purged as new ones install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+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 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted install
Change summary, because /boot is always to small on "LVM or Encrypted install". The former summary read like it was a user error, while it isn't. ** Summary changed: - Kernels not autoremoving, causing out of space error on LVM or Encrypted install with small /boot partition + Kernels not autoremoving, causing out of space error on LVM or Encrypted install -- 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/1357093 Title: Kernels not autoremoving, causing out of space error on LVM or Encrypted install Status in apt package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: Currently if one chooses to use LVM or encrypted install, a /boot partition is created of 236Mb Once kernel updates start being released this partition soon fills until people are left unable to upgrade. While you and I might know that we need to watch partition space, many of the people we have installing think that a windows disk is a disk and not a partition, education is probably the key - but in the meantime support venues keep needing to deal with the fact the partition is too small and/or old kernels are not purged as new ones install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1357093/+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 1388353] Re: package initramfs-tools 0.103ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
I convert this back to a bug. If you install Ubuntu 14.04 with encrypted disks, /boot is only 236M big. This is barely enough to keep 4 kernel versions. So either increase the default size of /boot so it can hold the number of old kernels, Ubuntu keeps by default or lower the number of old kernels, Ubuntu keeps by default to 2-3. ** Changed in: initramfs-tools (Ubuntu) Status: Invalid => Confirmed -- 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/1388353 Title: package initramfs-tools 0.103ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: I just was updating package's package initramfs-tools 0.103ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: initramfs-tools 0.103ubuntu4.2 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Sat Nov 1 13:19:01 2014 DuplicateSignature: package:initramfs-tools:0.103ubuntu4.2:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-07-17 (106 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140715) PackageArchitecture: all SourcePackage: initramfs-tools SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown Title: package initramfs-tools 0.103ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1388353/+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 1388353] Re: package initramfs-tools 0.103ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
/boot is just too small by default for the number of kernels kept if you are setting up Ubuntu 14.04 with encrypted disks. -- 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/1388353 Title: package initramfs-tools 0.103ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: I just was updating package's package initramfs-tools 0.103ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: initramfs-tools 0.103ubuntu4.2 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Sat Nov 1 13:19:01 2014 DuplicateSignature: package:initramfs-tools:0.103ubuntu4.2:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-07-17 (106 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140715) PackageArchitecture: all SourcePackage: initramfs-tools SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown Title: package initramfs-tools 0.103ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1388353/+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
