[Touch-packages] [Bug 1977916] [NEW] package libdbus-1-3 1.12.16-2ubuntu2.2 [modified: usr/share/doc/libdbus-1-3/NEWS.gz usr/share/doc/libdbus-1-3/changelog.Debian.gz] failed to install/upgrade: tryin
Public bug reported: trying to install wine 7 version ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libdbus-1-3 1.12.16-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jun 8 00:49:06 2022 DuplicateSignature: package:libdbus-1-3:1.12.16-2ubuntu2.2 [modified: usr/share/doc/libdbus-1-3/NEWS.gz usr/share/doc/libdbus-1-3/changelog.Debian.gz] Unpacking libapparmor1:i386 (2.13.3-7ubuntu5.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-9whLYQ/04-libapparmor1_2.13.3-7ubuntu5.1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libapparmor1/changelog.Debian.gz', which is different from other instances of package libapparmor1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libdbus-1-3/NEWS.gz', which is different from other instances of package libdbus-1-3:i386 InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.8 SourcePackage: dbus Title: package libdbus-1-3 1.12.16-2ubuntu2.2 [modified: usr/share/doc/libdbus-1-3/NEWS.gz usr/share/doc/libdbus-1-3/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libdbus-1-3/NEWS.gz', which is different from other instances of package libdbus-1-3:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check package-conflict -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1977916 Title: package libdbus-1-3 1.12.16-2ubuntu2.2 [modified: usr/share/doc/libdbus-1-3/NEWS.gz usr/share/doc/libdbus-1-3/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libdbus-1-3/NEWS.gz', which is different from other instances of package libdbus-1-3:i386 Status in dbus package in Ubuntu: New Bug description: trying to install wine 7 version ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libdbus-1-3 1.12.16-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jun 8 00:49:06 2022 DuplicateSignature: package:libdbus-1-3:1.12.16-2ubuntu2.2 [modified: usr/share/doc/libdbus-1-3/NEWS.gz usr/share/doc/libdbus-1-3/changelog.Debian.gz] Unpacking libapparmor1:i386 (2.13.3-7ubuntu5.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-9whLYQ/04-libapparmor1_2.13.3-7ubuntu5.1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libapparmor1/changelog.Debian.gz', which is different from other instances of package libapparmor1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libdbus-1-3/NEWS.gz', which is different from other instances of package libdbus-1-3:i386 InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.8 SourcePackage: dbus Title: package libdbus-1-3 1.12.16-2ubuntu2.2 [modified: usr/share/doc/libdbus-1-3/NEWS.gz usr/share/doc/libdbus-1-3/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libdbus-1-3/NEWS.gz', which is different from other instances of package libdbus-1-3:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1977916/+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 1977917] [NEW] package libxau6 1:1.0.9-0ubuntu1 [modified: usr/share/doc/libxau6/changelog.Debian.gz usr/share/doc/libxau6/copyright] failed to install/upgrade: trying to overwri
Public bug reported: trying to install wine 7 version ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libxau6 1:1.0.9-0ubuntu1 [modified: usr/share/doc/libxau6/changelog.Debian.gz usr/share/doc/libxau6/copyright] ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Wed Jun 8 00:52:50 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ErrorMessage: trying to overwrite shared '/usr/share/doc/libxau6/changelog.Debian.gz', which is different from other instances of package libxau6:i386 GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1028:0622] InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Dell Inc. Inspiron 3847 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-48-generic root=UUID=0522bd09-f431-472d-a066-6c45ce00f83c ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.8 SourcePackage: libxau Title: package libxau6 1:1.0.9-0ubuntu1 [modified: usr/share/doc/libxau6/changelog.Debian.gz usr/share/doc/libxau6/copyright] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libxau6/changelog.Debian.gz', which is different from other instances of package libxau6:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2019 dmi.bios.release: 65.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 088DT1 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/07/2019:br65.10:svnDellInc.:pnInspiron3847:pvr:rvnDellInc.:rn088DT1:rvrA01:cvnDellInc.:ct3:cvr:sku0622: dmi.product.family: To be filled by O.E.M. dmi.product.name: Inspiron 3847 dmi.product.sku: 0622 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A 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: libxau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxau in Ubuntu. https://bugs.launchpad.net/bugs/1977917 Title: package libxau6 1:1.0.9-0ubuntu1 [modified: usr/share/doc/libxau6/changelog.Debian.gz usr/share/doc/libxau6/copyright] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libxau6/changelog.Debian.gz', which is different from other instances of package libxau6:i386 Status in libxau package in Ubuntu: New Bug description: trying to install wine 7 version ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libxau6 1:1.0.9-0ubuntu1 [modified: usr/share/doc/libxau6/changelog.Debian.gz usr/share/doc/libxau6/copyright] ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Wed Jun 8 00:52:50 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ErrorMessage: trying to overwrite shared '/usr/share/doc/libxau6/changelog.Debian.gz', which is different from other instances of package libxau6:i386 GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1028:0622] InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Dell Inc. Inspiron 3847 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-48-generic root=UUID=0522bd09-f431-472d-a066-6c45ce00f83c ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.8 SourcePackage: libxau Title: package
[Touch-packages] [Bug 1977914] [NEW] package libapparmor1 2.13.3-7ubuntu5.1 [modified: usr/share/doc/libapparmor1/changelog.Debian.gz usr/share/doc/libapparmor1/copyright] failed to install/upgrade: t
Public bug reported: trying to install wine version 7 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libapparmor1 2.13.3-7ubuntu5.1 [modified: usr/share/doc/libapparmor1/changelog.Debian.gz usr/share/doc/libapparmor1/copyright] ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jun 8 00:49:06 2022 DuplicateSignature: package:libapparmor1:2.13.3-7ubuntu5.1 [modified: usr/share/doc/libapparmor1/changelog.Debian.gz usr/share/doc/libapparmor1/copyright] Unpacking libapparmor1:i386 (2.13.3-7ubuntu5.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-9whLYQ/04-libapparmor1_2.13.3-7ubuntu5.1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libapparmor1/changelog.Debian.gz', which is different from other instances of package libapparmor1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libapparmor1/changelog.Debian.gz', which is different from other instances of package libapparmor1:i386 InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.13.0-48-generic root=UUID=0522bd09-f431-472d-a066-6c45ce00f83c ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.8 SourcePackage: apparmor Title: package libapparmor1 2.13.3-7ubuntu5.1 [modified: usr/share/doc/libapparmor1/changelog.Debian.gz usr/share/doc/libapparmor1/copyright] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libapparmor1/changelog.Debian.gz', which is different from other instances of package libapparmor1:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check package-conflict -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1977914 Title: package libapparmor1 2.13.3-7ubuntu5.1 [modified: usr/share/doc/libapparmor1/changelog.Debian.gz usr/share/doc/libapparmor1/copyright] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libapparmor1/changelog.Debian.gz', which is different from other instances of package libapparmor1:i386 Status in apparmor package in Ubuntu: New Bug description: trying to install wine version 7 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libapparmor1 2.13.3-7ubuntu5.1 [modified: usr/share/doc/libapparmor1/changelog.Debian.gz usr/share/doc/libapparmor1/copyright] ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jun 8 00:49:06 2022 DuplicateSignature: package:libapparmor1:2.13.3-7ubuntu5.1 [modified: usr/share/doc/libapparmor1/changelog.Debian.gz usr/share/doc/libapparmor1/copyright] Unpacking libapparmor1:i386 (2.13.3-7ubuntu5.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-9whLYQ/04-libapparmor1_2.13.3-7ubuntu5.1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libapparmor1/changelog.Debian.gz', which is different from other instances of package libapparmor1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libapparmor1/changelog.Debian.gz', which is different from other instances of package libapparmor1:i386 InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.13.0-48-generic root=UUID=0522bd09-f431-472d-a066-6c45ce00f83c ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.8 SourcePackage: apparmor Title: package libapparmor1 2.13.3-7ubuntu5.1 [modified: usr/share/doc/libapparmor1/changelog.Debian.gz usr/share/doc/libapparmor1/copyright] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libapparmor1/changelog.Debian.gz', which is different from other instances of package libapparmor1:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1977914/+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 1977915] [NEW] package libbsd0 0.10.0-1 [modified: usr/share/doc/libbsd0/changelog.Debian.gz usr/share/doc/libbsd0/copyright] failed to install/upgrade: trying to overwrite share
Public bug reported: trying to install wine version 7 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libbsd0 0.10.0-1 [modified: usr/share/doc/libbsd0/changelog.Debian.gz usr/share/doc/libbsd0/copyright] ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jun 8 00:49:06 2022 DuplicateSignature: package:libbsd0:0.10.0-1 [modified: usr/share/doc/libbsd0/changelog.Debian.gz usr/share/doc/libbsd0/copyright] Unpacking libapparmor1:i386 (2.13.3-7ubuntu5.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-9whLYQ/04-libapparmor1_2.13.3-7ubuntu5.1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libapparmor1/changelog.Debian.gz', which is different from other instances of package libapparmor1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libbsd0/changelog.Debian.gz', which is different from other instances of package libbsd0:i386 InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.8 SourcePackage: libbsd Title: package libbsd0 0.10.0-1 [modified: usr/share/doc/libbsd0/changelog.Debian.gz usr/share/doc/libbsd0/copyright] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libbsd0/changelog.Debian.gz', which is different from other instances of package libbsd0:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libbsd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check package-conflict -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libbsd in Ubuntu. https://bugs.launchpad.net/bugs/1977915 Title: package libbsd0 0.10.0-1 [modified: usr/share/doc/libbsd0/changelog.Debian.gz usr/share/doc/libbsd0/copyright] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libbsd0/changelog.Debian.gz', which is different from other instances of package libbsd0:i386 Status in libbsd package in Ubuntu: New Bug description: trying to install wine version 7 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libbsd0 0.10.0-1 [modified: usr/share/doc/libbsd0/changelog.Debian.gz usr/share/doc/libbsd0/copyright] ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jun 8 00:49:06 2022 DuplicateSignature: package:libbsd0:0.10.0-1 [modified: usr/share/doc/libbsd0/changelog.Debian.gz usr/share/doc/libbsd0/copyright] Unpacking libapparmor1:i386 (2.13.3-7ubuntu5.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-9whLYQ/04-libapparmor1_2.13.3-7ubuntu5.1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libapparmor1/changelog.Debian.gz', which is different from other instances of package libapparmor1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libbsd0/changelog.Debian.gz', which is different from other instances of package libbsd0:i386 InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.8 SourcePackage: libbsd Title: package libbsd0 0.10.0-1 [modified: usr/share/doc/libbsd0/changelog.Debian.gz usr/share/doc/libbsd0/copyright] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libbsd0/changelog.Debian.gz', which is different from other instances of package libbsd0:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libbsd/+bug/1977915/+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 1977710] Re: /etc/adduser.conf.dpkg-save created by postinst since 3.121ubuntu1
>From what I can see of this postinst this looks to be a bug from adduser in debian itself - and would appear to come from https://salsa.debian.org/debian/adduser/-/blob/master/debian/postinst#L33 - ie. if the default value is unchanged then an /etc/adduser.conf.dpkg- save is always generated when the value of DIR_MODE is appended to /etc/adduser.conf. Can you confirm if this also occurs when debootstrapping a system from debian? ** Changed in: adduser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/1977710 Title: /etc/adduser.conf.dpkg-save created by postinst since 3.121ubuntu1 Status in adduser package in Ubuntu: Incomplete Bug description: Since version 3.121ubuntu1 adduser's postinst script creates /etc/adduser.conf.dpkg-save file on debootstrap's root filesystem, that is, even when /etc/adduser.conf doesn't exist prior to package installation. Because of the change below the postinst script changes packaged /etc/adduser.conf and creates /etc/adduser.conf.dpkg-save as a backup: - Enable private home directories by default (LP: #48734) + Set DIR_MODE=0750 in the default adduser.conf + Change the description and default value to select private home directories by default in debconf template + Change the DIR_MODE when private home directories is configured via debconf from 0751 to 0750 to ensure files are truly private The .dpkg-save file shouldn't be present on debootstrapped system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1977710/+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 1977897] [NEW] package initramfs-tools 0.140ubuntu13 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Public bug reported: Error just popped up while I was browsing, i.e. I was not upgrading at the time. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: initramfs-tools 0.140ubuntu13 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: ntfs-3g:amd64: Install libntfs-3g89:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Jun 7 20:22:10 2022 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-10-30 (220 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: /usr/bin/python3.10, Python 3.10.4, python-is-python3, 3.9.2-2 RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.5 SourcePackage: initramfs-tools Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-04-29 (39 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1977897 Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Error just popped up while I was browsing, i.e. I was not upgrading at the time. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: initramfs-tools 0.140ubuntu13 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: ntfs-3g:amd64: Install libntfs-3g89:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Jun 7 20:22:10 2022 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-10-30 (220 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: /usr/bin/python3.10, Python 3.10.4, python-is-python3, 3.9.2-2 RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.5 SourcePackage: initramfs-tools Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-04-29 (39 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1977897/+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 1977884] Re: package e2fsprogs 1.45.5-2ubuntu1 failed to install/upgrade: trying to overwrite '/etc/mke2fs.conf', which is also in package android-sdk-platform-tools 27.0.0+12
Hi Rabee, The metapackage android-sdk-platform-tools installs several packages, which includes e2fsprogs (https://packages.ubuntu.com/focal/android-sdk- platform-tools). It also make a symbolic link from /usr/lib/android- sdk/platform-tools/mke2fs.conf to /etc/mke2fs.conf All of which should not cause package conflicts. I attempted reproduce your bug by installing the latest version of Zorin in a VM (I had to use Zorin 16, since the default apt sources in Zorin 15 did not work). Then I installed android-sdk-platform-tools which brought e2fsprogs to version 1.45.5-2ubuntu1. The upgrade from e2fsprogs to version 1.45.5-2ubuntu1.1 worked smoothly on my VM environment. Does `ls -la /usr/lib/android-sdk/platform-tools/mke2fs.conf` print something like: `/usr/lib/android-sdk/platform-tools/mke2fs.conf -> /etc/mke2fs.conf`? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1977884 Title: package e2fsprogs 1.45.5-2ubuntu1 failed to install/upgrade: trying to overwrite '/etc/mke2fs.conf', which is also in package android-sdk- platform-tools 27.0.0+12 Status in e2fsprogs package in Ubuntu: New Bug description: The error happens during updates ProblemType: Package DistroRelease: Ubuntu 20.04 Package: e2fsprogs 1.45.5-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-113.127-generic 5.4.181 Uname: Linux 5.4.0-113-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 7 11:06:48 2022 DpkgTerminalLog: Preparing to unpack .../00-e2fsprogs_1.45.5-2ubuntu1.1_amd64.deb ... Unpacking e2fsprogs (1.45.5-2ubuntu1.1) over (1.45.5-2ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-oRpMVG/00-e2fsprogs_1.45.5-2ubuntu1.1_amd64.deb (--unpack): trying to overwrite '/etc/mke2fs.conf', which is also in package android-sdk-platform-tools 27.0.0+12 DuplicateSignature: package:e2fsprogs:1.45.5-2ubuntu1 Unpacking e2fsprogs (1.45.5-2ubuntu1.1) over (1.45.5-2ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-oRpMVG/00-e2fsprogs_1.45.5-2ubuntu1.1_amd64.deb (--unpack): trying to overwrite '/etc/mke2fs.conf', which is also in package android-sdk-platform-tools 27.0.0+12 ErrorMessage: trying to overwrite '/etc/mke2fs.conf', which is also in package android-sdk-platform-tools 27.0.0+12 InstallationDate: Installed on 2020-06-05 (732 days ago) InstallationMedia: Zorin-OS 15.1 Education 64bit Python3Details: /usr/bin/python3.8, Python 3.8.10, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.18, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.8 SourcePackage: e2fsprogs Title: package e2fsprogs 1.45.5-2ubuntu1 failed to install/upgrade: trying to overwrite '/etc/mke2fs.conf', which is also in package android-sdk-platform-tools 27.0.0+12 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1977884/+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 1948752] Re: apparmor is logging too many messages
with in the profile block, eg.
profile redshift {
or something similar, add the following rules
dbus send bus="system" path="/org/freedesktop/DBus"
interface="org.freedesktop.DBus"
member="{GetNameOwner,StartServiceByName,AddMatch}",
dbus send bus="system" path="/org/freedesktop/GeoClue2/Manager"
interface="org.freedesktop.DBus.Properties" member="GetAll",
dbus send bus="system" path="/org/freedesktop/GeoClue2/Manager"
interface="org.freedesktop.GeoClue2.Manager" member="GetClient",
I think I got everything that is needed but its possible I missed a couple
cases, also there may be other rules needed not covered by the above logs
after adding the above rules you need to reload the profile.
systemctl reload apparmor
should do it
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1948752
Title:
apparmor is logging too many messages
Status in Redshift:
New
Status in apparmor package in Ubuntu:
New
Bug description:
Unfortunately, this bug does not seem to be fixed yet.
My syslog is flooded with ALLOWED messages regarding redshift.
My system is a Kubuntu 21.04.
AppArmor is V. 3.0.0-0ubuntu7.1
Attached you'll find an excerpt from /var/log/syslog for the last 5
minutes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/redshift/+bug/1948752/+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 1977564] Re: wireplumber conflicts with pipewire-media-session & needs fixing
I'm assigning this to me for tracking but I won't be able to look into this more until next week. Sorry. ** Changed in: wireplumber (Ubuntu) Assignee: (unassigned) => Jeremy Bicha (jbicha) ** Changed in: ubuntu-meta (Ubuntu) Assignee: (unassigned) => Jeremy Bicha (jbicha) ** Changed in: pipewire-media-session (Ubuntu) Assignee: (unassigned) => Jeremy Bicha (jbicha) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1977564 Title: wireplumber conflicts with pipewire-media-session & needs fixing Status in pipewire-media-session package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: Triaged Status in wireplumber package in Ubuntu: Triaged Status in pipewire-media-session package in Debian: Confirmed Bug description: This issue was reported on IRC and we should probably fix it before installing wireplumber by default so I'm setting the block-proposed tag. https://i.imgur.com/L5VFZO8.png wireplumber is apparently too forceful in how it enables PipeWire. Both Arch Linux and Debian had to https://archlinux.org/news/undone-replacement-of-pipewire-media- session-with-wireplumber/ Is it necessary for wireplumber to conflict with pipewire-media- session? Should we add Replaces? What files does pipewire-media-session need to clean up when it is removed? See https://salsa.debian.org/gnome-team/gnome-remote- desktop/-/commit/52799cfd for an example of how files that aren't technically conffiles can be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire-media-session/+bug/1977564/+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 1977884] [NEW] package e2fsprogs 1.45.5-2ubuntu1 failed to install/upgrade: trying to overwrite '/etc/mke2fs.conf', which is also in package android-sdk-platform-tools 27.0.0+12
Public bug reported: The error happens during updates ProblemType: Package DistroRelease: Ubuntu 20.04 Package: e2fsprogs 1.45.5-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-113.127-generic 5.4.181 Uname: Linux 5.4.0-113-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 7 11:06:48 2022 DpkgTerminalLog: Preparing to unpack .../00-e2fsprogs_1.45.5-2ubuntu1.1_amd64.deb ... Unpacking e2fsprogs (1.45.5-2ubuntu1.1) over (1.45.5-2ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-oRpMVG/00-e2fsprogs_1.45.5-2ubuntu1.1_amd64.deb (--unpack): trying to overwrite '/etc/mke2fs.conf', which is also in package android-sdk-platform-tools 27.0.0+12 DuplicateSignature: package:e2fsprogs:1.45.5-2ubuntu1 Unpacking e2fsprogs (1.45.5-2ubuntu1.1) over (1.45.5-2ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-oRpMVG/00-e2fsprogs_1.45.5-2ubuntu1.1_amd64.deb (--unpack): trying to overwrite '/etc/mke2fs.conf', which is also in package android-sdk-platform-tools 27.0.0+12 ErrorMessage: trying to overwrite '/etc/mke2fs.conf', which is also in package android-sdk-platform-tools 27.0.0+12 InstallationDate: Installed on 2020-06-05 (732 days ago) InstallationMedia: Zorin-OS 15.1 Education 64bit Python3Details: /usr/bin/python3.8, Python 3.8.10, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.18, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.8 SourcePackage: e2fsprogs Title: package e2fsprogs 1.45.5-2ubuntu1 failed to install/upgrade: trying to overwrite '/etc/mke2fs.conf', which is also in package android-sdk-platform-tools 27.0.0+12 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: e2fsprogs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check package-conflict -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1977884 Title: package e2fsprogs 1.45.5-2ubuntu1 failed to install/upgrade: trying to overwrite '/etc/mke2fs.conf', which is also in package android-sdk- platform-tools 27.0.0+12 Status in e2fsprogs package in Ubuntu: New Bug description: The error happens during updates ProblemType: Package DistroRelease: Ubuntu 20.04 Package: e2fsprogs 1.45.5-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-113.127-generic 5.4.181 Uname: Linux 5.4.0-113-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 7 11:06:48 2022 DpkgTerminalLog: Preparing to unpack .../00-e2fsprogs_1.45.5-2ubuntu1.1_amd64.deb ... Unpacking e2fsprogs (1.45.5-2ubuntu1.1) over (1.45.5-2ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-oRpMVG/00-e2fsprogs_1.45.5-2ubuntu1.1_amd64.deb (--unpack): trying to overwrite '/etc/mke2fs.conf', which is also in package android-sdk-platform-tools 27.0.0+12 DuplicateSignature: package:e2fsprogs:1.45.5-2ubuntu1 Unpacking e2fsprogs (1.45.5-2ubuntu1.1) over (1.45.5-2ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-oRpMVG/00-e2fsprogs_1.45.5-2ubuntu1.1_amd64.deb (--unpack): trying to overwrite '/etc/mke2fs.conf', which is also in package android-sdk-platform-tools 27.0.0+12 ErrorMessage: trying to overwrite '/etc/mke2fs.conf', which is also in package android-sdk-platform-tools 27.0.0+12 InstallationDate: Installed on 2020-06-05 (732 days ago) InstallationMedia: Zorin-OS 15.1 Education 64bit Python3Details: /usr/bin/python3.8, Python 3.8.10, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.18, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.8 SourcePackage: e2fsprogs Title: package e2fsprogs 1.45.5-2ubuntu1 failed to install/upgrade: trying to overwrite '/etc/mke2fs.conf', which is also in package android-sdk-platform-tools 27.0.0+12 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1977884/+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 1948752] Re: apparmor is logging too many messages
Which would be? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1948752 Title: apparmor is logging too many messages Status in Redshift: New Status in apparmor package in Ubuntu: New Bug description: Unfortunately, this bug does not seem to be fixed yet. My syslog is flooded with ALLOWED messages regarding redshift. My system is a Kubuntu 21.04. AppArmor is V. 3.0.0-0ubuntu7.1 Attached you'll find an excerpt from /var/log/syslog for the last 5 minutes. To manage notifications about this bug go to: https://bugs.launchpad.net/redshift/+bug/1948752/+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 1933796] Re: resume from suspend while connected to power results in roaring fans
give me a day or two to test it. currently i am actually annoyed with another bug: closing the lid does not trigger hibernation anymore; i have to explicitly choose hibernation from the menu. -- 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/1933796 Title: resume from suspend while connected to power results in roaring fans Status in systemd package in Ubuntu: Incomplete Bug description: since upgrade to ubuntu 20.10 my thinkpad x1 carbon gen5 resumes from suspend with a roaring fan. i have to make sure to start the resume while the power cord is not connected, let it wake up fully and only then connect the power cord. this is quite an annoying regression, still persisting in ubuntu 21.04, since there is no way to calm the fan noise except to do a complete shutdown and power on cycle (reboot still keeps the fan at max). ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3.1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sun Jun 27 18:20:13 2021 InstallationDate: Installed on 2021-05-10 (48 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 004: ID 1199:9079 Sierra Wireless, Inc. EM7455 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HR0068GE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=6e4248be-ae78-4e70-a7c0-88bada1c53a8 ro mitigations=off quiet SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2017 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET39W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HR0068GE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrN1MET39W(1.24):bd09/27/2017:br1.24:efr1.17:svnLENOVO:pn20HR0068GE:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HR0068GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HR0068GE dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1933796/+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 1619258] Re: netplan should allow NICs to be disconnected and not stall the boot
@tbennett6421 Yes, please make use of the "optional: true" stanza in your interface definitions. https://netplan.io/reference/#common-properties-for-all-device-types -- 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/1619258 Title: netplan should allow NICs to be disconnected and not stall the boot Status in Snappy: Fix Released Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: in older snappy image we used to set "allow-hotplug" in /etc/network/interfaces.d/ when configuring a NIC to avoid the boot to completely stall or to be stuck for 5min when trying to find an internet connection. with recent versions of netplan the configuration seems to be back to require a network to be up before moving on with them boot so that booting takes forever until the network connection times out. netplan should make the system check the physical link status when trying to bring up a network device instead of stalling the boot. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1619258/+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 1977764] Re: kernel modules "zstd" and "z3fold" missing.
Ok, thanks for the fast reply. Hope you have a good day :D -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1977764 Title: kernel modules "zstd" and "z3fold" missing. Status in linux-raspi package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: New Status in linux-raspi source package in Jammy: New Status in ubuntu-settings source package in Jammy: New Status in linux-raspi source package in Kinetic: New Status in ubuntu-settings source package in Kinetic: New Bug description: The modules "zstd" and "z3fold" are missing despite being configured for zswap in "/boot/firmware/cmdline.txt." Messages appear on boot display that state they do not exist and so instead use compressor "lzo" and pool "zbud". Ubuntu version is 22.04 LTS flashed from the official image. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8 ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30 Uname: Linux 5.15.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 6 17:29:00 2022 ImageMediaBuild: 20220419 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1977764/+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 1973734] Re: FTBFS on riscv64 in focal
** Changed in: pulseaudio (Ubuntu Focal) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: pulseaudio (Ubuntu Focal) Importance: Undecided => Low ** Changed in: pulseaudio (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1973734 Title: FTBFS on riscv64 in focal Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Bug description: [Impact] * FTBFS on riscv64 in focal in unittest of volume test * Disable that unit test, as later releases do not run unittests on riscv64, and it's better to have up to date pulseaudio on riscv64 (with many security fixes), even if it doesn't completely correctly work. [Test Plan] * autopkgtests pass * riscv64 build is successful [Where problems could occur] * volume-test probably indicates that one can't set volume correctly on riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1973734/+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 1877194] Re: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot
** Tags removed: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1877194 Title: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: New Status in pulseaudio source package in Kinetic: Triaged Status in ubuntu-settings source package in Kinetic: New Bug description: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. In short: 1. Boot system 2. "Analogue Output - RODE NT-USB" is selected by default. I want to use "Line Out - Built-in Audio", which I choose. 3. Reboot. 4 Output device is now back to "Analogue Output - RODE NT-USB". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marcus 1604 F pulseaudio /dev/snd/controlC0: marcus 1604 F pulseaudio /dev/snd/controlC1: marcus 1604 F pulseaudio /dev/snd/pcmC1D0c: marcus 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1877194/+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 1969396] Re: Right Alt not working reliably as compose key unless the layout in effect is first in the list of sources
While an annoying issue and a regression, it's impacting some configurations only and is workaroundable so we are not going to handle it as a rls issue. We will work on trying to provide a fix if possible though ** Tags removed: rls-jj-incoming ** Tags added: rls-jj-notfixing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1969396 Title: Right Alt not working reliably as compose key unless the layout in effect is first in the list of sources Status in gnome-control-center package in Ubuntu: New Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: I noticed after upgrade from impish to jammy that my compose key is not working correctly. Going into gnome-control-center -> Keyboard, I see that 'Alternate Characters Key' and 'Compose Key' are both set to Right Alt. Setting Alternate Characters Key to None, and moving the Compose Key setting around between different options (and then back to Right Alt), the behavior of the Right Alt key is still AltGr and not Compose. From xev: KeyPress event, serial 37, synthetic NO, window 0x401, root 0x50e, subw 0x0, time 287242336, (310,502), root:(434,617), state 0x10, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x401, root 0x50e, subw 0x0, time 287242456, (310,502), root:(434,617), state 0x90, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XFilterEvent returns: False ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu12 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 18 16:01:10 2022 InstallationDate: Installed on 2019-12-23 (847 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-04-15 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1969396/+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 1969959] Re: [nouveau] Weird colors after startup (Ubuntu 22.04)
We aren't considering the issue as rls target at this point, it's on a limited set of hardware and the nvidia drivers don't have the issue and can we used instead -- 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/1969959 Title: [nouveau] Weird colors after startup (Ubuntu 22.04) Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: [Workaround/Fix] 1. When starting the Ubuntu live image, select the option 'Ubuntu (safe graphics)' from the boot menu. 2. During installation be sure to select the third-party software option checkbox in order to get the right Nvidia driver installed. [Original Description] I started Ubuntu 22.04 from a live pen drive. Everything seems fine, the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu appears. When hitting "Try Ubuntu", the screen turns black for a couple of seconds and then re-appears in yellow and brown colors, feels like a 4 color display (white, black, yellow and orange) and I can hardly see anything - sending this bug report from that live system right after starting it up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.470 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:54:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7C56 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969959/+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 1969959] Re: [nouveau] Weird colors after startup (Ubuntu 22.04)
sorry the previous mention to pipewire was for bug #1877194 ** Tags removed: rls-jj-incoming ** Tags added: rls-jj-notfixing -- 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/1969959 Title: [nouveau] Weird colors after startup (Ubuntu 22.04) Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: [Workaround/Fix] 1. When starting the Ubuntu live image, select the option 'Ubuntu (safe graphics)' from the boot menu. 2. During installation be sure to select the third-party software option checkbox in order to get the right Nvidia driver installed. [Original Description] I started Ubuntu 22.04 from a live pen drive. Everything seems fine, the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu appears. When hitting "Try Ubuntu", the screen turns black for a couple of seconds and then re-appears in yellow and brown colors, feels like a 4 color display (white, black, yellow and orange) and I can hardly see anything - sending this bug report from that live system right after starting it up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.470 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:54:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7C56 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969959/+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 1964494] Re: Setting DuplicateAddressDetection=none doesn't disable DAD for link-local IPs
This SRU should be combined with LP: #1969375 as uploaded in 249.11-0ubuntu3.3 (containing some more autopkgtest related changes) -- 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/1964494 Title: Setting DuplicateAddressDetection=none doesn't disable DAD for link- local IPs Status in systemd: Fix Released Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: New Status in systemd source package in Kinetic: Triaged Bug description: [impact] manual disabling of ipv4 DAD (IACD) for static link-local address does not work in jammy [test case] see 'Reproducer' in original description below [regression potential] failure to disable DAD, or incorrect disabling of DAD, or networkd issues around parsing of DAD config parsing [scope] this is needed for j and k introduced upstream by commit 1cf4ed142d6c1e2b9dc6a0bc74b6a83ae30b0f8e, first included in v249, so this bug does not affect impish or earlier fixed upstream by commit 2859932bd64d61a89f85fa027762bc16961fcf53 [original description] A customer reported network disconnections on their storage servers when running 'netplan apply'. The culprit was that they have link-local addresses configured and the Duplicate Address Detection (DAD) mechanism was delaying the interfaces from coming back up. As a workaround we tried to disable DAD for the interfaces but that's not working in Ubuntu 22.04: I've noticed that setting DuplicateAddressDetection=none for an interface with a link-local address (e.g., 169.254.*) via a .network file added to /etc/systemd/network/ doesn't really disable Duplicate Address Detection. OS and package versions: - Description: Ubuntu Jammy Jellyfish (development branch). Release: 22.04 - systemd 249.5-2ubuntu4 Reproducer: --- 1- Set up Ubuntu 22.04 VM 2- Increase systemlog level: mkdir -p /etc/systemd/system/systemd-networkd.service.d/ cat > /etc/systemd/system/systemd-networkd.service.d/10-debug.conf
[Touch-packages] [Bug 1969375] Re: systemd-cryptenroll does not support TPM2 devices
We're combining this SRU with LP: #1964494 (and other autopkgtest related changes) so I'm removing the block-proposed-jammy tag. ** Tags removed: block-proposed-jammy -- 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/1969375 Title: systemd-cryptenroll does not support TPM2 devices Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Kinetic: Triaged Bug description: [Impact] * TPM2/FIDO cannot be used to unlock luks encrpyted block devices * due to missing build-time support in systemd * Error message: "TPM2 not supported on this build." [Test Plan] # prepare test $ sudo apt install libtss2-rc0 # runtime dependency for TPM usage $ dd if=/dev/zero of=encrypted.img bs=1 count=0 seek=100M $ echo -n "s0s3cur3" | cryptsetup luksFormat encrypted.img - $ sudo /usr/lib/systemd/systemd-cryptsetup attach volume encrypted.img Please enter passphrase for disk volume: s0s3cure Set cipher aes, mode xts-plain64, key size 512 bits for device encrypted.img. $ sudo mkfs.ext4 /dev/mapper/volume $ sudo mount /dev/mapper/volume /mnt $ sudo touch /mnt/TPM_TEST $ ls -la /mnt drwxr-xr-x 3 root root 4096 Jun 7 15:06 . drwxr-xr-x 20 root root 4096 Apr 20 11:45 .. drwx-- 2 root root 16384 Jun 7 15:06 lost+found -rw-r--r-- 1 root root 0 Jun 7 15:06 TPM_TEST $ sudo umount /dev/mapper/volume $ sudo cryptsetup luksClose volume $ ls -la /mnt # empty # use TPM $ systemd-cryptenroll --tpm2-device=list PATHDEVICE DRIVER /dev/tpmrm0 MSFT0101:00 tpm_tis $ sudo systemd-cryptenroll --tpm2-device=auto --tpm2-pcrs=7 encrypted.img Please enter current passphrase for disk /home/lukas/canonical/systemd-dbg/encrypted.img: s0s3cur3 New TPM2 token enrolled as key slot 1. $ sudo /usr/lib/systemd/systemd-cryptsetup attach volume encrypted.img - tpm2-device=auto Set cipher aes, mode xts-plain64, key size 512 bits for device encrypted.img. Automatically discovered security TPM2 token unlocks volume. # no password needed above! $ sudo mount /dev/mapper/volume /mnt $ ls -la /mnt drwxr-xr-x 3 root root 4096 Jun 7 15:06 . drwxr-xr-x 20 root root 4096 Apr 20 11:45 .. drwx-- 2 root root 16384 Jun 7 15:06 lost+found -rw-r--r-- 1 root root 0 Jun 7 15:06 TPM_TEST #cleanup $ sudo umount /dev/mapper/volume $ sudo cryptsetup luksClose volume $ ls -la /mnt # empty $ sudo rm encrypted.img [Where problems could occur] * we're enabling a build-flag to allow usage of TPM/FIDO hardware * running new code paths in systemd due to enablement of a new feature, could trigger hidden bugs in systemd-cryptsetup, e.g. (un-)locking for encrypted devices * new functionality is only active/used if enabled explicitly and suggested runtime dependencies are manually installed [Other Info] * This is not necessarily fall under the HWE SRU policy, as the TPM is already there, but just can't be used via systemd-cryptencroll * In a discussion with the SRU team (@vorlon) we agreed that this should be an exception to the rule, due to low regression risk. As long as it would not pull in extra dependencies into the default installation, which it doesn't (new dependencies are only "Suggests:") * This will be enabled in Kinetic+ as soon as we merge systemd v251 from Debian: https://salsa.debian.org/systemd-team/systemd/-/commit/6b5e99f1d7f63c0c83007de9f98f7745f4a564f8 === original description === systemd-cryptenroll can make use of tpm2 modules to bind against secure boot pcrs and enable auto unlocking of luks devices. Following the instructions here: https://wiki.archlinux.org/title/Trusted_Platform_Module#systemd-cryptenroll the following commands fail on ubuntu jammy (5.15.0-25-generic) root@testbox:~# systemd-cryptenroll --tpm2-device=list TPM2 not supported on this build. root@testbox:~# systemd-cryptenroll --tpm2-device=auto --tpm2-pcrs=7 /dev/sda3 Please enter current passphrase for disk /dev/sda3: *** root@testbox:~# echo $? 1 It appears that this issue has been resolved in the debian build for systemd here: https://salsa.debian.org/systemd- team/systemd/-/commit/6b5e99f1d7f63c0c83007de9f98f7745f4a564f8 Can we get the same modifications to the Jammy systemd build? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969375/+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 1849972] Re: apt list --upgradable shows no additional updates
This no longer affects the latest version of ubuntu-advantage-tools so I'm marking Invalid. Please re-open if you think this still applies. ** Changed in: ubuntu-advantage-tools (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1849972 Title: apt list --upgradable shows no additional updates Status in apt package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: Invalid Bug description: Running `apt list --upgradable` does not show any additional packages to install. Should it? root@humble-mynah:/etc/apt/sources.list.d# apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 60 additional updates are available with UA Infrastructure ESM. To see these additional updates run: apt list --upgradable See https://ubuntu.com/advantage or run: sudo ua status root@humble-mynah:/etc/apt/sources.list.d# apt list --upgradable Listing... Done root@humble-mynah:/etc/apt/sources.list.d# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1849972/+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 1969375] Re: systemd-cryptenroll does not support TPM2 devices
** Description changed: + [Impact] + + * TPM2/FIDO cannot be used to unlock luks encrpyted block devices + * due to missing build-time support in systemd + * Error message: "TPM2 not supported on this build." + + [Test Plan] + + # prepare test + $ sudo apt install libtss2-rc0 # runtime dependency for TPM usage + $ dd if=/dev/zero of=encrypted.img bs=1 count=0 seek=100M + $ echo -n "s0s3cur3" | cryptsetup luksFormat encrypted.img - + $ sudo /usr/lib/systemd/systemd-cryptsetup attach volume encrypted.img + Please enter passphrase for disk volume: s0s3cure + Set cipher aes, mode xts-plain64, key size 512 bits for device encrypted.img. + $ sudo mkfs.ext4 /dev/mapper/volume + $ sudo mount /dev/mapper/volume /mnt + $ sudo touch /mnt/TPM_TEST + $ ls -la /mnt + drwxr-xr-x 3 root root 4096 Jun 7 15:06 . + drwxr-xr-x 20 root root 4096 Apr 20 11:45 .. + drwx-- 2 root root 16384 Jun 7 15:06 lost+found + -rw-r--r-- 1 root root 0 Jun 7 15:06 TPM_TEST + $ sudo umount /dev/mapper/volume + $ sudo cryptsetup luksClose volume + $ ls -la /mnt # empty + + # use TPM + $ systemd-cryptenroll --tpm2-device=list + PATHDEVICE DRIVER + /dev/tpmrm0 MSFT0101:00 tpm_tis + $ sudo systemd-cryptenroll --tpm2-device=auto --tpm2-pcrs=7 encrypted.img + Please enter current passphrase for disk /home/lukas/canonical/systemd-dbg/encrypted.img: s0s3cur3 + New TPM2 token enrolled as key slot 1. + $ sudo /usr/lib/systemd/systemd-cryptsetup attach volume encrypted.img - tpm2-device=auto + Set cipher aes, mode xts-plain64, key size 512 bits for device encrypted.img. + Automatically discovered security TPM2 token unlocks volume. + # no password needed above! + $ sudo mount /dev/mapper/volume /mnt + $ ls -la /mnt + drwxr-xr-x 3 root root 4096 Jun 7 15:06 . + drwxr-xr-x 20 root root 4096 Apr 20 11:45 .. + drwx-- 2 root root 16384 Jun 7 15:06 lost+found + -rw-r--r-- 1 root root 0 Jun 7 15:06 TPM_TEST + + #cleanup + $ sudo umount /dev/mapper/volume + $ sudo cryptsetup luksClose volume + $ ls -la /mnt # empty + + [Where problems could occur] + + * we're enabling a build-flag to allow usage of TPM/FIDO hardware + * running new code paths in systemd due to enablement of a new feature, could trigger hidden bugs in systemd-cryptsetup, e.g. (un-)locking for encrypted devices + * new functionality is only active/used if enabled explicitly and suggested runtime dependencies are manually installed + + [Other Info] + + * This is not necessarily fall under the HWE SRU policy, as the TPM is already there, but just can't be used via systemd-cryptencroll + * In a discussion with the SRU team (@vorlon) we agreed that this should be an exception to the rule, due to low very regression risk. As long as it would not pull in extra dependencies into the default installation, which it doesn't (new dependencies are only "Suggests:") + + === original description === + systemd-cryptenroll can make use of tpm2 modules to bind against secure boot pcrs and enable auto unlocking of luks devices. Following the instructions here: https://wiki.archlinux.org/title/Trusted_Platform_Module#systemd-cryptenroll the following commands fail on ubuntu jammy (5.15.0-25-generic) root@testbox:~# systemd-cryptenroll --tpm2-device=list TPM2 not supported on this build. root@testbox:~# systemd-cryptenroll --tpm2-device=auto --tpm2-pcrs=7 /dev/sda3 Please enter current passphrase for disk /dev/sda3: *** root@testbox:~# echo $? 1 It appears that this issue has been resolved in the debian build for systemd here: https://salsa.debian.org/systemd- team/systemd/-/commit/6b5e99f1d7f63c0c83007de9f98f7745f4a564f8 Can we get the same modifications to the Jammy systemd build? ** Description changed: [Impact] - * TPM2/FIDO cannot be used to unlock luks encrpyted block devices - * due to missing build-time support in systemd - * Error message: "TPM2 not supported on this build." + * TPM2/FIDO cannot be used to unlock luks encrpyted block devices + * due to missing build-time support in systemd + * Error message: "TPM2 not supported on this build." [Test Plan] # prepare test $ sudo apt install libtss2-rc0 # runtime dependency for TPM usage $ dd if=/dev/zero of=encrypted.img bs=1 count=0 seek=100M $ echo -n "s0s3cur3" | cryptsetup luksFormat encrypted.img - - $ sudo /usr/lib/systemd/systemd-cryptsetup attach volume encrypted.img + $ sudo /usr/lib/systemd/systemd-cryptsetup attach volume encrypted.img Please enter passphrase for disk volume: s0s3cure Set cipher aes, mode xts-plain64, key size 512 bits for device encrypted.img. $ sudo mkfs.ext4 /dev/mapper/volume $ sudo mount /dev/mapper/volume /mnt $ sudo touch /mnt/TPM_TEST $ ls -la /mnt drwxr-xr-x 3 root root 4096 Jun 7 15:06 . drwxr-xr-x 20 root root 4096 Apr 20 11:45 .. drwx-- 2 root root 16384 Jun 7 15:06 lost+found -rw-r--r-- 1 root root 0
[Touch-packages] [Bug 1958019]
Quick update: it works! sort of... I applied the first fixup (LEGION_15IMHG05), but it didn't work, and the second (YOGA7_14ITL) didn't either. But while booted from the kernel with the 2nd fixup, I decided to give it a quick suspend/wakeup cycle. After the wakeup, there is sound! But only from the left speaker. The sound is coming only from the left channel. I will report back after retrying the 1st fixup, this time with a suspend/wakeup cycle. (In reply to Cameron Berkenpas from comment #602) > Created attachment 300990 [details] > attachment-14829-0.html > > From your alsa-info (thanks!), I see that your subsystem id is 0x3822 > compared to the 0x1813 of the 15IMHG05. > > In the root of the linux source folder/directory, open the file: > sound/pci/hda/patch_realtek.c > > Find this line: > SND_PCI_QUIRK(0x17aa, 0x3813, "Legion 7i 15IMHG05", > ALC287_FIXUP_LEGION_15IMHG05_SPEAKERS), > > Next to that line (before or after doesn't matter), add your own line: > SND_PCI_QUIRK(0x17aa, 0x3822, "Legion 7i 15IMH5", > ALC287_FIXUP_LEGION_15IMHG05_SPEAKERS), > > If the ALC287_FIXUP_LEGION_15IMHG05_SPEAKERS fix doesn't work for your > laptop, try theALC287_FIXUP_YOGA7_14ITL_SPEAKERS fix as well. Ie, > SND_PCI_QUIRK(0x17aa, 0x3822, "Legion 7i 15IMH5", > ALC287_FIXUP_YOGA7_14ITL_SPEAKERS), > > But given the similarities between our laptop models, I strongly suspect > the 15IMHG05 fix will work for your laptop as well. > > Looks like you're running linux Mint, which, IIRC, is based on Debian or > Ubuntu. For deb based distributions, you can build packages for your > kernel like this: > make bindeb-pkg > > You only really need the linux-image and linux-headers (for Nvidia) > packages. To speed up the compile, you can pass in the -j option to > parallelize the build: > make -j$(nproc) bindeb-pkg > > > On 5/17/22 14:32, bugzilla-dae...@kernel.org wrote: > > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > > > --- Comment #601 from Andrei Miculita (andreimiculita+k...@gmail.com) --- > > (In reply to Cameron Berkenpas from comment #600) > >> Looking at the model number, there's a chance it's compatible with the > >> verbs of the 15IMHG05, or another model from around that time. > >> > >> Do you know how to build and run your own kernel? > >> > >> Also, please provide a URL to your alsa-info. > >> > >> On 5/15/2022 12:12 PM,bugzilla-dae...@kernel.org wrote: > >>> https://bugzilla.kernel.org/show_bug.cgi?id=208555 > >>> > >>> --- Comment #599 from Andrei Miculita (andreimiculita+k...@gmail.com) --- > >>> Lenovo Legion S7 15IMH5 > >>> > >>> Has anyone managed to get their sound working on it? Would appreciate a > >>> tutorial or some tips (the more specific, the better, as this thread is > >> full > >>> of > >>> other devices as well and it'd take a long time to try everything) > >>> > > > > I do, it might take me a while to get it done if I start now, but I've done > > it > > before for fun. > > > > > > My alsa-info: > > http://alsa-project.org/db/?f=c1ba1098da13b2d7d6793fbce823e4feed2ac4ee > > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack:
[Touch-packages] [Bug 1965439] Re: applications can no longer launch when called by kdesu
-MOREOVER- This bug is being worked on by volunteers. It will be fixed when it's fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: applications can no longer launch when called by kdesu Status in kdesu package in Ubuntu: Fix Released Status in kubuntu-settings package in Ubuntu: Fix Released Status in sudo package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: Fix Released Status in kdesu source package in Jammy: In Progress Status in kubuntu-settings source package in Jammy: In Progress Status in sudo source package in Jammy: Confirmed Status in ubuntustudio-default-settings source package in Jammy: In Progress Status in kdesu source package in Kinetic: Fix Released Status in kubuntu-settings source package in Kinetic: Fix Released Status in sudo source package in Kinetic: Confirmed Status in ubuntustudio-default-settings source package in Kinetic: Fix Released Status in kdesu package in Debian: Fix Released Bug description: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma- discover's "Software Sources" link. Steps to recrate: 1) Open Plasma-discover 2) Go to Settings 3) Under click on "Software Sources" 4) Attempt to enter password Expected: Software properties opens Actual: Pkexec keeps asking for password. -- Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver- manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-default-settings UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+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 1970190] Re: [Feature]Wrong default value for Brazil Keyboard layout on ThinkPad
I checked the source code, it should be from console-setup which is installed by ubiquity, it will load the Keyboard/ckb/rules/base.xml, currently it will select the first one after choosing country or timezone. Maybe we could set 'thinkpad' if we could detect the type of laptop. thinkpad Portuguese (Brazil, IBM/Lenovo ThinkPad) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1970190 Title: [Feature]Wrong default value for Brazil Keyboard layout on ThinkPad Status in OEM Priority Project: New Status in console-setup package in Ubuntu: New Bug description: On ThinkPad, when I select 'Portuguese(Brazil)', it will use 'Portuguese(Brazil)' on second column, but the default value should be 'Portuguese(Brazil)-Portuguese(Brazil, IBM/Lenovo ThinkPad)'. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1970190/+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 1965439] Re: applications can no longer launch when called by kdesu
@Blackmage If you need to use "Software Sources", there is a workaround that works for now. 1) Open a terminal and run xterm 2) in xterm run sudo software-properties-qt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: applications can no longer launch when called by kdesu Status in kdesu package in Ubuntu: Fix Released Status in kubuntu-settings package in Ubuntu: Fix Released Status in sudo package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: Fix Released Status in kdesu source package in Jammy: In Progress Status in kubuntu-settings source package in Jammy: In Progress Status in sudo source package in Jammy: Confirmed Status in ubuntustudio-default-settings source package in Jammy: In Progress Status in kdesu source package in Kinetic: Fix Released Status in kubuntu-settings source package in Kinetic: Fix Released Status in sudo source package in Kinetic: Confirmed Status in ubuntustudio-default-settings source package in Kinetic: Fix Released Status in kdesu package in Debian: Fix Released Bug description: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma- discover's "Software Sources" link. Steps to recrate: 1) Open Plasma-discover 2) Go to Settings 3) Under click on "Software Sources" 4) Attempt to enter password Expected: Software properties opens Actual: Pkexec keeps asking for password. -- Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver- manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-default-settings UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+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 1977652] Re: systemd loops trying to start systemd-ask-password-plymouth
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1977652 Title: systemd loops trying to start systemd-ask-password-plymouth Status in systemd package in Ubuntu: Confirmed Bug description: Short story: - after boot - when a systemd service wants a password - systemd-ask-password is invoked - systemd-ask-password-plymouth.path is reached - systemd-ask-password-plymouth.service is started Except: - the conditions for the latter are (apparently) not met End result: - 40.000x "Condition check resulted in Forward Password Requests to Plymouth being skipped." - 1.5 minutes of 100% cpu usage AFFECTED VERSION systemd 249.11-0ubuntu3.1 on Ubuntu/Jammy 22.04 HOW TO REPRODUCE If I leave the `systemd-ask-password-plymouth.path` unmasked/enabled and reboot. OpenVPN (calling systemd-ask-password) will trigger the condition. This causes high CPU usage for 1.5 minutes. It looks like /run/plymouth/pid exists (for the .path file) at first, when that is invoked, but then the resultant target (the .service file) checks again, and finds that it is gone. Manually reproducing: # ls /run/systemd/ask-password ask.5hW6rb sck.79cfe1203518610 # mkdir /run/plymouth/pid # systemctl start systemd-ask-password-plymouth.service systemd-ask-password-plymouth.path # systemctl show --value --property=MainPID systemd-ask-password-plymouth.service 24777 # rmdir /run/plymouth/pid ; kill 24777 Result: systemd going into a loop. Stop the loop with: # systemctl stop systemd-ask-password-plymouth.path ANALYSIS It looks like this: https://github.com/systemd/systemd/issues/21025 which is fixed by: https://github.com/systemd/systemd/pull/21030 Alternative bug reports: https://bugzilla.redhat.com/show_bug.cgi?id=1919538 Systemd's own analysis of the situation: # systemd-analyze critical-chain systemd-ask-password-plymouth.service ... systemd-ask-password-plymouth.service @1min 35.823s └─systemd-ask-password-plymouth.path @593ms └─plymouth-start.service @571ms +21ms └─systemd-udevd.service @450ms +119ms └─systemd-tmpfiles-setup-dev.service @429ms +18ms └─systemd-sysusers.service @382ms +46ms └─systemd-remount-fs.service @353ms +22ms └─systemd-journald.socket @318ms └─system.slice @264ms └─-.slice @264ms --- WORKAROUNDS --- This works as long as you don't need the plymouth-ask-password: # systemctl disable systemd-ask-password-plymouth.path # systemctl mask systemd-ask-password-plymouth.path Could you get the relevant patches from upstream sorted in Jammy? Thanks! Walter Doekes OSSO B.V. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1977652/+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 1969375] Re: systemd-cryptenroll does not support TPM2 devices
** Tags added: block-proposed-jammy -- 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/1969375 Title: systemd-cryptenroll does not support TPM2 devices Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Kinetic: Triaged Bug description: systemd-cryptenroll can make use of tpm2 modules to bind against secure boot pcrs and enable auto unlocking of luks devices. Following the instructions here: https://wiki.archlinux.org/title/Trusted_Platform_Module#systemd-cryptenroll the following commands fail on ubuntu jammy (5.15.0-25-generic) root@testbox:~# systemd-cryptenroll --tpm2-device=list TPM2 not supported on this build. root@testbox:~# systemd-cryptenroll --tpm2-device=auto --tpm2-pcrs=7 /dev/sda3 Please enter current passphrase for disk /dev/sda3: *** root@testbox:~# echo $? 1 It appears that this issue has been resolved in the debian build for systemd here: https://salsa.debian.org/systemd- team/systemd/-/commit/6b5e99f1d7f63c0c83007de9f98f7745f4a564f8 Can we get the same modifications to the Jammy systemd build? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969375/+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 1967576] Re: systemd: autopkgtest: tests-in-lxd fails because of remaining snap .mount units
** Description changed: - This build log provides an example of the problem: - https://autopkgtest.ubuntu.com/results/autopkgtest- - impish/impish/ppc64el/s/systemd/20220331_190433_fdbbe@/log.gz. + [Impact] + + * The "tests-in-lxd/boot-and-services/test_no_failed" autopkgtest fails + * it did not stand out due to LP: #1976607 + * we want to have proper autopkgtest coverage for systemd in Jammy LTS + + [Test Plan] + + * check autopkgtest logs on autopkgtest.ubuntu.com and make sure all + instances of "boot-and-services" PASS (especially the "test_no_failed" + test case. This includes running the test natively in autopkgtest and + inside the "tests-in-lxd" container. + + [Where problems could occur] + + * other/new snapd-*.mount regressions could be hidden. + * but snapd is being removed during systemd's tests anyway (introducing this failure) + + [Other Info] + + * The issue was not visible up to now, as the whole tests-in-lxd autopkgtests has been skipped: LP: #1976607 + + + === original description === + This build log provides an example of the problem: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220331_190433_fdbbe@/log.gz. During setup for tests-in-lxd, an attempt is made to purge snapd, but this fails: [ ... ] Purging configuration files for snapd (2.54.3+21.10.1ubuntu0.2) ... Stopping snap.lxd.activate.service Stopping unit snap.lxd.activate.service Waiting until unit snap.lxd.activate.service is stopped [attempt 1] snap.lxd.activate.service is stopped. Removing snap.lxd.activate.service Stopping snap.lxd.daemon.service Stopping unit snap.lxd.daemon.service Waiting until unit snap.lxd.daemon.service is stopped [attempt 1] snap.lxd.daemon.service is stopped. Removing snap.lxd.daemon.service Stopping snap.lxd.user-daemon.service Stopping unit snap.lxd.user-daemon.service Waiting until unit snap.lxd.user-daemon.service is stopped [attempt 1] snap.lxd.user-daemon.service is stopped. Removing snap.lxd.user-daemon.service Stopping snap-core20-1378.mount Stopping unit snap-core20-1378.mount Waiting until unit snap-core20-1378.mount is stopped [attempt 1] snap-core20-1378.mount is stopped. Removing snap core20 and revision 1378 Removing snap-core20-1378.mount Stopping snap-lxd-22672.mount Stopping unit snap-lxd-22672.mount Waiting until unit snap-lxd-22672.mount is stopped [attempt 1] snap-lxd-22672.mount is stopped. Removing snap lxd and revision 22672 rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/cpuinfo': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/meminfo': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/stat': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/uptime': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/diskstats': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/swaps': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/loadavg': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/slabinfo': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/cpu0': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/cpuidle': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/uevent': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/svm': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/hotplug': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/offline': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/present': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/power': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/dscr_default': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/probe': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/smt': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/vulnerabilities': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/cpufreq': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/isolated': Function not implemented rm: cannot remove
[Touch-packages] [Bug 1970190] Re: [Feature]Wrong default value for Brazil Keyboard layout on ThinkPad
@Peter: could you please provide more information? This feature request isn't trivial to implement; for instance, a user could use a Thinkpad but have an external keyboard plugged in. We need more information in order for us to design a solution. ** Changed in: oem-priority Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1970190 Title: [Feature]Wrong default value for Brazil Keyboard layout on ThinkPad Status in OEM Priority Project: New Status in console-setup package in Ubuntu: New Bug description: On ThinkPad, when I select 'Portuguese(Brazil)', it will use 'Portuguese(Brazil)' on second column, but the default value should be 'Portuguese(Brazil)-Portuguese(Brazil, IBM/Lenovo ThinkPad)'. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1970190/+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 1977764] Re: kernel modules "zstd" and "z3fold" missing.
Doh -- that one's my fault; included it in the kernel command line and completely forgot to include a patch in ubuntu-raspi-settings to add it to the set of modules for initramfs-tools to include in the initrd. The workaround for now: $ sudo -i # echo zstd >> /etc/initramfs-tools/modules # echo z3fold >> /etc/initramfs-tools/modules # update-initramfs -u I'll try and get this added to ubuntu-raspi-settings shortly. ** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu Kinetic) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: initramfs-tools (Ubuntu Jammy) Assignee: (unassigned) => Dave Jones (waveform) ** Also affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** No longer affects: initramfs-tools (Ubuntu) ** No longer affects: initramfs-tools (Ubuntu Kinetic) ** No longer affects: initramfs-tools (Ubuntu Jammy) ** Changed in: ubuntu-settings (Ubuntu Jammy) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: ubuntu-settings (Ubuntu Kinetic) Assignee: (unassigned) => Dave Jones (waveform) -- 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/1977764 Title: kernel modules "zstd" and "z3fold" missing. Status in linux-raspi package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: New Status in linux-raspi source package in Jammy: New Status in ubuntu-settings source package in Jammy: New Status in linux-raspi source package in Kinetic: New Status in ubuntu-settings source package in Kinetic: New Bug description: The modules "zstd" and "z3fold" are missing despite being configured for zswap in "/boot/firmware/cmdline.txt." Messages appear on boot display that state they do not exist and so instead use compressor "lzo" and pool "zbud". Ubuntu version is 22.04 LTS flashed from the official image. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8 ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30 Uname: Linux 5.15.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 6 17:29:00 2022 ImageMediaBuild: 20220419 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1977764/+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 1895762] Re: PH-B-500 Headphone makes bluetooth loop
Thanks for the bug report. Please let us know if you are still experiencing this bug, and if so then what version of Ubuntu? ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/1895762 Title: PH-B-500 Headphone makes bluetooth loop Status in bluez package in Ubuntu: Incomplete Bug description: Hi there, I am using Ubuntu 18.04.4 LTS(Brazilian Portuguese, so, sorry if I translated wrong some label) in a Dell Inspiron 15 series 3000 and I am having some Bluetooth problems. I always suffer to synchronize my Cadenza PH-B Bluetooth Headphone. It Shows as PH-B-500 at the bluetooth devices list What happens is: 1. I turn on the headphone 2. I go to Settings → Bluetooth 3. The Notebook entire bluetooth enters a shutdown reinitialize loop 4. It only stops when I turn off the headphone But if I: 1. Keep the headphone off 2. go to Settings → Bluetooth 3. Click on the PH-B-500 on the list 4. Turn the headphone on and at the same time click on Conection at the PH-B-500 Bluetooth window it usually starts working fine. The headphone works perfectly on my Android cell phone so I don’t believe it is broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1895762/+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 1870829] Re: AptX and AptX HD unavailable as Bluetooth audio quality options
The bug was reopened above because it was my understanding the feature never landed. It was stuck in upstream disputes: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/227 But it sounds like someone else took over and landed it: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/440 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1870829 Title: AptX and AptX HD unavailable as Bluetooth audio quality options Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio package in Debian: Fix Released Bug description: Current situation: When one connects a Bluetooth audio device, at best one can choose between "Headset Head Unit (HSP/HFP)" and "High Fidelity Playback (A2DP Sink)". That is sad when the audio device supports AptX or AptX HD. Expected situation: One can select AptX or AptX HD as the Bluetooth audio output profile. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870829/+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 1877194] Re: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot
switch-on-connect is a feature of PulseAudio only so we should probably say "Won't Fix" in kinetic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1877194 Title: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: New Status in pulseaudio source package in Kinetic: Triaged Status in ubuntu-settings source package in Kinetic: New Bug description: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. In short: 1. Boot system 2. "Analogue Output - RODE NT-USB" is selected by default. I want to use "Line Out - Built-in Audio", which I choose. 3. Reboot. 4 Output device is now back to "Analogue Output - RODE NT-USB". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marcus 1604 F pulseaudio /dev/snd/controlC0: marcus 1604 F pulseaudio /dev/snd/controlC1: marcus 1604 F pulseaudio /dev/snd/pcmC1D0c: marcus 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1877194/+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 1974428] Re: Update to the current 1.36 stable version
Thanks, the new ticket is bug #1977619 and is being discussed upstream now -- 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/1974428 Title: Update to the current 1.36 stable version Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Jammy: Fix Released Bug description: * Impact It's a stable update from upstream, the changes are listed in the NEWS https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS * Test Case Since it's an update with several fixes the testing should focus on a specific point but rather by validating that the testplan is green, https://wiki.ubuntu.com/NetworkManager/DistroTesting * Regression potential There are fixes around IPv6 handling, VPN connections and the hotspot feature, verify that those configurations are still working as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1974428/+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 1973835] Re: Ubuntu 22.04, Bluetooth issues
Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We understand the difficulties you are facing, but it is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs. ** Changed in: bluez (Ubuntu) Importance: Undecided => Low ** Changed in: bluez (Ubuntu) Status: New => Invalid -- 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/1973835 Title: Ubuntu 22.04, Bluetooth issues Status in bluez package in Ubuntu: Invalid Bug description: 0 I installed Ubuntu 22.04 and the Bluetooth was working fine. I turned off the bluetooth and could not turn it back on. I did some research and found some calls to turn it back on: sudo rfkill unblock all sudo hciconfig hci0 down sudo rmmod btusb sudo modprobe btusb sudo hciconfig hci0 up Now, I can turn it on and off as I please but It is now not connecting to any device. It would connect for a brief second and then disconnect. Can't find anything from research. Anyone can help with this ? Also, Whenever I boot up windows, the bluetooth works perfectly fine on windows. So it's not an hardware issue. I ran the command: bluetoothctl and the bluetooth is cycling through connecting to the device and disconnecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1973835/+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 1977561] Re: Sync gettext 0.21-6 from Debian Unstable
Thanks Nathan! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1977561 Title: Sync gettext 0.21-6 from Debian Unstable Status in gettext package in Ubuntu: Fix Released Bug description: This is a sync request for gettext 0.21-6. These were the latest Ubuntu changes: ==> debian/changelog <== gettext (0.21-4ubuntu4) jammy; urgency=medium * debian/patches/git-new-libunistring.patch: - cherry pick ah upstream change to fix the build with the new libunistring -- Sebastien Bacher Fri, 25 Mar 2022 11:31:07 +0100 gettext (0.21-4ubuntu3) impish; urgency=medium * Really fix the merge now -- Sebastien Bacher Fri, 18 Jun 2021 16:29:32 +0200 gettext (0.21-4ubuntu2) impish; urgency=medium * Restore part of the delta dropped by error move dh-elpa to Build-Depends-Indep (and change it to dh-sequence-elpa, thus allowing the removal of explicit "--with elpa" options in debian/rules) to fix FTBFS on i386 -- Sebastien Bacher Fri, 18 Jun 2021 16:23:57 +0200 gettext (0.21-4ubuntu1) impish; urgency=medium * Resynchronize on Debian, remaining change * Cherry-pick an upstream commit to fix a FTBFS on armhf (LP: #1910792) - debian/patches/05-fix-armhf-ftbfs.patch -- Sebastien Bacher Fri, 18 Jun 2021 16:02:07 +0200 ==> End <== The patches for those changes have been incorporated into the new version but under different names, although they are equivalent. The map is 0.21-4ubuntu ---> 0.21.6 git-new-libunistring.patch -> 05-update-after-gnulib-changed.patch 05-fix-armhf-ftbfs.patch ---> 06-remove-unportable-tests.patch So Ubuntu changes can be safely overwritten. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/1977561/+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 1977507] Re: Cupsd crashes every other job.
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: cups (Ubuntu) Importance: Undecided => High ** Changed in: cups (Ubuntu) Status: New => Incomplete ** Summary changed: - Cupsd crashes every other job. + Cupsd crashes every other job since 2.3.1-9ubuntu1.2 security update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1977507 Title: Cupsd crashes every other job since 2.3.1-9ubuntu1.2 security update Status in cups package in Ubuntu: Incomplete Bug description: After yesterdays upgrade (apt log attached) cupsd has stared to crash again every other job. It is then restarted and the next job prints fine. This situation I recognize from the past. It's been like this for a while in the past. Back then I didn't know the upgrade that caused it as half the time it would print just fine. I tried filing a bug with "ubuntu-bug" on the fileserver, but the firefox that was started to let me file the bug wasn't able to get me logged into launchpad. (Works like a charm on my desktop google- chrome). These packages were upgraded yesterday: Start-Date: 2022-06-01 17:55:34 Commandline: apt-get dist-upgrade Requested-By: wolff (1000) Upgrade: libcups2:amd64 (2.3.1-9ubuntu1.1, 2.3.1-9ubuntu1.2), libkmod2:amd64 (27-1ubuntu2, 27-1ubuntu2.1), libcups2-dev:amd64 (2.3.1-9ubuntu1.1, 2.3.1-9ubuntu1.2), libcupsimage2-dev:amd64 (2.3.1-9ubuntu1.1, 2.3.1-9ubuntu1.2), cups-server-common:amd64 (2.3.1-9ubuntu1.1, 2.3.1-9ubuntu1.2), cups-common:amd64 (2.3.1-9ubuntu1.1, 2.3.1-9ubuntu1.2), apache2-data:amd64 (2.4.41-4ubuntu3.10, 2.4.41-4ubuntu3.11), kmod:amd64 (27-1ubuntu2, 27-1ubuntu2.1), cups-ppdc:amd64 (2.3.1-9ubuntu1.1, 2.3.1-9ubuntu1.2), apache2-bin:amd64 (2.4.41-4ubuntu3.10, 2.4.41-4ubuntu3, 2.3.1-9ubuntu1.2), apache2-bin:amd64 (2.4.41-4ubuntu3.10, 2.4.41-4ubuntu3.11), cups-bsd:amd64 (2.3.1-9ubuntu1.1, 2.3.1-9ubuntu1.2), cups-core-drivers:amd64 (2.3.1-9ubuntu1.1, 2.3.1-9ubuntu1.2), cups-daemon:amd64 (2.3.1-9ubuntu1.1, 2.3.1-9ubuntu1.2), libcupsimage2:amd64 (2.3.1-9ubuntu1.1, 2.3.1-9ubuntu1.2), apache2:amd64 (2.4.41-4ubuntu3.10, 2.4.41-4ubuntu3.11), cups:amd64 (2.3.1-9ubuntu1.1, 2.3.1-9ubuntu1.2), apache2-utils:amd64 (2.4.41-4ubuntu3.10, 2.4.41-4ubuntu3.11), cups-client:amd64 (2.3.1-9ubuntu1.1, 2.3.1-9ubuntu1.2), cups-ipp-utils:amd64 (2.3.1-9ubuntu1.1, 2.3.1-9ubuntu1.2) End-Date: 2022-06-01 17:56:15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1977507/+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 1977561] Re: Sync gettext 0.21-6 from Debian Unstable
This bug was fixed in the package gettext - 0.21-6 Sponsored for Nathan Teodosio (nteodosio) --- gettext (0.21-6) unstable; urgency=medium * Remove unportable tests in perror and strerror_r. Should fix FTBFS problem in armel, armhf and mipsel. Patch by Paul Eggert. Reported by Florian Weimer here: https://lists.gnu.org/r/bug-gnulib/2020-08/msg00220.html -- Santiago Vila Sat, 26 Mar 2022 00:30:00 +0100 gettext (0.21-5) unstable; urgency=medium * Move dh-elpa to Build-Depends-Indep and change it to dh-sequence-elpa. Remove explicit "--with elpa" options in debian/rules. Closes: #990039. Thanks to Sebastien Bacher. * Update test for changed libunistring line breaking behaviour. Patch from Bruno Haible. Closes: #1005582. Thanks to Sebastien Bacher. -- Santiago Vila Fri, 25 Mar 2022 18:20:00 +0100 ** Changed in: gettext (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1977561 Title: Sync gettext 0.21-6 from Debian Unstable Status in gettext package in Ubuntu: Fix Released Bug description: This is a sync request for gettext 0.21-6. These were the latest Ubuntu changes: ==> debian/changelog <== gettext (0.21-4ubuntu4) jammy; urgency=medium * debian/patches/git-new-libunistring.patch: - cherry pick ah upstream change to fix the build with the new libunistring -- Sebastien Bacher Fri, 25 Mar 2022 11:31:07 +0100 gettext (0.21-4ubuntu3) impish; urgency=medium * Really fix the merge now -- Sebastien Bacher Fri, 18 Jun 2021 16:29:32 +0200 gettext (0.21-4ubuntu2) impish; urgency=medium * Restore part of the delta dropped by error move dh-elpa to Build-Depends-Indep (and change it to dh-sequence-elpa, thus allowing the removal of explicit "--with elpa" options in debian/rules) to fix FTBFS on i386 -- Sebastien Bacher Fri, 18 Jun 2021 16:23:57 +0200 gettext (0.21-4ubuntu1) impish; urgency=medium * Resynchronize on Debian, remaining change * Cherry-pick an upstream commit to fix a FTBFS on armhf (LP: #1910792) - debian/patches/05-fix-armhf-ftbfs.patch -- Sebastien Bacher Fri, 18 Jun 2021 16:02:07 +0200 ==> End <== The patches for those changes have been incorporated into the new version but under different names, although they are equivalent. The map is 0.21-4ubuntu ---> 0.21.6 git-new-libunistring.patch -> 05-update-after-gnulib-changed.patch 05-fix-armhf-ftbfs.patch ---> 06-remove-unportable-tests.patch So Ubuntu changes can be safely overwritten. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/1977561/+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 1977817] [NEW] Some Function Keys misassigned
Public bug reported: With the update from 1.6-6ubuntu1 to 1.6-6ubuntu1.1, some of the function keys on my device (HP Elite notebook) are misassigned. Specifically, Fn+F3 as well as Fn+F4 now toggle the microphone, while they should reduce/increase screen brightness. That worked well before the update. Fn+F8 also toggles the microphone, which was and is correct. So now I have three function keys doing the same thing, but no function keys for screen brightness. I'm running Linux Mint 20.3 Una 64.bit with MATE 1.26.0. The workaround for desktop use is to add a screen brightness applet to the panel. However, that does not work for console use. ** Affects: keyutils (Ubuntu) Importance: Undecided Status: New ** Tags: brightness function key ** Description changed: With the update from 1.6-6ubuntu1 to 1.6-6ubuntu1.1, some of the function keys on my device (HP Elite notebook) are misassigned. Specifically, Fn+F3 as well as Fn+F4 now toggle the microphone, while they should reduce/increase screen brightness. That worked well before the update. - Fnb+F8 also toggles the microphone, which was and is correct. So now I + Fn+F8 also toggles the microphone, which was and is correct. So now I have three function keys doing the same thing, but no function keys for screen brightness. I'm running Linux Mint 20.3 Una 64.bit with MATE 1.26.0. The workaround for desktop use is to add a screen brightness applet to the panel. However, that does not work for console use. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to keyutils in Ubuntu. https://bugs.launchpad.net/bugs/1977817 Title: Some Function Keys misassigned Status in keyutils package in Ubuntu: New Bug description: With the update from 1.6-6ubuntu1 to 1.6-6ubuntu1.1, some of the function keys on my device (HP Elite notebook) are misassigned. Specifically, Fn+F3 as well as Fn+F4 now toggle the microphone, while they should reduce/increase screen brightness. That worked well before the update. Fn+F8 also toggles the microphone, which was and is correct. So now I have three function keys doing the same thing, but no function keys for screen brightness. I'm running Linux Mint 20.3 Una 64.bit with MATE 1.26.0. The workaround for desktop use is to add a screen brightness applet to the panel. However, that does not work for console use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1977817/+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 1965439] Re: applications can no longer launch when called by kdesu
affects me too, i am at Ubuntu Jammy 22.04, i use LXQT as desktop and Muon as package manager. when will a fix be released? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: applications can no longer launch when called by kdesu Status in kdesu package in Ubuntu: Fix Released Status in kubuntu-settings package in Ubuntu: Fix Released Status in sudo package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: Fix Released Status in kdesu source package in Jammy: In Progress Status in kubuntu-settings source package in Jammy: In Progress Status in sudo source package in Jammy: Confirmed Status in ubuntustudio-default-settings source package in Jammy: In Progress Status in kdesu source package in Kinetic: Fix Released Status in kubuntu-settings source package in Kinetic: Fix Released Status in sudo source package in Kinetic: Confirmed Status in ubuntustudio-default-settings source package in Kinetic: Fix Released Status in kdesu package in Debian: Fix Released Bug description: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma- discover's "Software Sources" link. Steps to recrate: 1) Open Plasma-discover 2) Go to Settings 3) Under click on "Software Sources" 4) Attempt to enter password Expected: Software properties opens Actual: Pkexec keeps asking for password. -- Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver- manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-default-settings UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+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 938751] Re: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome)
** Changed in: gnome-shell Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/938751 Title: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome) Status in GNOME Shell: New Status in chromium-browser package in Ubuntu: Confirmed Status in colord package in Ubuntu: Confirmed Status in eog package in Ubuntu: Confirmed Status in inkscape package in Ubuntu: Confirmed Bug description: Images are washed out or colors are skewed in some apps, notably Chrome/Chromium and Image Viewer (eog). Workaround: 1. Settings > Colour > turn off the toggle switch for your monitor. 2. Restart any affected apps. Originally reported in https://bugzilla.gnome.org/show_bug.cgi?id=675645 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/938751/+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 1977619] Re: NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC
** Changed in: network-manager Status: Unknown => New -- 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/1977619 Title: NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC Status in NetworkManager: New Status in network-manager package in Ubuntu: Triaged Bug description: Situation: My network has both DHCPv6 and SLAAC (autoconf) for IPv6. From a privacy perspective, for readability reasons and for network management policies, DHCPv6 should *always* be preferred over SLAAC addresses when available. And according to RFC 6724, the smaller /128 scope of the DHCPv6 address should be chosen over the larger /64 scope of the SLAAC address. NetworkManager has always been able to adhere to that by simply setting ip6.privacy=0 for the connection (in nm-connection-editor *not* selecting "Prefer temporary address" for IPv6 privacy extensions). Then it would use the DHCPv6 address as the source for all outgoing traffic. So if you would - for instance - run `curl ifconfig.co`, the DHCPv6 address would be used to connect to the outside world and be echoed back. Regression: Since the update to 1.36.6, this is no longer the case. NetworkManager now routes outgoing traffic through the SLAAC address, even if ip6.privacy=0 is set for the connection. Constantly removing the SLAAC addresses with `ip addr del` or disabling SLAAC RA's on the router are now the only ways to stop NetworkManager from preferring SLAAC over DHCPv6. None of the local options in NetworkManager 1.36.6 are able to restore the previous, desired and correct way of working: the SLAAC address should never be used as the preferred address if a DHCPv6 lease is given. Looking at the changelog of NetworkManager 1.36.6, multiple things regarding IP address order and temporary addresses have been changed in that release, any of them (or a combination) introducing this bug: * Fix a bug in synchronization of IP addresses with kernel that could lead to a wrong address order. * Ignore addresses from DHCPv6 when the Otherconf router advertisement flag is set. * Ensure temporary IPv6 addresses are removed on disconnect and reapply. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS Steps to reproduce: 1. Connect to a network where the router sends "A" and "M" bits in the RA's and has a DHCPv6 server running (e.g. any OpenWrt router). 2. When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6 addresses. With NetworkManager 1.36.4 and earlier, this was not the case. (The Linux kernel uses the address highest in the list as preferred.) 3. When running something like `curl ifconfig.co`, the SLAAC address is being returned, which makes sense as that is now preferred by the kernel. (But it shouldn't be.) Desired behaviour: NetworkManager should always sort DHCPv6 addresses above SLAAC addresses, as is the case for all versions prior to 1.36.6 and also corrected again in 1.38.0. In case static addresses are manually set, those should take first priority, with DHCPv6 second and SLAAC/autoconf last. Implications: This can break many real-life use cases. For instance, my router gives out static leases to my machines. Those addresses are whitelisted in all kinds of firewalls to allow me to access servers for my work. Now that the "wrong" address is being preferred for outgoing traffic (a SLAAC address that I have no influence on and cannot centrally configure), I am being locked out of the servers in question unless I forcefully remove the addresses or disable SLAAC on my router, so my outgoing traffic is being routed through the DHCPv6 address again. Note that "just disabling SLAAC RA's on the router" is not something everybody can do, as it requires root access to the device. Moreover, it would break IPv6 connectivity entirely for devices that don't support DHCPv6 (read: Android). Conclusion: So this update introduces a very breaking change in IPv6 source address selection to an LTS release, while LTS releases should be stable. I should note that the bug is not present in NetworkManager 1.38.0 on Debian sid. That just prefers DHCPv6 addresses when available, like it should. As that version is also used in Ubuntu kinetic, most likely this bug is not present there. Looking at the changelog of 1.38.0: * Fix bug setting priority for IP addresses. * Static IPv6 addresses from "ipv6.addresses" are now preferred over addresses from DHCPv6, which are preferred over addresses from autoconf. This affects IPv6 source address selection, if the rules from RFC 6724, section 5 don't give a exhaustive match. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-38/NEWS It looks like Ubuntu just
[Touch-packages] [Bug 1977619] Re: NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC
Thanks for the detail, you might want consider to report the issue directly upstream next time which is the right place to fix a regression due to a version update,, I've forwarded it now to https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1021 ** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #1021 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1021 ** Changed in: network-manager (Ubuntu) Importance: Undecided => High ** Changed in: network-manager (Ubuntu) Status: Confirmed => Triaged ** Also affects: network-manager via https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1021 Importance: Unknown Status: Unknown -- 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/1977619 Title: NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Triaged Bug description: Situation: My network has both DHCPv6 and SLAAC (autoconf) for IPv6. From a privacy perspective, for readability reasons and for network management policies, DHCPv6 should *always* be preferred over SLAAC addresses when available. And according to RFC 6724, the smaller /128 scope of the DHCPv6 address should be chosen over the larger /64 scope of the SLAAC address. NetworkManager has always been able to adhere to that by simply setting ip6.privacy=0 for the connection (in nm-connection-editor *not* selecting "Prefer temporary address" for IPv6 privacy extensions). Then it would use the DHCPv6 address as the source for all outgoing traffic. So if you would - for instance - run `curl ifconfig.co`, the DHCPv6 address would be used to connect to the outside world and be echoed back. Regression: Since the update to 1.36.6, this is no longer the case. NetworkManager now routes outgoing traffic through the SLAAC address, even if ip6.privacy=0 is set for the connection. Constantly removing the SLAAC addresses with `ip addr del` or disabling SLAAC RA's on the router are now the only ways to stop NetworkManager from preferring SLAAC over DHCPv6. None of the local options in NetworkManager 1.36.6 are able to restore the previous, desired and correct way of working: the SLAAC address should never be used as the preferred address if a DHCPv6 lease is given. Looking at the changelog of NetworkManager 1.36.6, multiple things regarding IP address order and temporary addresses have been changed in that release, any of them (or a combination) introducing this bug: * Fix a bug in synchronization of IP addresses with kernel that could lead to a wrong address order. * Ignore addresses from DHCPv6 when the Otherconf router advertisement flag is set. * Ensure temporary IPv6 addresses are removed on disconnect and reapply. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS Steps to reproduce: 1. Connect to a network where the router sends "A" and "M" bits in the RA's and has a DHCPv6 server running (e.g. any OpenWrt router). 2. When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6 addresses. With NetworkManager 1.36.4 and earlier, this was not the case. (The Linux kernel uses the address highest in the list as preferred.) 3. When running something like `curl ifconfig.co`, the SLAAC address is being returned, which makes sense as that is now preferred by the kernel. (But it shouldn't be.) Desired behaviour: NetworkManager should always sort DHCPv6 addresses above SLAAC addresses, as is the case for all versions prior to 1.36.6 and also corrected again in 1.38.0. In case static addresses are manually set, those should take first priority, with DHCPv6 second and SLAAC/autoconf last. Implications: This can break many real-life use cases. For instance, my router gives out static leases to my machines. Those addresses are whitelisted in all kinds of firewalls to allow me to access servers for my work. Now that the "wrong" address is being preferred for outgoing traffic (a SLAAC address that I have no influence on and cannot centrally configure), I am being locked out of the servers in question unless I forcefully remove the addresses or disable SLAAC on my router, so my outgoing traffic is being routed through the DHCPv6 address again. Note that "just disabling SLAAC RA's on the router" is not something everybody can do, as it requires root access to the device. Moreover, it would break IPv6 connectivity entirely for devices that don't support DHCPv6 (read: Android). Conclusion: So this update introduces a very breaking change in IPv6 source address selection to an LTS release, while LTS releases should be stable. I should note that
[Touch-packages] [Bug 938751] Re: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome)
You don't need to remove a colour profile to fix the problem, just disable it: 1. Settings > Colour > turn off the toggle switch for your monitor. 2. Restart any affected apps. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4492 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4492 ** Changed in: gnome-shell Remote watch: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3033 => gitlab.gnome.org/GNOME/gnome-shell/-/issues #4492 ** Description changed: Images are washed out or colors are skewed in some apps, notably Chrome/Chromium and Image Viewer (eog). Workaround: - Settings > Devices > Colour > + Settings > Colour > and disable or remove your monitor's colour profile Originally reported in https://bugzilla.gnome.org/show_bug.cgi?id=675645 ** Description changed: Images are washed out or colors are skewed in some apps, notably Chrome/Chromium and Image Viewer (eog). Workaround: - Settings > Colour > - and disable or remove your monitor's colour profile + 1. Settings > Colour > turn off the toggle switch for your monitor. + + 2. Restart any affected apps. Originally reported in https://bugzilla.gnome.org/show_bug.cgi?id=675645 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/938751 Title: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome) Status in GNOME Shell: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in colord package in Ubuntu: Confirmed Status in eog package in Ubuntu: Confirmed Status in inkscape package in Ubuntu: Confirmed Bug description: Images are washed out or colors are skewed in some apps, notably Chrome/Chromium and Image Viewer (eog). Workaround: 1. Settings > Colour > turn off the toggle switch for your monitor. 2. Restart any affected apps. Originally reported in https://bugzilla.gnome.org/show_bug.cgi?id=675645 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/938751/+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 1977797] [NEW] CRITICAL rally [-] Unhandled error: KeyError: 'openstack'
Public bug reported: I am using openstack wallaby in tripleo architecture. I googled around and found i can use openstack-rally for testing the openstack deployment and will be able to genrate report also. so i tried installing openstack rally using "yum install openstack-rally", "pip3 install openstack-rally" and finally cloned the git repo and ran "python3 setup.py install" but no matter what i do i am getting the error 'unhandled error : keyerror 'openstack'' (overcloud) [root@hkg2director ~]# rally deployment create --fromenv --name=existing +--++--+--++ | uuid | created_at | name | status | active | +--++--+--++ | 484aae52-a690-4163-828b-16adcaa0d8fb | 2022-06-07T05:48:39.039296 | existing | deploy->finished || +--++--+--++ Using deployment: 484aae52-a690-4163-828b-16adcaa0d8fb (overcloud) [root@hkg2director ~]# rally deployment show 484aae52-a690-4163-828b-16adcaa0d8fb Command failed, please check log for more info 2022-06-07 13:48:58.651 482053 CRITICAL rally [-] Unhandled error: KeyError: 'openstack' 2022-06-07 13:48:58.651 482053 ERROR rally Traceback (most recent call last): 2022-06-07 13:48:58.651 482053 ERROR rally File "/bin/rally", line 10, in 2022-06-07 13:48:58.651 482053 ERROR rally sys.exit(main()) 2022-06-07 13:48:58.651 482053 ERROR rally File "/usr/local/lib/python3.6/site-packages/rally/cli/main.py", line 40, in main 2022-06-07 13:48:58.651 482053 ERROR rally return cliutils.run(sys.argv, categories) 2022-06-07 13:48:58.651 482053 ERROR rally File "/usr/local/lib/python3.6/site-packages/rally/cli/cliutils.py", line 669, in run 2022-06-07 13:48:58.651 482053 ERROR rally ret = fn(*fn_args, **fn_kwargs) 2022-06-07 13:48:58.651 482053 ERROR rally File "/usr/local/lib/python3.6/site-packages/rally/cli/envutils.py", line 142, in inner 2022-06-07 13:48:58.651 482053 ERROR rally return func(*args, **kwargs) 2022-06-07 13:48:58.651 482053 ERROR rally File "/usr/local/lib/python3.6/site-packages/rally/plugins/__init__.py", line 59, in wrapper 2022-06-07 13:48:58.651 482053 ERROR rally return func(*args, **kwargs) 2022-06-07 13:48:58.651 482053 ERROR rally File "/usr/local/lib/python3.6/site-packages/rally/cli/commands/deployment.py", line 205, in show 2022-06-07 13:48:58.651 482053 ERROR rally creds = deployment["credentials"]["openstack"][0] 2022-06-07 13:48:58.651 482053 ERROR rally KeyError: 'openstack' 2022-06-07 13:48:58.651 482053 ERROR rally can someone please help me in fixing this issue or give any suggestion on which tool to use to test the openstack deployment and benchmark. ** Affects: rally Importance: Undecided Status: New ** Tags: openstack-rally openstack-wallaby tripleo ** Package changed: wget (Ubuntu) => rally-openstack (Ubuntu) ** Package changed: rally-openstack (Ubuntu) => rally -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1977797 Title: CRITICAL rally [-] Unhandled error: KeyError: 'openstack' Status in Rally: New Bug description: I am using openstack wallaby in tripleo architecture. I googled around and found i can use openstack-rally for testing the openstack deployment and will be able to genrate report also. so i tried installing openstack rally using "yum install openstack-rally", "pip3 install openstack-rally" and finally cloned the git repo and ran "python3 setup.py install" but no matter what i do i am getting the error 'unhandled error : keyerror 'openstack'' (overcloud) [root@hkg2director ~]# rally deployment create --fromenv --name=existing +--++--+--++ | uuid | created_at | name | status | active | +--++--+--++ | 484aae52-a690-4163-828b-16adcaa0d8fb | 2022-06-07T05:48:39.039296 | existing | deploy->finished || +--++--+--++ Using deployment: 484aae52-a690-4163-828b-16adcaa0d8fb (overcloud) [root@hkg2director ~]# rally deployment show 484aae52-a690-4163-828b-16adcaa0d8fb Command failed, please check log for more info 2022-06-07 13:48:58.651 482053 CRITICAL rally [-] Unhandled error: KeyError: 'openstack' 2022-06-07 13:48:58.651 482053 ERROR rally Traceback (most recent call last): 2022-06-07 13:48:58.651
