[Touch-packages] [Bug 2017852] Re: package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2017852 Title: package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 27 07:47:41 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-11-10 (532 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: initramfs-tools Title: package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to jammy on 2022-08-27 (242 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017852/+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 2017852] [NEW] package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: . ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 27 07:47:41 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-11-10 (532 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: initramfs-tools Title: package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to jammy on 2022-08-27 (242 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2017852 Title: package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 27 07:47:41 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-11-10 (532 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: initramfs-tools Title: package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to jammy on 2022-08-27 (242 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017852/+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 2017846] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (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/2017846 Title: System kept waking up after pressing power button Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Tried it 3 times in the last 15min, each time it keeps waking back up. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yamiyuki 42974 F wireplumber /dev/snd/controlC3: yamiyuki 42974 F wireplumber /dev/snd/controlC0: yamiyuki 42974 F wireplumber /dev/snd/seq:yamiyuki 42972 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 27 00:45:37 2023 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570S AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER Package: systemd 252.5-2ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: lunar Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Touch-packages] [Bug 2017846] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2017846/+attachment/5669099/+files/acpidump.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/2017846 Title: System kept waking up after pressing power button Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Tried it 3 times in the last 15min, each time it keeps waking back up. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yamiyuki 42974 F wireplumber /dev/snd/controlC3: yamiyuki 42974 F wireplumber /dev/snd/controlC0: yamiyuki 42974 F wireplumber /dev/snd/seq:yamiyuki 42972 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 27 00:45:37 2023 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570S AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER Package: systemd 252.5-2ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: lunar Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Touch-packages] [Bug 2017846] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2017846/+attachment/5669098/+files/UdevDb.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/2017846 Title: System kept waking up after pressing power button Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Tried it 3 times in the last 15min, each time it keeps waking back up. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yamiyuki 42974 F wireplumber /dev/snd/controlC3: yamiyuki 42974 F wireplumber /dev/snd/controlC0: yamiyuki 42974 F wireplumber /dev/snd/seq:yamiyuki 42972 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 27 00:45:37 2023 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570S AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER Package: systemd 252.5-2ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: lunar Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Touch-packages] [Bug 2017846] SystemdDelta.txt
apport information ** Attachment added: "SystemdDelta.txt" https://bugs.launchpad.net/bugs/2017846/+attachment/5669097/+files/SystemdDelta.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/2017846 Title: System kept waking up after pressing power button Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Tried it 3 times in the last 15min, each time it keeps waking back up. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yamiyuki 42974 F wireplumber /dev/snd/controlC3: yamiyuki 42974 F wireplumber /dev/snd/controlC0: yamiyuki 42974 F wireplumber /dev/snd/seq:yamiyuki 42972 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 27 00:45:37 2023 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570S AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER Package: systemd 252.5-2ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: lunar Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Touch-packages] [Bug 2017846] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2017846/+attachment/5669096/+files/ProcModules.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/2017846 Title: System kept waking up after pressing power button Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Tried it 3 times in the last 15min, each time it keeps waking back up. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yamiyuki 42974 F wireplumber /dev/snd/controlC3: yamiyuki 42974 F wireplumber /dev/snd/controlC0: yamiyuki 42974 F wireplumber /dev/snd/seq:yamiyuki 42972 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 27 00:45:37 2023 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570S AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER Package: systemd 252.5-2ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: lunar Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Touch-packages] [Bug 2017846] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2017846/+attachment/5669095/+files/ProcInterrupts.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/2017846 Title: System kept waking up after pressing power button Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Tried it 3 times in the last 15min, each time it keeps waking back up. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yamiyuki 42974 F wireplumber /dev/snd/controlC3: yamiyuki 42974 F wireplumber /dev/snd/controlC0: yamiyuki 42974 F wireplumber /dev/snd/seq:yamiyuki 42972 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 27 00:45:37 2023 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570S AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER Package: systemd 252.5-2ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: lunar Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Touch-packages] [Bug 2017846] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2017846/+attachment/5669094/+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/2017846 Title: System kept waking up after pressing power button Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Tried it 3 times in the last 15min, each time it keeps waking back up. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yamiyuki 42974 F wireplumber /dev/snd/controlC3: yamiyuki 42974 F wireplumber /dev/snd/controlC0: yamiyuki 42974 F wireplumber /dev/snd/seq:yamiyuki 42972 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 27 00:45:37 2023 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570S AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER Package: systemd 252.5-2ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: lunar Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Touch-packages] [Bug 2017846] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2017846/+attachment/5669093/+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/2017846 Title: System kept waking up after pressing power button Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Tried it 3 times in the last 15min, each time it keeps waking back up. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yamiyuki 42974 F wireplumber /dev/snd/controlC3: yamiyuki 42974 F wireplumber /dev/snd/controlC0: yamiyuki 42974 F wireplumber /dev/snd/seq:yamiyuki 42972 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 27 00:45:37 2023 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570S AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER Package: systemd 252.5-2ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: lunar Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Touch-packages] [Bug 2017846] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2017846/+attachment/5669089/+files/Lsusb.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/2017846 Title: System kept waking up after pressing power button Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Tried it 3 times in the last 15min, each time it keeps waking back up. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yamiyuki 42974 F wireplumber /dev/snd/controlC3: yamiyuki 42974 F wireplumber /dev/snd/controlC0: yamiyuki 42974 F wireplumber /dev/snd/seq:yamiyuki 42972 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 27 00:45:37 2023 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570S AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER Package: systemd 252.5-2ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: lunar Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Touch-packages] [Bug 2017846] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2017846/+attachment/5669092/+files/ProcCpuinfo.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/2017846 Title: System kept waking up after pressing power button Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Tried it 3 times in the last 15min, each time it keeps waking back up. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yamiyuki 42974 F wireplumber /dev/snd/controlC3: yamiyuki 42974 F wireplumber /dev/snd/controlC0: yamiyuki 42974 F wireplumber /dev/snd/seq:yamiyuki 42972 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 27 00:45:37 2023 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570S AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER Package: systemd 252.5-2ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: lunar Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Touch-packages] [Bug 2017846] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2017846/+attachment/5669091/+files/Lsusb-v.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/2017846 Title: System kept waking up after pressing power button Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Tried it 3 times in the last 15min, each time it keeps waking back up. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yamiyuki 42974 F wireplumber /dev/snd/controlC3: yamiyuki 42974 F wireplumber /dev/snd/controlC0: yamiyuki 42974 F wireplumber /dev/snd/seq:yamiyuki 42972 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 27 00:45:37 2023 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570S AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER Package: systemd 252.5-2ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: lunar Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Touch-packages] [Bug 2017846] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2017846/+attachment/5669090/+files/Lsusb-t.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/2017846 Title: System kept waking up after pressing power button Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Tried it 3 times in the last 15min, each time it keeps waking back up. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yamiyuki 42974 F wireplumber /dev/snd/controlC3: yamiyuki 42974 F wireplumber /dev/snd/controlC0: yamiyuki 42974 F wireplumber /dev/snd/seq:yamiyuki 42972 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 27 00:45:37 2023 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570S AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER Package: systemd 252.5-2ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: lunar Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Touch-packages] [Bug 2017846] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2017846/+attachment/5669088/+files/Lspci-vt.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/2017846 Title: System kept waking up after pressing power button Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Tried it 3 times in the last 15min, each time it keeps waking back up. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yamiyuki 42974 F wireplumber /dev/snd/controlC3: yamiyuki 42974 F wireplumber /dev/snd/controlC0: yamiyuki 42974 F wireplumber /dev/snd/seq:yamiyuki 42972 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 27 00:45:37 2023 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570S AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER Package: systemd 252.5-2ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: lunar Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Touch-packages] [Bug 2017846] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2017846/+attachment/5669086/+files/Dependencies.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/2017846 Title: System kept waking up after pressing power button Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Tried it 3 times in the last 15min, each time it keeps waking back up. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yamiyuki 42974 F wireplumber /dev/snd/controlC3: yamiyuki 42974 F wireplumber /dev/snd/controlC0: yamiyuki 42974 F wireplumber /dev/snd/seq:yamiyuki 42972 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 27 00:45:37 2023 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570S AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER Package: systemd 252.5-2ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: lunar Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Touch-packages] [Bug 2017846] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2017846/+attachment/5669087/+files/Lspci.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/2017846 Title: System kept waking up after pressing power button Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Tried it 3 times in the last 15min, each time it keeps waking back up. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yamiyuki 42974 F wireplumber /dev/snd/controlC3: yamiyuki 42974 F wireplumber /dev/snd/controlC0: yamiyuki 42974 F wireplumber /dev/snd/seq:yamiyuki 42972 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 27 00:45:37 2023 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570S AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER Package: systemd 252.5-2ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: lunar Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Touch-packages] [Bug 2017846] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2017846/+attachment/5669085/+files/CurrentDmesg.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/2017846 Title: System kept waking up after pressing power button Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Tried it 3 times in the last 15min, each time it keeps waking back up. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yamiyuki 42974 F wireplumber /dev/snd/controlC3: yamiyuki 42974 F wireplumber /dev/snd/controlC0: yamiyuki 42974 F wireplumber /dev/snd/seq:yamiyuki 42972 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 27 00:45:37 2023 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570S AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER Package: systemd 252.5-2ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: lunar Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Touch-packages] [Bug 2017846] [NEW] System kept waking up after pressing power button
Public bug reported: Tried it 3 times in the last 15min, each time it keeps waking back up. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yamiyuki 42974 F wireplumber /dev/snd/controlC3: yamiyuki 42974 F wireplumber /dev/snd/controlC0: yamiyuki 42974 F wireplumber /dev/snd/seq:yamiyuki 42972 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 27 00:45:37 2023 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570S AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER Package: systemd 252.5-2ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: lunar Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570S AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620 ** Affects: linux (Ubuntu) Importance: Undecided Status: New
[Touch-packages] [Bug 2017840] [NEW] ifupdown resolved script has typo
Public bug reported: This error happens when you try to run ifup or ifdown: ``` # ifdown enp3s0 /etc/network/if-down.d/resolved: 12: mystatedir: not found # ifup enp3s0 /etc/network/if-up.d/resolved: 12: mystatedir: not found ``` Here's the first 12 lines of those scripts: ``` # head -n 12 /etc/network/if-up.d/resolved #!/bin/sh # # Script fragment to make ifupdown supply DNS infromation to resolved # case "$ADDRFAM" in inet|inet6) : ;; *) exit 0 ;; esac if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then mystatedir statedir ifindex interface ``` I'm thinking that the word `local` should appear before `mystatedir` on line 12. The `shellcheck` command is ok with that line, but only because it's not checking to see if `mystatedir` is an executable in the $PATH. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Description changed: This error happens when you try to run ifup or ifdown: ``` # ifdown enp3s0 /etc/network/if-down.d/resolved: 12: mystatedir: not found # ifup enp3s0 /etc/network/if-up.d/resolved: 12: mystatedir: not found ``` - Here's the first lines of that script: + Here's the first 12 lines of those scripts: ``` # head -n 12 /etc/network/if-up.d/resolved - + #!/bin/sh # # Script fragment to make ifupdown supply DNS infromation to resolved # case "$ADDRFAM" in - inet|inet6) : ;; - *) exit 0 ;; - esac + inet|inet6) : ;; + *) exit 0 ;; + esac if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then - mystatedir statedir ifindex interface + mystatedir statedir ifindex interface ``` I'm thinking that the word `local` should appear before `mystatedir` on line 12. The `shellcheck` command is ok with that line, but only because it's not checking to see if `mystatedir` is an executable in the $PATH. -- 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/2017840 Title: ifupdown resolved script has typo Status in systemd package in Ubuntu: New Bug description: This error happens when you try to run ifup or ifdown: ``` # ifdown enp3s0 /etc/network/if-down.d/resolved: 12: mystatedir: not found # ifup enp3s0 /etc/network/if-up.d/resolved: 12: mystatedir: not found ``` Here's the first 12 lines of those scripts: ``` # head -n 12 /etc/network/if-up.d/resolved #!/bin/sh # # Script fragment to make ifupdown supply DNS infromation to resolved # case "$ADDRFAM" in inet|inet6) : ;; *) exit 0 ;; esac if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then mystatedir statedir ifindex interface ``` I'm thinking that the word `local` should appear before `mystatedir` on line 12. The `shellcheck` command is ok with that line, but only because it's not checking to see if `mystatedir` is an executable in the $PATH. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2017840/+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 2017832] [NEW] No audio/sound after fresh 23.4 install, only dummy audio
Public bug reported: Did a fresh install of 23.4 and there is no working audio. Sound settings only show a "dummy output" audio device. If I plug headphones into the headphone jack, then a device shows up in sound settings: "Headphones - Tiger Lake-LP Smart Sound Technology Audio Controller". Then, if I try "test" and try to test the speakers, I hear nothing. If I open firefox and play a youtube video: 1. If I have headphones plugged in, I hear the audio over the internal speaker, not the headphones. 2. If I do not have the headphones plugged in, I hear nothing (dummy ouput in sound settings). Pipwire appears to be running: steve@steve-chromebook:~$ systemctl --user | grep wire pipewire-pulse.service loaded active running PipeWire PulseAudio pipewire.service loaded active running PipeWire Multimedia Service wireplumber.service loaded active running Multimedia Service Session Manager pipewire-pulse.socket loaded active running PipeWire PulseAudio pipewire.socket loaded active running PipeWire Multimedia System Socket Intel sound drivers appear to be running: $ lsmod | grep snd | grep intel snd_soc_intel_hda_dsp_common20480 1 snd_soc_sof_rt5682 snd_soc_intel_sof_maxim_common20480 1 snd_soc_sof_rt5682 snd_soc_intel_sof_realtek_common24576 1 snd_soc_sof_rt5682 snd_sof_pci_intel_tgl16384 0 snd_sof_intel_hda_common 188416 1 snd_sof_pci_intel_tgl soundwire_intel57344 1 snd_sof_intel_hda_common snd_sof_intel_hda 24576 1 snd_sof_intel_hda_common snd_sof_pci24576 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl snd_sof_xtensa_dsp 16384 1 snd_sof_intel_hda_common snd_sof 311296 6 snd_soc_sof_rt5682,snd_sof_pci,snd_sof_intel_hda_common,snd_soc_intel_sof_realtek_common,snd_sof_probes,snd_sof_intel_hda snd_soc_hdac_hda 24576 1 snd_sof_intel_hda_common snd_hda_ext_core 36864 4 snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_sof_intel_hda snd_soc_acpi_intel_match77824 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl snd_soc_acpi 16384 2 snd_soc_acpi_intel_match,snd_sof_intel_hda_common soundwire_bus 110592 5 regmap_sdw,soundwire_intel,soundwire_generic_allocation,soundwire_cadence,snd_soc_max98373_sdw snd_hda_intel 61440 0 snd_intel_dspcfg 36864 3 snd_hda_intel,snd_sof,snd_sof_intel_hda_common snd_intel_sdw_acpi 20480 2 snd_sof_intel_hda_common,snd_intel_dspcfg snd_soc_core 417792 16 snd_soc_max98373,snd_soc_sof_rt5682,snd_soc_rt5682,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_intel_sof_realtek_common,snd_soc_hdac_hda,snd_soc_max98373_i2c,snd_soc_intel_sof_maxim_common,snd_soc_max98373_sdw,snd_sof_probes,snd_soc_dmic,snd_soc_rt5682s,snd_soc_rt5682_i2c snd_hda_codec 204800 5 snd_hda_codec_hdmi,snd_hda_intel,snd_soc_intel_hda_dsp_common,snd_soc_hdac_hda,snd_sof_intel_hda snd_hda_core 139264 9 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_soc_intel_hda_dsp_common,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_sof_intel_hda snd_pcm 192512 18 snd_hda_codec_hdmi,snd_hda_intel,snd_soc_sof_rt5682,snd_soc_rt5682,snd_hda_codec,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_compress,snd_soc_intel_sof_realtek_common,snd_soc_max98373_i2c,snd_soc_core,snd_sof_utils,snd_soc_max98373_sdw,snd_hda_core,snd_soc_rt5682s,snd_pcm_dmaengine snd 135168 18 snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_soc_sof_rt5682,snd_hda_codec,snd_sof,snd_timer,snd_soc_hdac_hdmi,snd_compress,snd_soc_core,snd_pcm,snd_rawmidi Alsa info is here: http://alsa-project.org/db/?f=ea6f792b4f92dd965494ec53df480554c50c4456 This info shows some errors in dmesg, but I have no idea if they are expected or indicate a problem. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 1388 F wireplumber /dev/snd/seq:steve 1385 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 26 20:33:57 2023 InstallationDate: Installed on 2023-04-27 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64
[Touch-packages] [Bug 2017819] Re: Many broken symlinks and a few empty directories.
** Branch linked: lp:~ubuntu-art-pkg/humanity/release -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/2017819 Title: Many broken symlinks and a few empty directories. Status in Humanity: New Status in humanity-icon-theme package in Ubuntu: New Bug description: Broken symlinks- ./Humanity/apps/24/catfish.svg ./Humanity/apps/24/x-system-software-sources.svg ./Humanity/apps/24/panel-searchtool.svg ./Humanity/apps/24/pk-package-sources.svg ./Humanity/apps/24/xfce4-appfinder.svg ./Humanity/apps/24/gpk-repo.svg ./Humanity/apps/24/edit-urpm-sources.svg ./Humanity/apps/24/gnome-searchtool.svg ./Humanity/apps/48/catfish.svg ./Humanity/apps/48/x-system-software-sources.svg ./Humanity/apps/48/panel-searchtool.svg ./Humanity/apps/48/pk-package-sources.svg ./Humanity/apps/48/xfce4-appfinder.svg ./Humanity/apps/48/gpk-repo.svg ./Humanity/apps/48/edit-urpm-sources.svg ./Humanity/apps/48/gnome-searchtool.svg ./Humanity/status/48/aptdaemon-update-cache.svg ./Humanity/stock/24/stock_zoom-page.svg ./Humanity/stock/22/stock_zoom-page.svg ./Humanity/stock/48/stock_zoom-page.svg Empty directories- ./Humanity-Dark/places/32 ./Humanity-Dark/actions/24 ./Humanity-Dark/actions/22 To manage notifications about this bug go to: https://bugs.launchpad.net/humanity/+bug/2017819/+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 2017819] Re: Many broken symlinks and a few empty directories.
** Branch linked: lp:~wontfix/humanity/devel -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/2017819 Title: Many broken symlinks and a few empty directories. Status in Humanity: New Status in humanity-icon-theme package in Ubuntu: New Bug description: Broken symlinks- ./Humanity/apps/24/catfish.svg ./Humanity/apps/24/x-system-software-sources.svg ./Humanity/apps/24/panel-searchtool.svg ./Humanity/apps/24/pk-package-sources.svg ./Humanity/apps/24/xfce4-appfinder.svg ./Humanity/apps/24/gpk-repo.svg ./Humanity/apps/24/edit-urpm-sources.svg ./Humanity/apps/24/gnome-searchtool.svg ./Humanity/apps/48/catfish.svg ./Humanity/apps/48/x-system-software-sources.svg ./Humanity/apps/48/panel-searchtool.svg ./Humanity/apps/48/pk-package-sources.svg ./Humanity/apps/48/xfce4-appfinder.svg ./Humanity/apps/48/gpk-repo.svg ./Humanity/apps/48/edit-urpm-sources.svg ./Humanity/apps/48/gnome-searchtool.svg ./Humanity/status/48/aptdaemon-update-cache.svg ./Humanity/stock/24/stock_zoom-page.svg ./Humanity/stock/22/stock_zoom-page.svg ./Humanity/stock/48/stock_zoom-page.svg Empty directories- ./Humanity-Dark/places/32 ./Humanity-Dark/actions/24 ./Humanity-Dark/actions/22 To manage notifications about this bug go to: https://bugs.launchpad.net/humanity/+bug/2017819/+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 2017819] [NEW] Many broken symlinks and a few empty directories.
Public bug reported: Broken symlinks- ./Humanity/apps/24/catfish.svg ./Humanity/apps/24/x-system-software-sources.svg ./Humanity/apps/24/panel-searchtool.svg ./Humanity/apps/24/pk-package-sources.svg ./Humanity/apps/24/xfce4-appfinder.svg ./Humanity/apps/24/gpk-repo.svg ./Humanity/apps/24/edit-urpm-sources.svg ./Humanity/apps/24/gnome-searchtool.svg ./Humanity/apps/48/catfish.svg ./Humanity/apps/48/x-system-software-sources.svg ./Humanity/apps/48/panel-searchtool.svg ./Humanity/apps/48/pk-package-sources.svg ./Humanity/apps/48/xfce4-appfinder.svg ./Humanity/apps/48/gpk-repo.svg ./Humanity/apps/48/edit-urpm-sources.svg ./Humanity/apps/48/gnome-searchtool.svg ./Humanity/status/48/aptdaemon-update-cache.svg ./Humanity/stock/24/stock_zoom-page.svg ./Humanity/stock/22/stock_zoom-page.svg ./Humanity/stock/48/stock_zoom-page.svg Empty directories- ./Humanity-Dark/places/32 ./Humanity-Dark/actions/24 ./Humanity-Dark/actions/22 ** Affects: humanity Importance: Undecided Status: New ** Affects: humanity-icon-theme (Ubuntu) Importance: Undecided Status: New ** Tags: bionic focal humanity icons jammy kinetic lunar mantic ubuntu ** Also affects: humanity-icon-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/2017819 Title: Many broken symlinks and a few empty directories. Status in Humanity: New Status in humanity-icon-theme package in Ubuntu: New Bug description: Broken symlinks- ./Humanity/apps/24/catfish.svg ./Humanity/apps/24/x-system-software-sources.svg ./Humanity/apps/24/panel-searchtool.svg ./Humanity/apps/24/pk-package-sources.svg ./Humanity/apps/24/xfce4-appfinder.svg ./Humanity/apps/24/gpk-repo.svg ./Humanity/apps/24/edit-urpm-sources.svg ./Humanity/apps/24/gnome-searchtool.svg ./Humanity/apps/48/catfish.svg ./Humanity/apps/48/x-system-software-sources.svg ./Humanity/apps/48/panel-searchtool.svg ./Humanity/apps/48/pk-package-sources.svg ./Humanity/apps/48/xfce4-appfinder.svg ./Humanity/apps/48/gpk-repo.svg ./Humanity/apps/48/edit-urpm-sources.svg ./Humanity/apps/48/gnome-searchtool.svg ./Humanity/status/48/aptdaemon-update-cache.svg ./Humanity/stock/24/stock_zoom-page.svg ./Humanity/stock/22/stock_zoom-page.svg ./Humanity/stock/48/stock_zoom-page.svg Empty directories- ./Humanity-Dark/places/32 ./Humanity-Dark/actions/24 ./Humanity-Dark/actions/22 To manage notifications about this bug go to: https://bugs.launchpad.net/humanity/+bug/2017819/+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 1964828] Re: /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError: 'CasperMD5json'
** Changed in: apport (Ubuntu Focal) Assignee: cristian swing (sed1991s) => (unassigned) ** Changed in: apport (Ubuntu Jammy) Assignee: cristian swing (sed1991s) => (unassigned) -- 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/1964828 Title: /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError: 'CasperMD5json' Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: New Status in apport source package in Jammy: Fix Released Bug description: [Impact] If the user reports a bug and rejects to enter the root password for collecting information (like the CasperMD5json), the Ubuntu add_info hook will fail with a stack trace. The remaining code for collecting more information is not executed. So the resulting bug reports will be less helpful. The check_for_disk_error call is not reached and therefore skipped. [Test Plan] 1. Install Ubuntu (e.g. from ubuntu-22.04-desktop-amd64.iso) 2. Open a terminal 3. Run: ubuntu-bug -f 4. Select "installer" and click on OK 5. Click on "abort" when ask for the password 6. The terminal should not show a stacktrace [Where problems could occur] The changed code is the Ubuntu add_info hook. So this hook could fail due to a regression or reveal bugs in the later code path. The later code path could cause more more load on the users machine (but only when the user wants to report the issue). Apport will catch failing add_info hooks and store the failure in the report. [Orinial report] ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 81, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 1016, in attach_casper_md5check check = json.loads(report['CasperMD5json']) File "/usr/lib/python3.10/collections/__init__.py", line 1102, in __getitem__ raise KeyError(key) KeyError: 'CasperMD5json' kubuntu@kubuntu:~$ Gtk-Message: 21:22:43.923: Failed to load module "colorreload-gtk-module" ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperVersion: 1.467 CurrentDesktop: KDE Date: Mon Mar 14 21:22:23 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220314) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1964828/+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 1991975] Re: dev file system is mounted without nosuid or noexec
** Changed in: systemd (Ubuntu) Assignee: cristian swing (sed1991s) => (unassigned) ** Changed in: systemd (Ubuntu Focal) Assignee: cristian swing (sed1991s) => (unassigned) ** Changed in: systemd (Ubuntu Jammy) Assignee: cristian swing (sed1991s) => (unassigned) ** Changed in: linux (Ubuntu Focal) Status: Fix Released => In Progress ** Changed in: linux (Ubuntu Jammy) Status: Fix Released => In Progress ** Changed in: systemd (Ubuntu Focal) Status: Fix Released => Invalid ** Changed in: systemd (Ubuntu Jammy) Status: Fix Released => Invalid -- 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/1991975 Title: dev file system is mounted without nosuid or noexec Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in linux source package in Focal: In Progress Status in systemd source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in systemd source package in Jammy: Invalid Bug description: [ SRU TEMPLATE ] [ Impact ] * nosuid, and noexec bits are not set on /dev * This has the potential for nefarious actors to use this as an avenue for attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more discussion around this. * It is not best security practice. [ Test Plan ] 1.Boot a Canonical Supplied EC2 instance 2.Check the mount options for /dev. 3.You will notice the lack of nosuid and noexec on /dev. [ Where problems could occur ] * As of 2022/10/06, I need to test this, but don't know how to build -aws flavored ubuntu kernels. Instructions welcome. I'm holding off on adding SRU tags until I can actually get this tested. * If this is applied to non initramfs-less kernels it could potentially cause a regression for very old hardware that does nefarious things with memory. For a larger discussion about that see: https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/ * Low risk if a driver depends on /dev allowing suid or exec this might prevent boot. That being said, all kernels that have been booting with an initramfs have been getting nosuid, and noexec set so hopefully we can consider that risk fairly well tested. [ Other Info ] * Patch is accepted into 5.17, and will drop out quickly * Any server booting with an initramfs already has nosuid, and noexec set, so hopefully <<< ORIGINAL TEXT This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To
[Touch-packages] [Bug 1268556] Re: 8086:1502 [Fujitsu D3076-S1x] Ethernet disconnecting at boot and later
** Changed in: network-manager (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1268556 Title: 8086:1502 [Fujitsu D3076-S1x] Ethernet disconnecting at boot and later Status in network-manager package in Ubuntu: Fix Released Bug description: Fresh install XUbuntu 12.04. After boot network interface is down. After unplugging and plugging back network cable, network is up and running again. Later (randomly) it may go off again. Again, unplugging and plugging back network cable helps. Ethernet card is onboard Intel. Mainboard: FUJITSU D3076-S1 Same problem happens with onboard ethernet with Intel mainboard DH61BE. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-58-generic 3.2.0-58.88 ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53 Uname: Linux 3.2.0-58-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1641 F xfce4-volumed user 1718 F pulseaudio /dev/snd/controlC0: user 1641 F xfce4-volumed user 1718 F pulseaudio CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xfb22 irq 50' Mixer name : 'Conexant CX20642' Components : 'HDA:14f150a2,173411b0,00100100' Controls : 19 Simple ctrls : 9 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfb08 irq 17' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,10de094a,00100100' Controls : 12 Simple ctrls : 2 Date: Mon Jan 13 12:02:04 2014 HibernationDevice: RESUME=UUID=324bb3ce-d9ee-4142-a94d-1382ec436191 InstallationMedia: Xubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130822) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. MachineType: FUJITSU D3076-S1 MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-58-generic root=UUID=2d4ccd09-d6c3-47ee-80ad-14977144d770 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.2.0-58-generic N/A linux-backports-modules-3.2.0-58-generic N/A linux-firmware1.79.9 RfKill: SourcePackage: linux StagingDrivers: mei UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2012 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V4.6.4.0 R1.12.0 for D3076-S1x dmi.board.name: D3076-S1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3076-S1 dmi.chassis.type: 6 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.4.0R1.12.0forD3076-S1x:bd09/20/2012:svnFUJITSU:pnD3076-S1:pvr:rvnFUJITSU:rnD3076-S1:rvrS26361-D3076-S1:cvnFUJITSU:ct6:cvr: dmi.product.name: D3076-S1 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1268556/+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 1968154] Re: Only keep 2 kernels
Don't to what? Install unsigned kernel packages? My point is that there is a regression. linux-image-unsigned-* are longer considered kernel packages with the new patch. If linux-image-unsigned-5.4.0-1099-aws and linux-image- unsigned-5.4.0-1100-aws were the only kernel packages on the system, they both would be removed with 1.16.17 including the active kernel. That was not the case in 1.16.14. # apt autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-image-unsigned-5.4.0-1099-aws linux-image-unsigned-5.4.0-1100-aws linux-modules-5.4.0-1099-aws linux-modules-5.4.0-1100-aws 0 upgraded, 0 newly installed, 4 to remove and 66 not upgraded. After this operation, 165 MB disk space will be freed. Do you want to continue? [Y/n] ^C # uname -a Linux ip-xxx 5.4.0-1100-aws #108~18.04.1-Ubuntu SMP Thu Mar 30 02:15:05 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1968154 Title: Only keep 2 kernels Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Released Status in apt source package in Focal: Fix Released Status in apt source package in Impish: Fix Released Bug description: [Impact] APT currently keeps 3 kernels or even 4 in some releases. Our boot partition is sized for a steady state of 2 kernels + 1 new one being unpacked, hence users run out of space and new kernels fail to install, upgrade runs might abort in the middle. It's not nice. [Test plan] 1. Have two kernels installed (let's call them version 3, 2) 2. Check that both kernels are not autoremovable 3. Install an old kernel (let's call it 1), and mark it automatic 4. Check that 1 will be autoremovable (apt autoremove -s) 5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s) 6. Actually remove 2 7. Reboot into 3 and check that both 1 and 3 are now not autoremovable [Where problems could occur] We could keep the wrong kernels installed that the user did not expect. We remove the requirement to keep the most recently installed version, previously recorded in APT::LastInstalledKernel, to achieve this, as we had 3 hard requirements so far: 1. keep booted kernel 2. keep highest version 3. keep most recently installed 1 can't be removed as it would break running systems, 2 is what you definitely want to keep. During normal system lifetime, the most recently installed kernel is the same as the highest version, so 2==3, and there are no changes to behavior. Likewise, if you most recently installed an older kernel manually for debugging, it would be manually installed and not subject to removal, even if the rule is dropped. The behavior really only changes if you install an older kernel, and then mark it auto - that older kernel becomes automatically removable immediately after it is marked as auto. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1968154/+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 772024] Re: tzdata update keeps changing my timezone
The bionic SRU does not need a v2, because it does not have the pre-1970 timezone fix. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/772024 Title: tzdata update keeps changing my timezone Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Kinetic: New Status in tzdata package in Debian: Fix Released Bug description: [ Impact ] Users can select some time zones in debconf that the tzdata debconf script will replace on the next run. See "Original report" for more explanation. Either those time zones should not be selectable in debconf or they should not be replaced. [ Test Plan ] Select US/Central as time zone and run dpkg-reconfigure: ``` sudo ln -sf /usr/share/zoneinfo/US/Central /etc/localtime echo "US/Central" | sudo tee /etc/timezone sudo dpkg-reconfigure -fnoninteractive tzdata ``` The output of dpkg-reconfigure should say that the current default time zone is still US/Central. Besides this manual test, test_timezone_conversions is backported to check that there are no timezones which can be selected, but will be converted. [ Where problems could occur ] Besides added tests, the debconf part of tzdata is touched and could cause issues. The change does not touch the actual timezones. [ Original report ] Other than the fact that Chicago, Illinois is in US Central Timezone, I have no relationship to Chicago. I am not in Chicago. I do not want to be in Chicago. I am in the Central Timezone. I am physically closer to other cities mentioned in tzdata. Selecting America/Chicago versus US/Central is not easier for me nor is it more intuitive. I understand that the upstream tzdata package goes a long way in documenting all of the weirdness associated with timezones and different localities' treatment of timezones and daylight "savings" time. However, from an end-user perspective, the distribution should place no special importance or preference on one timezone specification or another. Likewise, if a user chooses a timezone, the system should never change it. To reproduce the issue: # Manually select US/Central me@ubuntu:~$ sudo dpkg-reconfigure tzdata [sudo] password for me: Current default time zone: 'US/Central' Local time is now: Wed Apr 27 16:05:02 CDT 2011. Universal Time is now: Wed Apr 27 21:05:02 UTC 2011. # Validation that selection was accepted me@ubuntu:~$ cat /etc/timezone US/Central me@ubuntu:~$ md5sum /etc/localtime /usr/share/zoneinfo/US/Central 6540624294b1193e22ed7a15692f2de7 /etc/localtime 6540624294b1193e22ed7a15692f2de7 /usr/share/zoneinfo/US/Central me@ubuntu:~$ debconf-show tzdata debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied tzdata/Zones/Australia: * tzdata/Zones/US: Central tzdata/Zones/Asia: * tzdata/Zones/Etc: UTC tzdata/Zones/SystemV: tzdata/Zones/Arctic: tzdata/Zones/Pacific: tzdata/Zones/Antarctica: tzdata/Zones/Europe: tzdata/Zones/Africa: * tzdata/Zones/America: Chicago * tzdata/Areas: US tzdata/Zones/Atlantic: tzdata/Zones/Indian: # Force the package to reinstall me@ubuntu:~$ aptitude reinstall tzdata The following packages will be REINSTALLED: tzdata 0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/658 kB of archives. After unpacking 0 B will be used. Preconfiguring packages ... (Reading database ... 168356 files and directories currently installed.) Preparing to replace tzdata 2011g-0ubuntu0.11.04 (using .../tzdata_2011g-0ubuntu0.11.04_all.deb) ... Unpacking replacement tzdata ... Setting up tzdata (2011g-0ubuntu0.11.04) ... Current default time zone: 'America/Chicago' Local time is now: Wed Apr 27 16:05:22 CDT 2011. Universal Time is now: Wed Apr 27 21:05:22 UTC 2011. Run 'dpkg-reconfigure tzdata' if you wish to change it. # Now previous indicators are reset to America/Chicago instead of US/Central ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: tzdata 2011g-0ubuntu0.11.04 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Wed Apr 27 15:54:33 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 LANGUAGE=en_US:en SourcePackage: tzdata UpgradeStatus: Upgraded to natty on 2011-04-10 (17 days ago) To manage notifications about this bug go to:
[Touch-packages] [Bug 772024] Re: tzdata update keeps changing my timezone
** Patch added: "tzdata_2023c-0ubuntu0.20.04.2_v2.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/772024/+attachment/5668983/+files/tzdata_2023c-0ubuntu0.20.04.2_v2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/772024 Title: tzdata update keeps changing my timezone Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Kinetic: New Status in tzdata package in Debian: Fix Released Bug description: [ Impact ] Users can select some time zones in debconf that the tzdata debconf script will replace on the next run. See "Original report" for more explanation. Either those time zones should not be selectable in debconf or they should not be replaced. [ Test Plan ] Select US/Central as time zone and run dpkg-reconfigure: ``` sudo ln -sf /usr/share/zoneinfo/US/Central /etc/localtime echo "US/Central" | sudo tee /etc/timezone sudo dpkg-reconfigure -fnoninteractive tzdata ``` The output of dpkg-reconfigure should say that the current default time zone is still US/Central. Besides this manual test, test_timezone_conversions is backported to check that there are no timezones which can be selected, but will be converted. [ Where problems could occur ] Besides added tests, the debconf part of tzdata is touched and could cause issues. The change does not touch the actual timezones. [ Original report ] Other than the fact that Chicago, Illinois is in US Central Timezone, I have no relationship to Chicago. I am not in Chicago. I do not want to be in Chicago. I am in the Central Timezone. I am physically closer to other cities mentioned in tzdata. Selecting America/Chicago versus US/Central is not easier for me nor is it more intuitive. I understand that the upstream tzdata package goes a long way in documenting all of the weirdness associated with timezones and different localities' treatment of timezones and daylight "savings" time. However, from an end-user perspective, the distribution should place no special importance or preference on one timezone specification or another. Likewise, if a user chooses a timezone, the system should never change it. To reproduce the issue: # Manually select US/Central me@ubuntu:~$ sudo dpkg-reconfigure tzdata [sudo] password for me: Current default time zone: 'US/Central' Local time is now: Wed Apr 27 16:05:02 CDT 2011. Universal Time is now: Wed Apr 27 21:05:02 UTC 2011. # Validation that selection was accepted me@ubuntu:~$ cat /etc/timezone US/Central me@ubuntu:~$ md5sum /etc/localtime /usr/share/zoneinfo/US/Central 6540624294b1193e22ed7a15692f2de7 /etc/localtime 6540624294b1193e22ed7a15692f2de7 /usr/share/zoneinfo/US/Central me@ubuntu:~$ debconf-show tzdata debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied tzdata/Zones/Australia: * tzdata/Zones/US: Central tzdata/Zones/Asia: * tzdata/Zones/Etc: UTC tzdata/Zones/SystemV: tzdata/Zones/Arctic: tzdata/Zones/Pacific: tzdata/Zones/Antarctica: tzdata/Zones/Europe: tzdata/Zones/Africa: * tzdata/Zones/America: Chicago * tzdata/Areas: US tzdata/Zones/Atlantic: tzdata/Zones/Indian: # Force the package to reinstall me@ubuntu:~$ aptitude reinstall tzdata The following packages will be REINSTALLED: tzdata 0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/658 kB of archives. After unpacking 0 B will be used. Preconfiguring packages ... (Reading database ... 168356 files and directories currently installed.) Preparing to replace tzdata 2011g-0ubuntu0.11.04 (using .../tzdata_2011g-0ubuntu0.11.04_all.deb) ... Unpacking replacement tzdata ... Setting up tzdata (2011g-0ubuntu0.11.04) ... Current default time zone: 'America/Chicago' Local time is now: Wed Apr 27 16:05:22 CDT 2011. Universal Time is now: Wed Apr 27 21:05:22 UTC 2011. Run 'dpkg-reconfigure tzdata' if you wish to change it. # Now previous indicators are reset to America/Chicago instead of US/Central ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: tzdata 2011g-0ubuntu0.11.04 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Wed Apr 27 15:54:33 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 LANGUAGE=en_US:en SourcePackage: tzdata UpgradeStatus: Upgraded to natty on 2011-04-10 (17 days ago) To manage
[Touch-packages] [Bug 772024] Re: tzdata update keeps changing my timezone
** Patch added: "tzdata_2023c-0ubuntu0.22.04.2_v2.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/772024/+attachment/5668982/+files/tzdata_2023c-0ubuntu0.22.04.2_v2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/772024 Title: tzdata update keeps changing my timezone Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Kinetic: New Status in tzdata package in Debian: Fix Released Bug description: [ Impact ] Users can select some time zones in debconf that the tzdata debconf script will replace on the next run. See "Original report" for more explanation. Either those time zones should not be selectable in debconf or they should not be replaced. [ Test Plan ] Select US/Central as time zone and run dpkg-reconfigure: ``` sudo ln -sf /usr/share/zoneinfo/US/Central /etc/localtime echo "US/Central" | sudo tee /etc/timezone sudo dpkg-reconfigure -fnoninteractive tzdata ``` The output of dpkg-reconfigure should say that the current default time zone is still US/Central. Besides this manual test, test_timezone_conversions is backported to check that there are no timezones which can be selected, but will be converted. [ Where problems could occur ] Besides added tests, the debconf part of tzdata is touched and could cause issues. The change does not touch the actual timezones. [ Original report ] Other than the fact that Chicago, Illinois is in US Central Timezone, I have no relationship to Chicago. I am not in Chicago. I do not want to be in Chicago. I am in the Central Timezone. I am physically closer to other cities mentioned in tzdata. Selecting America/Chicago versus US/Central is not easier for me nor is it more intuitive. I understand that the upstream tzdata package goes a long way in documenting all of the weirdness associated with timezones and different localities' treatment of timezones and daylight "savings" time. However, from an end-user perspective, the distribution should place no special importance or preference on one timezone specification or another. Likewise, if a user chooses a timezone, the system should never change it. To reproduce the issue: # Manually select US/Central me@ubuntu:~$ sudo dpkg-reconfigure tzdata [sudo] password for me: Current default time zone: 'US/Central' Local time is now: Wed Apr 27 16:05:02 CDT 2011. Universal Time is now: Wed Apr 27 21:05:02 UTC 2011. # Validation that selection was accepted me@ubuntu:~$ cat /etc/timezone US/Central me@ubuntu:~$ md5sum /etc/localtime /usr/share/zoneinfo/US/Central 6540624294b1193e22ed7a15692f2de7 /etc/localtime 6540624294b1193e22ed7a15692f2de7 /usr/share/zoneinfo/US/Central me@ubuntu:~$ debconf-show tzdata debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied tzdata/Zones/Australia: * tzdata/Zones/US: Central tzdata/Zones/Asia: * tzdata/Zones/Etc: UTC tzdata/Zones/SystemV: tzdata/Zones/Arctic: tzdata/Zones/Pacific: tzdata/Zones/Antarctica: tzdata/Zones/Europe: tzdata/Zones/Africa: * tzdata/Zones/America: Chicago * tzdata/Areas: US tzdata/Zones/Atlantic: tzdata/Zones/Indian: # Force the package to reinstall me@ubuntu:~$ aptitude reinstall tzdata The following packages will be REINSTALLED: tzdata 0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/658 kB of archives. After unpacking 0 B will be used. Preconfiguring packages ... (Reading database ... 168356 files and directories currently installed.) Preparing to replace tzdata 2011g-0ubuntu0.11.04 (using .../tzdata_2011g-0ubuntu0.11.04_all.deb) ... Unpacking replacement tzdata ... Setting up tzdata (2011g-0ubuntu0.11.04) ... Current default time zone: 'America/Chicago' Local time is now: Wed Apr 27 16:05:22 CDT 2011. Universal Time is now: Wed Apr 27 21:05:22 UTC 2011. Run 'dpkg-reconfigure tzdata' if you wish to change it. # Now previous indicators are reset to America/Chicago instead of US/Central ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: tzdata 2011g-0ubuntu0.11.04 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Wed Apr 27 15:54:33 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 LANGUAGE=en_US:en SourcePackage: tzdata UpgradeStatus: Upgraded to natty on 2011-04-10 (17 days ago) To manage
[Touch-packages] [Bug 2017804] [NEW] "Don't show this message again" button has no effect
Public bug reported: Since my upgrade to Ubuntu 23.04 I get annoying popups I've never seen before, especially when waking the computer from suspend, telling me e.g. that my connection to the WiFi network was lost or restored. Although these popups have a "Don't show this message again" button, that button seems to have no effect and I can't figure out how to stop the dialogs from appearing. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: network-manager 1.42.4-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Apr 26 13:26:32 2023 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-01-10 (1932 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 192.168.1.1 dev wlp4s0 proto dhcp src 192.168.1.202 metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.1.0/24 dev wlp4s0 proto kernel scope link src 192.168.1.202 metric 600 SourcePackage: network-manager UpgradeStatus: Upgraded to lunar on 2023-04-21 (5 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2017-10-21T17:11:24 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.42.4 connected started full enabled enabled enabled missing enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ** Attachment added: "example of the dialog I'm seeing" https://bugs.launchpad.net/bugs/2017804/+attachment/5668966/+files/Screenshot%20from%202023-04-25%2009-01-03.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2017804 Title: "Don't show this message again" button has no effect Status in network-manager package in Ubuntu: New Bug description: Since my upgrade to Ubuntu 23.04 I get annoying popups I've never seen before, especially when waking the computer from suspend, telling me e.g. that my connection to the WiFi network was lost or restored. Although these popups have a "Don't show this message again" button, that button seems to have no effect and I can't figure out how to stop the dialogs from appearing. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: network-manager 1.42.4-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Apr 26 13:26:32 2023 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-01-10 (1932 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 192.168.1.1 dev wlp4s0 proto dhcp src 192.168.1.202 metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.1.0/24 dev wlp4s0 proto kernel scope link src 192.168.1.202 metric 600 SourcePackage: network-manager UpgradeStatus: Upgraded to lunar on 2023-04-21 (5 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2017-10-21T17:11:24 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.42.4 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/2017804/+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 772024] Re: tzdata update keeps changing my timezone
Found more inconsistencies introduced by pre-1970 timezones. I will attach a set of v2 debdiffs to address those as well. ** Patch added: "tzdata_2023c-0ubuntu0.22.10.2_v2.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/772024/+attachment/5668963/+files/tzdata_2023c-0ubuntu0.22.10.2_v2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/772024 Title: tzdata update keeps changing my timezone Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Kinetic: New Status in tzdata package in Debian: Fix Released Bug description: [ Impact ] Users can select some time zones in debconf that the tzdata debconf script will replace on the next run. See "Original report" for more explanation. Either those time zones should not be selectable in debconf or they should not be replaced. [ Test Plan ] Select US/Central as time zone and run dpkg-reconfigure: ``` sudo ln -sf /usr/share/zoneinfo/US/Central /etc/localtime echo "US/Central" | sudo tee /etc/timezone sudo dpkg-reconfigure -fnoninteractive tzdata ``` The output of dpkg-reconfigure should say that the current default time zone is still US/Central. Besides this manual test, test_timezone_conversions is backported to check that there are no timezones which can be selected, but will be converted. [ Where problems could occur ] Besides added tests, the debconf part of tzdata is touched and could cause issues. The change does not touch the actual timezones. [ Original report ] Other than the fact that Chicago, Illinois is in US Central Timezone, I have no relationship to Chicago. I am not in Chicago. I do not want to be in Chicago. I am in the Central Timezone. I am physically closer to other cities mentioned in tzdata. Selecting America/Chicago versus US/Central is not easier for me nor is it more intuitive. I understand that the upstream tzdata package goes a long way in documenting all of the weirdness associated with timezones and different localities' treatment of timezones and daylight "savings" time. However, from an end-user perspective, the distribution should place no special importance or preference on one timezone specification or another. Likewise, if a user chooses a timezone, the system should never change it. To reproduce the issue: # Manually select US/Central me@ubuntu:~$ sudo dpkg-reconfigure tzdata [sudo] password for me: Current default time zone: 'US/Central' Local time is now: Wed Apr 27 16:05:02 CDT 2011. Universal Time is now: Wed Apr 27 21:05:02 UTC 2011. # Validation that selection was accepted me@ubuntu:~$ cat /etc/timezone US/Central me@ubuntu:~$ md5sum /etc/localtime /usr/share/zoneinfo/US/Central 6540624294b1193e22ed7a15692f2de7 /etc/localtime 6540624294b1193e22ed7a15692f2de7 /usr/share/zoneinfo/US/Central me@ubuntu:~$ debconf-show tzdata debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied tzdata/Zones/Australia: * tzdata/Zones/US: Central tzdata/Zones/Asia: * tzdata/Zones/Etc: UTC tzdata/Zones/SystemV: tzdata/Zones/Arctic: tzdata/Zones/Pacific: tzdata/Zones/Antarctica: tzdata/Zones/Europe: tzdata/Zones/Africa: * tzdata/Zones/America: Chicago * tzdata/Areas: US tzdata/Zones/Atlantic: tzdata/Zones/Indian: # Force the package to reinstall me@ubuntu:~$ aptitude reinstall tzdata The following packages will be REINSTALLED: tzdata 0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/658 kB of archives. After unpacking 0 B will be used. Preconfiguring packages ... (Reading database ... 168356 files and directories currently installed.) Preparing to replace tzdata 2011g-0ubuntu0.11.04 (using .../tzdata_2011g-0ubuntu0.11.04_all.deb) ... Unpacking replacement tzdata ... Setting up tzdata (2011g-0ubuntu0.11.04) ... Current default time zone: 'America/Chicago' Local time is now: Wed Apr 27 16:05:22 CDT 2011. Universal Time is now: Wed Apr 27 21:05:22 UTC 2011. Run 'dpkg-reconfigure tzdata' if you wish to change it. # Now previous indicators are reset to America/Chicago instead of US/Central ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: tzdata 2011g-0ubuntu0.11.04 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Wed Apr 27 15:54:33 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8
[Touch-packages] [Bug 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions
The attachment "mysuperpatch.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2017786 Title: update script in ubuntu-meta not handling germinate or specified versions Status in ubuntu-meta package in Ubuntu: New Bug description: update script handled debootstrap and devscripts, does not handle germinate. also doesn't handle potential specified versions in the package directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2017786/+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 2017792] [NEW] ifupdown on Ubuntu 22.04 fails to set DNS correctly -> DNS resolution does not work
Public bug reported: On a Ubuntu 22.04 system with /etc/network/interfaces configuration (ifupdown) instead of Netplan, DNS is not set correctly. Therefore, DNS resolution does not work. This explains the issue: https://unix.stackexchange.com/questions/714901/dns-broken-when-using- ifupdown-and-systemd-resolved-after-upgrade-to-ubuntu-22-0 Solution: Fix in /etc/network/if-up.d/resolved: Old: "$DNS"="$NEW_DNS" New: $DNS="$NEW_DNS" Old: "$DOMAINS"="$NEW_DOMAINS" New: $DOMAINS="$NEW_DOMAINS" /etc/network/if-up.d/resolved writes files /run/network/ifupdown-- containing the DNS configuration. The fix ensures that the files /run/network/ifupdown-- contain the correct syntax without quotes for the variable name. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ifupdown 0.8.36+nmu1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Apr 26 15:04:14 2023 InstallationDate: Installed on 2022-12-08 (139 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) ProcEnviron: LANGUAGE=nb:de:en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ifupdown UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.network.if-up.d.resolved: 2023-04-26T14:36:08.277304 ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/2017792 Title: ifupdown on Ubuntu 22.04 fails to set DNS correctly -> DNS resolution does not work Status in ifupdown package in Ubuntu: New Bug description: On a Ubuntu 22.04 system with /etc/network/interfaces configuration (ifupdown) instead of Netplan, DNS is not set correctly. Therefore, DNS resolution does not work. This explains the issue: https://unix.stackexchange.com/questions/714901/dns-broken-when-using- ifupdown-and-systemd-resolved-after-upgrade-to-ubuntu-22-0 Solution: Fix in /etc/network/if-up.d/resolved: Old: "$DNS"="$NEW_DNS" New: $DNS="$NEW_DNS" Old: "$DOMAINS"="$NEW_DOMAINS" New: $DOMAINS="$NEW_DOMAINS" /etc/network/if-up.d/resolved writes files /run/network/ifupdown-- containing the DNS configuration. The fix ensures that the files /run/network/ifupdown-- contain the correct syntax without quotes for the variable name. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ifupdown 0.8.36+nmu1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Apr 26 15:04:14 2023 InstallationDate: Installed on 2022-12-08 (139 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) ProcEnviron: LANGUAGE=nb:de:en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ifupdown UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.network.if-up.d.resolved: 2023-04-26T14:36:08.277304 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/2017792/+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 2017786] [NEW] update script in ubuntu-meta not handling germinate or specified versions
Public bug reported: update script handled debootstrap and devscripts, does not handle germinate. also doesn't handle potential specified versions in the package directory. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2017786 Title: update script in ubuntu-meta not handling germinate or specified versions Status in ubuntu-meta package in Ubuntu: New Bug description: update script handled debootstrap and devscripts, does not handle germinate. also doesn't handle potential specified versions in the package directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2017786/+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 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions
** Patch added: "mysuperpatch.debdiff" https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2017786/+attachment/5668944/+files/mysuperpatch.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2017786 Title: update script in ubuntu-meta not handling germinate or specified versions Status in ubuntu-meta package in Ubuntu: New Bug description: update script handled debootstrap and devscripts, does not handle germinate. also doesn't handle potential specified versions in the package directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2017786/+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 1992454] Re: iptables: segfault when renaming a chain
** Changed in: iptables (Ubuntu Kinetic) Assignee: Louis Bouchard (louis) => Andreas Hasenack (ahasenack) ** Changed in: iptables (Ubuntu Jammy) Assignee: Louis Bouchard (louis) => Andreas Hasenack (ahasenack) ** Changed in: iptables (Ubuntu Focal) Assignee: Louis Bouchard (louis) => Andreas Hasenack (ahasenack) ** Changed in: iptables (Ubuntu Bionic) Assignee: Louis Bouchard (louis) => Andreas Hasenack (ahasenack) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1992454 Title: iptables: segfault when renaming a chain Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Bionic: In Progress Status in iptables source package in Focal: In Progress Status in iptables source package in Jammy: In Progress Status in iptables source package in Kinetic: In Progress Bug description: [ Impact ] * An explanation of the effects of the bug on users This is the description for the upstream fix of this bug[1] : This is an odd bug: If the number of chains is right and one renames the last one in the list, libiptc dereferences a NULL pointer. * An explanation of the effects of the bug on users and * justification for backporting the fix to the stable release. Without this patch, users may experience segmentation fault when using the following versions of iptables : - Bionic : iptables - Focal : iptables - Jammy : iptables-legacy * In addition, it is helpful, but not required, to include an explanation of how the upload fixes this bug. The upstream fix adjust the size of the chain_index if the element is the last chain in the list. [1] http://git.netfilter.org/iptables/commit/?id=97bf4e68fc0794adba3243fd96f40f4568e7216f [ Test Plan ] * detailed instructions how to reproduce the bug The following code (adapted from the upstream commit to work on Kinetic) may be used to reproduce the issue : 8< #!/bin/bash # # Cover for a bug in libiptc: # - the chain 'node-98-tmp' is the last in the list sorted by name # - there are 81 chains in total, so three chain index buckets # - the last index bucket contains only the 'node-98-tmp' chain # => rename temporarily removes it from the bucket, leaving a NULL bucket # behind which is dereferenced later when inserting the chain again with new # name again ( echo "*filter" for chain in node-1 node-10 node-101 node-102 node-104 node-107 node-11 node-12 node-13 node-14 node-15 node-16 node-17 node-18 node-19 node-2 node-20 node-21 node-22 node-23 node-25 node-26 node-27 node-28 node-29 node-3 node-30 node-31 node-32 node-33 node-34 node-36 node-37 node-39 node-4 node-40 node-41 node-42 node-43 node-44 node-45 node-46 node-47 node-48 node-49 node-5 node-50 node-51 node-53 node-54 node-55 node-56 node-57 node-58 node-59 node-6 node-60 node-61 node-62 node-63 node-64 node-65 node-66 node-68 node-69 node-7 node-70 node-71 node-74 node-75 node-76 node-8 node-80 node-81 node-86 node-89 node-9 node-92 node-93 node-95 node-98-tmp; do echo ":$chain - [0:0]" done echo "COMMIT" ) | $XT_MULTI iptables-legacy-restore $XT_MULTI iptables-legacy -E node-98-tmp node-98 exit $? >8 [ Where problems could occur ] For Jammy and onward, only users of the -legacy commands may be affected. Since Jammy, iptables uses the new nft libraries which are not affected by the bug. For Bionic and Focal users, the regular iptables command is affected by the change. As stated in the manpage : E, --rename-chain old-chain new-chain Rename the user specified chain to the user supplied name. This is cosmetic, and has no effect on the structure of the table. In case of a problem, only the modification of the name would be affected as this is clearly outlined as a cosmetic only change. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1992454/+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 1979141] Re: ungrammatical line in ip-rule(8) page
Hey everyone, I just wanted to let you know that I have emailed a patch file to the iproute2 mailing list to fix the grammatical error in the ip-rule(8) man page. The patch file is titled '0001-Fix-grammar-in-ip-rule-8-man-page.patch'. I believe that this change will improve the readability and clarity of the man page, and make it easier for users to understand how to use the ip rule command. Thank you for your attention and consideration. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1979141 Title: ungrammatical line in ip-rule(8) page Status in iproute2 package in Ubuntu: New Bug description: The first line under DESCRIPTION on the ip-rule(8) man page is currently: > ip rule manipulates rules in the routing policy database control the route selection algorithm. It should have "control" changed to "that controls" (to apply to "database") or "to control" (to apply to "manipulates"). Ubuntu 22.04 LTS package version 5.15.0-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1979141/+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 1991975] Re: dev file system is mounted without nosuid or noexec
These metadata edits on this bug and a few others look spammy to me. Taking the appropriate action now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1991975 Title: dev file system is mounted without nosuid or noexec Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in linux source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [ SRU TEMPLATE ] [ Impact ] * nosuid, and noexec bits are not set on /dev * This has the potential for nefarious actors to use this as an avenue for attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more discussion around this. * It is not best security practice. [ Test Plan ] 1.Boot a Canonical Supplied EC2 instance 2.Check the mount options for /dev. 3.You will notice the lack of nosuid and noexec on /dev. [ Where problems could occur ] * As of 2022/10/06, I need to test this, but don't know how to build -aws flavored ubuntu kernels. Instructions welcome. I'm holding off on adding SRU tags until I can actually get this tested. * If this is applied to non initramfs-less kernels it could potentially cause a regression for very old hardware that does nefarious things with memory. For a larger discussion about that see: https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/ * Low risk if a driver depends on /dev allowing suid or exec this might prevent boot. That being said, all kernels that have been booting with an initramfs have been getting nosuid, and noexec set so hopefully we can consider that risk fairly well tested. [ Other Info ] * Patch is accepted into 5.17, and will drop out quickly * Any server booting with an initramfs already has nosuid, and noexec set, so hopefully <<< ORIGINAL TEXT This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+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 1991975] Re: dev file system is mounted without nosuid or noexec
I'm not too sure if updates from sed1991s above are correct -- 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/1991975 Title: dev file system is mounted without nosuid or noexec Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in linux source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [ SRU TEMPLATE ] [ Impact ] * nosuid, and noexec bits are not set on /dev * This has the potential for nefarious actors to use this as an avenue for attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more discussion around this. * It is not best security practice. [ Test Plan ] 1.Boot a Canonical Supplied EC2 instance 2.Check the mount options for /dev. 3.You will notice the lack of nosuid and noexec on /dev. [ Where problems could occur ] * As of 2022/10/06, I need to test this, but don't know how to build -aws flavored ubuntu kernels. Instructions welcome. I'm holding off on adding SRU tags until I can actually get this tested. * If this is applied to non initramfs-less kernels it could potentially cause a regression for very old hardware that does nefarious things with memory. For a larger discussion about that see: https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/ * Low risk if a driver depends on /dev allowing suid or exec this might prevent boot. That being said, all kernels that have been booting with an initramfs have been getting nosuid, and noexec set so hopefully we can consider that risk fairly well tested. [ Other Info ] * Patch is accepted into 5.17, and will drop out quickly * Any server booting with an initramfs already has nosuid, and noexec set, so hopefully <<< ORIGINAL TEXT This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+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 2003797] Re: Pre-1970 timestamps are knowingly wrong
While preparing the next SRUs, I noticed this change introduced inconsistencies in debconf. See bug #772024 for the debdiff for fixing those. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2003797 Title: Pre-1970 timestamps are knowingly wrong Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Bionic: Won't Fix Status in tzdata source package in Focal: Fix Released Status in tzdata source package in Jammy: Fix Released Status in tzdata source package in Kinetic: Fix Released Bug description: [ Impact ] tzdata 2021b says in NEWS: "Merge more location-based Zones whose timestamps agree since 1970, as pre-1970 timestamps are out of scope. This is part of a process that has been ongoing since 2013. This does not affect post-1970 timestamps, and timezone historians who build with 'make PACKRATDATA=backzone' should see no changes to pre-1970 timestamps." tzdata 2022b finished that process: "Finish moving to 'backzone' the location-based zones whose timestamps since 1970 are duplicates; adjust links accordingly. This change ordinarily affects only pre-1970 timestamps, and with the new PACKRATLIST option it does not affect any timestamps. In this round the affected zones are Antarctica/Vostok, Asia/Brunei, Asia/Kuala_Lumpur, Atlantic/Reykjavik, Europe/Amsterdam, Europe/Copenhagen, Europe/Luxembourg, Europe/Monaco, Europe/Oslo, Europe/Stockholm, Indian/Christmas, Indian/Cocos, Indian/Kerguelen, Indian/Mahe, Indian/Reunion, Pacific/Chuuk, Pacific/Funafuti, Pacific/Majuro, Pacific/Pohnpei, Pacific/Wake and Pacific/Wallis, and the affected links are Arctic/Longyearbyen, Atlantic/Jan_Mayen, Iceland, Pacific/Ponape, Pacific/Truk, and Pacific/Yap." The Debian/Ubuntu package builds tzdata with the default settings (PACKRATDATA unset) which merges zones whose timestamps agree since 1970. This leads to timestamps before 1970 being knowingly wrong. Example: Europe/Oslo is a link to Europe/Berlin since they are identical since 1970, but they differed before 1965. Berlin observed no summertime between 1950 and 1980, but Oslo did in 1959 to 1965. So summer 1960 in Oslo should be UTC+2 compared to UTC+1 in Berlin: ``` $ TZ=Europe/Oslo date -d "1960-07-01 10:00 Z" Fri Jul 1 12:00:00 CEST 1960 $ TZ=Europe/Berlin date -d "1960-07-01 10:00 Z" Fri Jul 1 11:00:00 CET 1960 ``` There was a big debate upstream (see https://lwn.net/Articles/870478/ or https://mm.icann.org/pipermail/tz/2021-May/030137.html). The Debian/Ubuntu package should ship timezones from backzone. Users that care about pre-1970 timestamps will be satisfied and users not caring will probably not care about the additional timezones. The install size will increase by around 20% and the amount of distinct (i.e. not symlinked) timezones will increase by 33%: ``` $ grep ^Zone africa antarctica asia australasia etcetera europe factory northamerica southamerica | wc -l 352 $ grep ^Zone backzone | wc -l 119 ``` [ Test plan ] The test case `test_pre_1970_timestamps` was added to the python autopkgtest for testing this change. So the test plan is to check that the autopkgtest succeeds. [ Where problems could occur ] Systems with incorrect timezone set may observe unexpected time shift. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2003797/+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 772024] Re: tzdata update keeps changing my timezone
** Description changed: - Binary package hint: tzdata + [ Impact ] + + Users can select some time zones in debconf that the tzdata debconf + script will replace on the next run. See "Original report" for more + explanation. Either those time zones should not be selectable in debconf + or they should not be replaced. + + [ Test Plan ] + + Select US/Central as time zone and run dpkg-reconfigure: + + ``` + sudo ln -sf /usr/share/zoneinfo/US/Central /etc/localtime + echo "US/Central" | sudo tee /etc/timezone + sudo dpkg-reconfigure -fnoninteractive tzdata + ``` + + The output of dpkg-reconfigure should say that the current default time + zone is still US/Central. + + Besides this manual test, test_timezone_conversions is backported to + check that there are no timezones which can be selected, but will be + converted. + + [ Where problems could occur ] + + Besides added tests, the debconf part of tzdata is touched and could + cause issues. The change does not touch the actual timezones. + + [ Original report ] Other than the fact that Chicago, Illinois is in US Central Timezone, I have no relationship to Chicago. I am not in Chicago. I do not want to be in Chicago. I am in the Central Timezone. I am physically closer to other cities mentioned in tzdata. Selecting America/Chicago versus US/Central is not easier for me nor is it more intuitive. I understand that the upstream tzdata package goes a long way in documenting all of the weirdness associated with timezones and different localities' treatment of timezones and daylight "savings" time. However, from an end-user perspective, the distribution should place no special importance or preference on one timezone specification or another. Likewise, if a user chooses a timezone, the system should never change it. To reproduce the issue: # Manually select US/Central me@ubuntu:~$ sudo dpkg-reconfigure tzdata - [sudo] password for me: + [sudo] password for me: Current default time zone: 'US/Central' Local time is now: Wed Apr 27 16:05:02 CDT 2011. Universal Time is now: Wed Apr 27 21:05:02 UTC 2011. # Validation that selection was accepted me@ubuntu:~$ cat /etc/timezone US/Central - me@ubuntu:~$ md5sum /etc/localtime /usr/share/zoneinfo/US/Central + me@ubuntu:~$ md5sum /etc/localtime /usr/share/zoneinfo/US/Central 6540624294b1193e22ed7a15692f2de7 /etc/localtime 6540624294b1193e22ed7a15692f2de7 /usr/share/zoneinfo/US/Central me@ubuntu:~$ debconf-show tzdata debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied - tzdata/Zones/Australia: + tzdata/Zones/Australia: * tzdata/Zones/US: Central - tzdata/Zones/Asia: + tzdata/Zones/Asia: * tzdata/Zones/Etc: UTC - tzdata/Zones/SystemV: - tzdata/Zones/Arctic: - tzdata/Zones/Pacific: - tzdata/Zones/Antarctica: - tzdata/Zones/Europe: - tzdata/Zones/Africa: + tzdata/Zones/SystemV: + tzdata/Zones/Arctic: + tzdata/Zones/Pacific: + tzdata/Zones/Antarctica: + tzdata/Zones/Europe: + tzdata/Zones/Africa: * tzdata/Zones/America: Chicago * tzdata/Areas: US - tzdata/Zones/Atlantic: - tzdata/Zones/Indian: + tzdata/Zones/Atlantic: + tzdata/Zones/Indian: # Force the package to reinstall me@ubuntu:~$ aptitude reinstall tzdata The following packages will be REINSTALLED: - tzdata + tzdata 0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/658 kB of archives. After unpacking 0 B will be used. - Preconfiguring packages ... + Preconfiguring packages ... (Reading database ... 168356 files and directories currently installed.) Preparing to replace tzdata 2011g-0ubuntu0.11.04 (using .../tzdata_2011g-0ubuntu0.11.04_all.deb) ... Unpacking replacement tzdata ... Setting up tzdata (2011g-0ubuntu0.11.04) ... Current default time zone: 'America/Chicago' Local time is now: Wed Apr 27 16:05:22 CDT 2011. Universal Time is now: Wed Apr 27 21:05:22 UTC 2011. Run 'dpkg-reconfigure tzdata' if you wish to change it. # Now previous indicators are reset to America/Chicago instead of US/Central ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: tzdata 2011g-0ubuntu0.11.04 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Wed Apr 27 15:54:33 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all ProcEnviron: - SHELL=/bin/bash - PATH=(custom, user) - LANG=en_US.UTF-8 - LANGUAGE=en_US:en + SHELL=/bin/bash + PATH=(custom, user) + LANG=en_US.UTF-8 + LANGUAGE=en_US:en SourcePackage: tzdata UpgradeStatus: Upgraded to natty on 2011-04-10 (17 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu.
[Touch-packages] [Bug 772024] Re: tzdata update keeps changing my timezone
** Also affects: tzdata (Ubuntu Bionic) Importance: Undecided Status: New ** Patch added: "tzdata_2023c-0ubuntu0.18.04.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/772024/+attachment/5668934/+files/tzdata_2023c-0ubuntu0.18.04.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/772024 Title: tzdata update keeps changing my timezone Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Kinetic: New Status in tzdata package in Debian: Fix Released Bug description: Binary package hint: tzdata Other than the fact that Chicago, Illinois is in US Central Timezone, I have no relationship to Chicago. I am not in Chicago. I do not want to be in Chicago. I am in the Central Timezone. I am physically closer to other cities mentioned in tzdata. Selecting America/Chicago versus US/Central is not easier for me nor is it more intuitive. I understand that the upstream tzdata package goes a long way in documenting all of the weirdness associated with timezones and different localities' treatment of timezones and daylight "savings" time. However, from an end-user perspective, the distribution should place no special importance or preference on one timezone specification or another. Likewise, if a user chooses a timezone, the system should never change it. To reproduce the issue: # Manually select US/Central me@ubuntu:~$ sudo dpkg-reconfigure tzdata [sudo] password for me: Current default time zone: 'US/Central' Local time is now: Wed Apr 27 16:05:02 CDT 2011. Universal Time is now: Wed Apr 27 21:05:02 UTC 2011. # Validation that selection was accepted me@ubuntu:~$ cat /etc/timezone US/Central me@ubuntu:~$ md5sum /etc/localtime /usr/share/zoneinfo/US/Central 6540624294b1193e22ed7a15692f2de7 /etc/localtime 6540624294b1193e22ed7a15692f2de7 /usr/share/zoneinfo/US/Central me@ubuntu:~$ debconf-show tzdata debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied tzdata/Zones/Australia: * tzdata/Zones/US: Central tzdata/Zones/Asia: * tzdata/Zones/Etc: UTC tzdata/Zones/SystemV: tzdata/Zones/Arctic: tzdata/Zones/Pacific: tzdata/Zones/Antarctica: tzdata/Zones/Europe: tzdata/Zones/Africa: * tzdata/Zones/America: Chicago * tzdata/Areas: US tzdata/Zones/Atlantic: tzdata/Zones/Indian: # Force the package to reinstall me@ubuntu:~$ aptitude reinstall tzdata The following packages will be REINSTALLED: tzdata 0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/658 kB of archives. After unpacking 0 B will be used. Preconfiguring packages ... (Reading database ... 168356 files and directories currently installed.) Preparing to replace tzdata 2011g-0ubuntu0.11.04 (using .../tzdata_2011g-0ubuntu0.11.04_all.deb) ... Unpacking replacement tzdata ... Setting up tzdata (2011g-0ubuntu0.11.04) ... Current default time zone: 'America/Chicago' Local time is now: Wed Apr 27 16:05:22 CDT 2011. Universal Time is now: Wed Apr 27 21:05:22 UTC 2011. Run 'dpkg-reconfigure tzdata' if you wish to change it. # Now previous indicators are reset to America/Chicago instead of US/Central ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: tzdata 2011g-0ubuntu0.11.04 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Wed Apr 27 15:54:33 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 LANGUAGE=en_US:en SourcePackage: tzdata UpgradeStatus: Upgraded to natty on 2011-04-10 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/772024/+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 1992454] Re: iptables: segfault when renaming a chain
You are too kind, Louis. I'm sorry I dropped this again. I'm tagging it now, so it appears in our team's weekly checkpoint, and will address it. ** Tags added: server-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1992454 Title: iptables: segfault when renaming a chain Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Bionic: In Progress Status in iptables source package in Focal: In Progress Status in iptables source package in Jammy: In Progress Status in iptables source package in Kinetic: In Progress Bug description: [ Impact ] * An explanation of the effects of the bug on users This is the description for the upstream fix of this bug[1] : This is an odd bug: If the number of chains is right and one renames the last one in the list, libiptc dereferences a NULL pointer. * An explanation of the effects of the bug on users and * justification for backporting the fix to the stable release. Without this patch, users may experience segmentation fault when using the following versions of iptables : - Bionic : iptables - Focal : iptables - Jammy : iptables-legacy * In addition, it is helpful, but not required, to include an explanation of how the upload fixes this bug. The upstream fix adjust the size of the chain_index if the element is the last chain in the list. [1] http://git.netfilter.org/iptables/commit/?id=97bf4e68fc0794adba3243fd96f40f4568e7216f [ Test Plan ] * detailed instructions how to reproduce the bug The following code (adapted from the upstream commit to work on Kinetic) may be used to reproduce the issue : 8< #!/bin/bash # # Cover for a bug in libiptc: # - the chain 'node-98-tmp' is the last in the list sorted by name # - there are 81 chains in total, so three chain index buckets # - the last index bucket contains only the 'node-98-tmp' chain # => rename temporarily removes it from the bucket, leaving a NULL bucket # behind which is dereferenced later when inserting the chain again with new # name again ( echo "*filter" for chain in node-1 node-10 node-101 node-102 node-104 node-107 node-11 node-12 node-13 node-14 node-15 node-16 node-17 node-18 node-19 node-2 node-20 node-21 node-22 node-23 node-25 node-26 node-27 node-28 node-29 node-3 node-30 node-31 node-32 node-33 node-34 node-36 node-37 node-39 node-4 node-40 node-41 node-42 node-43 node-44 node-45 node-46 node-47 node-48 node-49 node-5 node-50 node-51 node-53 node-54 node-55 node-56 node-57 node-58 node-59 node-6 node-60 node-61 node-62 node-63 node-64 node-65 node-66 node-68 node-69 node-7 node-70 node-71 node-74 node-75 node-76 node-8 node-80 node-81 node-86 node-89 node-9 node-92 node-93 node-95 node-98-tmp; do echo ":$chain - [0:0]" done echo "COMMIT" ) | $XT_MULTI iptables-legacy-restore $XT_MULTI iptables-legacy -E node-98-tmp node-98 exit $? >8 [ Where problems could occur ] For Jammy and onward, only users of the -legacy commands may be affected. Since Jammy, iptables uses the new nft libraries which are not affected by the bug. For Bionic and Focal users, the regular iptables command is affected by the change. As stated in the manpage : E, --rename-chain old-chain new-chain Rename the user specified chain to the user supplied name. This is cosmetic, and has no effect on the structure of the table. In case of a problem, only the modification of the name would be affected as this is clearly outlined as a cosmetic only change. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1992454/+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 772024] Re: tzdata update keeps changing my timezone
** Patch added: "tzdata_2023c-0ubuntu0.20.04.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/772024/+attachment/5668933/+files/tzdata_2023c-0ubuntu0.20.04.2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/772024 Title: tzdata update keeps changing my timezone Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Kinetic: New Status in tzdata package in Debian: Fix Released Bug description: Binary package hint: tzdata Other than the fact that Chicago, Illinois is in US Central Timezone, I have no relationship to Chicago. I am not in Chicago. I do not want to be in Chicago. I am in the Central Timezone. I am physically closer to other cities mentioned in tzdata. Selecting America/Chicago versus US/Central is not easier for me nor is it more intuitive. I understand that the upstream tzdata package goes a long way in documenting all of the weirdness associated with timezones and different localities' treatment of timezones and daylight "savings" time. However, from an end-user perspective, the distribution should place no special importance or preference on one timezone specification or another. Likewise, if a user chooses a timezone, the system should never change it. To reproduce the issue: # Manually select US/Central me@ubuntu:~$ sudo dpkg-reconfigure tzdata [sudo] password for me: Current default time zone: 'US/Central' Local time is now: Wed Apr 27 16:05:02 CDT 2011. Universal Time is now: Wed Apr 27 21:05:02 UTC 2011. # Validation that selection was accepted me@ubuntu:~$ cat /etc/timezone US/Central me@ubuntu:~$ md5sum /etc/localtime /usr/share/zoneinfo/US/Central 6540624294b1193e22ed7a15692f2de7 /etc/localtime 6540624294b1193e22ed7a15692f2de7 /usr/share/zoneinfo/US/Central me@ubuntu:~$ debconf-show tzdata debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied tzdata/Zones/Australia: * tzdata/Zones/US: Central tzdata/Zones/Asia: * tzdata/Zones/Etc: UTC tzdata/Zones/SystemV: tzdata/Zones/Arctic: tzdata/Zones/Pacific: tzdata/Zones/Antarctica: tzdata/Zones/Europe: tzdata/Zones/Africa: * tzdata/Zones/America: Chicago * tzdata/Areas: US tzdata/Zones/Atlantic: tzdata/Zones/Indian: # Force the package to reinstall me@ubuntu:~$ aptitude reinstall tzdata The following packages will be REINSTALLED: tzdata 0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/658 kB of archives. After unpacking 0 B will be used. Preconfiguring packages ... (Reading database ... 168356 files and directories currently installed.) Preparing to replace tzdata 2011g-0ubuntu0.11.04 (using .../tzdata_2011g-0ubuntu0.11.04_all.deb) ... Unpacking replacement tzdata ... Setting up tzdata (2011g-0ubuntu0.11.04) ... Current default time zone: 'America/Chicago' Local time is now: Wed Apr 27 16:05:22 CDT 2011. Universal Time is now: Wed Apr 27 21:05:22 UTC 2011. Run 'dpkg-reconfigure tzdata' if you wish to change it. # Now previous indicators are reset to America/Chicago instead of US/Central ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: tzdata 2011g-0ubuntu0.11.04 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Wed Apr 27 15:54:33 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 LANGUAGE=en_US:en SourcePackage: tzdata UpgradeStatus: Upgraded to natty on 2011-04-10 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/772024/+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 772024] Re: tzdata update keeps changing my timezone
** Patch added: "tzdata_2023c-0ubuntu0.22.04.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/772024/+attachment/5668932/+files/tzdata_2023c-0ubuntu0.22.04.2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/772024 Title: tzdata update keeps changing my timezone Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Kinetic: New Status in tzdata package in Debian: Fix Released Bug description: Binary package hint: tzdata Other than the fact that Chicago, Illinois is in US Central Timezone, I have no relationship to Chicago. I am not in Chicago. I do not want to be in Chicago. I am in the Central Timezone. I am physically closer to other cities mentioned in tzdata. Selecting America/Chicago versus US/Central is not easier for me nor is it more intuitive. I understand that the upstream tzdata package goes a long way in documenting all of the weirdness associated with timezones and different localities' treatment of timezones and daylight "savings" time. However, from an end-user perspective, the distribution should place no special importance or preference on one timezone specification or another. Likewise, if a user chooses a timezone, the system should never change it. To reproduce the issue: # Manually select US/Central me@ubuntu:~$ sudo dpkg-reconfigure tzdata [sudo] password for me: Current default time zone: 'US/Central' Local time is now: Wed Apr 27 16:05:02 CDT 2011. Universal Time is now: Wed Apr 27 21:05:02 UTC 2011. # Validation that selection was accepted me@ubuntu:~$ cat /etc/timezone US/Central me@ubuntu:~$ md5sum /etc/localtime /usr/share/zoneinfo/US/Central 6540624294b1193e22ed7a15692f2de7 /etc/localtime 6540624294b1193e22ed7a15692f2de7 /usr/share/zoneinfo/US/Central me@ubuntu:~$ debconf-show tzdata debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied tzdata/Zones/Australia: * tzdata/Zones/US: Central tzdata/Zones/Asia: * tzdata/Zones/Etc: UTC tzdata/Zones/SystemV: tzdata/Zones/Arctic: tzdata/Zones/Pacific: tzdata/Zones/Antarctica: tzdata/Zones/Europe: tzdata/Zones/Africa: * tzdata/Zones/America: Chicago * tzdata/Areas: US tzdata/Zones/Atlantic: tzdata/Zones/Indian: # Force the package to reinstall me@ubuntu:~$ aptitude reinstall tzdata The following packages will be REINSTALLED: tzdata 0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/658 kB of archives. After unpacking 0 B will be used. Preconfiguring packages ... (Reading database ... 168356 files and directories currently installed.) Preparing to replace tzdata 2011g-0ubuntu0.11.04 (using .../tzdata_2011g-0ubuntu0.11.04_all.deb) ... Unpacking replacement tzdata ... Setting up tzdata (2011g-0ubuntu0.11.04) ... Current default time zone: 'America/Chicago' Local time is now: Wed Apr 27 16:05:22 CDT 2011. Universal Time is now: Wed Apr 27 21:05:22 UTC 2011. Run 'dpkg-reconfigure tzdata' if you wish to change it. # Now previous indicators are reset to America/Chicago instead of US/Central ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: tzdata 2011g-0ubuntu0.11.04 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Wed Apr 27 15:54:33 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 LANGUAGE=en_US:en SourcePackage: tzdata UpgradeStatus: Upgraded to natty on 2011-04-10 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/772024/+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 772024] Re: tzdata update keeps changing my timezone
** Also affects: tzdata (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Kinetic) Importance: Undecided Status: New ** Patch added: "tzdata_2023c-0ubuntu0.22.10.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/772024/+attachment/5668931/+files/tzdata_2023c-0ubuntu0.22.10.2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/772024 Title: tzdata update keeps changing my timezone Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Kinetic: New Status in tzdata package in Debian: Fix Released Bug description: Binary package hint: tzdata Other than the fact that Chicago, Illinois is in US Central Timezone, I have no relationship to Chicago. I am not in Chicago. I do not want to be in Chicago. I am in the Central Timezone. I am physically closer to other cities mentioned in tzdata. Selecting America/Chicago versus US/Central is not easier for me nor is it more intuitive. I understand that the upstream tzdata package goes a long way in documenting all of the weirdness associated with timezones and different localities' treatment of timezones and daylight "savings" time. However, from an end-user perspective, the distribution should place no special importance or preference on one timezone specification or another. Likewise, if a user chooses a timezone, the system should never change it. To reproduce the issue: # Manually select US/Central me@ubuntu:~$ sudo dpkg-reconfigure tzdata [sudo] password for me: Current default time zone: 'US/Central' Local time is now: Wed Apr 27 16:05:02 CDT 2011. Universal Time is now: Wed Apr 27 21:05:02 UTC 2011. # Validation that selection was accepted me@ubuntu:~$ cat /etc/timezone US/Central me@ubuntu:~$ md5sum /etc/localtime /usr/share/zoneinfo/US/Central 6540624294b1193e22ed7a15692f2de7 /etc/localtime 6540624294b1193e22ed7a15692f2de7 /usr/share/zoneinfo/US/Central me@ubuntu:~$ debconf-show tzdata debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied tzdata/Zones/Australia: * tzdata/Zones/US: Central tzdata/Zones/Asia: * tzdata/Zones/Etc: UTC tzdata/Zones/SystemV: tzdata/Zones/Arctic: tzdata/Zones/Pacific: tzdata/Zones/Antarctica: tzdata/Zones/Europe: tzdata/Zones/Africa: * tzdata/Zones/America: Chicago * tzdata/Areas: US tzdata/Zones/Atlantic: tzdata/Zones/Indian: # Force the package to reinstall me@ubuntu:~$ aptitude reinstall tzdata The following packages will be REINSTALLED: tzdata 0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/658 kB of archives. After unpacking 0 B will be used. Preconfiguring packages ... (Reading database ... 168356 files and directories currently installed.) Preparing to replace tzdata 2011g-0ubuntu0.11.04 (using .../tzdata_2011g-0ubuntu0.11.04_all.deb) ... Unpacking replacement tzdata ... Setting up tzdata (2011g-0ubuntu0.11.04) ... Current default time zone: 'America/Chicago' Local time is now: Wed Apr 27 16:05:22 CDT 2011. Universal Time is now: Wed Apr 27 21:05:22 UTC 2011. Run 'dpkg-reconfigure tzdata' if you wish to change it. # Now previous indicators are reset to America/Chicago instead of US/Central ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: tzdata 2011g-0ubuntu0.11.04 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Wed Apr 27 15:54:33 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 LANGUAGE=en_US:en SourcePackage: tzdata UpgradeStatus: Upgraded to natty on 2011-04-10 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/772024/+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 1427600] Re: apport-unpack: ValueError: ['UserGroups'] has no binary content
** Changed in: apport (Ubuntu Xenial) Assignee: (unassigned) => cristian swing (sed1991s) -- 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/1427600 Title: apport-unpack: ValueError: ['UserGroups'] has no binary content Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Won't Fix Status in apport source package in Focal: Fix Released Status in apport source package in Groovy: Fix Released Bug description: [Impact] apport-unpack crashes when trying to unpack a crash [Test Case] On a system running 20.04 LTS: 1) create an additional user who is only a member of their own group e.g. bdmurray@clean-focal-amd64:~$ id crashy uid=1001(crashy) gid=1001(crashy) groups=1001(crashy) 2) Launch a process as that user 3) kill -11 that process 4) Confirm there is a crash file in /var/crash for that process 5) Run apport-unpack on that .crash file With the version of apport from -proposed you will not get another crash file when unpacking the crash file. [Regression Potential] We are just setting UserGroups to 'N/A' as opposed to having it be completely empty so there isn't any chance for regression. When running apport-unpack to get at a core dump laney@raleigh> sudo apport-unpack _usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz [sudo] password for laney: Traceback (most recent call last): File "/usr/bin/apport-unpack", line 73, in pr.extract_keys(f, bin_keys, dir) File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in extract_keys [item for item, element in b64_block.items() if element is False]) ValueError: ['UserGroups'] has no binary content laney@raleigh> apport-cli --version 2.16.2 It's not terrible, because most files are unpacked (those which sort before UserGroups, I guess). ProblemType: BugDistroRelease: Ubuntu 15.04 Package: apport 2.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportLog: ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 3 10:09:26 2015 InstallationDate: Installed on 2012-10-07 (876 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) PackageArchitecture: allSourcePackage: apport UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1427600/+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 1964828] Re: /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError: 'CasperMD5json'
** Changed in: apport (Ubuntu Focal) Assignee: (unassigned) => cristian swing (sed1991s) ** Changed in: apport (Ubuntu Jammy) Assignee: (unassigned) => cristian swing (sed1991s) -- 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/1964828 Title: /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError: 'CasperMD5json' Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: New Status in apport source package in Jammy: Fix Released Bug description: [Impact] If the user reports a bug and rejects to enter the root password for collecting information (like the CasperMD5json), the Ubuntu add_info hook will fail with a stack trace. The remaining code for collecting more information is not executed. So the resulting bug reports will be less helpful. The check_for_disk_error call is not reached and therefore skipped. [Test Plan] 1. Install Ubuntu (e.g. from ubuntu-22.04-desktop-amd64.iso) 2. Open a terminal 3. Run: ubuntu-bug -f 4. Select "installer" and click on OK 5. Click on "abort" when ask for the password 6. The terminal should not show a stacktrace [Where problems could occur] The changed code is the Ubuntu add_info hook. So this hook could fail due to a regression or reveal bugs in the later code path. The later code path could cause more more load on the users machine (but only when the user wants to report the issue). Apport will catch failing add_info hooks and store the failure in the report. [Orinial report] ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 81, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 1016, in attach_casper_md5check check = json.loads(report['CasperMD5json']) File "/usr/lib/python3.10/collections/__init__.py", line 1102, in __getitem__ raise KeyError(key) KeyError: 'CasperMD5json' kubuntu@kubuntu:~$ Gtk-Message: 21:22:43.923: Failed to load module "colorreload-gtk-module" ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperVersion: 1.467 CurrentDesktop: KDE Date: Mon Mar 14 21:22:23 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220314) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1964828/+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 2017743] Re: Wrong Timezone Name - Kyiv instead of Kiev
I tried to reproduce your problem, but everything that I tested worked on Ubuntu 22.04: ``` $ sudo timedatectl set-timezone Europe/Kyiv $ ls -alh /etc/localtime lrwxrwxrwx 1 root root 31 Apr 26 15:15 /etc/localtime -> /usr/share/zoneinfo/Europe/Kyiv $ cat /etc/timezone Europe/Kyiv $ timedatectl Local time: Mi 2023-04-26 15:18:45 EEST Universal time: Mi 2023-04-26 12:18:45 UTC RTC time: Mi 2023-04-26 12:18:44 Time zone: Europe/Kyiv (EEST, +0300) System clock synchronized: yes NTP service: active RTC in local TZ: no ``` The proposed workaround in the linked forum to set TZ=Europe/Kiev when calling teams indicate that the problem is in MS Teams. ** Summary changed: - Wrong Timezone Name - Kyiv instead of Kiev + Wrong Timezone Name - Kyiv instead of Kiev in MS Teams ** Summary changed: - Wrong Timezone Name - Kyiv instead of Kiev in MS Teams + Wrong Timezone Name in MS Teams - Kyiv instead of Kiev ** Changed in: tzdata (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017743 Title: Wrong Timezone Name in MS Teams - Kyiv instead of Kiev Status in tzdata package in Ubuntu: Incomplete Bug description: To solve MS Teams Calendar issue on Ubuntu, we need to update the time zone: > sudo timedatectl set-timezone Europe/Kyiv but it doesn't work, the only in old-fashioned spell 'kiev' works: > sudo timedatectl set-timezone Europe/Kiev So, is it possible to add the time zone 'Europe/Kyiv' to the list? Links: https://answers.microsoft.com/en-us/msteams/forum/all/wrong-time-in- the-ms-teams-linux-app/c14eced8-3b55-4be8-b0c2-a01015072df2 https://en.wikipedia.org/wiki/Kyiv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2017743/+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 1991975] Re: dev file system is mounted without nosuid or noexec
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Released ** Changed in: systemd (Ubuntu Focal) Status: Invalid => Fix Released ** Changed in: systemd (Ubuntu Jammy) Status: Invalid => Fix Released ** Changed in: systemd (Ubuntu Focal) Assignee: (unassigned) => cristian swing (sed1991s) ** Changed in: systemd (Ubuntu Jammy) Assignee: (unassigned) => cristian swing (sed1991s) ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => cristian swing (sed1991s) -- 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/1991975 Title: dev file system is mounted without nosuid or noexec Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in linux source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [ SRU TEMPLATE ] [ Impact ] * nosuid, and noexec bits are not set on /dev * This has the potential for nefarious actors to use this as an avenue for attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more discussion around this. * It is not best security practice. [ Test Plan ] 1.Boot a Canonical Supplied EC2 instance 2.Check the mount options for /dev. 3.You will notice the lack of nosuid and noexec on /dev. [ Where problems could occur ] * As of 2022/10/06, I need to test this, but don't know how to build -aws flavored ubuntu kernels. Instructions welcome. I'm holding off on adding SRU tags until I can actually get this tested. * If this is applied to non initramfs-less kernels it could potentially cause a regression for very old hardware that does nefarious things with memory. For a larger discussion about that see: https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/ * Low risk if a driver depends on /dev allowing suid or exec this might prevent boot. That being said, all kernels that have been booting with an initramfs have been getting nosuid, and noexec set so hopefully we can consider that risk fairly well tested. [ Other Info ] * Patch is accepted into 5.17, and will drop out quickly * Any server booting with an initramfs already has nosuid, and noexec set, so hopefully <<< ORIGINAL TEXT This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon
[Touch-packages] [Bug 2017743] Re: Wrong Timezone Name - Kyiv instead of Kiev
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2017743 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017743 Title: Wrong Timezone Name - Kyiv instead of Kiev Status in tzdata package in Ubuntu: New Bug description: To solve MS Teams Calendar issue on Ubuntu, we need to update the time zone: > sudo timedatectl set-timezone Europe/Kyiv but it doesn't work, the only in old-fashioned spell 'kiev' works: > sudo timedatectl set-timezone Europe/Kiev So, is it possible to add the time zone 'Europe/Kyiv' to the list? Links: https://answers.microsoft.com/en-us/msteams/forum/all/wrong-time-in- the-ms-teams-linux-app/c14eced8-3b55-4be8-b0c2-a01015072df2 https://en.wikipedia.org/wiki/Kyiv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2017743/+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 2017743] Re: Wrong Timezone Name - Kyiv instead of Kiev
Wrong package, the "system" timezones are handled by tzdata ** Package changed: libdatetime-timezone-perl (Ubuntu) => tzdata (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017743 Title: Wrong Timezone Name - Kyiv instead of Kiev Status in tzdata package in Ubuntu: New Bug description: To solve MS Teams Calendar issue on Ubuntu, we need to update the time zone: > sudo timedatectl set-timezone Europe/Kyiv but it doesn't work, the only in old-fashioned spell 'kiev' works: > sudo timedatectl set-timezone Europe/Kiev So, is it possible to add the time zone 'Europe/Kyiv' to the list? Links: https://answers.microsoft.com/en-us/msteams/forum/all/wrong-time-in- the-ms-teams-linux-app/c14eced8-3b55-4be8-b0c2-a01015072df2 https://en.wikipedia.org/wiki/Kyiv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2017743/+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 2017770] [NEW] "Enter code on ubuntu.com/pro/attach" is not clickable URL like everything else
Public bug reported: Enter code on ubuntu.com/pro/attach is not a clickable url. however ubuntu.com/pro and "register new account" are. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2023-04-26 12-05-00.png" https://bugs.launchpad.net/bugs/2017770/+attachment/5668913/+files/Screenshot%20from%202023-04-26%2012-05-00.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/2017770 Title: "Enter code on ubuntu.com/pro/attach" is not clickable URL like everything else Status in software-properties package in Ubuntu: New Bug description: Enter code on ubuntu.com/pro/attach is not a clickable url. however ubuntu.com/pro and "register new account" are. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2017770/+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 2007730] Re: Unpatched CVE in Jammy
A fix for this issue has been released, as per USN-6039-1 (https://ubuntu.com/security/notices/USN-6039-1). ** Changed in: openssl (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2007730 Title: Unpatched CVE in Jammy Status in openssl package in Ubuntu: Fix Released Bug description: CVE-2022-3996 (7.5) is showing as in need of patching in Jammy. I was able to apply the upstream patch without modification to the source. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2007730/+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 2017762] Re: GLX apps fail to run in X2Go remote desktop
** Also affects: mesa (Debian) Importance: Undecided Status: New ** Also affects: mesa (Fedora) Importance: Undecided Status: New -- 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/2017762 Title: GLX apps fail to run in X2Go remote desktop Status in mesa package in Ubuntu: New Status in mesa package in Debian: New Status in mesa package in Fedora: New Bug description: GLX apps fail to run on Ubuntu LTS 22.04. They used to run fine on Ubuntu LTS 20.04 USER@COMPUTER:~$ glxgears X Error of failed request: GLXUnsupportedPrivateRequest Major opcode of failed request: 143 (GLX) Minor opcode of failed request: 17 (X_GLXVendorPrivateWithReply) Serial number of failed request: 32 Current serial number in output stream: 32 USER@COMPUTER:~$ glxinfo name of display: :50.0 X Error of failed request: GLXUnsupportedPrivateRequest Major opcode of failed request: 143 (GLX) Minor opcode of failed request: 17 (X_GLXVendorPrivateWithReply) Serial number of failed request: 27 Current serial number in output stream: 27 Manually downgrading to mesa-21.x from the Ubuntu 20.04 repository solves the problem: sudo apt purge libgl1-amber-dri sudo dpkg -i \ libegl-mesa0_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libgbm1_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libglapi-mesa_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libglx-mesa0_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libxatracker2_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ mesa-va-drivers_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ mesa-vdpau-drivers_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ mesa-vulkan-drivers_21.2.6-0ubuntu0.1~20.04.2_amd64.deb sudo apt-mark hold \ libegl-mesa0 \ libgl1-mesa-dri \ libglapi-mesa \ libglx-mesa0 \ mesa-va-drivers \ mesa-vdpau-drivers \ mesa-vulkan-drivers \ libgbm1 \ libxatracker2 There's also a discussion about this on the X2Go user list, but no solution so far (just the workaround to downgrade to mesa 21.x): https://lists.x2go.org/pipermail/x2go-user/2022-June/006825.html Similar problems on Ubuntu 23.-04 with mesa 23.x, although there the error message is different. Tested on several computers with connections from different Linux, Windows and Mac clients. All show the same behaviour: no go with mesa-22.x on Ubuntu-22.04. Success with downgraded mesa. How to replicate: - install ubuntu 22.04 on real hardware or on a VM (tested with QEMU/virt-manager) - apt-get install x2goserver-xsession mesa-utils - make X2Go connection from another client to new install - run 'glxinfo' -> GLX error - downgrade mesa to v. 21.x -> no GLX error ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.108.03 Thu Oct 20 05:10:45 UTC 2022 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: XFCE Date: Wed Apr 26 10:41:42 2023 DistUpgraded: 2022-05-12 16:08:31,041 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/510.108.03, 5.19.0-38-generic, x86_64: installed nvidia/510.108.03, 5.19.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204GL [Quadro M4000] [10de:13f1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM204GL [Quadro M4000] [10de:1153] InstallationDate: Installed on 2017-03-24 (2223 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Precision WorkStation 690 ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=UUID=a6888b05-975d-4ffe-9cf1-a37038661267 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to jammy on 2022-05-12 (348
[Touch-packages] [Bug 2017762] [NEW] GLX apps fail to run in X2Go remote desktop
Public bug reported: GLX apps fail to run on Ubuntu LTS 22.04. They used to run fine on Ubuntu LTS 20.04 USER@COMPUTER:~$ glxgears X Error of failed request: GLXUnsupportedPrivateRequest Major opcode of failed request: 143 (GLX) Minor opcode of failed request: 17 (X_GLXVendorPrivateWithReply) Serial number of failed request: 32 Current serial number in output stream: 32 USER@COMPUTER:~$ glxinfo name of display: :50.0 X Error of failed request: GLXUnsupportedPrivateRequest Major opcode of failed request: 143 (GLX) Minor opcode of failed request: 17 (X_GLXVendorPrivateWithReply) Serial number of failed request: 27 Current serial number in output stream: 27 Manually downgrading to mesa-21.x from the Ubuntu 20.04 repository solves the problem: sudo apt purge libgl1-amber-dri sudo dpkg -i \ libegl-mesa0_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libgbm1_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libglapi-mesa_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libglx-mesa0_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libxatracker2_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ mesa-va-drivers_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ mesa-vdpau-drivers_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ mesa-vulkan-drivers_21.2.6-0ubuntu0.1~20.04.2_amd64.deb sudo apt-mark hold \ libegl-mesa0 \ libgl1-mesa-dri \ libglapi-mesa \ libglx-mesa0 \ mesa-va-drivers \ mesa-vdpau-drivers \ mesa-vulkan-drivers \ libgbm1 \ libxatracker2 There's also a discussion about this on the X2Go user list, but no solution so far (just the workaround to downgrade to mesa 21.x): https://lists.x2go.org/pipermail/x2go-user/2022-June/006825.html Similar problems on Ubuntu 23.-04 with mesa 23.x, although there the error message is different. Tested on several computers with connections from different Linux, Windows and Mac clients. All show the same behaviour: no go with mesa-22.x on Ubuntu-22.04. Success with downgraded mesa. How to replicate: - install ubuntu 22.04 on real hardware or on a VM (tested with QEMU/virt-manager) - apt-get install x2goserver-xsession mesa-utils - make X2Go connection from another client to new install - run 'glxinfo' -> GLX error - downgrade mesa to v. 21.x -> no GLX error ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.108.03 Thu Oct 20 05:10:45 UTC 2022 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: XFCE Date: Wed Apr 26 10:41:42 2023 DistUpgraded: 2022-05-12 16:08:31,041 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/510.108.03, 5.19.0-38-generic, x86_64: installed nvidia/510.108.03, 5.19.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204GL [Quadro M4000] [10de:13f1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM204GL [Quadro M4000] [10de:1153] InstallationDate: Installed on 2017-03-24 (2223 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Precision WorkStation 690 ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=UUID=a6888b05-975d-4ffe-9cf1-a37038661267 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to jammy on 2022-05-12 (348 days ago) dmi.bios.date: 04/25/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0MY171 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/25/2008:svnDellInc.:pnPrecisionWorkStation690:pvr:rvnDellInc.:rn0MY171:rvrA01:cvnDellInc.:ct7:cvr:sku: dmi.product.name: Precision WorkStation 690 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.nvidia-graphics-drivers:
[Touch-packages] [Bug 2017677] Re: Unable to drag window by title bar
This bug doesn't just affect window movement (dragging), it also fails to properly select the window, so that it doesn't become the foreground window -- 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/2017677 Title: Unable to drag window by title bar Status in xorg package in Ubuntu: New Bug description: >lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 Intermittent - more often than not this works fine. However, sometimes unable to move window by left-click & drag on the title bar. Not sure what exact conditions are, maybe when alt-tabbing to a different window or when moving onto a different monitor. Upgraded to 23.04 late yesterday and it's happened about 4 times so far today.When it doesn't work - the dragged window just stays still, but relocating the mouse to lower on the window (say the menu bar) resolves the problem. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 25 15:48:44 2023 DistUpgraded: 2023-04-24 20:50:34,905 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 [1558:1413] InstallationDate: Installed on 2021-12-13 (498 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b649 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Entroware Apollo ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=943b6cc2-9015-4dda-8079-67ac161950f9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-24 (0 days ago) dmi.bios.date: 03/26/2018 dmi.bios.release: 5.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02E dmi.board.asset.tag: Tag 12345 dmi.board.name: Apollo dmi.board.vendor: Entroware dmi.board.version: EL02R5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Entroware dmi.chassis.version: N/A dmi.ec.firmware.release: 5.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02E:bd03/26/2018:br5.2:efr5.2:svnEntroware:pnApollo:pvrEL02R5:rvnEntroware:rnApollo:rvrEL02R5:cvnEntroware:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: Apollo dmi.product.sku: Not Applicable dmi.product.version: EL02R5 dmi.sys.vendor: Entroware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2017677/+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 2016597] Re: Tests create ~/.ssh/authorized_keys group writable due to wrong umask
** Changed in: tinyssh (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2016597 Title: Tests create ~/.ssh/authorized_keys group writable due to wrong umask Status in systemd package in Ubuntu: Invalid Status in tinyssh package in Ubuntu: In Progress Bug description: Traditionally, the default umask as been 0022, which is still the case on Debian and for the root user on Ubuntu. But for non-root users PAM sets a user's session umask to 0002 by default (/etc/pam.d/common-session*), as defined in "/etc/login.defs" via USERGROUPS_ENAB. tinyssh's sshd will reject connections if ~/.ssh/authorized_key is writable by group/other. The test case (re-)creates ~/.ssh/authorized_keys by echoing some strings/keys into it, which creates a new file on the default umask, breaking the test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2016597/+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 1968154] Re: Only keep 2 kernels
If those are your only two kernels both should be kept. If you have a higher versioned kernel, it's correct that 1100 is removed. That's a feature, not a bug. Also don't do that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1968154 Title: Only keep 2 kernels Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Released Status in apt source package in Focal: Fix Released Status in apt source package in Impish: Fix Released Bug description: [Impact] APT currently keeps 3 kernels or even 4 in some releases. Our boot partition is sized for a steady state of 2 kernels + 1 new one being unpacked, hence users run out of space and new kernels fail to install, upgrade runs might abort in the middle. It's not nice. [Test plan] 1. Have two kernels installed (let's call them version 3, 2) 2. Check that both kernels are not autoremovable 3. Install an old kernel (let's call it 1), and mark it automatic 4. Check that 1 will be autoremovable (apt autoremove -s) 5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s) 6. Actually remove 2 7. Reboot into 3 and check that both 1 and 3 are now not autoremovable [Where problems could occur] We could keep the wrong kernels installed that the user did not expect. We remove the requirement to keep the most recently installed version, previously recorded in APT::LastInstalledKernel, to achieve this, as we had 3 hard requirements so far: 1. keep booted kernel 2. keep highest version 3. keep most recently installed 1 can't be removed as it would break running systems, 2 is what you definitely want to keep. During normal system lifetime, the most recently installed kernel is the same as the highest version, so 2==3, and there are no changes to behavior. Likewise, if you most recently installed an older kernel manually for debugging, it would be manually installed and not subject to removal, even if the rule is dropped. The behavior really only changes if you install an older kernel, and then mark it auto - that older kernel becomes automatically removable immediately after it is marked as auto. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1968154/+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 2017734] Re: package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to install/upgrade: triggers looping, abandoned
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/2017734 Title: package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to install/upgrade: triggers looping, abandoned Status in gdk-pixbuf package in Ubuntu: New Bug description: Upgrade from Ubuntu 22.10 to 23.04 on iMac 5k 2014 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Apr 26 08:57:37 2023 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2023-01-24 (91 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to lunar on 2023-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/2017734/+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 2017734] [NEW] package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: Upgrade from Ubuntu 22.10 to 23.04 on iMac 5k 2014 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Apr 26 08:57:37 2023 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2023-01-24 (91 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to lunar on 2023-04-26 (0 days ago) ** Affects: gdk-pixbuf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/2017734 Title: package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to install/upgrade: triggers looping, abandoned Status in gdk-pixbuf package in Ubuntu: New Bug description: Upgrade from Ubuntu 22.10 to 23.04 on iMac 5k 2014 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Apr 26 08:57:37 2023 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2023-01-24 (91 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to lunar on 2023-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/2017734/+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
