[Touch-packages] [Bug 1892559] Re: [MIR] ccid opensc pcsc-lite
** Changed in: ccid (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => Ray Veldkamp (rayveldkamp) ** Changed in: ccid (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1892559 Title: [MIR] ccid opensc pcsc-lite Status in ccid package in Ubuntu: In Progress Status in opensc package in Ubuntu: Incomplete Status in pam-pkcs11 package in Ubuntu: Invalid Status in pcsc-lite package in Ubuntu: New Status in pcsc-perl package in Ubuntu: Invalid Status in pcsc-tools package in Ubuntu: Invalid Bug description: ==> ccid <== [Availability] ccid is in universe, and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs for ccid are listed in our database. Doesn't appear to bind to a socket. No privileged executables, but does have udev rules. Probably needs a security review. [Quality assurance] No test suite. Does require odd hardware that we'll probably need to buy. I don't see debconf questions. ccid is well maintained in Debian by upstream author. One open wishlist bug in BTS, harmless. One open bug in launchpad, not security, but looks very frustrating for the users. The upstream author was engaged but it never reached resolution. https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465 Has a debian/watch file. Quilt packaging. P: ccid source: no-dep5-copyright P: ccid source: package-uses-experimental-debhelper-compat-version 13 [Dependencies] Minimal dependencies, in main [Standards compliance] Appears to satisfy FHS and Debian policy [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] ccid provides drivers to interact with usb-connected smart card readers. ==> libpam-pkcs11 <== [Availability] Source package pam-pkcs11 is in universe and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs in our database. Doesn't appear to bind to sockets. No privileged executables (but is a PAM module). As a PAM module this will require a security review. [Quality assurance] The package does not call pam-auth-update in its postinst #1650366 Does not ask questions during install. One Ubuntu bug claims very poor behaviour if a card isn't plugged in. No Debian bugs. Occasional updates in Debian by long-term maintainer. Does require odd hardware that we'll probably need to buy. Does not appear to run tests during build. Has scary warnings in the build logs. Has a debian/watch file. Ancient standards version; other smaller lintian messages, mostly documentation problems. Quilt packaging. [Dependencies] Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1 All are in main. [Standards compliance] The package does not call pam-auth-update in its postinst #1650366 Otherwise looks to conform to FHS and Debian policies [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] This PAM module can use CRLs and full-chain verification of certificates. It can also do LDAP, AD, and Kerberos username mapping. ==> libpcsc-perl <== [Availability] Source package pcsc-perl is in universe, builds for all architectures, plus i386 [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] There are no cves for pcsc-perl in our database. No privileged executables. Doesn't appear to bind to sockets. Probably needs a security review. [Quality assurance] Library package not intended to be used directly. No debconf questions. No bugs in Debian. No bugs in Ubuntu. Does require odd hardware that we'll probably need to buy. Tests exist, not run during the build; probably can't run during the build. Includes debian/watch file. A handful of lintian issues Quilt packaging. [Dependencies] libpcsc-perl depends upon libpcsclite1, libc6, perl, perlapi-5.30.0. All are in main. [Standards compliance] One oddity, Card.pod is stored in /usr/lib/x86_64-linux-gnu/perl5/5.30/Chipcard/PCSC/ Many other perl packages have .pod files in these directory trees so maybe it's fine, but it seems funny all the same. Otherwise appears to satisfy FHS and Debian policy. [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team
[Touch-packages] [Bug 1912950] Re: rsync halts with Permission denied (13) with a sticky dir and only recent kernels
[Expired for rsync (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rsync (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1912950 Title: rsync halts with Permission denied (13) with a sticky dir and only recent kernels Status in rsync package in Ubuntu: Expired Bug description: Looks like rsync should be adapted to a new policy of the Linux kernel. I found a report in the ZFS Github that looks a lot like my problem : https://github.com/openzfs/zfs/issues/10742 But on that page, the suggested solution using /proc/sys/fs/protected_regular doesn't seem to be ideal and instead rsync should be able to figure it out by itself so that users aren't encouraged to keep that security measure turned off (perhaps my idea is bad, but pros and cons have to be figured out). I'm regularly backing up a remote folder on a machine that has a different user list and that folder has sticky bit set, while being root on both sides. I had no error using Ubuntu 18.04 : it started failing just after upgrading to 20.04. If I try to rsync individual files of that folder, I get error 13 in most cases, but if I chmod -t on that folder, I can rsync them, but if I try rsyncing the folder again (by recursion), rsync does chmod +t on it before rsyncing individual files in the folder, and then it fails again. And of course, to work around the problem, rsync would probably have to catch error 13 and retry after doing chmod -t temporarily on the folder, then schedule a chmod +t after this folder is finished syncing, or at cleanup time (Ctrl+c or SIGTERM). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1912950/+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 1958311] Re: Show all Ubuntu Advantage services
Currently available for testing in https://launchpad.net/~robert- ancell/+archive/ubuntu/ubuntu-pro -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1958311 Title: Show all Ubuntu Advantage services Status in software-properties package in Ubuntu: In Progress Status in software-properties source package in Bionic: In Progress Status in software-properties source package in Focal: In Progress Status in software-properties source package in Jammy: In Progress Bug description: Replace the Livepatch page with an "Ubuntu Pro" page that shows full status and control of Ubuntu Advantage services. This gives graphical control of features that the 'ua' command line tool provides. [Test Plan] 1. Open software-properties 2. Go to Ubuntu Pro page. 3. Check able to attach and detach this machine from an Ubuntu Advantage subscription. Check status matches what the 'ua' command line tool shows. Check graphical attachment status updates when performed from the command line. 4. Check able to enable/disable services. Check graphical service status updates when performed from the command line. [Where problems could occur] This is a major structural change in how Livepatch is enabled, and thus could break this existing feature (however this also removes a lot of the work currently performed to enable Livepatch and leaves that to the 'ua' tool). The new features could introduce new bugs, such as causing software-properties to crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1958311/+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 1958311] Re: Show all Ubuntu Advantage services
Blocked on ubuntu-advantage-desktop-daemon MIR (LP: #1954909) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1958311 Title: Show all Ubuntu Advantage services Status in software-properties package in Ubuntu: In Progress Status in software-properties source package in Bionic: In Progress Status in software-properties source package in Focal: In Progress Status in software-properties source package in Jammy: In Progress Bug description: Replace the Livepatch page with an "Ubuntu Pro" page that shows full status and control of Ubuntu Advantage services. This gives graphical control of features that the 'ua' command line tool provides. [Test Plan] 1. Open software-properties 2. Go to Ubuntu Pro page. 3. Check able to attach and detach this machine from an Ubuntu Advantage subscription. Check status matches what the 'ua' command line tool shows. Check graphical attachment status updates when performed from the command line. 4. Check able to enable/disable services. Check graphical service status updates when performed from the command line. [Where problems could occur] This is a major structural change in how Livepatch is enabled, and thus could break this existing feature (however this also removes a lot of the work currently performed to enable Livepatch and leaves that to the 'ua' tool). The new features could introduce new bugs, such as causing software-properties to crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1958311/+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 1958311] Re: Show all Ubuntu Advantage services
** Changed in: software-properties (Ubuntu Bionic) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: software-properties (Ubuntu Focal) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: software-properties (Ubuntu Jammy) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: software-properties (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: software-properties (Ubuntu Focal) Importance: Undecided => High ** Changed in: software-properties (Ubuntu Bionic) Importance: Medium => High ** Changed in: software-properties (Ubuntu Jammy) Importance: Undecided => High ** Changed in: software-properties (Ubuntu Bionic) Status: New => Triaged ** Changed in: software-properties (Ubuntu Focal) Status: New => In Progress ** Changed in: software-properties (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: software-properties (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1958311 Title: Show all Ubuntu Advantage services Status in software-properties package in Ubuntu: In Progress Status in software-properties source package in Bionic: In Progress Status in software-properties source package in Focal: In Progress Status in software-properties source package in Jammy: In Progress Bug description: Replace the Livepatch page with an "Ubuntu Pro" page that shows full status and control of Ubuntu Advantage services. This gives graphical control of features that the 'ua' command line tool provides. [Test Plan] 1. Open software-properties 2. Go to Ubuntu Pro page. 3. Check able to attach and detach this machine from an Ubuntu Advantage subscription. Check status matches what the 'ua' command line tool shows. Check graphical attachment status updates when performed from the command line. 4. Check able to enable/disable services. Check graphical service status updates when performed from the command line. [Where problems could occur] This is a major structural change in how Livepatch is enabled, and thus could break this existing feature (however this also removes a lot of the work currently performed to enable Livepatch and leaves that to the 'ua' tool). The new features could introduce new bugs, such as causing software-properties to crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1958311/+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 1927192] Re: gdb ftbfs on armhf, testsuite timeouts
This bug was fixed in the package gdb - 9.2-0ubuntu1~20.04.1 --- gdb (9.2-0ubuntu1~20.04.1) focal; urgency=medium * Re-enable running the tests on armhf, build-depend / depend on libc6-dbg on armhf. (LP: #1927192) -- Brian Murray Tue, 07 Dec 2021 15:49:12 -0800 ** Changed in: gdb (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1927192 Title: gdb ftbfs on armhf, testsuite timeouts Status in gdb: Incomplete Status in gdb package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Fix Released Status in gdb source package in Focal: Fix Released Status in glibc source package in Focal: Fix Committed Status in gdb source package in Groovy: Won't Fix Status in glibc source package in Groovy: Won't Fix Status in gdb source package in Hirsute: Won't Fix Status in glibc source package in Hirsute: Won't Fix Status in gdb source package in Impish: Fix Released Status in glibc source package in Impish: Fix Released Bug description: [Impact] * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is not installed. [Test Plan] * Check that ld.so is not stripped on armhf: $ /lib/*/ld-2.31.so libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not stripped * Check that ld.so is stripped on amd64: $ file /lib/x86_64-linux-gnu/ld-2.31.so /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped [Where problems could occur] * The fix is not stripping ld.so on armhf. Not stripping it comes with a notable increase in file size and it may be performance critical 109K stripped vs 1.3M unstripped. Accidentally ld.so could be left unstripped on other architectures, but the test plan covers checking that, at least on amd64. Other than those not stripping ld.so should not cause any issue. [Original Bug Text] see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1927192/+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 1927192] Update Released
The verification of the Stable Release Update for gdb has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1927192 Title: gdb ftbfs on armhf, testsuite timeouts Status in gdb: Incomplete Status in gdb package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Fix Released Status in gdb source package in Focal: Fix Released Status in glibc source package in Focal: Fix Committed Status in gdb source package in Groovy: Won't Fix Status in glibc source package in Groovy: Won't Fix Status in gdb source package in Hirsute: Won't Fix Status in glibc source package in Hirsute: Won't Fix Status in gdb source package in Impish: Fix Released Status in glibc source package in Impish: Fix Released Bug description: [Impact] * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is not installed. [Test Plan] * Check that ld.so is not stripped on armhf: $ /lib/*/ld-2.31.so libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not stripped * Check that ld.so is stripped on amd64: $ file /lib/x86_64-linux-gnu/ld-2.31.so /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped [Where problems could occur] * The fix is not stripping ld.so on armhf. Not stripping it comes with a notable increase in file size and it may be performance critical 109K stripped vs 1.3M unstripped. Accidentally ld.so could be left unstripped on other architectures, but the test plan covers checking that, at least on amd64. Other than those not stripping ld.so should not cause any issue. [Original Bug Text] see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1927192/+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 1958311] [NEW] Show all Ubuntu Advantage services
Public bug reported: Replace the Livepatch page with an "Ubuntu Pro" page that shows full status and control of Ubuntu Advantage services. This gives graphical control of features that the 'ua' command line tool provides. [Test Plan] 1. Open software-properties 2. Go to Ubuntu Pro page. 3. Check able to attach and detach this machine from an Ubuntu Advantage subscription. Check status matches what the 'ua' command line tool shows. Check graphical attachment status updates when performed from the command line. 4. Check able to enable/disable services. Check graphical service status updates when performed from the command line. [Where problems could occur] This is a major structural change in how Livepatch is enabled, and thus could break this existing feature (however this also removes a lot of the work currently performed to enable Livepatch and leaves that to the 'ua' tool). The new features could introduce new bugs, such as causing software-properties to crash. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Focal) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1958311 Title: Show all Ubuntu Advantage services Status in software-properties package in Ubuntu: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Status in software-properties source package in Jammy: New Bug description: Replace the Livepatch page with an "Ubuntu Pro" page that shows full status and control of Ubuntu Advantage services. This gives graphical control of features that the 'ua' command line tool provides. [Test Plan] 1. Open software-properties 2. Go to Ubuntu Pro page. 3. Check able to attach and detach this machine from an Ubuntu Advantage subscription. Check status matches what the 'ua' command line tool shows. Check graphical attachment status updates when performed from the command line. 4. Check able to enable/disable services. Check graphical service status updates when performed from the command line. [Where problems could occur] This is a major structural change in how Livepatch is enabled, and thus could break this existing feature (however this also removes a lot of the work currently performed to enable Livepatch and leaves that to the 'ua' tool). The new features could introduce new bugs, such as causing software-properties to crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1958311/+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 1586528] Re: Avahi-daemon withdraws address record
I've just seen this issue the first time on a Ubuntu 20.04 (updated several months ago from 16.04) AWS EC2 machine. Looking closer into this, the machine lost its IP address multiple times in the last hours. The following avahi-daemon log messages made me find this bug report: ck@focal:~$ grep avahi-daemon /var/log/syslog | grep -i withdrawing Jan 18 20:17:42 inf-mon04-p avahi-daemon[941]: Withdrawing address record for 10.10.1.41 on eth0. Jan 18 21:44:52 inf-mon04-p avahi-daemon[941]: Withdrawing address record for 10.10.1.41 on eth0. It's very interesting, that both of these events happened EXACTLY one hour after the system boot: ck@focal:~$ last | head ck pts/0xx.xx.xx.xxx Tue Jan 18 22:11 still logged in root ttyS0 Tue Jan 18 21:50 still logged in reboot system boot 5.4.0-91-generic Tue Jan 18 20:44 still running reboot system boot 5.4.0-91-generic Tue Jan 18 19:17 - 20:39 (01:22) Running "dhclient" on the EC2 console, as suggested in comment #46, re- assigns the IP address. Relevant versions installed: ck@focal:~$ dpkg -l|egrep "(dhcp|network-manager)" ii isc-dhcp-client 4.4.1-2.1ubuntu5.20.04.2 amd64DHCP client for automatically obtaining an IP address ii isc-dhcp-common 4.4.1-2.1ubuntu5.20.04.2 amd64common manpages relevant to all of the isc-dhcp packages ii network-manager 1.22.10-1ubuntu2.2 amd64network management framework (daemon and userspace tools) ii network-manager-gnome1.8.24-1ubuntu3 amd64network management framework (GNOME frontend) ii network-manager-pptp 1.2.8-2 amd64network management framework (PPTP plugin core) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1586528 Title: Avahi-daemon withdraws address record Status in avahi package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Bug description: For some reason, if I leave my Ubuntu VM up for a prolonged period of time the machine will lose connection to the network. ip addr shows that the nic port no longer has an address and an examination of the syslog shows this: May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record for 10.0.2.15 on enp0s3. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast group on interface enp0s3.IPv4 with address 10.0.2.15. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no longer relevant for mDNS. for no known reason. The only reliable way to get the network to come back (that I have found) is a full reboot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 27 15:11:34 2016 InstallationDate: Installed on 2015-10-22 (218 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: avahi UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+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 1817946] Re: package linux-image-4.15.0-45-generic 4.15.0-45.48 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to update a package on your system due to a lack of free space on your system. Please resolve this situation manually and try the update again. ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Tags added: no-free-space -- 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/1817946 Title: package linux-image-4.15.0-45-generic 4.15.0-45.48 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: package linus-image-4.15.0-45-generic 4.15.0-45.48 failed to install/upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-45-generic 4.15.0-45.48 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1176 F pulseaudio namirasalm 1548 F pulseaudio /dev/snd/controlC0: gdm1176 F pulseaudio namirasalm 1548 F pulseaudio Date: Tue Feb 26 00:16:03 2019 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=49e290fc-e6be-4c95-9a10-3f1c79417eab InstallationDate: Installed on 2018-10-23 (127 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80XU ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=54d2d971-1eed-45d6-a46f-e5ba244f02ea ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8.6 SourcePackage: initramfs-tools Title: package linux-image-4.15.0-45-generic 4.15.0-45.48 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5PCN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55731WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-14AST dmi.modalias: dmi:bvnLENOVO:bvr5PCN24WW:bd10/29/2018:svnLENOVO:pn80XU:pvrLenovoideapad320-14AST:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55731WIN:cvnLENOVO:ct10:cvrLenovoideapad320-14AST: dmi.product.family: ideapad 320-14AST dmi.product.name: 80XU dmi.product.version: Lenovo ideapad 320-14AST dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1817946/+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 1858631] Re: package linux-image-extra-4.4.0-92-generic 4.4.0-92.115 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to update the kernel on your system due to a lack of free space in your boot partition. Please resolve this situation manually and try the update again. ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Tags added: no-boot-space -- 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/1858631 Title: package linux-image-extra-4.4.0-92-generic 4.4.0-92.115 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: cannot boot after upgrade now using previous kernel (4.4.0-91) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-92-generic 4.4.0-92.115 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 Uname: Linux 4.4.0-91-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erbe01 1836 F pulseaudio gdm2094 F pulseaudio /dev/snd/controlC1: erbe01 1836 F pulseaudio gdm2094 F pulseaudio Date: Tue Jan 7 15:09:54 2020 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=/dev/mapper/EC--WEB01--vg-swap_1 MachineType: Dell Inc. Vostro 3650 ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-91-generic root=/dev/mapper/EC--WEB01--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.23 SourcePackage: initramfs-tools Title: package linux-image-extra-4.4.0-92-generic 4.4.0-92.115 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.2.4 dmi.board.name: 0VGHXY dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr3.2.4:bd06/17/2016:svnDellInc.:pnVostro3650:pvrX00:rvnDellInc.:rn0VGHXY:rvrA01:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.name: Vostro 3650 dmi.product.version: X00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1858631/+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 1948575] Re: package linux-firmware 1.187.19 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to update a package on your system due to a lack of free space on your system. Please resolve this situation manually and try the update again. ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Tags added: no-free-space -- 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/1948575 Title: package linux-firmware 1.187.19 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: verly long and old maintained authentication keys in trusted software repository of ubuntu software updater. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.19 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: arun 1871 F pulseaudio CasperMD5CheckResult: skip Date: Sun Oct 24 15:12:21 2021 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-09-08 (46 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 80T7 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-34-generic root=UUID=99f31926-b2b0-4b03-a8ba-a15f3b4a9fcd ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 SourcePackage: initramfs-tools Title: package linux-firmware 1.187.19 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.release: 1.15 dmi.bios.vendor: LENOVO dmi.bios.version: 1GCN15WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: 00RD15IPG076 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15IBR dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvr1GCN15WW:bd04/07/2016:br1.15:efr1.15:svnLENOVO:pn80T7:pvrLenovoideapad110-15IBR:skuLENOVO_MT_80T7_BU_idea_FM_Lenovoideapad110-15IBR:rvnLENOVO:rn00RD15IPG076:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad110-15IBR: dmi.product.family: IDEAPAD dmi.product.name: 80T7 dmi.product.sku: LENOVO_MT_80T7_BU_idea_FM_Lenovo ideapad 110-15IBR dmi.product.version: Lenovo ideapad 110-15IBR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1948575/+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 1879449] Re: package linux-image-5.4.0-31-generic 5.4.0-31.35 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
I wonder if our installation process is creating /boot partitions that are too small for kernel upgrades. Could you provide some information about how you installed Ubuntu? Did you use the desktop or server installer? Did you use the guided installation process or something else? Thanks in advance! ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Incomplete -- 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/1879449 Title: package linux-image-5.4.0-31-generic 5.4.0-31.35 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Incomplete Bug description: I got a warning message that partition /boot does not have enough disk space while I was updating the system using apt update / apt upgrade. Then the update failed and I got an error message as shown in the attached screenshot. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ahmedelhosseiny 2397 F pulseaudio CRDA: global country EG: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 40), (N/A, 20), (N/A) (5250 - 5330 @ 40), (N/A, 20), (0 ms), DFS CasperMD5CheckResult: skip Date: Tue May 19 09:08:03 2020 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-04-27 (21 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Latitude E5570 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=59a72f08-8b23-4827-a49c-b82fb036be27 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. 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: grub-pc 2.04-1ubuntu26 SourcePackage: initramfs-tools Title: package linux-image-5.4.0-31-generic 5.4.0-31.35 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.6 dmi.board.name: 0GF89W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.6:bd02/07/2017:svnDellInc.:pnLatitudeE5570:pvr:rvnDellInc.:rn0GF89W:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E5570 dmi.product.sku: 06DF dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879449/+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 1898482] Re: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Could you please run 'apport-collect 1898482' in a terminal? This will gather log files related to your upgrade which will be helpful in determining what went wrong. ** Package changed: initramfs-tools (Ubuntu) => ubuntu-release-upgrader (Ubuntu) ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Incomplete -- 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/1898482 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 ubuntu-release-upgrader package in Ubuntu: Incomplete Bug description: do-release-upgrade said it would need 1.5G free diskspace, used 1.7G and the disk was then full. 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: Sun Oct 4 20:45:27 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 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-10-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898482/+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 1938056] Re: failed on install from USB boot install media
Updating the kernel on a live media isn't supported. ** Changed in: initramfs-tools (Ubuntu) Status: New => 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/1938056 Title: failed on install from USB boot install media Status in initramfs-tools package in Ubuntu: Invalid Bug description: error message after install ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jul 26 08:23:41 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess 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/1938056/+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 1942119] Re: package linux-image-5.11.0-33-generic 5.11.0-33.35 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
I'm curious about how you installed Ubuntu as there may be an issue with the installation process creating too small of a /boot partition. What version of Ubuntu did you first install and how did you setup the partition of your disk? Did you allow the installer to set it up? Thanks in advance. ** Changed in: initramfs-tools (Ubuntu) Status: New => Incomplete -- 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/1942119 Title: package linux-image-5.11.0-33-generic 5.11.0-33.35 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Incomplete Bug description: out of space on boot ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-33-generic 5.11.0-33.35 ProcVersionSignature: Ubuntu 5.11.0-26.28-generic 5.11.22 Uname: Linux 5.11.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 AptOrdering: linux-image-5.11.0-34-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ed 3762 F pulseaudio /dev/snd/controlC0: ed 3762 F pulseaudio CasperMD5CheckResult: unknown Date: Mon Aug 30 12:49:06 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=d2593ab0-191d-4408-97ee-05d6ed8ca557 InstallationDate: Installed on 2018-06-24 (1163 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: lono wireless extensions. eth0 no wireless extensions. virbr0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-26-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: initramfs-tools Title: package linux-image-5.11.0-33-generic 5.11.0-33.35 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.00 dmi.board.name: AB350 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.00:bd07/13/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1942119/+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 1829397] Re: package linux-image-4.4.0-148-generic 4.4.0-148.174 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to update a package on your system due to a lack of free space on your system. Please resolve this situation manually and try the update again. ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Tags added: no-free-space -- 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/1829397 Title: package linux-image-4.4.0-148-generic 4.4.0-148.174 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: Server reported error - package linux-image-4.4.0-148-generic 4.4.0-148.174 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-148-generic 4.4.0-148.174 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 Uname: Linux 4.4.0-146-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu May 16 06:22:57 2019 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2016-09-21 (967 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: initramfs-tools Title: package linux-image-4.4.0-148-generic 4.4.0-148.174 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 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/1829397/+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 1824617] Re: package linux-firmware 1.157.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to update the kernel on your system due to a lack of free space in your boot partition. Please resolve this situation manually and try the update again. ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Tags added: no-boot-space -- 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/1824617 Title: package linux-firmware 1.157.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: when I switched on computer a propmt occured and thats it ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.21 ProcVersionSignature: Ubuntu 4.15.0-39.42~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: initramfs-tools: Configure linux-firmware: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Apr 13 13:47:51 2019 Dependencies: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-01-13 (454 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: initramfs-tools Title: package linux-firmware 1.157.21 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/1824617/+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 1884082] Re: package linux-image-5.4.0-37-generic 5.4.0-37.41 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to update a package on your system due to a lack of free space on your system. Please resolve this situation manually and try the update again. ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Tags added: no-free-space -- 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/1884082 Title: package linux-image-5.4.0-37-generic 5.4.0-37.41 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: Popped up just like dat. Had boot problems just befo dat du 2 2 less space. Keep up da gud work. Peace! Ps: sry fo ma dumb langauge. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cellardoor 1500 F pulseaudio CasperMD5CheckResult: skip Date: Wed Jun 17 12:16:57 2020 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-05-28 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M |__ Port 2: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: LENOVO 4243W4K ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=2115cb1b-ab29-42d1-8560-2ded1bfc06c3 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26 SourcePackage: initramfs-tools Title: package linux-image-5.4.0-37-generic 5.4.0-37.41 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET65WW (1.45 ) dmi.board.asset.tag: Not Available dmi.board.name: 4243W4K dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8AET65WW(1.45):bd05/14/2015:svnLENOVO:pn4243W4K:pvrThinkPadT520:rvnLENOVO:rn4243W4K:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T520 dmi.product.name: 4243W4K dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1884082/+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 1879421] Re: update-initramfs doesn't consider free space in /var/tmp
** Summary changed: - package initramfs-tools 0.133ubuntu10 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 + update-initramfs doesn't consider free space in /var/tmp -- 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/1879421 Title: update-initramfs doesn't consider free space in /var/tmp Status in initramfs-tools package in Ubuntu: New Bug description: Low disk space in /var/tmp mount causes post-installation script to fail. It should probably detect it. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: initramfs-tools 0.133ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-1023.25-raspi2 5.3.18 Uname: Linux 5.3.0-1023-raspi2 aarch64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: arm64 Date: Tue May 19 00:23:34 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to eoan on 2020-05-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879421/+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 1845836] Re: package linux-image-4.4.0-164-generic 4.4.0-164.192 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to update the kernel on your system due to a lack of free space in your boot partition. Please resolve this situation manually and try the update again. ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Tags added: no-boot-space -- 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/1845836 Title: package linux-image-4.4.0-164-generic 4.4.0-164.192 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: no ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-164-generic 4.4.0-164.192 Uname: Linux 4.8.0-040800-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Fri Sep 27 18:57:03 2019 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2018-07-05 (451 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.29ubuntu0.1 SourcePackage: initramfs-tools Title: package linux-image-4.4.0-164-generic 4.4.0-164.192 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 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/1845836/+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 1892143] Re: package linux-image-4.4.0-189-generic 4.4.0-189.219 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to update the kernel on your system due to a lack of free space in your boot partition. Please resolve this situation manually and try the update again. ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Tags added: no-boot-space -- 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/1892143 Title: package linux-image-4.4.0-189-generic 4.4.0-189.219 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: it is not upgrading ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-189-generic 4.4.0-189.219 ProcVersionSignature: Ubuntu 4.4.0-187.217-generic 4.4.230 Uname: Linux 4.4.0-187-generic i686 ApportVersion: 2.20.1-0ubuntu2.24 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pawan 1835 F pulseaudio Date: Wed Aug 19 13:27:54 2020 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=8fa258f5-01b1-490e-a55d-4abf285935f3 InstallationDate: Installed on 2015-12-13 (1710 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MachineType: Dell Inc. Inspiron 3252 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-187-generic root=UUID=28a6ff81-c9aa-4f94-af2c-1ce175675fd6 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.27 SourcePackage: initramfs-tools Title: package linux-image-4.4.0-189-generic 4.4.0-189.219 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to xenial on 2020-07-30 (19 days ago) dmi.bios.date: 12/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.6 dmi.board.name: 0WVYMC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.3.6:bd12/07/2015:svnDellInc.:pnInspiron3252:pvr2.3.6:rvnDellInc.:rn0WVYMC:rvrA00:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.name: Inspiron 3252 dmi.product.version: 2.3.6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1892143/+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 1958284] Re: shutdown hangs at "Waiting for process: ..." for 90s, ignoring DefaultTimeoutStopSec
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => 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/1958284 Title: shutdown hangs at "Waiting for process: ..." for 90s, ignoring DefaultTimeoutStopSec Status in systemd package in Ubuntu: Confirmed Bug description: With systemd v245 as shipped with 20.04, the shutdown sequence does not use the value of `DefaultTimeoutStopSec` to wait for remaining processes, it instead uses the compiled in default of 90s. This is most visible with services that use `KillMode=process` (docker, k8s, k3s, etc...), especially if the remaining processes do not handle `SIGTERM` or choose to ignore it. For example: ``` [ OK ] Finished Reboot. [ OK ] Reached target Reboot. [ 243.652848 ] systemd-shutdown[1]: Waiting for process: containerd-shim, containerd-shim, containerd-shim, fluent-bit --- hangs here for 90s even if DefaultTimeoutStopSec is set to a lower value --- ``` The bug has been fixed upstream here: https://github.com/systemd/systemd/commit/7d9eea2bd3d4f83668c7a78754d201b22 Marc was kind enough to package the patch for 20.04 so I could test it (https://launchpad.net/~mdeslaur/+archive/ubuntu/testing/+sourcepub/13210617/+listing- archive-extra) and with that package, I can confirm that it indeed fixes the issue. Here's a few github issues I stumbled upon while trying to debug this, along with a short writeup of the workaround I ended up using: - https://github.com/moby/moby/issues/41831 - https://github.com/k3s-io/k3s/issues/2400 - https://github.com/systemd/systemd/issues/16991 - https://raby.sh/debugging-90s-hangs-during-shutdown-on-ubuntu-2004.html Of course, it would be much better if all the processes would properly handle `SIGTERM`, but having a way to enforce a maximum wait time at shutdown is a decent workaround. Given that the patch is relatively simple, would it be possible to add it the package for 20.04? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1958284/+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 1958284] Re: shutdown hangs at "Waiting for process: ..." for 90s, ignoring DefaultTimeoutStopSec
** Description changed: With systemd v245 as shipped with 20.04, the shutdown sequence does not use the value of `DefaultTimeoutStopSec` to wait for remaining processes, it instead uses the compiled in default of 90s. This is most visible with services that use `KillMode=process` (docker, k8s, k3s, etc...), especially if the remaining processes do not handle `SIGTERM` or choose to ignore it. For example: ``` [ OK ] Finished Reboot. [ OK ] Reached target Reboot. [ 243.652848 ] systemd-shutdown[1]: Waiting for process: containerd-shim, containerd-shim, containerd-shim, fluent-bit --- hangs here for 90s even if DefaultTimeoutStopSec is set to a lower value --- ``` The bug has been fixed upstream here: https://github.com/systemd/systemd/commit/7d9eea2bd3d4f83668c7a78754d201b22 Marc was kind enough to package the patch for 20.04 so I could test it (https://launchpad.net/~mdeslaur/+archive/ubuntu/testing/+sourcepub/13210617/+listing- archive-extra) and with that package, I can confirm that it indeed fixes the issue. Here's a few github issues I stumbled upon while trying to debug this, along with a short writeup of the workaround I ended up using: - https://github.com/moby/moby/issues/41831 - https://github.com/k3s-io/k3s/issues/2400 - - http://localhost:8000/debugging-90s-hangs-during-shutdown-on-ubuntu-2004.html + - https://github.com/systemd/systemd/issues/16991 + - https://raby.sh/debugging-90s-hangs-during-shutdown-on-ubuntu-2004.html Of course, it would be much better if all the processes would properly handle `SIGTERM`, but having a way to enforce a maximum wait time at shutdown is a decent workaround. Given that the patch is relatively simple, would it be possible to add it the package for 20.04? Thanks -- 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/1958284 Title: shutdown hangs at "Waiting for process: ..." for 90s, ignoring DefaultTimeoutStopSec Status in systemd package in Ubuntu: New Bug description: With systemd v245 as shipped with 20.04, the shutdown sequence does not use the value of `DefaultTimeoutStopSec` to wait for remaining processes, it instead uses the compiled in default of 90s. This is most visible with services that use `KillMode=process` (docker, k8s, k3s, etc...), especially if the remaining processes do not handle `SIGTERM` or choose to ignore it. For example: ``` [ OK ] Finished Reboot. [ OK ] Reached target Reboot. [ 243.652848 ] systemd-shutdown[1]: Waiting for process: containerd-shim, containerd-shim, containerd-shim, fluent-bit --- hangs here for 90s even if DefaultTimeoutStopSec is set to a lower value --- ``` The bug has been fixed upstream here: https://github.com/systemd/systemd/commit/7d9eea2bd3d4f83668c7a78754d201b22 Marc was kind enough to package the patch for 20.04 so I could test it (https://launchpad.net/~mdeslaur/+archive/ubuntu/testing/+sourcepub/13210617/+listing- archive-extra) and with that package, I can confirm that it indeed fixes the issue. Here's a few github issues I stumbled upon while trying to debug this, along with a short writeup of the workaround I ended up using: - https://github.com/moby/moby/issues/41831 - https://github.com/k3s-io/k3s/issues/2400 - https://github.com/systemd/systemd/issues/16991 - https://raby.sh/debugging-90s-hangs-during-shutdown-on-ubuntu-2004.html Of course, it would be much better if all the processes would properly handle `SIGTERM`, but having a way to enforce a maximum wait time at shutdown is a decent workaround. Given that the patch is relatively simple, would it be possible to add it the package for 20.04? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1958284/+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 1955797] Re: [SRU] network-manager can’t modify MTU automatically based on what ModemManager exposes for WWAN modems.
Hello Jerry, or anyone else affected, Accepted network-manager into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.22.10-1ubuntu2.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: network-manager (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1955797 Title: [SRU] network-manager can’t modify MTU automatically based on what ModemManager exposes for WWAN modems. Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Focal: Fix Committed Bug description: [Impact] Some 4G/5G mobile networks(for ex., AT) requires a specific MTU setting, this setting will be exposed by the ModemManager for network- manger to configure the MTU of the modem network interface . The current modem-manager v1.22.10-1ubuntu2.2 in focal can’t pass AT’s modem system certification. [Fix] This upstream patch can resolve this bug: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/499/diffs?commit_id=212758ea05a4c13d65f36b55c90aee7919642631 [Test Plan] 1. Use a Lenovo platform SE30 including 4G Quectel EM160 modem and an AT SIM card in US 2. Enable 4G modem and connect to AT apn $ sudo mmcli -i 0 --pin= $ sudo mmcli --modem 0 --enable $ sudo mmcli -m 0 --simple-connect="pin=,apn=emome" $ sudo nmcli radio wwan on $ sudo nmcli connection add type gsm ifname wwan0p2MBIM con-name mymodem apn emome $ sudo nmcli connection up id mymodem 3. Check if the MTU got from the following results are the same: $ sudo mmcli --bearer 5 | mtu $ ifconfig mhi_mbim0 | grep mtu * Expected result: Both MTUs are the same value 1430 * Actual tested result: Different values (one is 1430 , another is 1500) [Where problems could occur] Very low. This is a simple fix: network-manager gets the MTU from the ModemManager then sets the MTU of the modem interface. [Other info] 1. Network-manager v1.30.0-1ubuntu3 in hirsute has included the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1955797/+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 1913775] Re: Copy from Firefox Wayland fails to be pasted anywhere else
Hello Stefano, or anyone else affected, Accepted gtk+3.0 into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.30-1ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gtk+3.0 (Ubuntu Impish) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1913775 Title: Copy from Firefox Wayland fails to be pasted anywhere else Status in GTK+: Unknown Status in firefox package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Impish: Fix Committed Bug description: * Impact The clipboard copies from GTK based software sometime stop working under wayland * Test Case - in a wayland session try to copy text between software, from firefox to gedit for example, it should work in a consistent manner alternative testcase inspired from the gitlab ticket - install wl-clipboard - use evince to open a pdf - select and copy some content - on a cmdline do $ wl-paste -t TEXT - try to paste then in another software, gedit for example the copied text should be pasted * Regression potential The changes are in the wayland selection source so the impact should only be for wayland users and limited to clipboard interactions -- Running Firefox 84.0.2 for Ubuntu Canonical-1.0 on Ubuntu 20.04.1 LTS, on Wayland native Version 84.0.2 Build ID 20210105180113 Window Protocol wayland Desktop Environment gnome DESCRIPTION OF THE PROBLEM: If I copy text from a web page and try to paste it into another Firefox page, the text is pasted correctly. If I copy text from a web page and try to paste it in [gedit, libreoffice, thunderbird, terminal, slack (electron)] nothing happens. The Gnome Clipboard extension stays empty when content is copied from Firefox Wayland. Pasting *from* another app *to* Firefox works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1913775/+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 1958284] [NEW] shutdown hangs at "Waiting for process: ..." for 90s, ignoring DefaultTimeoutStopSec
Public bug reported: With systemd v245 as shipped with 20.04, the shutdown sequence does not use the value of `DefaultTimeoutStopSec` to wait for remaining processes, it instead uses the compiled in default of 90s. This is most visible with services that use `KillMode=process` (docker, k8s, k3s, etc...), especially if the remaining processes do not handle `SIGTERM` or choose to ignore it. For example: ``` [ OK ] Finished Reboot. [ OK ] Reached target Reboot. [ 243.652848 ] systemd-shutdown[1]: Waiting for process: containerd-shim, containerd-shim, containerd-shim, fluent-bit --- hangs here for 90s even if DefaultTimeoutStopSec is set to a lower value --- ``` The bug has been fixed upstream here: https://github.com/systemd/systemd/commit/7d9eea2bd3d4f83668c7a78754d201b22 Marc was kind enough to package the patch for 20.04 so I could test it (https://launchpad.net/~mdeslaur/+archive/ubuntu/testing/+sourcepub/13210617/+listing- archive-extra) and with that package, I can confirm that it indeed fixes the issue. Here's a few github issues I stumbled upon while trying to debug this, along with a short writeup of the workaround I ended up using: - https://github.com/moby/moby/issues/41831 - https://github.com/k3s-io/k3s/issues/2400 - http://localhost:8000/debugging-90s-hangs-during-shutdown-on-ubuntu-2004.html Of course, it would be much better if all the processes would properly handle `SIGTERM`, but having a way to enforce a maximum wait time at shutdown is a decent workaround. Given that the patch is relatively simple, would it be possible to add it the package for 20.04? Thanks ** 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/1958284 Title: shutdown hangs at "Waiting for process: ..." for 90s, ignoring DefaultTimeoutStopSec Status in systemd package in Ubuntu: New Bug description: With systemd v245 as shipped with 20.04, the shutdown sequence does not use the value of `DefaultTimeoutStopSec` to wait for remaining processes, it instead uses the compiled in default of 90s. This is most visible with services that use `KillMode=process` (docker, k8s, k3s, etc...), especially if the remaining processes do not handle `SIGTERM` or choose to ignore it. For example: ``` [ OK ] Finished Reboot. [ OK ] Reached target Reboot. [ 243.652848 ] systemd-shutdown[1]: Waiting for process: containerd-shim, containerd-shim, containerd-shim, fluent-bit --- hangs here for 90s even if DefaultTimeoutStopSec is set to a lower value --- ``` The bug has been fixed upstream here: https://github.com/systemd/systemd/commit/7d9eea2bd3d4f83668c7a78754d201b22 Marc was kind enough to package the patch for 20.04 so I could test it (https://launchpad.net/~mdeslaur/+archive/ubuntu/testing/+sourcepub/13210617/+listing- archive-extra) and with that package, I can confirm that it indeed fixes the issue. Here's a few github issues I stumbled upon while trying to debug this, along with a short writeup of the workaround I ended up using: - https://github.com/moby/moby/issues/41831 - https://github.com/k3s-io/k3s/issues/2400 - http://localhost:8000/debugging-90s-hangs-during-shutdown-on-ubuntu-2004.html Of course, it would be much better if all the processes would properly handle `SIGTERM`, but having a way to enforce a maximum wait time at shutdown is a decent workaround. Given that the patch is relatively simple, would it be possible to add it the package for 20.04? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1958284/+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 1950828] Re: ibus-daemon crashed with SIGABRT in g_mutex_clear().
The only change I have made after the new installation was move my home to other partition. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1950828 Title: ibus-daemon crashed with SIGABRT in g_mutex_clear(). Status in ibus package in Ubuntu: New Bug description: Bug report generated after logging in. Nothing other then the log in was done. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: ibus 1.5.25-2build1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Nov 12 15:58:02 2021 ExecutablePath: /usr/bin/ibus-daemon InstallationDate: Installed on 2021-10-27 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211025) ProcCmdline: ibus-daemon --panel disable ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: ibus StacktraceTop: g_mutex_clear () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-daemon crashed with SIGABRT in g_mutex_clear() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1950828/+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 1931902] Re: [AMD Ellesmere] Crackling sound on Pulseaudio
The problem still occurs on the latest stable PulseAudio packages (1:15.0+dfsg1-1ubuntu2.2) for Ubuntu 21.10. Also, doing a "pulseaudio -k" on the Terminal, and then restarting any software that was outputting audio, fixes the issue. I've noticed that this only happens after the output audio device is changed between the available devices. So, going from the "HDMI/DP3 output" to "Digital Output" and then back will cause the crackling after a few minutes. ** Attachment added: "Audio output devices" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1931902/+attachment/205/+files/Captura%20de%20tela%20de%202022-01-18%2014-07-36.png -- 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/1931902 Title: [AMD Ellesmere] Crackling sound on Pulseaudio Status in pulseaudio package in Ubuntu: Confirmed Bug description: While playing back any sounds, a certain crackling sound (static) will play with a fixed delay of the sound being played. The amount and volume of the static will depend on the sound/music that is being played, and this only starts occurring after a somewhat long time (30 minutes or more). What is interesting to see is that while playing back music from Spotify (Snap) the static will only start after a second or so, but when playing YouTube videos on Firefox, it will be immediate and output that static while the video is playing. I've added two sound recordings, one while playing back a song from Spotify and the other while playing a song from YouTube. This issue goes away when restarting the PulseAudio service, but it comes back after a random amount of time. 1) Description: Ubuntu 21.04 Release: 21.04 2) pulseaudio: Installed: 1:14.2-1ubuntu1 Candidate: 1:14.2-1ubuntu1 Version table: 1:14.2-1ubuntu1.1 1 (phased 10%) 500 http://br.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages *** 1:14.2-1ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: pulseaudio 1:14.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: matheus 18662 F pulseaudio /dev/snd/controlC2: matheus 18662 F pulseaudio /dev/snd/controlC0: matheus 18662 F pulseaudio /dev/snd/pcmC0D8p: matheus 18662 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 14 16:58:43 2021 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2021-05-03 (41 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: LANG=pt_BR.UTF-8 LANGUAGE=pt_BR:pt:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: Default string dmi.board.name: PRIME B450-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd03/11/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1931902/+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 1945713] Re: Flaky test brotli/basic on focal amd64?
That's true that it works fine in jammy, but the breakage does still
occur sometimes on focal. In case others run across this issue on
focal, probably worth keeping this bug report open for reference.
** Also affects: libsoup2.4 (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libsoup2.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1945713
Title:
Flaky test brotli/basic on focal amd64?
Status in libsoup2.4 package in Ubuntu:
Fix Released
Status in libsoup2.4 source package in Focal:
New
Bug description:
The brotli/basic test case periodically fails. It appears that a few
retriggers can result in a pass:
https://autopkgtest.ubuntu.com/packages/libs/libsoup2.4/focal/amd64
The failures look like this in autopkgtest logs:
ERROR:../tests/brotli-decompressor-test.c:59:test_brotli:
assertion failed ((char*)out_bytes->data == contents): ("***\nU" ==
"***\n")
I've replaced most of the text with '***' to highlight the difference
is a 'U' character appended.
The test case is essentially doing a decompression of 'brotli-
data/compressed.br' and comparing that it matches 'brotli-
data/uncompressed.txt'. I've done this manually using the brotli cli,
and the files do indeed have the same content. I've also built the
package and run the test case locally in a focal lxc container on
amd64:
$ cd
libsoup2.4-gu/debian/libsoup2.4-tests/usr/libexec/installed-tests/libsoup-2.4
$ while : ; do ./brotli-decompressor-test | grep 'brotli/basic'; sleep
0.1; done
I left that to run several hundred cycles but no failures reported at
all.
There are a bunch of instances of this failure, here's a few for
reference:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20210602_152107_d1d56@/log.gz
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20210531_201241_8b1be@/log.gz
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20200508_211619_2aec8@/log.gz
That last link is the earliest instance I've been able to find.
You'll notice in the second two links they also have a failure "not ok
2 /ssl/tls-interaction", but the first link shows only the brotli
failure.
Interestingly, I've not found instances of this failure against other
architectures than amd64, nor have I seen it on releases other than
focal. No dice from googling for bug reports or other reports of test
failures with libsoup2.4 + brotli.
The test's code is doing this, basically:
SoupBrotliDecompressor *dec = soup_brotli_decompressor_new ();
do {
result = g_converter_convert (G_CONVERTER (dec), in_buf,
length, out_buf, sizeof out_buf, 0,
_read, _written,
);
g_byte_array_append (out_bytes, out_buf, bytes_written);
in_buf += bytes_read;
length -= bytes_read;
} while (result == G_CONVERTER_CONVERTED);
soup_brotli_decompressor's code is here:
https://gitlab.gnome.org/GNOME/libsoup/-/blob/master/libsoup/content-
decoder/soup-brotli-decompressor.c
But I'm not spotting anything that would obviously cause a 'U' to be
randomly appended sometimes. And why 'U'? UINT? Unknown? User error?
There are some interesting bug reports in GNOME about brotli in
libsoup's bug tracker (e.g. #106, #146, #119, and #193), but none that
match this.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1945713/+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 1958266] Re: package python3 3.9.7-4 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4
Upgrade was successful but there were problems in the rtupdate like: Exception: cannot get content of ibus-hangul so had to: cd /usr/share/python3/runtime.d sudo mkdir temp sudo mv ibus-hangul.rtupdate temp Had to move all of those those .rtupdate that said cannot get content of. Then dpkg --configure -a continued successfully. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1958266 Title: package python3 3.9.7-4 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 Status in python3-defaults package in Ubuntu: New Bug description: Upgraded to jammy and this crash showed up. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: python3 3.9.7-4 ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19 Uname: Linux 5.13.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Jan 18 23:57:23 2022 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2021-10-05 (105 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Beta amd64 (20211004) Python3Details: /usr/bin/python3.9, Python 3.9.9, python3-minimal, 3.9.7-4 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu3 apt 2.3.14 SourcePackage: python3-defaults Title: package python3 3.9.7-4 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to jammy on 2022-01-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1958266/+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 1958148] Re: mkinitramfs is too slow
** Tags added: fr-1977 -- 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/1958148 Title: mkinitramfs is too slow Status in initramfs-tools package in Ubuntu: In Progress Bug description: On the Nezha board creating an initrd takes more than 1 hour. The compression level -19 for zstd is unwisely chosen. Here are durations and compression results for an SiFive Unmatched board with four cores using zstd: -T0 -1 => 13.92s, 136298155 bytes -T0 -2 => 15.73s, 131717830 bytes -T0 -3 => 26.11s, 127434653 bytes -T0 -4 => 29.31s, 126924540 bytes -T0 -5 => 36.44s, 125296557 bytes -T0 -6 => 39.36s, 124781669 bytes -T0 -7 => 46.56s, 116200665 bytes -T0 -8 => 51.95s, 113172941 bytes -T0 -9 => 55.89s, 112835937 bytes -T0 -10 => 61.32s, 108326876 bytes -T0 -11 => 64.32s, 108115060 bytes -T0 -12 => 76.37s, 108016478 bytes -T0 -13 => 148.99s, 109121308 bytes -T0 -14 => 156.58s, 108908574 bytes -T0 -15 => 228.64s, 109213554 bytes -T0 -16 => 380.26s, 107260643 bytes -T0 -17 => 453.36s, 103679714 bytes -T0 -18 => 714.79s, 100402249 bytes -T0 -19 => 1046.58s, 100188713 bytes Compression level between -2 to -10 offer a good compromise between CPU time and compression results. Ideally there would be a parameter that we could pass to mkinitfs. But for as fast solution we should simply replace -19 by -9 in mkinitramfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+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 1958267] [NEW] "Connection failed" for WPA Enterprise network eduroam
Public bug reported: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wpa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy uec-images wayland-session ** Description changed: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by - Universities worldwide. I get a "Connection failed" message or q request + Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) + - Tried a 21.10 live session on the same machine: works fine! - - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - - Upgraded wpasupplicant back to the latest version: fails to connect again. + + - Manually downgraded wpasupplicant to the impish version + (2:2.9.0-21build1): connected normally. + + - Upgraded wpasupplicant to the latest version: fails to connect again. + ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network eduroam Status in wpa package in Ubuntu: New Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1958266] [NEW] package python3 3.9.7-4 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4
Public bug reported: Upgraded to jammy and this crash showed up. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: python3 3.9.7-4 ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19 Uname: Linux 5.13.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Jan 18 23:57:23 2022 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2021-10-05 (105 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Beta amd64 (20211004) Python3Details: /usr/bin/python3.9, Python 3.9.9, python3-minimal, 3.9.7-4 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu3 apt 2.3.14 SourcePackage: python3-defaults Title: package python3 3.9.7-4 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to jammy on 2022-01-18 (0 days ago) ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1958266 Title: package python3 3.9.7-4 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 Status in python3-defaults package in Ubuntu: New Bug description: Upgraded to jammy and this crash showed up. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: python3 3.9.7-4 ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19 Uname: Linux 5.13.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Jan 18 23:57:23 2022 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2021-10-05 (105 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Beta amd64 (20211004) Python3Details: /usr/bin/python3.9, Python 3.9.9, python3-minimal, 3.9.7-4 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu3 apt 2.3.14 SourcePackage: python3-defaults Title: package python3 3.9.7-4 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to jammy on 2022-01-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1958266/+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 1958148] Re: mkinitramfs is too slow
initramfs-tools - 0.140ubuntu11 is available in ppa:xypron/gnu-efi and needs a sponsor. ** Changed in: initramfs-tools (Ubuntu) Status: New => In Progress -- 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/1958148 Title: mkinitramfs is too slow Status in initramfs-tools package in Ubuntu: In Progress Bug description: On the Nezha board creating an initrd takes more than 1 hour. The compression level -19 for zstd is unwisely chosen. Here are durations and compression results for an SiFive Unmatched board with four cores using zstd: -T0 -1 => 13.92s, 136298155 bytes -T0 -2 => 15.73s, 131717830 bytes -T0 -3 => 26.11s, 127434653 bytes -T0 -4 => 29.31s, 126924540 bytes -T0 -5 => 36.44s, 125296557 bytes -T0 -6 => 39.36s, 124781669 bytes -T0 -7 => 46.56s, 116200665 bytes -T0 -8 => 51.95s, 113172941 bytes -T0 -9 => 55.89s, 112835937 bytes -T0 -10 => 61.32s, 108326876 bytes -T0 -11 => 64.32s, 108115060 bytes -T0 -12 => 76.37s, 108016478 bytes -T0 -13 => 148.99s, 109121308 bytes -T0 -14 => 156.58s, 108908574 bytes -T0 -15 => 228.64s, 109213554 bytes -T0 -16 => 380.26s, 107260643 bytes -T0 -17 => 453.36s, 103679714 bytes -T0 -18 => 714.79s, 100402249 bytes -T0 -19 => 1046.58s, 100188713 bytes Compression level between -2 to -10 offer a good compromise between CPU time and compression results. Ideally there would be a parameter that we could pass to mkinitfs. But for as fast solution we should simply replace -19 by -9 in mkinitramfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+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 1957816] Re: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed
I don't know if the speed is exactly doubled, by but changing the output definitely changes the playback speed of any media. I tried making a video to show it: https://youtu.be/hlqw_ijdxOE -- 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/1957816 Title: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed Status in pulseaudio package in Ubuntu: New Bug description: I have a desktop computer with a 60Hz 4K display connected through Display Port. The display is a ThinkVision X1 with built in audio. With the Display Port cable I am then able to output sound from the monitor and this works without any issues. I have now added a 4K Samsung television through HDMI to the same GPU, which also allows me to do 4K at 60Hz, albeit only with Wayland. In Xorg I can only do 30Hz on the television while doing 60Hz on the ThinkVision X1. It is clear however, that when it is set to 60Hz in Wayland, the animation on the television is much more smooth. The problem is that whenever I set the television to 60Hz, the playback of any sound is both high pitched and faster than normal. If I play a video in YouTube, the video appears to playback about twice as fast as normal and and very high pitched sound (everyone sounds like chipmunks). This is the case on the entire system (also when playing the video or any other sounds on the X1 display at 60Hz). Only if I set the refresh rate, on the television, to 30Hz again does everything play and sound normal again. It is only the playback of media that is doubled in speed. Everything else (animations, mouse, etc.) is still behaving as normal. If I change audio output to the ThinkVision X1 (or something else) at 60Hz while also being connected to the television at 60Hz, the audio stays high pitched and sped up. If I unplug the main display, ThinkVision X1, then the playback of media on the television becomes normal. I have tried with different +100 USD HDMI cables, that are all rated as HDMI 2.0 and the behavior stays the same. My system is Ubuntu 20.04 LTS. I tried in a LiveUSB 21.10, but the behavior was the same. I have an AMD Radeon VII GPU (Has 3x Display Port and 1x HDMI). As mentioned I cannot test it in Xorg, but that is only because it does not allow me to set the refresh rate to 60Hz. I am uncertain whether this is related to MESA, Pulseaudio or maybe Mutter/Wayland? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1957816/+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 1957086] Re: Autopkgtest systemd fail against dnsmasq 2.86 (22.04)
I tested the test of 249.5-2ubuntu2 (running autopkgtest against the dsc file of 249.5-2ubuntu2) vs the binary systemd build in your PPA (systemd_249.7-1ubuntu1~slyon0) + the dnsmasq from proposed. And I got: resolved: domain-restricted DNS servers ... ok That means: 1. the fix is not in debian/tests of the new systemd version 2. that your new build works to resolve that issue -- 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/1957086 Title: Autopkgtest systemd fail against dnsmasq 2.86 (22.04) Status in dnsmasq package in Ubuntu: New Status in systemd package in Ubuntu: In Progress Bug description: Full log (same on all architectures): https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/s/systemd/20220106_214401_24d29@/log.gz The test is from systemd: https://github.com/systemd/systemd/blob/main/test/networkd-test.py#L619 Tail of the log: ``` ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/tmp/autopkgtest.NdIvJq/build.fBQ/src/test/networkd-test.py", line 678, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.9/subprocess.py", line 424, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.9/subprocess.py", line 528, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. ``` Tagging update-excuse to be shown in excuses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1957086/+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 1957086] Re: Autopkgtest systemd fail against dnsmasq 2.86 (22.04)
** Changed in: systemd (Ubuntu) Status: New => In Progress -- 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/1957086 Title: Autopkgtest systemd fail against dnsmasq 2.86 (22.04) Status in dnsmasq package in Ubuntu: New Status in systemd package in Ubuntu: In Progress Bug description: Full log (same on all architectures): https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/s/systemd/20220106_214401_24d29@/log.gz The test is from systemd: https://github.com/systemd/systemd/blob/main/test/networkd-test.py#L619 Tail of the log: ``` ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/tmp/autopkgtest.NdIvJq/build.fBQ/src/test/networkd-test.py", line 678, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.9/subprocess.py", line 424, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.9/subprocess.py", line 528, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. ``` Tagging update-excuse to be shown in excuses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1957086/+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 1954649] Re: autopkgtest regressions with python3.10 as supported
** Changed in: python-hypothesis (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1954649 Title: autopkgtest regressions with python3.10 as supported Status in ipywidgets package in Ubuntu: New Status in pygobject package in Ubuntu: Fix Released Status in pytest-twisted package in Ubuntu: New Status in python-b2sdk package in Ubuntu: New Status in python-hypothesis package in Ubuntu: New Status in python-taskflow package in Ubuntu: Fix Released Status in python3-defaults package in Ubuntu: New Status in skimage package in Ubuntu: Invalid Status in supysonic package in Ubuntu: New Status in vorta package in Ubuntu: New Status in ipywidgets package in Debian: New Status in pygobject package in Debian: Fix Released Status in pytest-twisted package in Debian: New Status in python-b2sdk package in Debian: New Status in python-hypothesis package in Debian: Fix Released Status in supysonic package in Debian: Confirmed Status in vorta package in Debian: Confirmed Bug description: This bug is for tracking the packages having autopkgtest regressions with python3.10 as a supported version, blocking migration of python3-defaults/3.9.7-4. All packages are in universe except pygobject and python-taskflow in main. All packages have RC bugs in Debian except python-taskflow which is based on a newer upstream version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipywidgets/+bug/1954649/+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 1958244] [NEW] Sync acl 2.3.1-1 (main) from Debian unstable (main)
Public bug reported: Please sync acl 2.3.1-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * No-change rebuild to build packages with zstd compression. * Build with -fno-strict-aliasing * No-change rebuild to drop the udeb package. The aliasing issue has been fixed upstream, see https://git.savannah.nongnu.org/cgit/acl.git/commit/?id=cad5d69545765e00715d0cb0c88a3b4c20a59c1e Changelog entries since current jammy version 2.2.53-10ubuntu2: acl (2.3.1-1) unstable; urgency=medium * New upstream release. - Remove upstream patches included in this release. - Refresh remaining patches. - Update upstream signing key. * Add support for the noudeb build profile. -- Guillem Jover Sun, 29 Aug 2021 16:26:27 +0200 ** Affects: acl (Ubuntu) Importance: Wishlist Status: New ** Changed in: acl (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to acl in Ubuntu. https://bugs.launchpad.net/bugs/1958244 Title: Sync acl 2.3.1-1 (main) from Debian unstable (main) Status in acl package in Ubuntu: New Bug description: Please sync acl 2.3.1-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * No-change rebuild to build packages with zstd compression. * Build with -fno-strict-aliasing * No-change rebuild to drop the udeb package. The aliasing issue has been fixed upstream, see https://git.savannah.nongnu.org/cgit/acl.git/commit/?id=cad5d69545765e00715d0cb0c88a3b4c20a59c1e Changelog entries since current jammy version 2.2.53-10ubuntu2: acl (2.3.1-1) unstable; urgency=medium * New upstream release. - Remove upstream patches included in this release. - Refresh remaining patches. - Update upstream signing key. * Add support for the noudeb build profile. -- Guillem Jover Sun, 29 Aug 2021 16:26:27 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acl/+bug/1958244/+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 1958242] [NEW] mesa update freeze/crash screen before login
Public bug reported: After updating my laptop after a long trip. It starts to bootm, then screen goes black with the mouse pointer hanging over, sddm does not start. This symptoms I saw them before and were related to mesa libraries. See https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1909171 for details on that. But the actual problem seems somewhat different this time. Furthermore dmesg shows: [66.441074] QSGRenderThread[1134]: segfault at 39 ip 7f1ca6c7311b sp 7f1c98b76630 error 4 in r300_dri.so[7f1ca660b000+10ab000] [66.441088] Code: b6 40 2d eb ef 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 31 f6 e9 95 a2 f9 ff 0f 1f 44 00 00 41 54 48 8d 15 97 b8 b2 00 55 53 <0f> b6 47 39 48 89 f3 48 63 04 82 48 01 d0 3e ff e0 0f 1f 40 00bd r300_dri.so is from the package libgl1-mesa-dri I applied the same workaround I did for the previous time that mesa was broken: downgrade to previous mesa version. I went to Ctrl+Alt-F2, logged in and: ** sudo apt install libglapi-mesa=21.0.3-0ubuntu0.3~20.04.5 libglx-mesa0=21.0.3-0ubuntu0.3~20.04.5 libgl1-mesa-dri=21.0.3-0ubuntu0.3~20.04.5 libegl-mesa0=21.0.3-0ubuntu0.3~20.04.5 libgbm1=21.0.3-0ubuntu0.3~20.04.5 sudo apt-mark hold libglapi-mesa=21.0.3-0ubuntu0.3~20.04.5 libglx-mesa0=21.0.3-0ubuntu0.3~20.04.5 libgl1-mesa-dri=21.0.3-0ubuntu0.3~20.04.5 libegl-mesa0=21.0.3-0ubuntu0.3~20.04.5 libgbm1=21.0.3-0ubuntu0.3~20.04.5 *** Now everything works fine. Other than the mentioned mesa packages everything else is fully updated. === In short something got broken again in mesa 21.2.6, downgrading to 21.0.3 fixes the issue. === Running Lubuntu 20.04 Kernel: 5.4.0-94-generic #106-Ubuntu SMP Thu Jan 6 23:58:14 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux lsb_release -rd: Description:Ubuntu 20.04.3 LTS Release:20.04 GPU: Advanced Micro Devices [AMD/ATI] RS482M [Mobility Radeon Xpress 200] driver: radeon ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Description changed: After updating my laptop after a long trip. It starts to bootm, then screen goes black with the mouse pointer hanging over, sddm does not start. This symptoms I saw them before and were related to mesa libraries. See https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1909171 for details on that. But the actual problem seems somewhat different this time. Furthermore dmesg shows: [66.441074] QSGRenderThread[1134]: segfault at 39 ip 7f1ca6c7311b sp 7f1c98b76630 error 4 in r300_dri.so[7f1ca660b000+10ab000] [66.441088] Code: b6 40 2d eb ef 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 31 f6 e9 95 a2 f9 ff 0f 1f 44 00 00 41 54 48 8d 15 97 b8 b2 00 55 53 <0f> b6 47 39 48 89 f3 48 63 04 82 48 01 d0 3e ff e0 0f 1f 40 00bd r300_dri.so is from the package libgl1-mesa-dri I applied the same workaround I did for the previous time that mesa was broken: downgrade to previous mesa version. + I went to Ctrl+Alt-F2, logged in and: ** apt install libglapi-mesa=21.0.3-0ubuntu0.3~20.04.5 libglx-mesa0=21.0.3-0ubuntu0.3~20.04.5 libgl1-mesa-dri=21.0.3-0ubuntu0.3~20.04.5 libegl-mesa0=21.0.3-0ubuntu0.3~20.04.5 libgbm1=21.0.3-0ubuntu0.3~20.04.5 apt-mark hold libglapi-mesa=21.0.3-0ubuntu0.3~20.04.5 libglx-mesa0=21.0.3-0ubuntu0.3~20.04.5 libgl1-mesa-dri=21.0.3-0ubuntu0.3~20.04.5 libegl-mesa0=21.0.3-0ubuntu0.3~20.04.5 libgbm1=21.0.3-0ubuntu0.3~20.04.5 *** Now everything works fine. Other than the mentioned mesa packages everything else is fully updated. - === In short something got broken again in mesa 21.2.6, downgrading to 21.0.3 fixes the issue. === - Running Lubuntu 20.04 Kernel: 5.4.0-94-generic #106-Ubuntu SMP Thu Jan 6 23:58:14 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux lsb_release -rd: Description:Ubuntu 20.04.3 LTS Release:20.04 GPU: Advanced Micro Devices [AMD/ATI] RS482M [Mobility Radeon Xpress 200] driver: radeon ** Description changed: After updating my laptop after a long trip. It starts to bootm, then screen goes black with the mouse pointer hanging over, sddm does not start. This symptoms I saw them before and were related to mesa libraries. See https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1909171 for details on that. But the actual problem seems somewhat different this time. Furthermore dmesg shows: [66.441074] QSGRenderThread[1134]: segfault at 39 ip 7f1ca6c7311b sp 7f1c98b76630 error 4 in r300_dri.so[7f1ca660b000+10ab000] [66.441088] Code: b6 40 2d eb ef 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 31 f6 e9 95 a2 f9 ff 0f 1f 44 00 00 41 54 48 8d 15 97 b8 b2 00 55 53 <0f> b6 47 39 48 89 f3 48 63 04 82 48 01 d0 3e ff e0 0f 1f 40 00bd r300_dri.so is from the package libgl1-mesa-dri I applied the same workaround I did for the previous time that mesa was broken: downgrade to previous mesa version. I went to Ctrl+Alt-F2, logged in and: ** - apt
[Touch-packages] [Bug 1958053] Re: If dmesg has bug, then make popup info, to triage and fix.
** Changed in: util-linux (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1958053 Title: If dmesg has bug, then make popup info, to triage and fix. Status in util-linux package in Ubuntu: New Bug description: If dmesg has bug, then make popup info, to triage and fix. Like there was solution help written in dmesgn for Bug #1958038 automatization, but i dont know that i have a bug until i need to start using wifi. dmesg | grep -i firmware [3.832374] [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work. [ 22.693320] b43 ssb0:0: Direct firmware load for b43/ucode5.fw failed with error -2 [ 22.693365] b43 ssb0:0: Direct firmware load for b43/ucode5.fw failed with error -2 [ 22.693412] b43 ssb0:0: Direct firmware load for b43-open/ucode5.fw failed with error -2 [ 22.693446] b43 ssb0:0: Direct firmware load for b43-open/ucode5.fw failed with error -2 [ 22.693451] b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found [ 22.693458] b43-phy0 ERROR: Firmware file "b43-open/ucode5.fw" not found [ 22.693461] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website. [ 22.693545] Broadcom 43xx driver loaded [ Features: PNL ] [ 23.076733] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: util-linux 2.31.1-0.4ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157 Uname: Linux 5.4.0-94-generic i686 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: i386 CurrentDesktop: KDE Date: Sun Jan 16 04:44:01 2022 InstallationDate: Installed on 2022-01-15 (0 days ago) InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 (20200806.1) SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1958053/+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 1957086] Re: Autopkgtest systemd fail against dnsmasq 2.86 (22.04)
Thank you for all the investigation, Christian! I was planning to upgrade to >= v249.6 for Jammy anyway (probably 249.9). Will check the logs/patches for anything suspicious and verify if this solves this issue. There is a bileto PPA that contains a 249.7 prototype: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4704/+packages It might be worth a try copying the dnsmasq package into there and see if the tests pass. Let me check that. -- 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/1957086 Title: Autopkgtest systemd fail against dnsmasq 2.86 (22.04) Status in dnsmasq package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Full log (same on all architectures): https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/s/systemd/20220106_214401_24d29@/log.gz The test is from systemd: https://github.com/systemd/systemd/blob/main/test/networkd-test.py#L619 Tail of the log: ``` ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/tmp/autopkgtest.NdIvJq/build.fBQ/src/test/networkd-test.py", line 678, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.9/subprocess.py", line 424, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.9/subprocess.py", line 528, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. ``` Tagging update-excuse to be shown in excuses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1957086/+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
