[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Will this be released to Ubuntu 20.04? This is very important for voice calls in these times. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: Fix Released Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Committed Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
The fix is in the newest version https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/3.40.1-1 and has been SRUed to focal waiting for review ** Changed in: evolution-data-server (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x Status in evolution-data-server package in Ubuntu: Fix Released Bug description: There is a recently introduced bug in evolution-data-server which broke access to email in iCloud. The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+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 1923564] Re: BlueZ 5.58 release
Uploaded ** Changed in: bluez (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1923564 Title: BlueZ 5.58 release Status in bluez package in Ubuntu: Fix Committed Bug description: BlueZ 5.58 has been released. We should look at it for the 21.10 cycle... http://www.bluez.org/release-of-bluez-5-58-and-5-57/ https://mirrors.edge.kernel.org/pub/linux/bluetooth/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1923564/+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 1914279] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted backport-iwlwifi-dkms into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /backport-iwlwifi-dkms/8324-0ubuntu3~20.04.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: bcmwl (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: New Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: New Status in bcmwl package in Ubuntu: New Status in dahdi-linux package in Ubuntu: New Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: New Status in evdi package in Ubuntu: New Status in gost-crypto package in Ubuntu: New Status in iptables-netflow package in Ubuntu: New Status in liblzf package in Ubuntu: New Status in lime-forensics package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in r8168 package in Ubuntu: New Status in rtl8812au package in Ubuntu: New Status in sysdig package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in acpi-call source package in Focal: Fix Committed Status in backport-iwlwifi-dkms source package in Focal: Fix Committed Status in bcmwl source package in Focal: Fix Committed Status in dahdi-linux source package in Focal: Fix Committed Status in dm-writeboost source package in Focal: Fix Committed Status in evdi source package in Focal: Fix Committed Status in gost-crypto source package in Focal: Fix Committed Status in iptables-netflow source package in Focal: Fix Committed Status in liblzf source package in Focal: Fix Committed Status in lime-forensics source package in Focal: Fix Committed Status in lttng-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Status in oss4 source package in Focal: Fix Committed Status in r8168 source package in Focal: Fix Committed Status in rtl8812au source package in Focal: Fix Committed Status in sysdig source package in Focal: Fix Committed Status in v4l2loopback source package in Focal: Fix Committed Status in virtualbox source package in Focal: Fix Committed Status in virtualbox-hwe source package in Focal: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providi
[Touch-packages] [Bug 1927500] Re: package linux-firmware 1.187.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- 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/1927500 Title: package linux-firmware 1.187.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Ubuntu Ver. 20.04 LTS ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.12 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abacon 2023 F pulseaudio /dev/snd/controlC1: abacon 2023 F pulseaudio CasperMD5CheckResult: skip Date: Thu May 6 09:21:21 2021 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=41f89867-56b0-4c8e-864c-c2be78496c3b InstallationDate: Installed on 2016-06-11 (1789 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-72-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.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc N/A RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: initramfs-tools Title: package linux-firmware 1.187.12 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/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FB dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A78M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFB:bd04/27/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1927500/+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 1914279] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted dahdi-linux into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dahdi- linux/1:2.11.1~dfsg-1ubuntu6.2 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: dm-writeboost (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: New Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: New Status in bcmwl package in Ubuntu: New Status in dahdi-linux package in Ubuntu: New Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: New Status in evdi package in Ubuntu: New Status in gost-crypto package in Ubuntu: New Status in iptables-netflow package in Ubuntu: New Status in liblzf package in Ubuntu: New Status in lime-forensics package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in r8168 package in Ubuntu: New Status in rtl8812au package in Ubuntu: New Status in sysdig package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in acpi-call source package in Focal: Fix Committed Status in backport-iwlwifi-dkms source package in Focal: Fix Committed Status in bcmwl source package in Focal: Fix Committed Status in dahdi-linux source package in Focal: Fix Committed Status in dm-writeboost source package in Focal: Fix Committed Status in evdi source package in Focal: Fix Committed Status in gost-crypto source package in Focal: Fix Committed Status in iptables-netflow source package in Focal: Fix Committed Status in liblzf source package in Focal: Fix Committed Status in lime-forensics source package in Focal: Fix Committed Status in lttng-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Status in oss4 source package in Focal: Fix Committed Status in r8168 source package in Focal: Fix Committed Status in rtl8812au source package in Focal: Fix Committed Status in sysdig source package in Focal: Fix Committed Status in v4l2loopback source package in Focal: Fix Committed Status in virtualbox source package in Focal: Fix Committed Status in virtualbox-hwe source package in Focal: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networ
[Touch-packages] [Bug 1914279] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted evdi into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/evdi/1.7.0+dfsg- 1ubuntu1~20.04.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: gost-crypto (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: New Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: New Status in bcmwl package in Ubuntu: New Status in dahdi-linux package in Ubuntu: New Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: New Status in evdi package in Ubuntu: New Status in gost-crypto package in Ubuntu: New Status in iptables-netflow package in Ubuntu: New Status in liblzf package in Ubuntu: New Status in lime-forensics package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in r8168 package in Ubuntu: New Status in rtl8812au package in Ubuntu: New Status in sysdig package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in acpi-call source package in Focal: Fix Committed Status in backport-iwlwifi-dkms source package in Focal: Fix Committed Status in bcmwl source package in Focal: Fix Committed Status in dahdi-linux source package in Focal: Fix Committed Status in dm-writeboost source package in Focal: Fix Committed Status in evdi source package in Focal: Fix Committed Status in gost-crypto source package in Focal: Fix Committed Status in iptables-netflow source package in Focal: Fix Committed Status in liblzf source package in Focal: Fix Committed Status in lime-forensics source package in Focal: Fix Committed Status in lttng-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Status in oss4 source package in Focal: Fix Committed Status in r8168 source package in Focal: Fix Committed Status in rtl8812au source package in Focal: Fix Committed Status in sysdig source package in Focal: Fix Committed Status in v4l2loopback source package in Focal: Fix Committed Status in virtualbox source package in Focal: Fix Committed Status in virtualbox-hwe source package in Focal: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them
[Touch-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
** Also affects: acpi-call (Ubuntu) Importance: Undecided Status: New ** Also affects: backport-iwlwifi-dkms (Ubuntu) Importance: Undecided Status: New ** Also affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Also affects: dahdi-linux (Ubuntu) Importance: Undecided Status: New ** Also affects: dm-writeboost (Ubuntu) Importance: Undecided Status: New ** Also affects: evdi (Ubuntu) Importance: Undecided Status: New ** Also affects: gost-crypto (Ubuntu) Importance: Undecided Status: New ** Also affects: iptables-netflow (Ubuntu) Importance: Undecided Status: New ** Also affects: liblzf (Ubuntu) Importance: Undecided Status: New ** Also affects: lime-forensics (Ubuntu) Importance: Undecided Status: New ** Also affects: lttng-modules (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Also affects: openafs (Ubuntu) Importance: Undecided Status: New ** Also affects: oss4 (Ubuntu) Importance: Undecided Status: New ** Also affects: r8168 (Ubuntu) Importance: Undecided Status: New ** Also affects: rtl8812au (Ubuntu) Importance: Undecided Status: New ** Also affects: sysdig (Ubuntu) Importance: Undecided Status: New ** Also affects: v4l2loopback (Ubuntu) Importance: Undecided Status: New ** Also affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Also affects: virtualbox-hwe (Ubuntu) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: New Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: New Status in bcmwl package in Ubuntu: New Status in dahdi-linux package in Ubuntu: New Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: New Status in evdi package in Ubuntu: New Status in gost-crypto package in Ubuntu: New Status in iptables-netflow package in Ubuntu: New Status in liblzf package in Ubuntu: New Status in lime-forensics package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in r8168 package in Ubuntu: New Status in rtl8812au package in Ubuntu: New Status in sysdig package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+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 1923464] Re: ideally should boot rootfs from a matching hard drive
** Tags added: fr-1344 -- 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/1923464 Title: ideally should boot rootfs from a matching hard drive Status in cloud-images: New Status in grub2 package in Ubuntu: New Status in initramfs-tools package in Ubuntu: New Status in systemd package in Ubuntu: New Status in u-boot package in Ubuntu: New Status in u-boot-menu package in Ubuntu: New Bug description: Ideally we should strive to boot rootfs from a matching hard drive. I.e. if we are booting rootfs by UUID, we should try to find the one that came from the same drive as where ESP (UEFI) came from, or u-boot spl / u-boot got loaded from (loader1/loader2). Such that for example, when booted from external usb stick, rootfs from there is mounted. Or when booted from internal drive whilst a dd backup is attached over usb, rootfs is loaded from the internal drive not from the usb attached backup. This would need: * u-boot to export the drive it loaded extlinux.conf / bootscript from, and pass it on kernel command line * grub to export the device UUID it got loaded from (from the BootServices EFI table) and pass it on the kernel command line or via runtime EFI variable * sdboot already does that I believe, but not sure if initramfs-tools consumes the sdboot provided information * initramfs-tools to consume above and sort the discovered devices based on that, when deciding what to mount as rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1923464/+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 1923464] Re: ideally should boot rootfs from a matching hard drive
Just to not forget: This should work. We pass the ESP/boot partition to kernel, initramfs then looks at it, and if it finds UUID on same drive, it will take that one. If not it will take UUID from any drive, thus handling RAID or encryption automagically. -- 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/1923464 Title: ideally should boot rootfs from a matching hard drive Status in cloud-images: New Status in grub2 package in Ubuntu: New Status in initramfs-tools package in Ubuntu: New Status in systemd package in Ubuntu: New Status in u-boot package in Ubuntu: New Status in u-boot-menu package in Ubuntu: New Bug description: Ideally we should strive to boot rootfs from a matching hard drive. I.e. if we are booting rootfs by UUID, we should try to find the one that came from the same drive as where ESP (UEFI) came from, or u-boot spl / u-boot got loaded from (loader1/loader2). Such that for example, when booted from external usb stick, rootfs from there is mounted. Or when booted from internal drive whilst a dd backup is attached over usb, rootfs is loaded from the internal drive not from the usb attached backup. This would need: * u-boot to export the drive it loaded extlinux.conf / bootscript from, and pass it on kernel command line * grub to export the device UUID it got loaded from (from the BootServices EFI table) and pass it on the kernel command line or via runtime EFI variable * sdboot already does that I believe, but not sure if initramfs-tools consumes the sdboot provided information * initramfs-tools to consume above and sort the discovered devices based on that, when deciding what to mount as rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1923464/+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 1914279] Re: linux from security may force reboots without complete dkms modules
Hello Dimitri, or anyone else affected, Accepted acpi-call into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/acpi- call/1.1.0-5ubuntu0.2 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: acpi-call (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal ** Changed in: backport-iwlwifi-dkms (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: New Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: New Status in bcmwl package in Ubuntu: New Status in dahdi-linux package in Ubuntu: New Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: New Status in evdi package in Ubuntu: New Status in gost-crypto package in Ubuntu: New Status in iptables-netflow package in Ubuntu: New Status in liblzf package in Ubuntu: New Status in lime-forensics package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in r8168 package in Ubuntu: New Status in rtl8812au package in Ubuntu: New Status in sysdig package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in acpi-call source package in Focal: Fix Committed Status in backport-iwlwifi-dkms source package in Focal: Fix Committed Status in bcmwl source package in Focal: Fix Committed Status in dahdi-linux source package in Focal: Fix Committed Status in dm-writeboost source package in Focal: Fix Committed Status in evdi source package in Focal: Fix Committed Status in gost-crypto source package in Focal: Fix Committed Status in iptables-netflow source package in Focal: Fix Committed Status in liblzf source package in Focal: Fix Committed Status in lime-forensics source package in Focal: Fix Committed Status in lttng-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Status in oss4 source package in Focal: Fix Committed Status in r8168 source package in Focal: Fix Committed Status in rtl8812au source package in Focal: Fix Committed Status in sysdig source package in Focal: Fix Committed Status in v4l2loopback source package in Focal: Fix Committed Status in virtualbox source package in Focal: Fix Committed Status in virtualbox-hwe source package in Focal: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to re
[Touch-packages] [Bug 1914279] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted sysdig into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/sysdig/0.26.4-1ubuntu0.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: v4l2loopback (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: New Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: New Status in bcmwl package in Ubuntu: New Status in dahdi-linux package in Ubuntu: New Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: New Status in evdi package in Ubuntu: New Status in gost-crypto package in Ubuntu: New Status in iptables-netflow package in Ubuntu: New Status in liblzf package in Ubuntu: New Status in lime-forensics package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in r8168 package in Ubuntu: New Status in rtl8812au package in Ubuntu: New Status in sysdig package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in acpi-call source package in Focal: Fix Committed Status in backport-iwlwifi-dkms source package in Focal: Fix Committed Status in bcmwl source package in Focal: Fix Committed Status in dahdi-linux source package in Focal: Fix Committed Status in dm-writeboost source package in Focal: Fix Committed Status in evdi source package in Focal: Fix Committed Status in gost-crypto source package in Focal: Fix Committed Status in iptables-netflow source package in Focal: Fix Committed Status in liblzf source package in Focal: Fix Committed Status in lime-forensics source package in Focal: Fix Committed Status in lttng-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Status in oss4 source package in Focal: Fix Committed Status in r8168 source package in Focal: Fix Committed Status in rtl8812au source package in Focal: Fix Committed Status in sysdig source package in Focal: Fix Committed Status in v4l2loopback source package in Focal: Fix Committed Status in virtualbox source package in Focal: Fix Committed Status in virtualbox-hwe source package in Focal: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. S
[Touch-packages] [Bug 1914279] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted v4l2loopback into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/v4l2loopback/0.12.3-1ubuntu0.4 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: virtualbox (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: New Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: New Status in bcmwl package in Ubuntu: New Status in dahdi-linux package in Ubuntu: New Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: New Status in evdi package in Ubuntu: New Status in gost-crypto package in Ubuntu: New Status in iptables-netflow package in Ubuntu: New Status in liblzf package in Ubuntu: New Status in lime-forensics package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in r8168 package in Ubuntu: New Status in rtl8812au package in Ubuntu: New Status in sysdig package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in acpi-call source package in Focal: Fix Committed Status in backport-iwlwifi-dkms source package in Focal: Fix Committed Status in bcmwl source package in Focal: Fix Committed Status in dahdi-linux source package in Focal: Fix Committed Status in dm-writeboost source package in Focal: Fix Committed Status in evdi source package in Focal: Fix Committed Status in gost-crypto source package in Focal: Fix Committed Status in iptables-netflow source package in Focal: Fix Committed Status in liblzf source package in Focal: Fix Committed Status in lime-forensics source package in Focal: Fix Committed Status in lttng-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Status in oss4 source package in Focal: Fix Committed Status in r8168 source package in Focal: Fix Committed Status in rtl8812au source package in Focal: Fix Committed Status in sysdig source package in Focal: Fix Committed Status in v4l2loopback source package in Focal: Fix Committed Status in virtualbox source package in Focal: Fix Committed Status in virtualbox-hwe source package in Focal: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for
[Touch-packages] [Bug 1914279] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted nvidia-graphics-drivers-340 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 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: oss4 (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: New Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: New Status in bcmwl package in Ubuntu: New Status in dahdi-linux package in Ubuntu: New Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: New Status in evdi package in Ubuntu: New Status in gost-crypto package in Ubuntu: New Status in iptables-netflow package in Ubuntu: New Status in liblzf package in Ubuntu: New Status in lime-forensics package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in r8168 package in Ubuntu: New Status in rtl8812au package in Ubuntu: New Status in sysdig package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in acpi-call source package in Focal: Fix Committed Status in backport-iwlwifi-dkms source package in Focal: Fix Committed Status in bcmwl source package in Focal: Fix Committed Status in dahdi-linux source package in Focal: Fix Committed Status in dm-writeboost source package in Focal: Fix Committed Status in evdi source package in Focal: Fix Committed Status in gost-crypto source package in Focal: Fix Committed Status in iptables-netflow source package in Focal: Fix Committed Status in liblzf source package in Focal: Fix Committed Status in lime-forensics source package in Focal: Fix Committed Status in lttng-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Status in oss4 source package in Focal: Fix Committed Status in r8168 source package in Focal: Fix Committed Status in rtl8812au source package in Focal: Fix Committed Status in sysdig source package in Focal: Fix Committed Status in v4l2loopback source package in Focal: Fix Committed Status in virtualbox source package in Focal: Fix Committed Status in virtualbox-hwe source package in Focal: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that mi
[Touch-packages] [Bug 1914279] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted virtualbox into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/virtualbox/6.1.16-dfsg-6~ubuntu1.20.04.2 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: virtualbox-hwe (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: New Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: New Status in bcmwl package in Ubuntu: New Status in dahdi-linux package in Ubuntu: New Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: New Status in evdi package in Ubuntu: New Status in gost-crypto package in Ubuntu: New Status in iptables-netflow package in Ubuntu: New Status in liblzf package in Ubuntu: New Status in lime-forensics package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in r8168 package in Ubuntu: New Status in rtl8812au package in Ubuntu: New Status in sysdig package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in acpi-call source package in Focal: Fix Committed Status in backport-iwlwifi-dkms source package in Focal: Fix Committed Status in bcmwl source package in Focal: Fix Committed Status in dahdi-linux source package in Focal: Fix Committed Status in dm-writeboost source package in Focal: Fix Committed Status in evdi source package in Focal: Fix Committed Status in gost-crypto source package in Focal: Fix Committed Status in iptables-netflow source package in Focal: Fix Committed Status in liblzf source package in Focal: Fix Committed Status in lime-forensics source package in Focal: Fix Committed Status in lttng-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Status in oss4 source package in Focal: Fix Committed Status in r8168 source package in Focal: Fix Committed Status in rtl8812au source package in Focal: Fix Committed Status in sysdig source package in Focal: Fix Committed Status in v4l2loopback source package in Focal: Fix Committed Status in virtualbox source package in Focal: Fix Committed Status in virtualbox-hwe source package in Focal: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing net
[Touch-packages] [Bug 1914279] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted dm-writeboost into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dm- writeboost/2.2.9-1ubuntu1.2 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: evdi (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: New Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: New Status in bcmwl package in Ubuntu: New Status in dahdi-linux package in Ubuntu: New Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: New Status in evdi package in Ubuntu: New Status in gost-crypto package in Ubuntu: New Status in iptables-netflow package in Ubuntu: New Status in liblzf package in Ubuntu: New Status in lime-forensics package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in r8168 package in Ubuntu: New Status in rtl8812au package in Ubuntu: New Status in sysdig package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in acpi-call source package in Focal: Fix Committed Status in backport-iwlwifi-dkms source package in Focal: Fix Committed Status in bcmwl source package in Focal: Fix Committed Status in dahdi-linux source package in Focal: Fix Committed Status in dm-writeboost source package in Focal: Fix Committed Status in evdi source package in Focal: Fix Committed Status in gost-crypto source package in Focal: Fix Committed Status in iptables-netflow source package in Focal: Fix Committed Status in liblzf source package in Focal: Fix Committed Status in lime-forensics source package in Focal: Fix Committed Status in lttng-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Status in oss4 source package in Focal: Fix Committed Status in r8168 source package in Focal: Fix Committed Status in rtl8812au source package in Focal: Fix Committed Status in sysdig source package in Focal: Fix Committed Status in v4l2loopback source package in Focal: Fix Committed Status in virtualbox source package in Focal: Fix Committed Status in virtualbox-hwe source package in Focal: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them
[Touch-packages] [Bug 1914279] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted rtl8812au into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/rtl8812au/4.3.8.12175.20140902 +dfsg-0ubuntu13~20.04.2 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: sysdig (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: New Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: New Status in bcmwl package in Ubuntu: New Status in dahdi-linux package in Ubuntu: New Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: New Status in evdi package in Ubuntu: New Status in gost-crypto package in Ubuntu: New Status in iptables-netflow package in Ubuntu: New Status in liblzf package in Ubuntu: New Status in lime-forensics package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in r8168 package in Ubuntu: New Status in rtl8812au package in Ubuntu: New Status in sysdig package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in acpi-call source package in Focal: Fix Committed Status in backport-iwlwifi-dkms source package in Focal: Fix Committed Status in bcmwl source package in Focal: Fix Committed Status in dahdi-linux source package in Focal: Fix Committed Status in dm-writeboost source package in Focal: Fix Committed Status in evdi source package in Focal: Fix Committed Status in gost-crypto source package in Focal: Fix Committed Status in iptables-netflow source package in Focal: Fix Committed Status in liblzf source package in Focal: Fix Committed Status in lime-forensics source package in Focal: Fix Committed Status in lttng-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Status in oss4 source package in Focal: Fix Committed Status in r8168 source package in Focal: Fix Committed Status in rtl8812au source package in Focal: Fix Committed Status in sysdig source package in Focal: Fix Committed Status in v4l2loopback source package in Focal: Fix Committed Status in virtualbox source package in Focal: Fix Committed Status in virtualbox-hwe source package in Focal: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providin
[Touch-packages] [Bug 1914279] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted lttng-modules into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lttng- modules/2.12.2-1ubuntu1~20.04.2 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: nvidia-graphics-drivers-340 (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: New Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: New Status in bcmwl package in Ubuntu: New Status in dahdi-linux package in Ubuntu: New Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: New Status in evdi package in Ubuntu: New Status in gost-crypto package in Ubuntu: New Status in iptables-netflow package in Ubuntu: New Status in liblzf package in Ubuntu: New Status in lime-forensics package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in r8168 package in Ubuntu: New Status in rtl8812au package in Ubuntu: New Status in sysdig package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in acpi-call source package in Focal: Fix Committed Status in backport-iwlwifi-dkms source package in Focal: Fix Committed Status in bcmwl source package in Focal: Fix Committed Status in dahdi-linux source package in Focal: Fix Committed Status in dm-writeboost source package in Focal: Fix Committed Status in evdi source package in Focal: Fix Committed Status in gost-crypto source package in Focal: Fix Committed Status in iptables-netflow source package in Focal: Fix Committed Status in liblzf source package in Focal: Fix Committed Status in lime-forensics source package in Focal: Fix Committed Status in lttng-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Status in oss4 source package in Focal: Fix Committed Status in r8168 source package in Focal: Fix Committed Status in rtl8812au source package in Focal: Fix Committed Status in sysdig source package in Focal: Fix Committed Status in v4l2loopback source package in Focal: Fix Committed Status in virtualbox source package in Focal: Fix Committed Status in virtualbox-hwe source package in Focal: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be
[Touch-packages] [Bug 1914279] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted r8168 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/r8168/8.048.00-1ubuntu0.20.04.2 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: rtl8812au (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: New Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: New Status in bcmwl package in Ubuntu: New Status in dahdi-linux package in Ubuntu: New Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: New Status in evdi package in Ubuntu: New Status in gost-crypto package in Ubuntu: New Status in iptables-netflow package in Ubuntu: New Status in liblzf package in Ubuntu: New Status in lime-forensics package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in r8168 package in Ubuntu: New Status in rtl8812au package in Ubuntu: New Status in sysdig package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in acpi-call source package in Focal: Fix Committed Status in backport-iwlwifi-dkms source package in Focal: Fix Committed Status in bcmwl source package in Focal: Fix Committed Status in dahdi-linux source package in Focal: Fix Committed Status in dm-writeboost source package in Focal: Fix Committed Status in evdi source package in Focal: Fix Committed Status in gost-crypto source package in Focal: Fix Committed Status in iptables-netflow source package in Focal: Fix Committed Status in liblzf source package in Focal: Fix Committed Status in lime-forensics source package in Focal: Fix Committed Status in lttng-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Status in oss4 source package in Focal: Fix Committed Status in r8168 source package in Focal: Fix Committed Status in rtl8812au source package in Focal: Fix Committed Status in sysdig source package in Focal: Fix Committed Status in v4l2loopback source package in Focal: Fix Committed Status in virtualbox source package in Focal: Fix Committed Status in virtualbox-hwe source package in Focal: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them.
[Touch-packages] [Bug 1926855] Re: Raspberry Pi: desktop forgets audio device selected after reboot
** Tags added: raspi-image -- 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/1926855 Title: Raspberry Pi: desktop forgets audio device selected after reboot Status in pulseaudio package in Ubuntu: New Bug description: Hirsute 21.04 Raspberry Pi on Pi 4B 4GB Audio output device defaults to 'Headphones - Built-in Audio': this is the AV jack. Settings also lists 'Digital Output (S/PDIF) - Built-in Audio' which is HDMI, and I can get audio from it correctly. However, this setting is not saved, and on reboot it defaults back to 'Headphones - Built-in Audio'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1926855/+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 1914279] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted gost-crypto into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gost- crypto/0.3.2-2ubuntu0.2 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: iptables-netflow (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: New Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: New Status in bcmwl package in Ubuntu: New Status in dahdi-linux package in Ubuntu: New Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: New Status in evdi package in Ubuntu: New Status in gost-crypto package in Ubuntu: New Status in iptables-netflow package in Ubuntu: New Status in liblzf package in Ubuntu: New Status in lime-forensics package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in r8168 package in Ubuntu: New Status in rtl8812au package in Ubuntu: New Status in sysdig package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in acpi-call source package in Focal: Fix Committed Status in backport-iwlwifi-dkms source package in Focal: Fix Committed Status in bcmwl source package in Focal: Fix Committed Status in dahdi-linux source package in Focal: Fix Committed Status in dm-writeboost source package in Focal: Fix Committed Status in evdi source package in Focal: Fix Committed Status in gost-crypto source package in Focal: Fix Committed Status in iptables-netflow source package in Focal: Fix Committed Status in liblzf source package in Focal: Fix Committed Status in lime-forensics source package in Focal: Fix Committed Status in lttng-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Status in oss4 source package in Focal: Fix Committed Status in r8168 source package in Focal: Fix Committed Status in rtl8812au source package in Focal: Fix Committed Status in sysdig source package in Focal: Fix Committed Status in v4l2loopback source package in Focal: Fix Committed Status in virtualbox source package in Focal: Fix Committed Status in virtualbox-hwe source package in Focal: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking
[Touch-packages] [Bug 1914279] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted iptables-netflow into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/iptables- netflow/2.4-2ubuntu0.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: liblzf (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: New Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: New Status in bcmwl package in Ubuntu: New Status in dahdi-linux package in Ubuntu: New Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: New Status in evdi package in Ubuntu: New Status in gost-crypto package in Ubuntu: New Status in iptables-netflow package in Ubuntu: New Status in liblzf package in Ubuntu: New Status in lime-forensics package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in r8168 package in Ubuntu: New Status in rtl8812au package in Ubuntu: New Status in sysdig package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in acpi-call source package in Focal: Fix Committed Status in backport-iwlwifi-dkms source package in Focal: Fix Committed Status in bcmwl source package in Focal: Fix Committed Status in dahdi-linux source package in Focal: Fix Committed Status in dm-writeboost source package in Focal: Fix Committed Status in evdi source package in Focal: Fix Committed Status in gost-crypto source package in Focal: Fix Committed Status in iptables-netflow source package in Focal: Fix Committed Status in liblzf source package in Focal: Fix Committed Status in lime-forensics source package in Focal: Fix Committed Status in lttng-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Status in oss4 source package in Focal: Fix Committed Status in r8168 source package in Focal: Fix Committed Status in rtl8812au source package in Focal: Fix Committed Status in sysdig source package in Focal: Fix Committed Status in v4l2loopback source package in Focal: Fix Committed Status in virtualbox source package in Focal: Fix Committed Status in virtualbox-hwe source package in Focal: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking fo
[Touch-packages] [Bug 1914279] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted virtualbox-hwe into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/virtualbox- hwe/6.1.16-dfsg-6ubuntu1.20.04.2 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: zfs-linux (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: New Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: New Status in bcmwl package in Ubuntu: New Status in dahdi-linux package in Ubuntu: New Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: New Status in evdi package in Ubuntu: New Status in gost-crypto package in Ubuntu: New Status in iptables-netflow package in Ubuntu: New Status in liblzf package in Ubuntu: New Status in lime-forensics package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in r8168 package in Ubuntu: New Status in rtl8812au package in Ubuntu: New Status in sysdig package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in acpi-call source package in Focal: Fix Committed Status in backport-iwlwifi-dkms source package in Focal: Fix Committed Status in bcmwl source package in Focal: Fix Committed Status in dahdi-linux source package in Focal: Fix Committed Status in dm-writeboost source package in Focal: Fix Committed Status in evdi source package in Focal: Fix Committed Status in gost-crypto source package in Focal: Fix Committed Status in iptables-netflow source package in Focal: Fix Committed Status in liblzf source package in Focal: Fix Committed Status in lime-forensics source package in Focal: Fix Committed Status in lttng-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Status in oss4 source package in Focal: Fix Committed Status in r8168 source package in Focal: Fix Committed Status in rtl8812au source package in Focal: Fix Committed Status in sysdig source package in Focal: Fix Committed Status in v4l2loopback source package in Focal: Fix Committed Status in virtualbox source package in Focal: Fix Committed Status in virtualbox-hwe source package in Focal: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing
[Touch-packages] [Bug 1914279] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted lime-forensics into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lime- forensics/1.9-1ubuntu0.2 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: lttng-modules (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: New Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: New Status in bcmwl package in Ubuntu: New Status in dahdi-linux package in Ubuntu: New Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: New Status in evdi package in Ubuntu: New Status in gost-crypto package in Ubuntu: New Status in iptables-netflow package in Ubuntu: New Status in liblzf package in Ubuntu: New Status in lime-forensics package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in r8168 package in Ubuntu: New Status in rtl8812au package in Ubuntu: New Status in sysdig package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in acpi-call source package in Focal: Fix Committed Status in backport-iwlwifi-dkms source package in Focal: Fix Committed Status in bcmwl source package in Focal: Fix Committed Status in dahdi-linux source package in Focal: Fix Committed Status in dm-writeboost source package in Focal: Fix Committed Status in evdi source package in Focal: Fix Committed Status in gost-crypto source package in Focal: Fix Committed Status in iptables-netflow source package in Focal: Fix Committed Status in liblzf source package in Focal: Fix Committed Status in lime-forensics source package in Focal: Fix Committed Status in lttng-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Status in oss4 source package in Focal: Fix Committed Status in r8168 source package in Focal: Fix Committed Status in rtl8812au source package in Focal: Fix Committed Status in sysdig source package in Focal: Fix Committed Status in v4l2loopback source package in Focal: Fix Committed Status in virtualbox source package in Focal: Fix Committed Status in virtualbox-hwe source package in Focal: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking
[Touch-packages] [Bug 1914279] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted oss4 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/oss4/4.2-build2010-5ubuntu6~20.04.2 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: r8168 (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: New Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: New Status in bcmwl package in Ubuntu: New Status in dahdi-linux package in Ubuntu: New Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: New Status in evdi package in Ubuntu: New Status in gost-crypto package in Ubuntu: New Status in iptables-netflow package in Ubuntu: New Status in liblzf package in Ubuntu: New Status in lime-forensics package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in r8168 package in Ubuntu: New Status in rtl8812au package in Ubuntu: New Status in sysdig package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in acpi-call source package in Focal: Fix Committed Status in backport-iwlwifi-dkms source package in Focal: Fix Committed Status in bcmwl source package in Focal: Fix Committed Status in dahdi-linux source package in Focal: Fix Committed Status in dm-writeboost source package in Focal: Fix Committed Status in evdi source package in Focal: Fix Committed Status in gost-crypto source package in Focal: Fix Committed Status in iptables-netflow source package in Focal: Fix Committed Status in liblzf source package in Focal: Fix Committed Status in lime-forensics source package in Focal: Fix Committed Status in lttng-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Status in oss4 source package in Focal: Fix Committed Status in r8168 source package in Focal: Fix Committed Status in rtl8812au source package in Focal: Fix Committed Status in sysdig source package in Focal: Fix Committed Status in v4l2loopback source package in Focal: Fix Committed Status in virtualbox source package in Focal: Fix Committed Status in virtualbox-hwe source package in Focal: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them.
[Touch-packages] [Bug 1914279] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted zfs-linux into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/zfs- linux/0.8.3-1ubuntu12.9 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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: New Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: New Status in bcmwl package in Ubuntu: New Status in dahdi-linux package in Ubuntu: New Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: New Status in evdi package in Ubuntu: New Status in gost-crypto package in Ubuntu: New Status in iptables-netflow package in Ubuntu: New Status in liblzf package in Ubuntu: New Status in lime-forensics package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in r8168 package in Ubuntu: New Status in rtl8812au package in Ubuntu: New Status in sysdig package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in acpi-call source package in Focal: Fix Committed Status in backport-iwlwifi-dkms source package in Focal: Fix Committed Status in bcmwl source package in Focal: Fix Committed Status in dahdi-linux source package in Focal: Fix Committed Status in dm-writeboost source package in Focal: Fix Committed Status in evdi source package in Focal: Fix Committed Status in gost-crypto source package in Focal: Fix Committed Status in iptables-netflow source package in Focal: Fix Committed Status in liblzf source package in Focal: Fix Committed Status in lime-forensics source package in Focal: Fix Committed Status in lttng-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Status in oss4 source package in Focal: Fix Committed Status in r8168 source package in Focal: Fix Committed Status in rtl8812au source package in Focal: Fix Committed Status in sysdig source package in Focal: Fix Committed Status in v4l2loopback source package in Focal: Fix Committed Status in virtualbox source package in Focal: Fix Committed Status in virtualbox-hwe source package in Focal: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket,
[Touch-packages] [Bug 1927192] Re: gdb ftbfs on armhf, testsuite timeouts
** Also affects: gdb (Ubuntu Impish) Importance: High Status: Confirmed ** Tags removed: rls-ii-incoming ** Tags added: fr-1346 -- 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: Confirmed Status in gdb package in Ubuntu: Confirmed Status in gdb source package in Impish: Confirmed Bug description: 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 1923464] Re: ideally should boot rootfs from a matching hard drive
** Tags removed: rls-ii-incoming ** Also affects: grub2 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: u-boot (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: u-boot-menu (Ubuntu Impish) 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/1923464 Title: ideally should boot rootfs from a matching hard drive Status in cloud-images: New Status in grub2 package in Ubuntu: New Status in initramfs-tools package in Ubuntu: New Status in systemd package in Ubuntu: New Status in u-boot package in Ubuntu: New Status in u-boot-menu package in Ubuntu: New Status in grub2 source package in Impish: New Status in initramfs-tools source package in Impish: New Status in systemd source package in Impish: New Status in u-boot source package in Impish: New Status in u-boot-menu source package in Impish: New Bug description: Ideally we should strive to boot rootfs from a matching hard drive. I.e. if we are booting rootfs by UUID, we should try to find the one that came from the same drive as where ESP (UEFI) came from, or u-boot spl / u-boot got loaded from (loader1/loader2). Such that for example, when booted from external usb stick, rootfs from there is mounted. Or when booted from internal drive whilst a dd backup is attached over usb, rootfs is loaded from the internal drive not from the usb attached backup. This would need: * u-boot to export the drive it loaded extlinux.conf / bootscript from, and pass it on kernel command line * grub to export the device UUID it got loaded from (from the BootServices EFI table) and pass it on the kernel command line or via runtime EFI variable * sdboot already does that I believe, but not sure if initramfs-tools consumes the sdboot provided information * initramfs-tools to consume above and sort the discovered devices based on that, when deciding what to mount as rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1923464/+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 1926906] Re: (Ubuntu 21.04) RPi4 audio is slow and crackling
** Tags added: raspi-image -- 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/1926906 Title: (Ubuntu 21.04) RPi4 audio is slow and crackling Status in pulseaudio package in Ubuntu: New Bug description: I'm using a Raspberry Pi 4. After updating from Ubuntu 20.10 to 21.04, I noticed audio problems. The sound is slow and crackling. I'm using the headphone jack and the config.txt option: dtparam=audio=on If I start a video or audio file in VLC player and select the VLC options: Audio: Output module: ALSA Audio Output Device: bcm2835 Headphones, bcm2835 Headphones Default Audio Device Then the playback speed seems to be normal but the "electric" crackling in voices remains. And system-wide the problem persists, too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1926906/+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 1927554] Re: View with all opened windows is not closing
*** This bug is a duplicate of bug 1922353 *** https://bugs.launchpad.net/bugs/1922353 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1922353, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1922353 Overview sometimes fails to appear or disappear -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1927554 Title: View with all opened windows is not closing Status in xorg package in Ubuntu: New Bug description: Did a fresh install of Ubuntu 21.04 today and experienced the following problem: When I hit the Windows/Super button, a view with all opened windows is shown. It looks a bit different from the view that opens up when you click on "Activities" in the top left corner. Windows can be closed via orange (x) at the top right corner and new windows can be opened (via click on icons in dock and task bar) but the view itself cannot be closed. I can press any key but it won't disappear. As quick fix I logged out and back in again, the desktop was behaving normal afterwards. But as soon as I push the Windows/Super button, the view is there again and I cannot close it. Quite interesting: When the mentioned view appears I am still able to switch the virtual desktop via Ctrl + Alt + Arrow Keys. The second desktop is empty, the view doesn't appear here. But as soon as I switch back to the first desktop, the view is there again. Concerning the package in which I found this bug: I wasn't able to choose Wayland, because I was told that something went wrong with my search. Tell me if you need further information. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 6 22:25:05 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: openrazer-driver, 3.0.1, 5.11.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:8478] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Ti Mobile] [103c:8478] InstallationDate: Installed on 2021-05-06 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP HP Pavilion Gaming Laptop 15-cx0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic root=/dev/mapper/vglinux-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2019 dmi.bios.release: 15.20 dmi.bios.vendor: Insyde dmi.bios.version: F.20 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8478 dmi.board.vendor: HP dmi.board.version: 70.55 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 70.55 dmi.modalias: dmi:bvnInsyde:bvrF.20:bd05/07/2019:br15.20:efr70.55:svnHP:pnHPPavilionGamingLaptop15-cx0xxx:pvrType1ProductConfigId:rvnHP:rn8478:rvr70.55:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-cx0xxx dmi.product.sku: 8XN28EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To man
[Touch-packages] [Bug 1927554] Re: View with all opened windows is not closing
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1927554 Title: View with all opened windows is not closing Status in xorg package in Ubuntu: New Bug description: Did a fresh install of Ubuntu 21.04 today and experienced the following problem: When I hit the Windows/Super button, a view with all opened windows is shown. It looks a bit different from the view that opens up when you click on "Activities" in the top left corner. Windows can be closed via orange (x) at the top right corner and new windows can be opened (via click on icons in dock and task bar) but the view itself cannot be closed. I can press any key but it won't disappear. As quick fix I logged out and back in again, the desktop was behaving normal afterwards. But as soon as I push the Windows/Super button, the view is there again and I cannot close it. Quite interesting: When the mentioned view appears I am still able to switch the virtual desktop via Ctrl + Alt + Arrow Keys. The second desktop is empty, the view doesn't appear here. But as soon as I switch back to the first desktop, the view is there again. Concerning the package in which I found this bug: I wasn't able to choose Wayland, because I was told that something went wrong with my search. Tell me if you need further information. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 6 22:25:05 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: openrazer-driver, 3.0.1, 5.11.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:8478] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Ti Mobile] [103c:8478] InstallationDate: Installed on 2021-05-06 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP HP Pavilion Gaming Laptop 15-cx0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic root=/dev/mapper/vglinux-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2019 dmi.bios.release: 15.20 dmi.bios.vendor: Insyde dmi.bios.version: F.20 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8478 dmi.board.vendor: HP dmi.board.version: 70.55 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 70.55 dmi.modalias: dmi:bvnInsyde:bvrF.20:bd05/07/2019:br15.20:efr70.55:svnHP:pnHPPavilionGamingLaptop15-cx0xxx:pvrType1ProductConfigId:rvnHP:rn8478:rvr70.55:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-cx0xxx dmi.product.sku: 8XN28EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1927554/+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 1927554] [NEW] View with all opened windows is not closing
You have been subscribed to a public bug: Did a fresh install of Ubuntu 21.04 today and experienced the following problem: When I hit the Windows/Super button, a view with all opened windows is shown. It looks a bit different from the view that opens up when you click on "Activities" in the top left corner. Windows can be closed via orange (x) at the top right corner and new windows can be opened (via click on icons in dock and task bar) but the view itself cannot be closed. I can press any key but it won't disappear. As quick fix I logged out and back in again, the desktop was behaving normal afterwards. But as soon as I push the Windows/Super button, the view is there again and I cannot close it. Quite interesting: When the mentioned view appears I am still able to switch the virtual desktop via Ctrl + Alt + Arrow Keys. The second desktop is empty, the view doesn't appear here. But as soon as I switch back to the first desktop, the view is there again. Concerning the package in which I found this bug: I wasn't able to choose Wayland, because I was told that something went wrong with my search. Tell me if you need further information. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 6 22:25:05 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: openrazer-driver, 3.0.1, 5.11.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:8478] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Ti Mobile] [103c:8478] InstallationDate: Installed on 2021-05-06 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP HP Pavilion Gaming Laptop 15-cx0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic root=/dev/mapper/vglinux-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2019 dmi.bios.release: 15.20 dmi.bios.vendor: Insyde dmi.bios.version: F.20 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8478 dmi.board.vendor: HP dmi.board.version: 70.55 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 70.55 dmi.modalias: dmi:bvnInsyde:bvrF.20:bd05/07/2019:br15.20:efr70.55:svnHP:pnHPPavilionGamingLaptop15-cx0xxx:pvrType1ProductConfigId:rvnHP:rn8478:rvr70.55:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-cx0xxx dmi.product.sku: 8XN28EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu wayland-session -- View with all opened windows is not closing https://bugs.launchpad.net/bugs/1927554 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- 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 1927552] [NEW] Problem with pop-up scan (goldendict) with multiple desktops in Wayland.
Public bug reported: The problem arises with the use of multiple desktops. The popup scan has erratic behavior and does not work when it should (works on a desktop only). According to my research it is an old problem: https://github.com/goldendict/goldendict/issues/913 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] Permissão recusada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 6 17:54:19 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000] InstallationDate: Installed on 2021-03-04 (63 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash radeon.audio=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: SEx dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu wayland-session ** Description changed: The problem arises with the use of multiple desktops. The popup scan has erratic behavior and does not work when it should (works on a desktop - only) + only). According to my research it is an old problem: + https://github.com/goldendict/goldendict/issues/913 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] Permissão recusada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 6 17:54:19 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) -Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000] + Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) + Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000] InstallationDate: Installed on 2021-03-04 (63 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash radeon.audio=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: SEx dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sy
[Touch-packages] [Bug 1925057] Re: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1925057 Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound Status in linux package in Ubuntu: Incomplete Bug description: Hello, I'm using Ubuntu together with Windows on my laptop. If I boot in Ubuntu after Windows sound doesn't work well (instead of system sounds I can hear only shot noise). To fix the issue I need to completely shut down the system (call Power Off via Ubuntu GUI) and then boot again in Ubuntu. Please note, that reboot (called via Ubuntu GUI) doesn't help to fix the issue. Expected result: sound works well regardless of boot history. Actual result: every time I boot in Ubuntu after Windows sound doesn't work. Issue occurrence: 100%. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Thank you in advance! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1640 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 19 19:37:56 2021 InstallationDate: Installed on 2021-03-06 (43 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: кві 19 19:37:21 tiptop pulseaudio[958]: After module unload, module 'module-null-sink' was still loaded! кві 19 19:37:21 tiptop systemd[944]: pulseaudio.service: Succeeded. кві 19 19:37:40 tiptop systemd[944]: pulseaudio.service: Succeeded. кві 19 19:37:50 tiptop systemd[944]: pulseaudio.socket: Succeeded. Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to hirsute on 2021-03-06 (43 days ago) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925057/+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 1914279] Autopkgtest regression report (virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2)
All autopkgtests for the newly accepted virtualbox-hwe (6.1.16-dfsg-6ubuntu1.20.04.2) for focal have finished running. The following regressions have been reported in tests triggered by the package: virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (s390x, ppc64el, armhf, arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#virtualbox-hwe [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: New Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: New Status in bcmwl package in Ubuntu: New Status in dahdi-linux package in Ubuntu: New Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: New Status in evdi package in Ubuntu: New Status in gost-crypto package in Ubuntu: New Status in iptables-netflow package in Ubuntu: New Status in liblzf package in Ubuntu: New Status in lime-forensics package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in r8168 package in Ubuntu: New Status in rtl8812au package in Ubuntu: New Status in sysdig package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in acpi-call source package in Focal: Fix Committed Status in backport-iwlwifi-dkms source package in Focal: Fix Committed Status in bcmwl source package in Focal: Fix Committed Status in dahdi-linux source package in Focal: Fix Committed Status in dm-writeboost source package in Focal: Fix Committed Status in evdi source package in Focal: Fix Committed Status in gost-crypto source package in Focal: Fix Committed Status in iptables-netflow source package in Focal: Fix Committed Status in liblzf source package in Focal: Fix Committed Status in lime-forensics source package in Focal: Fix Committed Status in lttng-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Status in oss4 source package in Focal: Fix Committed Status in r8168 source package in Focal: Fix Committed Status in rtl8812au source package in Focal: Fix Committed Status in sysdig source package in Focal: Fix Committed Status in v4l2loopback source package in Focal: Fix Committed Status in virtualbox source package in Focal: Fix Committed Status in virtualbox-hwe source package in Focal: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+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 1432413] Re: Synaptic Touchpad xevents are hijacked under X
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1432413 Title: Synaptic Touchpad xevents are hijacked under X Status in xorg package in Ubuntu: Confirmed Bug description: Synaptic Touchpad xevents are hijacked under X11. I have a problem with the synaptic touch-pad on my Acer Aspire that started around a week ago. The problem can be described as that there is a massive amount of xevents being generated and appearing to originate from the touch-pad even though the touch-pad is not used. I have tested the HW which seems to work fine. The test performed is to start a terminal session (Ctrl + Alt + 2) before the fault occurs and check the xevents by running ~$ sudo evtest /dev/input/eventX where the X to use is found in /proc/bus/input/devices and found by running ~$ cat /proc/bus/input/devices |grep mouse No matter how much the touch-pad is used will the console show the corresponding events which indicates that HW and driver works OK as long it is not under X When the problem has occurred (in Desktop mode) is it easy (but inconvenient) to get back to normal by key combo Fn+F7 twice, turn off touch-pad and then turn on again. And more, one can get unlucky in the sense that the generated events could click somewhere one do not want to click. During the problem is it impossible to use the mouse since it flies around (mostly going in a bottom to top of screen direction) but one can check the generated events using evtest again. How can I help troubleshooting the problem? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Mar 15 19:51:13 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0933] InstallationDate: Installed on 2015-02-21 (22 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Acer Aspire E3-112 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic root=UUID=a97d0b51-4244-48ca-ba87-bc3a38a8b62d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireE3-112:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E3-112 dmi.product.version: V1.08 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Mar 15 18:59:07 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1576 vendor BOE xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1432413/+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 1927552] Re: Problem with pop-up scan (goldendict) with multiple desktops in Wayland.
** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Also affects: goldendict (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1927552 Title: Problem with pop-up scan (goldendict) with multiple desktops in Wayland. Status in goldendict package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: The problem arises with the use of multiple desktops. The popup scan has erratic behavior and does not work when it should (works on a desktop only). According to my research it is an old problem: https://github.com/goldendict/goldendict/issues/913 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] Permissão recusada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 6 17:54:19 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000] InstallationDate: Installed on 2021-03-04 (63 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash radeon.audio=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: SEx dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/goldendict/+bug/1927552/+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 1926254] Please test proposed package
Hello Matthew, or anyone else affected, Accepted openssl into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssl/1.1.1f- 1ubuntu4.4 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- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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: openssl (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1926254 Title: x509 Certificate verification fails when basicConstraints=CA:FALSE,pathlen:0 on self-signed leaf certs Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Focal: Fix Committed Status in openssl source package in Groovy: Fix Committed Status in openssl source package in Hirsute: Fix Released Bug description: [Impact] In openssl 1.1.1f, the below commit was merged: commit ba4356ae4002a04e28642da60c551877eea804f7 Author: Bernd Edlinger Date: Sat Jan 4 15:54:53 2020 +0100 Subject: Fix error handling in x509v3_cache_extensions and related functions Link: https://github.com/openssl/openssl/commit/ba4356ae4002a04e28642da60c551877eea804f7 This introduced a regression which caused certificate validation to fail when certificates violate RFC 5280 [1], namely, when a certificate has "basicConstraints=CA:FALSE,pathlen:0". This combination is commonly seen by self-signed leaf certificates with an intermediate CA before the root CA. Because of this, openssl 1.1.1f rejects these certificates and they cannot be used in the system certificate store, and ssl connections fail when you try to use them to connect to a ssl endpoint. The error you see when you try verify is: $ openssl verify -CAfile CA/rootCA_cert.pem -untrusted CA/subCA_cert.pem user1_cert.pem error 20 at 0 depth lookup: unable to get local issuer certificate error user1_cert.pem: verification failed The exact same certificates work fine on Xenial, Bionic and Hirsute. [1] https://tools.ietf.org/html/rfc5280.html [Testcase] We will create our own root CA, intermediate CA and leaf server certificate. Create necessary directories: $ mkdir reproducer $ cd reproducer $ mkdir CA Write openssl configuration files to disk for each CA and cert: $ cat << EOF >> rootCA.cnf [ req ] prompt = no distinguished_name = req_distinguished_name x509_extensions = usr_cert [ req_distinguished_name ] C = DE O = Test Org CN = Test RSA PSS Root-CA [ usr_cert ] basicConstraints= critical,CA:TRUE keyUsage= critical,keyCertSign,cRLSign subjectKeyIdentifier= hash authorityKeyIdentifier = keyid:always EOF $ cat << EOF >> subCA.cnf [ req ] prompt = no distinguished_name = req_distinguished_name x509_extensions = usr_cert [ req_distinguished_name ] C = DE O = Test Org CN = Test RSA PSS Sub-CA [ usr_cert ] basicConstraints= critical,CA:TRUE,pathlen:0 keyUsage= critical,keyCertSign,cRLSign subjectKeyIdentifier= hash authorityKeyIdentifier = keyid:always EOF $ cat << EOF >> user.cnf [ req ] prompt = no distinguished_name = req_distinguished_name x509_extensions = usr_cert [ req_distinguished_name ] C = DE O = Test Org CN = Test User [ usr_cert ] basicConstraints= critical,CA:FALSE,pathlen:0 keyUsage= critical,digitalSignature,keyAgreement extendedKeyUsage= clientAuth,serverAuth subjectKeyIdentifier= hash authorityKeyIdentifier = keyid:always EOF Then generate the necessary RSA keys and form certificates: $ openssl genpkey -algorithm RSA-PSS -out rootCA_key.pem -pkeyopt rsa_keygen_bits:2048 $ openssl req -config rootCA.cnf -set_serial 01 -new -batch -sha256 -nodes -
[Touch-packages] [Bug 1927161] Please test proposed package
Hello Dan, or anyone else affected, Accepted openssl into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssl/1.1.1f- 1ubuntu4.4 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- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1927161 Title: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one Status in openssl package in Ubuntu: In Progress Status in openssl source package in Groovy: Fix Committed Status in openssl source package in Hirsute: Fix Committed Status in openssl source package in Impish: In Progress Bug description: [impact] openssl doesn't build source properly because of a badly-constructed patch [test case] $ pull-lp-source openssl groovy ... $ cd openssl-1.1.1f/ $ quilt pop -a ... $ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1f-1ubuntu4.3 dpkg-buildpackage: info: source distribution groovy-security dpkg-buildpackage: info: source changed by Marc Deslauriers dpkg-source --before-build . dpkg-source: warning: can't parse dependency perl:native dpkg-source: error: diff 'openssl-1.1.1f/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned exit status 25 Test builds are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1927161-test [regression potential] any regression would likely cause a failed build or would affect the functionality that patch pr12272 was added for, which is adding support for Intel CET [scope] this is needed only for g and later this is caused by the bad patch 'pr12272.patch' which is only included in g/h/i, so this does not apply to f or earlier [other info] note that if the patches are applied, this bug is bypassed; i.e. if 'quilt pop -a' is removed from the test case above, the bug doesn't reproduce. this is only a problem when the patches aren't already applied and dpkg-buildpackage needs to call dpkg-source to apply the patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+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 1916651] Re: asks about irc user home directory during upgrade
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: base-passwd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-passwd in Ubuntu. https://bugs.launchpad.net/bugs/1916651 Title: asks about irc user home directory during upgrade Status in base-passwd package in Ubuntu: Confirmed Bug description: Upgrading from groovy to hirsuite, base-passwd asks if the `irc` user's home directory should be moved from `/var/run/ircd` to `/run/ircd`. Having no IRC server installed makes this very confusing, but appears harmless (https://askubuntu.com/questions/876975/user-irc-inside-of-default- ubuntu-16-04-server). Possibly caused by https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=946884, but can this not prompt the user for a decision? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: base-passwd 3.5.49 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Feb 23 12:02:59 2021 InstallationDate: Installed on 2019-08-17 (556 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RebootRequiredPkgs: libc6 libc6 libssl1.1 libssl1.1 SourcePackage: base-passwd UpgradeStatus: Upgraded to hirsute on 2021-02-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/1916651/+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 1926254] Please test proposed package
Hello Matthew, or anyone else affected, Accepted openssl into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssl/1.1.1f- 1ubuntu2.4 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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1926254 Title: x509 Certificate verification fails when basicConstraints=CA:FALSE,pathlen:0 on self-signed leaf certs Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Focal: Fix Committed Status in openssl source package in Groovy: Fix Committed Status in openssl source package in Hirsute: Fix Released Bug description: [Impact] In openssl 1.1.1f, the below commit was merged: commit ba4356ae4002a04e28642da60c551877eea804f7 Author: Bernd Edlinger Date: Sat Jan 4 15:54:53 2020 +0100 Subject: Fix error handling in x509v3_cache_extensions and related functions Link: https://github.com/openssl/openssl/commit/ba4356ae4002a04e28642da60c551877eea804f7 This introduced a regression which caused certificate validation to fail when certificates violate RFC 5280 [1], namely, when a certificate has "basicConstraints=CA:FALSE,pathlen:0". This combination is commonly seen by self-signed leaf certificates with an intermediate CA before the root CA. Because of this, openssl 1.1.1f rejects these certificates and they cannot be used in the system certificate store, and ssl connections fail when you try to use them to connect to a ssl endpoint. The error you see when you try verify is: $ openssl verify -CAfile CA/rootCA_cert.pem -untrusted CA/subCA_cert.pem user1_cert.pem error 20 at 0 depth lookup: unable to get local issuer certificate error user1_cert.pem: verification failed The exact same certificates work fine on Xenial, Bionic and Hirsute. [1] https://tools.ietf.org/html/rfc5280.html [Testcase] We will create our own root CA, intermediate CA and leaf server certificate. Create necessary directories: $ mkdir reproducer $ cd reproducer $ mkdir CA Write openssl configuration files to disk for each CA and cert: $ cat << EOF >> rootCA.cnf [ req ] prompt = no distinguished_name = req_distinguished_name x509_extensions = usr_cert [ req_distinguished_name ] C = DE O = Test Org CN = Test RSA PSS Root-CA [ usr_cert ] basicConstraints= critical,CA:TRUE keyUsage= critical,keyCertSign,cRLSign subjectKeyIdentifier= hash authorityKeyIdentifier = keyid:always EOF $ cat << EOF >> subCA.cnf [ req ] prompt = no distinguished_name = req_distinguished_name x509_extensions = usr_cert [ req_distinguished_name ] C = DE O = Test Org CN = Test RSA PSS Sub-CA [ usr_cert ] basicConstraints= critical,CA:TRUE,pathlen:0 keyUsage= critical,keyCertSign,cRLSign subjectKeyIdentifier= hash authorityKeyIdentifier = keyid:always EOF $ cat << EOF >> user.cnf [ req ] prompt = no distinguished_name = req_distinguished_name x509_extensions = usr_cert [ req_distinguished_name ] C = DE O = Test Org CN = Test User [ usr_cert ] basicConstraints= critical,CA:FALSE,pathlen:0 keyUsage= critical,digitalSignature,keyAgreement extendedKeyUsage= clientAuth,serverAuth subjectKeyIdentifier= hash authorityKeyIdentifier = keyid:always EOF Then generate the necessary RSA keys and form certificates: $ openssl genpkey -algorithm RSA-PSS -out rootCA_key.pem -pkeyopt rsa_keygen_bits:2048 $ openssl req -config rootCA.cnf -set_serial 01 -new -batch -sha256 -nodes -x509 -days 9125 -out CA/rootCA_cert.pem -key rootCA_key.pem -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 $ openssl
[Touch-packages] [Bug 1927161] Re: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one
Hello Dan, or anyone else affected, Accepted openssl into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssl/1.1.1j- 1ubuntu3.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- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. 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: openssl (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-hirsute ** Changed in: openssl (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1927161 Title: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one Status in openssl package in Ubuntu: In Progress Status in openssl source package in Groovy: Fix Committed Status in openssl source package in Hirsute: Fix Committed Status in openssl source package in Impish: In Progress Bug description: [impact] openssl doesn't build source properly because of a badly-constructed patch [test case] $ pull-lp-source openssl groovy ... $ cd openssl-1.1.1f/ $ quilt pop -a ... $ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1f-1ubuntu4.3 dpkg-buildpackage: info: source distribution groovy-security dpkg-buildpackage: info: source changed by Marc Deslauriers dpkg-source --before-build . dpkg-source: warning: can't parse dependency perl:native dpkg-source: error: diff 'openssl-1.1.1f/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned exit status 25 Test builds are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1927161-test [regression potential] any regression would likely cause a failed build or would affect the functionality that patch pr12272 was added for, which is adding support for Intel CET [scope] this is needed only for g and later this is caused by the bad patch 'pr12272.patch' which is only included in g/h/i, so this does not apply to f or earlier [other info] note that if the patches are applied, this bug is bypassed; i.e. if 'quilt pop -a' is removed from the test case above, the bug doesn't reproduce. this is only a problem when the patches aren't already applied and dpkg-buildpackage needs to call dpkg-source to apply the patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+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 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2
This bug was fixed in the package livecd-rootfs - 2.721 --- livecd-rootfs (2.721) impish; urgency=medium [ Dimitri John Ledkov ] * 999-cpc-fixes: enable more code on grub2 armhf & arm64 (LP: #1925780) * Add support for generic preinstalled images. LP: #1923832 * Change iptables calls, to query rules and quickly check that connectivity works after transparent proxy has been installed. LP: #1917920 * magic-proxy: replace http.client with urllib calls * buildd: Re-enable merged /usr by default, as it is now required [ Michael Hudson-Doyle ] * remove the workaround for bug #1893818 [ Łukasz 'sil2100' Zemczak ] * Start using the ubuntu-server-raspi seeds for preinstalled raspi server images, similarly to how it's done for desktop-preinstalled images. * Drop the unused imx6 support. -- Dimitri John Ledkov Wed, 05 May 2021 19:08:21 +0100 ** Changed in: livecd-rootfs (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 Status in launchpad-buildd: New Status in iptables package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Fix Released Status in lxd package in Ubuntu: New Bug description: when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic proxy stopped working in livecd-rootfs. It does very simple thing: iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 inside hirsute lxd container, with quite high privileges, in a bionic VM, running 4.15 kernel. With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound connectivity the very first http networking command after the above call would just hang indefinitely. However, if one does this instead: iptables -vv -t nat -S iptables-legacy -vv -t nat -S iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 somehow magically everything starts to work fine. weird. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+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 1927724] Re: package base-passwd 3.5.49 failed to install/upgrade: installed base-passwd package post-installation script subprocess was killed by signal (Aborted), core dumped
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-passwd in Ubuntu. https://bugs.launchpad.net/bugs/1927724 Title: package base-passwd 3.5.49 failed to install/upgrade: installed base- passwd package post-installation script subprocess was killed by signal (Aborted), core dumped Status in base-passwd package in Ubuntu: New Bug description: failed on installation ProblemType: Package DistroRelease: Ubuntu 21.04 Package: base-passwd 3.5.49 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri May 7 03:51:43 2021 ErrorMessage: installed base-passwd package post-installation script subprocess was killed by signal (Aborted), core dumped InstallationDate: Installed on 2020-06-30 (311 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.9, Python 3.9.4, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SourcePackage: base-passwd Title: package base-passwd 3.5.49 failed to install/upgrade: installed base-passwd package post-installation script subprocess was killed by signal (Aborted), core dumped UpgradeStatus: Upgraded to hirsute on 2021-05-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/1927724/+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 1926998] Re: package libpam-systemd:i386 237-3ubuntu10.46 failed to install/upgrade: installed libpam-systemd:i386 package post-installation script subprocess returned error exit
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1926998 Title: package libpam-systemd:i386 237-3ubuntu10.46 failed to install/upgrade: installed libpam-systemd:i386 package post- installation script subprocess returned error exit status 128 Status in systemd package in Ubuntu: New Bug description: package libpam-systemd:i386 237-3ubuntu10.46 failed to install/upgrade: installed libpam-systemd:i386 package post- installation script subprocess returned error exit status 128 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpam-systemd:i386 237-3ubuntu10.46 ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18 Uname: Linux 4.15.0-142-generic i686 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: i386 Date: Tue May 4 00:13:30 2021 ErrorMessage: installed libpam-systemd:i386 package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2021-05-03 (0 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.13 SourcePackage: systemd Title: package libpam-systemd:i386 237-3ubuntu10.46 failed to install/upgrade: installed libpam-systemd:i386 package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926998/+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 1926998] Re: package libpam-systemd:i386 237-3ubuntu10.46 failed to install/upgrade: installed libpam-systemd:i386 package post-installation script subprocess returned error exit
** Tags removed: need-duplicate-check -- 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/1926998 Title: package libpam-systemd:i386 237-3ubuntu10.46 failed to install/upgrade: installed libpam-systemd:i386 package post- installation script subprocess returned error exit status 128 Status in systemd package in Ubuntu: New Bug description: package libpam-systemd:i386 237-3ubuntu10.46 failed to install/upgrade: installed libpam-systemd:i386 package post- installation script subprocess returned error exit status 128 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpam-systemd:i386 237-3ubuntu10.46 ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18 Uname: Linux 4.15.0-142-generic i686 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: i386 Date: Tue May 4 00:13:30 2021 ErrorMessage: installed libpam-systemd:i386 package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2021-05-03 (0 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.13 SourcePackage: systemd Title: package libpam-systemd:i386 237-3ubuntu10.46 failed to install/upgrade: installed libpam-systemd:i386 package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926998/+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]
After investigating this, the root cause of the timeouts is caused by GDB using the wrong type of breakpoint (between a 4 bytes ARM breakpoint and a 2 bytes thumb breakpoint), which causes some unexpected results. The reason why this is happening is a bit more complex though. GDB has a couple mechanisms for tracking loading/unloading of shared libraries in dynamically-linked binaries. Via _dl_debug_state and r_brk and via stap probes. Up until Ubuntu 18.04 (glibc 2.27), GDB could not use the stap probes mechanism because it ran into a bug when parsing stap expression, thus failing the check and falling back to using the old _dl_debug_state and r_brk mechanism. The _dl_debug_state/r_brk mechanism works because we have an entry for _dl_debug_state in the .dynsym section of ld.so. Even though ld.so is completely stripped of mapping symbols (another way to tell arm/thumb modes apart), which are only available via the debug symbols file, GDB can still tell _dl_debug_state is arm or thumb mode because the ELF symbol carries a flag indicating so. That's why this fallback mechanism works. On Ubuntu 20.04, running glibc 2.31, GDB no longer runs into problems with stap probes. Thus GDB decides to use this mechanism instead of the old _dl_debug_state/r_brk one. Both mechanisms function by having GDB insert breakpoints at specific location so shared library events can be tracked. But in the stap probes case there are no real symbols. What we have is metadata that contains the name of the probe and its address. This address falls within a particular function. For example, init_start and init_complete are probe points that fall within dl_main. The probe points do not seem to carry any information about whether we have arm or thumb mode. As before, the mapping symbols should tell us what the mode is, but ld.so is stripped and doesn't carry those. But GDB could look at the ELF symbol of the function the probe is sitting at, except that these symbols (not considered special in any way) have been stripped as well. So the arm/thumb information is completely gone and GDB can no longer make the correct decision. So GDB defaults to assuming arm mode for the breakpoint to use, which is obviously wrong for thumb code. There are two possible solutions: 1 - Fallback to using _dl_debug_state/r_brk for armhf in GDB. This is considered bad by GDB's maintainers, because it means using an outdated mechanism instead of better interfaces. 2 - Don't strip glibc/ld.so function symbols that have stap probes installed in them. Right now, these are the functions that contain probes and that GDB wants to breakpoint in a special way: _dl_main, _dl_map_object_from_fd, lose, dl_open_worker and _dl_close_worker -- 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: Confirmed Status in gdb source package in Impish: Confirmed Bug description: 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 1925379] Re: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4
The gtk3 packages from this ppa also fix this bug on 21.04 https://github.com/flutter/flutter/issues/76383, thank you! ** Bug watch added: github.com/flutter/flutter/issues #76383 https://github.com/flutter/flutter/issues/76383 -- 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/1925379 Title: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4 Status in gtk+3.0 package in Ubuntu: Fix Committed Status in libreoffice package in Ubuntu: Confirmed Bug description: I just did a fresh install of Ubuntu 21.04 (smooth as silk), but then discovered that Auto-Correct in LibreOffice does not work. Yesterday, when I was still running 20.04, Auto-Correct worked fine -- same LibreOffice version, same LibreOffice profile, same LibreOffice document, and no changes on my part to my LibreOffice settings since I installed Ubuntu 21.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1925379/+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 1926093] Re: package gconf-service 3.2.6-6ubuntu1 failed to install/upgrade: problemas de dependência - deixando desconfigurado
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1926093 Title: package gconf-service 3.2.6-6ubuntu1 failed to install/upgrade: problemas de dependência - deixando desconfigurado Status in gconf package in Ubuntu: New Bug description: Toda vez que eu abro o meu Ubuntu aparece que aconteceu um erro, não sei o pq ProblemType: Package DistroRelease: Ubuntu 20.04 Package: gconf-service 3.2.6-6ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 AptOrdering: libcaca0:i386: Install libcaca0:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 20 18:09:53 2021 ErrorMessage: problemas de dependência - deixando desconfigurado InstallationDate: Installed on 2021-04-17 (7 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: gconf Title: package gconf-service 3.2.6-6ubuntu1 failed to install/upgrade: problemas de dependência - deixando desconfigurado UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1926093/+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 1923564] Re: BlueZ 5.58 release
This bug was fixed in the package bluez - 5.58-0ubuntu1 --- bluez (5.58-0ubuntu1) impish; urgency=medium * New upstream release 5.58 (LP: #1923564): - Fix issue with usage of deprecated GLib functions. * New upstream release 5.57: - Fix issue with handling GATT notification PDU parsing. - Fix issue with registering DIS without a valid source. - Fix issue with removing remote SEPs when loading from cache. * Drop hog-lib-Fix-crash-when-receiving-UHID_GET_REPORT.patch because it is upstreamed in version 5.57. * Drop a couple of nonexistent symbols (in sixaxis.so) from libbluetooth3.symbols to quieten lintian. -- Daniel van Vugt Tue, 04 May 2021 15:23:46 +0800 ** Changed in: bluez (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1923564 Title: BlueZ 5.58 release Status in bluez package in Ubuntu: Fix Released Bug description: BlueZ 5.58 has been released. We should look at it for the 21.10 cycle... http://www.bluez.org/release-of-bluez-5-58-and-5-57/ https://mirrors.edge.kernel.org/pub/linux/bluetooth/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1923564/+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 1783881] Re: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes
Found on focal/azure-5.8 5.8.0-1031.33~20.04.1 ** Tags added: sru-20210412 -- 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/1783881 Title: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in systemd source package in Xenial: New Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in systemd source package in Bionic: New Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+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 1926796] Re: [SRU] Enable support for Xena Cloud Archive
Verified successfully on focal-proposed: root@f1:~# apt policy software-properties-common software-properties-common: Installed: 0.98.9.5 Candidate: 0.98.9.5 Version table: *** 0.98.9.5 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 0.98.9.4 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 0.98.9.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 0.98.9 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages root@f1:~# sudo add-apt-repository cloud-archive:xena --yes Reading package lists... Building dependency tree... Reading state information... The following package was automatically installed and is no longer required: libfreetype6 Use 'sudo apt autoremove' to remove it. The following NEW packages will be installed: ubuntu-cloud-keyring 0 upgraded, 1 newly installed, 0 to remove and 21 not upgraded. Need to get 5688 B of archives. After this operation, 22.5 kB of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 ubuntu-cloud-keyring all 2020.02.11.4 [5688 B] Fetched 5688 B in 0s (25.8 kB/s) Selecting previously unselected package ubuntu-cloud-keyring. (Reading database ... 31590 files and directories currently installed.) Preparing to unpack .../ubuntu-cloud-keyring_2020.02.11.4_all.deb ... Unpacking ubuntu-cloud-keyring (2020.02.11.4) ... Setting up ubuntu-cloud-keyring (2020.02.11.4) ... Hit:1 http://security.ubuntu.com/ubuntu focal-security InRelease Hit:2 http://archive.ubuntu.com/ubuntu focal InRelease Get:3 http://ubuntu-cloud.archive.canonical.com/ubuntu focal-updates/xena InRelease [7616 B] Get:4 http://ubuntu-cloud.archive.canonical.com/ubuntu focal-updates/xena/main amd64 Packages [155 kB] Hit:5 http://archive.ubuntu.com/ubuntu focal-updates InRelease Hit:6 http://archive.ubuntu.com/ubuntu focal-proposed InRelease Hit:7 http://archive.ubuntu.com/ubuntu focal-backports InRelease Fetched 162 kB in 1s (125 kB/s) Reading package lists... Done root@f1:~# sudo add-apt-repository cloud-archive:xena-proposed --yes Reading package lists... Building dependency tree... Reading state information... ubuntu-cloud-keyring is already the newest version (2020.02.11.4). The following package was automatically installed and is no longer required: libfreetype6 Use 'sudo apt autoremove' to remove it. 0 upgraded, 0 newly installed, 0 to remove and 28 not upgraded. Get:1 http://ubuntu-cloud.archive.canonical.com/ubuntu focal-proposed/xena InRelease [7618 B] Hit:2 http://ubuntu-cloud.archive.canonical.com/ubuntu focal-updates/xena InRelease Get:3 http://ubuntu-cloud.archive.canonical.com/ubuntu focal-proposed/xena/main amd64 Packages [155 kB] Hit:4 http://archive.ubuntu.com/ubuntu focal InRelease Get:5 http://security.ubuntu.com/ubuntu focal-security InRelease [109 kB] Hit:6 http://archive.ubuntu.com/ubuntu focal-updates InRelease Hit:7 http://archive.ubuntu.com/ubuntu focal-proposed InRelease Hit:8 http://archive.ubuntu.com/ubuntu focal-backports InRelease Fetched 272 kB in 1s (259 kB/s) Reading package lists... Done root@f1:~# apt policy python3-openstackclient python3-openstackclient: Installed: (none) Candidate: 5.5.0-0ubuntu1~cloud0 Version table: 5.5.0-0ubuntu1~cloud0 500 500 http://ubuntu-cloud.archive.canonical.com/ubuntu focal-proposed/xena/main amd64 Packages 500 http://ubuntu-cloud.archive.canonical.com/ubuntu focal-updates/xena/main amd64 Packages 5.2.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages root@f1:~# sudo apt install --yes python3-openstackclient ... root@f1:~# apt policy python3-openstackclient python3-openstackclient: Installed: 5.5.0-0ubuntu1~cloud0 Candidate: 5.5.0-0ubuntu1~cloud0 Version table: *** 5.5.0-0ubuntu1~cloud0 500 500 http://ubuntu-cloud.archive.canonical.com/ubuntu focal-proposed/xena/main amd64 Packages 500 http://ubuntu-cloud.archive.canonical.com/ubuntu focal-updates/xena/main amd64 Packages 100 /var/lib/dpkg/status 5.2.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages root@f1:~# openstack --version openstack 5.5.0 ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1926796 Title: [SRU] Enable support for Xena Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-proper
[Touch-packages] [Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall
Nice day, 2 slapd malfunction in the same time, maybe du to network
connectivity issue.
I have the backtrace for one of them.
Please the the attachment.
Thanks.
** Attachment added: "slapd backtrace during sched_yield loop"
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+attachment/5495540/+files/2021070_backtrace_front02_..txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1926265
Title:
slapd enter in infinite loop on sched_yield syscall
Status in openldap package in Ubuntu:
Incomplete
Bug description:
On a production server, sometimes slapd become unbresponsive, some threads
loops in sched_yield syscall and consumme all CPU.
To recover, slapd needs to restart.
No related information is reported in log file.
All same issues in OpenLDAP upstream project are old and fixed.
So maybe this issue affects only Ubuntu package.
It occurs randomly, so I have no steps to reproduce.
OS : Bionic
Openldap version:
libldap-2.4-2:amd642.4.45+dfsg-1ubuntu1.10
libldap-common 2.4.45+dfsg-1ubuntu1.10
slapd 2.4.45+dfsg-1ubuntu1.10
Modules loaded:
olcModuleLoad: {0}back_bdb
olcModuleLoad: {1}syncprov
olcModuleLoad: {2}back_monitor
olcModuleLoad: {3}memberof.la
olcModuleLoad: {4}refint.la
olcModuleLoad: {5}rwm
olcModuleload: {6}back_ldap
Backend is BDB. slapd run in (single) master - (multi) slave mode.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+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
** Changed in: gdb Status: Confirmed => Incomplete -- 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: Confirmed Status in gdb source package in Impish: Confirmed Bug description: 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 1926843] Re: online accounts integration with fb isn't working
** Changed in: gnome-online-accounts (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1926843 Title: online accounts integration with fb isn't working Status in gnome-online-accounts package in Ubuntu: Fix Committed Bug description: Hi i tryed to use gnome-control-center online-accounts to make easy like windows 10 to login to email or add other login so its more easy with ID to use pincode or other ID fingerprint and other. But its look its much issue compared with windows 10 with thunderbird, firefox, and other program. Worst is facebook only little windows with issue with login? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-online-accounts 3.38.1-1ubuntu1 Uname: Linux 5.12.0-051200-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 1 19:38:03 2021 InstallationDate: Installed on 2019-05-07 (725 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+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 1926796] Re: [SRU] Enable support for Xena Cloud Archive
Hello Corey, or anyone else affected, Accepted software-properties into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/software- properties/0.98.9.5 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: software-properties (Ubuntu Focal) Status: Triaged => 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 software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1926796 Title: [SRU] Enable support for Xena Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Focal: Fix Committed Status in software-properties source package in Impish: Fix Released Bug description: Please add support for: cloud-archive:xena cloud-archive:xena-proposed This will also need to be SRU'd back to focal. [Impact] End users have to manually enable the xena cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:xena sudo add-apt-repository cloud-archive:xena-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1926796/+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 1927705] Re: package libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-5ubuntu0.2 failed to install/upgrade: triggers looping, abandoned
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1927705 Title: package libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-5ubuntu0.2 failed to install/upgrade: triggers looping, abandoned Status in gdk-pixbuf package in Ubuntu: New Bug description: upgrade from 20.04 to 20.10 ProblemType: Package DistroRelease: Ubuntu 20.10 Package: libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-5ubuntu0.2 ProcVersionSignature: Ubuntu 5.6.0-1055.59-oem 5.6.19 Uname: Linux 5.6.0-1055-oem x86_64 ApportVersion: 2.20.11-0ubuntu50.6 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri May 7 10:11:41 2021 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2021-04-22 (14 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.3 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-5ubuntu0.2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1927705/+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 1927705] [NEW] package libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-5ubuntu0.2 failed to install/upgrade: triggers looping, abandoned
Public bug reported: upgrade from 20.04 to 20.10 ProblemType: Package DistroRelease: Ubuntu 20.10 Package: libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-5ubuntu0.2 ProcVersionSignature: Ubuntu 5.6.0-1055.59-oem 5.6.19 Uname: Linux 5.6.0-1055-oem x86_64 ApportVersion: 2.20.11-0ubuntu50.6 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri May 7 10:11:41 2021 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2021-04-22 (14 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.3 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-5ubuntu0.2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdk-pixbuf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1927705 Title: package libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-5ubuntu0.2 failed to install/upgrade: triggers looping, abandoned Status in gdk-pixbuf package in Ubuntu: New Bug description: upgrade from 20.04 to 20.10 ProblemType: Package DistroRelease: Ubuntu 20.10 Package: libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-5ubuntu0.2 ProcVersionSignature: Ubuntu 5.6.0-1055.59-oem 5.6.19 Uname: Linux 5.6.0-1055-oem x86_64 ApportVersion: 2.20.11-0ubuntu50.6 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri May 7 10:11:41 2021 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2021-04-22 (14 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.3 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-5ubuntu0.2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1927705/+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 1921655] Re: lightdm-guest-session ICEauthority error
This bug was fixed in the package lightdm - 1.30.0-0ubuntu4~20.10.1
---
lightdm (1.30.0-0ubuntu4~20.10.1) groovy; urgency=medium
* debian/patches/fix-guest-session-ICEauthority-error.patch:
- Fixes AppArmor issue which prevented access to the guest session
feature in e.g. MATE (LP: #1921655). Thanks to Jonas Wiegert for
the solution!
* debian/patches/dont-turn-format-warnings-into-errors.patch:
- Works around FTBFS on s390x with gcc versions higher than gcc-9.
-- Gunnar Hjalmarsson Mon, 12 Apr 2021 19:56:00
+0200
** Changed in: lightdm (Ubuntu Groovy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1921655
Title:
lightdm-guest-session ICEauthority error
Status in Ubuntu MATE:
New
Status in lightdm package in Ubuntu:
Fix Released
Status in lightdm source package in Focal:
Fix Committed
Status in lightdm source package in Groovy:
Fix Released
Status in lightdm source package in Hirsute:
Fix Released
Bug description:
[Impact]
If you enable the guest session feature on e.g. Ubuntu MATE, you are
met by an error message when trying to enter a guest session:
"Could not update file ICEauthority file /run/user/XXX/ICEauthority"
Even if it's not always a fatal error (the login may succeed after a
few minutes), the user experience is really bad, and you are inclined
to conclude that you are completely blocked from using the feature.
The proposed fix adds a rule to the lightdm-guest-session AppArmor
profile and prevents the error from happening.
[Test Plan]
On an updated Ubuntu MATE installation:
* Enable guest session
sudo sh -c 'printf "[Seat:*]\nallow-guest=true\n"
>/etc/lightdm/lightdm.conf.d/50-enable-guest.conf'
* Install lightdm from {focal,groovy}-proposed
* Reboot
You should now be able to enter a guest session without being stopped
by the ICEauthority error.
[Where problems could occur]
This one-liner is a harmless change.
The guest session is run in an unconfined mode since Ubuntu 16.10.
That's why the feature is disabled by default.
So if the additional rule would be wrong somehow (which I have no
reason to believe), it wouldn't break the AppArmor security layer for
the simple reason that it's already broken to begin with.
[Original description]
Hello I ran into trouble to start the lightdm-guest-session in linux
mint (cinnamon).
## How to reproduce:
- boot linux mint (20.02) or ubuntu mate (20.04) I haven't tested other
distros but I think others are also affected.
- enable guest user session
- try to login as guest user
## Error logs:
### Error Message:
` Could not update file ICEauthority file /run/user/XXX/ICEauthority`
### aa-notify:
```
Profile: /usr/lib/lightdm/lightdm-guest-session
Operation: open
Name: /proc/8125/uid_map
Denied: w
Logfile: /var/log/kern.log
Profile: /usr/lib/lightdm/lightdm-guest-session
Operation: open
Name: /proc/8125/setgroups
Denied: w
Logfile: /var/log/kern.log
Profile: /usr/lib/lightdm/lightdm-guest-session
Operation: open
Name: /proc/8125/gid_map
Denied: w
Logfile: /var/log/kern.log
Profile: /usr/lib/lightdm/lightdm-guest-session
Operation: open
Name: /proc/8624/fd/
Denied: r
Logfile: /var/log/kern.log
```
### dmesg:
```
[ 218.831289] audit: type=1400 audit(1616864450.287:76): apparmor="DENIED"
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/run/systemd/journal/dev-log" pid=3916 comm="cinnamon-sessio"
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
[ 1157.263045] audit: type=1400 audit(1616865388.720:1084): apparmor="DENIED"
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/proc/9899/fd/" pid=9899 comm="gpg-agent" requested_mask="r"
denied_mask="r" fsuid=999 #ouid=0
[ 1157.899223] audit: type=1400 audit(1616865389.356:1085): apparmor="DENIED"
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/proc/1/cgroup" pid=9840 comm="cinnamon-sessio" requested_mask="r"
denied_mask="r" fsuid=999 ouid=0
[ 1157.899445] audit: type=1400 audit(1616865389.360:1086): apparmor="DENIED"
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/run/systemd/journal/dev-log" pid=9840 comm="cinnamon-sessio"
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
[ 1157.903410] audit: type=1400 audit(1616865389.364:1087): apparmor="DENIED"
operation="link" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/run/user/999/ICEauthority-l" pid=9840 comm="cinnamon-sessio"
requested_mask="l" denied_mask="l" fsuid=999 ouid=999
target="/run/user/999/ICEauthority-c"
```
## Solutions:
### bad but common work around
Solutions I found in different forums were to move lightdm-guest-session into
complain mode like th
[Touch-packages] [Bug 1921655] Update Released
The verification of the Stable Release Update for lightdm 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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1921655
Title:
lightdm-guest-session ICEauthority error
Status in Ubuntu MATE:
New
Status in lightdm package in Ubuntu:
Fix Released
Status in lightdm source package in Focal:
Fix Committed
Status in lightdm source package in Groovy:
Fix Released
Status in lightdm source package in Hirsute:
Fix Released
Bug description:
[Impact]
If you enable the guest session feature on e.g. Ubuntu MATE, you are
met by an error message when trying to enter a guest session:
"Could not update file ICEauthority file /run/user/XXX/ICEauthority"
Even if it's not always a fatal error (the login may succeed after a
few minutes), the user experience is really bad, and you are inclined
to conclude that you are completely blocked from using the feature.
The proposed fix adds a rule to the lightdm-guest-session AppArmor
profile and prevents the error from happening.
[Test Plan]
On an updated Ubuntu MATE installation:
* Enable guest session
sudo sh -c 'printf "[Seat:*]\nallow-guest=true\n"
>/etc/lightdm/lightdm.conf.d/50-enable-guest.conf'
* Install lightdm from {focal,groovy}-proposed
* Reboot
You should now be able to enter a guest session without being stopped
by the ICEauthority error.
[Where problems could occur]
This one-liner is a harmless change.
The guest session is run in an unconfined mode since Ubuntu 16.10.
That's why the feature is disabled by default.
So if the additional rule would be wrong somehow (which I have no
reason to believe), it wouldn't break the AppArmor security layer for
the simple reason that it's already broken to begin with.
[Original description]
Hello I ran into trouble to start the lightdm-guest-session in linux
mint (cinnamon).
## How to reproduce:
- boot linux mint (20.02) or ubuntu mate (20.04) I haven't tested other
distros but I think others are also affected.
- enable guest user session
- try to login as guest user
## Error logs:
### Error Message:
` Could not update file ICEauthority file /run/user/XXX/ICEauthority`
### aa-notify:
```
Profile: /usr/lib/lightdm/lightdm-guest-session
Operation: open
Name: /proc/8125/uid_map
Denied: w
Logfile: /var/log/kern.log
Profile: /usr/lib/lightdm/lightdm-guest-session
Operation: open
Name: /proc/8125/setgroups
Denied: w
Logfile: /var/log/kern.log
Profile: /usr/lib/lightdm/lightdm-guest-session
Operation: open
Name: /proc/8125/gid_map
Denied: w
Logfile: /var/log/kern.log
Profile: /usr/lib/lightdm/lightdm-guest-session
Operation: open
Name: /proc/8624/fd/
Denied: r
Logfile: /var/log/kern.log
```
### dmesg:
```
[ 218.831289] audit: type=1400 audit(1616864450.287:76): apparmor="DENIED"
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/run/systemd/journal/dev-log" pid=3916 comm="cinnamon-sessio"
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
[ 1157.263045] audit: type=1400 audit(1616865388.720:1084): apparmor="DENIED"
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/proc/9899/fd/" pid=9899 comm="gpg-agent" requested_mask="r"
denied_mask="r" fsuid=999 #ouid=0
[ 1157.899223] audit: type=1400 audit(1616865389.356:1085): apparmor="DENIED"
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/proc/1/cgroup" pid=9840 comm="cinnamon-sessio" requested_mask="r"
denied_mask="r" fsuid=999 ouid=0
[ 1157.899445] audit: type=1400 audit(1616865389.360:1086): apparmor="DENIED"
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/run/systemd/journal/dev-log" pid=9840 comm="cinnamon-sessio"
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
[ 1157.903410] audit: type=1400 audit(1616865389.364:1087): apparmor="DENIED"
operation="link" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/run/user/999/ICEauthority-l" pid=9840 comm="cinnamon-sessio"
requested_mask="l" denied_mask="l" fsuid=999 ouid=999
target="/run/user/999/ICEauthority-c"
```
## Solutions:
### bad but common work around
Solutions I found in different forums were to move lightdm-guest-session into
complain mode like this:
`aa-complain /usr/lib/lightdm/lightdm-guest-session`
### maybe better sollution:
My fix would be to add this to `/etc/apparmor.d/lightdm-guest-session`:
```
...
/usr/l
[Touch-packages] [Bug 1920837] Re: apport bugs from official raspi or riscv images are not identified
This bug was fixed in the package apport - 2.20.11-0ubuntu50.6 --- apport (2.20.11-0ubuntu50.6) groovy; urgency=medium * data/general-hooks/ubuntu.py: tag bugs from Raspberry Pi images and RISCV images appropriately. (LP: #1920837) * apport/hookutils.py: spawn pkttyagent so that log files can be gathered as root in a non-graphical environment (LP: #1821415). Thanks to Iain Lane for the patch. * apport/hookutils.py: root access is needed to read the casper-md5check.json file so switch to using that. (LP: #1922937) -- Brian Murray Mon, 26 Apr 2021 12:45:36 -0700 ** Changed in: apport (Ubuntu Groovy) Status: Fix Committed => Fix Released ** Changed in: apport (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1920837 Title: apport bugs from official raspi or riscv images are not identified Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Released Status in apport source package in Groovy: Fix Released Bug description: It would be helpful if bugs reported from images for Raspberry Pi's or RISCV systems were tagged so that one could search for bugs from systems running those images e.g. 'raspi-image'. [Test Case] After installing a preinstalled image of Ubuntu for Raspberry Pi do the following: 1) run 'ubuntu-bug apport' 2) view the bug report and check the Tags field With the current version of apport you will not see the tag 'raspi-image'. With the version of apport in -proposed you will see the tag 'raspi-image'. [Where problems could occur] If the code being added is syntactically incorrect then we'd see a Traceback which would be bad as it could affect all bug / crash reports. [Other Info] Since there aren't any Groovy images for RISC-V there will be nothing to test there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1920837/+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 1925779] Re: [20UHZ5DXUS, ATI R6xx HDMI, Digital Out, HDMI] [Lenovo T14s-AMD] No sound at all when the audio output from HDMI port.
** Tags added: hwe-audio -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1925779 Title: [20UHZ5DXUS, ATI R6xx HDMI, Digital Out, HDMI] [Lenovo T14s-AMD] No sound at all when the audio output from HDMI port. Status in alsa-driver package in Ubuntu: New Bug description: No sound at all when the audio output from HDMI port. [Steps to reproduce] 1. Install the daily build image on Lenovo T14s-AMD 2. Login the system 3. Connect the HDMI port with a Monitor 4. Select the 'Output Device' is HDMI 5. Try to play sound from the monitor [Actual result] No sound at all when the audio output from HDMI port. The internal speaker works normally. [Test image] http://cdimage.ubuntu.com/ubuntu/daily-live/current/hirsute-desktop-amd64.iso [Test Device] https://certification.canonical.com/hardware/202006-27964 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: u 1424 F pulseaudio /dev/snd/controlC1: u 1424 F pulseaudio /dev/snd/controlC0: u 1424 F pulseaudio /dev/snd/pcmC0D0c: u 1424 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 06:18:01 2021 InstallationDate: Installed on 2021-04-23 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: u 1424 F pulseaudio /dev/snd/controlC1: u 1424 F pulseaudio /dev/snd/controlC0: u 1424 F pulseaudio /dev/snd/pcmC0D0c: u 1424 F...m pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [20UHZ5DXUS, ATI R6xx HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2020 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET55T(1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UHZ5DXUS dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvrR1CET55T(1.24):bd09/15/2020:br1.24:efr1.24:svnLENOVO:pn20UHZ5DXUS:pvrThinkPadT14sGen1:rvnLENOVO:rn20UHZ5DXUS:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14s Gen 1 dmi.product.name: 20UHZ5DXUS dmi.product.sku: LENOVO_MT_20UH_BU_Think_FM_ThinkPad T14s Gen 1 dmi.product.version: ThinkPad T14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1925779/+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 1821415] Re: pkexec fails in a non-graphical environment
This bug was fixed in the package apport - 2.20.11-0ubuntu27.17 --- apport (2.20.11-0ubuntu27.17) focal; urgency=medium * data/general-hooks/ubuntu.py: tag bugs from Raspberry Pi images and RISCV images appropriately. (LP: #1920837) * apport/hookutils.py: spawn pkttyagent so that log files can be gathered as root in a non-graphical environment (LP: #1821415). Thanks to Iain Lane for the patch. * apport/hookutils.py: root access is needed to read the casper-md5check.json file so switch to using that. (LP: #1922937) -- Brian Murray Mon, 26 Apr 2021 13:28:49 -0700 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1821415 Title: pkexec fails in a non-graphical environment Status in PolicyKit: New Status in apport package in Ubuntu: Fix Released Status in policykit-1 package in Ubuntu: Won't Fix Status in apport source package in Focal: Fix Released Status in policykit-1 source package in Focal: Won't Fix Status in apport source package in Groovy: Fix Released Status in policykit-1 source package in Groovy: Won't Fix Bug description: [Impact] The plymouth apport source package hooks wants to gather log files as the root user and apport provides a policy kit policy for collecting that information. This works fine in a graphical environment but not in a non-graphical one. [Test Case] 1) ssh into an Ubuntu Desktop install of Ubuntu 20.04 LTS or Ubuntu 20.10 2) sudo touch /var/log/plymouth-debug.log 3) ubuntu@disco:~$ ubuntu-bug plymouth *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. AUTHENTICATING FOR com.ubuntu.apport.root-info === Authentication is required to collect system information for this problem report Authenticating as: Ubuntu (ubuntu) Password: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie AUTHENTICATION FAILED === Error executing command as another user: Not authorized This incident has been reported. With the version of apport from -proposed you will not see the "AUTHENTICATION FAILED" error and the plymouth-debug.log file will be collected. [Where Problems Could Occur] It's possible that the spawned pkttyagent process does not get cleaned up properly and could be left running. When testing the SRU we should confirm it is not still running. To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1821415/+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 1821415] Update Released
The verification of the Stable Release Update for apport 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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1821415 Title: pkexec fails in a non-graphical environment Status in PolicyKit: New Status in apport package in Ubuntu: Fix Released Status in policykit-1 package in Ubuntu: Won't Fix Status in apport source package in Focal: Fix Released Status in policykit-1 source package in Focal: Won't Fix Status in apport source package in Groovy: Fix Released Status in policykit-1 source package in Groovy: Won't Fix Bug description: [Impact] The plymouth apport source package hooks wants to gather log files as the root user and apport provides a policy kit policy for collecting that information. This works fine in a graphical environment but not in a non-graphical one. [Test Case] 1) ssh into an Ubuntu Desktop install of Ubuntu 20.04 LTS or Ubuntu 20.10 2) sudo touch /var/log/plymouth-debug.log 3) ubuntu@disco:~$ ubuntu-bug plymouth *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. AUTHENTICATING FOR com.ubuntu.apport.root-info === Authentication is required to collect system information for this problem report Authenticating as: Ubuntu (ubuntu) Password: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie AUTHENTICATION FAILED === Error executing command as another user: Not authorized This incident has been reported. With the version of apport from -proposed you will not see the "AUTHENTICATION FAILED" error and the plymouth-debug.log file will be collected. [Where Problems Could Occur] It's possible that the spawned pkttyagent process does not get cleaned up properly and could be left running. When testing the SRU we should confirm it is not still running. To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1821415/+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 1922937] Re: reading casper-md5check.json fails
This bug was fixed in the package apport - 2.20.11-0ubuntu27.17 --- apport (2.20.11-0ubuntu27.17) focal; urgency=medium * data/general-hooks/ubuntu.py: tag bugs from Raspberry Pi images and RISCV images appropriately. (LP: #1920837) * apport/hookutils.py: spawn pkttyagent so that log files can be gathered as root in a non-graphical environment (LP: #1821415). Thanks to Iain Lane for the patch. * apport/hookutils.py: root access is needed to read the casper-md5check.json file so switch to using that. (LP: #1922937) -- Brian Murray Mon, 26 Apr 2021 13:28:49 -0700 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1922937 Title: reading casper-md5check.json fails Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Released Status in apport source package in Groovy: Fix Released Status in apport source package in Hirsute: Fix Released Bug description: [Impact] Bugs reported by apport are not including information about the results of the md5 check of the installation media used. Additionally, users are presented with a traceback regarding the ubuntu hook which is used with all bug reports. [Test Case] 1) Boot an Ubuntu 20.04 LTS or Ubuntu 20.10 install 2) Create the file /var/log/installer/casper-md5check.json with mode 0600. 3) Run 'ubuntu-bug coreutils' *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ..ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 84, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 995, in attach_casper_md5check with open(location) as json_file: PermissionError: [Errno 13] Permission denied: '/var/log/installer/casper-md5check.json' [Where problems could occur] We are switching to reading the file with attach_root_command_outputs which is a well tested function in apport so the only problem would be a result of the new code being added. This works well in Hirsute so there is little chance of their being an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1922937/+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 1821415] Re: pkexec fails in a non-graphical environment
This bug was fixed in the package apport - 2.20.11-0ubuntu50.6 --- apport (2.20.11-0ubuntu50.6) groovy; urgency=medium * data/general-hooks/ubuntu.py: tag bugs from Raspberry Pi images and RISCV images appropriately. (LP: #1920837) * apport/hookutils.py: spawn pkttyagent so that log files can be gathered as root in a non-graphical environment (LP: #1821415). Thanks to Iain Lane for the patch. * apport/hookutils.py: root access is needed to read the casper-md5check.json file so switch to using that. (LP: #1922937) -- Brian Murray Mon, 26 Apr 2021 12:45:36 -0700 ** Changed in: apport (Ubuntu Groovy) Status: Fix Committed => Fix Released ** Changed in: apport (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1821415 Title: pkexec fails in a non-graphical environment Status in PolicyKit: New Status in apport package in Ubuntu: Fix Released Status in policykit-1 package in Ubuntu: Won't Fix Status in apport source package in Focal: Fix Released Status in policykit-1 source package in Focal: Won't Fix Status in apport source package in Groovy: Fix Released Status in policykit-1 source package in Groovy: Won't Fix Bug description: [Impact] The plymouth apport source package hooks wants to gather log files as the root user and apport provides a policy kit policy for collecting that information. This works fine in a graphical environment but not in a non-graphical one. [Test Case] 1) ssh into an Ubuntu Desktop install of Ubuntu 20.04 LTS or Ubuntu 20.10 2) sudo touch /var/log/plymouth-debug.log 3) ubuntu@disco:~$ ubuntu-bug plymouth *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. AUTHENTICATING FOR com.ubuntu.apport.root-info === Authentication is required to collect system information for this problem report Authenticating as: Ubuntu (ubuntu) Password: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie AUTHENTICATION FAILED === Error executing command as another user: Not authorized This incident has been reported. With the version of apport from -proposed you will not see the "AUTHENTICATION FAILED" error and the plymouth-debug.log file will be collected. [Where Problems Could Occur] It's possible that the spawned pkttyagent process does not get cleaned up properly and could be left running. When testing the SRU we should confirm it is not still running. To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1821415/+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 1920837] Update Released
The verification of the Stable Release Update for apport 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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1920837 Title: apport bugs from official raspi or riscv images are not identified Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Released Status in apport source package in Groovy: Fix Released Bug description: It would be helpful if bugs reported from images for Raspberry Pi's or RISCV systems were tagged so that one could search for bugs from systems running those images e.g. 'raspi-image'. [Test Case] After installing a preinstalled image of Ubuntu for Raspberry Pi do the following: 1) run 'ubuntu-bug apport' 2) view the bug report and check the Tags field With the current version of apport you will not see the tag 'raspi-image'. With the version of apport in -proposed you will see the tag 'raspi-image'. [Where problems could occur] If the code being added is syntactically incorrect then we'd see a Traceback which would be bad as it could affect all bug / crash reports. [Other Info] Since there aren't any Groovy images for RISC-V there will be nothing to test there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1920837/+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 1922937] Re: reading casper-md5check.json fails
This bug was fixed in the package apport - 2.20.11-0ubuntu50.6 --- apport (2.20.11-0ubuntu50.6) groovy; urgency=medium * data/general-hooks/ubuntu.py: tag bugs from Raspberry Pi images and RISCV images appropriately. (LP: #1920837) * apport/hookutils.py: spawn pkttyagent so that log files can be gathered as root in a non-graphical environment (LP: #1821415). Thanks to Iain Lane for the patch. * apport/hookutils.py: root access is needed to read the casper-md5check.json file so switch to using that. (LP: #1922937) -- Brian Murray Mon, 26 Apr 2021 12:45:36 -0700 ** Changed in: apport (Ubuntu Groovy) Status: Fix Committed => Fix Released ** Changed in: apport (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1922937 Title: reading casper-md5check.json fails Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Released Status in apport source package in Groovy: Fix Released Status in apport source package in Hirsute: Fix Released Bug description: [Impact] Bugs reported by apport are not including information about the results of the md5 check of the installation media used. Additionally, users are presented with a traceback regarding the ubuntu hook which is used with all bug reports. [Test Case] 1) Boot an Ubuntu 20.04 LTS or Ubuntu 20.10 install 2) Create the file /var/log/installer/casper-md5check.json with mode 0600. 3) Run 'ubuntu-bug coreutils' *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ..ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 84, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 995, in attach_casper_md5check with open(location) as json_file: PermissionError: [Errno 13] Permission denied: '/var/log/installer/casper-md5check.json' [Where problems could occur] We are switching to reading the file with attach_root_command_outputs which is a well tested function in apport so the only problem would be a result of the new code being added. This works well in Hirsute so there is little chance of their being an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1922937/+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 1920837] Re: apport bugs from official raspi or riscv images are not identified
This bug was fixed in the package apport - 2.20.11-0ubuntu27.17 --- apport (2.20.11-0ubuntu27.17) focal; urgency=medium * data/general-hooks/ubuntu.py: tag bugs from Raspberry Pi images and RISCV images appropriately. (LP: #1920837) * apport/hookutils.py: spawn pkttyagent so that log files can be gathered as root in a non-graphical environment (LP: #1821415). Thanks to Iain Lane for the patch. * apport/hookutils.py: root access is needed to read the casper-md5check.json file so switch to using that. (LP: #1922937) -- Brian Murray Mon, 26 Apr 2021 13:28:49 -0700 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1920837 Title: apport bugs from official raspi or riscv images are not identified Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Released Status in apport source package in Groovy: Fix Released Bug description: It would be helpful if bugs reported from images for Raspberry Pi's or RISCV systems were tagged so that one could search for bugs from systems running those images e.g. 'raspi-image'. [Test Case] After installing a preinstalled image of Ubuntu for Raspberry Pi do the following: 1) run 'ubuntu-bug apport' 2) view the bug report and check the Tags field With the current version of apport you will not see the tag 'raspi-image'. With the version of apport in -proposed you will see the tag 'raspi-image'. [Where problems could occur] If the code being added is syntactically incorrect then we'd see a Traceback which would be bad as it could affect all bug / crash reports. [Other Info] Since there aren't any Groovy images for RISC-V there will be nothing to test there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1920837/+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 1922937] Update Released
The verification of the Stable Release Update for apport 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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1922937 Title: reading casper-md5check.json fails Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Released Status in apport source package in Groovy: Fix Released Status in apport source package in Hirsute: Fix Released Bug description: [Impact] Bugs reported by apport are not including information about the results of the md5 check of the installation media used. Additionally, users are presented with a traceback regarding the ubuntu hook which is used with all bug reports. [Test Case] 1) Boot an Ubuntu 20.04 LTS or Ubuntu 20.10 install 2) Create the file /var/log/installer/casper-md5check.json with mode 0600. 3) Run 'ubuntu-bug coreutils' *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ..ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 84, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 995, in attach_casper_md5check with open(location) as json_file: PermissionError: [Errno 13] Permission denied: '/var/log/installer/casper-md5check.json' [Where problems could occur] We are switching to reading the file with attach_root_command_outputs which is a well tested function in apport so the only problem would be a result of the new code being added. This works well in Hirsute so there is little chance of their being an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1922937/+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 1923841] Re: [SRU] Increase recording quality
This bug was fixed in the package alsa-utils - 1.2.2-1ubuntu2.1 --- alsa-utils (1.2.2-1ubuntu2.1) focal; urgency=medium * d/p/0013-aplay-try-to-use-16-bit-format-to-increase-capture-q.patch - aplay: try to use 16-bit format to increase capture quality (LP: #1923841) -- Kai-Heng Feng Wed, 14 Apr 2021 21:38:30 +0800 ** Changed in: alsa-utils (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 alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1923841 Title: [SRU] Increase recording quality Status in HWE Next: New Status in alsa-utils package in Ubuntu: Fix Released Status in alsa-utils source package in Focal: Fix Released Bug description: [Impact] Audio gets recorded by "arecord" has really bad sound quality when the volume is low. [Fix] https://github.com/alsa-project/alsa-utils/pull/69 Switch the default audio format from 8 bits to 16 bits if hardware supports it. [Test] 1. Plug a microphone. 2. Run `arecord | aplay` and say something to the microphone. 3. Only noise can be heard. With the fix applied, the recording is clear. [Where problems could occur] If there's any hardware falsely advertised to support 16 bits, this change will break them. However, this is effectively using `arecord -f cd` or `arecord -f cdr`, so that's not likely. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1923841/+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 1923115] Update Released
The verification of the Stable Release Update for systemd 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1923115 Title: Networkd vs udev nic renaming race condition Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [Impact] systemd-networkd renames nic just after udev renamed it e.g kernel: [ 2.827368] vmxnet3 :0b:00.0 ens192: renamed from eth0 kernel: [ 7.562729] vmxnet3 :0b:00.0 eth0: renamed from ens192 systemd-networkd[511]: ens192: Interface name change detected, ens192 has been renamed to eth0. This cause netplan or the other network management pkg can't find proper nic sometimes. This happens on Bionic Below commit seems to solve this issue. https://github.com/systemd/systemd/pull/11881/commits/30de2b89d125a8692c22579ef805b03f2054b30b There are bunch of related commits but above one the customer tested it worked. [Test Plan] The customer has issue and they could help us to test this. Internally they already test this and it worked. Please refer to github issue's reproduction step as well. https://github.com/systemd/systemd/issues/7293#issue-272917058 where the test plan is described as: "Reboot a couple of times. Sometimes the interface is renamed correctly. Sometimes it is not." [Where problems could occur] systemd-networkd should be restarted for this patch. systemd-networkd nic renaming could have issue. renaming may not be happening unexpectedly. e.g doesn't rename it properly or rename it when it should do. [Others] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923115/+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 1927255] Re: [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04)
** Summary changed: - [USB-Audio - RODECaster Pro, playback] Sound is distorted + [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1927255 Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04) Status in alsa-driver package in Ubuntu: New Bug description: I got a Rodecaster Pro USB device that has been causing trouble before and already lead to quirk handling in the kernel for the sample rate, see https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/usb/format.c?h=v5.8#n412 The Rodecaster is running fine on my laptop, but on my desktop, only audio input is working. The audio output is distorted. It's played kind of very slowly. Interestingly, if the source is a video file, the video plays slower, e.g. YouTube in a browser. I have never seen anything like that before. I have tried to figure out what the cause might be and I think I have reached the end of where I can get to on my own. I have documented most things at https://ubuntuforums.org/showthread.php?t=2461568 Putting my last step it in a nutshell: I have booted both my computers with a plain Ubuntu 21.04 from a pen drive (it uses kernel version 5.11.0-16-generic) to make sure it's not some different configuration that I have set up over the years on my systems (both Ubuntu 20.04 with kernel 5.8.18). I attached the Rodecaster. It runs fine on my laptop, but not on my desktop (used the output test from). I then detected the card number with aplay -l I killed pulseaudio with pulseaudio -k I then played the same sample (encoded in 48000 Hz in PCM signed 32 bit little endian format) using aplay -f S32_LE -c 2 -r 48000 -D hw:x ~/sample.wav where x is the appropriate card number and the rest of the arguments meet the Rodecaster's narrow specification. It's playing fine on the laptop, but distorted on the desktop. As far as I understand using aplay this way without a plugin should send the file directly to the device, so I assume there's something on the way from aplay to the Rodecaster that's interfering (kernel or even some piece of hardware) - and that definitely is where my expertise ends (rather a little before :-)). I'll gladly contribute any information that could be useful and I will willingly help to debug this problem if it may be related to the kernel. If there's anything I can do, please let me know. Cheers, Oliver ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.18-050818-generic x86_64 NonfreeKernelModules: blackmagic_io nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed May 5 18:28:46 2021 InstallationDate: Installed on 2020-05-15 (355 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Pro failed Symptom_Card: RODECaster Pro - RODECaster Pro Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1927255/+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 1923115] Re: Networkd vs udev nic renaming race condition
This bug was fixed in the package systemd - 237-3ubuntu10.47 --- systemd (237-3ubuntu10.47) bionic; urgency=medium * d/p/network_always_drop_configs_when_interface_is_renamed.patch: Fix networkd renaming race condition (LP: #1923115) -- Seyeong Kim Wed, 07 Apr 2021 15:11:17 +0900 ** Changed in: systemd (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1923115 Title: Networkd vs udev nic renaming race condition Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [Impact] systemd-networkd renames nic just after udev renamed it e.g kernel: [ 2.827368] vmxnet3 :0b:00.0 ens192: renamed from eth0 kernel: [ 7.562729] vmxnet3 :0b:00.0 eth0: renamed from ens192 systemd-networkd[511]: ens192: Interface name change detected, ens192 has been renamed to eth0. This cause netplan or the other network management pkg can't find proper nic sometimes. This happens on Bionic Below commit seems to solve this issue. https://github.com/systemd/systemd/pull/11881/commits/30de2b89d125a8692c22579ef805b03f2054b30b There are bunch of related commits but above one the customer tested it worked. [Test Plan] The customer has issue and they could help us to test this. Internally they already test this and it worked. Please refer to github issue's reproduction step as well. https://github.com/systemd/systemd/issues/7293#issue-272917058 where the test plan is described as: "Reboot a couple of times. Sometimes the interface is renamed correctly. Sometimes it is not." [Where problems could occur] systemd-networkd should be restarted for this patch. systemd-networkd nic renaming could have issue. renaming may not be happening unexpectedly. e.g doesn't rename it properly or rename it when it should do. [Others] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923115/+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 1926934]
this is "fixed" in the glibc 2.33 branch, if I understand the glibc maintainers correctly, they consider this as a workaround (see PR27744). -- 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/1926934 Title: gdb batch calls time out on armhf Status in gdb: Confirmed Status in gdb package in Ubuntu: New Bug description: seen when trying to build the gcc-10, or gcc-snapshot packages. A lot of tests in the guality test suite time out after 300 seconds (the default dejagnu timeout). These tests, like pr36728-1.c run ok on other architectures (and fail), but timeout on armhf. Seen in impish with gcc-10 and gcc-snapshot. Trying to run the gdb 10.2 tests on both hirsute and impish, I see a lot of timeouts as well. To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1926934/+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 1921452] Update Released
The verification of the Stable Release Update for alsa-lib 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 alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1921452 Title: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Status in OEM Priority Project: Fix Released Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Released Status in alsa-lib source package in Hirsute: Fix Released Bug description: [Impact] On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio. [Fix] Disable IEC958 (SPDIF) through ALSA UCM. [Test] With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. [Where problems will occur] "Cmedia Audio" is the sound card name of this usb audio dongle, and this string is got from usb string descriptor, that is to say the "Cmedia Audio" is hard-coded in the firmware of that usb dongle. Not all Cmedia usb audio dongle use "Cmedia Audio", most of the dongles don't set string descriptor, then the audio driver sets a generic name "USB Audio Device" for them, if a dongle has string descriptor, it may have different string like "C-Media USB Headphone Set", and all dongles I met before don't have SPDIF interface. So If this SRU could introduce regression, it will happen on a Cmedia usb audio dongle which also hard-codes the "Cmedia Audio" in the string descriptor and it has SPDIF interface on it, after this SRU, users couldn't find the SPDIF playback device from the gnome-sound-setting. But this regression chance is very low since it is very rare a cmedia usb audio dongle uses "Cmedia Audio" in the string descriptor and it is very rare a usb audio dongle has SPDIF interface. So far we haven't met such a cmedia usb audio dongle. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921452/+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 1927337] [NEW] [USB-Audio - RODECaster Pro, playback] Sound is distorted (21.04)
Public bug reported: I got a Rodecaster Pro USB device that has been causing trouble before and already lead to quirk handling in the kernel for the sample rate, see https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/usb/format.c?h=v5.8#n412 The Rodecaster is running fine on my laptop, but on my desktop, only audio input is working. The audio output is distorted. It's played kind of very slowly. Interestingly, if the source is a video file, the video plays slower, e.g. YouTube in a browser. I have never seen anything like that before. I have tried to figure out what the cause might be and I think I have reached the end of where I can get to on my own. I have documented most things at https://ubuntuforums.org/showthread.php?t=2461568 Putting my last step it in a nutshell: I have booted both my computers with a plain Ubuntu 21.04 from a pen drive (it uses kernel version 5.11.0-16-generic) to make sure it's not some different configuration that I have set up over the years on my systems (both Ubuntu 20.04 with kernel 5.8.18). I attached the Rodecaster. It runs fine on my laptop, but not on my desktop (used the output test from). I then detected the card number with aplay -l I killed pulseaudio with pulseaudio -k I then played the same sample (encoded in 48000 Hz in PCM signed 32 bit little endian format) using aplay -f S32_LE -c 2 -r 48000 -D hw:x ~/sample.wav where x is the appropriate card number and the rest of the arguments meet the Rodecaster's narrow specification. It's playing fine on the laptop, but distorted on the desktop. As far as I understand using aplay this way without a plugin should send the file directly to the device, so I assume there's something on the way from aplay to the Rodecaster that's interfering (kernel or even some piece of hardware) - and that definitely is where my expertise ends (rather a little before :-)). I'll gladly contribute any information that could be useful and I will willingly help to debug this problem if it may be related to the kernel. If there's anything I can do, please let me know. Cheers, Oliver ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Thu May 6 09:33:40 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Pro failed Symptom_Card: RODECaster Pro - RODECaster Pro Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Summary changed: - [USB-Audio - RODECaster Pro, playback] Sound is distorted + [USB-Audio - RODECaster Pro, playback] Sound is distorted (21.04) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1927337 Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted (21.04) Status in alsa-driver package in Ubuntu: New Bug description: I got a Rodecaster Pro USB device that has been causing trouble before and already lead to quirk handling in the kernel for the sample rate, see https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/usb/format.c?h=v5.8#n412 The Rodecaster is running fine on my laptop, but on my desktop, only audio input is working. The audio output is distorted. It's played kind of very slowly. Interestingly, if the source is a video file, the video plays sl
[Touch-packages] [Bug 1921655] Re: lightdm-guest-session ICEauthority error
This bug was fixed in the package lightdm - 1.30.0-0ubuntu4~20.04.1
---
lightdm (1.30.0-0ubuntu4~20.04.1) focal; urgency=medium
* debian/patches/fix-guest-session-ICEauthority-error.patch:
- Fixes AppArmor issue which prevented access to the guest session
feature in e.g. MATE (LP: #1921655). Thanks to Jonas Wiegert for
the solution!
-- Gunnar Hjalmarsson Mon, 12 Apr 2021 19:57:08
+0200
** Changed in: lightdm (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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1921655
Title:
lightdm-guest-session ICEauthority error
Status in Ubuntu MATE:
New
Status in lightdm package in Ubuntu:
Fix Released
Status in lightdm source package in Focal:
Fix Released
Status in lightdm source package in Groovy:
Fix Released
Status in lightdm source package in Hirsute:
Fix Released
Bug description:
[Impact]
If you enable the guest session feature on e.g. Ubuntu MATE, you are
met by an error message when trying to enter a guest session:
"Could not update file ICEauthority file /run/user/XXX/ICEauthority"
Even if it's not always a fatal error (the login may succeed after a
few minutes), the user experience is really bad, and you are inclined
to conclude that you are completely blocked from using the feature.
The proposed fix adds a rule to the lightdm-guest-session AppArmor
profile and prevents the error from happening.
[Test Plan]
On an updated Ubuntu MATE installation:
* Enable guest session
sudo sh -c 'printf "[Seat:*]\nallow-guest=true\n"
>/etc/lightdm/lightdm.conf.d/50-enable-guest.conf'
* Install lightdm from {focal,groovy}-proposed
* Reboot
You should now be able to enter a guest session without being stopped
by the ICEauthority error.
[Where problems could occur]
This one-liner is a harmless change.
The guest session is run in an unconfined mode since Ubuntu 16.10.
That's why the feature is disabled by default.
So if the additional rule would be wrong somehow (which I have no
reason to believe), it wouldn't break the AppArmor security layer for
the simple reason that it's already broken to begin with.
[Original description]
Hello I ran into trouble to start the lightdm-guest-session in linux
mint (cinnamon).
## How to reproduce:
- boot linux mint (20.02) or ubuntu mate (20.04) I haven't tested other
distros but I think others are also affected.
- enable guest user session
- try to login as guest user
## Error logs:
### Error Message:
` Could not update file ICEauthority file /run/user/XXX/ICEauthority`
### aa-notify:
```
Profile: /usr/lib/lightdm/lightdm-guest-session
Operation: open
Name: /proc/8125/uid_map
Denied: w
Logfile: /var/log/kern.log
Profile: /usr/lib/lightdm/lightdm-guest-session
Operation: open
Name: /proc/8125/setgroups
Denied: w
Logfile: /var/log/kern.log
Profile: /usr/lib/lightdm/lightdm-guest-session
Operation: open
Name: /proc/8125/gid_map
Denied: w
Logfile: /var/log/kern.log
Profile: /usr/lib/lightdm/lightdm-guest-session
Operation: open
Name: /proc/8624/fd/
Denied: r
Logfile: /var/log/kern.log
```
### dmesg:
```
[ 218.831289] audit: type=1400 audit(1616864450.287:76): apparmor="DENIED"
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/run/systemd/journal/dev-log" pid=3916 comm="cinnamon-sessio"
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
[ 1157.263045] audit: type=1400 audit(1616865388.720:1084): apparmor="DENIED"
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/proc/9899/fd/" pid=9899 comm="gpg-agent" requested_mask="r"
denied_mask="r" fsuid=999 #ouid=0
[ 1157.899223] audit: type=1400 audit(1616865389.356:1085): apparmor="DENIED"
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/proc/1/cgroup" pid=9840 comm="cinnamon-sessio" requested_mask="r"
denied_mask="r" fsuid=999 ouid=0
[ 1157.899445] audit: type=1400 audit(1616865389.360:1086): apparmor="DENIED"
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/run/systemd/journal/dev-log" pid=9840 comm="cinnamon-sessio"
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
[ 1157.903410] audit: type=1400 audit(1616865389.364:1087): apparmor="DENIED"
operation="link" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/run/user/999/ICEauthority-l" pid=9840 comm="cinnamon-sessio"
requested_mask="l" denied_mask="l" fsuid=999 ouid=999
target="/run/user/999/ICEauthority-c"
```
## Solutions:
### bad but common work around
Solutions I found in different forums were to move lightdm-guest-session into
complain mode like this:
`aa-complain /usr/lib/lightdm/lightdm-guest-session`
### maybe better sollution:
My fix would be to add this to `/etc/apparmor.d
[Touch-packages] [Bug 1923841] Update Released
The verification of the Stable Release Update for alsa-utils 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 alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1923841 Title: [SRU] Increase recording quality Status in HWE Next: New Status in alsa-utils package in Ubuntu: Fix Released Status in alsa-utils source package in Focal: Fix Released Bug description: [Impact] Audio gets recorded by "arecord" has really bad sound quality when the volume is low. [Fix] https://github.com/alsa-project/alsa-utils/pull/69 Switch the default audio format from 8 bits to 16 bits if hardware supports it. [Test] 1. Plug a microphone. 2. Run `arecord | aplay` and say something to the microphone. 3. Only noise can be heard. With the fix applied, the recording is clear. [Where problems could occur] If there's any hardware falsely advertised to support 16 bits, this change will break them. However, this is effectively using `arecord -f cd` or `arecord -f cdr`, so that's not likely. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1923841/+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 1925379] Re: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4
Thanks, the fix is uploaded and waiting for SRU review now ** Changed in: gtk+3.0 (Ubuntu) Status: In Progress => Fix Committed -- 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/1925379 Title: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4 Status in gtk+3.0 package in Ubuntu: Fix Committed Status in libreoffice package in Ubuntu: Confirmed Bug description: I just did a fresh install of Ubuntu 21.04 (smooth as silk), but then discovered that Auto-Correct in LibreOffice does not work. Yesterday, when I was still running 20.04, Auto-Correct worked fine -- same LibreOffice version, same LibreOffice profile, same LibreOffice document, and no changes on my part to my LibreOffice settings since I installed Ubuntu 21.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1925379/+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 1923115] Re: Networkd vs udev nic renaming race condition
...as for the autopkgtest failures being marked as failed even thought they passed, it seems britney wasn't running for bionic since the 27th of April! It was not caused by any changes or anything, it simply wasn't running - after digging deeper it seems that there was a stale lockfile that prevented it from running. I have cleared it and hopefully things should be working normally now. -- 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/1923115 Title: Networkd vs udev nic renaming race condition Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [Impact] systemd-networkd renames nic just after udev renamed it e.g kernel: [ 2.827368] vmxnet3 :0b:00.0 ens192: renamed from eth0 kernel: [ 7.562729] vmxnet3 :0b:00.0 eth0: renamed from ens192 systemd-networkd[511]: ens192: Interface name change detected, ens192 has been renamed to eth0. This cause netplan or the other network management pkg can't find proper nic sometimes. This happens on Bionic Below commit seems to solve this issue. https://github.com/systemd/systemd/pull/11881/commits/30de2b89d125a8692c22579ef805b03f2054b30b There are bunch of related commits but above one the customer tested it worked. [Test Plan] The customer has issue and they could help us to test this. Internally they already test this and it worked. Please refer to github issue's reproduction step as well. https://github.com/systemd/systemd/issues/7293#issue-272917058 where the test plan is described as: "Reboot a couple of times. Sometimes the interface is renamed correctly. Sometimes it is not." [Where problems could occur] systemd-networkd should be restarted for this patch. systemd-networkd nic renaming could have issue. renaming may not be happening unexpectedly. e.g doesn't rename it properly or rename it when it should do. [Others] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923115/+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 1926254] Re: x509 Certificate verification fails when basicConstraints=CA:FALSE, pathlen:0 on self-signed leaf certs
I very much appreciate the security review by Seth here. When I first started reading this bug I was going to insist on having a security review, but then I saw you've already taken care to arrange that. Thank you! ** Changed in: openssl (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1926254 Title: x509 Certificate verification fails when basicConstraints=CA:FALSE,pathlen:0 on self-signed leaf certs Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Focal: Fix Committed Status in openssl source package in Groovy: Fix Committed Status in openssl source package in Hirsute: Fix Released Bug description: [Impact] In openssl 1.1.1f, the below commit was merged: commit ba4356ae4002a04e28642da60c551877eea804f7 Author: Bernd Edlinger Date: Sat Jan 4 15:54:53 2020 +0100 Subject: Fix error handling in x509v3_cache_extensions and related functions Link: https://github.com/openssl/openssl/commit/ba4356ae4002a04e28642da60c551877eea804f7 This introduced a regression which caused certificate validation to fail when certificates violate RFC 5280 [1], namely, when a certificate has "basicConstraints=CA:FALSE,pathlen:0". This combination is commonly seen by self-signed leaf certificates with an intermediate CA before the root CA. Because of this, openssl 1.1.1f rejects these certificates and they cannot be used in the system certificate store, and ssl connections fail when you try to use them to connect to a ssl endpoint. The error you see when you try verify is: $ openssl verify -CAfile CA/rootCA_cert.pem -untrusted CA/subCA_cert.pem user1_cert.pem error 20 at 0 depth lookup: unable to get local issuer certificate error user1_cert.pem: verification failed The exact same certificates work fine on Xenial, Bionic and Hirsute. [1] https://tools.ietf.org/html/rfc5280.html [Testcase] We will create our own root CA, intermediate CA and leaf server certificate. Create necessary directories: $ mkdir reproducer $ cd reproducer $ mkdir CA Write openssl configuration files to disk for each CA and cert: $ cat << EOF >> rootCA.cnf [ req ] prompt = no distinguished_name = req_distinguished_name x509_extensions = usr_cert [ req_distinguished_name ] C = DE O = Test Org CN = Test RSA PSS Root-CA [ usr_cert ] basicConstraints= critical,CA:TRUE keyUsage= critical,keyCertSign,cRLSign subjectKeyIdentifier= hash authorityKeyIdentifier = keyid:always EOF $ cat << EOF >> subCA.cnf [ req ] prompt = no distinguished_name = req_distinguished_name x509_extensions = usr_cert [ req_distinguished_name ] C = DE O = Test Org CN = Test RSA PSS Sub-CA [ usr_cert ] basicConstraints= critical,CA:TRUE,pathlen:0 keyUsage= critical,keyCertSign,cRLSign subjectKeyIdentifier= hash authorityKeyIdentifier = keyid:always EOF $ cat << EOF >> user.cnf [ req ] prompt = no distinguished_name = req_distinguished_name x509_extensions = usr_cert [ req_distinguished_name ] C = DE O = Test Org CN = Test User [ usr_cert ] basicConstraints= critical,CA:FALSE,pathlen:0 keyUsage= critical,digitalSignature,keyAgreement extendedKeyUsage= clientAuth,serverAuth subjectKeyIdentifier= hash authorityKeyIdentifier = keyid:always EOF Then generate the necessary RSA keys and form certificates: $ openssl genpkey -algorithm RSA-PSS -out rootCA_key.pem -pkeyopt rsa_keygen_bits:2048 $ openssl req -config rootCA.cnf -set_serial 01 -new -batch -sha256 -nodes -x509 -days 9125 -out CA/rootCA_cert.pem -key rootCA_key.pem -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 $ openssl genpkey -algorithm RSA-PSS -out subCA_key.pem -pkeyopt rsa_keygen_bits:2048 $ openssl req -config subCA.cnf -new -out subCA_req.pem -key subCA_key.pem -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 $ openssl x509 -req -sha256 -in subCA_req.pem -CA CA/rootCA_cert.pem -CAkey rootCA_key.pem -out CA/subCA_cert.pem -CAserial rootCA_serial.txt -CAcreateserial -extfile subCA.cnf -extensions usr_cert -days 4380 -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 $ c_rehash CA $ openssl genpkey -algorithm RSA-PSS -out user1_key.pem -pkeyopt rsa_keygen_bits:2048 $ openssl req -config user.cnf -new -out user1_req.pem -key user1_key.pem -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 $ openssl x509 -req -sha256 -in user1_req.pem -CA CA/subCA_cert.pem -CAkey subCA_key.pem -out user1_cert.pem -CAserial subCA_serial.txt -CAcreateserial -extfile user.cnf -exte
[Touch-packages] [Bug 1927500] [NEW] package linux-firmware 1.187.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Public bug reported: Ubuntu Ver. 20.04 LTS ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.12 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abacon 2023 F pulseaudio /dev/snd/controlC1: abacon 2023 F pulseaudio CasperMD5CheckResult: skip Date: Thu May 6 09:21:21 2021 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=41f89867-56b0-4c8e-864c-c2be78496c3b InstallationDate: Installed on 2016-06-11 (1789 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-72-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.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc N/A RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: initramfs-tools Title: package linux-firmware 1.187.12 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/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FB dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A78M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFB:bd04/27/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1927500 Title: package linux-firmware 1.187.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Ubuntu Ver. 20.04 LTS ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.12 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abacon 2023 F pulseaudio /dev/snd/controlC1: abacon 2023 F pulseaudio CasperMD5CheckResult: skip Date: Thu May 6 09:21:21 2021 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=41f89867-56b0-4c8e-864c-c2be78496c3b InstallationDate: Installed on 2016-06-11 (1789 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-72-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.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc N/A RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: initramfs-tools Title: package linux-firmware 1.187.12 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/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FB dmi.board.a
[Touch-packages] [Bug 1914279] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted bcmwl into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bcmwl/6.30.223.271 +bdcom-0ubuntu7~20.04.2 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: dahdi-linux (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: New Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: New Status in bcmwl package in Ubuntu: New Status in dahdi-linux package in Ubuntu: New Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: New Status in evdi package in Ubuntu: New Status in gost-crypto package in Ubuntu: New Status in iptables-netflow package in Ubuntu: New Status in liblzf package in Ubuntu: New Status in lime-forensics package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in r8168 package in Ubuntu: New Status in rtl8812au package in Ubuntu: New Status in sysdig package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in acpi-call source package in Focal: Fix Committed Status in backport-iwlwifi-dkms source package in Focal: Fix Committed Status in bcmwl source package in Focal: Fix Committed Status in dahdi-linux source package in Focal: Fix Committed Status in dm-writeboost source package in Focal: Fix Committed Status in evdi source package in Focal: Fix Committed Status in gost-crypto source package in Focal: Fix Committed Status in iptables-netflow source package in Focal: Fix Committed Status in liblzf source package in Focal: Fix Committed Status in lime-forensics source package in Focal: Fix Committed Status in lttng-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Status in oss4 source package in Focal: Fix Committed Status in r8168 source package in Focal: Fix Committed Status in rtl8812au source package in Focal: Fix Committed Status in sysdig source package in Focal: Fix Committed Status in v4l2loopback source package in Focal: Fix Committed Status in virtualbox source package in Focal: Fix Committed Status in virtualbox-hwe source package in Focal: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networkin
[Touch-packages] [Bug 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device
This bug was fixed in the package alsa-lib - 1.2.3.2-1ubuntu3.2 --- alsa-lib (1.2.3.2-1ubuntu3.2) groovy; urgency=medium * d/p/0001-conf-USB-add-Cmedia-Audio-to-USB-Audio.pcm.iec958_de.patch: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device (LP: #1921452) -- Shengyao Xue Tue, 06 Apr 2021 21:26:31 +0200 ** Changed in: alsa-lib (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1921452 Title: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Status in OEM Priority Project: Fix Released Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Released Status in alsa-lib source package in Hirsute: Fix Released Bug description: [Impact] On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio. [Fix] Disable IEC958 (SPDIF) through ALSA UCM. [Test] With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. [Where problems will occur] "Cmedia Audio" is the sound card name of this usb audio dongle, and this string is got from usb string descriptor, that is to say the "Cmedia Audio" is hard-coded in the firmware of that usb dongle. Not all Cmedia usb audio dongle use "Cmedia Audio", most of the dongles don't set string descriptor, then the audio driver sets a generic name "USB Audio Device" for them, if a dongle has string descriptor, it may have different string like "C-Media USB Headphone Set", and all dongles I met before don't have SPDIF interface. So If this SRU could introduce regression, it will happen on a Cmedia usb audio dongle which also hard-codes the "Cmedia Audio" in the string descriptor and it has SPDIF interface on it, after this SRU, users couldn't find the SPDIF playback device from the gnome-sound-setting. But this regression chance is very low since it is very rare a cmedia usb audio dongle uses "Cmedia Audio" in the string descriptor and it is very rare a usb audio dongle has SPDIF interface. So far we haven't met such a cmedia usb audio dongle. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921452/+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 1927712] [NEW] The Pacemaker module "ocf:heartbeat:CTDB" does not work on Bionic
Public bug reported: Pacemaker on Ubuntu 18.04 is not able to create a resource of type: ocf:heartbeat:CTDB. It seems to be because the command ctdb version return Ubuntu in the vesion. The issue is fixed upstream in the commit https://github.com/ClusterLabs /resource-agents/commit/0c513d16259d94b492f0fe8dd0cbc2e5f98ee912#diff- 6f2dd2a1f5930ef451c54c7bf8df90adc5675aff2e0018552b5f428c66c59060 = To reproduce = * apt install ctdb pacemaker corosync pcs * passwd hacluster * pcs cluster auth localhost -u hacluster * pcs cluster setup --name test localhost --force --enable * pcs cluster start --all * echo "127.0.0.1" > /etc/ctdb/nodes * touch /etc/default/ctdb * pcs resource create ctdb ocf:heartbeat:CTDB ctdb_recovery_lock="/tmp/lock" == Actual result == The command pcs resource debug-start ctdb return Operation start for ctdb (ocf:heartbeat:CTDB) returned: 'unknown error' (1) == Expected result == pcs resource debug-start ctdb return Operation start for ctdb (ocf:heartbeat:CTDB) returned: 'ok' (0) ** Affects: pacemaker (Ubuntu) Importance: Undecided Status: New ** Description changed: Pacemaker is not able to create a resource of type: ocf:heartbeat:CTDB. - It seems to be because the command + It seems to be because the command ``` ctdb version ``` return Ubuntu in the vesion. The issue is fixed upstream in the commit https://github.com/ClusterLabs /resource-agents/commit/0c513d16259d94b492f0fe8dd0cbc2e5f98ee912#diff- 6f2dd2a1f5930ef451c54c7bf8df90adc5675aff2e0018552b5f428c66c59060 - # To reproduce + = To reproduce = + * apt install ctdb pacemaker corosync pcs * passwd hacluster * pcs cluster auth localhost -u hacluster * pcs cluster setup --name test localhost --force --enable * pcs cluster start --all * echo "127.0.0.1" > /etc/ctdb/nodes * touch /etc/default/ctdb * pcs resource create ctdb ocf:heartbeat:CTDB ctdb_recovery_lock="/tmp/lock" - - ## Actual result + == Actual result == The command - ``` + pcs resource debug-start ctdb - ``` + return - ``` + Operation start for ctdb (ocf:heartbeat:CTDB) returned: 'unknown error' (1) - ``` + - ## Expected result + == Expected result == - ``` + pcs resource debug-start ctdb - ``` + return - ``` + Operation start for ctdb (ocf:heartbeat:CTDB) returned: 'ok' (0) - ``` + ** Description changed: Pacemaker is not able to create a resource of type: ocf:heartbeat:CTDB. It seems to be because the command - ``` + ctdb version - ``` + return Ubuntu in the vesion. The issue is fixed upstream in the commit https://github.com/ClusterLabs /resource-agents/commit/0c513d16259d94b492f0fe8dd0cbc2e5f98ee912#diff- 6f2dd2a1f5930ef451c54c7bf8df90adc5675aff2e0018552b5f428c66c59060 = To reproduce = * apt install ctdb pacemaker corosync pcs * passwd hacluster * pcs cluster auth localhost -u hacluster * pcs cluster setup --name test localhost --force --enable * pcs cluster start --all * echo "127.0.0.1" > /etc/ctdb/nodes * touch /etc/default/ctdb * pcs resource create ctdb ocf:heartbeat:CTDB ctdb_recovery_lock="/tmp/lock" == Actual result == The command pcs resource debug-start ctdb return Operation start for ctdb (ocf:heartbeat:CTDB) returned: 'unknown error' (1) == Expected result == pcs resource debug-start ctdb return Operation start for ctdb (ocf:heartbeat:CTDB) returned: 'ok' (0) ** Package changed: systemd (Ubuntu) => pacemaker (Ubuntu) ** Description changed: - Pacemaker is not able to create a resource of type: ocf:heartbeat:CTDB. + Pacemaker on Ubuntu 18.04 is not able to create a resource of type: ocf:heartbeat:CTDB. It seems to be because the command ctdb version return Ubuntu in the vesion. The issue is fixed upstream in the commit https://github.com/ClusterLabs /resource-agents/commit/0c513d16259d94b492f0fe8dd0cbc2e5f98ee912#diff- 6f2dd2a1f5930ef451c54c7bf8df90adc5675aff2e0018552b5f428c66c59060 = To reproduce = * apt install ctdb pacemaker corosync pcs * passwd hacluster * pcs cluster auth localhost -u hacluster * pcs cluster setup --name test localhost --force --enable * pcs cluster start --all * echo "127.0.0.1" > /etc/ctdb/nodes * touch /etc/default/ctdb * pcs resource create ctdb ocf:heartbeat:CTDB ctdb_recovery_lock="/tmp/lock" == Actual result == The command pcs resource debug-start ctdb return Operation start for ctdb (ocf:heartbeat:CTDB) returned: 'unknown error' (1) == Expected result == pcs resource debug-start ctdb return Operation start for ctdb (ocf:heartbeat:CTDB) returned: 'ok' (0) -- 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/1927712 Title: The Pacemaker module "ocf:h
[Touch-packages] [Bug 1927724] [NEW] package base-passwd 3.5.49 failed to install/upgrade: installed base-passwd package post-installation script subprocess was killed by signal (Aborted), core dumped
Public bug reported: failed on installation ProblemType: Package DistroRelease: Ubuntu 21.04 Package: base-passwd 3.5.49 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri May 7 03:51:43 2021 ErrorMessage: installed base-passwd package post-installation script subprocess was killed by signal (Aborted), core dumped InstallationDate: Installed on 2020-06-30 (311 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.9, Python 3.9.4, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SourcePackage: base-passwd Title: package base-passwd 3.5.49 failed to install/upgrade: installed base-passwd package post-installation script subprocess was killed by signal (Aborted), core dumped UpgradeStatus: Upgraded to hirsute on 2021-05-07 (0 days ago) ** Affects: base-passwd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-passwd in Ubuntu. https://bugs.launchpad.net/bugs/1927724 Title: package base-passwd 3.5.49 failed to install/upgrade: installed base- passwd package post-installation script subprocess was killed by signal (Aborted), core dumped Status in base-passwd package in Ubuntu: New Bug description: failed on installation ProblemType: Package DistroRelease: Ubuntu 21.04 Package: base-passwd 3.5.49 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri May 7 03:51:43 2021 ErrorMessage: installed base-passwd package post-installation script subprocess was killed by signal (Aborted), core dumped InstallationDate: Installed on 2020-06-30 (311 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.9, Python 3.9.4, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SourcePackage: base-passwd Title: package base-passwd 3.5.49 failed to install/upgrade: installed base-passwd package post-installation script subprocess was killed by signal (Aborted), core dumped UpgradeStatus: Upgraded to hirsute on 2021-05-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/1927724/+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 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device
This bug was fixed in the package alsa-lib - 1.2.2-2.1ubuntu2.4 --- alsa-lib (1.2.2-2.1ubuntu2.4) focal; urgency=medium * d/p/0001-conf-USB-add-Cmedia-Audio-to-USB-Audio.pcm.iec958_de.patch: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device (LP: #1921452) -- Shengyao Xue Tue, 06 Apr 2021 21:33:31 +0200 ** Changed in: alsa-lib (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 alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1921452 Title: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Status in OEM Priority Project: Fix Released Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-lib source package in Groovy: Fix Released Status in alsa-lib source package in Hirsute: Fix Released Bug description: [Impact] On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio. [Fix] Disable IEC958 (SPDIF) through ALSA UCM. [Test] With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. [Where problems will occur] "Cmedia Audio" is the sound card name of this usb audio dongle, and this string is got from usb string descriptor, that is to say the "Cmedia Audio" is hard-coded in the firmware of that usb dongle. Not all Cmedia usb audio dongle use "Cmedia Audio", most of the dongles don't set string descriptor, then the audio driver sets a generic name "USB Audio Device" for them, if a dongle has string descriptor, it may have different string like "C-Media USB Headphone Set", and all dongles I met before don't have SPDIF interface. So If this SRU could introduce regression, it will happen on a Cmedia usb audio dongle which also hard-codes the "Cmedia Audio" in the string descriptor and it has SPDIF interface on it, after this SRU, users couldn't find the SPDIF playback device from the gnome-sound-setting. But this regression chance is very low since it is very rare a cmedia usb audio dongle uses "Cmedia Audio" in the string descriptor and it is very rare a usb audio dongle has SPDIF interface. So far we haven't met such a cmedia usb audio dongle. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921452/+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 1923564] Re: BlueZ 5.58 release
** Attachment added: "bluez_5.58-0ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1923564/+attachment/5495028/+files/bluez_5.58-0ubuntu1.debian.tar.xz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1923564 Title: BlueZ 5.58 release Status in bluez package in Ubuntu: In Progress Bug description: BlueZ 5.58 has been released. We should look at it for the 21.10 cycle... http://www.bluez.org/release-of-bluez-5-58-and-5-57/ https://mirrors.edge.kernel.org/pub/linux/bluetooth/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1923564/+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 1923564] Re: BlueZ 5.58 release
** Attachment removed: "bluez_5.58-0ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1923564/+attachment/5494657/+files/bluez_5.58-0ubuntu1.debian.tar.xz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1923564 Title: BlueZ 5.58 release Status in bluez package in Ubuntu: In Progress Bug description: BlueZ 5.58 has been released. We should look at it for the 21.10 cycle... http://www.bluez.org/release-of-bluez-5-58-and-5-57/ https://mirrors.edge.kernel.org/pub/linux/bluetooth/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1923564/+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 1522675] Re: Warning messages about unsandboxed downloads
This showed up on Ubuntu 21.04. Regression? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in aptitude package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Fix Released Status in aptitude source package in Xenial: Confirmed Status in synaptic source package in Xenial: Confirmed Status in update-notifier source package in Xenial: Fix Released Status in apt source package in Hirsute: Fix Released Status in aptitude source package in Hirsute: Fix Released Status in synaptic source package in Hirsute: Triaged Status in update-notifier source package in Hirsute: Fix Released Status in apt package in Debian: Fix Released Status in aptitude package in Debian: Fix Released Status in synaptic package in Debian: New Bug description: READ ME FIRST = This is only a regression on a cosmetic level. Previous versions of apt did not have any sandboxing whatsoever, so this means apt reverted back to that old behavior. update-notifier SRU --- [Impact] Cosmetic. Warnings when installing packages using update-notifier downloading stuff [Test case] Install flashplugin-installer with apt and check that the output does not contain a message like this: W: Can't drop privileges for downloading as file '...' couldn't be accessed by user '_apt' [Regression Potential] It just chowns /var/lib/update-notifier/package-data- downloads/partial/ to _apt:root, there should not be any regression. Original report --- Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1914279] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted liblzf into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/liblzf/3.6-2~ubuntu1.20.04.2 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: lime-forensics (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: New Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: New Status in bcmwl package in Ubuntu: New Status in dahdi-linux package in Ubuntu: New Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: New Status in evdi package in Ubuntu: New Status in gost-crypto package in Ubuntu: New Status in iptables-netflow package in Ubuntu: New Status in liblzf package in Ubuntu: New Status in lime-forensics package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in r8168 package in Ubuntu: New Status in rtl8812au package in Ubuntu: New Status in sysdig package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in acpi-call source package in Focal: Fix Committed Status in backport-iwlwifi-dkms source package in Focal: Fix Committed Status in bcmwl source package in Focal: Fix Committed Status in dahdi-linux source package in Focal: Fix Committed Status in dm-writeboost source package in Focal: Fix Committed Status in evdi source package in Focal: Fix Committed Status in gost-crypto source package in Focal: Fix Committed Status in iptables-netflow source package in Focal: Fix Committed Status in liblzf source package in Focal: Fix Committed Status in lime-forensics source package in Focal: Fix Committed Status in lttng-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Status in oss4 source package in Focal: Fix Committed Status in r8168 source package in Focal: Fix Committed Status in rtl8812au source package in Focal: Fix Committed Status in sysdig source package in Focal: Fix Committed Status in v4l2loopback source package in Focal: Fix Committed Status in virtualbox source package in Focal: Fix Committed Status in virtualbox-hwe source package in Focal: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them
[Touch-packages] [Bug 1927163] Re: Support time status is not correctly if we use ubuntu-support-status command in terminal
Also marking update-manager as affected since the ubuntu-support-status command is part of update-manager-core. ** Also affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1927163 Title: Support time status is not correctly if we use ubuntu-support-status command in terminal Status in brotli package in Ubuntu: New Status in gst-plugins-good1.0 package in Ubuntu: New Status in update-manager package in Ubuntu: New Status in woff2 package in Ubuntu: New Bug description: Dear Launchpad Community, I used ubuntu-support-status command on my Ubuntu 18.04.5 system and I can see that these packages are not supported: gstreamer1.0-gtk3 libbrotli1 libwoff1 Like we know these packages are from main repositore so this should have support to 2023 year so this is why I report this like bug. Package: gstreamer1.0-gtk3 Version: 1.14.5-0ubuntu1~18.04.2 Package: libbrotli1 Version: 1.0.3-1ubuntu1.3 Package: libwoff1 Version: 1.0.2-1build0.1 lsb_release -a Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic I hope that you fix it or explain me why these packages are not supported. Yours faithfully, Piotr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brotli/+bug/1927163/+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
It's ok to strip glibc/ld.so on armhf, but then gdb needs to be able to find the debug symbols. For impish, - call dh_strip in glibc with current debhelper, not compat 8, so that the build-id's are resolved by build file system layout, not the original file names. That's already done in glibc 2.33-0ubuntu6 - let the gdb build depend on libc6-dbg on armhf, also let gdb depend on libc6-dbg on armhf, instead of recommending it. The alternative is not to strip glibc's ld.so on armhf, as Luis suggested. ** Also affects: gdb (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: gdb (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: gdb (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: glibc (Ubuntu) Importance: Undecided Status: New ** Tags added: rls-ff-incoming rls-gg-incoming rls-hh-incoming ** Changed in: glibc (Ubuntu Impish) Status: New => Fix Committed ** Changed in: gdb (Ubuntu Impish) Status: Confirmed => Fix Committed -- 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 Committed Status in glibc package in Ubuntu: Fix Committed Status in gdb source package in Focal: New Status in glibc source package in Focal: New Status in gdb source package in Groovy: New Status in glibc source package in Groovy: New Status in gdb source package in Hirsute: New Status in glibc source package in Hirsute: New Status in gdb source package in Impish: Fix Committed Status in glibc source package in Impish: Fix Committed Bug description: 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 1926843] Re: online accounts integration with fb isn't working
stil the samme issue? XDG_CURRENT_DESKTOP=GNOME gnome-control-center Gtk-Message: 18:39:14.049: Failed to load module "appmenu-gtk-module" Gtk-Message: 18:39:19.385: Failed to load module "appmenu-gtk-module" (WebKitWebProcess:2): dbind-WARNING **: 18:39:19.409: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-pkft2CzOvy: file or folder did not exist. Also want to know sed -i ‘s/^Exec.*/Exec=env XDG_CURRENT_DESKTOP=GNOME gnome-control- center --overview/’ ~/.local/share/applications/gnome-control- center.desktop --debug how to use that one? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1926843 Title: online accounts integration with fb isn't working Status in gnome-online-accounts package in Ubuntu: Fix Committed Bug description: Hi i tryed to use gnome-control-center online-accounts to make easy like windows 10 to login to email or add other login so its more easy with ID to use pincode or other ID fingerprint and other. But its look its much issue compared with windows 10 with thunderbird, firefox, and other program. Worst is facebook only little windows with issue with login? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-online-accounts 3.38.1-1ubuntu1 Uname: Linux 5.12.0-051200-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 1 19:38:03 2021 InstallationDate: Installed on 2019-05-07 (725 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+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 1926843] Re: online accounts integration with fb isn't working
gnome-online-accounts (3.38.1-1ubuntu1). sudo apt-get upgrade 0 upgrade, 0 new installed, 0 to remove and 0 no upgrades. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1926843 Title: online accounts integration with fb isn't working Status in gnome-online-accounts package in Ubuntu: Fix Committed Bug description: Hi i tryed to use gnome-control-center online-accounts to make easy like windows 10 to login to email or add other login so its more easy with ID to use pincode or other ID fingerprint and other. But its look its much issue compared with windows 10 with thunderbird, firefox, and other program. Worst is facebook only little windows with issue with login? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-online-accounts 3.38.1-1ubuntu1 Uname: Linux 5.12.0-051200-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 1 19:38:03 2021 InstallationDate: Installed on 2019-05-07 (725 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+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 1921475] Re: [2.9.2] Commissioning does not collect correct storage information
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd via https://github.com/lxc/lxd/issues/8718 Importance: Unknown Status: Unknown ** No longer affects: systemd ** Also affects: lxd via https://github.com/lxc/lxd/issues/8718 Importance: Unknown Status: Unknown -- 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/1921475 Title: [2.9.2] Commissioning does not collect correct storage information Status in lxd: Unknown Status in MAAS: Invalid Status in systemd package in Ubuntu: New Bug description: MAAS version 2.9.2 When commissioning servers with different storage types (SSDs in a virtual disk behind RAID controller, NVMes and HDDs), but everything shows up tagged as SSD. The commissioning step 50-maas-01-commissioning is generating _incorrect_ storage info such as a random serial and it’s missing the rpm for the virtual disk (behind RAID controller) and the HDDs. The commissioning step maas-lshw generates the correct info, but is not used. I have added screenshot of storage after commission and outputs from both 50-maas-01-commissioning and maas-lshw here: https://discourse.maas.io/t/how-to-work-with-storage- tags/4344/3?u=szeestraten See https://discourse.maas.io/t/how-to-work-with-storage-tags/4344 for conversation To manage notifications about this bug go to: https://bugs.launchpad.net/lxd/+bug/1921475/+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 1926844] Re: get white screen when i play with Videos app or totem name wrong
its other bug on other pc, ** Attachment added: "videos not find.png" https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1926844/+attachment/5495544/+files/videos%20not%20find.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1926844 Title: get white screen when i play with Videos app or totem name wrong Status in gstreamer1.0 package in Ubuntu: New Bug description: I get white screen https://gitlab.gnome.org/GNOME/totem/-/issues/461 When i plays video same if i use: ** (totem:40351): DEBUG: 18:05:56.040: Initializing XApp GtkModule (totem:40351): GLib-GIO-DEBUG: 18:05:56.045: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’ ** (totem:40351): DEBUG: 18:05:56.045: Adding a Favorites shortcut to GtkPlacesSideBars (totem:40351): GLib-GIO-DEBUG: 18:05:56.046: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ (totem:40351): dconf-DEBUG: 18:05:56.046: watch_fast: "/org/appmenu/gtk-module/" (establishing: 0, active: 0) (totem:40351): dconf-DEBUG: 18:05:56.046: unwatch_fast: "/org/appmenu/gtk-module/" (active: 0, establishing: 1) (totem:40351): dconf-DEBUG: 18:05:56.047: watch_established: "/org/appmenu/gtk-module/" (establishing: 0) (totem:40351): dconf-DEBUG: 18:05:56.084: watch_fast: "/org/appmenu/gtk-module/" (establishing: 0, active: 0) (totem:40351): dconf-DEBUG: 18:05:56.085: unwatch_fast: "/org/appmenu/gtk-module/" (active: 0, establishing: 1) (totem:40351): dconf-DEBUG: 18:05:56.085: watch_established: "/org/appmenu/gtk-module/" (establishing: 0) (totem:40351): dconf-DEBUG: 18:05:56.243: watch_fast: "/org/gnome/Totem/" (establishing: 0, active: 0) (totem:40351): dconf-DEBUG: 18:05:56.244: watch_established: "/org/gnome/Totem/" (establishing: 1) (totem:40351): GLib-DEBUG: 18:05:56.257: unsetenv() is not thread-safe and should not be used after threads are created (totem:40351): Gtk-DEBUG: 18:05:56.257: Connecting to session manager (totem:40351): dconf-DEBUG: 18:05:56.262: watch_fast: "/org/gnome/Totem/" (establishing: 0, active: 1) (totem:40351): dconf-DEBUG: 18:05:56.262: watch_fast: "/org/gnome/desktop/lockdown/" (establishing: 0, active: 0) (totem:40351): dconf-DEBUG: 18:05:56.262: watch_established: "/org/gnome/desktop/lockdown/" (establishing: 1) (totem:40351): dconf-DEBUG: 18:05:56.418: watch_fast: "/org/gnome/desktop/thumbnailers/" (establishing: 0, active: 0) (totem:40351): dconf-DEBUG: 18:05:56.419: watch_established: "/org/gnome/desktop/thumbnailers/" (establishing: 1) (totem:40351): GLib-GIO-DEBUG: 18:05:56.421: Failed to initialize portal (GNetworkMonitorPortal) for gio-network-monitor: Not using portals (totem:40351): GLib-GIO-DEBUG: 18:05:56.423: _g_io_module_get_default: Found default implementation networkmanager (GNetworkMonitorNM) for ‘gio-network-monitor’ (totem:40351): dconf-DEBUG: 18:05:56.424: watch_fast: "/org/gnome/Totem/" (establishing: 0, active: 2) (totem:40351): dconf-DEBUG: 18:05:56.424: unwatch_fast: "/org/gnome/Totem/" (active: 3, establishing: 0) (totem:40351): dconf-DEBUG: 18:05:56.512: change_fast (totem:40351): dconf-DEBUG: 18:05:56.512: change_notify: /org/gnome/Totem/subtitle-encoding (totem:40351): dconf-DEBUG: 18:05:56.512: watch_fast: "/org/gnome/Totem/" (establishing: 0, active: 2) (totem:40351): dconf-DEBUG: 18:05:56.512: unwatch_fast: "/org/gnome/Totem/" (active: 3, establishing: 0) (totem:40351): dconf-DEBUG: 18:05:56.512: watch_fast: "/org/gnome/Totem/" (establishing: 0, active: 2) ** (totem:40351): DEBUG: 18:05:56.524: Setting rotation to '0,00' (totem:40351): dconf-DEBUG: 18:05:56.531: watch_fast: "/org/gnome/desktop/lockdown/" (establishing: 0, active: 1) (totem:40351): dconf-DEBUG: 18:05:56.535: watch_fast: "/org/gnome/Totem/" (establishing: 0, active: 3) (totem:40351): Totem-DEBUG: 18:05:56.535: TotemGrilo: Resuming videos thumbnailing (totem:40351): Totem-DEBUG: 18:05:56.535: TotemGrilo: Activating plugins (totem:40351): Tracker-DEBUG: 18:05:56.554: Using backend = 'AUTO' Tracker-INFO: 18:05:56.554: Setting database locations Tracker-INFO: 18:05:56.555: Checking whether database files exist Tracker-INFO: 18:05:56.555: Opened sqlite3 database:'/home/larsmartin/.cache/tracker/meta.db' (totem:40351): Tracker-DEBUG: 18:05:56.555: Resetting collator in db interface 0x55a80b5493f0 (totem:40351): Tracker-DEBUG: 18:05:56.555: [ICU collation] Initializing collator for locale 'en_GB.UTF-8' (totem:40351): Tracker-DEBUG: 18:05:56.555: [ICU collation] Initializing collator for locale 'en_GB.UTF-8' (totem:40351): Tracker-DEBUG: 18:05:56.555: Preparing query: 'PRAGMA synchronous = OFF;' ** (totem:40351): DEBUG: 18:05:56.563: Name com.canonical.AppMenu.Registrar does not exist on the session bus
[Touch-packages] [Bug 1926844] Re: get white screen when i play with Videos app or totem name wrong
** Attachment added: "videos issue" https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1926844/+attachment/5495545/+files/videos%20gnome%20issue.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1926844 Title: get white screen when i play with Videos app or totem name wrong Status in gstreamer1.0 package in Ubuntu: New Bug description: I get white screen https://gitlab.gnome.org/GNOME/totem/-/issues/461 When i plays video same if i use: ** (totem:40351): DEBUG: 18:05:56.040: Initializing XApp GtkModule (totem:40351): GLib-GIO-DEBUG: 18:05:56.045: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’ ** (totem:40351): DEBUG: 18:05:56.045: Adding a Favorites shortcut to GtkPlacesSideBars (totem:40351): GLib-GIO-DEBUG: 18:05:56.046: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ (totem:40351): dconf-DEBUG: 18:05:56.046: watch_fast: "/org/appmenu/gtk-module/" (establishing: 0, active: 0) (totem:40351): dconf-DEBUG: 18:05:56.046: unwatch_fast: "/org/appmenu/gtk-module/" (active: 0, establishing: 1) (totem:40351): dconf-DEBUG: 18:05:56.047: watch_established: "/org/appmenu/gtk-module/" (establishing: 0) (totem:40351): dconf-DEBUG: 18:05:56.084: watch_fast: "/org/appmenu/gtk-module/" (establishing: 0, active: 0) (totem:40351): dconf-DEBUG: 18:05:56.085: unwatch_fast: "/org/appmenu/gtk-module/" (active: 0, establishing: 1) (totem:40351): dconf-DEBUG: 18:05:56.085: watch_established: "/org/appmenu/gtk-module/" (establishing: 0) (totem:40351): dconf-DEBUG: 18:05:56.243: watch_fast: "/org/gnome/Totem/" (establishing: 0, active: 0) (totem:40351): dconf-DEBUG: 18:05:56.244: watch_established: "/org/gnome/Totem/" (establishing: 1) (totem:40351): GLib-DEBUG: 18:05:56.257: unsetenv() is not thread-safe and should not be used after threads are created (totem:40351): Gtk-DEBUG: 18:05:56.257: Connecting to session manager (totem:40351): dconf-DEBUG: 18:05:56.262: watch_fast: "/org/gnome/Totem/" (establishing: 0, active: 1) (totem:40351): dconf-DEBUG: 18:05:56.262: watch_fast: "/org/gnome/desktop/lockdown/" (establishing: 0, active: 0) (totem:40351): dconf-DEBUG: 18:05:56.262: watch_established: "/org/gnome/desktop/lockdown/" (establishing: 1) (totem:40351): dconf-DEBUG: 18:05:56.418: watch_fast: "/org/gnome/desktop/thumbnailers/" (establishing: 0, active: 0) (totem:40351): dconf-DEBUG: 18:05:56.419: watch_established: "/org/gnome/desktop/thumbnailers/" (establishing: 1) (totem:40351): GLib-GIO-DEBUG: 18:05:56.421: Failed to initialize portal (GNetworkMonitorPortal) for gio-network-monitor: Not using portals (totem:40351): GLib-GIO-DEBUG: 18:05:56.423: _g_io_module_get_default: Found default implementation networkmanager (GNetworkMonitorNM) for ‘gio-network-monitor’ (totem:40351): dconf-DEBUG: 18:05:56.424: watch_fast: "/org/gnome/Totem/" (establishing: 0, active: 2) (totem:40351): dconf-DEBUG: 18:05:56.424: unwatch_fast: "/org/gnome/Totem/" (active: 3, establishing: 0) (totem:40351): dconf-DEBUG: 18:05:56.512: change_fast (totem:40351): dconf-DEBUG: 18:05:56.512: change_notify: /org/gnome/Totem/subtitle-encoding (totem:40351): dconf-DEBUG: 18:05:56.512: watch_fast: "/org/gnome/Totem/" (establishing: 0, active: 2) (totem:40351): dconf-DEBUG: 18:05:56.512: unwatch_fast: "/org/gnome/Totem/" (active: 3, establishing: 0) (totem:40351): dconf-DEBUG: 18:05:56.512: watch_fast: "/org/gnome/Totem/" (establishing: 0, active: 2) ** (totem:40351): DEBUG: 18:05:56.524: Setting rotation to '0,00' (totem:40351): dconf-DEBUG: 18:05:56.531: watch_fast: "/org/gnome/desktop/lockdown/" (establishing: 0, active: 1) (totem:40351): dconf-DEBUG: 18:05:56.535: watch_fast: "/org/gnome/Totem/" (establishing: 0, active: 3) (totem:40351): Totem-DEBUG: 18:05:56.535: TotemGrilo: Resuming videos thumbnailing (totem:40351): Totem-DEBUG: 18:05:56.535: TotemGrilo: Activating plugins (totem:40351): Tracker-DEBUG: 18:05:56.554: Using backend = 'AUTO' Tracker-INFO: 18:05:56.554: Setting database locations Tracker-INFO: 18:05:56.555: Checking whether database files exist Tracker-INFO: 18:05:56.555: Opened sqlite3 database:'/home/larsmartin/.cache/tracker/meta.db' (totem:40351): Tracker-DEBUG: 18:05:56.555: Resetting collator in db interface 0x55a80b5493f0 (totem:40351): Tracker-DEBUG: 18:05:56.555: [ICU collation] Initializing collator for locale 'en_GB.UTF-8' (totem:40351): Tracker-DEBUG: 18:05:56.555: [ICU collation] Initializing collator for locale 'en_GB.UTF-8' (totem:40351): Tracker-DEBUG: 18:05:56.555: Preparing query: 'PRAGMA synchronous = OFF;' ** (totem:40351): DEBUG: 18:05:56.563: Name com.canonical.AppMenu.Registrar does not exist on the session bus (totem:40351): dconf-DEBUG: 18:0
[Touch-packages] [Bug 1927779] [NEW] MODULES=list results in error
Public bug reported: [impact] setting MODULES=list in /etc/initramfs-tools/initramfs.conf results in an error/warning when running update-initramfs [test case] edit initramfs.conf to change MODULES=list and run update-initramfs: $ grep MODULES /etc/initramfs-tools/initramfs.conf # MODULES: [ most | netboot | dep | list ] MODULES=list $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.8.0-48-generic find: ‘/var/tmp/mkinitramfs_Yr04uh/lib/modules/5.8.0-48-generic/kernel’: No such file or directory [regression potential] any regression would likely result in an initramfs that did not include the correct/required modules, and/or failure to build a new initramfs [scope] this is needed for g and earlier. this is not fixed in debian, but is fixed in h and i. for debian, MR open: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/48 [other info] this caused some of the 'amd64-*' autopkgtests to fail in h until it was fixed. those autopkgtests don't exist in g and earlier so this was not noticed until now. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: initramfs-tools (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: initramfs-tools (Ubuntu Focal) Importance: Undecided Status: New ** Affects: initramfs-tools (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu) Status: New => Fix Released ** Description changed: [impact] setting MODULES=list in /etc/initramfs-tools/initramfs.conf results in an error/warning when running update-initramfs [test case] edit initramfs.conf to change MODULES=list and run update-initramfs: $ grep MODULES /etc/initramfs-tools/initramfs.conf # MODULES: [ most | netboot | dep | list ] MODULES=list $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.8.0-48-generic find: ‘/var/tmp/mkinitramfs_Yr04uh/lib/modules/5.8.0-48-generic/kernel’: No such file or directory [regression potential] any regression would likely result in an initramfs that did not include the correct/required modules, and/or failure to build a new initramfs [scope] this is needed for g and earlier. this is not fixed in debian, but is fixed in h and i. + for debian, MR open: + https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/48 + [other info] this caused some of the 'amd64-*' autopkgtests to fail in h until it was fixed. those autopkgtests don't exist in g and earlier so this was not noticed until now. -- 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/1927779 Title: MODULES=list results in error Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: New Status in initramfs-tools source package in Focal: New Status in initramfs-tools source package in Groovy: New Bug description: [impact] setting MODULES=list in /etc/initramfs-tools/initramfs.conf results in an error/warning when running update-initramfs [test case] edit initramfs.conf to change MODULES=list and run update-initramfs: $ grep MODULES /etc/initramfs-tools/initramfs.conf # MODULES: [ most | netboot | dep | list ] MODULES=list $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.8.0-48-generic find: ‘/var/tmp/mkinitramfs_Yr04uh/lib/modules/5.8.0-48-generic/kernel’: No such file or directory [regression potential] any regression would likely result in an initramfs that did not include the correct/required modules, and/or failure to build a new initramfs [scope] this is needed for g and earlier. this is not fixed in debian, but is fixed in h and i. for debian, MR open: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/48 [other info] this caused some of the 'amd64-*' autopkgtests to fail in h until it was fixed. those autopkgtests don't exist in g and earlier so this was not noticed until now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1927779/+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
