[Touch-packages] [Bug 2061708] Re: Yubikey stopped working after noble upgrade
I don't recommend running with pcscd, it's much more stable to run with direct access, but I do not know why it doesn't seem to work for you, it certainly does for me. It failing with pcscd is nice, it not telling us why and how to fix it is bad UX though. ** Changed in: gnupg2 (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/2061708 Title: Yubikey stopped working after noble upgrade Status in Arch Linux on Launchpad: Fix Released Status in gnupg2 package in Ubuntu: Triaged Status in pcsc-lite package in Ubuntu: Invalid Bug description: In Ubuntu 22.04 I used by GPG key stored on a Yubikey smart card, but since upgrading to Noble I get the following trying to access it. $ gpg --card-status gpg: selecting card failed: No such device gpg: OpenPGP card not available: No such device If I run this as root it works: $ sudo gpg --card-status Reader ...: 1050:0407:X:0 Application ID ...: D27600012401000609082616 Application type .: OpenPGP Version ..: 2.1 Manufacturer .: Yubico Serial number : Name of cardholder: [not set] Language prefs ...: [not set] Salutation ...: URL of public key : [not set] Login data ...: [not set] Signature PIN : not forced Key attributes ...: rsa4096 rsa4096 rsa2048 Max. PIN lengths .: 127 127 127 PIN retry counter : 10 0 10 Signature counter : 1172 UIF setting ..: Sign=off Decrypt=off Auth=off Signature key : created : Encryption key: created : Authentication key: [none] General key info..: [none] If I manually run pcscd.service then it stops working both as root and a user. $ sudo pkill -9 scdaemon $ sudo systemctl start pcscd.service $ gpg --card-status gpg: selecting card failed: No such device gpg: OpenPGP card not available: No such device $ sudo gpg --card-status gpg: selecting card failed: No such device gpg: OpenPGP card not available: No such device It might be worth mentioning I'm accessing the machine over SSH, so I also did experiment with a polkit rule like this: polkit.addRule(function(action, subject) { if (action.id == "org.debian.pcsc-lite.access_card" && subject.isInGroup("sudo")) { return polkit.Result.YES; } }); polkit.addRule(function(action, subject) { if (action.id == "org.debian.pcsc-lite.access_pcsc" && subject.isInGroup("sudo")) { return polkit.Result.YES; } }); Added into /etc/polkit-1/rules.d/99-pcscd.rules and then reloading polkit.service in case this was a polkit issue, but this didn't do anything. Versions in noble: pcscd: 2.0.3-1build1 libpcslite1: 2.0.3-1build1 gnupg: 2.4.4-2ubuntu17 scdaemon: 2.4.4-2ubuntu17 To manage notifications about this bug go to: https://bugs.launchpad.net/archlinux-lp/+bug/2061708/+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 2063545] [NEW] package click 0.5.2-2ubuntu4 failed to install/upgrade: new click package pre-removal script subprocess returned error exit status 1
Public bug reported: I was updating to new unity sorry i really dont know i am newbie ProblemType: Package DistroRelease: Ubuntu 24.04 Package: click 0.5.2-2ubuntu4 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 25 21:27:28 2024 ErrorMessage: new click package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2024-02-11 (75 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: click Title: package click 0.5.2-2ubuntu4 failed to install/upgrade: new click package pre-removal script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-04-26 (0 days ago) ** Affects: click (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/2063545 Title: package click 0.5.2-2ubuntu4 failed to install/upgrade: new click package pre-removal script subprocess returned error exit status 1 Status in click package in Ubuntu: New Bug description: I was updating to new unity sorry i really dont know i am newbie ProblemType: Package DistroRelease: Ubuntu 24.04 Package: click 0.5.2-2ubuntu4 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 25 21:27:28 2024 ErrorMessage: new click package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2024-02-11 (75 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: click Title: package click 0.5.2-2ubuntu4 failed to install/upgrade: new click package pre-removal script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/2063545/+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 2046856] Re: package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status
*** This bug is a duplicate of bug 2047975 *** https://bugs.launchpad.net/bugs/2047975 ** Summary changed: - package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 + package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] ** This bug has been marked a duplicate of bug 2047975 package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] -- 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/2046856 Title: package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] Status in systemd package in Ubuntu: New Bug description: Issue in upgrade of version, more details to be added ProblemType: Package DistroRelease: Ubuntu 23.04 Package: systemd-resolved 252.5-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-39.40-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: server CloudID: configdrive CloudName: configdrive CloudPlatform: configdrive CloudSerial: 20221022 CloudSubPlatform: config-disk (/dev/vdb) Date: Tue Dec 19 01:45:42 2023 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: systemd Title: package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-12-19 (0 days ago) mtime.conffile..etc.systemd.resolved.conf: 2023-08-25T21:57:40.440350 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2046856/+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 2047975] Re: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status
** Summary changed: - package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 + package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] ** Tags added: mantic -- 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/2047975 Title: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] Status in systemd package in Ubuntu: Confirmed Bug description: upgraded from 22.04 -> 24.04 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: systemd-resolved 253.5-1ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Wed Jan 3 21:06:55 2024 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-02-27 (311 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.1ubuntu5 apt 2.7.6 SourcePackage: systemd Title: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-01-03 (0 days ago) mtime.conffile..etc.systemd.resolved.conf: 2023-02-27T21:16:55.869158 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2047975/+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 2046857] Re: package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status
*** This bug is a duplicate of bug 2047975 *** https://bugs.launchpad.net/bugs/2047975 ** This bug is no longer a duplicate of bug 2046856 package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] ** This bug has been marked a duplicate of bug 2047975 package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] -- 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/2046857 Title: package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: Duplicate of 2046856 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: systemd-resolved 252.5-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-39.40-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 AptOrdering: NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: server CloudID: configdrive CloudName: configdrive CloudPlatform: configdrive CloudSerial: 20221022 CloudSubPlatform: config-disk (/dev/vdb) Date: Tue Dec 19 01:56:08 2023 DpkgTerminalLog: Setting up systemd-resolved (252.5-2ubuntu3) ... Converting /etc/resolv.conf to a symlink to /run/systemd/resolve/stub-resolv.conf... cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file dpkg: error processing package systemd-resolved (--configure): installed systemd-resolved package post-installation script subprocess returned error exit status 1 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: systemd Title: package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-12-19 (0 days ago) mtime.conffile..etc.systemd.resolved.conf: 2023-08-25T21:57:40.440350 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2046857/+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 2062550] Re: package systemd-resolved 253.5-1ubuntu6.1 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit statu
*** This bug is a duplicate of bug 2047975 *** https://bugs.launchpad.net/bugs/2047975 ** Summary changed: - package systemd-resolved 253.5-1ubuntu6.1 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 + package systemd-resolved 253.5-1ubuntu6.1 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] ** This bug has been marked a duplicate of bug 2047975 package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] -- 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/2062550 Title: package systemd-resolved 253.5-1ubuntu6.1 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] Status in systemd package in Ubuntu: New Bug description: Upgrade from 22.04 LTS to 23.10 ProblemType: Package DistroRelease: Ubuntu 23.10 Package: systemd-resolved 253.5-1ubuntu6.1 ProcVersionSignature: Ubuntu 6.5.0-1020.21-oem 6.5.13 Uname: Linux 6.5.0-1020-oem x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Apr 19 16:01:52 2024 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-10-24 (178 days ago) InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230810) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.0ubuntu1.1 apt 2.7.3ubuntu0.1 SourcePackage: systemd Title: package systemd-resolved 253.5-1ubuntu6.1 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to mantic on 2024-04-19 (0 days ago) mtime.conffile..etc.systemd.resolved.conf: 2023-10-30T21:36:27.073262 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2062550/+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 2063533] Re: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status
*** This bug is a duplicate of bug 2047975 *** https://bugs.launchpad.net/bugs/2047975 ** Summary changed: - package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 + package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] ** This bug has been marked a duplicate of bug 2047975 package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] -- 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/2063533 Title: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] Status in systemd package in Ubuntu: New Bug description: Trying to update 22.04.4 to 24.04 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Thu Apr 25 23:05:36 2024 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-04-09 (16 days ago) InstallationMedia: Ubuntu-Server 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: systemd Title: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-04-26 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-04-18T19:50:32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063533/+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 2063533] [NEW] package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit statu
Public bug reported: Trying to update 22.04.4 to 24.04 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Thu Apr 25 23:05:36 2024 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-04-09 (16 days ago) InstallationMedia: Ubuntu-Server 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: systemd Title: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-04-26 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-04-18T19:50:32 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check noble -- 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/2063533 Title: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: Trying to update 22.04.4 to 24.04 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Thu Apr 25 23:05:36 2024 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-04-09 (16 days ago) InstallationMedia: Ubuntu-Server 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: systemd Title: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-04-26 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-04-18T19:50:32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063533/+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 2063452] Re: Xorg freeze
It looks like the kernel ran out of memory and the main culprit is a 'java' process. This is not an Ubuntu bug. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2063452 Title: Xorg freeze Status in Ubuntu: Invalid Bug description: My Ubuntu system crashes every time I use an application. It freezes, and I have to force the system to shut down in order to restart it for use, but the problem persists.Please help me ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 13:40:11 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a68] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TigerLake-H GT1 [UHD Graphics] [1462:12eb] Subsystem: Micro-Star International Co., Ltd. [MSI] GA107M [GeForce RTX 3050 Mobile] [1462:12eb] InstallationDate: Installed on 2023-12-01 (145 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Micro-Star International Co., Ltd. Katana GF76 11UC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic root=UUID=0cd75e64-7400-4f1e-bbce-c9c2c1a67e8a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2021 dmi.bios.release: 3.14 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E17L2IMS.30E dmi.board.asset.tag: Default string dmi.board.name: MS-17L2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE17L2IMS.30E:bd10/15/2021:br3.14:svnMicro-StarInternationalCo.,Ltd.:pnKatanaGF7611UC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17L2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17L2.3: dmi.product.family: GF dmi.product.name: Katana GF76 11UC dmi.product.sku: 17L2.3 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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/+bug/2063452/+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 2063503] Re: NVidia drivers won't install completely
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-550 (Ubuntu) ** Also affects: nvidia-graphics-drivers-545 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2063503 Title: NVidia drivers won't install completely Status in nvidia-graphics-drivers-545 package in Ubuntu: New Status in nvidia-graphics-drivers-550 package in Ubuntu: New Bug description: ll versions of the nvidia driver fail to install no matter what. Including the one downloaded from Nvidia. It doesn't matter the version. :~$ sudo apt install nvidia-driver-550 [sudo] password for jim: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following package was automatically installed and is no longer required: nvidia-firmware-545-545.29.06 Use 'sudo apt autoremove' to remove it. The following additional packages will be installed: libnvidia-cfg1-550 libnvidia-common-550 libnvidia-compute-550 libnvidia-compute-550:i386 libnvidia-decode-550 libnvidia-decode-550:i386 libnvidia-encode-550 libnvidia-encode-550:i386 libnvidia-extra-550 libnvidia-fbc1-550 libnvidia-fbc1-550:i386 libnvidia-gl-550 libnvidia-gl-550:i386 nvidia-compute-utils-550 nvidia-dkms-550 nvidia-firmware-550-550.67 nvidia-kernel-common-550 nvidia-kernel-source-550 nvidia-utils-550 xserver-xorg-video-nvidia-550 The following packages will be REMOVED: libnvidia-cfg1-545 libnvidia-common-545 libnvidia-compute-545 libnvidia-compute-545:i386 libnvidia-decode-545 libnvidia-decode-545:i386 libnvidia-encode-545 libnvidia-encode-545:i386 libnvidia-extra-545 libnvidia-fbc1-545 libnvidia-fbc1-545:i386 libnvidia-gl-545 libnvidia-gl-545:i386 nvidia-compute-utils-545 nvidia-dkms-545 nvidia-driver-545 nvidia-kernel-common-545 nvidia-kernel-source-545 nvidia-utils-545 xserver-xorg-video-nvidia-545 The following NEW packages will be installed: libnvidia-cfg1-550 libnvidia-common-550 libnvidia-compute-550 libnvidia-compute-550:i386 libnvidia-decode-550 libnvidia-decode-550:i386 libnvidia-encode-550 libnvidia-encode-550:i386 libnvidia-extra-550 libnvidia-fbc1-550 libnvidia-fbc1-550:i386 libnvidia-gl-550 libnvidia-gl-550:i386 nvidia-compute-utils-550 nvidia-dkms-550 nvidia-driver-550 nvidia-firmware-550-550.67 nvidia-kernel-common-550 nvidia-kernel-source-550 nvidia-utils-550 xserver-xorg-video-nvidia-550 0 upgraded, 21 newly installed, 20 to remove and 15 not upgraded. 2 not fully installed or removed. Need to get 360 MB of archives. After this operation, 14.7 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu noble/multiverse amd64 nvidia-dkms-550 amd64 550.67-0ubuntu3 [35.8 kB] Get:2 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-cfg1-550 amd64 550.67-0ubuntu3 [155 kB] Get:3 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-common-550 all 550.67-0ubuntu3 [14.8 kB] Get:4 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-compute-550 amd64 550.67-0ubuntu3 [41.3 MB] Get:5 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-compute-550 i386 550.67-0ubuntu3 [41.2 MB] Get:6 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-decode-550 amd64 550.67-0ubuntu3 [2,028 kB] Get:7 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-decode-550 i386 550.67-0ubuntu3 [2,470 kB] Get:8 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-encode-550 i386 550.67-0ubuntu3 [115 kB] Get:9 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-encode-550 amd64 550.67-0ubuntu3 [105 kB] Get:10 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-extra-550 amd64 550.67-0ubuntu3 [72.9 kB] Get:11 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-fbc1-550 amd64 550.67-0ubuntu3 [56.4 kB] Get:12 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-fbc1-550 i386 550.67-0ubuntu3 [61.9 kB] Get:13 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-gl-550 amd64 550.67-0ubuntu3 [155 MB] Get:14 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-gl-550 i386 550.67-0ubuntu3 [33.8 MB] Get:15 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-compute-utils-550 amd64 550.67-0ubuntu3 [123 kB] Get:16 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-kernel-source-550 amd64 550.67-0ubuntu3 [41.7 MB] Get:17 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-firmware-550-550.67 amd64 550.67-0ubuntu3 [38.1 MB] Get:18 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-kernel-common-550 amd64
[Touch-packages] [Bug 2063464] VarLogDistupgradeApttermlog.txt
apport information ** Attachment added: "VarLogDistupgradeApttermlog.txt" https://bugs.launchpad.net/bugs/2063464/+attachment/5770666/+files/VarLogDistupgradeApttermlog.txt -- 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/2063464 Title: Package wasn't installed on upgrade from Jammy to Noble Status in systemd package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Incomplete Bug description: I just do-release-upgraded from Jammy to Noble on a pretty minimal server. After upgrade, network was fine but DNS names could not be resolved. I discovered systemd-resolved wasn't installed. I copied and installed that package manually, which immediately resolved the problem. So I assume this is a mistake in the upgrade process. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 25 15:27:23 2024 SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:0:0:25766:2024-04-25 15:32:14.748564723 +:2024-04-25 15:32:14.747564766 +:/var/crash/_usr_bin_docker-compose.0.crash DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Tags: noble dist-upgrade Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) UserGroups: N/A VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063464/+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 2063464] VarLogDistupgradeMainlog.txt
apport information ** Attachment added: "VarLogDistupgradeMainlog.txt" https://bugs.launchpad.net/bugs/2063464/+attachment/5770667/+files/VarLogDistupgradeMainlog.txt -- 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/2063464 Title: Package wasn't installed on upgrade from Jammy to Noble Status in systemd package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Incomplete Bug description: I just do-release-upgraded from Jammy to Noble on a pretty minimal server. After upgrade, network was fine but DNS names could not be resolved. I discovered systemd-resolved wasn't installed. I copied and installed that package manually, which immediately resolved the problem. So I assume this is a mistake in the upgrade process. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 25 15:27:23 2024 SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:0:0:25766:2024-04-25 15:32:14.748564723 +:2024-04-25 15:32:14.747564766 +:/var/crash/_usr_bin_docker-compose.0.crash DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Tags: noble dist-upgrade Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) UserGroups: N/A VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063464/+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 2063464] VarLogDistupgradeAptlog.txt
apport information ** Attachment added: "VarLogDistupgradeAptlog.txt" https://bugs.launchpad.net/bugs/2063464/+attachment/5770665/+files/VarLogDistupgradeAptlog.txt -- 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/2063464 Title: Package wasn't installed on upgrade from Jammy to Noble Status in systemd package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Incomplete Bug description: I just do-release-upgraded from Jammy to Noble on a pretty minimal server. After upgrade, network was fine but DNS names could not be resolved. I discovered systemd-resolved wasn't installed. I copied and installed that package manually, which immediately resolved the problem. So I assume this is a mistake in the upgrade process. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 25 15:27:23 2024 SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:0:0:25766:2024-04-25 15:32:14.748564723 +:2024-04-25 15:32:14.747564766 +:/var/crash/_usr_bin_docker-compose.0.crash DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Tags: noble dist-upgrade Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) UserGroups: N/A VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063464/+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 2063464] VarLogDistupgradeAptHistorylog.txt
apport information ** Attachment added: "VarLogDistupgradeAptHistorylog.txt" https://bugs.launchpad.net/bugs/2063464/+attachment/5770663/+files/VarLogDistupgradeAptHistorylog.txt -- 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/2063464 Title: Package wasn't installed on upgrade from Jammy to Noble Status in systemd package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Incomplete Bug description: I just do-release-upgraded from Jammy to Noble on a pretty minimal server. After upgrade, network was fine but DNS names could not be resolved. I discovered systemd-resolved wasn't installed. I copied and installed that package manually, which immediately resolved the problem. So I assume this is a mistake in the upgrade process. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 25 15:27:23 2024 SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:0:0:25766:2024-04-25 15:32:14.748564723 +:2024-04-25 15:32:14.747564766 +:/var/crash/_usr_bin_docker-compose.0.crash DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Tags: noble dist-upgrade Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) UserGroups: N/A VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063464/+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 2063464] VarLogDistupgradeAptclonesystemstate.tar.gz
apport information ** Attachment added: "VarLogDistupgradeAptclonesystemstate.tar.gz" https://bugs.launchpad.net/bugs/2063464/+attachment/5770664/+files/VarLogDistupgradeAptclonesystemstate.tar.gz -- 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/2063464 Title: Package wasn't installed on upgrade from Jammy to Noble Status in systemd package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Incomplete Bug description: I just do-release-upgraded from Jammy to Noble on a pretty minimal server. After upgrade, network was fine but DNS names could not be resolved. I discovered systemd-resolved wasn't installed. I copied and installed that package manually, which immediately resolved the problem. So I assume this is a mistake in the upgrade process. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 25 15:27:23 2024 SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:0:0:25766:2024-04-25 15:32:14.748564723 +:2024-04-25 15:32:14.747564766 +:/var/crash/_usr_bin_docker-compose.0.crash DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Tags: noble dist-upgrade Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) UserGroups: N/A VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063464/+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 2063464] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2063464/+attachment/5770662/+files/ProcEnviron.txt -- 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/2063464 Title: Package wasn't installed on upgrade from Jammy to Noble Status in systemd package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Incomplete Bug description: I just do-release-upgraded from Jammy to Noble on a pretty minimal server. After upgrade, network was fine but DNS names could not be resolved. I discovered systemd-resolved wasn't installed. I copied and installed that package manually, which immediately resolved the problem. So I assume this is a mistake in the upgrade process. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 25 15:27:23 2024 SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:0:0:25766:2024-04-25 15:32:14.748564723 +:2024-04-25 15:32:14.747564766 +:/var/crash/_usr_bin_docker-compose.0.crash DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Tags: noble dist-upgrade Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) UserGroups: N/A VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063464/+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 2063464] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2063464/+attachment/5770661/+files/ProcCpuinfoMinimal.txt -- 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/2063464 Title: Package wasn't installed on upgrade from Jammy to Noble Status in systemd package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Incomplete Bug description: I just do-release-upgraded from Jammy to Noble on a pretty minimal server. After upgrade, network was fine but DNS names could not be resolved. I discovered systemd-resolved wasn't installed. I copied and installed that package manually, which immediately resolved the problem. So I assume this is a mistake in the upgrade process. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 25 15:27:23 2024 SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:0:0:25766:2024-04-25 15:32:14.748564723 +:2024-04-25 15:32:14.747564766 +:/var/crash/_usr_bin_docker-compose.0.crash DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Tags: noble dist-upgrade Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) UserGroups: N/A VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063464/+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 2063464] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/2063464/+attachment/5770660/+files/JournalErrors.txt -- 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/2063464 Title: Package wasn't installed on upgrade from Jammy to Noble Status in systemd package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Incomplete Bug description: I just do-release-upgraded from Jammy to Noble on a pretty minimal server. After upgrade, network was fine but DNS names could not be resolved. I discovered systemd-resolved wasn't installed. I copied and installed that package manually, which immediately resolved the problem. So I assume this is a mistake in the upgrade process. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 25 15:27:23 2024 SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:0:0:25766:2024-04-25 15:32:14.748564723 +:2024-04-25 15:32:14.747564766 +:/var/crash/_usr_bin_docker-compose.0.crash DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Tags: noble dist-upgrade Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) UserGroups: N/A VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063464/+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 2063464] Re: Package wasn't installed on upgrade from Jammy to Noble
apport information ** Tags added: apport-collected dist-upgrade ** Description changed: I just do-release-upgraded from Jammy to Noble on a pretty minimal server. After upgrade, network was fine but DNS names could not be resolved. I discovered systemd-resolved wasn't installed. I copied and installed that package manually, which immediately resolved the problem. So I assume this is a mistake in the upgrade process. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 25 15:27:23 2024 SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) + --- + ProblemType: Bug + ApportVersion: 2.28.1-0ubuntu2 + Architecture: amd64 + CasperMD5CheckResult: unknown + CrashDB: ubuntu + CrashReports: 640:0:0:25766:2024-04-25 15:32:14.748564723 +:2024-04-25 15:32:14.747564766 +:/var/crash/_usr_bin_docker-compose.0.crash + DistroRelease: Ubuntu 24.04 + Package: ubuntu-release-upgrader (not installed) + ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 + Tags: noble dist-upgrade + Uname: Linux 6.8.0-31-generic x86_64 + UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) + UserGroups: N/A + VarLogDistupgradeXorgFixuplog: + INFO:root:/usr/bin/do-release-upgrade running + INFO:root:No xorg.conf, exiting + _MarkForUpload: True ** Attachment added: "CurrentDmesg.txt.txt" https://bugs.launchpad.net/bugs/2063464/+attachment/5770659/+files/CurrentDmesg.txt.txt -- 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/2063464 Title: Package wasn't installed on upgrade from Jammy to Noble Status in systemd package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Incomplete Bug description: I just do-release-upgraded from Jammy to Noble on a pretty minimal server. After upgrade, network was fine but DNS names could not be resolved. I discovered systemd-resolved wasn't installed. I copied and installed that package manually, which immediately resolved the problem. So I assume this is a mistake in the upgrade process. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 25 15:27:23 2024 SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:0:0:25766:2024-04-25 15:32:14.748564723 +:2024-04-25 15:32:14.747564766 +:/var/crash/_usr_bin_docker-compose.0.crash DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Tags: noble dist-upgrade Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) UserGroups: N/A VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063464/+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 2063503] Re: NVidia drivers won't install completely
This appears to be the issue. DRM_UNLOCKED does not exist for nvidia- drm-drv.c to compile. Missing ot changed kernel header? # CC [M] /var/lib/dkms/nvidia/545.29.06/build/nvidia-drm/nvidia-drm-gem-nvkms-memory.o cc -Wp,-MMD,/var/lib/dkms/nvidia/545.29.06/build/nvidia-drm/.nvidia-drm-gem-nvkms-memory.o.d -nostdinc -I./arch/x86/include -I./arch/x86/include/generated -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/compiler-version.h -include ./include/linux/kconfig.h -I./ubuntu/include -include ./include/linux/compiler_types.h -D__KERNEL__ -fmacro-prefix-map=./= -std=gnu11 -fshort-wchar -funsigned-char -fno-common -fno-PIE -fno-strict-aliasing -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -fcf-protection=none -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -mindirect-branch-cs-prefix -mfunction-return=thunk-extern -fno-jump-tables -mharden-sls=all -fpatchable-function-entry=16,16 -fno-delete-null-pointer-checks -O2 -fno-allow-store-data-races -fstack-protector-strong -fno-omit-frame-pointer -fno-optimize-sibling-calls -ftrivial-auto-var-init=zero -fno-stack-clash-protection -fzero-call-used-regs=used-gpr -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY -falign-functions=16 -fstrict-flex-arrays=3 -fno-strict-overflow -fno-stack-check -fconserve-stack -Wall -Wundef -Werror=implicit-function-declaration -Werror=implicit-int -Werror=return-type -Werror=strict-prototypes -Wno-format-security -Wno-trigraphs -Wno-frame-address -Wno-address-of-packed-member -Wmissing-declarations -Wmissing-prototypes -Wframe-larger-than=1024 -Wno-main -Wno-unused-but-set-variable -Wno-unused-const-variable -Wno-dangling-pointer -Wvla -Wno-pointer-sign -Wcast-function-type -Wno-stringop-overflow -Wno-array-bounds -Wno-alloc-size-larger-than -Wimplicit-fallthrough=5 -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -Wenum-conversion -Wno-unused-but-set-variable -Wno-unused-const-variable -Wno-restrict -Wno-packed-not-aligned -Wno-format-overflow -Wno-format-truncation -Wno-stringop-truncation -Wno-missing-field-initializers -Wno-type-limits -Wno-shift-negative-value -Wno-maybe-uninitialized -Wno-sign-compare -g -gdwarf-5 -I/var/lib/dkms/nvidia/545.29.06/build/common/inc -I/var/lib/dkms/nvidia/545.29.06/build -Wall -Wno-cast-qual -Wno-error -Wno-format-extra-args -D__KERNEL__ -DMODULE -DNVRM -DNV_VERSION_STRING=\"545.29.06\" -DNV_FILESYSTEM_ACCESS_AVAILABLE=1 -Wno-unused-function -Wuninitialized -fno-strict-aliasing -ffreestanding -mno-red-zone -mcmodel=kernel -DNV_UVM_ENABLE -Werror=undef -DNV_SPECTRE_V2=0 -DNV_KERNEL_INTERFACE_LAYER -I/var/lib/dkms/nvidia/545.29.06/build/nvidia-drm -UDEBUG -U_DEBUG -DNDEBUG -DNV_BUILD_MODULE_INSTANCES=0 -fsanitize=bounds-strict -fsanitize=shift -fsanitize=bool -fsanitize=enum -DMODULE -DKBUILD_BASENAME='"nvidia_drm_gem_nvkms_memory"' -DKBUILD_MODNAME='"nvidia_drm"' -D__KBUILD_MODNAME=kmod_nvidia_drm -c -o /var/lib/dkms/nvidia/545.29.06/build/nvidia-drm/nvidia-drm-gem-nvkms-memory.o /var/lib/dkms/nvidia/545.29.06/build/nvidia-drm/nvidia-drm-gem-nvkms-memory.c ; ./tools/objtool/objtool --hacks=jump_label --hacks=noinstr --hacks=skylake --retpoline --rethunk --sls --stackval --static-call --uaccess --prefix=16 --module /var/lib/dkms/nvidia/545.29.06/build/nvidia-drm/nvidia-drm-gem-nvkms-memory.o In file included from /var/lib/dkms/nvidia/545.29.06/build/nvidia-drm/nvidia-drm-drv.c:64: /var/lib/dkms/nvidia/545.29.06/build/nvidia-drm/nvidia-drm-drv.c:1489:40: error: ‘DRM_UNLOCKED’ undeclared here (not in a function); did you mean ‘VM_LOCKED’? 1489 | DRM_RENDER_ALLOW|DRM_UNLOCKED), |^~~~ ./include/drm/drm_ioctl.h:155:26: note: in definition of macro ‘DRM_IOCTL_DEF_DRV’ 155 | .flags = _flags, \ | ^~ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2063503 Title: NVidia drivers won't install completely Status in xorg package in Ubuntu: New Bug description: ll versions of the nvidia driver fail to install no matter what. Including the one downloaded from Nvidia. It doesn't matter the version. :~$ sudo apt install nvidia-driver-550 [sudo] password for jim: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following package was automatically installed and is no longer required: nvidia-firmware-545-545.29.06 Use 'sudo apt autoremove' to remove
[Touch-packages] [Bug 2061708] Re: Yubikey stopped working after noble upgrade
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnupg2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/2061708 Title: Yubikey stopped working after noble upgrade Status in Arch Linux on Launchpad: Fix Released Status in gnupg2 package in Ubuntu: Confirmed Status in pcsc-lite package in Ubuntu: Invalid Bug description: In Ubuntu 22.04 I used by GPG key stored on a Yubikey smart card, but since upgrading to Noble I get the following trying to access it. $ gpg --card-status gpg: selecting card failed: No such device gpg: OpenPGP card not available: No such device If I run this as root it works: $ sudo gpg --card-status Reader ...: 1050:0407:X:0 Application ID ...: D27600012401000609082616 Application type .: OpenPGP Version ..: 2.1 Manufacturer .: Yubico Serial number : Name of cardholder: [not set] Language prefs ...: [not set] Salutation ...: URL of public key : [not set] Login data ...: [not set] Signature PIN : not forced Key attributes ...: rsa4096 rsa4096 rsa2048 Max. PIN lengths .: 127 127 127 PIN retry counter : 10 0 10 Signature counter : 1172 UIF setting ..: Sign=off Decrypt=off Auth=off Signature key : created : Encryption key: created : Authentication key: [none] General key info..: [none] If I manually run pcscd.service then it stops working both as root and a user. $ sudo pkill -9 scdaemon $ sudo systemctl start pcscd.service $ gpg --card-status gpg: selecting card failed: No such device gpg: OpenPGP card not available: No such device $ sudo gpg --card-status gpg: selecting card failed: No such device gpg: OpenPGP card not available: No such device It might be worth mentioning I'm accessing the machine over SSH, so I also did experiment with a polkit rule like this: polkit.addRule(function(action, subject) { if (action.id == "org.debian.pcsc-lite.access_card" && subject.isInGroup("sudo")) { return polkit.Result.YES; } }); polkit.addRule(function(action, subject) { if (action.id == "org.debian.pcsc-lite.access_pcsc" && subject.isInGroup("sudo")) { return polkit.Result.YES; } }); Added into /etc/polkit-1/rules.d/99-pcscd.rules and then reloading polkit.service in case this was a polkit issue, but this didn't do anything. Versions in noble: pcscd: 2.0.3-1build1 libpcslite1: 2.0.3-1build1 gnupg: 2.4.4-2ubuntu17 scdaemon: 2.4.4-2ubuntu17 To manage notifications about this bug go to: https://bugs.launchpad.net/archlinux-lp/+bug/2061708/+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 2063503] Re: NVidia drivers won't install completely
** Attachment added: "The make.log referred to in my comment above" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2063503/+attachment/5770654/+files/make.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2063503 Title: NVidia drivers won't install completely Status in xorg package in Ubuntu: New Bug description: ll versions of the nvidia driver fail to install no matter what. Including the one downloaded from Nvidia. It doesn't matter the version. :~$ sudo apt install nvidia-driver-550 [sudo] password for jim: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following package was automatically installed and is no longer required: nvidia-firmware-545-545.29.06 Use 'sudo apt autoremove' to remove it. The following additional packages will be installed: libnvidia-cfg1-550 libnvidia-common-550 libnvidia-compute-550 libnvidia-compute-550:i386 libnvidia-decode-550 libnvidia-decode-550:i386 libnvidia-encode-550 libnvidia-encode-550:i386 libnvidia-extra-550 libnvidia-fbc1-550 libnvidia-fbc1-550:i386 libnvidia-gl-550 libnvidia-gl-550:i386 nvidia-compute-utils-550 nvidia-dkms-550 nvidia-firmware-550-550.67 nvidia-kernel-common-550 nvidia-kernel-source-550 nvidia-utils-550 xserver-xorg-video-nvidia-550 The following packages will be REMOVED: libnvidia-cfg1-545 libnvidia-common-545 libnvidia-compute-545 libnvidia-compute-545:i386 libnvidia-decode-545 libnvidia-decode-545:i386 libnvidia-encode-545 libnvidia-encode-545:i386 libnvidia-extra-545 libnvidia-fbc1-545 libnvidia-fbc1-545:i386 libnvidia-gl-545 libnvidia-gl-545:i386 nvidia-compute-utils-545 nvidia-dkms-545 nvidia-driver-545 nvidia-kernel-common-545 nvidia-kernel-source-545 nvidia-utils-545 xserver-xorg-video-nvidia-545 The following NEW packages will be installed: libnvidia-cfg1-550 libnvidia-common-550 libnvidia-compute-550 libnvidia-compute-550:i386 libnvidia-decode-550 libnvidia-decode-550:i386 libnvidia-encode-550 libnvidia-encode-550:i386 libnvidia-extra-550 libnvidia-fbc1-550 libnvidia-fbc1-550:i386 libnvidia-gl-550 libnvidia-gl-550:i386 nvidia-compute-utils-550 nvidia-dkms-550 nvidia-driver-550 nvidia-firmware-550-550.67 nvidia-kernel-common-550 nvidia-kernel-source-550 nvidia-utils-550 xserver-xorg-video-nvidia-550 0 upgraded, 21 newly installed, 20 to remove and 15 not upgraded. 2 not fully installed or removed. Need to get 360 MB of archives. After this operation, 14.7 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu noble/multiverse amd64 nvidia-dkms-550 amd64 550.67-0ubuntu3 [35.8 kB] Get:2 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-cfg1-550 amd64 550.67-0ubuntu3 [155 kB] Get:3 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-common-550 all 550.67-0ubuntu3 [14.8 kB] Get:4 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-compute-550 amd64 550.67-0ubuntu3 [41.3 MB] Get:5 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-compute-550 i386 550.67-0ubuntu3 [41.2 MB] Get:6 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-decode-550 amd64 550.67-0ubuntu3 [2,028 kB] Get:7 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-decode-550 i386 550.67-0ubuntu3 [2,470 kB] Get:8 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-encode-550 i386 550.67-0ubuntu3 [115 kB] Get:9 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-encode-550 amd64 550.67-0ubuntu3 [105 kB] Get:10 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-extra-550 amd64 550.67-0ubuntu3 [72.9 kB] Get:11 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-fbc1-550 amd64 550.67-0ubuntu3 [56.4 kB] Get:12 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-fbc1-550 i386 550.67-0ubuntu3 [61.9 kB] Get:13 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-gl-550 amd64 550.67-0ubuntu3 [155 MB] Get:14 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-gl-550 i386 550.67-0ubuntu3 [33.8 MB] Get:15 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-compute-utils-550 amd64 550.67-0ubuntu3 [123 kB] Get:16 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-kernel-source-550 amd64 550.67-0ubuntu3 [41.7 MB] Get:17 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-firmware-550-550.67 amd64 550.67-0ubuntu3 [38.1 MB] Get:18 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-kernel-common-550 amd64 550.67-0ubuntu3 [120 kB] Get:19 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64
[Touch-packages] [Bug 2063503] Re: NVidia drivers won't install completely
Tried again after purging all things NVidia and rebooting. :~$ sudo ubuntu-drivers install --recommended udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: libnvidia-cfg1-545 libnvidia-common-545 libnvidia-compute-545 libnvidia-decode-545 libnvidia-encode-545 libnvidia-extra-545 libnvidia-fbc1-545 libnvidia-gl-545 libnvidia-gl-545:i386 nvidia-compute-utils-545 nvidia-firmware-545-545.29.06 nvidia-kernel-common-545 nvidia-kernel-source-545 nvidia-prime nvidia-settings nvidia-utils-545 xserver-xorg-video-nvidia-545 The following NEW packages will be installed: libnvidia-cfg1-545 libnvidia-common-545 libnvidia-compute-545 libnvidia-decode-545 libnvidia-encode-545 libnvidia-extra-545 libnvidia-fbc1-545 libnvidia-gl-545 libnvidia-gl-545:i386 nvidia-compute-utils-545 nvidia-dkms-545 nvidia-driver-545 nvidia-firmware-545-545.29.06 nvidia-kernel-common-545 nvidia-kernel-source-545 nvidia-prime nvidia-settings nvidia-utils-545 xserver-xorg-video-nvidia-545 0 upgraded, 19 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/338 MB of archives. After this operation, 908 MB of additional disk space will be used. Selecting previously unselected package libnvidia-cfg1-545:amd64. (Reading database ... 339019 files and directories currently installed.) Preparing to unpack .../00-libnvidia-cfg1-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking libnvidia-cfg1-545:amd64 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package libnvidia-common-545. Preparing to unpack .../01-libnvidia-common-545_545.29.06-0ubuntu0~gpu24.04.1_all.deb ... Unpacking libnvidia-common-545 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package libnvidia-compute-545:amd64. Preparing to unpack .../02-libnvidia-compute-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking libnvidia-compute-545:amd64 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package libnvidia-decode-545:amd64. Preparing to unpack .../03-libnvidia-decode-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking libnvidia-decode-545:amd64 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package libnvidia-encode-545:amd64. Preparing to unpack .../04-libnvidia-encode-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking libnvidia-encode-545:amd64 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package libnvidia-extra-545:amd64. Preparing to unpack .../05-libnvidia-extra-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking libnvidia-extra-545:amd64 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package libnvidia-fbc1-545:amd64. Preparing to unpack .../06-libnvidia-fbc1-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking libnvidia-fbc1-545:amd64 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package libnvidia-gl-545:i386. Preparing to unpack .../07-libnvidia-gl-545_545.29.06-0ubuntu0~gpu24.04.1_i386.deb ... dpkg-query: no packages found matching libnvidia-gl-535 Unpacking libnvidia-gl-545:i386 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package libnvidia-gl-545:amd64. Preparing to unpack .../08-libnvidia-gl-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... dpkg-query: no packages found matching libnvidia-gl-535 Unpacking libnvidia-gl-545:amd64 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package nvidia-compute-utils-545. Preparing to unpack .../09-nvidia-compute-utils-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking nvidia-compute-utils-545 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package nvidia-kernel-source-545. Preparing to unpack .../10-nvidia-kernel-source-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking nvidia-kernel-source-545 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package nvidia-firmware-545-545.29.06. Preparing to unpack .../11-nvidia-firmware-545-545.29.06_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking nvidia-firmware-545-545.29.06 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package nvidia-kernel-common-545. Preparing to unpack .../12-nvidia-kernel-common-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking nvidia-kernel-common-545 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously unselected package nvidia-dkms-545. Preparing to unpack .../13-nvidia-dkms-545_545.29.06-0ubuntu0~gpu24.04.1_amd64.deb ... Unpacking nvidia-dkms-545 (545.29.06-0ubuntu0~gpu24.04.1) ... Selecting previously
[Touch-packages] [Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 I had UI crash during upgrade from jammy. I had to go to recovery mode and run dpkg. I confirm sudo apt install systemd-resolved resolves the problem. But the upgrade is not recommended as you may encounter unfinished upgrade and gnome shell crash. -- 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/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to the end of the upgrade, I got an „Oh, no! Something has gone wrong and the system cannot recover. Call the system administrator” message after a red FAILED in the terminal. The system administrator is myself, because my computer is a personal one. Hard reset, same error, Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the update with dpkg. While dpkg was upgrading, it printed an error message for every WiFi connection: „[Failed] Failed to migrate [I do not remember, something with /etc/netplan]” It took at least one and a half hour to find the solution on Ask Ubuntu. The problem was: /etc/resolv.conf became a broken link, along with systemd-resolve.service. I needed to remove both of them and write a new resolv.conf to fix the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 08:21:02 2024 InstallationDate: Installed on 2023-07-05 (236 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) IpRoute: default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.45.90 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+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 2063369] Re: e2image reports invalid argument when used with big partitions
Oh, sorry, I thought the limit cannot be reached that easy in case of sparse files full of unalocated blocks. Apparently the limit includes the unallocated space. I retested that again and the sparse file really gets truncated to 16TB and I believe that's exactly the moment when the tool should report some error like: "Unable to create sparse file of that size! Unsupported by the target filesystem." Instead of that the tool continues to extract data and after a long time it fails with Invalid argument. To prevent confusion, would it be possible to modify the code to make it fail immediately when it fails to create the sparse file of the required size? Thank you. -- 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/2063369 Title: e2image reports invalid argument when used with big partitions Status in e2fsprogs package in Ubuntu: New Bug description: It seems e2image is unable to work correctly with large filesystems. I get the following error with etx4 on top of 48TB RAID5 array. # e2image -pr /dev/md3 md3.e2i e2image 1.46.5 (30-Dec-2021) Scanning inodes... Copying 802818 / 1547571 blocks (52%) 00:02:21 remaining at 20.50 MB/sseek_relative: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2063369/+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 2063503] [NEW] NVidia drivers won't install completely
Public bug reported: ll versions of the nvidia driver fail to install no matter what. Including the one downloaded from Nvidia. It doesn't matter the version. :~$ sudo apt install nvidia-driver-550 [sudo] password for jim: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following package was automatically installed and is no longer required: nvidia-firmware-545-545.29.06 Use 'sudo apt autoremove' to remove it. The following additional packages will be installed: libnvidia-cfg1-550 libnvidia-common-550 libnvidia-compute-550 libnvidia-compute-550:i386 libnvidia-decode-550 libnvidia-decode-550:i386 libnvidia-encode-550 libnvidia-encode-550:i386 libnvidia-extra-550 libnvidia-fbc1-550 libnvidia-fbc1-550:i386 libnvidia-gl-550 libnvidia-gl-550:i386 nvidia-compute-utils-550 nvidia-dkms-550 nvidia-firmware-550-550.67 nvidia-kernel-common-550 nvidia-kernel-source-550 nvidia-utils-550 xserver-xorg-video-nvidia-550 The following packages will be REMOVED: libnvidia-cfg1-545 libnvidia-common-545 libnvidia-compute-545 libnvidia-compute-545:i386 libnvidia-decode-545 libnvidia-decode-545:i386 libnvidia-encode-545 libnvidia-encode-545:i386 libnvidia-extra-545 libnvidia-fbc1-545 libnvidia-fbc1-545:i386 libnvidia-gl-545 libnvidia-gl-545:i386 nvidia-compute-utils-545 nvidia-dkms-545 nvidia-driver-545 nvidia-kernel-common-545 nvidia-kernel-source-545 nvidia-utils-545 xserver-xorg-video-nvidia-545 The following NEW packages will be installed: libnvidia-cfg1-550 libnvidia-common-550 libnvidia-compute-550 libnvidia-compute-550:i386 libnvidia-decode-550 libnvidia-decode-550:i386 libnvidia-encode-550 libnvidia-encode-550:i386 libnvidia-extra-550 libnvidia-fbc1-550 libnvidia-fbc1-550:i386 libnvidia-gl-550 libnvidia-gl-550:i386 nvidia-compute-utils-550 nvidia-dkms-550 nvidia-driver-550 nvidia-firmware-550-550.67 nvidia-kernel-common-550 nvidia-kernel-source-550 nvidia-utils-550 xserver-xorg-video-nvidia-550 0 upgraded, 21 newly installed, 20 to remove and 15 not upgraded. 2 not fully installed or removed. Need to get 360 MB of archives. After this operation, 14.7 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu noble/multiverse amd64 nvidia-dkms-550 amd64 550.67-0ubuntu3 [35.8 kB] Get:2 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-cfg1-550 amd64 550.67-0ubuntu3 [155 kB] Get:3 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-common-550 all 550.67-0ubuntu3 [14.8 kB] Get:4 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-compute-550 amd64 550.67-0ubuntu3 [41.3 MB] Get:5 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-compute-550 i386 550.67-0ubuntu3 [41.2 MB] Get:6 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-decode-550 amd64 550.67-0ubuntu3 [2,028 kB] Get:7 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-decode-550 i386 550.67-0ubuntu3 [2,470 kB] Get:8 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-encode-550 i386 550.67-0ubuntu3 [115 kB] Get:9 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-encode-550 amd64 550.67-0ubuntu3 [105 kB] Get:10 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-extra-550 amd64 550.67-0ubuntu3 [72.9 kB] Get:11 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-fbc1-550 amd64 550.67-0ubuntu3 [56.4 kB] Get:12 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-fbc1-550 i386 550.67-0ubuntu3 [61.9 kB] Get:13 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-gl-550 amd64 550.67-0ubuntu3 [155 MB] Get:14 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-gl-550 i386 550.67-0ubuntu3 [33.8 MB] Get:15 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-compute-utils-550 amd64 550.67-0ubuntu3 [123 kB] Get:16 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-kernel-source-550 amd64 550.67-0ubuntu3 [41.7 MB] Get:17 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-firmware-550-550.67 amd64 550.67-0ubuntu3 [38.1 MB] Get:18 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-kernel-common-550 amd64 550.67-0ubuntu3 [120 kB] Get:19 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-utils-550 amd64 550.67-0ubuntu3 [521 kB] Get:20 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 xserver-xorg-video-nvidia-550 amd64 550.67-0ubuntu3 [1,616 kB] Get:21 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-driver-550 amd64 550.67-0ubuntu3 [486 kB] Fetched 360 MB in 30s (11.8 MB/s) (Reading database ... 339762 files and directories currently installed.) Removing nvidia-driver-545 (545.29.06-0ubuntu0~gpu24.04.1) ... Removing nvidia-dkms-545
[Touch-packages] [Bug 2036761] Re: [mantic] ppa-purge no longer purges what add-apt-repository adds
Apparently, there is nothing to be sponsored here, I am unsubscribing ~ubuntu-sponsors. If I misunderstood the status of this bug and there is something ready to be sponsored, please subscribe ~ubuntu-sponsors again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2036761 Title: [mantic] ppa-purge no longer purges what add-apt-repository adds Status in ppa-purge package in Ubuntu: Fix Released Status in software-properties package in Ubuntu: Confirmed Status in ppa-purge source package in Mantic: Fix Committed Status in software-properties source package in Mantic: Confirmed Status in ppa-purge source package in Noble: Fix Released Status in software-properties source package in Noble: Confirmed Bug description: Thank you @jbicha for the original bug report! [ Impact ] Currently ppa-purge fails to purge packages on distribution using the deb822 source format. Currently mantic and noble make use of this format and are affected by this issue. When running ppa-purge to remove a custom PPA, ppa-purge fails to disable the custom PPA since it cannot disable deb822 sources and leads to apt still querying the ppa when running: $ apt update In older versions of ubuntu, PPAs used the ".list" format which could be disabled by simply commenting out the "deb" line with a "#". This was the method that ppa-purge used to disable PPAs. This new patch allows ppa-purge to detect and disable deb822 source files by adding an "Enabled: no" field in each component section of the deb822 file. It also removes any line that starts with "Enabled:" to make sure the resulting file is clean. [ Test Plan ] The changes were tested on both mantic and noble in a lxc container using the oibaf mesa PPA (https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers) as the test PPA. The following steps were recorded in a noble lxc container. - First make sure that mesa-utils is installed in your environment: $ sudo apt update && sudo apt install mesa-utils - Add the oibaf PPA to your system using the following command: $ sudo add-apt-repository ppa:oibaf/graphics-drivers - Make sure that the mesa-utils packages were upgraded after adding the PPA: $ sudo apt update && sudo apt upgrade $ dpkg - l | grep mesa - output should be similar to the following: ii libegl-mesa0:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the EGL API -- Mesa vendor library ii libgl1-mesa-dri:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the OpenGL API -- DRI modules ii libglapi-mesa:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the GL API -- shared library ii libglx-mesa0:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the OpenGL API -- GLX vendor library ii mesa-utils 9.0.0-2 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd649.0.0-2 amd64Miscellaneous Mesa utilities -- native applications ii mesa-vulkan-drivers:amd64 24.1~git2402280600.41722c~oibaf~n amd64Mesa Vulkan graphics drivers - Install and run ppa-purge: $ sudo apt install ppa-purge $ sudo ppa-purge ppa:oibaf/graphics-drivers - ppa-purge will report at the end that none of the oibaf packages need to be downgraded/removed: libglapi-mesa is already the newest version (24.1~git2402280600.41722c~oibaf~n). libglapi-mesa set to manually installed. libglx-mesa0 is already the newest version (24.1~git2402280600.41722c~oibaf~n). libglx-mesa0 set to manually installed. mesa-vulkan-drivers is already the newest version (24.1~git2402280600.41722c~oibaf~n). mesa-vulkan-drivers set to manually installed. Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-amdgpu1' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [all]) for 'libdrm-common' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-intel1' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-nouveau2' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-radeon1' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers -
[Touch-packages] [Bug 1958019]
Created attachment 306213 kernel-mute.log (In reply to Tintin from comment #874) > # . tas2781-2dev-on.sh 2 Sorry if this is a bit long, but trying to include info to help debug the issue. Well, it has finally happened again... It seems like the script hasn't really helped... But I'll have to try it again next time this happens to determine what, if any, role it had. So far it looks like it hasn't helped. I was able to get my sound working by running this: "killall pipewire- pulse" and quitting/killing audacious (audacious usually but not always hangs when this starts happening), and quitting firefox, thought not necessarily in that order? But even that isn't enough to completely fix it. Likely, it would come back as soon as I start playing audio from more than one application at a time. When playing audio from another application, it would work for a few seconds, and then one of the applications would stop working. Almost like the audio device had become usable by one application at a time (like in the early ALSA days prior to pulseaudio becoming common). And probably if I stopped the other application, it usually wouldn't stop working again until repeating the above steps. But playing with it some more (with both quitting applications, killing pipewire-pulse over and over), I was eventually able to get audio to consistently work again (ie, normally) for about the last 30 minutes or so. I tried logging out and back at one point... That didn't seem to fix it either. It wasn't until several (or a bunch more) killing pipewire- pulse, restarting firefox and audacious a few times (I could try other software too!) that it started working again. I'm leaning toward this being a pipewire-pulse issue at this point... but it's possible that there's a driver issue that causes pipewise-pulse becoming wedged, and that running tas2781-2dev-on.sh and killing pipewise-pulse I'm eventually able to get things into a good state. If this happens again, I will conduct more testing... And I say if, because I think Ubuntu 24.04 is out today, and if it is... I will likely upgrade. If this is a software issue, good chance 24.04 won't have this problem. I'll report back with my results either way. Anyone else tried killing pipewire-pulse when having issues? I didn't see any sort of run away processes, I simply did "ps paux | grep pulse" and that was the only process that showed up so I tried killing it. It was just a guess from remembering all the early pulseaudio issues from over a decade ago. :D Here's my info for convenience: Kernel 6.8.7 Kubuntu 23.10 Running with KDE+Wayland My pipewire-pulse info: apt policy pipewire-pulse pipewire-pulse: Installed: 0.3.79-2 Candidate: 0.3.79-2 Version table: *** 0.3.79-2 500 500 http://us.archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status I didn't have this problem with the older kernel 6.7.x series, but maybe there was a pipewire-pulse update that happened? Or and update to a package it depends on? Finally, I've attached the requested dmesg output. My audio problems started after 10:30 (maybe around 10:40-ish?) and my audio had been completely working for around 15 minutes as of the time I'd captured that dmesg output. Seems like nothing really relevant, but maybe there's something helpful? -- 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: USER
[Touch-packages] [Bug 2061118] Re: Rendering issues in vmware with 3d on (GTK ngl backend)
Microsoft Windows [Version 10.0.22631.3447] Processor AMD Ryzen 7 3700X 8-Core Processor, 3600 Mhz, 8 Core(s), 16 Logical Processor(s) System ModelX570 AORUS PRO WIFI RTX 2070 -- 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/2061118 Title: Rendering issues in vmware with 3d on (GTK ngl backend) Status in GTK+: New Status in Mesa: New Status in gtk4 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Status in gtk4 source package in Noble: Invalid Status in mesa source package in Noble: Triaged Bug description: Build: Noble Daily Current from 12th April Host OS: Windows 11 VM App: VMWare Workstation 17 Player Issue: During installation there is continuous black flickering artefacts throughout the flow. Installation completed successfully, got to GDM, logged in but desktop screen is black and then locks up the whole application, cannot shutdown or interact with Player and need to hard kill from task manager. The issue appears does not appear with Mantic with the exact same machine configuration and appears to be an issue with GPU, my host machine is running an NVIDIA 4070ti with the latest windows drivers. On reboot some elements of the desktop are visible but cannot be interacted with without further lockups. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+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 2061118] Re: Rendering issues in vmware with 3d on (GTK ngl backend)
vmware 17.5 win 11 not fixed with todays iso. mesa is 24.0.5. Can see gui without enable 3d acceleration, but black screen and have to task manager kill with 3d acceleration. rtx 2070 -- 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/2061118 Title: Rendering issues in vmware with 3d on (GTK ngl backend) Status in GTK+: New Status in Mesa: New Status in gtk4 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Status in gtk4 source package in Noble: Invalid Status in mesa source package in Noble: Triaged Bug description: Build: Noble Daily Current from 12th April Host OS: Windows 11 VM App: VMWare Workstation 17 Player Issue: During installation there is continuous black flickering artefacts throughout the flow. Installation completed successfully, got to GDM, logged in but desktop screen is black and then locks up the whole application, cannot shutdown or interact with Player and need to hard kill from task manager. The issue appears does not appear with Mantic with the exact same machine configuration and appears to be an issue with GPU, my host machine is running an NVIDIA 4070ti with the latest windows drivers. On reboot some elements of the desktop are visible but cannot be interacted with without further lockups. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+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 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs
@Matthew I took a look at your debdiffs (I hope they are updated) and they look good in general, I checked the debdiffs for Focal, Jammy, Mantic and Noble. The Noble debdiff requires a rebase, now in Noble we have version 1.47.0-2.4~exp1ubuntu4, so we want version 1.47.0-2.4~exp1ubuntu4.1 with your changes (it will be a SRU for Noble as well at this point). This will need to be fixed in the next development release (OO series) to avoid any future regression. But at the moment the archive is not yet open for that. Please, fix that and someone can sponsor the uploads targeting all supported releases at once. I am unsubscribing ~ubuntu-sponsors, once you address the comment above please subscribe it again and someone will take a look. -- 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/2036467 Title: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs Status in cloud-images: New Status in e2fsprogs package in Ubuntu: In Progress Status in e2fsprogs source package in Trusty: Won't Fix Status in e2fsprogs source package in Xenial: Won't Fix Status in e2fsprogs source package in Bionic: Won't Fix Status in e2fsprogs source package in Focal: In Progress Status in e2fsprogs source package in Jammy: In Progress Status in e2fsprogs source package in Lunar: Won't Fix Status in e2fsprogs source package in Mantic: In Progress Status in e2fsprogs source package in Noble: In Progress Bug description: [Impact] This is a long running bug plaguing cloud-images, where on a rare occasion resize2fs would fail and the image would not resize to fit the entire disk. Online resizes would fail due to a superblock checksum mismatch, where the superblock in memory differs from what is currently on disk due to changes made to the image. $ resize2fs /dev/nvme1n1p1 resize2fs 1.47.0 (5-Feb-2023) resize2fs: Superblock checksum does not match superblock while trying to open /dev/nvme1n1p1 Couldn't find valid filesystem superblock. Changing the read of the superblock to Direct I/O solves the issue. [Testcase] Start an c5.large instance on AWS, and attach a 60gb gp3 volume for use as a scratch disk. Run the following script, courtesy of Krister Johansen and his team: #!/usr/bin/bash set -euxo pipefail while true do parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s sleep .5 mkfs.ext4 /dev/nvme1n1p1 mount -t ext4 /dev/nvme1n1p1 /mnt stress-ng --temp-path /mnt -D 4 & STRESS_PID=$! sleep 1 growpart /dev/nvme1n1 1 resize2fs /dev/nvme1n1p1 kill $STRESS_PID wait $STRESS_PID umount /mnt wipefs -a /dev/nvme1n1p1 wipefs -a /dev/nvme1n1 done Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test If you install the test packages, the race no longer occurs. [Where problems could occur] We are changing how resize2fs reads the superblock from underlying disks. If a regression were to occur, resize2fs could fail to resize offline or online volumes. As all cloud-images are online resized during their initial boot, this could have a large impact to public and private clouds should a regression occur. [Other info] Upstream mailing list discussion: https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/ https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/ This was fixed in the below commit upstream: commit 43a498e938887956f393b5e45ea6ac79cc5f4b84 Author: Theodore Ts'o Date: Thu, 15 Jun 2023 00:17:01 -0400 Subject: resize2fs: use Direct I/O when reading the superblock for online resizes Link: https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84 The commit has not been tagged to any release. All supported Ubuntu releases require this fix, and need to be published in standard non- ESM archives to be picked up in cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036467/+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 2063443] Re: krb5.conf seems to ignore rdns = false
** Description changed: We have a scenario where we need to disable reverse lookups for canonicalization in Kerberos as the customer's PTR records are not consistent and lead to wrongly requested SPNs otherwise (see https://web.mit.edu/kerberos/krb5-latest/doc/admin/princ_dns.html#reverse- dns-mismatches) - Therfore we have set "rdns = false" in /etc/krb5.conf as follows: + Therefore we have set "rdns = false" in /etc/krb5.conf as follows: # cat /etc/krb5.conf [libdefaults] udp_preference_limit = 0 default_realm = EMEA.EXAMPLE.COM rdns = false However this setting seems to get ignored for some reason. I tried to do - some debugging and comparison as we don't have the same issue for + some debugging and comparisons as we don't have the same issue for example on a RHEL8 (using krb5-libs-1.18.2-26.el8_9.x86_64) machine. On those RHEL machines the setting seems to do exactly what it's supposed to, in fact I can reproduce the issue we have on Ubuntu on RHEL as well if I remove the "rdns = false" line from the configuration. Kerberos authentication (in our test we use a simple ldapsearch with GSSAPI auth) fails then randomly as it sometimes gets a wrong SPN due to using a wrong PTR for canonicalization. On our Ubuntu 22.04 LTS (with libkrb5-3:amd64 1.19.2-2ubuntu0.3) however - the setting does not seem to have any effect. + the setting does not seem to have any effect. I then re-did the same + test with Debian oldstable, stable and sid as well, all with the exact + same result. - I actually run a tcpdump while trying to do a Kerberos auth with the + I actually ran a tcpdump while trying to do a Kerberos auth with the "rdns = false" setting in place and I can still see the reverse lookup - being performed in the tcpdump (anonymized some things so don't get + being performed in the tcpdump (I anonymized some things so don't get confused about the IPs): 10:47:58.382684 IP 1.2.3.4.55001 > 123.123.123.123.53: 12962+ [1au] A? domaincontroller01.emea.example.com. (55) 10:47:58.382809 IP 1.2.3.4.37669 > 123.123.123.123.53: 38376+ [1au] ? domaincontroller01.emea.example.com. (55) 10:47:58.412041 IP 123.123.123.123.53 > 1.2.3.4.37669: 38376* 0/1/1 (143) - 10:47:58.412564 IP 123.123.123.123.53 > 1.2.3.4.55001: 12962* 1/9/10 A 10.145.214.16 (602) - 10:47:58.442326 IP 1.2.3.4.51232 > 123.123.123.123.53: 16995+ [1au] PTR? 16.214.145.10.in-addr.arpa. (55) + 10:47:58.412564 IP 123.123.123.123.53 > 1.2.3.4.55001: 12962* 1/9/10 A 5.6.7.8 (602) + 10:47:58.442326 IP 1.2.3.4.51232 > 123.123.123.123.53: 16995+ [1au] PTR? 8.7.6.5.in-addr.arpa. (55) 10:47:58.471669 IP 123.123.123.123.53 > 1.2.3.4.51232: 16995 2/2/3 PTR emea.example.com., PTR DOMAINCONTROLLER.emea.example.com. (238) As you see there it does the PTR lookup and retrieves two entries (emea.example.com and DOMAINCONTROLLER.emea.example.com) If I do the same test on the RHEL8 machine I can actually see in tcpdump that with the "rdns = false" setting the reverse lookup is correctly NOT performed. I am a bit puzzled why this is the case as I have not seen other people - reporting it even though in a quick test I was also able to get the same - wrong result with Debian stable. + reporting it (maybe everyone else has their reverse DNS under control + ;)) even though as said in a quick test I was also able to get the same + wrong result with multiple Debian releases and the mentioned Ubuntu + release. The only thing I've found in the past where this exact issue was - mentioned as many years ago: + mentioned was many years ago: https://mailman.mit.edu/pipermail/krb5-bugs/2011-June/008684.html However this has been fixed ever since. I have not done yet any actual code comparison with the version that RHEL uses, also I'm not sure if - the issue is even there or (as in that recent bug linked above) might - come from some glibc issue? + the issue actually really exists in libkrb5 itself or if it might be a + sideeffect from some other lib. How to reproduce on your own: Even if you don't have erroneous reverse DNS entries you could still try to reproduce it by just looking at tcpdump and checking if you see reverse lookups performed with and without the option. - - I attached the apport for libkrb5 but let me know if something else is - needed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/2063443 Title: krb5.conf seems to ignore rdns = false Status in krb5 package in Ubuntu: New Bug description: We have a scenario where we need to disable reverse lookups for canonicalization in Kerberos as the customer's PTR records are not consistent and lead to wrongly requested SPNs otherwise (see https://web.mit.edu/kerberos/krb5-latest/doc/admin/princ_dns.html#reverse- dns-mismatches) Therefore we have set "rdns = false" in
[Touch-packages] [Bug 2063443] Re: krb5.conf seems to ignore rdns = false
** No longer affects: kerberos -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/2063443 Title: krb5.conf seems to ignore rdns = false Status in krb5 package in Ubuntu: New Bug description: We have a scenario where we need to disable reverse lookups for canonicalization in Kerberos as the customer's PTR records are not consistent and lead to wrongly requested SPNs otherwise (see https://web.mit.edu/kerberos/krb5-latest/doc/admin/princ_dns.html#reverse- dns-mismatches) Therfore we have set "rdns = false" in /etc/krb5.conf as follows: # cat /etc/krb5.conf [libdefaults] udp_preference_limit = 0 default_realm = EMEA.EXAMPLE.COM rdns = false However this setting seems to get ignored for some reason. I tried to do some debugging and comparison as we don't have the same issue for example on a RHEL8 (using krb5-libs-1.18.2-26.el8_9.x86_64) machine. On those RHEL machines the setting seems to do exactly what it's supposed to, in fact I can reproduce the issue we have on Ubuntu on RHEL as well if I remove the "rdns = false" line from the configuration. Kerberos authentication (in our test we use a simple ldapsearch with GSSAPI auth) fails then randomly as it sometimes gets a wrong SPN due to using a wrong PTR for canonicalization. On our Ubuntu 22.04 LTS (with libkrb5-3:amd64 1.19.2-2ubuntu0.3) however the setting does not seem to have any effect. I actually run a tcpdump while trying to do a Kerberos auth with the "rdns = false" setting in place and I can still see the reverse lookup being performed in the tcpdump (anonymized some things so don't get confused about the IPs): 10:47:58.382684 IP 1.2.3.4.55001 > 123.123.123.123.53: 12962+ [1au] A? domaincontroller01.emea.example.com. (55) 10:47:58.382809 IP 1.2.3.4.37669 > 123.123.123.123.53: 38376+ [1au] ? domaincontroller01.emea.example.com. (55) 10:47:58.412041 IP 123.123.123.123.53 > 1.2.3.4.37669: 38376* 0/1/1 (143) 10:47:58.412564 IP 123.123.123.123.53 > 1.2.3.4.55001: 12962* 1/9/10 A 10.145.214.16 (602) 10:47:58.442326 IP 1.2.3.4.51232 > 123.123.123.123.53: 16995+ [1au] PTR? 16.214.145.10.in-addr.arpa. (55) 10:47:58.471669 IP 123.123.123.123.53 > 1.2.3.4.51232: 16995 2/2/3 PTR emea.example.com., PTR DOMAINCONTROLLER.emea.example.com. (238) As you see there it does the PTR lookup and retrieves two entries (emea.example.com and DOMAINCONTROLLER.emea.example.com) If I do the same test on the RHEL8 machine I can actually see in tcpdump that with the "rdns = false" setting the reverse lookup is correctly NOT performed. I am a bit puzzled why this is the case as I have not seen other people reporting it even though in a quick test I was also able to get the same wrong result with Debian stable. The only thing I've found in the past where this exact issue was mentioned as many years ago: https://mailman.mit.edu/pipermail/krb5-bugs/2011-June/008684.html However this has been fixed ever since. I have not done yet any actual code comparison with the version that RHEL uses, also I'm not sure if the issue is even there or (as in that recent bug linked above) might come from some glibc issue? How to reproduce on your own: Even if you don't have erroneous reverse DNS entries you could still try to reproduce it by just looking at tcpdump and checking if you see reverse lookups performed with and without the option. I attached the apport for libkrb5 but let me know if something else is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/2063443/+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 2063464] Re: Package wasn't installed on upgrade from Jammy to Noble
Sorry for the previous noise, I was on the wrong page. Can you please run apport-collect -p ubuntu-release-upgrader 2063464 so that upgrade logs are attached? ** Also affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Incomplete ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- 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/2063464 Title: Package wasn't installed on upgrade from Jammy to Noble Status in systemd package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Incomplete Bug description: I just do-release-upgraded from Jammy to Noble on a pretty minimal server. After upgrade, network was fine but DNS names could not be resolved. I discovered systemd-resolved wasn't installed. I copied and installed that package manually, which immediately resolved the problem. So I assume this is a mistake in the upgrade process. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 25 15:27:23 2024 SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063464/+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 2063464] Re: Package wasn't installed on upgrade from Jammy to Noble
-- 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/2063464 Title: Package wasn't installed on upgrade from Jammy to Noble Status in systemd package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Incomplete Bug description: I just do-release-upgraded from Jammy to Noble on a pretty minimal server. After upgrade, network was fine but DNS names could not be resolved. I discovered systemd-resolved wasn't installed. I copied and installed that package manually, which immediately resolved the problem. So I assume this is a mistake in the upgrade process. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 25 15:27:23 2024 SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063464/+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 2063257] Re: Noble: default pam config for login tries do load non-existent pam_lastlog.so
*** This bug is a duplicate of bug 2060676 *** https://bugs.launchpad.net/bugs/2060676 ** This bug has been marked a duplicate of bug 2060676 login: remove pam_lastlog.so from config -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/2063257 Title: Noble: default pam config for login tries do load non-existent pam_lastlog.so Status in shadow package in Ubuntu: New Status in shadow source package in Noble: New Status in shadow package in Debian: New Bug description: pam_lastlog.so was dropped by upstream in 1.5.3[1][4]. It's still there in the code, but not built by default. And indeed, in noble (1.5.3) we don't have it, while mantic (1.5.2) does. This does not prevent console logins, but generates an error in the logs: Apr 23 20:02:09 n1 login[835]: PAM unable to dlopen(pam_lastlog.so): /usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file or directory Apr 23 20:02:09 n1 login[835]: PAM adding faulty module: pam_lastlog.so Debian's shadow package is also still shipping this config[2]. If you think we should re-enable pam_lastlog, then this becomes a bug in the src:pam package, but keep in mind upstream is keen on removing it, and we might be better off switching to an alternative, perhaps pam_lastlog2[3]. 1. https://github.com/linux-pam/linux-pam/blob/cec36a8cd2c69cc87eacc21da471334fbef128ee/NEWS#L65 2. https://salsa.debian.org/debian/shadow/-/blob/master/debian/login.pam?ref_type=heads#L82 3. https://wiki.debian.org/PamLastlog2 4. https://github.com/linux-pam/linux-pam/commit/357a4ddbe9b4b10ebd805d2af3e32f3ead5b8816 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2063257/+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 2063349] Re: systemd-coredump handler does not forward the crash to the container
** Changed in: apport Importance: Undecided => Medium ** Changed in: apport Status: New => In Progress ** Changed in: apport (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2063349 Title: systemd-coredump handler does not forward the crash to the container Status in Apport: In Progress Status in apport package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. install systemd-coredump on the host 2. open a shell on a noble container 2.1 machinectl pull-raw "http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img; noble 2.2 machinectl start noble 2.3 machinectl shell noble 3. install chaos-marmosets inside the container (# apt install chaos-marmosets) 4. generate a crash inside the container (# divide-by-zero) Observed behaviour: The .crash file is present on the host /var/crash Expected behaviour: The .crash file should be present inside the container /var/crash Note: Here is how you can enable Host Network on the container https://wiki.archlinux.org/title/systemd-nspawn#Use_host_networking ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: apport 2.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportLog: INFO: apport (pid 126611) 2024-04-24 16:34:39,226: executable: /usr/bin/divide-by-zero (command line "divide-by-zero") INFO: apport (pid 126611) 2024-04-24 16:34:39,664: wrote report /var/crash/_usr_bin_divide-by-zero.1000.crash INFO: apport (pid 127435) 2024-04-24 16:41:16,322: executable: /usr/bin/divide-by-zero (command line "divide-by-zero") INFO: apport (pid 127435) 2024-04-24 16:41:16,758: wrote report /var/crash/_usr_bin_divide-by-zero.297664512.crash ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 17:03:02 2024 InstallationDate: Installed on 2024-04-18 (6 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240418) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2063349/+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 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 I confirm fixing of the issue with sudo apt install systemd-resolved after broken update from 22.04 -- 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/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to the end of the upgrade, I got an „Oh, no! Something has gone wrong and the system cannot recover. Call the system administrator” message after a red FAILED in the terminal. The system administrator is myself, because my computer is a personal one. Hard reset, same error, Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the update with dpkg. While dpkg was upgrading, it printed an error message for every WiFi connection: „[Failed] Failed to migrate [I do not remember, something with /etc/netplan]” It took at least one and a half hour to find the solution on Ask Ubuntu. The problem was: /etc/resolv.conf became a broken link, along with systemd-resolve.service. I needed to remove both of them and write a new resolv.conf to fix the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 08:21:02 2024 InstallationDate: Installed on 2023-07-05 (236 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) IpRoute: default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.45.90 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+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 2063484] Re: Other Software now displays the Suites instead of the Comments
** Attachment added: "with-comment-result.png" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2063484/+attachment/5770432/+files/with-comment-result.png ** Description changed: Since updating from Ubuntu 24.04 (from 23.10), software-properties-gtk shows the wrong field in the UI for Other Software. Where it should show the Comment field, it shows the Suites field. It only does it if there is a value in Comment though. For instance, imagine I have Inkscape PPA as a software source, with the Suites “hirsute” and the Comment “Inkscape”. In the UI, it will show “hirsute” instead of “Inkscape” as a title like it used to do. If I empty the Comment field, it does remove the title and “hirsute” is not displayed. One more thing from the upgrade: all the Comment fields’ content got lost in the process. So I have no some sources that I can’t remember why I had installed, even though I have software coming from them, which I had indicated in Comment. + + This has been working well for the past 10-15 years, so it’s definitely + a mistake that has been introduced with the new version. The field edit + dialogue has changed a little bit, so I’m guessing that change + introduced the bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2063484 Title: Other Software now displays the Suites instead of the Comments Status in software-properties package in Ubuntu: New Bug description: Since updating from Ubuntu 24.04 (from 23.10), software-properties-gtk shows the wrong field in the UI for Other Software. Where it should show the Comment field, it shows the Suites field. It only does it if there is a value in Comment though. For instance, imagine I have Inkscape PPA as a software source, with the Suites “hirsute” and the Comment “Inkscape”. In the UI, it will show “hirsute” instead of “Inkscape” as a title like it used to do. If I empty the Comment field, it does remove the title and “hirsute” is not displayed. One more thing from the upgrade: all the Comment fields’ content got lost in the process. So I have no some sources that I can’t remember why I had installed, even though I have software coming from them, which I had indicated in Comment. This has been working well for the past 10-15 years, so it’s definitely a mistake that has been introduced with the new version. The field edit dialogue has changed a little bit, so I’m guessing that change introduced the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2063484/+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 2063484] Re: Other Software now displays the Suites instead of the Comments
** Attachment added: "without-comment-result.png" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2063484/+attachment/5770430/+files/without-comment-result.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2063484 Title: Other Software now displays the Suites instead of the Comments Status in software-properties package in Ubuntu: New Bug description: Since updating from Ubuntu 24.04 (from 23.10), software-properties-gtk shows the wrong field in the UI for Other Software. Where it should show the Comment field, it shows the Suites field. It only does it if there is a value in Comment though. For instance, imagine I have Inkscape PPA as a software source, with the Suites “hirsute” and the Comment “Inkscape”. In the UI, it will show “hirsute” instead of “Inkscape” as a title like it used to do. If I empty the Comment field, it does remove the title and “hirsute” is not displayed. One more thing from the upgrade: all the Comment fields’ content got lost in the process. So I have no some sources that I can’t remember why I had installed, even though I have software coming from them, which I had indicated in Comment. This has been working well for the past 10-15 years, so it’s definitely a mistake that has been introduced with the new version. The field edit dialogue has changed a little bit, so I’m guessing that change introduced the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2063484/+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 2063484] Re: Other Software now displays the Suites instead of the Comments
** Attachment added: "with-comment.png" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2063484/+attachment/5770431/+files/with-comment.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2063484 Title: Other Software now displays the Suites instead of the Comments Status in software-properties package in Ubuntu: New Bug description: Since updating from Ubuntu 24.04 (from 23.10), software-properties-gtk shows the wrong field in the UI for Other Software. Where it should show the Comment field, it shows the Suites field. It only does it if there is a value in Comment though. For instance, imagine I have Inkscape PPA as a software source, with the Suites “hirsute” and the Comment “Inkscape”. In the UI, it will show “hirsute” instead of “Inkscape” as a title like it used to do. If I empty the Comment field, it does remove the title and “hirsute” is not displayed. One more thing from the upgrade: all the Comment fields’ content got lost in the process. So I have no some sources that I can’t remember why I had installed, even though I have software coming from them, which I had indicated in Comment. This has been working well for the past 10-15 years, so it’s definitely a mistake that has been introduced with the new version. The field edit dialogue has changed a little bit, so I’m guessing that change introduced the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2063484/+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 2063484] Re: Other Software now displays the Suites instead of the Comments
** Attachment added: "without-comment.png" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2063484/+attachment/5770409/+files/without-comment.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2063484 Title: Other Software now displays the Suites instead of the Comments Status in software-properties package in Ubuntu: New Bug description: Since updating from Ubuntu 24.04 (from 23.10), software-properties-gtk shows the wrong field in the UI for Other Software. Where it should show the Comment field, it shows the Suites field. It only does it if there is a value in Comment though. For instance, imagine I have Inkscape PPA as a software source, with the Suites “hirsute” and the Comment “Inkscape”. In the UI, it will show “hirsute” instead of “Inkscape” as a title like it used to do. If I empty the Comment field, it does remove the title and “hirsute” is not displayed. One more thing from the upgrade: all the Comment fields’ content got lost in the process. So I have no some sources that I can’t remember why I had installed, even though I have software coming from them, which I had indicated in Comment. This has been working well for the past 10-15 years, so it’s definitely a mistake that has been introduced with the new version. The field edit dialogue has changed a little bit, so I’m guessing that change introduced the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2063484/+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 2063484] [NEW] Other Software now displays the Suites instead of the Comments
Public bug reported: Since updating from Ubuntu 24.04 (from 23.10), software-properties-gtk shows the wrong field in the UI for Other Software. Where it should show the Comment field, it shows the Suites field. It only does it if there is a value in Comment though. For instance, imagine I have Inkscape PPA as a software source, with the Suites “hirsute” and the Comment “Inkscape”. In the UI, it will show “hirsute” instead of “Inkscape” as a title like it used to do. If I empty the Comment field, it does remove the title and “hirsute” is not displayed. One more thing from the upgrade: all the Comment fields’ content got lost in the process. So I have no some sources that I can’t remember why I had installed, even though I have software coming from them, which I had indicated in Comment. This has been working well for the past 10-15 years, so it’s definitely a mistake that has been introduced with the new version. The field edit dialogue has changed a little bit, so I’m guessing that change introduced the bug. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2063484 Title: Other Software now displays the Suites instead of the Comments Status in software-properties package in Ubuntu: New Bug description: Since updating from Ubuntu 24.04 (from 23.10), software-properties-gtk shows the wrong field in the UI for Other Software. Where it should show the Comment field, it shows the Suites field. It only does it if there is a value in Comment though. For instance, imagine I have Inkscape PPA as a software source, with the Suites “hirsute” and the Comment “Inkscape”. In the UI, it will show “hirsute” instead of “Inkscape” as a title like it used to do. If I empty the Comment field, it does remove the title and “hirsute” is not displayed. One more thing from the upgrade: all the Comment fields’ content got lost in the process. So I have no some sources that I can’t remember why I had installed, even though I have software coming from them, which I had indicated in Comment. This has been working well for the past 10-15 years, so it’s definitely a mistake that has been introduced with the new version. The field edit dialogue has changed a little bit, so I’m guessing that change introduced the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2063484/+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 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 Same issue upgrading from 22.04 to 24.04, confirmed the fix of `sudo apt install systemd-resolved` fixes the issue. Had a crash partway through the upgrade where I was left with the UI showing "something went wrong", which was partially fixed by dropping into a terminal and commadning `sudo dpkg --configure -a`, but it was left in this state afterwards. -- 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/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to the end of the upgrade, I got an „Oh, no! Something has gone wrong and the system cannot recover. Call the system administrator” message after a red FAILED in the terminal. The system administrator is myself, because my computer is a personal one. Hard reset, same error, Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the update with dpkg. While dpkg was upgrading, it printed an error message for every WiFi connection: „[Failed] Failed to migrate [I do not remember, something with /etc/netplan]” It took at least one and a half hour to find the solution on Ask Ubuntu. The problem was: /etc/resolv.conf became a broken link, along with systemd-resolve.service. I needed to remove both of them and write a new resolv.conf to fix the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 08:21:02 2024 InstallationDate: Installed on 2023-07-05 (236 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) IpRoute: default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.45.90 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+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 2039294] Re: apparmor docker
To make this generic so that it will work on older and newer hosts we should probably change the peer expression to signal (receive) peer={runc,unconfined}, or possibly, define an @{runc} variable in the preamble and use that. This really only is advantageous, in that it shows semantic intent, if if using the value of unconfined, or if @[runc} is used multiple times within the profile. @{runc}={peer,unconfined} signal (receive) peer=@{runc}, -- 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/2039294 Title: apparmor docker Status in docker: New Status in apparmor package in Ubuntu: Incomplete Bug description: No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 23.10 Release:23.10 Codename: mantic Docker version 24.0.5, build 24.0.5-0ubuntu1 Graceful shutdown doesn't work anymore due to SIGTERM and SIGKILL (maybe all signals?) doesn't reach the target process. Works when apparmor is uninstalled. [17990.085295] audit: type=1400 audit(1697213244.019:981): apparmor="DENIED" operation="signal" class="signal" profile="docker-default" pid=172626 comm="runc" requested_mask="receive" denied_mask="receive" signal=term peer="/usr/sbin/runc" [17992.112517] audit: type=1400 audit(1697213246.043:982): apparmor="DENIED" operation="signal" class="signal" profile="docker-default" pid=172633 comm="runc" requested_mask="receive" denied_mask="receive" signal=kill peer="/usr/sbin/runc" To manage notifications about this bug go to: https://bugs.launchpad.net/docker/+bug/2039294/+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 2063464] [NEW] Package wasn't installed on upgrade from Jammy to Noble
Public bug reported: I just do-release-upgraded from Jammy to Noble on a pretty minimal server. After upgrade, network was fine but DNS names could not be resolved. I discovered systemd-resolved wasn't installed. I copied and installed that package manually, which immediately resolved the problem. So I assume this is a mistake in the upgrade process. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 25 15:27:23 2024 SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- 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/2063464 Title: Package wasn't installed on upgrade from Jammy to Noble Status in systemd package in Ubuntu: New Bug description: I just do-release-upgraded from Jammy to Noble on a pretty minimal server. After upgrade, network was fine but DNS names could not be resolved. I discovered systemd-resolved wasn't installed. I copied and installed that package manually, which immediately resolved the problem. So I assume this is a mistake in the upgrade process. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 25 15:27:23 2024 SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063464/+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 2043597] Re: Kernal-sound: [950QED, Realtek ALC298, Speaker, Internal] Pulseaudio fails to detect card
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/2043597 Title: Kernal-sound: [950QED, Realtek ALC298, Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Confirmed Bug description: The input and output audio does not work for my system and I cannot find a kernel to install to fix this issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:jacques1494 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Nov 15 10:47:30 2023 InstallationDate: Installed on 2022-11-22 (358 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Speaker, Internal Title: [950QED, Realtek ALC298, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P07AKK.620.220407.SH dmi.board.asset.tag: No Asset Tag dmi.board.name: NP950QED-KB1US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLB182A1Z-C01-G002-S0001+10.0.22000 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP07AKK.620.220407.SH:bd04/07/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950QED:pvrP07AKK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP950QED-KB1US:rvrSGLB182A1Z-C01-G002-S0001+10.0.22000:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PAKK: dmi.product.family: Galaxy Book2 Pro 360 dmi.product.name: 950QED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PAKK dmi.product.version: P07AKK dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2043597/+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 2063369] Re: e2image reports invalid argument when used with big partitions
If the file system has a limit on the size of the file (for example, ext4 has a maximum file size of 16TB), then when you do a relative seek via llseek(fd, offset, SEEK_CURR), the system call will return EINVAL. This is what is causing the error. If you want to create a raw image of a very large file system, you'll either to write it to a block device which is sufficiently large, or you'll have to make sure the destination file system can support a file size of that particular length. (And, of course, has sufficient free space to hold the raw image in the first place.) Another workaround is to compress the file, e.g., "e2image -pr /dev/md3 - | gzip > md3.e2i.gz" -- 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/2063369 Title: e2image reports invalid argument when used with big partitions Status in e2fsprogs package in Ubuntu: New Bug description: It seems e2image is unable to work correctly with large filesystems. I get the following error with etx4 on top of 48TB RAID5 array. # e2image -pr /dev/md3 md3.e2i e2image 1.46.5 (30-Dec-2021) Scanning inodes... Copying 802818 / 1547571 blocks (52%) 00:02:21 remaining at 20.50 MB/sseek_relative: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2063369/+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 2063349] Re: systemd-coredump handler does not forward the crash to the container
Apport cannot do anything useful with these crash reports, because the information about the crashed process does not contain the process number seen from inside the container and because the crashed process is already gone when Apport gets the crash from systemd-coredump. So let Apport just ignore crash reports from systemd-coredump if the crashes happened inside containers: https://github.com/canonical/apport/pull/326 ** Also affects: apport Importance: Undecided Status: New ** Changed in: apport Milestone: None => 2.29.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2063349 Title: systemd-coredump handler does not forward the crash to the container Status in Apport: New Status in apport package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. install systemd-coredump on the host 2. open a shell on a noble container 2.1 machinectl pull-raw "http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img; noble 2.2 machinectl start noble 2.3 machinectl shell noble 3. install chaos-marmosets inside the container (# apt install chaos-marmosets) 4. generate a crash inside the container (# divide-by-zero) Observed behaviour: The .crash file is present on the host /var/crash Expected behaviour: The .crash file should be present inside the container /var/crash Note: Here is how you can enable Host Network on the container https://wiki.archlinux.org/title/systemd-nspawn#Use_host_networking ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: apport 2.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportLog: INFO: apport (pid 126611) 2024-04-24 16:34:39,226: executable: /usr/bin/divide-by-zero (command line "divide-by-zero") INFO: apport (pid 126611) 2024-04-24 16:34:39,664: wrote report /var/crash/_usr_bin_divide-by-zero.1000.crash INFO: apport (pid 127435) 2024-04-24 16:41:16,322: executable: /usr/bin/divide-by-zero (command line "divide-by-zero") INFO: apport (pid 127435) 2024-04-24 16:41:16,758: wrote report /var/crash/_usr_bin_divide-by-zero.297664512.crash ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 17:03:02 2024 InstallationDate: Installed on 2024-04-18 (6 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240418) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2063349/+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 2063381] Re: NFS Client can't mount via NFS version 4.0
Ryan, I think you are experiencing https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2059197 which is a regression on focal from a previous update that also tried to address the version negotiation. There is a new nfs-utils package in focal-proposed to address that, would you mind trying it out? The instructions are in that bug. ** Package changed: util-linux (Ubuntu) => nfs-utils (Ubuntu) ** Changed in: nfs-utils (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2063381 Title: NFS Client can't mount via NFS version 4.0 Status in nfs-utils package in Ubuntu: Incomplete Bug description: When specifying vers=4.0 or nfsvers=4.0 in NFSv4 mount options, the client ends up using version 4.2 instead. This option seems to be ignored. This happens with pam_mount and manual mount. We have been using pam_mount for years with the option vers=4.0, but now it appears to be broken. Just recently noticed this is happening while troubleshooting root causes of some other issues on our servers. Test: mounting manually with option: minorversion=0, the client does not mount, no errors are seen with -vvv, no errors in logs either, it just fails silently. With pam_mount this option fails as well but is logged as mount failed into auth.log ex: Apr 24 17:15:22 servername sshd[666278]: (pam_mount.c:522): mount of /mnt/nfs/home/admin_username failed other nfs4 mount options we are using: sec=krb5p,noatime,nodiratime,async I see that something similar was fixed in autofs, but this is not autofs related, as we do not use it. https://bugs.launchpad.net/bugs/1818121 Found a similar [oracle] issue but cannot read it= https://support.oracle.com/knowledge/Oracle%20Linux%20and%20Virtualization/2528012_1.html --- Description:Ubuntu 20.04.6 LTS Release:20.04 --- util-linux: Installed: 2.34-0.1ubuntu9.6 Candidate: 2.34-0.1ubuntu9.6 Version table: *** 2.34-0.1ubuntu9.6 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.34-0.1ubuntu9 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages mount: Installed: 2.34-0.1ubuntu9.6 Candidate: 2.34-0.1ubuntu9.6 Version table: *** 2.34-0.1ubuntu9.6 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.34-0.1ubuntu9 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages nfs-common: Installed: 1:1.3.4-2.5ubuntu3.6 Candidate: 1:1.3.4-2.5ubuntu3.6 Version table: *** 1:1.3.4-2.5ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:1.3.4-2.5ubuntu3.3 500 500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:1.3.4-2.5ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2063381/+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 2063452] [NEW] Xorg freeze
Public bug reported: My Ubuntu system crashes every time I use an application. It freezes, and I have to force the system to shut down in order to restart it for use, but the problem persists.Please help me ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 13:40:11 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a68] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TigerLake-H GT1 [UHD Graphics] [1462:12eb] Subsystem: Micro-Star International Co., Ltd. [MSI] GA107M [GeForce RTX 3050 Mobile] [1462:12eb] InstallationDate: Installed on 2023-12-01 (145 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Micro-Star International Co., Ltd. Katana GF76 11UC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic root=UUID=0cd75e64-7400-4f1e-bbce-c9c2c1a67e8a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2021 dmi.bios.release: 3.14 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E17L2IMS.30E dmi.board.asset.tag: Default string dmi.board.name: MS-17L2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE17L2IMS.30E:bd10/15/2021:br3.14:svnMicro-StarInternationalCo.,Ltd.:pnKatanaGF7611UC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17L2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17L2.3: dmi.product.family: GF dmi.product.name: Katana GF76 11UC dmi.product.sku: 17L2.3 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze jammy ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2063452 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: My Ubuntu system crashes every time I use an application. It freezes, and I have to force the system to shut down in order to restart it for use, but the problem persists.Please help me ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 13:40:11 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a68] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TigerLake-H GT1 [UHD Graphics] [1462:12eb] Subsystem: Micro-Star International Co., Ltd. [MSI] GA107M [GeForce RTX 3050 Mobile] [1462:12eb] InstallationDate: Installed on 2023-12-01 (145 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Micro-Star International Co., Ltd. Katana GF76 11UC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic
[Touch-packages] [Bug 2063443] Re: krb5.conf seems to ignore rdns = false
** Description changed: We have a scenario where we need to disable reverse lookups for canonicalization in Kerberos as the customer's PTR records are not - consistent and lead to wrongly requested SPNs otherwise. + consistent and lead to wrongly requested SPNs otherwise (see + https://web.mit.edu/kerberos/krb5-latest/doc/admin/princ_dns.html#reverse- + dns-mismatches) Therfore we have set "rdns = false" in /etc/krb5.conf as follows: # cat /etc/krb5.conf [libdefaults] udp_preference_limit = 0 default_realm = EMEA.EXAMPLE.COM rdns = false However this setting seems to get ignored for some reason. I tried to do some debugging and comparison as we don't have the same issue for example on a RHEL8 (using krb5-libs-1.18.2-26.el8_9.x86_64) machine. On those RHEL machines the setting seems to do exactly what it's supposed to, in fact I can reproduce the issue we have on Ubuntu on RHEL as well if I remove the "rdns = false" line from the configuration. Kerberos authentication (in our test we use a simple ldapsearch with GSSAPI auth) fails then randomly as it sometimes gets a wrong SPN due to using a wrong PTR for canonicalization. On our Ubuntu 22.04 LTS (with libkrb5-3:amd64 1.19.2-2ubuntu0.3) however the setting does not seem to have any effect. I actually run a tcpdump while trying to do a Kerberos auth with the "rdns = false" setting in place and I can still see the reverse lookup being performed in the tcpdump (anonymized some things so don't get confused about the IPs): 10:47:58.382684 IP 1.2.3.4.55001 > 123.123.123.123.53: 12962+ [1au] A? domaincontroller01.emea.example.com. (55) 10:47:58.382809 IP 1.2.3.4.37669 > 123.123.123.123.53: 38376+ [1au] ? domaincontroller01.emea.example.com. (55) 10:47:58.412041 IP 123.123.123.123.53 > 1.2.3.4.37669: 38376* 0/1/1 (143) 10:47:58.412564 IP 123.123.123.123.53 > 1.2.3.4.55001: 12962* 1/9/10 A 10.145.214.16 (602) 10:47:58.442326 IP 1.2.3.4.51232 > 123.123.123.123.53: 16995+ [1au] PTR? 16.214.145.10.in-addr.arpa. (55) 10:47:58.471669 IP 123.123.123.123.53 > 1.2.3.4.51232: 16995 2/2/3 PTR emea.example.com., PTR DOMAINCONTROLLER.emea.example.com. (238) - - As you see there it does the PTR lookup and retrieves two entries (emea.example.com and DOMAINCONTROLLER.emea.example.com) + As you see there it does the PTR lookup and retrieves two entries + (emea.example.com and DOMAINCONTROLLER.emea.example.com) If I do the same test on the RHEL8 machine I can actually see in tcpdump that with the "rdns = false" setting the reverse lookup is correctly NOT performed. I am a bit puzzled why this is the case as I have not seen other people reporting it even though in a quick test I was also able to get the same wrong result with Debian stable. The only thing I've found in the past where this exact issue was mentioned as many years ago: https://mailman.mit.edu/pipermail/krb5-bugs/2011-June/008684.html However this has been fixed ever since. I have not done yet any actual code comparison with the version that RHEL uses, also I'm not sure if the issue is even there or (as in that recent bug linked above) might come from some glibc issue? How to reproduce on your own: Even if you don't have erroneous reverse DNS entries you could still try to reproduce it by just looking at tcpdump and checking if you see reverse lookups performed with and without the option. I attached the apport for libkrb5 but let me know if something else is needed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/2063443 Title: krb5.conf seems to ignore rdns = false Status in Kerberos: New Status in krb5 package in Ubuntu: New Bug description: We have a scenario where we need to disable reverse lookups for canonicalization in Kerberos as the customer's PTR records are not consistent and lead to wrongly requested SPNs otherwise (see https://web.mit.edu/kerberos/krb5-latest/doc/admin/princ_dns.html#reverse- dns-mismatches) Therfore we have set "rdns = false" in /etc/krb5.conf as follows: # cat /etc/krb5.conf [libdefaults] udp_preference_limit = 0 default_realm = EMEA.EXAMPLE.COM rdns = false However this setting seems to get ignored for some reason. I tried to do some debugging and comparison as we don't have the same issue for example on a RHEL8 (using krb5-libs-1.18.2-26.el8_9.x86_64) machine. On those RHEL machines the setting seems to do exactly what it's supposed to, in fact I can reproduce the issue we have on Ubuntu on RHEL as well if I remove the "rdns = false" line from the configuration. Kerberos authentication (in our test we use a simple ldapsearch with GSSAPI auth) fails then randomly as it sometimes gets a wrong SPN due to using a wrong PTR for canonicalization. On our Ubuntu
[Touch-packages] [Bug 2063443] Re: krb5.conf seems to ignore rdns = false
** Project changed: launchpad => kerberos ** Also affects: krb5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/2063443 Title: krb5.conf seems to ignore rdns = false Status in Kerberos: New Status in krb5 package in Ubuntu: New Bug description: We have a scenario where we need to disable reverse lookups for canonicalization in Kerberos as the customer's PTR records are not consistent and lead to wrongly requested SPNs otherwise. Therfore we have set "rdns = false" in /etc/krb5.conf as follows: # cat /etc/krb5.conf [libdefaults] udp_preference_limit = 0 default_realm = EMEA.EXAMPLE.COM rdns = false However this setting seems to get ignored for some reason. I tried to do some debugging and comparison as we don't have the same issue for example on a RHEL8 (using krb5-libs-1.18.2-26.el8_9.x86_64) machine. On those RHEL machines the setting seems to do exactly what it's supposed to, in fact I can reproduce the issue we have on Ubuntu on RHEL as well if I remove the "rdns = false" line from the configuration. Kerberos authentication (in our test we use a simple ldapsearch with GSSAPI auth) fails then randomly as it sometimes gets a wrong SPN due to using a wrong PTR for canonicalization. On our Ubuntu 22.04 LTS (with libkrb5-3:amd64 1.19.2-2ubuntu0.3) however the setting does not seem to have any effect. I actually run a tcpdump while trying to do a Kerberos auth with the "rdns = false" setting in place and I can still see the reverse lookup being performed in the tcpdump (anonymized some things so don't get confused about the IPs): 10:47:58.382684 IP 1.2.3.4.55001 > 123.123.123.123.53: 12962+ [1au] A? domaincontroller01.emea.example.com. (55) 10:47:58.382809 IP 1.2.3.4.37669 > 123.123.123.123.53: 38376+ [1au] ? domaincontroller01.emea.example.com. (55) 10:47:58.412041 IP 123.123.123.123.53 > 1.2.3.4.37669: 38376* 0/1/1 (143) 10:47:58.412564 IP 123.123.123.123.53 > 1.2.3.4.55001: 12962* 1/9/10 A 10.145.214.16 (602) 10:47:58.442326 IP 1.2.3.4.51232 > 123.123.123.123.53: 16995+ [1au] PTR? 16.214.145.10.in-addr.arpa. (55) 10:47:58.471669 IP 123.123.123.123.53 > 1.2.3.4.51232: 16995 2/2/3 PTR emea.example.com., PTR DOMAINCONTROLLER.emea.example.com. (238) As you see there it does the PTR lookup and retrieves two entries (emea.example.com and DOMAINCONTROLLER.emea.example.com) If I do the same test on the RHEL8 machine I can actually see in tcpdump that with the "rdns = false" setting the reverse lookup is correctly NOT performed. I am a bit puzzled why this is the case as I have not seen other people reporting it even though in a quick test I was also able to get the same wrong result with Debian stable. The only thing I've found in the past where this exact issue was mentioned as many years ago: https://mailman.mit.edu/pipermail/krb5-bugs/2011-June/008684.html However this has been fixed ever since. I have not done yet any actual code comparison with the version that RHEL uses, also I'm not sure if the issue is even there or (as in that recent bug linked above) might come from some glibc issue? How to reproduce on your own: Even if you don't have erroneous reverse DNS entries you could still try to reproduce it by just looking at tcpdump and checking if you see reverse lookups performed with and without the option. I attached the apport for libkrb5 but let me know if something else is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/kerberos/+bug/2063443/+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 2063438] [NEW] click fails to install in Noble
Public bug reported: click fails to install on Noble - 24.04 Setting up python3-click-package (0.5.2-2ubuntu4) ... Setting up click (0.5.2-2ubuntu4) ... Failed to preset unit, unit click-user-hooks.service does not exist. /usr/bin/deb-systemd-helper: error: systemctl preset failed on click-user-hooks.service: No such file or directory Traceback (most recent call last): File "/usr/bin/click", line 110, in sys.exit(main()) ^^ File "/usr/bin/click", line 85, in main %s""") % commands.help_text()) File "/usr/lib/python3/dist-packages/click_package/commands/__init__.py", line 54, in help_text mod = load_command(command) ^ File "/usr/lib/python3/dist-packages/click_package/commands/__init__.py", line 46, in load_command return importlib.import_module("click_package.commands.%s" % command) ^^ File "/usr/lib/python3.12/importlib/__init__.py", line 90, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1387, in _gcd_import File "", line 1360, in _find_and_load File "", line 1331, in _find_and_load_unlocked File "", line 935, in _load_unlocked File "", line 995, in exec_module File "", line 488, in _call_with_frames_removed File "/usr/lib/python3/dist-packages/click_package/commands/build.py", line 28, in from click_package.build import ClickBuildError, ClickBuilder File "/usr/lib/python3/dist-packages/click_package/build.py", line 53, in from click_package.framework import ( File "/usr/lib/python3/dist-packages/click_package/framework.py", line 27, in import click_package.paths File "/usr/lib/python3/dist-packages/click_package/paths.py", line 18, in __multiarch = subprocess.run(['dpkg-architecture', '-q', 'DEB_HOST_MULTIARCH'], capture_output=True, check=True).stdout ^^ File "/usr/lib/python3.12/subprocess.py", line 548, in run with Popen(*popenargs, **kwargs) as process: ^^^ File "/usr/lib/python3.12/subprocess.py", line 1026, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.12/subprocess.py", line 1955, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'dpkg-architecture' dpkg: error processing package click (--configure): installed click package post-installation script subprocess returned error exit status 1 Processing triggers for man-db (2.12.0-4build2) ... Processing triggers for shared-mime-info (2.4-4) ... Processing triggers for libc-bin (2.39-0ubuntu8) ... Errors were encountered while processing: click E: Sub-process /usr/bin/dpkg returned an error code (1) ** Affects: click (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/2063438 Title: click fails to install in Noble Status in click package in Ubuntu: New Bug description: click fails to install on Noble - 24.04 Setting up python3-click-package (0.5.2-2ubuntu4) ... Setting up click (0.5.2-2ubuntu4) ... Failed to preset unit, unit click-user-hooks.service does not exist. /usr/bin/deb-systemd-helper: error: systemctl preset failed on click-user-hooks.service: No such file or directory Traceback (most recent call last): File "/usr/bin/click", line 110, in sys.exit(main()) ^^ File "/usr/bin/click", line 85, in main %s""") % commands.help_text()) File "/usr/lib/python3/dist-packages/click_package/commands/__init__.py", line 54, in help_text mod = load_command(command) ^ File "/usr/lib/python3/dist-packages/click_package/commands/__init__.py", line 46, in load_command return importlib.import_module("click_package.commands.%s" % command) ^^ File "/usr/lib/python3.12/importlib/__init__.py", line 90, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1387, in _gcd_import File "", line 1360, in _find_and_load File "", line 1331, in _find_and_load_unlocked File "", line 935, in _load_unlocked File "", line 995, in exec_module File "", line 488, in _call_with_frames_removed File "/usr/lib/python3/dist-packages/click_package/commands/build.py", line 28, in from click_package.build import
[Touch-packages] [Bug 2063332] Re: Multiple problems Ubuntu 24.04 with Qt5
Thank you for you answer. It is most definitely a regression in Ubuntu 24.04. I have just tested Ubuntu 22.04 on Wayland, the same Qt5 apps and all is working - keyboard shortcuts - window controls are on the left - window titlebar doubleclick to maximize Not sure if it's Wayland, Qt5 or something else When I try your suggestion with qgnomeplatform-qt5 then: - window controls are on the left [OK] - window titlebar doubleclick also works as expected [OK] - fullscreen window state is remembered and restored properly [OK] - keyboard shortcuts still do not work properly [ERR] Anything else I should try? But obviously the behavior is different from Ubuntu 22.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/2063332 Title: Multiple problems Ubuntu 24.04 with Qt5 Status in qtbase-opensource-src package in Ubuntu: New Bug description: After the upgrade to the 24.04 beta Qt5 UI is not at its best. Please, notice that all this functionality is working on 22.04. 1. Windows controls settings from Gnome are not applied When you set the Windows Title bar buttons to Placement Left, then Qt apps ignore this setting. The default gt4 apps behave properly and place the buttons to the left. 2. Windows actions like double click to maximize from settings also do not with in the Qt5 apps unlike in gt4 apps. 3. Several keyboard shortcuts are passed differently to Qt5 apps. The key "Ctrl+Period" is not passed to the qt app at all The key "Ctrl+~" is passed as "Ctrl+0" The key "Shift+Alt+F7" is also not working This means some different handling is applied in Qt5 apps 4. If you use the env var "export QT_QPA_PLATFORM=xcb" and start the Qt5 app, then it all works properly. The windows controls are on the right side, you can use double click the title bar to maximize and also the shortcuts are working fine. However, in such scenario no app starts fullscreen. It starts in a positioned window (the position is remembered) instead even if you maximized the window before you exited it. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libqt5core5t64 5.15.13+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1 Uname: Linux 6.8.0-28-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 14:20:24 2024 InstallationDate: Installed on 2020-05-12 (1443 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: qtbase-opensource-src UpgradeStatus: Upgraded to noble on 2024-04-20 (4 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-04-19T01:50:32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/2063332/+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 2061726] Re: rsyslog apparmor denial on reading /proc/sys/net/ipv6/conf/all/disable_ipv6
** Tags removed: rls-nn-incoming ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2061726 Title: rsyslog apparmor denial on reading /proc/sys/net/ipv6/conf/all/disable_ipv6 Status in apparmor package in Ubuntu: New Status in rsyslog package in Ubuntu: New Bug description: One of our Cockpit integration tests [1] spotted an AppArmor regression in rsyslogd. This is coincidental, the test passes and it doesn't do anything with rsyslogd -- just something happens to happen in the background to trigger this (and I can actually reproduce it locally quite reliably). Mar 08 10:48:20 m1.cockpit.lan systemd[1]: dpkg-db-backup.service: Deactivated successfully. Mar 08 10:48:20 m1.cockpit.lan systemd[1]: Finished dpkg-db-backup.service - Daily dpkg database backup service. Mar 08 10:48:20 m1.cockpit.lan systemd[1]: rsyslog.service: Sent signal SIGHUP to main process 752 (rsyslogd) on client request. Mar 08 10:48:20 m1.cockpit.lan kernel: audit: type=1400 audit(1615200500.418:125): apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=752 comm="rsyslogd" requested_mask="r" denied_mask="r" fsuid=102 ouid=0 Mar 08 10:48:20 m1.cockpit.lan kernel: audit: type=1400 audit(1615200500.418:126): apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=752 comm="rsyslogd" requested_mask="r" denied_mask="r" fsuid=102 ouid=0 This happens on current Ubuntu 24.04 LTS noble devel, rsyslog 8.2312.0-3ubuntu8 and apparmor 4.0.0-beta3-0ubuntu3. [1] https://cockpit-logs.us-east-1.linodeobjects.com/pull-20317-ce39e07e-20240415-204952-ubuntu-stable-other/log.html#152 [2] https://cockpit-logs.us-east-1.linodeobjects.com/pull-20317-ce39e07e-20240415-204952-ubuntu-stable-other/TestHistoryMetrics-testEvents-ubuntu-stable-127.0.0.2-2901-FAIL.log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2061726/+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 1977986] Re: UPower and battery indicator show update in 2 minutes when connecting power cable ThinkPad
** Tags added: originate-from-2063092 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1977986 Title: UPower and battery indicator show update in 2 minutes when connecting power cable ThinkPad Status in OEM Priority Project: In Progress Status in upower package in Ubuntu: New Bug description: We found this issue on several ThinkPad. The upower will change 'pending-charge' to 'charging' after 2 minutes later, but the /sys/class/power_supply/BAT0/status changes to 'Charging' immediately when connecting the power cable. $ upower -i /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: Sunwoda model:5B10W13975 serial: 34226 power supply: yes updated: Wed 08 Jun 2022 11:42:02 PM CST (1 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 55.94 Wh energy-empty:0 Wh energy-full: 57 Wh energy-full-design: 57 Wh energy-rate: 5.79 W voltage: 16.688 V percentage: 98% capacity:100% technology: lithium-polymer icon-name: 'battery-full-charging-symbolic' History (charge): 1654702882 98.000 pending-charge 1654702863 97.000 pending-charge History (rate): 1654702863 5.790 pending-charge 1654702863 6.171 pending-charge $ cat /sys/class/power_supply/BAT0/status Charging To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1977986/+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 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs
Hi Matthew, It's been a couple months. We'd really love to get the fix for Focal, Jammy, and Noble. Any chance this could get sponsored and approved soon? I also checked up on upstream and it appears that they're preparing a 1.47.1 release of e2fsprogs that should include this fix. It hasn't been tagged yet, but they're starting the process: https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=3fcbc9ffbeaa0df3dd06113b61f9b3bed4efb92e -- 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/2036467 Title: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs Status in cloud-images: New Status in e2fsprogs package in Ubuntu: In Progress Status in e2fsprogs source package in Trusty: Won't Fix Status in e2fsprogs source package in Xenial: Won't Fix Status in e2fsprogs source package in Bionic: Won't Fix Status in e2fsprogs source package in Focal: In Progress Status in e2fsprogs source package in Jammy: In Progress Status in e2fsprogs source package in Lunar: Won't Fix Status in e2fsprogs source package in Mantic: In Progress Status in e2fsprogs source package in Noble: In Progress Bug description: [Impact] This is a long running bug plaguing cloud-images, where on a rare occasion resize2fs would fail and the image would not resize to fit the entire disk. Online resizes would fail due to a superblock checksum mismatch, where the superblock in memory differs from what is currently on disk due to changes made to the image. $ resize2fs /dev/nvme1n1p1 resize2fs 1.47.0 (5-Feb-2023) resize2fs: Superblock checksum does not match superblock while trying to open /dev/nvme1n1p1 Couldn't find valid filesystem superblock. Changing the read of the superblock to Direct I/O solves the issue. [Testcase] Start an c5.large instance on AWS, and attach a 60gb gp3 volume for use as a scratch disk. Run the following script, courtesy of Krister Johansen and his team: #!/usr/bin/bash set -euxo pipefail while true do parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s sleep .5 mkfs.ext4 /dev/nvme1n1p1 mount -t ext4 /dev/nvme1n1p1 /mnt stress-ng --temp-path /mnt -D 4 & STRESS_PID=$! sleep 1 growpart /dev/nvme1n1 1 resize2fs /dev/nvme1n1p1 kill $STRESS_PID wait $STRESS_PID umount /mnt wipefs -a /dev/nvme1n1p1 wipefs -a /dev/nvme1n1 done Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test If you install the test packages, the race no longer occurs. [Where problems could occur] We are changing how resize2fs reads the superblock from underlying disks. If a regression were to occur, resize2fs could fail to resize offline or online volumes. As all cloud-images are online resized during their initial boot, this could have a large impact to public and private clouds should a regression occur. [Other info] Upstream mailing list discussion: https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/ https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/ This was fixed in the below commit upstream: commit 43a498e938887956f393b5e45ea6ac79cc5f4b84 Author: Theodore Ts'o Date: Thu, 15 Jun 2023 00:17:01 -0400 Subject: resize2fs: use Direct I/O when reading the superblock for online resizes Link: https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84 The commit has not been tagged to any release. All supported Ubuntu releases require this fix, and need to be published in standard non- ESM archives to be picked up in cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036467/+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 2063094] Re: unattended-upgrades is running forever
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unattended-upgrades (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/2063094 Title: unattended-upgrades is running forever Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: 28433 root 39 19 354904 111480 71296 R 99.7 0.7 107:29.26 unattended-upgr ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: unattended-upgrades 2.9.1+nmu4ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1 Uname: Linux 6.8.0-28-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 10:27:34 2024 InstallationDate: Installed on 2022-01-07 (836 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: Upgraded to noble on 2024-04-10 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2063094/+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 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-release-upgrader (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/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to the end of the upgrade, I got an „Oh, no! Something has gone wrong and the system cannot recover. Call the system administrator” message after a red FAILED in the terminal. The system administrator is myself, because my computer is a personal one. Hard reset, same error, Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the update with dpkg. While dpkg was upgrading, it printed an error message for every WiFi connection: „[Failed] Failed to migrate [I do not remember, something with /etc/netplan]” It took at least one and a half hour to find the solution on Ask Ubuntu. The problem was: /etc/resolv.conf became a broken link, along with systemd-resolve.service. I needed to remove both of them and write a new resolv.conf to fix the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 08:21:02 2024 InstallationDate: Installed on 2023-07-05 (236 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) IpRoute: default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.45.90 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+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 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 I have the same issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to the end of the upgrade, I got an „Oh, no! Something has gone wrong and the system cannot recover. Call the system administrator” message after a red FAILED in the terminal. The system administrator is myself, because my computer is a personal one. Hard reset, same error, Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the update with dpkg. While dpkg was upgrading, it printed an error message for every WiFi connection: „[Failed] Failed to migrate [I do not remember, something with /etc/netplan]” It took at least one and a half hour to find the solution on Ask Ubuntu. The problem was: /etc/resolv.conf became a broken link, along with systemd-resolve.service. I needed to remove both of them and write a new resolv.conf to fix the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 08:21:02 2024 InstallationDate: Installed on 2023-07-05 (236 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) IpRoute: default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.45.90 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+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 2061214] Re: [SRU] Software Sources is not compatible with deb822
@theofficialgman this is specifically about the qt interface, so i've you've found a bug against the gtk one, it is something different. please file a separate bug. thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2061214 Title: [SRU] Software Sources is not compatible with deb822 Status in software-properties package in Ubuntu: Confirmed Status in software-properties-qt package in Ubuntu: Fix Released Status in software-properties source package in Noble: Confirmed Status in software-properties-qt source package in Noble: Fix Released Bug description: [ Impact ] Ubuntu 24.04 now uses deb822 to represent software sources for deb packages, instead of /etc/apt/sources.list. The complete rationale for this change can be found here: https://discourse.ubuntu.com/t/spec- apt-deb822-sources-by-default/29333 software-properties has two graphical frontends for editing these software sources, one is GTK-based and the other is Qt-based. When the underlying change to deb822 sources was made, the GTK-based frontend and the DBus backend interface gained support. The original bug report shown below informed us of the lack of deb822 support in the Qt frontend, which results in a broken, non-functional interface when attempting to view or edit most values on the first two tabs. The fix for this is to implement a Qt dialog for deb822 sources that somewhat matches the existing GTK interface. [ Test Plan ] Install software-properties-qt 0.99.48 or earlier. Reproducing the bug: 1. From the menu, open Software Sources. Alternatively, run `sudo -E software-properties-qt` in a terminal. 2. Observe that all four checkboxes on the Ubuntu Software tab (main, universe, restricted, and multiverse) are unchecked. 3. Move to the Other Software tab and observe that there are no items in the list. Upgrade to software-properties-qt 0.99.49. Intended functionality: 1. From the menu, open Software Sources. Alternatively, run `sudo -E software-properties-qt` in a terminal. 2. Observe that one or more checkboxes on the Ubuntu Software tab (representing main, universe, restricted, or multiverse) are checked. Toggle one or more of the checkboxes. 3. Using a text editor of some kind (perhaps Vim), confirm that /etc/apt/sources.list.d/ubuntu.sources reflects your changes. 4. Switch to the Other Software tab, there should be one item in the list. 5. Select that item, then click Edit at the bottom of the dialog. Make a modification to every field on the screen, or a combination of fields you would like to test. All fields should work. 6. Click the OK button at the bottom of the dialog to confirm the changes, then click Edit for that item again. The changes you made should be reflected (meaning, the changes were saved.) 7. Using a text editor of some kind (perhaps Vim), confirm that /etc/apt/sources.list.d/ubuntu.sources reflects your changes. [ Where problems could occur ] This is well-tested code. That being said, the following small edge cases exist: - If you create a very large amount of rows, it infinitely expands the dialog without a scroll wheel. This is the same functionality as the GTK frontend. - Error validation is not performed on the deb822 lines, they are simply written to the ubuntu.sources file. This is good as a starting point, but also relies on the appropriate update notifier handling these errors. This is the same functionality as the GTK frontend. In a future update, this functionality could be broken by one or more of the following underlying changes: - Changes to the software-properties backend which are only implemented for the GTK frontend. - Changes to the location or formatting of the ubuntu.sources file. - Regressions in the Python bindings for Qt 5, which are rare but possible. - Regressions in Python itself. [ Other Info ] Ubuntu Studio's live ISO and installed system are affected by this. Only Lubuntu's installed system is affected by this. [ Original Report ] Upgrading Lubuntu Jammy to Lubuntu Noble using TUI results in "Software sources" not correctly updated after upgrade. Prompt= shows normal and not LTS Used command sudo do-release-upgrade -d Otherwise the upgrade is good see attached screenshot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: software-properties-common 0.99.46 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Apr 13 11:44:28 2024 InstallationDate: Installed on 2024-04-13 (0 days ago) InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240331) PackageArchitecture: all SourcePackage: