[Touch-packages] [Bug 1938998] Re: [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not render properly
See attached screenshot. ** Attachment added: "Screenshot showing result after apt upgrade" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+attachment/5553494/+files/ss75.png -- 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/1938998 Title: [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not render properly Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinay 1218 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-01-30 (187 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. ens33 no wireless extensions. tailscale0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 RfKill: Tags: ulyssa Uname: Linux 5.4.0-80-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+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 1938998] Re: [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not render properly
I've checked, and the problem is still there. The update: ~ $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: adobe-flashplugin libllvm11 libllvm11:i386 Use 'sudo apt autoremove' to remove them. The following NEW packages will be installed libllvm12 libllvm12:i386 linux-headers-5.4.0-94 linux-headers-5.4.0-94-generic linux-image-5.4.0-94-generic linux-modules-5.4.0-94-generic linux-modules-extra-5.4.0-94-generic The following packages will be upgraded: libegl-mesa0 libexiv2-27 libgbm1 libgl1-mesa-dri:i386 libgl1-mesa-dri libgl1-mesa-glx:i386 libgl1-mesa-glx libglapi-mesa:i386 libglapi-mesa libglx-mesa0 libglx-mesa0:i386 liblightdm-gobject-1-0 libxatracker2 lightdm linux-generic linux-headers-generic linux-image-generic linux-libc-dev mesa-va-drivers mesa-vdpau-drivers mesa-vulkan-drivers mesa-vulkan-drivers:i386 xserver-common xserver-xephyr xserver-xorg-core xserver-xorg-legacy xwayland 27 to upgrade, 7 to newly install, 0 to remove and 0 not to upgrade. 10 standard security updates Need to get 160 MB of archives. After this operation, 634 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/universe amd64 lightdm amd64 1.30.0-0ubuntu4~20.04.2 [144 kB] Get:2 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main amd64 libegl-mesa0 amd64 21.0.3-0ubuntu0.3~20.04.5 [96.2 kB] Get:3 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main amd64 libgbm1 amd64 21.0.3-0ubuntu0.3~20.04.5 [28.7 kB] Get:4 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main amd64 xserver-common all 2:1.20.13-1ubuntu1~20.04.2 [26.5 kB] Get:5 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main amd64 xserver-xorg-legacy amd64 2:1.20.13-1ubuntu1~20.04.2 [32.2 kB] Get:6 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main amd64 xserver-xorg-core amd64 2:1.20.13-1ubuntu1~20.04.2 [1,339 kB] Get:7 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main amd64 libllvm12 amd64 1:12.0.0-3ubuntu1~20.04.4 [18.8 MB] Get:8 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main amd64 libgl1-mesa-dri amd64 21.0.3-0ubuntu0.3~20.04.5 [10.5 MB] Get:9 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main i386 libgl1-mesa-dri i386 21.0.3-0ubuntu0.3~20.04.5 [10.9 MB] Get:10 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main i386 libllvm12 i386 1:12.0.0-3ubuntu1~20.04.4 [19.2 MB] Get:11 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main amd64 libglx-mesa0 amd64 21.0.3-0ubuntu0.3~20.04.5 [138 kB] Get:12 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main i386 libglx-mesa0 i386 21.0.3-0ubuntu0.3~20.04.5 [146 kB] Get:13 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main i386 libglapi-mesa i386 21.0.3-0ubuntu0.3~20.04.5 [26.9 kB] Get:14 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main amd64 libglapi-mesa amd64 21.0.3-0ubuntu0.3~20.04.5 [26.8 kB] Get:15 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main amd64 libexiv2-27 amd64 0.27.2-8ubuntu2.7 [792 kB] Get:16 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main i386 libgl1-mesa-glx i386 21.0.3-0ubuntu0.3~20.04.5 [5,532 B] Get:17 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main amd64 libgl1-mesa-glx amd64 21.0.3-0ubuntu0.3~20.04.5 [5,532 B] Get:18 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/universe amd64 liblightdm-gobject-1-0 amd64 1.30.0-0ubuntu4~20.04.2 [40.0 kB] Get:19 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main amd64 libxatracker2 amd64 21.0.3-0ubuntu0.3~20.04.5 [1,716 kB] Get:20 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main amd64 linux-modules-5.4.0-94-generic amd64 5.4.0-94.106 [14.8 MB] Get:21 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main amd64 linux-image-5.4.0-94-generic amd64 5.4.0-94.106 [10.5 MB] Get:22
[Touch-packages] [Bug 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
Fixed in gwenview version 21.12.1. --- gwenview (4:21.12.1-0ubuntu1) jammy; urgency=medium * New upstream release (21.12.1) -- Rik Mills Thu, 06 Jan 2022 10:21:02 + ** Changed in: gwenview (Ubuntu) Importance: Undecided => Medium ** Changed in: gwenview (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Fix Released Status in exiv2 package in Ubuntu: Fix Released Status in gwenview package in Ubuntu: Fix Released Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1938998] Re: [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not render properly
This sounds related, but it was closed by Cinnamon blaming the graphics library: https://github.com/linuxmint/cinnamon/issues/10067 and is now in: https://bugzilla.redhat.com/show_bug.cgi?id=1956512 -- 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/1938998 Title: [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not render properly Status in mesa package in Ubuntu: New Bug description: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinay 1218 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-01-30 (187 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. ens33 no wireless extensions. tailscale0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 RfKill: Tags: ulyssa Uname: Linux 5.4.0-80-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1938998/+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 1938998] Re: [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not render properly
Thanks. It looks like there's a basic texturing problem in OpenGL. Since that's done entirely in software for VMs, this should be assigned either to Mesa or to Cinnamon itself. I don't think we need to involve the kernel. ** No longer affects: linux (Ubuntu) ** No longer affects: xorg-server (Ubuntu) ** Bug watch added: github.com/linuxmint/cinnamon/issues #10067 https://github.com/linuxmint/cinnamon/issues/10067 ** Bug watch added: Red Hat Bugzilla #1956512 https://bugzilla.redhat.com/show_bug.cgi?id=1956512 -- 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/1938998 Title: [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not render properly Status in mesa package in Ubuntu: New Bug description: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinay 1218 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-01-30 (187 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. ens33 no wireless extensions. tailscale0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 RfKill: Tags: ulyssa Uname: Linux 5.4.0-80-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1938998/+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 1956202] Re: `libexpat1-dev` CMake configuration error
This seems to be an upstream issue: https://github.com/libexpat/libexpat/issues/501 With that said, it doesn't seem like an upstream fix is likely any time soon, as is suggested by this comment by one of the members of the `libexpat` GitHub team on this NixOS pull request addressing this issue: https://github.com/NixOS/nixpkgs/pull/128997#issuecomment-873137856 NixOS seems to have a custom packaging setup, so the fix above is most likely not applicable. ** Bug watch added: github.com/libexpat/libexpat/issues #501 https://github.com/libexpat/libexpat/issues/501 ** Description changed: Using the package provided by Ubuntu Impish results in the following CMake configuration error when trying to build OpenColorIO: ``` […] CMake Error in src/OpenColorIO/CMakeLists.txt: - Imported target "expat::expat" includes non-existent path + Imported target "expat::expat" includes non-existent path - "/usr/lib/include" + "/usr/lib/include" - in its INTERFACE_INCLUDE_DIRECTORIES. Possible reasons include: + in its INTERFACE_INCLUDE_DIRECTORIES. Possible reasons include: - * The path was deleted, renamed, or moved to another location. + * The path was deleted, renamed, or moved to another location. - * An install or uninstall procedure did not complete successfully. + * An install or uninstall procedure did not complete successfully. - * The installation package was faulty and references files it does not - provide. + * The installation package was faulty and references files it does not + provide. […] ``` This wasn't an issue in Ubuntu Hirsute as far as I can recall and is not an issue when using the ASWF-provided packages — CMake flag `-DOCIO_INSTALL_EXT_PACKAGES=ALL`. A patch is attached that allows OpenColorIO to build using system-provided packages. - Related ticket over on the OpenColorIO GitHub repository: - https://github.com/AcademySoftwareFoundation/OpenColorIO/issues/1415 + Further information in the related ticket in the OpenColorIO repository: + https://github.com/AcademySoftwareFoundation/OpenColorIO/issues/1415#issuecomment-1003826550 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to expat in Ubuntu. https://bugs.launchpad.net/bugs/1956202 Title: `libexpat1-dev` CMake configuration error Status in expat package in Ubuntu: New Bug description: Using the package provided by Ubuntu Impish results in the following CMake configuration error when trying to build OpenColorIO: ``` […] CMake Error in src/OpenColorIO/CMakeLists.txt: Imported target "expat::expat" includes non-existent path "/usr/lib/include" in its INTERFACE_INCLUDE_DIRECTORIES. Possible reasons include: * The path was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and references files it does not provide. […] ``` This wasn't an issue in Ubuntu Hirsute as far as I can recall and is not an issue when using the ASWF-provided packages — CMake flag `-DOCIO_INSTALL_EXT_PACKAGES=ALL`. A patch is attached that allows OpenColorIO to build using system-provided packages. Further information in the related ticket in the OpenColorIO repository: https://github.com/AcademySoftwareFoundation/OpenColorIO/issues/1415#issuecomment-1003826550 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1956202/+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 1957126] [NEW] lscpu not showing number of sockets on arm64
Public bug reported: When running `lscpu` on arm64, the number of sockets is not populated. This is seen on both Raspberry Pi hardware and in the autopkgtest environment. Example output: Architecture:aarch64 CPU op-mode(s):32-bit, 64-bit Byte Order:Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Vendor ID: ARM Model name:Cortex-A72 Model: 3 Thread(s) per core: 1 Core(s) per cluster: 4 Socket(s): - Cluster(s): 1 Stepping:r0p3 CPU max MHz: 1500. CPU min MHz: 600. BogoMIPS:108.00 Flags: fp asimd evtstrm crc32 cpuid Vulnerabilities: Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Spec store bypass: Vulnerable Spectre v1:Mitigation; __user pointer sanitization Spectre v2:Vulnerable Srbds: Not affected Tsx async abort: Not affected ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1957126 Title: lscpu not showing number of sockets on arm64 Status in util-linux package in Ubuntu: New Bug description: When running `lscpu` on arm64, the number of sockets is not populated. This is seen on both Raspberry Pi hardware and in the autopkgtest environment. Example output: Architecture:aarch64 CPU op-mode(s):32-bit, 64-bit Byte Order:Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Vendor ID: ARM Model name:Cortex-A72 Model: 3 Thread(s) per core: 1 Core(s) per cluster: 4 Socket(s): - Cluster(s): 1 Stepping:r0p3 CPU max MHz: 1500. CPU min MHz: 600. BogoMIPS:108.00 Flags: fp asimd evtstrm crc32 cpuid Vulnerabilities: Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Spec store bypass: Vulnerable Spectre v1:Mitigation; __user pointer sanitization Spectre v2:Vulnerable Srbds: Not affected Tsx async abort: Not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1957126/+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 1405452] Re: Typo in man page ("introduce a much improvement mechanism")
Fixed in wpa version 2:2.9.0+git2026+0b853303ae31-1
** Changed in: wpa (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1405452
Title:
Typo in man page ("introduce a much improvement mechanism")
Status in One Hundred Papercuts:
Fix Released
Status in wpa package in Ubuntu:
Fix Committed
Status in wpa package in Debian:
New
Bug description:
"introduce a much improvement mechanism" should be "introduce a much
improved mechanism".
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: wpasupplicant 2.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Dec 24 16:19:30 2014
InstallationDate: Installed on 2014-12-19 (4 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64
(20141022.1)
SourcePackage: wpa
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1405452/+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 1957055] Re: Xorg freeze
*** This bug is a duplicate of bug 1955297 *** https://bugs.launchpad.net/bugs/1955297 ** This bug has been marked a duplicate of bug 1955297 Xorg freeze -- 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/1957055 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: tried with nvidia 390 driver also ,but no improvement ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 11 14:22:12 2022 DistUpgraded: 2021-08-22 20:45:57,513 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04b6] NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 525M] [1028:04b6] InstallationDate: Installed on 2021-08-08 (156 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. Dell System XPS L502X ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=e240f53d-7bb3-4a6d-a0c5-abc23ed371b1 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2021-08-22 (141 days ago) dmi.bios.date: 09/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0YR8NN 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.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: Dell System XPS L502X dmi.product.sku: System SKUNumber dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~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/1957055/+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 1955997] Re: The airplane hotkey has no function on a HP platform
Okay, so the current patch is for Focal? Please also provide debdiffs for Jammy and Impish, as we'll stick with v249 (in Jammy) for the LTS and Impish will not see a systemd update either. We need to fix it in Jammy first, before we can start SRUing the change. ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1955997 Title: The airplane hotkey has no function on a HP platform Status in OEM Priority Project: Triaged Status in systemd package in Ubuntu: New Status in systemd source package in Focal: New Status in systemd source package in Impish: New Status in systemd source package in Jammy: New Bug description: [Impact] The airplane hokey doesn't work on HP new generation machines. [Test Plan] Press airplane hokey. Before the patch, nothing happens. After the patch, the rfkill works as expected. [Where problems could occur] In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will not work but HP confirmed the new HP generation won't contain the HPQ6001 and also each DM still need to deal with multi-rfkill events because upstream changes[2]. --- In the last year, HP mentions HP machines need to use hp-wireless (HPQ6001) as the rfkill source[1]. However, HP confirms the HPQ6001 has been retired in the platforms since 2022. In the platforms after 2022, there are two sources of rkfill events (intel-hid, atkbd) and HP only guarantee the intel-hid works. Therefore, the upstream already accept the patch[2] to unmask intel-hid and mention this big change in the NEWS. This change makes the pre-2022 HP platforms meet the regression since they have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing function key. Thus, there is a patch[3] to make sure the GNOME could deal with this case smoothly. However, the systemd change will still cause other DEs meet the regression (xfce, KDE, lxde, etc..). Backport systemd change to make HP 2022 platforms work is not the best choice on stable version (focal in this case). We still need a solution to make airplane key works on 2022 HP platforms (intel-hid and atkbd only). The potential solution from my mind that is to maintain a whitelist to unmask intel-hid in ubuntu-patch in focal, something like: ``` evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:* KEYBOARD_KEY_8=wlan # Use hp-wireless instead ``` after "KEYBOARD_KEY_8=unkown". [1] https://bugs.launchpad.net/bugs/1883846 [2] https://github.com/systemd/systemd/pull/20219 [3] https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1955997/+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 1957055] [NEW] Xorg freeze
Public bug reported: tried with nvidia 390 driver also ,but no improvement ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 11 14:22:12 2022 DistUpgraded: 2021-08-22 20:45:57,513 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04b6] NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 525M] [1028:04b6] InstallationDate: Installed on 2021-08-08 (156 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. Dell System XPS L502X ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=e240f53d-7bb3-4a6d-a0c5-abc23ed371b1 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2021-08-22 (141 days ago) dmi.bios.date: 09/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0YR8NN 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.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: Dell System XPS L502X dmi.product.sku: System SKUNumber dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~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 freeze 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/1957055 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: tried with nvidia 390 driver also ,but no improvement ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 11 14:22:12 2022 DistUpgraded: 2021-08-22 20:45:57,513 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04b6] NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 525M] [1028:04b6] InstallationDate: Installed on 2021-08-08 (156 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. Dell System XPS L502X ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=e240f53d-7bb3-4a6d-a0c5-abc23ed371b1 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2021-08-22 (141 days ago) dmi.bios.date: 09/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0YR8NN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc.
[Touch-packages] [Bug 1957068] [NEW] package linux-image-5.11.0-46-generic 5.11.0-46.51~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: During update occured a system error. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-46-generic 5.11.0-46.51~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jan 11 09:47:04 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-05-28 (592 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-image-5.11.0-46-generic 5.11.0-46.51~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1957068 Title: package linux-image-5.11.0-46-generic 5.11.0-46.51~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: During update occured a system error. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-46-generic 5.11.0-46.51~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jan 11 09:47:04 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-05-28 (592 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-image-5.11.0-46-generic 5.11.0-46.51~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1957068/+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 1956915] Re: New bugfix release 21.2.6
I have installed version 21.2.6 by: sudo add-apt-repository ppa:savoury1/display && sudo apt upgrade since some time. I never had noticed problems and bug 1950044 was fixed by that. -- 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/1956915 Title: New bugfix release 21.2.6 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Focal: Fix Committed Status in mesa source package in Impish: Fix Committed Bug description: [Impact] This is the last point-release of the 21.2.x-series, we should put it in impish so latest bugfixes would get there, and in focal for 20.04.4 image. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1956915/+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 1957076] Re: sync cyrus-sasl2 2.1.27+dfsg2-3
** Changed in: cyrus-sasl2 (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1957076 Title: sync cyrus-sasl2 2.1.27+dfsg2-3 Status in cyrus-sasl2 package in Ubuntu: In Progress Bug description: It has the fix for bug #1956833, which is our only delta presently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1957076/+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 1957068] Re: package linux-image-5.11.0-46-generic 5.11.0-46.51~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1957068 Title: package linux-image-5.11.0-46-generic 5.11.0-46.51~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: During update occured a system error. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-46-generic 5.11.0-46.51~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jan 11 09:47:04 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-05-28 (592 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-image-5.11.0-46-generic 5.11.0-46.51~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1957068/+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 1957076] [NEW] sync cyrus-sasl2 2.1.27+dfsg2-3
Public bug reported: It has the fix for bug #1956833, which is our only delta presently. ** Affects: cyrus-sasl2 (Ubuntu) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: Triaged ** Tags: needs-merge -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1957076 Title: sync cyrus-sasl2 2.1.27+dfsg2-3 Status in cyrus-sasl2 package in Ubuntu: Triaged Bug description: It has the fix for bug #1956833, which is our only delta presently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1957076/+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 1677781] Re: Missing dep8 tests
We were recently hit by bug #1956833, where GSS-SPNEGO was suddenly
disabled and nobody noticed until an app tried to use it.
For that case, I'm thinking about a very simple test that would be like
this:
for algo in $ALGORITHMS; do
saslpluginviewer -m $algo > /dev/null || {
echo "Algorithm $algo not available"
exit 1
}
done
And ALGORITHMS is a list of the algorithms we expect to always be available,
like:
SCRAM-SHA-1 SCRAM-SHA-256 GS2-IAKERB GS2-KRB5 GSS-SPNEGO GSSAPI DIGEST-MD5
EXTERNAL CRAM-MD5 NTLM PLAIN LOGIN ANONYMOUS
** Tags added: bitesize
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/1677781
Title:
Missing dep8 tests
Status in cyrus-sasl2 package in Ubuntu:
New
Bug description:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
As of March 29, 2017, this source package did not contain dep8 tests in
the current development release of Ubuntu, named Zesty. This was
determined by running `pull-lp-source cyrus-sasl2 zesty` and then
checking for the existence of 'debian/tests/' and
'debian/tests/control'.
Test automation is essential to higher levels of quality and confidence
in updates to packages. dep8 tests [1] specify how automatic testing can
be integrated into packages and then run by package maintainers before
new uploads.
This defect is to report the absence of these tests and to report the
opportunity as a potential item for development by both new and
experienced contributors.
[1] http://packaging.ubuntu.com/html/auto-pkg-test.html
affects ubuntu/cyrus-sasl2
status new
importance wishlist
tag needs-dep8
- ---
Joshua Powers
Ubuntu Server
Canonical Ltd
-BEGIN PGP SIGNATURE-
iQIcBAEBCAAGBQJY3XaTAAoJEIP8BxPaZgwlJr8P/j8yn8mXWnAIiXUgHX7jBIGj
JuMQGO5wwcfHRxOwJEOlsO/SIATUN1L1BB84anP7Bp4cfLqXonF8eKFPkEotwaf1
3wADCH98EwLuSyJOaKXsTQHppAKdJ6UEW4jHvfhYizenEWssPfCQdg68LSGZ2enR
wD9ZhZgjwJIpLbqDTp7ygklR0htf4ZAFq/vIcyLykT6qagVE3xC8SAgd+7tb/fYe
4PYfqgGso/qpL0v6JL+YkCKH/aiMYV+HD45o1NcUbGdoiuUa9jpeYSSTP/9OgWpY
nALDXe/dJZT/wz5Zv0cy6sGRh7gtjVqI0608WAM00Jp8CmFX60z4yrq/3t37wKbz
iDQF4HyltqfCNF5oQ6xva9xAq/c2tyP8nBHzQ+ZtH/o1hyS/JdgoR38OojldyUc5
WzcTFL+h612ZVZVNm4lqBpg/0dpEkwXTE9KczyB5kSr5VVz0WXtjU5wFxKMdZpr5
Gq9uM+fHU4YHQqfGGZxmHFOgz7tCAyEsZEzpnPiYvoSksj3tJMkQG7FbIISltort
CBAwLIt1hLR9g4T3p0e4ipCJf6kL/yZR3kMGhsjbDe012bTaC8ZeLG7VYmWkBaxY
ieFMZIxmGgCq7KjDfNPh9JEmCtNgenkEOu6BszZK+gwmhL/AxVuuNRdd5OeBGy3G
WY9JzBOc6MUi46Hh9ZN5
=szTz
-END PGP SIGNATURE-
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1677781/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Hi everyone, small progress report : I tried the pipewire trick and it didn't work out for me, while it initially seemed to work: auto switch to the HSP/HPF profile didn't work and after a manual switch the headset would drop out during a conversation. I reverted to pulseaudio and invested a bit more time, now I am _almost_ there : I had to add the following to ~/.config/pulse/default.pa .include /etc/pulse/default.pa .nofail unload-module module-bluetooth-policy .fail .ifexists module-bluetooth-policy.so load-module module-bluetooth-policy auto_switch=2 .endif .ifexists module-bluetooth-discover.so load-module module-bluetooth-discover .endif to get the autoswitch to work. I am happy to report that in slack (from snap) the audio now behaves just right and friends tell me I no longer sound like a robot. Unfortunately this still doesn't work with zoom and there seems to be multiple issues. They probably come from zoom itself but I am unsure what to report to them. according to https://gavv.github.io/articles/pulseaudio-under-the- hood/#autodetecting-properties it should be possible to make pulseaudio understand that it has to switch profiles by changing /usr/share/applications/Zoom.desktop and adding Telephony to the categories. I have not been able to make this work without auto_switch=2 Here are two scenarios that fail: after a fresh boot (so all the stars are aligned), start zoom, create a new meeting, start the recording, say a few words, stop the recording, stop the meeting, open the resulting audio or video file the sound is bad when it is expected to be good. After a fresh boot (so all the stars are aligned), start zoom, go to settings-> audio, after doing this my headset is non functional and I must shut it down and start it back up to restore functionality. can someone help me determine what zoom is doing wrong ? I will also try a few other apps in the coming weeks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: Fix Released Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias:
[Touch-packages] [Bug 1957086] [NEW] Autopkgtest systemd fail against dnsmasq 2.86 (22.04)
Public bug reported: Full log (same on all architectures): https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/s/systemd/20220106_214401_24d29@/log.gz The test is from systemd: https://github.com/systemd/systemd/blob/main/test/networkd-test.py#L619 Tail of the log: ``` ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/tmp/autopkgtest.NdIvJq/build.fBQ/src/test/networkd-test.py", line 678, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.9/subprocess.py", line 424, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.9/subprocess.py", line 528, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. ``` Tagging update-excuse to be shown in excuses ** Affects: dnsmasq (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Assignee: Lukas Märdian (slyon) Status: New ** Tags: update-excuse ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1957086 Title: Autopkgtest systemd fail against dnsmasq 2.86 (22.04) Status in dnsmasq package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Full log (same on all architectures): https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/s/systemd/20220106_214401_24d29@/log.gz The test is from systemd: https://github.com/systemd/systemd/blob/main/test/networkd-test.py#L619 Tail of the log: ``` ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/tmp/autopkgtest.NdIvJq/build.fBQ/src/test/networkd-test.py", line 678, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.9/subprocess.py", line 424, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.9/subprocess.py", line 528, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. ``` Tagging update-excuse to be shown in excuses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1957086/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1948533] Re: (No Subject)
Hi Marc, will the issue of dns specified in network-manager not being forward in vpn tunnel when using openvpn (bug occuring ONLY on current ubuntu 21.10) will it be solved on next ubuntu release?? I really hope so since it will be a LTS (dns leaks are common on linux when using openvpn and putting one (whitchever one) in NM is such a simple and universal fix, one I recomend all my friends and clients... I tried other distros (fedora, debian10 and 11, manjaro) none are affected I need to know if I need to leave ubuntu (currently reverted to ubunut 20.04 witch is not affected by this (up to 21.04 ubuntu was behaving as expected on this). I used ubuntu for nearly 10 years but this issue is critical for me. Thanks a lot Sent with [ProtonMail](https://protonmail.com) Secure Email. ‐‐‐ Original Message ‐‐‐ On Tuesday, January 11, 2022 2:14 PM, gnu.linux1 at pm.me <06b6m7zt+gnu.linux1=pm...@anonaddy.me> wrote: > This email was sent to 06b6m...@anonaddy.me from gnu.lin...@pm.me with > subject "(No Subject)" and has been forwarded by > [AnonAddy](https://anonaddy.com) > Click > [here](https://app.anonaddy.com/deactivate/b094640d-0f4f-4e43-ad7b-0b1794928280?signature=9b46cf2a6cde81a072327647918b15de917c14b8491a7a866142b116e7dc821b) > to deactivate this alias > 06b6 is the code > > Sent with [ProtonMail](https://protonmail.com) Secure Email. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1948533 Title: any dns defined in network-manager doesnt go in openvpn tunnel (leaks on gnome/mate/xubuntu only in 21.10) Status in network-manager package in Ubuntu: Incomplete Bug description: in all linux including ubuntu up to version 21.04, when dns is set to not automatic in network manager and one dns is set manually (exemple 1.1.1.1) when openvpn is used the dns is going through the vpn tunnel. On ubuntu 21.10 (I tested ubuntu, ubuntu mate and xubuntu)I can affirm the dns in this case is not going trough the vpn.it is leaking.I have used ubuntu for years this is first time this problem occurs (21.10).(and it s not just a question of packages because on my arch linux installs I never had such problem, so it must be a config problem. (when using packages stubby or dnscrypt-proxy (to encrypt dns queries) and dns 127.0.0.1 is set in network-manager the dns does goes trough the vpn (but stubby service needs to be sometimes reloded, it is less reliable that it used to be with previous versions of ubuntu) (I cannot speculate where the bug is from (network-manager, systemd resolved etc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1948533/+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 1957076] Re: sync cyrus-sasl2 2.1.27+dfsg2-3
** Changed in: cyrus-sasl2 (Ubuntu) Milestone: None => ubuntu-22.01 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1957076 Title: sync cyrus-sasl2 2.1.27+dfsg2-3 Status in cyrus-sasl2 package in Ubuntu: Triaged Bug description: It has the fix for bug #1956833, which is our only delta presently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1957076/+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 1957076] Re: sync cyrus-sasl2 2.1.27+dfsg2-3
This bug was fixed in the package cyrus-sasl2 - 2.1.27+dfsg2-3 --- cyrus-sasl2 (2.1.27+dfsg2-3) unstable; urgency=medium [ Andreas Hasenack ] * Fix configure.ac for autoconf 2.70 (Closes: #1003355, #1000152) -- Bastian Germann Tue, 11 Jan 2022 11:25:37 +0100 ** Changed in: cyrus-sasl2 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1957076 Title: sync cyrus-sasl2 2.1.27+dfsg2-3 Status in cyrus-sasl2 package in Ubuntu: Fix Released Bug description: It has the fix for bug #1956833, which is our only delta presently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1957076/+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 1949970] Re: attempt to dlopen nonexistent pam_kwallet.so spams log
ubuntu@lp1949970-i:~$ dpkg -l lightdm|grep lightdm ii lightdm 1.30.0-0ubuntu4 amd64Display Manager ubuntu@lp1949970-i:~$ journalctl -b -g 'unable to dlopen' -- Journal begins at Tue 2022-01-11 17:28:57 UTC, ends at Tue 2022-01-11 17:59:05 UTC. -- Jan 11 17:58:14 lp1949970-i lightdm[939]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Jan 11 17:58:14 lp1949970-i lightdm[939]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory Jan 11 17:58:16 lp1949970-i lightdm[1083]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Jan 11 17:58:16 lp1949970-i lightdm[1083]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory ...(upgrade and reboot)... ubuntu@lp1949970-i:~$ dpkg -l lightdm|grep lightdm ii lightdm1.30.0-0ubuntu4.21.10.1 amd64Display Manager ubuntu@lp1949970-i:~$ journalctl -b -g 'unable to dlopen' -- Journal begins at Tue 2022-01-11 17:28:57 UTC, ends at Tue 2022-01-11 18:01:00 UTC. -- -- No entries -- -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1949970 Title: attempt to dlopen nonexistent pam_kwallet.so spams log Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Bionic: New Status in lightdm source package in Focal: Fix Committed Status in lightdm source package in Hirsute: Fix Committed Status in lightdm source package in Impish: Fix Committed Status in lightdm source package in Jammy: Fix Released Bug description: [impact] lightdm's pam.d config includes an attempt to dlopen pam_kwallet.so as well as pam_kwallet5.so, however pam_wallet.so comes from pam-kwallet which died around Trusty (https://launchpad.net/ubuntu/+source/pam- kwallet) while pam_kwallet5.so comes from kwallet-pam which provides only the newer '5' version, not the older unversioned library file. This results in repeated spam error messages in the system log complaining about failure to load pam_kwallet.so [test case] install/enable lightdm and check system log at boot for messages like: Nov 04 18:17:47 thrain lightdm[2510]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Nov 04 18:17:47 thrain lightdm[2510]: PAM adding faulty module: pam_kwallet.so [regression potential] any regression would likely cause problems during login and/or missing or extra log messages during pam authentication. [scope] this is needed in all releases [other info] https://github.com/canonical/lightdm/pull/216 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1949970/+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 1949970] Re: attempt to dlopen nonexistent pam_kwallet.so spams log
ubuntu@lp1949970-f:~$ dpkg -l lightdm|grep lightdm ii lightdm1.30.0-0ubuntu4~20.04.1 amd64Display Manager ubuntu@lp1949970-f:~$ journalctl -b -g 'unable to dlopen' -- Logs begin at Tue 2022-01-11 17:28:51 UTC, end at Tue 2022-01-11 18:02:33 UTC. -- Jan 11 17:58:09 lp1949970-f lightdm[1048]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Jan 11 17:58:09 lp1949970-f lightdm[1048]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory Jan 11 17:58:11 lp1949970-f lightdm[1278]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Jan 11 17:58:11 lp1949970-f lightdm[1278]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory ...(upgrade and reboot)... ubuntu@lp1949970-f:~$ dpkg -l lightdm|grep lightdm ii lightdm1.30.0-0ubuntu4~20.04.2 amd64Display Manager ubuntu@lp1949970-f:~$ journalctl -b -g 'unable to dlopen' -- Logs begin at Tue 2022-01-11 17:28:51 UTC, end at Tue 2022-01-11 18:03:41 UTC. -- -- No entries -- ** Tags removed: verification-needed verification-needed-focal verification-needed-impish ** Tags added: verification-done verification-done-focal verification-done-impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1949970 Title: attempt to dlopen nonexistent pam_kwallet.so spams log Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Bionic: New Status in lightdm source package in Focal: Fix Committed Status in lightdm source package in Hirsute: Fix Committed Status in lightdm source package in Impish: Fix Committed Status in lightdm source package in Jammy: Fix Released Bug description: [impact] lightdm's pam.d config includes an attempt to dlopen pam_kwallet.so as well as pam_kwallet5.so, however pam_wallet.so comes from pam-kwallet which died around Trusty (https://launchpad.net/ubuntu/+source/pam- kwallet) while pam_kwallet5.so comes from kwallet-pam which provides only the newer '5' version, not the older unversioned library file. This results in repeated spam error messages in the system log complaining about failure to load pam_kwallet.so [test case] install/enable lightdm and check system log at boot for messages like: Nov 04 18:17:47 thrain lightdm[2510]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Nov 04 18:17:47 thrain lightdm[2510]: PAM adding faulty module: pam_kwallet.so [regression potential] any regression would likely cause problems during login and/or missing or extra log messages during pam authentication. [scope] this is needed in all releases [other info] https://github.com/canonical/lightdm/pull/216 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1949970/+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 1949970] Re: attempt to dlopen nonexistent pam_kwallet.so spams log
I think we should ignore hirsute since it reaches EOL next week. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1949970 Title: attempt to dlopen nonexistent pam_kwallet.so spams log Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Bionic: New Status in lightdm source package in Focal: Fix Committed Status in lightdm source package in Hirsute: Fix Committed Status in lightdm source package in Impish: Fix Committed Status in lightdm source package in Jammy: Fix Released Bug description: [impact] lightdm's pam.d config includes an attempt to dlopen pam_kwallet.so as well as pam_kwallet5.so, however pam_wallet.so comes from pam-kwallet which died around Trusty (https://launchpad.net/ubuntu/+source/pam- kwallet) while pam_kwallet5.so comes from kwallet-pam which provides only the newer '5' version, not the older unversioned library file. This results in repeated spam error messages in the system log complaining about failure to load pam_kwallet.so [test case] install/enable lightdm and check system log at boot for messages like: Nov 04 18:17:47 thrain lightdm[2510]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Nov 04 18:17:47 thrain lightdm[2510]: PAM adding faulty module: pam_kwallet.so [regression potential] any regression would likely cause problems during login and/or missing or extra log messages during pam authentication. [scope] this is needed in all releases [other info] https://github.com/canonical/lightdm/pull/216 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1949970/+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 1957104] [NEW] updating openssh-server fails, because port 22 is in use by systemd
Public bug reported: openssh-server tries to restart itself, but openssh-server reports port 22 in use. This is true: systemd has taken port 22 to start sshd if one connects to port 22. two solutions: 1. dont start sshd after installing. configure it without starting it afterwards. 2. stop systemd listening on port 22 before starting sshd, then start sshd, terminate it after configuring, then start systemd listening on port 22 again. Second problem: starting ssh.service does not check if "/run/sshd" exists. This directory has to be created before sshd is started. Unclear if this is an error with sshd not creating this directory before dropping privileges or if this has to be done once while installing. IMHO the first is the case. Workaround: systemctl stop ssh.service systemctl disable ssh.service apt upgrade systemctl enable ssh.service killall sshd mkdir /run/sshd systemctl start ssh.service ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: openssh-server 1:8.4p1-6ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Tue Jan 11 19:11:47 2022 InstallationDate: Installed on 2021-08-18 (146 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SSHDConfig: Error: command ['pkexec', '/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /run/sshd SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- 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/1957104 Title: updating openssh-server fails, because port 22 is in use by systemd Status in openssh package in Ubuntu: New Bug description: openssh-server tries to restart itself, but openssh-server reports port 22 in use. This is true: systemd has taken port 22 to start sshd if one connects to port 22. two solutions: 1. dont start sshd after installing. configure it without starting it afterwards. 2. stop systemd listening on port 22 before starting sshd, then start sshd, terminate it after configuring, then start systemd listening on port 22 again. Second problem: starting ssh.service does not check if "/run/sshd" exists. This directory has to be created before sshd is started. Unclear if this is an error with sshd not creating this directory before dropping privileges or if this has to be done once while installing. IMHO the first is the case. Workaround: systemctl stop ssh.service systemctl disable ssh.service apt upgrade systemctl enable ssh.service killall sshd mkdir /run/sshd systemctl start ssh.service ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: openssh-server 1:8.4p1-6ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Tue Jan 11 19:11:47 2022 InstallationDate: Installed on 2021-08-18 (146 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SSHDConfig: Error: command ['pkexec', '/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /run/sshd SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1957104/+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 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
This bug was fixed in the package exiv2 - 0.27.3-3ubuntu1.6 --- exiv2 (0.27.3-3ubuntu1.6) hirsute-security; urgency=medium * SECURITY REGRESSION: out of range access that may cause a crash - debian/patches/CVE-2021-37620-4.patch: fix out of range access that may cause a crash (LP: #1941752) - debian/patches/CVE-2021-37620-5.patch: backport to C++98 (a str.pop_back that was added in C++11) - Thanks Simon Schmeißer -- Leonidas Da Silva Barbosa Mon, 10 Jan 2022 10:22:10 -0300 ** Changed in: exiv2 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Fix Released Status in exiv2 package in Ubuntu: Fix Released Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
This bug was fixed in the package exiv2 - 0.27.3-3ubuntu4.1 --- exiv2 (0.27.3-3ubuntu4.1) impish-security; urgency=medium * SECURITY REGRESSION: out of range access that may cause a crash - debian/patches/CVE-2021-37620-4.patch: fix out of range access that may cause a crash (LP: #1941752) - debian/patches/CVE-2021-37620-5.patch: backport to C++98 (a str.pop_back that was added in C++11) - Thanks Simon Schmeißer -- Leonidas Da Silva Barbosa Mon, 10 Jan 2022 10:28:12 -0300 ** Changed in: exiv2 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: exiv2 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Fix Released Status in exiv2 package in Ubuntu: Fix Released Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1955347] Re: rsync works bad with encfs now
It seems to be like this is a bug in encfs rather than in rsync? I
appreciate newer rsync might have changed behaviour, but ultimately
encfs needs to provide a regular (if virtual) filesystem. Where it
doesn't, rsync can't be expected to work.
Is there any specific reason to think that encfs is working correctly in
your failure case?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1955347
Title:
rsync works bad with encfs now
Status in rsync package in Ubuntu:
Incomplete
Bug description:
Hello,
I think rsync works bad with encfs now.
When root uses it, rsync cannot read a directory encrypted with encfs
by a user. More precisely, it cannot read the mounted directory, the
virtual one where the user can read the datas.
Until now there was only a warning like this
"rsync: readlink_stat("/home/claude/Documents_chiffres") failed:
Permission denied (13)"
and the software went on working (only ignoring the content of the mounted
directory and of course without saving this content)
But recently there is this more:
"IO error encountered -- skipping file deletion"
and because of this "skipping file deletion", the software can't work
normally. The destination gets bigger more and more because the deleted files
in the source are not deleted in the destination.
Thanks for reading me.
rsync 3.1.3-8ubuntu0.1
Description:Ubuntu 20.04.3 LTS
Release:20.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1955347/+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 1955997] Re: The airplane hotkey has no function on a HP platform
** Changed in: oem-priority Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1955997 Title: The airplane hotkey has no function on a HP platform Status in OEM Priority Project: In Progress Status in systemd package in Ubuntu: New Status in systemd source package in Focal: New Status in systemd source package in Impish: New Status in systemd source package in Jammy: New Bug description: [Impact] The airplane hokey doesn't work on HP new generation machines. [Test Plan] Press airplane hokey. Before the patch, nothing happens. After the patch, the rfkill works as expected. [Where problems could occur] In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will not work but HP confirmed the new HP generation won't contain the HPQ6001 and also each DM still need to deal with multi-rfkill events because upstream changes[2]. --- In the last year, HP mentions HP machines need to use hp-wireless (HPQ6001) as the rfkill source[1]. However, HP confirms the HPQ6001 has been retired in the platforms since 2022. In the platforms after 2022, there are two sources of rkfill events (intel-hid, atkbd) and HP only guarantee the intel-hid works. Therefore, the upstream already accept the patch[2] to unmask intel-hid and mention this big change in the NEWS. This change makes the pre-2022 HP platforms meet the regression since they have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing function key. Thus, there is a patch[3] to make sure the GNOME could deal with this case smoothly. However, the systemd change will still cause other DEs meet the regression (xfce, KDE, lxde, etc..). Backport systemd change to make HP 2022 platforms work is not the best choice on stable version (focal in this case). We still need a solution to make airplane key works on 2022 HP platforms (intel-hid and atkbd only). The potential solution from my mind that is to maintain a whitelist to unmask intel-hid in ubuntu-patch in focal, something like: ``` evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:* KEYBOARD_KEY_8=wlan # Use hp-wireless instead ``` after "KEYBOARD_KEY_8=unkown". [1] https://bugs.launchpad.net/bugs/1883846 [2] https://github.com/systemd/systemd/pull/20219 [3] https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1955997/+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 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
This bug was fixed in the package exiv2 - 0.27.2-8ubuntu2.7 --- exiv2 (0.27.2-8ubuntu2.7) focal-security; urgency=medium * SECURITY REGRESSION: fix out of range access * Bugfix: Fix regression introduced when fixing CVE-2021-37620 (LP: #1941752) - debian/patches/CVE-2021-37620-4.patch: fix out of range access - debian/patches/CVE-2021-37620-5.patch: backport to C++98 -- Simon Schmeißer Thu, 30 Dec 2021 21:40:13 +0100 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Fix Released Status in exiv2 package in Ubuntu: Fix Released Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1957086] Re: Autopkgtest systemd fail against dnsmasq 2.86 (22.04)
Result of the repro: #2 ipv6 fails and gets into a loop dig @10.241.3.1 -t math.lab #2a - Good case (dnsmasq 2.85) root@j-dnsmasq-release:~# dig @10.241.3.1 -t math.lab dnsmasq: query[] math.lab from 10.241.3.1 dnsmasq: config math.lab is NODATA-IPv6 ; <<>> DiG 9.16.15-Ubuntu <<>> @10.241.3.1 -t math.lab ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48650 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;math.lab. IN ;; Query time: 0 msec ;; SERVER: 10.241.3.1#53(10.241.3.1) ;; WHEN: Tue Jan 11 13:09:21 UTC 2022 ;; MSG SIZE rcvd: 37 #2b - Bad case (dnsmasq 2.86) root@j-dnsmasq-proposed:~# dig @10.241.3.1 -t math.lab dnsmasq: query[] math.lab from 10.241.3.1 dnsmasq: forwarded math.lab to 127.0.0.53 dnsmasq: query[] math.lab from 10.241.3.1 dnsmasq: forwarded math.lab to 127.0.0.53 dnsmasq: query[] math.lab from 10.241.3.1 ... dnsmasq: Maximum number of concurrent DNS queries reached (max: 150) dnsmasq: config error is REFUSED ... repeats infinitely There is no ipv6 answer configured, so it is ok to return an empty/bad answer. But dnsmasq should not fall into a forwarding loop right? Or does this test make a hard configuration mistake (always did) that now in 2.86 exposes an issue, but was always wrong? The original test command of `resolvectl query math.lab` gets into a "wait until timeout" with the new behavior. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1957086 Title: Autopkgtest systemd fail against dnsmasq 2.86 (22.04) Status in dnsmasq package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Full log (same on all architectures): https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/s/systemd/20220106_214401_24d29@/log.gz The test is from systemd: https://github.com/systemd/systemd/blob/main/test/networkd-test.py#L619 Tail of the log: ``` ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/tmp/autopkgtest.NdIvJq/build.fBQ/src/test/networkd-test.py", line 678, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.9/subprocess.py", line 424, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.9/subprocess.py", line 528, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. ``` Tagging update-excuse to be shown in excuses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1957086/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1957086] Re: Autopkgtest systemd fail against dnsmasq 2.86 (22.04)
As usual once you know what you search for the results are much better. It turns out that it might be related to one of those reports: - https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2022q1/016015.html - https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2022q1/016069.html But even better was the finding that Debian at 249-5-2 was affected by the same. - https://ci.debian.net/packages/s/systemd/unstable/amd64/ - https://ci.debian.net/data/autopkgtest/unstable/amd64/s/systemd/16383273/log.gz That seems to be fixed since systemd 249.6-1 and checking that made me find To me there is nothing obvious in regard to this in debian => https://salsa.debian.org/systemd-team/systemd/-/commits/debian/master nor in upstream => https://github.com/systemd/systemd-stable/commits/v249.6 But I think this is enough to get the bug reported and maybe eyes more used to systemd will see the related fix as it seems it must be there somewhere ... @systemd maintainer (Lukas?) does this ring a bell to you or do you see the change that might have fixed this? Also is there a PPA with a Ubuntu build of >=249.6-1 to check if it resolves the issue also in Ubuntu? ** Tags added: update-excuse ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Lukas Märdian (slyon) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1957086 Title: Autopkgtest systemd fail against dnsmasq 2.86 (22.04) Status in dnsmasq package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Full log (same on all architectures): https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/s/systemd/20220106_214401_24d29@/log.gz The test is from systemd: https://github.com/systemd/systemd/blob/main/test/networkd-test.py#L619 Tail of the log: ``` ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/tmp/autopkgtest.NdIvJq/build.fBQ/src/test/networkd-test.py", line 678, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.9/subprocess.py", line 424, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.9/subprocess.py", line 528, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. ``` Tagging update-excuse to be shown in excuses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1957086/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1957086] Re: Autopkgtest systemd fail against dnsmasq 2.86 (22.04)
# FYI cleanup # Minimal Reset (e.g. when switching dnsmasq) killall dnsmasq rm /tmp/dnsmasq* dnsmasq --no-daemon --log-queries --log-facility=/tmp/dnsmasq.log --conf-file=/dev/null --dhcp-leasefile=/tmp/dnsmasq.leases --bind-interfaces --interface=router_eth42 --except-interface=lo --dhcp-range=192.168.5.10,192.168.5.200 --address=/#/192.168.42.1 & dnsmasq --no-daemon --log-queries --log-facility=/tmp/dnsmasq-vpn.log --conf-file=/dev/null --dhcp-leasefile=/dev/null --bind-interfaces --interface=testvpnrouter --except-interface=lo --address=/math.lab/10.241.3.3 --address=/cantina.company/10.241.4.4 & dig @10.241.3.1 -t math.lab ^^ With this I could confirm that switchign the good case to dnsmasq 2.86 makes it enter the forwarding loop. Vice versa switching the bad system to dnsmasq 2.85 makes it work (not entering the loop). # Full cleanup sudo killall dnsmasq sudo rm /run/systemd/network/general.network sudo rm /run/systemd/network/vpn.network sudo rm /run/systemd/resolved.conf.d/test-enable-dnssec.conf for i in testvpnrouter testvpnclient test_eth42 router_eth42; do sudo ip link dev $i down; done for i in testvpnrouter testvpnclient test_eth42 router_eth42; do sudo ip link del dev $i down; done sudo systemctl restart systemd-resolved sudo systemctl restart systemd-networkd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1957086 Title: Autopkgtest systemd fail against dnsmasq 2.86 (22.04) Status in dnsmasq package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Full log (same on all architectures): https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/s/systemd/20220106_214401_24d29@/log.gz The test is from systemd: https://github.com/systemd/systemd/blob/main/test/networkd-test.py#L619 Tail of the log: ``` ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/tmp/autopkgtest.NdIvJq/build.fBQ/src/test/networkd-test.py", line 678, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.9/subprocess.py", line 424, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.9/subprocess.py", line 528, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. ``` Tagging update-excuse to be shown in excuses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1957086/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1957086] Re: Autopkgtest systemd fail against dnsmasq 2.86 (22.04)
Detailed Logs: Before the test: dnsmasq.log is identical dnsmasq-vpn.log as well, except the version number Good Case: ubuntu@autopkgtest:~$ resolvectl query math.lab math.lab: 10.241.3.3 -- link: testvpnrouter -- Information acquired via protocol DNS in 20.8ms. -- Data is authenticated: no; Data was acquired via local or encrypted transport: no -- Data from: network Bad Case: ubuntu@autopkgtest:~$ resolvectl query math.lab math.lab: resolve call failed: Connection timed out After the test: - dnsmasq.log is still identical - dnsmasq-vpn.log is quite different Entries in Good case: Jan 11 11:54:18 dnsmasq[7952]: query[A] math.lab from 10.241.3.1 Jan 11 11:54:18 dnsmasq[7952]: config math.lab is 10.241.3.3 Jan 11 11:54:18 dnsmasq[7952]: query[] math.lab from 10.241.3.1 Jan 11 11:54:18 dnsmasq[7952]: config math.lab is NODATA-IPv6 Entries in Bad case: Jan 11 11:54:16 dnsmasq[8871]: query[A] math.lab from 10.241.3.1 Jan 11 11:54:16 dnsmasq[8871]: config math.lab is 10.241.3.3 Jan 11 11:54:16 dnsmasq[8871]: query[] math.lab from 10.241.3.1 Jan 11 11:54:16 dnsmasq[8871]: forwarded math.lab to 127.0.0.53 Jan 11 11:54:16 dnsmasq[8871]: query[] math.lab from 10.241.3.1 Jan 11 11:54:16 dnsmasq[8871]: forwarded math.lab to 127.0.0.53 ... the last two lines repeat until a timeout occurs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1957086 Title: Autopkgtest systemd fail against dnsmasq 2.86 (22.04) Status in dnsmasq package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Full log (same on all architectures): https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/s/systemd/20220106_214401_24d29@/log.gz The test is from systemd: https://github.com/systemd/systemd/blob/main/test/networkd-test.py#L619 Tail of the log: ``` ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/tmp/autopkgtest.NdIvJq/build.fBQ/src/test/networkd-test.py", line 678, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.9/subprocess.py", line 424, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.9/subprocess.py", line 528, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. ``` Tagging update-excuse to be shown in excuses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1957086/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1957086] Re: Autopkgtest systemd fail against dnsmasq 2.86 (22.04)
Reproducing the case outside the systemd tests (Commands on Ubuntu 22.04, with root permissions) jammy-Proposed has dnsmasq 2.86 right now apt update; apt upgrade -y; apt install dnsmasq-base systemctl reset-failed systemd-networkd systemd-resolved mkdir /run/systemd/resolved.conf.d cat > /run/systemd/resolved.conf.d/test-enable-dnssec.conf << EOF [Resolve] DNSSEC=allow-downgrade LLMNR=no MulticastDNS=no DNSOverTLS=no EOF ip link add name test_eth42 address de:ad:be:ef:47:11 type veth peer name router_eth42 ip a flush dev router_eth42 ip a add 192.168.5.1/24 dev router_eth42 ip link set router_eth42 up dnsmasq --no-daemon --log-queries --log-facility=/tmp/dnsmasq.log --conf-file=/dev/null --dhcp-leasefile=/tmp/dnsmasq.leases --bind- interfaces --interface=router_eth42 --except-interface=lo --dhcp- range=192.168.5.10,192.168.5.200 --address=/#/192.168.42.1 & cat > /run/systemd/network/general.network << EOF [Match] Name=test_eth42 [Network] DHCP=ipv4 IPv6AcceptRA=False DNSSECNegativeTrustAnchors=search.example.com EOF ip link add name testvpnclient type veth peer name testvpnrouter ip a flush dev testvpnrouter ip a add 10.241.3.1/24 dev testvpnrouter ip link set testvpnrouter up dnsmasq --no-daemon --log-queries --log-facility=/tmp/dnsmasq-vpn.log --conf-file=/dev/null --dhcp-leasefile=/dev/null --bind-interfaces --interface=testvpnrouter --except-interface=lo --address=/math.lab/10.241.3.3 --address=/cantina.company/10.241.4.4 & cat > /run/systemd/network/vpn.network << EOF [Match] Name=testvpnclient [Network] IPv6AcceptRA=False Address=10.241.3.2/24 DNS=10.241.3.1 Domains=~company ~lab DNSSECNegativeTrustAnchors=company la EOF systemctl restart systemd-networkd /usr/lib/systemd/systemd-networkd-wait-online --interface test_eth42 --interface=testvpnclient --timeout=20 systemctl restart systemd-resolved # The original test runs "resolvectl query math.lab" # That would probe everything, do this step by step #1 ipv4 works and looks pretty much the same result on good/bad case dig @10.241.3.1 -t A math.lab root@j-dnsmasq-proposed:~# dig @10.241.3.1 -t A math.lab dnsmasq: query[A] math.lab from 10.241.3.1 dnsmasq: config math.lab is 10.241.3.3 ; <<>> DiG 9.16.15-Ubuntu <<>> @10.241.3.1 -t A math.lab ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11869 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;math.lab. IN A ;; ANSWER SECTION: math.lab. 0 IN A 10.241.3.3 ;; Query time: 0 msec ;; SERVER: 10.241.3.1#53(10.241.3.1) ;; WHEN: Tue Jan 11 13:09:07 UTC 2022 ;; MSG SIZE rcvd: 53 #2 ipv6 fails and gets into a loop dig @10.241.3.1 -t math.lab -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1957086 Title: Autopkgtest systemd fail against dnsmasq 2.86 (22.04) Status in dnsmasq package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Full log (same on all architectures): https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/s/systemd/20220106_214401_24d29@/log.gz The test is from systemd: https://github.com/systemd/systemd/blob/main/test/networkd-test.py#L619 Tail of the log: ``` ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/tmp/autopkgtest.NdIvJq/build.fBQ/src/test/networkd-test.py", line 678, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.9/subprocess.py", line 424, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.9/subprocess.py", line 528, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. ``` Tagging update-excuse to be shown in excuses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1957086/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1949970] Re: attempt to dlopen nonexistent pam_kwallet.so spams log
This bug was fixed in the package lightdm - 1.30.0-0ubuntu4.21.10.1 --- lightdm (1.30.0-0ubuntu4.21.10.1) impish; urgency=medium * debian/lightdm.lightdm-greeter.pam, debian/lightdm.pam: - Suppress log error for missing pam modules (LP: #1949970) -- Dan Streetman Fri, 05 Nov 2021 10:18:32 -0400 ** Changed in: lightdm (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1949970 Title: attempt to dlopen nonexistent pam_kwallet.so spams log Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Bionic: New Status in lightdm source package in Focal: Fix Released Status in lightdm source package in Hirsute: Fix Committed Status in lightdm source package in Impish: Fix Released Status in lightdm source package in Jammy: Fix Released Bug description: [impact] lightdm's pam.d config includes an attempt to dlopen pam_kwallet.so as well as pam_kwallet5.so, however pam_wallet.so comes from pam-kwallet which died around Trusty (https://launchpad.net/ubuntu/+source/pam- kwallet) while pam_kwallet5.so comes from kwallet-pam which provides only the newer '5' version, not the older unversioned library file. This results in repeated spam error messages in the system log complaining about failure to load pam_kwallet.so [test case] install/enable lightdm and check system log at boot for messages like: Nov 04 18:17:47 thrain lightdm[2510]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Nov 04 18:17:47 thrain lightdm[2510]: PAM adding faulty module: pam_kwallet.so [regression potential] any regression would likely cause problems during login and/or missing or extra log messages during pam authentication. [scope] this is needed in all releases [other info] https://github.com/canonical/lightdm/pull/216 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1949970/+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 1949970] Update Released
The verification of the Stable Release Update for lightdm has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1949970 Title: attempt to dlopen nonexistent pam_kwallet.so spams log Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Bionic: New Status in lightdm source package in Focal: Fix Released Status in lightdm source package in Hirsute: Fix Committed Status in lightdm source package in Impish: Fix Released Status in lightdm source package in Jammy: Fix Released Bug description: [impact] lightdm's pam.d config includes an attempt to dlopen pam_kwallet.so as well as pam_kwallet5.so, however pam_wallet.so comes from pam-kwallet which died around Trusty (https://launchpad.net/ubuntu/+source/pam- kwallet) while pam_kwallet5.so comes from kwallet-pam which provides only the newer '5' version, not the older unversioned library file. This results in repeated spam error messages in the system log complaining about failure to load pam_kwallet.so [test case] install/enable lightdm and check system log at boot for messages like: Nov 04 18:17:47 thrain lightdm[2510]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Nov 04 18:17:47 thrain lightdm[2510]: PAM adding faulty module: pam_kwallet.so [regression potential] any regression would likely cause problems during login and/or missing or extra log messages during pam authentication. [scope] this is needed in all releases [other info] https://github.com/canonical/lightdm/pull/216 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1949970/+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 1949970] Re: attempt to dlopen nonexistent pam_kwallet.so spams log
This bug was fixed in the package lightdm - 1.30.0-0ubuntu4~20.04.2 --- lightdm (1.30.0-0ubuntu4~20.04.2) focal; urgency=medium * debian/lightdm.lightdm-greeter.pam, debian/lightdm.pam: - Suppress log error for missing pam modules (LP: #1949970) -- Dan Streetman Fri, 05 Nov 2021 10:20:53 -0400 ** Changed in: lightdm (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1949970 Title: attempt to dlopen nonexistent pam_kwallet.so spams log Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Bionic: New Status in lightdm source package in Focal: Fix Released Status in lightdm source package in Hirsute: Fix Committed Status in lightdm source package in Impish: Fix Released Status in lightdm source package in Jammy: Fix Released Bug description: [impact] lightdm's pam.d config includes an attempt to dlopen pam_kwallet.so as well as pam_kwallet5.so, however pam_wallet.so comes from pam-kwallet which died around Trusty (https://launchpad.net/ubuntu/+source/pam- kwallet) while pam_kwallet5.so comes from kwallet-pam which provides only the newer '5' version, not the older unversioned library file. This results in repeated spam error messages in the system log complaining about failure to load pam_kwallet.so [test case] install/enable lightdm and check system log at boot for messages like: Nov 04 18:17:47 thrain lightdm[2510]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Nov 04 18:17:47 thrain lightdm[2510]: PAM adding faulty module: pam_kwallet.so [regression potential] any regression would likely cause problems during login and/or missing or extra log messages during pam authentication. [scope] this is needed in all releases [other info] https://github.com/canonical/lightdm/pull/216 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1949970/+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
