[Touch-packages] [Bug 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'
per quick test, we need focal/apt 2.0.5 to fix this issue. -- 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/1923150 Title: unexpected error pop-up after 'apt install nvidia-driver-455' Status in OEM Priority Project: Confirmed Status in apt package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-455 package in Ubuntu: Incomplete Bug description: Ubuntu info: $ lsb_release -rd Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52) Release 20.04 Full reproduce step 1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first place, without all i386 pkg installed. 2. run update-manager to do upgrade. 3. it will show error after download deb and didn't upgrade anything. Per test with the command to do the upgrade, it will have an extra error message, but it will just upgrade and install recommended i386 debs. The error msgs are: E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) Short way to get the error: # apt-get install libgcc-s1:i386 --dry-run Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16 libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate Use 'apt autoremove' to remove them. The following additional packages will be installed: gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 libunistring2:i386 Suggested packages: glibc-doc glibc-doc:i386 locales:i386 The following NEW packages will be installed: gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 libunistring2:i386 The following packages will be upgraded: libc6 1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded. Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) [] Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) [] Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) For now, we think the above Error is the root cause of update-manager failure. --- This happens as upgrade package nvidia-driver-455 from 455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1. for more detail, please check the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923150/+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 1924667] [NEW] Once in a while, xorg crashes after a restart.
Public bug reported: [ 1681.827] (II) FBDEV: driver for framebuffer: fbdev [ 1681.827] (II) VESA: driver for VESA chipsets: vesa [ 1681.828] (**) modeset(0): claimed PCI slot 0@0:2:0 [ 1681.828] (II) modeset(0): using default device [ 1681.828] (WW) Falling back to old probe method for fbdev [ 1681.828] (II) Loading sub module "fbdevhw" [ 1681.828] (II) LoadModule: "fbdevhw" [ 1681.828] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so [ 1681.828] (II) Module fbdevhw: vendor="X.Org Foundation" [ 1681.828]compiled for 1.20.8, module version = 0.0.2 [ 1681.828]ABI class: X.Org Video Driver, version 24.1 [ 1681.828] (II) modeset(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [ 1681.828] (==) modeset(0): Depth 24, (==) framebuffer bpp 32 [ 1681.828] (EE) [ 1681.828] (EE) Backtrace: [ 1681.829] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x563983d6277c] [ 1681.829] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f7d9807041f] [ 1681.829] (EE) 2: /usr/lib/xorg/Xorg (xf86PlatformMatchDriver+0x5b0) [0x563983c5c400] [ 1681.829] (EE) 3: /usr/lib/xorg/Xorg (xf86CollectOptions+0x77) [0x563983c3f227] [ 1681.829] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 1681.829] (EE) 4: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f7d97845bd0] [ 1681.829] (EE) 5: /usr/lib/xorg/Xorg (InitOutput+0xb94) [0x563983c42be4] [ 1681.829] (EE) 6: /usr/lib/xorg/Xorg (InitFonts+0x1d4) [0x563983c04e34] [ 1681.829] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7f7d97e8e0b3] [ 1681.829] (EE) 8: /usr/lib/xorg/Xorg (_start+0x2e) [0x563983beea7e] [ 1681.829] (EE) [ 1681.829] (EE) Segmentation fault at address 0x124 [ 1681.829] (EE) Fatal server error: [ 1681.829] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 1681.829] (EE) [ 1681.829] (EE) I am using Ubuntu 20.04. When I reboot my laptop, the screen will probably go grey. After checking the log, I find the error message above. ** Affects: xorg (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/1924667 Title: Once in a while, xorg crashes after a restart. Status in xorg package in Ubuntu: New Bug description: [ 1681.827] (II) FBDEV: driver for framebuffer: fbdev [ 1681.827] (II) VESA: driver for VESA chipsets: vesa [ 1681.828] (**) modeset(0): claimed PCI slot 0@0:2:0 [ 1681.828] (II) modeset(0): using default device [ 1681.828] (WW) Falling back to old probe method for fbdev [ 1681.828] (II) Loading sub module "fbdevhw" [ 1681.828] (II) LoadModule: "fbdevhw" [ 1681.828] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so [ 1681.828] (II) Module fbdevhw: vendor="X.Org Foundation" [ 1681.828] compiled for 1.20.8, module version = 0.0.2 [ 1681.828] ABI class: X.Org Video Driver, version 24.1 [ 1681.828] (II) modeset(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [ 1681.828] (==) modeset(0): Depth 24, (==) framebuffer bpp 32 [ 1681.828] (EE) [ 1681.828] (EE) Backtrace: [ 1681.829] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x563983d6277c] [ 1681.829] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f7d9807041f] [ 1681.829] (EE) 2: /usr/lib/xorg/Xorg (xf86PlatformMatchDriver+0x5b0) [0x563983c5c400] [ 1681.829] (EE) 3: /usr/lib/xorg/Xorg (xf86CollectOptions+0x77) [0x563983c3f227] [ 1681.829] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 1681.829] (EE) 4: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f7d97845bd0] [ 1681.829] (EE) 5: /usr/lib/xorg/Xorg (InitOutput+0xb94) [0x563983c42be4] [ 1681.829] (EE) 6: /usr/lib/xorg/Xorg (InitFonts+0x1d4) [0x563983c04e34] [ 1681.829] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7f7d97e8e0b3] [ 1681.829] (EE) 8: /usr/lib/xorg/Xorg (_start+0x2e) [0x563983beea7e] [ 1681.829] (EE) [ 1681.829] (EE) Segmentation fault at address 0x124 [ 1681.829] (EE) Fatal server error: [ 1681.829] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 1681.829] (EE) [ 1681.829] (EE) I am using Ubuntu 20.04. When I reboot my laptop, the screen will probably go grey. After checking the log, I find the error message above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924667/+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 1924623] Re: Bluetooth headset pairing issue (HOCO ES32 PLUS)
** Summary changed: - Bluetooth headset pairing issue + Bluetooth headset pairing issue (HOCO ES32 PLUS) -- 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/1924623 Title: Bluetooth headset pairing issue (HOCO ES32 PLUS) Status in bluez package in Ubuntu: New Bug description: I am unable to connect a HOCO ES32 PLUS bluetooth headset. Device is visible and in pairable mode, but after running: bluetoothctl [bluetooth]# show Controller 04:33:C2:AA:17:60 (public) Name: mykyt Alias: mykyt Class: 0x001c010c Powered: yes Discoverable: yes DiscoverableTimeout: 0x Pairable: yes UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) UUID: Message Access Server (1132--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) UUID: Vendor specific (5005--1000-8000-0002ee01) UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0535 Discovering: yes Advertising Features: ActiveInstances: 0x00 SupportedInstances: 0x05 SupportedIncludes: tx-power SupportedIncludes: appearance SupportedIncludes: local-name SupportedSecondaryChannels: 1M SupportedSecondaryChannels: 2M SupportedSecondaryChannels: Coded i get: Failed to pair: org.bluez.Error.AuthenticationTimeout or Failed to pair: org.bluez.Error.AuthenticationCanceled or Failed to pair: org.bluez.Error.Failed I tried every single solution i was able to find for similar problems, including changing controller mode to bredr, reinstalling pulseaudio, unblocking rfkill, checking if my device is in pairable mode, using blueman and so on. The fact is, bluetooth is working on my laptop (I can connect to my phone and my other bluetooth headset MEIZU EP51) and also my headset HOCO ES32 PLUS is working and is able to connect to my phone and my other laptop DELL INSPIRON 7359 which is running on ubuntu 18.04. I really hope you can help me. Please tell me if you need more information and I will provide it. Thank you! -- lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 apt-cache policy bluez bluez: Installed: 5.53-0ubuntu3 Candidate: 5.53-0ubuntu3 Version table: *** 5.53-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status -- Expected behavior: After turning on bluetooth and clicking on device name in settings -> bluetooth device is connecting and pairing successfully. Current behavior: Pairing fails. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 16 00:28:19 2021 InstallationDate: Installed on 2020-08-27 (231 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Swift SF314-57G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=59c2b478-ae5a-4c28-8c13-6b3721fe1f3b ro nouveau.modeset=0 quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2020 dmi.bios.release: 1.14 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Floris_IL dmi.board.vendor: IL dmi.board.version: V1.14 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.14 dmi.modalias:
[Touch-packages] [Bug 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'
For completeness, apt pkg versions in focal are focal: 2.0.2 focal-security: 2.0.2ubuntu0.2 focal-update 2.0.5 If 2.0.2ubuntu0.2 can cover this, then we are all clear, since it will be upgraded by unattended upgrade. -- 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/1923150 Title: unexpected error pop-up after 'apt install nvidia-driver-455' Status in OEM Priority Project: Confirmed Status in apt package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-455 package in Ubuntu: Incomplete Bug description: Ubuntu info: $ lsb_release -rd Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52) Release 20.04 Full reproduce step 1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first place, without all i386 pkg installed. 2. run update-manager to do upgrade. 3. it will show error after download deb and didn't upgrade anything. Per test with the command to do the upgrade, it will have an extra error message, but it will just upgrade and install recommended i386 debs. The error msgs are: E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) Short way to get the error: # apt-get install libgcc-s1:i386 --dry-run Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16 libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate Use 'apt autoremove' to remove them. The following additional packages will be installed: gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 libunistring2:i386 Suggested packages: glibc-doc glibc-doc:i386 locales:i386 The following NEW packages will be installed: gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 libunistring2:i386 The following packages will be upgraded: libc6 1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded. Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) [] Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) [] Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) For now, we think the above Error is the root cause of update-manager failure. --- This happens as upgrade package nvidia-driver-455 from 455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1. for more detail, please check the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923150/+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 1922266] Re: eth0 interface name change fails on Pi 3/3+
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1922266 Title: eth0 interface name change fails on Pi 3/3+ Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-meta source package in Hirsute: Fix Released Status in ubuntu-settings source package in Hirsute: New Bug description: The netplan configuration in ubuntu-raspi-settings (and more widely, the network-config in the gadget used on the server images) fails to rename the internal ethernet interface on Pi 3B and 3B+ models from "en" to "eth0". In the netplan case this is because the driver matching logic doesn't handle space-separate driver matches (although the underlying networkd system does); in the cloud-init case it simply refuses to rename interfaces that aren't matched by full MAC address. The intended fix is to stop attempting to do this via netplan or cloud-init, and simply handle this via a networkd .link file in ubuntu-raspi-settings. This will require an update to the relevant seeds as this package is currently only pulled into ubuntu-desktop- raspi, not ubuntu-server-raspi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1922266/+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
Hello Seyeong, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.47 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- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. 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: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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 Committed 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 1909918] Re: software-properties-gtk crashed with AttributeError in __init__(): 'ElementTree' object has no attribute 'getiterator'
as pointed out in bug #1923553 , this bug affects all the various software-properties gui's (including software-properties-qt, software- properties-kde), not just software-properties-gtk. it is also mentioned in the other bug report that the issue seems to be that the underlying python code being called is using the long deprecated and now removed "getiterator" method in ElementTree to generate the list of "other" download sources. -- 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/1909918 Title: software-properties-gtk crashed with AttributeError in __init__(): 'ElementTree' object has no attribute 'getiterator' Status in software-properties package in Ubuntu: In Progress Bug description: lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.99.5 Candidate: 0.99.5 Version table: *** 0.99.5 500 500 http://nl.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: software-properties-gtk 0.99.5 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sun Jan 3 17:37:55 2021 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2021-01-03 (0 days ago) InstallationMedia: Ubuntu-Server 21.04 "Hirsute Hippo" - Alpha amd64 (20201231) InterpreterPath: /usr/bin/python3.9 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.9, Python 3.9.1, python3-minimal, 3.9.0-3ubuntu1 PythonArgs: ['/usr/bin/software-properties-gtk'] PythonDetails: N/A SourcePackage: software-properties Title: software-properties-gtk crashed with AttributeError in __init__(): 'ElementTree' object has no attribute 'getiterator' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1909918/+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 1923553] Re: software-properties gui python exception on selecting "other" package source
*** This bug is a duplicate of bug 1909918 ***
https://bugs.launchpad.net/bugs/1909918
updated bug #1909918 with the extra info.
--
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/1923553
Title:
software-properties gui python exception on selecting "other" package
source
Status in software-properties package in Ubuntu:
New
Bug description:
on hirsute (21.04) software-properties-qt (software-properties-
qt/hirsute 0.99.8) (also callable as software-properties-kde) throws a
python exception when a package download source of "other" is
selected. the same underlying error occurs when using software-
properties-gtk (software-properties-gtk/hirsute 0.99.8).
this python traceback appears in the console for the qt gui:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py",
line 454, in on_combobox_server_changed
dialogue = DialogMirror(self.userinterface, self.datadir, self.distro,
self.custom_mirrors)
File
"/usr/lib/python3/dist-packages/softwareproperties/qt/DialogMirror.py", line
55, in __init__
self.country_info = CountryInformation()
File
"/usr/lib/python3/dist-packages/softwareproperties/CountryInformation.py", line
34, in __init__
it = et.getiterator('iso_3166_entry')
AttributeError: 'ElementTree' object has no attribute 'getiterator'
and this appears for the gtk gui:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 661, in on_combobox_server_changed
dialog = DialogMirror(self.window_main,
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogMirror.py", line
85, in __init__
self.country_info = CountryInformation()
File
"/usr/lib/python3/dist-packages/softwareproperties/CountryInformation.py", line
34, in __init__
it = et.getiterator('iso_3166_entry')
AttributeError: 'ElementTree' object has no attribute 'getiterator'
i assume the underlying python code being called is using the long deprecated
and now removed "getiterator" method in ElementTree to generate the list of
"other" download sources.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1923553/+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 1923553] Re: software-properties gui python exception on selecting "other" package source
*** This bug is a duplicate of bug 1909918 ***
https://bugs.launchpad.net/bugs/1909918
yes bug #1909918 mentions the same issue, but my report has a little
more info on what the underlying python problem is and also mentions
that it occurs in all the various software-properties gui's, not just
software-properties-gtk as is stated in the the other bug report.
--
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/1923553
Title:
software-properties gui python exception on selecting "other" package
source
Status in software-properties package in Ubuntu:
New
Bug description:
on hirsute (21.04) software-properties-qt (software-properties-
qt/hirsute 0.99.8) (also callable as software-properties-kde) throws a
python exception when a package download source of "other" is
selected. the same underlying error occurs when using software-
properties-gtk (software-properties-gtk/hirsute 0.99.8).
this python traceback appears in the console for the qt gui:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py",
line 454, in on_combobox_server_changed
dialogue = DialogMirror(self.userinterface, self.datadir, self.distro,
self.custom_mirrors)
File
"/usr/lib/python3/dist-packages/softwareproperties/qt/DialogMirror.py", line
55, in __init__
self.country_info = CountryInformation()
File
"/usr/lib/python3/dist-packages/softwareproperties/CountryInformation.py", line
34, in __init__
it = et.getiterator('iso_3166_entry')
AttributeError: 'ElementTree' object has no attribute 'getiterator'
and this appears for the gtk gui:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 661, in on_combobox_server_changed
dialog = DialogMirror(self.window_main,
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogMirror.py", line
85, in __init__
self.country_info = CountryInformation()
File
"/usr/lib/python3/dist-packages/softwareproperties/CountryInformation.py", line
34, in __init__
it = et.getiterator('iso_3166_entry')
AttributeError: 'ElementTree' object has no attribute 'getiterator'
i assume the underlying python code being called is using the long deprecated
and now removed "getiterator" method in ElementTree to generate the list of
"other" download sources.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1923553/+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 1924623] Re: Bluetooth headset pairing issue
** Description changed: I am unable to connect a HOCO ES32 PLUS bluetooth headset. Device is visible and in pairable mode, but after running: bluetoothctl [bluetooth]# show Controller 04:33:C2:AA:17:60 (public) - Name: mykyt - Alias: mykyt - Class: 0x001c010c - Powered: yes - Discoverable: yes - DiscoverableTimeout: 0x - Pairable: yes - UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) - UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) - UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) - UUID: Message Access Server (1132--1000-8000-00805f9b34fb) - UUID: PnP Information (1200--1000-8000-00805f9b34fb) - UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) - UUID: Vendor specific (5005--1000-8000-0002ee01) - UUID: Headset AG(1112--1000-8000-00805f9b34fb) - UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) - UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) - UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) - UUID: Audio Sink(110b--1000-8000-00805f9b34fb) - UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) - UUID: Headset (1108--1000-8000-00805f9b34fb) - UUID: Audio Source (110a--1000-8000-00805f9b34fb) - UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb) - Modalias: usb:v1D6Bp0246d0535 - Discovering: yes + Name: mykyt + Alias: mykyt + Class: 0x001c010c + Powered: yes + Discoverable: yes + DiscoverableTimeout: 0x + Pairable: yes + UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) + UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) + UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) + UUID: Message Access Server (1132--1000-8000-00805f9b34fb) + UUID: PnP Information (1200--1000-8000-00805f9b34fb) + UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) + UUID: Vendor specific (5005--1000-8000-0002ee01) + UUID: Headset AG(1112--1000-8000-00805f9b34fb) + UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) + UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) + UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) + UUID: Audio Sink(110b--1000-8000-00805f9b34fb) + UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) + UUID: Headset (1108--1000-8000-00805f9b34fb) + UUID: Audio Source (110a--1000-8000-00805f9b34fb) + UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb) + Modalias: usb:v1D6Bp0246d0535 + Discovering: yes Advertising Features: - ActiveInstances: 0x00 - SupportedInstances: 0x05 - SupportedIncludes: tx-power - SupportedIncludes: appearance - SupportedIncludes: local-name - SupportedSecondaryChannels: 1M - SupportedSecondaryChannels: 2M - SupportedSecondaryChannels: Coded - + ActiveInstances: 0x00 + SupportedInstances: 0x05 + SupportedIncludes: tx-power + SupportedIncludes: appearance + SupportedIncludes: local-name + SupportedSecondaryChannels: 1M + SupportedSecondaryChannels: 2M + SupportedSecondaryChannels: Coded i get: Failed to pair: org.bluez.Error.AuthenticationTimeout or Failed to pair: org.bluez.Error.AuthenticationCanceled + or - I tried every single solution i was able to find for similar problems, including changing controller mode to bredr, reinstalling pulseaudio, unblocking rfkill, checking if my device is in pairable mode, using blueman and so on. + Failed to pair: org.bluez.Error.Failed + + I tried every single solution i was able to find for similar problems, + including changing controller mode to bredr, reinstalling pulseaudio, + unblocking rfkill, checking if my device is in pairable mode, using + blueman and so on. The fact is, bluetooth is working on my laptop (I can connect to my phone and my other bluetooth headset MEIZU EP51) and also my headset HOCO ES32 PLUS is working and is able to connect to my phone and my other laptop DELL INSPIRON 7359 which is running on ubuntu 18.04. I really hope you can help me. Please tell me if you need more information and I will provide it. Thank you! -- lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 - apt-cache policy bluez bluez: - Installed: 5.53-0ubuntu3 - Candidate: 5.53-0ubuntu3 -
[Touch-packages] [Bug 1922266] Re: eth0 interface name change fails on Pi 3/3+
** Also affects: ubuntu-meta (Ubuntu Hirsute) Importance: Undecided Status: Fix Released ** Also affects: ubuntu-settings (Ubuntu Hirsute) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1922266 Title: eth0 interface name change fails on Pi 3/3+ Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-meta source package in Hirsute: Fix Released Status in ubuntu-settings source package in Hirsute: New Bug description: The netplan configuration in ubuntu-raspi-settings (and more widely, the network-config in the gadget used on the server images) fails to rename the internal ethernet interface on Pi 3B and 3B+ models from "en" to "eth0". In the netplan case this is because the driver matching logic doesn't handle space-separate driver matches (although the underlying networkd system does); in the cloud-init case it simply refuses to rename interfaces that aren't matched by full MAC address. The intended fix is to stop attempting to do this via netplan or cloud-init, and simply handle this via a networkd .link file in ubuntu-raspi-settings. This will require an update to the relevant seeds as this package is currently only pulled into ubuntu-desktop- raspi, not ubuntu-server-raspi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1922266/+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 1924623] [NEW] Bluetooth headset pairing issue
Public bug reported: I am unable to connect a HOCO ES32 PLUS bluetooth headset. Device is visible and in pairable mode, but after running: bluetoothctl [bluetooth]# show Controller 04:33:C2:AA:17:60 (public) Name: mykyt Alias: mykyt Class: 0x001c010c Powered: yes Discoverable: yes DiscoverableTimeout: 0x Pairable: yes UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) UUID: Message Access Server (1132--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) UUID: Vendor specific (5005--1000-8000-0002ee01) UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0535 Discovering: yes Advertising Features: ActiveInstances: 0x00 SupportedInstances: 0x05 SupportedIncludes: tx-power SupportedIncludes: appearance SupportedIncludes: local-name SupportedSecondaryChannels: 1M SupportedSecondaryChannels: 2M SupportedSecondaryChannels: Coded i get: Failed to pair: org.bluez.Error.AuthenticationTimeout or Failed to pair: org.bluez.Error.AuthenticationCanceled or Failed to pair: org.bluez.Error.Failed I tried every single solution i was able to find for similar problems, including changing controller mode to bredr, reinstalling pulseaudio, unblocking rfkill, checking if my device is in pairable mode, using blueman and so on. The fact is, bluetooth is working on my laptop (I can connect to my phone and my other bluetooth headset MEIZU EP51) and also my headset HOCO ES32 PLUS is working and is able to connect to my phone and my other laptop DELL INSPIRON 7359 which is running on ubuntu 18.04. I really hope you can help me. Please tell me if you need more information and I will provide it. Thank you! -- lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 apt-cache policy bluez bluez: Installed: 5.53-0ubuntu3 Candidate: 5.53-0ubuntu3 Version table: *** 5.53-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status -- Expected behavior: After turning on bluetooth and clicking on device name in settings -> bluetooth device is connecting and pairing successfully. Current behavior: Pairing fails. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 16 00:28:19 2021 InstallationDate: Installed on 2020-08-27 (231 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Swift SF314-57G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=59c2b478-ae5a-4c28-8c13-6b3721fe1f3b ro nouveau.modeset=0 quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2020 dmi.bios.release: 1.14 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Floris_IL dmi.board.vendor: IL dmi.board.version: V1.14 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.14:bd05/06/2020:br1.14:efr1.14:svnAcer:pnSwiftSF314-57G:pvrV1.14:rvnIL:rnFloris_IL:rvrV1.14:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-57G dmi.product.sku: dmi.product.version: V1.14 dmi.sys.vendor: Acer hciconfig: hci0: Type: Primary Bus: USB BD Address: 04:33:C2:AA:17:60 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:39055 acl:127 sco:0 events:3605 errors:0 TX bytes:791744 acl:182 sco:0 commands:3327 errors:0 mtime.conffile..etc.bluetooth.network.conf: 2021-04-15T23:51:23.664531 ** Affects: bluez (Ubuntu) Importance:
[Touch-packages] [Bug 1922266] Re: eth0 interface name change fails on Pi 3/3+
Attaching debdiff; test builds are available from the following PPA: https://launchpad.net/~waveform/+archive/ubuntu/ubuntu- settings/+packages ** Patch added: "1-1922266.debdiff" https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1922266/+attachment/5488517/+files/1-1922266.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1922266 Title: eth0 interface name change fails on Pi 3/3+ Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: New Bug description: The netplan configuration in ubuntu-raspi-settings (and more widely, the network-config in the gadget used on the server images) fails to rename the internal ethernet interface on Pi 3B and 3B+ models from "en" to "eth0". In the netplan case this is because the driver matching logic doesn't handle space-separate driver matches (although the underlying networkd system does); in the cloud-init case it simply refuses to rename interfaces that aren't matched by full MAC address. The intended fix is to stop attempting to do this via netplan or cloud-init, and simply handle this via a networkd .link file in ubuntu-raspi-settings. This will require an update to the relevant seeds as this package is currently only pulled into ubuntu-desktop- raspi, not ubuntu-server-raspi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1922266/+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 1274613] Re: module-bluetooth-discover does not load on login
Same problem still persists on focal. module-bluetooth-discover is not loaded when the system is started up and can`t be manually loaded too. Please reach out if you need more info. -- 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/1274613 Title: module-bluetooth-discover does not load on login Status in pulseaudio package in Ubuntu: Triaged Bug description: The following lines appear in /etc/pulse/default.pa, which I have not modified: .ifexists module-bluetooth-discover.so load-module module-bluetooth-discover .endif Expected: module-bluetooth-discover is loaded on login, as configured. Observed: pulseaudio's module-bluetooth-discover does not load on login. My system does not detect and set up sinks when I connect to Bluetooth devices (including an A2DP speaker and a headset). If I issue, in a terminal window: $ pactl load-module module-bluetooth-discover 24 …then the devices are detected and sinks set up correctly. $ lsb_release -rd && apt-cache policy pulseaudio-module-bluetooth Description:Ubuntu 13.10 Release:13.10 pulseaudio-module-bluetooth: Installed: 1:4.0-0ubuntu6 Candidate: 1:4.0-0ubuntu6 Version table: *** 1:4.0-0ubuntu6 0 500 http://mirrors.mit.edu/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.30-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: khaeru 2051 F pulseaudio Date: Thu Jan 30 12:18:50 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2012-10-29 (457 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to saucy on 2013-09-11 (140 days ago) dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 085VR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn085VR5:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1274613/+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.4-1ubuntu3 --- alsa-utils (1.2.4-1ubuntu3) hirsute; 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 16:27:22 +0800 ** Changed in: alsa-utils (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 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 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 310262] Re: APT::Acquire::Retries only applies to archives and source files
This was fixed in Version: 1.6~alpha6 ** Changed in: apt (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 apt in Ubuntu. https://bugs.launchpad.net/bugs/310262 Title: APT::Acquire::Retries only applies to archives and source files Status in apt package in Ubuntu: Fix Released Status in apt package in Debian: Fix Released Bug description: Binary package hint: apt The APT::Acquire::Retries configuration directive for apt only applies to source and archive, not the various index files (Packages, Release and friends). Intuitively, you would think that it should, but it does not. As far as I can tell, there is no other equivalent directive that would restrict the number of time apt should try to fetch an index case before it give up. This can trigger a relatively rare problem where apt would try to download the same index file again and again, forever until stopped, if the download systematically fail abruptly midway. See LP #291748 for such an example. If apt is being run automatically in the background, this could end consuming a lot of bandwidth and hammer the archive pretty badly before someone notice. According to long-standing upstream Debian bug #119544, fixing this bug would be a relatively trivial code change, but would break the ABI. As such, I would be curious to know if there is an ABI bump on apt roadmap; if yes, would it be possible to nominate this bug for the next major release of apt? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/310262/+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 1924597] [NEW] package openssh-server 1:8.3p1-1ubuntu0.1 failed to install/upgrade: podproces zainstalowany pakiet openssh-server skrypt post-installation zwrócił kod błędu 1
Public bug reported: that happen when i try to install ssh ProblemType: Package DistroRelease: Ubuntu 20.10 Package: openssh-server 1:8.3p1-1ubuntu0.1 ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 AptOrdering: ncurses-term:amd64: Install openssh-sftp-server:amd64: Install openssh-server:amd64: Install ssh-import-id:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Apr 15 19:12:21 2021 ErrorMessage: podproces zainstalowany pakiet openssh-server skrypt post-installation zwrócił kod błędu 1 InstallationDate: Installed on 2021-04-15 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: gnome-shell RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.3 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: /etc/ssh/sshd_config: No such file or directory SourcePackage: openssh Title: package openssh-server 1:8.3p1-1ubuntu0.1 failed to install/upgrade: podproces zainstalowany pakiet openssh-server skrypt post-installation zwrócił kod błędu 1 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.ssh.moduli: [deleted] ** Affects: openssh (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 openssh in Ubuntu. https://bugs.launchpad.net/bugs/1924597 Title: package openssh-server 1:8.3p1-1ubuntu0.1 failed to install/upgrade: podproces zainstalowany pakiet openssh-server skrypt post-installation zwrócił kod błędu 1 Status in openssh package in Ubuntu: New Bug description: that happen when i try to install ssh ProblemType: Package DistroRelease: Ubuntu 20.10 Package: openssh-server 1:8.3p1-1ubuntu0.1 ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 AptOrdering: ncurses-term:amd64: Install openssh-sftp-server:amd64: Install openssh-server:amd64: Install ssh-import-id:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Apr 15 19:12:21 2021 ErrorMessage: podproces zainstalowany pakiet openssh-server skrypt post-installation zwrócił kod błędu 1 InstallationDate: Installed on 2021-04-15 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: gnome-shell RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.3 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: /etc/ssh/sshd_config: No such file or directory SourcePackage: openssh Title: package openssh-server 1:8.3p1-1ubuntu0.1 failed to install/upgrade: podproces zainstalowany pakiet openssh-server skrypt post-installation zwrócił kod błędu 1 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.ssh.moduli: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1924597/+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 1896171] Re: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver)
This bug was fixed in the package mutter - 3.38.4-1ubuntu2 --- mutter (3.38.4-1ubuntu2) hirsute; urgency=medium [ Daniel van Vugt ] * Revert "debian/patches: Properly handle configuration events on windows" to fix a regression making some windows to move on resize (LP: #1922034). * Add 61-mutter.rules-Enable-KMS-modifiers-for-Raspberry-P.patch. To enable KMS modifiers on Raspberry Pi, which means to enable the first fix in wayland-dma-buf-Add-support-for-DRM_FORMAT_ABGR2101010.patch (LP: #1896171) [ Marco Trevisan (Treviño) ] * debian/patches: Backport workspace fixes from upstream gnome-3-38 branch * debian/patches: Use Xwayland pkg-config if available * debian/patches: Use -listenfd to invoke XWayland if available (LP: #1922539) -- Marco Trevisan (Treviño) Thu, 15 Apr 2021 06:28:51 +0200 ** Changed in: mutter (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 mesa in Ubuntu. https://bugs.launchpad.net/bugs/1896171 Title: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver) Status in Mutter: Unknown Status in mesa package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Bug description: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver). Seen in glmark2-wayland, glmark2-es2-wayland, weston-simple-egl. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1896171/+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 1923541] Re: /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError: 'CasperMD5json'
This bug was fixed in the package apport - 2.20.11-0ubuntu65 --- apport (2.20.11-0ubuntu65) hirsute; urgency=medium * test/test_backend_apt_dpkg.py: libc6 recommends packages, some of which are not installed on buildds now, so switch to testing libc-bin which only has dependencies and is what the test is supposed to test. -- Brian Murray Wed, 14 Apr 2021 13:52:22 -0700 ** Changed in: apport (Ubuntu Hirsute) Status: In Progress => 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/1923541 Title: /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError: 'CasperMD5json' Status in apport package in Ubuntu: Fix Released Status in apport source package in Hirsute: Fix Released Bug description: Currently running 21.04, apport version is 2.20.11-0ubuntu62 . When I try to fill a bug, I see: $ ubuntu-bug network-manager 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 1002, in attach_casper_md5check del report['CasperMD5json'] File "/usr/lib/python3.9/collections/__init__.py", line 1064, in __delitem__ del self.data[key] KeyError: 'CasperMD5json' It's not crashing the bug reporting itself, but it looks wrong to have a stacktrace on the command line. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1923541/+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 264313] Re: ls --color hangs for directories linked from network
I do think the fact that a workaround exists is not enough. I really think the default behaviour in Ubuntu of a oft-used command should not create hangs of well over a minute in fairly standard circumstances. It also hangs on links that are not accessible because they have not been Kerberos authenticated or are on unmounted USB devices. So I do think the default should at least be changed here. It is unreasonable default behaviour, not least because it is really unobvious to most users why it happens. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/264313 Title: ls --color hangs for directories linked from network Status in coreutils package in Ubuntu: Confirmed Bug description: Binary package hint: coreutils ls --color hangs for directories linked from network resources if those resources are not available I guess it hangs in trying to validate the link ( have not tried to wait and see if it times out or not ) easily reproducible. annoying since --color is default Running Ubuntu 8.0.4 2.6.24-21-generic #1 SMP Mon Aug 25 16:57:51 UTC 2008 x86_64 GNU/Linux ls (GNU coreutils) 6.10 ISSUE: since ls --color will try to determine if a symlink is broken or not (so that it will be correctly coloured), it *will* timeout on vanished resources. WORKAROUND: Inhibit 'ls' from following symlinks (at least in the context of --color): eval `dircolors -b | sed s/or=[^:]*://` Add the above to your profile. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/264313/+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 1924594] Re: libgmock-dev build dependency needed
** Merge proposal linked: https://code.launchpad.net/~hellsworth/ubuntu/+source/indicator-power/+git/indicator-power/+merge/401240 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1924594 Title: libgmock-dev build dependency needed Status in indicator-power package in Ubuntu: New Bug description: indicator-power no longer builds. make[3]: *** No rule to make target 'tests/gmock/libgmock_main.a', needed by 'tests/test-notify'. Stop. The build failure: https://launchpadlibrarian.net/532498126 /buildlog_ubuntu-hirsute-amd64.indicator- power_12.10.6+17.10.20170829.1-0ubuntu6_BUILDING.txt.gz If you install libgmock-dev in the build environment first, it fixes the build problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1924594/+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 1924594] [NEW] libgmock-dev build dependency needed
Public bug reported: indicator-power no longer builds. make[3]: *** No rule to make target 'tests/gmock/libgmock_main.a', needed by 'tests/test-notify'. Stop. The build failure: https://launchpadlibrarian.net/532498126 /buildlog_ubuntu-hirsute-amd64.indicator- power_12.10.6+17.10.20170829.1-0ubuntu6_BUILDING.txt.gz If you install libgmock-dev in the build environment first, it fixes the build problem. ** Affects: indicator-power (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1924594 Title: libgmock-dev build dependency needed Status in indicator-power package in Ubuntu: New Bug description: indicator-power no longer builds. make[3]: *** No rule to make target 'tests/gmock/libgmock_main.a', needed by 'tests/test-notify'. Stop. The build failure: https://launchpadlibrarian.net/532498126 /buildlog_ubuntu-hirsute-amd64.indicator- power_12.10.6+17.10.20170829.1-0ubuntu6_BUILDING.txt.gz If you install libgmock-dev in the build environment first, it fixes the build problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1924594/+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 1924583] Re: ASPEED AST driver seems unstable in 20.04.2 LTS
** 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/1924583 Title: ASPEED AST driver seems unstable in 20.04.2 LTS Status in xorg package in Ubuntu: New Bug description: I have had the screen go blank several times. Each time that this occurred, I was selecting the "Settings" item from the upper right corner arrow. Perhaps there are a lot of low level accesses that occur when this menu item is selected that somehow locks up the ASPEED AST driver or some other part of the display? When this problem occurs, the only way I have been able to recover is to power cycle the system. The info collected for this bug report was taken after rebooting the system. I originally had a problem that the initial login screen did not display (blank screen) but I came across the following that provided a solution of disable Wayland: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872091 I am not able to reproduce the problem at will. I can usually access the "Settings" without a problem. However, each time the screen has gone blank it was right after clicking on the "Settings" menu item. I have six identical machines (Supermicro SYS-5019C-FL) and this problem has occurred on several of them. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 15 08:16:08 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 41) (prog-if 00 [VGA controller]) Subsystem: Super Micro Computer Inc ASPEED Graphics Family [15d9:1b0e] InstallationDate: Installed on 2021-04-13 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Supermicro Super Server ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=9242ef3a-0904-41c6-8ee2-4c224bb71e1a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2020 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11SCL-IF dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.5:bd10/05/2020:br5.13:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SCL-IF:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro 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/xorg/+bug/1924583/+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 1924583] [NEW] ASPEED AST driver seems unstable in 20.04.2 LTS
You have been subscribed to a public bug: I have had the screen go blank several times. Each time that this occurred, I was selecting the "Settings" item from the upper right corner arrow. Perhaps there are a lot of low level accesses that occur when this menu item is selected that somehow locks up the ASPEED AST driver or some other part of the display? When this problem occurs, the only way I have been able to recover is to power cycle the system. The info collected for this bug report was taken after rebooting the system. I originally had a problem that the initial login screen did not display (blank screen) but I came across the following that provided a solution of disable Wayland: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872091 I am not able to reproduce the problem at will. I can usually access the "Settings" without a problem. However, each time the screen has gone blank it was right after clicking on the "Settings" menu item. I have six identical machines (Supermicro SYS-5019C-FL) and this problem has occurred on several of them. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 15 08:16:08 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 41) (prog-if 00 [VGA controller]) Subsystem: Super Micro Computer Inc ASPEED Graphics Family [15d9:1b0e] InstallationDate: Installed on 2021-04-13 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Supermicro Super Server ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=9242ef3a-0904-41c6-8ee2-4c224bb71e1a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2020 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11SCL-IF dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.5:bd10/05/2020:br5.13:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SCL-IF:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro 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 ubuntu -- ASPEED AST driver seems unstable in 20.04.2 LTS https://bugs.launchpad.net/bugs/1924583 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 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'
** Tags removed: rls-hh-incoming ** Tags added: rls-ff-incoming -- 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/1923150 Title: unexpected error pop-up after 'apt install nvidia-driver-455' Status in OEM Priority Project: Confirmed Status in apt package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-455 package in Ubuntu: Incomplete Bug description: Ubuntu info: $ lsb_release -rd Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52) Release 20.04 Full reproduce step 1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first place, without all i386 pkg installed. 2. run update-manager to do upgrade. 3. it will show error after download deb and didn't upgrade anything. Per test with the command to do the upgrade, it will have an extra error message, but it will just upgrade and install recommended i386 debs. The error msgs are: E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) Short way to get the error: # apt-get install libgcc-s1:i386 --dry-run Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16 libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate Use 'apt autoremove' to remove them. The following additional packages will be installed: gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 libunistring2:i386 Suggested packages: glibc-doc glibc-doc:i386 locales:i386 The following NEW packages will be installed: gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 libunistring2:i386 The following packages will be upgraded: libc6 1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded. Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) [] Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) [] Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) For now, we think the above Error is the root cause of update-manager failure. --- This happens as upgrade package nvidia-driver-455 from 455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1. for more detail, please check the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923150/+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 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'
20.04.1 is obsolete point release. Can you please try with 20.04.2? ** Changed in: nvidia-graphics-drivers-455 (Ubuntu) Status: New => Incomplete -- 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/1923150 Title: unexpected error pop-up after 'apt install nvidia-driver-455' Status in OEM Priority Project: Confirmed Status in apt package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-455 package in Ubuntu: Incomplete Bug description: Ubuntu info: $ lsb_release -rd Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52) Release 20.04 Full reproduce step 1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first place, without all i386 pkg installed. 2. run update-manager to do upgrade. 3. it will show error after download deb and didn't upgrade anything. Per test with the command to do the upgrade, it will have an extra error message, but it will just upgrade and install recommended i386 debs. The error msgs are: E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) Short way to get the error: # apt-get install libgcc-s1:i386 --dry-run Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16 libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate Use 'apt autoremove' to remove them. The following additional packages will be installed: gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 libunistring2:i386 Suggested packages: glibc-doc glibc-doc:i386 locales:i386 The following NEW packages will be installed: gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 libunistring2:i386 The following packages will be upgraded: libc6 1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded. Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) [] Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) [] Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) For now, we think the above Error is the root cause of update-manager failure. --- This happens as upgrade package nvidia-driver-455 from 455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1. for more detail, please check the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923150/+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 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'
I mean 2.0.4, of course, which is included in the current LTS images (20.04.2); your image is the previous version (20.04.1) -- 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/1923150 Title: unexpected error pop-up after 'apt install nvidia-driver-455' Status in OEM Priority Project: Confirmed Status in apt package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-455 package in Ubuntu: New Bug description: Ubuntu info: $ lsb_release -rd Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52) Release 20.04 Full reproduce step 1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first place, without all i386 pkg installed. 2. run update-manager to do upgrade. 3. it will show error after download deb and didn't upgrade anything. Per test with the command to do the upgrade, it will have an extra error message, but it will just upgrade and install recommended i386 debs. The error msgs are: E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) Short way to get the error: # apt-get install libgcc-s1:i386 --dry-run Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16 libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate Use 'apt autoremove' to remove them. The following additional packages will be installed: gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 libunistring2:i386 Suggested packages: glibc-doc glibc-doc:i386 locales:i386 The following NEW packages will be installed: gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 libunistring2:i386 The following packages will be upgraded: libc6 1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded. Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) [] Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) [] Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) For now, we think the above Error is the root cause of update-manager failure. --- This happens as upgrade package nvidia-driver-455 from 455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1. for more detail, please check the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923150/+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 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'
It seems you are not using libapt-pkg6.0 in version 2.1.10ubuntu0.2 or later? This issue was fixed in that version. ** Changed in: apt (Ubuntu) Status: New => Incomplete -- 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/1923150 Title: unexpected error pop-up after 'apt install nvidia-driver-455' Status in OEM Priority Project: Confirmed Status in apt package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-455 package in Ubuntu: New Bug description: Ubuntu info: $ lsb_release -rd Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52) Release 20.04 Full reproduce step 1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first place, without all i386 pkg installed. 2. run update-manager to do upgrade. 3. it will show error after download deb and didn't upgrade anything. Per test with the command to do the upgrade, it will have an extra error message, but it will just upgrade and install recommended i386 debs. The error msgs are: E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) Short way to get the error: # apt-get install libgcc-s1:i386 --dry-run Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16 libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate Use 'apt autoremove' to remove them. The following additional packages will be installed: gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 libunistring2:i386 Suggested packages: glibc-doc glibc-doc:i386 locales:i386 The following NEW packages will be installed: gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 libunistring2:i386 The following packages will be upgraded: libc6 1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded. Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) [] Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) [] Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) For now, we think the above Error is the root cause of update-manager failure. --- This happens as upgrade package nvidia-driver-455 from 455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1. for more detail, please check the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923150/+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 1924494] [NEW] Systemd shutdown order unmounts filesystem used by qemu/kvm guest before shutting down the guest
Public bug reported: Last night I started a reboot without manually shutting down a qemu/kvm guest first. After X went down a bunch of I/O errors associated with a network block device that contains a NTFS filesystem showed up on the console. I noticed that the umount.target had been reached but the virt-guest-shutdown.target was still waiting for the guest to shut down, until it timed out. Wouldn't it be beneficial for all guests to be shutdown before unmounting all filesystems? ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246.6-1ubuntu1.3 ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Apr 15 08:35:48 2021 InstallationDate: Installed on 2021-01-17 (88 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP ZBook 15u G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=25df7fed-1baf-421e-941e-7f7c280db6e8 ro iommu=pt intel_iommu=on default_hugepagesz=1G hugepagesz=1G hugepages=6 pcie_aspm.policy=performance SourcePackage: systemd UpgradeStatus: Upgraded to groovy on 2021-04-08 (6 days ago) dmi.bios.date: 01/08/2021 dmi.bios.release: 8.1 dmi.bios.vendor: HP dmi.bios.version: R70 Ver. 01.08.01 dmi.board.name: 8549 dmi.board.vendor: HP dmi.board.version: KBC Version 52.67.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 82.103 dmi.modalias: dmi:bvnHP:bvrR70Ver.01.08.01:bd01/08/2021:br8.1:efr82.103:svnHP:pnHPZBook15uG6:pvr:rvnHP:rn8549:rvrKBCVersion52.67.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook 15u G6 dmi.product.sku: 9AP56LP#ABA dmi.sys.vendor: HP ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1924494 Title: Systemd shutdown order unmounts filesystem used by qemu/kvm guest before shutting down the guest Status in systemd package in Ubuntu: New Bug description: Last night I started a reboot without manually shutting down a qemu/kvm guest first. After X went down a bunch of I/O errors associated with a network block device that contains a NTFS filesystem showed up on the console. I noticed that the umount.target had been reached but the virt-guest-shutdown.target was still waiting for the guest to shut down, until it timed out. Wouldn't it be beneficial for all guests to be shutdown before unmounting all filesystems? ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246.6-1ubuntu1.3 ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Apr 15 08:35:48 2021 InstallationDate: Installed on 2021-01-17 (88 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP ZBook 15u G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=25df7fed-1baf-421e-941e-7f7c280db6e8 ro iommu=pt intel_iommu=on default_hugepagesz=1G hugepagesz=1G hugepages=6 pcie_aspm.policy=performance SourcePackage: systemd UpgradeStatus: Upgraded to groovy on 2021-04-08 (6 days ago) dmi.bios.date: 01/08/2021 dmi.bios.release: 8.1 dmi.bios.vendor: HP dmi.bios.version: R70 Ver. 01.08.01 dmi.board.name: 8549 dmi.board.vendor: HP dmi.board.version: KBC Version 52.67.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 82.103 dmi.modalias: dmi:bvnHP:bvrR70Ver.01.08.01:bd01/08/2021:br8.1:efr82.103:svnHP:pnHPZBook15uG6:pvr:rvnHP:rn8549:rvrKBCVersion52.67.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook 15u G6 dmi.product.sku: 9AP56LP#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1924494/+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 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'
** Also affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags added: rls-hh-incoming -- 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/1923150 Title: unexpected error pop-up after 'apt install nvidia-driver-455' Status in OEM Priority Project: Confirmed Status in apt package in Ubuntu: New Status in nvidia-graphics-drivers-455 package in Ubuntu: New Bug description: Ubuntu info: $ lsb_release -rd Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52) Release 20.04 Full reproduce step 1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first place, without all i386 pkg installed. 2. run update-manager to do upgrade. 3. it will show error after download deb and didn't upgrade anything. Per test with the command to do the upgrade, it will have an extra error message, but it will just upgrade and install recommended i386 debs. The error msgs are: E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) Short way to get the error: # apt-get install libgcc-s1:i386 --dry-run Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16 libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate Use 'apt autoremove' to remove them. The following additional packages will be installed: gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 libunistring2:i386 Suggested packages: glibc-doc glibc-doc:i386 locales:i386 The following NEW packages will be installed: gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 libunistring2:i386 The following packages will be upgraded: libc6 1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded. Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) [] Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) [] Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) For now, we think the above Error is the root cause of update-manager failure. --- This happens as upgrade package nvidia-driver-455 from 455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1. for more detail, please check the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923150/+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 1878969] Re: time-epoch never changes in SRUs
This bug was fixed in the package systemd - 229-4ubuntu21.31
---
systemd (229-4ubuntu21.31) xenial; urgency=medium
* d/p/lp1878969-time-epoch-use-source-date-epoch.patch:
- Fix configure.ac change to set time epoch
(LP: #1878969)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=30bf11d2759499ec94d3b82eaf22f55583f4758b
systemd (229-4ubuntu21.30) xenial; urgency=medium
* d/p/lp1878969-time-epoch-use-source-date-epoch.patch:
- Set time epoch using $SOURCE_DATE_EPOCH
(LP: #1878969)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9e1ad364d94b3619947c541b72aa506010ee3f38
* d/p/lp1913763-udev-rules-add-rule-to-create-dev-ptp_hyperv.patch:
- Create symlink for hyperv-provided ptp device
(LP: #1913763)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ae39f8878ca5dabb4e9d8ba5ebdb6ed003993b9f
-- Dan Streetman Thu, 01 Apr 2021 22:51:58
-0400
** Changed in: systemd (Ubuntu Xenial)
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/1878969
Title:
time-epoch never changes in SRUs
Status in ubuntu-core-initramfs:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
Fix Released
Status in systemd source package in Bionic:
Fix Released
Status in systemd source package in Focal:
Fix Released
Bug description:
[Impact]
* Systems without hwclock come up with a fixed time epoch which is not
updated in SRUs
* Ideally booting with a newer built of systemd should move time epoch to be
at least when systemd was last built. For example to the value of
SOURCE_DATE_EPOCH.
[Test Case]
* Boot without network NTP or hwclock
* Observe that the epoch is the same as the time when NEWS entry in the
systemd source code was last touched.
* Boot newer update of systemd, observe that the time epoch is at least 2020
[Regression Potential]
* Bad epoch, may result in unable to perform TLS connections,
validated GPG signatures, and snapd assertions. Changing epoch to be
more recent is desired. Some machines may rely on the fact that
"bionic" without hwclock always comes up in year 2018. But in practice
that is incorrect thing to do.
[Other Info]
* By default
option('time-epoch', type : 'integer', value : '-1',
description : 'time epoch for time clients')
in systemd is set to the modification time of the NEW entry
time_epoch = run_command(stat, '-c', '%Y', NEWS).stdout().to_int()
If available, it should be set to SOURCE_DATE_EPOCH=1585051767 value
to be compliant with the https://reproducible-
builds.org/docs/timestamps/ specification.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-core-initramfs/+bug/1878969/+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 1913763] Re: hyperv: unable to distinguish PTP devices
This bug was fixed in the package systemd - 229-4ubuntu21.31
---
systemd (229-4ubuntu21.31) xenial; urgency=medium
* d/p/lp1878969-time-epoch-use-source-date-epoch.patch:
- Fix configure.ac change to set time epoch
(LP: #1878969)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=30bf11d2759499ec94d3b82eaf22f55583f4758b
systemd (229-4ubuntu21.30) xenial; urgency=medium
* d/p/lp1878969-time-epoch-use-source-date-epoch.patch:
- Set time epoch using $SOURCE_DATE_EPOCH
(LP: #1878969)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9e1ad364d94b3619947c541b72aa506010ee3f38
* d/p/lp1913763-udev-rules-add-rule-to-create-dev-ptp_hyperv.patch:
- Create symlink for hyperv-provided ptp device
(LP: #1913763)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ae39f8878ca5dabb4e9d8ba5ebdb6ed003993b9f
-- Dan Streetman Thu, 01 Apr 2021 22:51:58
-0400
** Changed in: systemd (Ubuntu Xenial)
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/1913763
Title:
hyperv: unable to distinguish PTP devices
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
Fix Released
Status in systemd source package in Bionic:
Fix Released
Status in systemd source package in Focal:
Fix Released
Status in systemd source package in Groovy:
Fix Released
Bug description:
[impact]
the /dev/ptp0 device for a hyperv instance may not be the correct,
hyperv-provided, ptp device.
[test case]
on some hyperv instance types, particularly those that might contain
passthrough network card(s) that also provide ptp, the first ptp
device may not be the correct one to use for ptp, e.g. there may be
multiple ones:
$ ls /dev/ptp*
/dev/ptp0 /dev/ptp1
$ cat /sys/class/ptp/ptp0/clock_name
hyperv
$ cat /sys/class/ptp/ptp1/clock_name
mlx5_p2p
the order can change across boots, so a consistent way of addressing
the hyperv-provided one is needed
[regression potential]
any regression would involve failure to properly create the ptp
symlink, or other failure while udev is processing newly detected ptp
device(s)
[scope]
this is needed in all releases
this was fixed upstream with the commit
32e868f058da8b90add00b2958c516241c532b70 which is not yet included in
any release
[original description]
Hyperv provides a PTP device. On system with multiple PTP devices,
services like Chrony don't have a way to know which one is which.
We would like to have a udev rule to create a symlink to the hyperv
clock. This way, services could be configured to always use this clock
no matter if it is ptp0, ptp1, etc..
For example:
```
SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv"
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913763/+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 1921626] Re: size mismatch error if request of unknown size is larger than others
This bug was fixed in the package apt - 2.2.3 --- apt (2.2.3) unstable; urgency=medium * tests: Check for and discard expected warning from MaybeAddAuth. For some reason, this was only noticed with LTO enabled, but should be a general issue. * Fix downloads of unsized files that are largest in pipeline (LP: #1921626) * Warn on packages without a Size field. Such repositories are broken and need to be fixed, as we do not test apt against them, see the bug above for more details. Set Acquire::AllowUnsizedPackages to disable the warning. -- Julian Andres Klode Tue, 13 Apr 2021 17:53:32 +0200 ** Changed in: apt (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- 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/1921626 Title: size mismatch error if request of unknown size is larger than others Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: New Status in apt source package in Focal: New Status in apt source package in Groovy: New Status in apt source package in Hirsute: Fix Released Bug description: [Impact] Downloads fail if: - there is at least one package each with Size and no size on a mirror - a package without a Size field is larger than a package with a Size field that's currently in the pipeline Also, this was silent, we need to add an error so people fix repos. For hirsute, this is a warning; for hirsute+1 it's an error so people's CI fails on them and doesn't "succeed with warnings" [Test plan] We have included a test case in the apt integration tests, which downloads three packages a, b, c where b is largest and has no Size field. With 2.2.2, it fails; with 2.2.3 it succceeds. We have also added a test case that a warning is shown. [Where problems could occur] Problems can only occur if you try to download packages without a Size field, as that is the only place code changes (adding code guarded with if ... Size ... == 0; 0 being unknown size). [Other changes] 2.2.3 includes the same change as 2.2.2ubuntu1 [Original bug report] 1) Ubuntu 18.04.5 LTS 2) apt 1.6.12ubuntu0.2 3) What you expected to happen I set a custom set of repositories in /etc/apt/sources.list and then I run "apt install ". I expect the command to download and install the packages. 4) What happened instead "apt install ..." fails during the download phase with "File has unexpected size " 5) What I've established trying to debug the issue: - Disabling http pipelining resolves the issue: "apt -oAcquire::http::Pipeline-Depth=0 install ..." - All the packages, and repo metadata in the referenced repositories is correct - The issue is easily reproducible in my setup with different repositories - tcpdump shows that requests and responses are in the correct order, and contain the correct data More details about the issue: https://projects.theforeman.org/issues/32178 With all the above in mind, it appears that this must be a bug in apt's http pipeline handling. It seem that apt is trying to match a request to do wrong response, and size doesn't match. I've attached an example log, where the error pops up for multiple packages, and they all appear to be compared to one size (86464 bytes). That size is correct for one of the package being downloaded, but somehow apt is trying to match to multiple other packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1921626/+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 1918696] Re: libseccomp 2.5.1 will break unit tests on ppc
This bug was fixed in the package systemd - 237-3ubuntu10.46 --- systemd (237-3ubuntu10.46) bionic; urgency=medium * d/p/lp1916485-Newer-Glibc-use-faccessat2-to-implement-faccessat.patch: Add support for faccessat2 (LP: #1916485) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b5f11a9baecf0cefb503632e938d473234172128 * d/p/lp1918696-shared-seccomp-util-address-family-filtering-is-brok.patch: Stop attempting to restrict address families on ppc archs (LP: #1918696) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4569a047ece8b1b300ef63e49b5aea8aba35c500 * d/p/lp1891810-seccomp-util-add-new-syscalls-from-kernel-5.6-to-sys.patch: Add openat2() syscall to seccomp filter list (LP: #1891810) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2ddfbfa79af4f22b7adf946c4299433fd74a4f17 -- Dan Streetman Wed, 17 Mar 2021 17:38:05 -0400 ** 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/1918696 Title: libseccomp 2.5.1 will break unit tests on ppc 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 Status in systemd source package in Groovy: Fix Released Bug description: [impact] when libseccomp is upgraded to 2.5.1 on all releases, the systemd seccomp unit tests will start failing on ppc, as RestrictAddressFamilies= will no longer work on that arch. However, the systemd.exec man page has stated that RestrictAddressFamiles= doesn't work on ppc since before bionic. [test case] check systemd autopkgtest on ppc, looking at the test_restrict_access_familes unit test [regression potential] any regression would involve the use of RestrictAddressFamilies=, either no longer restricting or incorrectly restricting address familes. [scope] this is needed for b/f/g this was fixed upstream by commit d5923e38bc0e6cf9d7620ed5f1f8606fe7fe1168 which is included in 247, so this is fixed in h already This isn't needed in x, because it doesn't include upstream commit 469830d1426a91e0897c321fdc8ee428f0a750c1 which reworked the code to switch from seccomp_rule_add to seccomp_rule_add_exact, so systemd could handle lack of arch support itself, instead of allowing the 'not exact' seccomp syscall to just ignore the call due to lack of arch support. [other info] libseccomp will be updated to 2.5.1 in the near future so this is needed before that update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696/+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 1916485] Re: test -x fails inside shell scripts in containers
This bug was fixed in the package systemd - 237-3ubuntu10.46 --- systemd (237-3ubuntu10.46) bionic; urgency=medium * d/p/lp1916485-Newer-Glibc-use-faccessat2-to-implement-faccessat.patch: Add support for faccessat2 (LP: #1916485) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b5f11a9baecf0cefb503632e938d473234172128 * d/p/lp1918696-shared-seccomp-util-address-family-filtering-is-brok.patch: Stop attempting to restrict address families on ppc archs (LP: #1918696) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4569a047ece8b1b300ef63e49b5aea8aba35c500 * d/p/lp1891810-seccomp-util-add-new-syscalls-from-kernel-5.6-to-sys.patch: Add openat2() syscall to seccomp filter list (LP: #1891810) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2ddfbfa79af4f22b7adf946c4299433fd74a4f17 -- Dan Streetman Wed, 17 Mar 2021 17:38:05 -0400 ** 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/1916485 Title: test -x fails inside shell scripts in containers Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: Invalid Status in docker.io source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: Fix Committed Status in systemd source package in Bionic: Fix Released Status in docker.io source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: Fix Committed Status in systemd source package in Focal: Fix Released Status in docker.io source package in Groovy: New Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: Fix Committed Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: New Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd package in Debian: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug
[Touch-packages] [Bug 1891810] Re: Backport 2.5.1 to fix missing openat2 syscall, causing problems for fuse-overlayfs in nspawn containers
This bug was fixed in the package systemd - 237-3ubuntu10.46 --- systemd (237-3ubuntu10.46) bionic; urgency=medium * d/p/lp1916485-Newer-Glibc-use-faccessat2-to-implement-faccessat.patch: Add support for faccessat2 (LP: #1916485) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b5f11a9baecf0cefb503632e938d473234172128 * d/p/lp1918696-shared-seccomp-util-address-family-filtering-is-brok.patch: Stop attempting to restrict address families on ppc archs (LP: #1918696) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4569a047ece8b1b300ef63e49b5aea8aba35c500 * d/p/lp1891810-seccomp-util-add-new-syscalls-from-kernel-5.6-to-sys.patch: Add openat2() syscall to seccomp filter list (LP: #1891810) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2ddfbfa79af4f22b7adf946c4299433fd74a4f17 -- Dan Streetman Wed, 17 Mar 2021 17:38:05 -0400 ** 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/1891810 Title: Backport 2.5.1 to fix missing openat2 syscall, causing problems for fuse-overlayfs in nspawn containers Status in libseccomp package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in libseccomp source package in Xenial: Fix Released Status in systemd source package in Xenial: Invalid Status in libseccomp source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in libseccomp source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in libseccomp source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Status in libseccomp source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Bug description: [Impact] The version of libseccomp2 in X/B/F/G does not know about the openat2 syscall. As such applications that use libseccomp cannot specify a system-call filter against this system-call and so it cannot be mediated. [Test Plan] This can be tested by simply running scmp_sys_resolver from the seccomp binary package and specifying this system-call: Existing behaviour: $ scmp_sys_resolver openat2 -1 Expected behaviour: $ scmp_sys_resolver openat2 437 (Note this value will be different on other architectures) [Where problems could occur] In version 2.5.1 of libseccomp which adds this new system-call, changes were also made in the way the socket system-call is handled by libseccomp on PPC platforms - this resulted in a change in the expected behaviour and so this has already been noticed and a fix is required for the systemd unit tests as a result https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696 There was also a similar change for s390x but so far no regressions have been observed as a result as systemd already expected that behaviour from libseccomp, it was only PPC that was missing. In the event that a regression is observed however, we can easily either patch the affected package to cope with the new behaviour of this updated libseccomp since in each case the change in behaviour only affects a few system calls on particular architectures, or we can revert this update. [Other Info] * As usual thorough testing of this update has been performed both manually via the QA Regression Testing scripts, and via the autopkgtest infrastructure against packages in the Ubuntu Security Proposed PPA https://launchpad.net/~ubuntu-security- proposed/+archive/ubuntu/ppa/ with results seen https://people.canonical.com/~platform/security-britney/current/ I have attached debdiffs of the prepared updates which are also sitting in the Ubuntu Security Proposed PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1891810/+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 1909918] Re: software-properties-gtk crashed with AttributeError in __init__(): 'ElementTree' object has no attribute 'getiterator'
** Changed in: software-properties (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1909918 Title: software-properties-gtk crashed with AttributeError in __init__(): 'ElementTree' object has no attribute 'getiterator' Status in software-properties package in Ubuntu: In Progress Bug description: lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.99.5 Candidate: 0.99.5 Version table: *** 0.99.5 500 500 http://nl.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: software-properties-gtk 0.99.5 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sun Jan 3 17:37:55 2021 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2021-01-03 (0 days ago) InstallationMedia: Ubuntu-Server 21.04 "Hirsute Hippo" - Alpha amd64 (20201231) InterpreterPath: /usr/bin/python3.9 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.9, Python 3.9.1, python3-minimal, 3.9.0-3ubuntu1 PythonArgs: ['/usr/bin/software-properties-gtk'] PythonDetails: N/A SourcePackage: software-properties Title: software-properties-gtk crashed with AttributeError in __init__(): 'ElementTree' object has no attribute 'getiterator' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1909918/+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 1909918] Re: software-properties-gtk crashed with AttributeError in __init__(): 'ElementTree' object has no attribute 'getiterator'
** Information type changed from Private to Public -- 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/1909918 Title: software-properties-gtk crashed with AttributeError in __init__(): 'ElementTree' object has no attribute 'getiterator' Status in software-properties package in Ubuntu: In Progress Bug description: lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.99.5 Candidate: 0.99.5 Version table: *** 0.99.5 500 500 http://nl.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: software-properties-gtk 0.99.5 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sun Jan 3 17:37:55 2021 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2021-01-03 (0 days ago) InstallationMedia: Ubuntu-Server 21.04 "Hirsute Hippo" - Alpha amd64 (20201231) InterpreterPath: /usr/bin/python3.9 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.9, Python 3.9.1, python3-minimal, 3.9.0-3ubuntu1 PythonArgs: ['/usr/bin/software-properties-gtk'] PythonDetails: N/A SourcePackage: software-properties Title: software-properties-gtk crashed with AttributeError in __init__(): 'ElementTree' object has no attribute 'getiterator' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1909918/+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 1923553] Re: software-properties gui python exception on selecting "other" package source
*** This bug is a duplicate of bug 1909918 ***
https://bugs.launchpad.net/bugs/1909918
** This bug has been marked a duplicate of bug 1909918
software-properties-gtk crashed with AttributeError in __init__():
'ElementTree' object has no attribute 'getiterator'
--
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/1923553
Title:
software-properties gui python exception on selecting "other" package
source
Status in software-properties package in Ubuntu:
New
Bug description:
on hirsute (21.04) software-properties-qt (software-properties-
qt/hirsute 0.99.8) (also callable as software-properties-kde) throws a
python exception when a package download source of "other" is
selected. the same underlying error occurs when using software-
properties-gtk (software-properties-gtk/hirsute 0.99.8).
this python traceback appears in the console for the qt gui:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py",
line 454, in on_combobox_server_changed
dialogue = DialogMirror(self.userinterface, self.datadir, self.distro,
self.custom_mirrors)
File
"/usr/lib/python3/dist-packages/softwareproperties/qt/DialogMirror.py", line
55, in __init__
self.country_info = CountryInformation()
File
"/usr/lib/python3/dist-packages/softwareproperties/CountryInformation.py", line
34, in __init__
it = et.getiterator('iso_3166_entry')
AttributeError: 'ElementTree' object has no attribute 'getiterator'
and this appears for the gtk gui:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 661, in on_combobox_server_changed
dialog = DialogMirror(self.window_main,
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogMirror.py", line
85, in __init__
self.country_info = CountryInformation()
File
"/usr/lib/python3/dist-packages/softwareproperties/CountryInformation.py", line
34, in __init__
it = et.getiterator('iso_3166_entry')
AttributeError: 'ElementTree' object has no attribute 'getiterator'
i assume the underlying python code being called is using the long deprecated
and now removed "getiterator" method in ElementTree to generate the list of
"other" download sources.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1923553/+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 1909918] Re: software-properties-gtk crashed with AttributeError in __init__(): 'ElementTree' object has no attribute 'getiterator'
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- 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/1909918 Title: software-properties-gtk crashed with AttributeError in __init__(): 'ElementTree' object has no attribute 'getiterator' Status in software-properties package in Ubuntu: In Progress Bug description: lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.99.5 Candidate: 0.99.5 Version table: *** 0.99.5 500 500 http://nl.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: software-properties-gtk 0.99.5 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sun Jan 3 17:37:55 2021 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2021-01-03 (0 days ago) InstallationMedia: Ubuntu-Server 21.04 "Hirsute Hippo" - Alpha amd64 (20201231) InterpreterPath: /usr/bin/python3.9 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.9, Python 3.9.1, python3-minimal, 3.9.0-3ubuntu1 PythonArgs: ['/usr/bin/software-properties-gtk'] PythonDetails: N/A SourcePackage: software-properties Title: software-properties-gtk crashed with AttributeError in __init__(): 'ElementTree' object has no attribute 'getiterator' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1909918/+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 1874824] Re: pgrep reports error "cannot allocate" when run without stack limit
This bug was fixed in the package procps - 2:3.3.16-1ubuntu2.1 --- procps (2:3.3.16-1ubuntu2.1) focal; urgency=medium * Address slowness and crashes with large or unlimited stack limits (LP: #1874824) -- William 'jawn-smith' Wilson Wed, 24 Mar 2021 13:51:32 -0500 ** Changed in: procps (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 procps in Ubuntu. https://bugs.launchpad.net/bugs/1874824 Title: pgrep reports error "cannot allocate" when run without stack limit Status in procps package in Ubuntu: Fix Released Status in procps source package in Focal: Fix Released Status in procps source package in Groovy: Fix Released Status in procps source package in Hirsute: Fix Released Status in procps package in Debian: New Bug description: [Impact] - Users who have ulimit set high would see either slow or failed pgrep and pkill commands - Users who have ulimit set to unlimited would see failed pgrep and pkill commands - This bug occurs because the behavior of sysconf(_SC_ARG_MAX) changed with a newer version of the kernel. [Test Case] - set the ulimit to unlimited by running `ulimit -S -s unlimited` - run `pgrep bash` to see that the "cannot allocate" error is printed and the command has failed. [Where Problems Could Occur] - We have set upper and lower limits on the size of the malloc, but if further kernel versions break the call to sysconf in unexpected ways we could still see problems. [Original Description] If you have no stack limit (ulimit -S -s unlimited), any pgrep call will fail with an error: > pgrep vim pgrep: cannot allocate 4611686018427387903 bytes If you have a high stack limit (e.g. ulimit -S -s 50), pgrep is very slow: > time pgrep vim 2196 real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444 The relevant upstream bug report could be: https://gitlab.com/procps-ng/procps/-/issues/152 Archlinux bug report: https://bugs.archlinux.org/task/66093 procps: Installed: 2:3.3.16-1ubuntu2 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+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 1908818] Re: pure packaging of libnss3
This bug was fixed in the package nss - 2:3.55-1ubuntu3.1
---
nss (2:3.55-1ubuntu3.1) groovy; urgency=medium
* d/libnss3.links: Chmod +x d/libnss3.links, otherwise dh-exec can't do
the right job in substituting DEB_HOST_MULTIARCH (LP: #1908818)
-- Christian Ehrhardt Tue, 06 Apr
2021 12:10:12 +0200
** Changed in: nss (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 nss in Ubuntu.
https://bugs.launchpad.net/bugs/1908818
Title:
pure packaging of libnss3
Status in nss package in Ubuntu:
Fix Released
Status in nss source package in Groovy:
Fix Released
Status in nss source package in Hirsute:
Fix Released
Bug description:
[Impact]
* A packaging error in the current version has led library symlinks
to be broken and in the wrong place.
* Fix by applying the later change to Groovy as well
[Test Plan]
* install libnss3
* check (path depends on the architecture) the lib links
$ dpkg -L libnss3 | grep MULTIARCH
# ^^ should be empty
$ ll /usr/lib/x86_64-linux-gnu/libfreebl3.so
# vv should look like that:
lrwxrwxrwx 1 root root 17 Feb 16 15:18
/usr/lib/x86_64-linux-gnu/libfreebl3.so -> nss/libfreebl3.so
root@h:~# ll /usr/lib/x86_64-linux-gnu/libfreebl*
lrwxrwxrwx 1 root root 18 Feb 16 15:18
/usr/lib/x86_64-linux-gnu/libfreebl3.chk -> nss/libfreebl3.chk
lrwxrwxrwx 1 root root 17 Feb 16 15:18
/usr/lib/x86_64-linux-gnu/libfreebl3.so -> nss/libfreebl3.so
lrwxrwxrwx 1 root root 22 Feb 16 15:18
/usr/lib/x86_64-linux-gnu/libfreeblpriv3.chk -> nss/libfreeblpriv3.chk
lrwxrwxrwx 1 root root 21 Feb 16 15:18
/usr/lib/x86_64-linux-gnu/libfreeblpriv3.so -> nss/libfreeblpriv3.so
[Where problems could occur]
* I first was afraid, that no matter how bad the paths would
have been we'd need to retain them for anyone using them
already. But the existing links go into nowhere since they
are relative therefore the regression risk should be minimal
root@g:~# ll '/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so'
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so'
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk'
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk'
lrwxrwxrwx 1 root root 18 Sep 29 2020
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk' -> nss/libfreebl3.chk
lrwxrwxrwx 1 root root 17 Sep 29 2020
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so' -> nss/libfreebl3.so
lrwxrwxrwx 1 root root 22 Sep 29 2020
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk' -> nss/libfreeblpriv3.chk
lrwxrwxrwx 1 root root 21 Sep 29 2020
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so' -> nss/libfreeblpriv3.so
* never the less, to be clear - if problems occur they would be in
loading these libraries. E.g. a user could have had this package
and a self built nss on his system, after the change it might load the
packaged one.
[Other Info]
* n/a
---
dpkg -L libnss3
/.
/usr
/usr/lib
/usr/lib/${DEB_HOST_MULTIARCH}
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libnss3.so
/usr/lib/x86_64-linux-gnu/libnssutil3.so
/usr/lib/x86_64-linux-gnu/libsmime3.so
/usr/lib/x86_64-linux-gnu/libssl3.so
/usr/lib/x86_64-linux-gnu/nss
/usr/lib/x86_64-linux-gnu/nss/libfreebl3.chk
/usr/lib/x86_64-linux-gnu/nss/libfreebl3.so
/usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.chk
/usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.so
/usr/lib/x86_64-linux-gnu/nss/libnssckbi.so
/usr/lib/x86_64-linux-gnu/nss/libnssdbm3.chk
/usr/lib/x86_64-linux-gnu/nss/libnssdbm3.so
/usr/lib/x86_64-linux-gnu/nss/libsoftokn3.chk
/usr/lib/x86_64-linux-gnu/nss/libsoftokn3.so
/usr/share
/usr/share/doc
/usr/share/doc/libnss3
/usr/share/doc/libnss3/changelog.Debian.gz
/usr/share/doc/libnss3/copyright
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/libnss3
/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk
/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk
as we can see soft links to libraries do nor resolve
${DEB_HOST_MULTIARCH} to x86_64-linux-gnu
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: libnss3 2:3.55-1ubuntu3
ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
Uname: Linux 5.8.0-33-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Dec 20 14:36:10 2020
SourcePackage: nss
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1908818/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help :
[Touch-packages] [Bug 1908818] Update Released
The verification of the Stable Release Update for nss 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 nss in Ubuntu.
https://bugs.launchpad.net/bugs/1908818
Title:
pure packaging of libnss3
Status in nss package in Ubuntu:
Fix Released
Status in nss source package in Groovy:
Fix Released
Status in nss source package in Hirsute:
Fix Released
Bug description:
[Impact]
* A packaging error in the current version has led library symlinks
to be broken and in the wrong place.
* Fix by applying the later change to Groovy as well
[Test Plan]
* install libnss3
* check (path depends on the architecture) the lib links
$ dpkg -L libnss3 | grep MULTIARCH
# ^^ should be empty
$ ll /usr/lib/x86_64-linux-gnu/libfreebl3.so
# vv should look like that:
lrwxrwxrwx 1 root root 17 Feb 16 15:18
/usr/lib/x86_64-linux-gnu/libfreebl3.so -> nss/libfreebl3.so
root@h:~# ll /usr/lib/x86_64-linux-gnu/libfreebl*
lrwxrwxrwx 1 root root 18 Feb 16 15:18
/usr/lib/x86_64-linux-gnu/libfreebl3.chk -> nss/libfreebl3.chk
lrwxrwxrwx 1 root root 17 Feb 16 15:18
/usr/lib/x86_64-linux-gnu/libfreebl3.so -> nss/libfreebl3.so
lrwxrwxrwx 1 root root 22 Feb 16 15:18
/usr/lib/x86_64-linux-gnu/libfreeblpriv3.chk -> nss/libfreeblpriv3.chk
lrwxrwxrwx 1 root root 21 Feb 16 15:18
/usr/lib/x86_64-linux-gnu/libfreeblpriv3.so -> nss/libfreeblpriv3.so
[Where problems could occur]
* I first was afraid, that no matter how bad the paths would
have been we'd need to retain them for anyone using them
already. But the existing links go into nowhere since they
are relative therefore the regression risk should be minimal
root@g:~# ll '/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so'
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so'
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk'
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk'
lrwxrwxrwx 1 root root 18 Sep 29 2020
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk' -> nss/libfreebl3.chk
lrwxrwxrwx 1 root root 17 Sep 29 2020
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so' -> nss/libfreebl3.so
lrwxrwxrwx 1 root root 22 Sep 29 2020
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk' -> nss/libfreeblpriv3.chk
lrwxrwxrwx 1 root root 21 Sep 29 2020
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so' -> nss/libfreeblpriv3.so
* never the less, to be clear - if problems occur they would be in
loading these libraries. E.g. a user could have had this package
and a self built nss on his system, after the change it might load the
packaged one.
[Other Info]
* n/a
---
dpkg -L libnss3
/.
/usr
/usr/lib
/usr/lib/${DEB_HOST_MULTIARCH}
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libnss3.so
/usr/lib/x86_64-linux-gnu/libnssutil3.so
/usr/lib/x86_64-linux-gnu/libsmime3.so
/usr/lib/x86_64-linux-gnu/libssl3.so
/usr/lib/x86_64-linux-gnu/nss
/usr/lib/x86_64-linux-gnu/nss/libfreebl3.chk
/usr/lib/x86_64-linux-gnu/nss/libfreebl3.so
/usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.chk
/usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.so
/usr/lib/x86_64-linux-gnu/nss/libnssckbi.so
/usr/lib/x86_64-linux-gnu/nss/libnssdbm3.chk
/usr/lib/x86_64-linux-gnu/nss/libnssdbm3.so
/usr/lib/x86_64-linux-gnu/nss/libsoftokn3.chk
/usr/lib/x86_64-linux-gnu/nss/libsoftokn3.so
/usr/share
/usr/share/doc
/usr/share/doc/libnss3
/usr/share/doc/libnss3/changelog.Debian.gz
/usr/share/doc/libnss3/copyright
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/libnss3
/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk
/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk
as we can see soft links to libraries do nor resolve
${DEB_HOST_MULTIARCH} to x86_64-linux-gnu
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: libnss3 2:3.55-1ubuntu3
ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
Uname: Linux 5.8.0-33-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Dec 20 14:36:10 2020
SourcePackage: nss
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1908818/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe :
[Touch-packages] [Bug 1874824] Re: pgrep reports error "cannot allocate" when run without stack limit
This bug was fixed in the package procps - 2:3.3.16-5ubuntu2.1 --- procps (2:3.3.16-5ubuntu2.1) groovy; urgency=medium * Address slowness and crashes with large or unlimited stack limits (LP: #1874824) -- William 'jawn-smith' Wilson Wed, 24 Mar 2021 10:09:08 -0500 ** Changed in: procps (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 procps in Ubuntu. https://bugs.launchpad.net/bugs/1874824 Title: pgrep reports error "cannot allocate" when run without stack limit Status in procps package in Ubuntu: Fix Released Status in procps source package in Focal: Fix Committed Status in procps source package in Groovy: Fix Released Status in procps source package in Hirsute: Fix Released Status in procps package in Debian: New Bug description: [Impact] - Users who have ulimit set high would see either slow or failed pgrep and pkill commands - Users who have ulimit set to unlimited would see failed pgrep and pkill commands - This bug occurs because the behavior of sysconf(_SC_ARG_MAX) changed with a newer version of the kernel. [Test Case] - set the ulimit to unlimited by running `ulimit -S -s unlimited` - run `pgrep bash` to see that the "cannot allocate" error is printed and the command has failed. [Where Problems Could Occur] - We have set upper and lower limits on the size of the malloc, but if further kernel versions break the call to sysconf in unexpected ways we could still see problems. [Original Description] If you have no stack limit (ulimit -S -s unlimited), any pgrep call will fail with an error: > pgrep vim pgrep: cannot allocate 4611686018427387903 bytes If you have a high stack limit (e.g. ulimit -S -s 50), pgrep is very slow: > time pgrep vim 2196 real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444 The relevant upstream bug report could be: https://gitlab.com/procps-ng/procps/-/issues/152 Archlinux bug report: https://bugs.archlinux.org/task/66093 procps: Installed: 2:3.3.16-1ubuntu2 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+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 1874824] Update Released
The verification of the Stable Release Update for procps 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 procps in Ubuntu. https://bugs.launchpad.net/bugs/1874824 Title: pgrep reports error "cannot allocate" when run without stack limit Status in procps package in Ubuntu: Fix Released Status in procps source package in Focal: Fix Committed Status in procps source package in Groovy: Fix Released Status in procps source package in Hirsute: Fix Released Status in procps package in Debian: New Bug description: [Impact] - Users who have ulimit set high would see either slow or failed pgrep and pkill commands - Users who have ulimit set to unlimited would see failed pgrep and pkill commands - This bug occurs because the behavior of sysconf(_SC_ARG_MAX) changed with a newer version of the kernel. [Test Case] - set the ulimit to unlimited by running `ulimit -S -s unlimited` - run `pgrep bash` to see that the "cannot allocate" error is printed and the command has failed. [Where Problems Could Occur] - We have set upper and lower limits on the size of the malloc, but if further kernel versions break the call to sysconf in unexpected ways we could still see problems. [Original Description] If you have no stack limit (ulimit -S -s unlimited), any pgrep call will fail with an error: > pgrep vim pgrep: cannot allocate 4611686018427387903 bytes If you have a high stack limit (e.g. ulimit -S -s 50), pgrep is very slow: > time pgrep vim 2196 real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444 The relevant upstream bug report could be: https://gitlab.com/procps-ng/procps/-/issues/152 Archlinux bug report: https://bugs.archlinux.org/task/66093 procps: Installed: 2:3.3.16-1ubuntu2 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+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
Yes we can skip groovy. Thanks! -- 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 Committed 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 1923841] Re: [SRU] Increase recording quality
Thanks, I've uploaded to focal and hirsute. Do you care about 20.10 at this point? It feels like we could probably skip this one to spare some verification work since it's about to be replaced by a new stable and isn't a LTS ** Changed in: alsa-utils (Ubuntu) Importance: Undecided => Low ** Changed in: alsa-utils (Ubuntu) Status: New => Fix Committed -- 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 Committed 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 1923485] Re: unable to reconize Asgard NVME with short serial
Happy to see it being fixed so quickly. -- 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/1923485 Title: unable to reconize Asgard NVME with short serial Status in curtin: New Status in systemd package in Ubuntu: New Bug description: check this: https://discourse.maas.io/t/unable-to-deploy-valueerror-failed-to-find-storage-volume-id-nvme0n1/4442/4 Maybe the line os.listdir should be changed with os.walk to discover all child directories? Or maybe this is just a BUG of MAAS? To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1923485/+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 1924217] Re: bluetoothd 5.56 segfaults when keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()]
Prepared a fix for future update 5.56-0ubuntu5 (approximately) -- 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/1924217 Title: bluetoothd 5.56 segfaults when keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()] Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Committed Bug description: https://errors.ubuntu.com/problem/e93420b383ce737e9a5dd894617135836bd75eb8 --- bluetoothd crashes when my Lenovo Trackpoint II keyboard connects. I see this in dmesg: [ 58.257605] input: TrackPoint Keyboard II Keyboard as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input26 [ 58.258542] input: TrackPoint Keyboard II Mouse as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input27 [ 58.259561] input: TrackPoint Keyboard II Consumer Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input /input28 [ 58.259661] input: TrackPoint Keyboard II System Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/i nput29 [ 58.260151] input: TrackPoint Keyboard II as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input31 [ 58.260267] hid-generic 0005:17EF:60E1.0005: input,hidraw4: BLUETOOTH HID v0.47 Keyboard [TrackPoint Keyboard II] on 10:4a:7d:01:8d:7f [ 58.263556] bluetoothd[685]: segfault at 59 ip 5574d1d10683 sp 7ffd03bd7570 error 6 in bluetoothd[5574d1ce5000+a9000] [ 58.263568] Code: 00 00 4c 8b 21 64 48 8b 04 25 28 00 00 00 48 89 84 24 38 11 00 00 31 c0 48 8d 6c 24 10 89 fb 49 89 c9 48 89 ef b9 23 02 00 00 <41> c7 44 24 58 00 00 00 00 f3 48 ab c7 44 24 10 0a 00 00 00 c7 07 This segfault is with bluez 5.56-0ubuntu3 in Ubuntu 21.04 (up-to-date as of today). It did not happen in 20.10. When I downgraded bluez to 5.55-0ubuntu1.1 the problem went away. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu3 Uname: Linux 5.11.0-051100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Apr 14 21:03:29 2021 InstallationDate: Installed on 2021-02-26 (47 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20AW0006US ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-051100-generic root=UUID=d3f49081-f2cd-43ca-b9ed-bd8157d94ee3 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-14 (0 days ago) dmi.bios.date: 01/27/2015 dmi.bios.release: 2.31 dmi.bios.vendor: LENOVO dmi.bios.version: GLET77WW (2.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AW0006US dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrGLET77WW(2.31):bd01/27/2015:br2.31:efr1.8:svnLENOVO:pn20AW0006US:pvrThinkPadT440p:rvnLENOVO:rn20AW0006US:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AW0006US dmi.product.sku: LENOVO_MT_20AW_BU_Think_FM_ThinkPad T440p dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 10:4A:7D:01:8D:7F ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING RX bytes:267050 acl:16636 sco:0 events:966 errors:0 TX bytes:28087 acl:371 sco:0 commands:388 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1924217/+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 1924217] Re: bluetoothd 5.56 segfaults when keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()]
Private is the default state for crashes because those bugs could potentially contain personal information in crash data. -- 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/1924217 Title: bluetoothd 5.56 segfaults when keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()] Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Committed Bug description: https://errors.ubuntu.com/problem/e93420b383ce737e9a5dd894617135836bd75eb8 --- bluetoothd crashes when my Lenovo Trackpoint II keyboard connects. I see this in dmesg: [ 58.257605] input: TrackPoint Keyboard II Keyboard as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input26 [ 58.258542] input: TrackPoint Keyboard II Mouse as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input27 [ 58.259561] input: TrackPoint Keyboard II Consumer Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input /input28 [ 58.259661] input: TrackPoint Keyboard II System Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/i nput29 [ 58.260151] input: TrackPoint Keyboard II as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input31 [ 58.260267] hid-generic 0005:17EF:60E1.0005: input,hidraw4: BLUETOOTH HID v0.47 Keyboard [TrackPoint Keyboard II] on 10:4a:7d:01:8d:7f [ 58.263556] bluetoothd[685]: segfault at 59 ip 5574d1d10683 sp 7ffd03bd7570 error 6 in bluetoothd[5574d1ce5000+a9000] [ 58.263568] Code: 00 00 4c 8b 21 64 48 8b 04 25 28 00 00 00 48 89 84 24 38 11 00 00 31 c0 48 8d 6c 24 10 89 fb 49 89 c9 48 89 ef b9 23 02 00 00 <41> c7 44 24 58 00 00 00 00 f3 48 ab c7 44 24 10 0a 00 00 00 c7 07 This segfault is with bluez 5.56-0ubuntu3 in Ubuntu 21.04 (up-to-date as of today). It did not happen in 20.10. When I downgraded bluez to 5.55-0ubuntu1.1 the problem went away. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu3 Uname: Linux 5.11.0-051100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Apr 14 21:03:29 2021 InstallationDate: Installed on 2021-02-26 (47 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20AW0006US ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-051100-generic root=UUID=d3f49081-f2cd-43ca-b9ed-bd8157d94ee3 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-14 (0 days ago) dmi.bios.date: 01/27/2015 dmi.bios.release: 2.31 dmi.bios.vendor: LENOVO dmi.bios.version: GLET77WW (2.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AW0006US dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrGLET77WW(2.31):bd01/27/2015:br2.31:efr1.8:svnLENOVO:pn20AW0006US:pvrThinkPadT440p:rvnLENOVO:rn20AW0006US:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AW0006US dmi.product.sku: LENOVO_MT_20AW_BU_Think_FM_ThinkPad T440p dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 10:4A:7D:01:8D:7F ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING RX bytes:267050 acl:16636 sco:0 events:966 errors:0 TX bytes:28087 acl:371 sco:0 commands:388 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1924217/+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 1924217] Re: bluetoothd 5.56 segfaults when keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()]
That's the only crash I'm experiencing. I didn't intend to set the other bug as private, so I'm not sure what's up there. -- 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/1924217 Title: bluetoothd 5.56 segfaults when keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()] Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Committed Bug description: https://errors.ubuntu.com/problem/e93420b383ce737e9a5dd894617135836bd75eb8 --- bluetoothd crashes when my Lenovo Trackpoint II keyboard connects. I see this in dmesg: [ 58.257605] input: TrackPoint Keyboard II Keyboard as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input26 [ 58.258542] input: TrackPoint Keyboard II Mouse as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input27 [ 58.259561] input: TrackPoint Keyboard II Consumer Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input /input28 [ 58.259661] input: TrackPoint Keyboard II System Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/i nput29 [ 58.260151] input: TrackPoint Keyboard II as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input31 [ 58.260267] hid-generic 0005:17EF:60E1.0005: input,hidraw4: BLUETOOTH HID v0.47 Keyboard [TrackPoint Keyboard II] on 10:4a:7d:01:8d:7f [ 58.263556] bluetoothd[685]: segfault at 59 ip 5574d1d10683 sp 7ffd03bd7570 error 6 in bluetoothd[5574d1ce5000+a9000] [ 58.263568] Code: 00 00 4c 8b 21 64 48 8b 04 25 28 00 00 00 48 89 84 24 38 11 00 00 31 c0 48 8d 6c 24 10 89 fb 49 89 c9 48 89 ef b9 23 02 00 00 <41> c7 44 24 58 00 00 00 00 f3 48 ab c7 44 24 10 0a 00 00 00 c7 07 This segfault is with bluez 5.56-0ubuntu3 in Ubuntu 21.04 (up-to-date as of today). It did not happen in 20.10. When I downgraded bluez to 5.55-0ubuntu1.1 the problem went away. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu3 Uname: Linux 5.11.0-051100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Apr 14 21:03:29 2021 InstallationDate: Installed on 2021-02-26 (47 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20AW0006US ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-051100-generic root=UUID=d3f49081-f2cd-43ca-b9ed-bd8157d94ee3 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-14 (0 days ago) dmi.bios.date: 01/27/2015 dmi.bios.release: 2.31 dmi.bios.vendor: LENOVO dmi.bios.version: GLET77WW (2.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AW0006US dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrGLET77WW(2.31):bd01/27/2015:br2.31:efr1.8:svnLENOVO:pn20AW0006US:pvrThinkPadT440p:rvnLENOVO:rn20AW0006US:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AW0006US dmi.product.sku: LENOVO_MT_20AW_BU_Think_FM_ThinkPad T440p dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 10:4A:7D:01:8D:7F ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING RX bytes:267050 acl:16636 sco:0 events:966 errors:0 TX bytes:28087 acl:371 sco:0 commands:388 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1924217/+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
