[Touch-packages] [Bug 1956126] Re: Why is the full xorg package being installed in Noble?
** Summary changed: - Why is the full xorg package being installed in Mantic? + Why is the full xorg package being installed in Noble? ** Tags removed: lunar ** Tags added: noble -- 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/1956126 Title: Why is the full xorg package being installed in Noble? Status in ubuntu-meta package in Ubuntu: New Status in xorg package in Ubuntu: Triaged Bug description: xorg is a required dependency of ubuntu-desktop and ubuntu-desktop- minimal. It requires the package x11-apps and xorg-docs-core. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1956126/+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 2044061] Re: [amdgpu] Green vertical and horizontal lines appearing since update
The amdgpu kernel driver here doesn't seem to be from Ubuntu so we can't track its bugs here. Please consider uninstalling the drivers that are presumably from AMD, then reboot and report new bugs to Ubuntu for any issues you find. ** Changed in: linux-hwe-6.2 (Ubuntu) Status: New => Invalid ** Changed in: mesa (Ubuntu) Status: New => Invalid -- 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/2044061 Title: [amdgpu] Green vertical and horizontal lines appearing since update Status in linux-hwe-6.2 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Bug description: Did sudo apt update && upgrade, now getting vertical and horizontal visual artifacts -Tried installing amd drivers -Tried using an older kernel Still no luck; definitely 100% not a hardware issue, machine is dual boot and they do not appear on the windows side. It's related to the update. It occurs particularly frequently if I'm writing code or moving windows around. Attaching a picture to try and show it (it's hard to catch on pictures and I don't think it shows up in a screen shot). It's very annoying. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 21:30:01 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: amdgpu/6.2.4-1683306.22.04, 6.2.0-36-generic, x86_64: installed amdgpu/6.2.4-1683306.22.04, 6.2.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Radeon RX 580 Armor 4G OC [1462:3418] InstallationDate: Installed on 2023-10-30 (21 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Micro-Star International Co., Ltd MS-7B86 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic root=UUID=6628c08f-0884-4517-a532-a5ba1ff5653e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M.70 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450-A PRO MAX (MS-7B86) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 4.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 4.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM.70:bd06/17/2020:br5.14:svnMicro-StarInternationalCo.,Ltd:pnMS-7B86:pvr4.0:rvnMicro-StarInternationalCo.,Ltd:rnB450-APROMAX(MS-7B86):rvr4.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr4.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B86 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 4.0 dmi.sys.vendor: Micro-Star International Co., Ltd version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2044061/+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 2045196] Re: [amdgpu] Two monitors have night light, one does not
Thanks for the bug report. Please try logging into Wayland instead. There is a menu in the corner of the login screen where you can select Ubuntu (which is Wayland) or Ubuntu on Xorg. Also it looks like your kernel driver amdgpu/6.2.4-1683306.22.04 did not come from Ubuntu so please also try uninstalling that driver (which presumably came from AMD?). ** Summary changed: - two monitors have night light, one does not + [amdgpu] Two monitors have night light, one does not ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Incomplete ** Tags added: amdgpu gamma nightlight -- 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/2045196 Title: [amdgpu] Two monitors have night light, one does not Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: Two monitors have night light, one does not. It's on a scheduler (although I don't think the scheduler is turning it off properly once it's on, either) for sunset and sunrise. Including a screen shot. Tried turning it off and on again in display settings to no avail. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 29 16:43:52 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: amdgpu/6.2.4-1683306.22.04, 6.2.0-36-generic, x86_64: installed amdgpu/6.2.4-1683306.22.04, 6.2.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Radeon RX 580 Armor 4G OC [1462:3418] InstallationDate: Installed on 2023-10-30 (30 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Micro-Star International Co., Ltd MS-7B86 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=UUID=6628c08f-0884-4517-a532-a5ba1ff5653e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M.70 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450-A PRO MAX (MS-7B86) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 4.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 4.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM.70:bd06/17/2020:br5.14:svnMicro-StarInternationalCo.,Ltd:pnMS-7B86:pvr4.0:rvnMicro-StarInternationalCo.,Ltd:rnB450-APROMAX(MS-7B86):rvr4.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr4.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B86 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 4.0 dmi.sys.vendor: Micro-Star International Co., Ltd version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/2045196/+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 2032825] Re: classless routes served by DHCP not in installer/BusyBox
[Expired for isc-dhcp (Ubuntu) because there has been no activity for 60 days.] ** Changed in: isc-dhcp (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/2032825 Title: classless routes served by DHCP not in installer/BusyBox Status in casper package in Ubuntu: Expired Status in isc-dhcp package in Ubuntu: Expired Bug description: Hi, we have many installation with two or more network interfaces. The standard ist classless routes DHCP Option 121. This ist functional for SLES und RHEL Installations, but not for ubuntu installation. The bug ist with all version of ubuntu, namely we use currently ubuntu20 LTS and ubuntu22 LTS. After PXE booting, kernel und initial Ramdisk, the installer become IP and Nameserver and so on, but not a default GW IP, because of classless. So this installation cannot reach other server, for example foreman. Please fix this in BusyBox, this bug ist open for serveral years. Hope for a fast response, Hartmut Koptein To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/2032825/+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 2032825] Re: classless routes served by DHCP not in installer/BusyBox
[Expired for casper (Ubuntu) because there has been no activity for 60 days.] ** Changed in: casper (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/2032825 Title: classless routes served by DHCP not in installer/BusyBox Status in casper package in Ubuntu: Expired Status in isc-dhcp package in Ubuntu: Expired Bug description: Hi, we have many installation with two or more network interfaces. The standard ist classless routes DHCP Option 121. This ist functional for SLES und RHEL Installations, but not for ubuntu installation. The bug ist with all version of ubuntu, namely we use currently ubuntu20 LTS and ubuntu22 LTS. After PXE booting, kernel und initial Ramdisk, the installer become IP and Nameserver and so on, but not a default GW IP, because of classless. So this installation cannot reach other server, for example foreman. Please fix this in BusyBox, this bug ist open for serveral years. Hope for a fast response, Hartmut Koptein To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/2032825/+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 2045196] Re: two monitors have night light, one does not
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2045196 Title: two monitors have night light, one does not Status in xorg package in Ubuntu: New Bug description: Two monitors have night light, one does not. It's on a scheduler (although I don't think the scheduler is turning it off properly once it's on, either) for sunset and sunrise. Including a screen shot. Tried turning it off and on again in display settings to no avail. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 29 16:43:52 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: amdgpu/6.2.4-1683306.22.04, 6.2.0-36-generic, x86_64: installed amdgpu/6.2.4-1683306.22.04, 6.2.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Radeon RX 580 Armor 4G OC [1462:3418] InstallationDate: Installed on 2023-10-30 (30 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Micro-Star International Co., Ltd MS-7B86 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=UUID=6628c08f-0884-4517-a532-a5ba1ff5653e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M.70 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450-A PRO MAX (MS-7B86) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 4.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 4.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM.70:bd06/17/2020:br5.14:svnMicro-StarInternationalCo.,Ltd:pnMS-7B86:pvr4.0:rvnMicro-StarInternationalCo.,Ltd:rnB450-APROMAX(MS-7B86):rvr4.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr4.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B86 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 4.0 dmi.sys.vendor: Micro-Star International Co., Ltd version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2045196/+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 2045196] [NEW] two monitors have night light, one does not
You have been subscribed to a public bug: Two monitors have night light, one does not. It's on a scheduler (although I don't think the scheduler is turning it off properly once it's on, either) for sunset and sunrise. Including a screen shot. Tried turning it off and on again in display settings to no avail. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 29 16:43:52 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: amdgpu/6.2.4-1683306.22.04, 6.2.0-36-generic, x86_64: installed amdgpu/6.2.4-1683306.22.04, 6.2.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Radeon RX 580 Armor 4G OC [1462:3418] InstallationDate: Installed on 2023-10-30 (30 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Micro-Star International Co., Ltd MS-7B86 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=UUID=6628c08f-0884-4517-a532-a5ba1ff5653e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M.70 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450-A PRO MAX (MS-7B86) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 4.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 4.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM.70:bd06/17/2020:br5.14:svnMicro-StarInternationalCo.,Ltd:pnMS-7B86:pvr4.0:rvnMicro-StarInternationalCo.,Ltd:rnB450-APROMAX(MS-7B86):rvr4.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr4.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B86 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 4.0 dmi.sys.vendor: Micro-Star International Co., Ltd version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- two monitors have night light, one does not https://bugs.launchpad.net/bugs/2045196 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2029464] Re: A stack overflow in GNU Tar
@kerneldude - do you know if MITRE ever assigned a CVE for this? ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/2029464 Title: A stack overflow in GNU Tar Status in tar package in Ubuntu: New Bug description: A stack overflow vulnerability exists in GNU Tar up to including v1.34, as far as I can see, Ubuntu is using v1.3. The bug exists in the function xattr_decoder() in xheader.c, where alloca() is used and it may overflow the stack if a sufficiently long xattr key is used. The vulnerability can be triggered when extracting a tar/pax archive that contains such a long xattr key. Vulnerable code: https://git.savannah.gnu.org/cgit/tar.git/tree/src/xheader.c?h=release_1_34#n1723 PoC tar archive is attached in a zip archive to reduce the size. I reported the vulnerability yesterday to GNU Tar maintainers and they replied that the issue was fixed in the version that was released two weeks ago: "Sergey fixed that bug here: https://git.savannah.gnu.org/cgit/tar.git/commit/?id=a339f05cd269013fa133d2f148d73f6f7d4247e4 and the fix appears in tar 1.35, released July 18. " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/2029464/+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 2044625] Re: package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to install/upgrade: зацикливание триггеров, отмена работы
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/2044625 Title: package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to install/upgrade: зацикливание триггеров, отмена работы Status in gdk-pixbuf package in Ubuntu: New Bug description: ubuntu update to lunar lobster version ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126 Uname: Linux 5.15.0-89-generic x86_64 ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Nov 26 02:02:30 2023 ErrorMessage: зацикливание триггеров, отмена работы InstallationDate: Installed on 2023-11-25 (0 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0ubuntu0.1 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to install/upgrade: зацикливание триггеров, отмена работы UpgradeStatus: Upgraded to lunar on 2023-11-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/2044625/+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 2032851] Update Released
The verification of the Stable Release Update for apparmor has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2032851 Title: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new apparmor package pre-installation script subprocess returned error exit status 1 Status in apparmor package in Ubuntu: Fix Released Status in apparmor source package in Focal: Fix Released Bug description: [ Impact ] * During an apparmor package upgrade, the cache files were deleted, but there could also be directories under /etc/apparmor.d/cache/ which the pre installation scripts did not account for. The upgrade would then fail with the following error message because it would not be able to remove the directories: package:apparmor:2.12-4ubuntu5.3 Preparing to unpack .../16-apparmor_2.13.3-7ubuntu5.2_amd64.deb ... rm: cannot remove '/etc/apparmor.d/cache/bf9d6da9.0': Is a directory dpkg: error processing archive /tmp/apt-dpkg-install-InP0fz/16-apparmor_2.13.3-7ubuntu5.2_amd64.deb (--unpack): new apparmor package pre-installation script subprocess returned error exit status 1 ErrorMessage: new apparmor package pre-installation script subprocess returned error exit status 1 [ Test Plan ] * On a bionic machine, create a directory under /etc/apparmor.d/cache sudo mkdir /etc/apparmor.d/cache/test * To simulate a system upgrade to focal, you can run the following steps 1. Add the focal archive sudo bash -c "cat
[Touch-packages] [Bug 2032851] Re: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new apparmor package pre-installation script subprocess returned error exit status 1
This bug was fixed in the package apparmor - 2.13.3-7ubuntu5.3 --- apparmor (2.13.3-7ubuntu5.3) focal; urgency=medium * apparmor.preinst: recursively remove cache directories during a upgrade. (LP: #2032851) -- Georgia Garcia Tue, 10 Oct 2023 09:20:12 -0300 ** Changed in: apparmor (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2032851 Title: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new apparmor package pre-installation script subprocess returned error exit status 1 Status in apparmor package in Ubuntu: Fix Released Status in apparmor source package in Focal: Fix Released Bug description: [ Impact ] * During an apparmor package upgrade, the cache files were deleted, but there could also be directories under /etc/apparmor.d/cache/ which the pre installation scripts did not account for. The upgrade would then fail with the following error message because it would not be able to remove the directories: package:apparmor:2.12-4ubuntu5.3 Preparing to unpack .../16-apparmor_2.13.3-7ubuntu5.2_amd64.deb ... rm: cannot remove '/etc/apparmor.d/cache/bf9d6da9.0': Is a directory dpkg: error processing archive /tmp/apt-dpkg-install-InP0fz/16-apparmor_2.13.3-7ubuntu5.2_amd64.deb (--unpack): new apparmor package pre-installation script subprocess returned error exit status 1 ErrorMessage: new apparmor package pre-installation script subprocess returned error exit status 1 [ Test Plan ] * On a bionic machine, create a directory under /etc/apparmor.d/cache sudo mkdir /etc/apparmor.d/cache/test * To simulate a system upgrade to focal, you can run the following steps 1. Add the focal archive sudo bash -c "cat
[Touch-packages] [Bug 1801762] Re: Dual-signed things should be easy to verify with one key
** Changed in: ubuntu-keyring (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1801762 Title: Dual-signed things should be easy to verify with one key Status in apt package in Ubuntu: New Status in debmirror package in Ubuntu: New Status in gnupg2 package in Ubuntu: New Status in ubuntu-keyring package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: As part of Ubuntu key rotation strategy, we rely on dual-signing (inline, or detached) such that validation with at least one key available in a keyring should be trusted, without using web-of-trust. However, it seems to be only correctly so far implemented by the apt's gpgv method. Ideally, we should ship an easy enough to use the helper that is `like gpgv` to use, and possibly reusing apt's gpgv code and/or exposing it via apt-key's verify. The problem seems to be that 1 good sig + 1 no public key available, results in gpgv exiting with 2, instead of 0 or 1. Ideally it should be easy enough to use gpgv/gpg to verify that at least one signature is good, and decrypt/extract signed contents only. More details and reproducers to follow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1801762/+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 2045186] Re: nmcli is script unfriendly
** Description changed: Ubuntu 20.04, Linux Mint 20.3, amd64 network-manager 1.22.10-1ubuntu2.3 + + $ nmcli -v + nmcli tool, version 1.22.10 I wanted to script nmcli to make configuration of WiFi of IoT device easy but it is not an easy task. I assume this is a bug in nmcli design, not specific to Ubuntu... The problem. IoT devices with WiFi has to be configured in some way. WiFi parameters could be hardcoded in the code or there could be a way to configure WiFi in other way, like that device is switched to AP mode and user can connect and configure the device. ESP32 devices have WiFi Manager library for WiFi provisioning https://dronebotworkshop.com/wifimanager/ A nice example of such device is NerdMiner based on ESP32, https://github.com/BitMaker-hub/NerdMiner_v2 NerdMiner in WiFi provisioning mode creates WiFi AP with SSID NerdMinerAP and WiFi password is MineYourCoins. I found it really boring to configure this device manually and I tried to script it. It is boring to wait until user notebook founds WiFi "NerdMinerAP, it can take a minute or two, so I tried to use nmcli to automate the process... Issues: 1) I know I want to connect to AP NerdMinerAP but until notebook founds it, I cannot do that. There is no way to force nmcli to wait for NerdMinerAP: ``` $ nmcli --wait 120 dev wifi connect NerdMinerAP; echo $? Error: No network with SSID 'NerdMinerAP' found. 10 $ # NerdMinerAP is visible, nmcli can connect $ nmcli --wait 120 dev wifi connect NerdMinerAP; echo $? Device 'wlo1' successfully activated with '7d333cdb-87e0-409b-9c98-9ef63b5c331c'. 0 ``` 2) nmcli dev wifi scan returns always "Success" and error code 10. NerdMinerAP is not available: ``` $ nmcli dev wifi list | grep NerdMinerAP; nmcli dev wifi list bssid NerdMinerAP; echo $? Success 10 ``` NerdMinerAP is visible, error code is 10, again :-(: ``` $ nmcli dev wifi list | grep NerdMinerAP; nmcli dev wifi list bssid NerdMinerAP; echo $? 86:FC:E6:11:22:33 NerdMinerAP Infra 1 135 Mbit/s 90 ▂▄▆█ WPA2 Success 10 ``` --- It is possible to script that action but it is not as easy as it could be. This is a working solution: ``` #!/bin/sh BSSID="NerdMinerAP" [ -n "$1" ] && BSSID="$1" # wait until provisioning AP is visible.. while sleep 2; do echo "INFO: Waiting for WiFi $BSSID..." R="$(nmcli dev wifi list 2>/dev/null | grep $BSSID)" [ -n "$R" ] && break #nmcli device wifi rescan ssid "$BSSID" 2>/dev/null done # We have found it, connect to it! echo "INFO: WiFi $BSSID detected, connecting..." nmcli dev wifi connect "$BSSID" # show connection details nmcli connection show --active nmcli dev wifi show # show QR code!! password is shown... ``` --- Other working solution, try to connect again and again... ``` #!/bin/sh BSSID="NerdMinerAP" [ -n "$1" ] && BSSID="$1" while sleep 2; do echo "INFO: Waiting for WiFi $BSSID..." nmcli dev wifi connect "$BSSID" 2>/dev/null && break nmcli device wifi rescan ssid "$BSSID" 2>/dev/null done echo "INFO: Connected to WiFi $BSSID" nmcli connection show --active nmcli dev wifi show # show QR code!! password is shown... ``` This one works too but time from time the script ends with an error: ``` INFO: Waiting for WiFi NerdMinerAP... Error: Connection activation failed: (0) No reason given. ``` ** Description changed: Ubuntu 20.04, Linux Mint 20.3, amd64 network-manager 1.22.10-1ubuntu2.3 + ``` $ nmcli -v nmcli tool, version 1.22.10 + ``` I wanted to script nmcli to make configuration of WiFi of IoT device easy but it is not an easy task. I assume this is a bug in nmcli design, not specific to Ubuntu... The problem. IoT devices with WiFi has to be configured in some way. WiFi parameters could be hardcoded in the code or there could be a way to configure WiFi in other way, like that device is switched to AP mode and user can connect and configure the device. ESP32 devices have WiFi Manager library for WiFi provisioning https://dronebotworkshop.com/wifimanager/ A nice example of such device is NerdMiner based on ESP32, https://github.com/BitMaker-hub/NerdMiner_v2 NerdMiner in WiFi provisioning mode creates WiFi AP with SSID NerdMinerAP and WiFi password is MineYourCoins. I found it really boring to configure this device manually and I tried to script it. It is boring to wait until user notebook founds WiFi "NerdMinerAP, it can take a minute or two, so I tried to use nmcli to automate the process... Issues: 1) I know I want to connect to AP NerdMinerAP but until notebook founds it, I cannot do that. There is no way to force nmcli to wait for NerdMinerAP: ``` $ nmcli --wait 120 dev wifi connect NerdMinerAP; echo $? Error: No network with SSID
[Touch-packages] [Bug 2045186] Re: nmcli is script unfriendly
** Description changed: Ubuntu 20.04, Linux Mint 20.3, amd64 network-manager 1.22.10-1ubuntu2.3 I wanted to script nmcli to make configuration of WiFi of IoT device easy but it is not an easy task. I assume this is a bug in nmcli design, not specific to Ubuntu... The problem. IoT devices with WiFi has to be configured in some way. WiFi parameters could be hardcoded in the code or there could be a way to configure WiFi in other way, like that device is switched to AP mode and user can connect and configure the device. ESP32 devices have WiFi Manager library for WiFi provisioning https://dronebotworkshop.com/wifimanager/ A nice example of such device is NerdMiner based on ESP32, https://github.com/BitMaker-hub/NerdMiner_v2 NerdMiner in WiFi provisioning mode creates WiFi AP with SSID NerdMinerAP and WiFi password is MineYourCoins. I found it really boring to configure this device manually and I tried to script it. It is boring to wait until user notebook founds WiFi "NerdMinerAP, it can take a minute or two, so I tried to use nmcli to automate the process... Issues: 1) I know I want to connect to AP NerdMinerAP but until notebook founds it, I cannot do that. There is no way to force nmcli to wait for NerdMinerAP: ``` $ nmcli --wait 120 dev wifi connect NerdMinerAP; echo $? Error: No network with SSID 'NerdMinerAP' found. 10 $ # NerdMinerAP is visible, nmcli can connect $ nmcli --wait 120 dev wifi connect NerdMinerAP; echo $? Device 'wlo1' successfully activated with '7d333cdb-87e0-409b-9c98-9ef63b5c331c'. 0 ``` 2) nmcli dev wifi scan returns always "Success" and error code 10. NerdMinerAP is not available: ``` $ nmcli dev wifi list | grep NerdMinerAP; nmcli dev wifi list bssid NerdMinerAP; echo $? Success 10 ``` NerdMinerAP is visible, error code is 10, again :-(: ``` $ nmcli dev wifi list | grep NerdMinerAP; nmcli dev wifi list bssid NerdMinerAP; echo $? 86:FC:E6:11:22:33 NerdMinerAP Infra 1 135 Mbit/s 90 ▂▄▆█ WPA2 Success 10 ``` --- It is possible to script that action but it is not as easy as it could be. This is a working solution: ``` #!/bin/sh BSSID="NerdMinerAP" [ -n "$1" ] && BSSID="$1" # wait until provisioning AP is visible.. while sleep 2; do echo "INFO: Waiting for WiFi $BSSID..." R="$(nmcli dev wifi list 2> /dev/null | grep $BSSID)" [ -n "$R" ] && break #nmcli device wifi rescan ssid "$BSSID" 2>/dev/null done # We have found it, connect to it! echo "INFO: WiFi $BSSID detected, connecting..." nmcli dev wifi connect "$BSSID" # show connection details nmcli connection show --active nmcli dev wifi show # show QR code!! password is shown... ``` --- Other working solution, try to connect again and again... ``` #!/bin/sh BSSID="NerdMinerAP" [ -n "$1" ] && BSSID="$1" while sleep 2; do echo "INFO: Waiting for WiFi $BSSID..." nmcli dev wifi connect "$BSSID" 2> /dev/null && break #nmcli device wifi rescan ssid "$BSSID" 2>/dev/null done echo "INFO: Connected to WiFi $BSSID" nmcli connection show --active nmcli dev wifi show # show QR code!! password is shown... ``` + + This one works too but time from time the script ends with an error: + + ``` + INFO: Waiting for WiFi NerdMinerAP... + Error: Connection activation failed: (0) No reason given. + ``` ** Description changed: Ubuntu 20.04, Linux Mint 20.3, amd64 network-manager 1.22.10-1ubuntu2.3 I wanted to script nmcli to make configuration of WiFi of IoT device easy but it is not an easy task. I assume this is a bug in nmcli design, not specific to Ubuntu... The problem. IoT devices with WiFi has to be configured in some way. WiFi parameters could be hardcoded in the code or there could be a way to configure WiFi in other way, like that device is switched to AP mode and user can connect and configure the device. ESP32 devices have WiFi Manager library for WiFi provisioning https://dronebotworkshop.com/wifimanager/ A nice example of such device is NerdMiner based on ESP32, https://github.com/BitMaker-hub/NerdMiner_v2 NerdMiner in WiFi provisioning mode creates WiFi AP with SSID NerdMinerAP and WiFi password is MineYourCoins. I found it really boring to configure this device manually and I tried to script it. It is boring to wait until user notebook founds WiFi "NerdMinerAP, it can take a minute or two, so I tried to use nmcli to automate the process... Issues: 1) I know I want to connect to AP NerdMinerAP but until notebook founds it, I cannot do that. There is no way to force nmcli to wait for NerdMinerAP: ``` $ nmcli --wait 120 dev wifi connect NerdMinerAP; echo $? Error: No network with SSID 'NerdMinerAP' found. 10 $ # NerdMinerAP is visible, nmcli can connect $ nmcli --wait 120 dev wifi
[Touch-packages] [Bug 2045186] Re: nmcli is script unfriendly
** Description changed: Ubuntu 20.04, Linux Mint 20.3, amd64 network-manager 1.22.10-1ubuntu2.3 I wanted to script nmcli to make configuration of WiFi of IoT device easy but it is not an easy task. I assume this is a bug in nmcli design, not specific to Ubuntu... The problem. IoT devices with WiFi has to be configured in some way. WiFi parameters could be hardcoded in the code or there could be a way to configure WiFi in other way, like that device is switched to AP mode and user can connect and configure the device. ESP32 devices have WiFi Manager library for WiFi provisioning https://dronebotworkshop.com/wifimanager/ A nice example of such device is NerdMiner based on ESP32, https://github.com/BitMaker-hub/NerdMiner_v2 NerdMiner in WiFi provisioning mode creates WiFi AP with SSID NerdMinerAP and WiFi password is MineYourCoins. I found it really boring to configure this device manually and I tried to script it. It is boring to wait until user notebook founds WiFi "NerdMinerAP, it can take a minute or two, so I tried to use nmcli to automate the process... Issues: 1) I know I want to connect to AP NerdMinerAP but until notebook founds it, I cannot do that. There is no way to force nmcli to wait for NerdMinerAP: ``` $ nmcli --wait 120 dev wifi connect NerdMinerAP; echo $? Error: No network with SSID 'NerdMinerAP' found. 10 $ # NerdMinerAP is visible, nmcli can connect $ nmcli --wait 120 dev wifi connect NerdMinerAP; echo $? Device 'wlo1' successfully activated with '7d333cdb-87e0-409b-9c98-9ef63b5c331c'. 0 ``` 2) nmcli dev wifi scan returns always "Success" and error code 10. NerdMinerAP is not available: ``` $ nmcli dev wifi list | grep NerdMinerAP; nmcli dev wifi list bssid NerdMinerAP; echo $? Success 10 ``` NerdMinerAP is visible, error code is 10, again :-(: ``` $ nmcli dev wifi list | grep NerdMinerAP; nmcli dev wifi list bssid NerdMinerAP; echo $? 86:FC:E6:11:22:33 NerdMinerAP Infra 1 135 Mbit/s 90 ▂▄▆█ WPA2 Success 10 ``` --- It is possible to script that action but it is not as easy as it could be. This is a working solution: ``` #!/bin/sh BSSID="NerdMinerAP" [ -n "$1" ] && BSSID="$1" # wait until provisioning AP is visible.. while sleep 2; do - echo "Waiting for WiFi $BSSID..." + echo "INFO: Waiting for WiFi $BSSID..." R="$(nmcli dev wifi list 2> /dev/null | grep $BSSID)" [ -n "$R" ] && break #nmcli device wifi rescan ssid "$BSSID" 2>/dev/null done # We have found it, connect to it! - echo "WiFi $BSSID detected, connecting..." + echo "INFO: WiFi $BSSID detected, connecting..." nmcli dev wifi connect "$BSSID" # show connection details nmcli connection show --active nmcli dev wifi show # show QR code!! Shows password... ``` + + --- + + Other working solution, try to connect again and again... + + + ``` + #!/bin/sh + + BSSID="NerdMinerAP" + [ -n "$1" ] && BSSID="$1" + + while sleep 2; do + echo "INFO: Waiting for WiFi $BSSID..." + nmcli dev wifi connect "$BSSID" 2> /dev/null && break + #nmcli device wifi rescan ssid "$BSSID" 2>/dev/null + done + echo "INFO: Connected to WiFi $BSSID" + + nmcli connection show --active + nmcli dev wifi show # show QR code!! password is shown... + + + ``` ** Description changed: Ubuntu 20.04, Linux Mint 20.3, amd64 network-manager 1.22.10-1ubuntu2.3 I wanted to script nmcli to make configuration of WiFi of IoT device easy but it is not an easy task. I assume this is a bug in nmcli design, not specific to Ubuntu... The problem. IoT devices with WiFi has to be configured in some way. WiFi parameters could be hardcoded in the code or there could be a way to configure WiFi in other way, like that device is switched to AP mode and user can connect and configure the device. ESP32 devices have WiFi Manager library for WiFi provisioning https://dronebotworkshop.com/wifimanager/ A nice example of such device is NerdMiner based on ESP32, https://github.com/BitMaker-hub/NerdMiner_v2 NerdMiner in WiFi provisioning mode creates WiFi AP with SSID NerdMinerAP and WiFi password is MineYourCoins. I found it really boring to configure this device manually and I tried to script it. It is boring to wait until user notebook founds WiFi "NerdMinerAP, it can take a minute or two, so I tried to use nmcli to automate the process... Issues: 1) I know I want to connect to AP NerdMinerAP but until notebook founds it, I cannot do that. There is no way to force nmcli to wait for NerdMinerAP: ``` $ nmcli --wait 120 dev wifi connect NerdMinerAP; echo $? Error: No network with SSID 'NerdMinerAP' found. 10 $ # NerdMinerAP is visible, nmcli can connect $ nmcli --wait 120 dev wifi connect NerdMinerAP; echo $? Device 'wlo1' successfully activated with
[Touch-packages] [Bug 2045186] Re: nmcli is script unfriendly
** Description changed: Ubuntu 20.04, Linux Mint 20.3, amd64 network-manager 1.22.10-1ubuntu2.3 I wanted to script nmcli to make configuration of WiFi of IoT device easy but it is not an easy task. I assume this is a bug in nmcli design, not specific to Ubuntu... The problem. IoT devices with WiFi has to be configured in some way. WiFi parameters could be hardcoded in the code or there could be a way to configure WiFi in other way, like that device is switched to AP mode and user can connect and configure the device. ESP32 devices have WiFi Manager library for WiFi provisioning https://dronebotworkshop.com/wifimanager/ A nice example of such device is NerdMiner based on ESP32, https://github.com/BitMaker-hub/NerdMiner_v2 NerdMiner in WiFi provisioning mode creates WiFi AP with SSID NerdMinerAP and WiFi password is MineYourCoins. I found it really boring to configure this device manually and I tried to script it. It is boring to wait until user notebook founds WiFi "NerdMinerAP, it can take a minute or two, so I tried to use nmcli to automate the process... Issues: 1) I know I want to connect to AP NerdMinerAP but until notebook founds it, I cannot do that. There is no way to force nmcli to wait for NerdMinerAP: - $ nmcli --wait 120 dev wifi connect NerdMinerAP + $ nmcli --wait 120 dev wifi connect NerdMinerAP; echo $? Error: No network with SSID 'NerdMinerAP' found. + 10 + + $ # NerdMinerAP is visible, nmcli can connect + $ nmcli --wait 120 dev wifi connect NerdMinerAP; echo $? + Device 'wlo1' successfully activated with '7d333cdb-87e0-409b-9c98-9ef63b5c331c'. + 0 2) nmcli dev wifi scan returns always "Success" and error code 10. NerdMinerAP is not available: $ nmcli dev wifi list | grep NerdMinerAP; nmcli dev wifi list bssid NerdMinerAP; echo $? Success 10 NerdMinerAP is visible, error code is 10, again :-(: $ nmcli dev wifi list | grep NerdMinerAP; nmcli dev wifi list bssid NerdMinerAP; echo $? 86:FC:E6:11:22:33 NerdMinerAP Infra 1 135 Mbit/s 90 ▂▄▆█ WPA2 Success 10 --- It is possible to script that action but it is not as easy as it could be. This is a working solution: ``` #!/bin/sh BSSID="NerdMinerAP" [ -n "$1" ] && BSSID="$1" # wait until provisioning AP is visible.. while sleep 2; do echo "Waiting for WiFi $BSSID..." R="$(nmcli dev wifi list 2> /dev/null | grep $BSSID)" [ -n "$R" ] && break #nmcli device wifi rescan ssid "$BSSID" 2>/dev/null done # We have found it, connect to it! echo "WiFi $BSSID detected, connecting..." nmcli dev wifi connect "$BSSID" # show connection details nmcli connection show --active nmcli dev wifi show # show QR code!! Shows password... ``` ** Description changed: Ubuntu 20.04, Linux Mint 20.3, amd64 network-manager 1.22.10-1ubuntu2.3 I wanted to script nmcli to make configuration of WiFi of IoT device easy but it is not an easy task. I assume this is a bug in nmcli design, not specific to Ubuntu... The problem. IoT devices with WiFi has to be configured in some way. WiFi parameters could be hardcoded in the code or there could be a way to configure WiFi in other way, like that device is switched to AP mode and user can connect and configure the device. ESP32 devices have WiFi Manager library for WiFi provisioning https://dronebotworkshop.com/wifimanager/ A nice example of such device is NerdMiner based on ESP32, https://github.com/BitMaker-hub/NerdMiner_v2 NerdMiner in WiFi provisioning mode creates WiFi AP with SSID NerdMinerAP and WiFi password is MineYourCoins. I found it really boring to configure this device manually and I tried to script it. It is boring to wait until user notebook founds WiFi "NerdMinerAP, it can take a minute or two, so I tried to use nmcli to automate the process... Issues: 1) I know I want to connect to AP NerdMinerAP but until notebook founds it, I cannot do that. There is no way to force nmcli to wait for NerdMinerAP: + ``` $ nmcli --wait 120 dev wifi connect NerdMinerAP; echo $? Error: No network with SSID 'NerdMinerAP' found. 10 $ # NerdMinerAP is visible, nmcli can connect $ nmcli --wait 120 dev wifi connect NerdMinerAP; echo $? Device 'wlo1' successfully activated with '7d333cdb-87e0-409b-9c98-9ef63b5c331c'. 0 + ``` 2) nmcli dev wifi scan returns always "Success" and error code 10. NerdMinerAP is not available: + ``` $ nmcli dev wifi list | grep NerdMinerAP; nmcli dev wifi list bssid NerdMinerAP; echo $? Success 10 + ``` NerdMinerAP is visible, error code is 10, again :-(: + ``` $ nmcli dev wifi list | grep NerdMinerAP; nmcli dev wifi list bssid NerdMinerAP; echo $? 86:FC:E6:11:22:33 NerdMinerAP Infra 1 135 Mbit/s 90 ▂▄▆█ WPA2 Success 10 + ``` --- It is possible to script
[Touch-packages] [Bug 2045186] Re: nmcli is script unfriendly
** Description changed: Ubuntu 20.04, Linux Mint 20.3, amd64 network-manager 1.22.10-1ubuntu2.3 I wanted to script nmcli to make configuration of WiFi of IoT device easy but it is not an easy task. I assume this is a bug in nmcli design, not specific to Ubuntu... The problem. IoT devices with WiFi has to be configured in some way. WiFi parameters could be hardcoded in the code or there could be a way to configure WiFi in other way, like that device is switched to AP mode and user can connect and configure the device. ESP32 devices have WiFi Manager library for WiFi provisioning https://dronebotworkshop.com/wifimanager/ A nice example of such device is NerdMiner based on ESP32, https://github.com/BitMaker-hub/NerdMiner_v2 NerdMiner in WiFi provisioning mode creates WiFi AP with SSID NerdMinerAP and WiFi password is MineYourCoins. I found it really boring to configure this device manually and I tried to script it. It is boring to wait until user notebook founds WiFi "NerdMinerAP, it can take a minute or two, so I tried to use nmcli to automate the process... Issues: 1) I know I want to connect to AP NerdMinerAP but until notebook founds it, I cannot do that. There is no way to force nmcli to wait for NerdMinerAP: $ nmcli --wait 120 dev wifi connect NerdMinerAP Error: No network with SSID 'NerdMinerAP' found. 2) nmcli dev wifi scan returns always "Success" and error code 10. NerdMinerAP is not available: $ nmcli dev wifi list | grep NerdMinerAP; nmcli dev wifi list bssid NerdMinerAP; echo $? Success 10 NerdMinerAP is visible, error code is 10, again :-(: $ nmcli dev wifi list | grep NerdMinerAP; nmcli dev wifi list bssid NerdMinerAP; echo $? 86:FC:E6:11:22:33 NerdMinerAP Infra 1 135 Mbit/s 90 ▂▄▆█ WPA2 Success 10 --- It is possible to script that action but it is not as easy as it could be. This is a working solution: ``` #!/bin/sh BSSID="NerdMinerAP" [ -n "$1" ] && BSSID="$1" # wait until provisioning AP is visible.. while sleep 2; do echo "Waiting for WiFi $BSSID..." R="$(nmcli dev wifi list 2> /dev/null | grep $BSSID)" [ -n "$R" ] && break - #nmcli device wifi rescan 2>/dev/null + #nmcli device wifi rescan ssid "$BSSID" 2>/dev/null done # We have found it, connect to it! echo "WiFi $BSSID detected, connecting..." nmcli dev wifi connect "$BSSID" # show connection details nmcli connection show --active nmcli dev wifi show # show QR code!! Shows password... ``` -- 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/2045186 Title: nmcli is script unfriendly Status in network-manager package in Ubuntu: New Bug description: Ubuntu 20.04, Linux Mint 20.3, amd64 network-manager 1.22.10-1ubuntu2.3 I wanted to script nmcli to make configuration of WiFi of IoT device easy but it is not an easy task. I assume this is a bug in nmcli design, not specific to Ubuntu... The problem. IoT devices with WiFi has to be configured in some way. WiFi parameters could be hardcoded in the code or there could be a way to configure WiFi in other way, like that device is switched to AP mode and user can connect and configure the device. ESP32 devices have WiFi Manager library for WiFi provisioning https://dronebotworkshop.com/wifimanager/ A nice example of such device is NerdMiner based on ESP32, https://github.com/BitMaker-hub/NerdMiner_v2 NerdMiner in WiFi provisioning mode creates WiFi AP with SSID NerdMinerAP and WiFi password is MineYourCoins. I found it really boring to configure this device manually and I tried to script it. It is boring to wait until user notebook founds WiFi "NerdMinerAP, it can take a minute or two, so I tried to use nmcli to automate the process... Issues: 1) I know I want to connect to AP NerdMinerAP but until notebook founds it, I cannot do that. There is no way to force nmcli to wait for NerdMinerAP: $ nmcli --wait 120 dev wifi connect NerdMinerAP Error: No network with SSID 'NerdMinerAP' found. 2) nmcli dev wifi scan returns always "Success" and error code 10. NerdMinerAP is not available: $ nmcli dev wifi list | grep NerdMinerAP; nmcli dev wifi list bssid NerdMinerAP; echo $? Success 10 NerdMinerAP is visible, error code is 10, again :-(: $ nmcli dev wifi list | grep NerdMinerAP; nmcli dev wifi list bssid NerdMinerAP; echo $? 86:FC:E6:11:22:33 NerdMinerAP Infra 1 135 Mbit/s 90 ▂▄▆█ WPA2 Success 10 --- It is possible to script that action but it is not as easy as it could be. This is a working solution: ``` #!/bin/sh BSSID="NerdMinerAP" [ -n "$1" ] && BSSID="$1" # wait until provisioning AP is visible.. while sleep 2; do echo
[Touch-packages] [Bug 2045186] [NEW] nmcli is script unfriendly
Public bug reported: Ubuntu 20.04, Linux Mint 20.3, amd64 network-manager 1.22.10-1ubuntu2.3 I wanted to script nmcli to make configuration of WiFi of IoT device easy but it is not an easy task. I assume this is a bug in nmcli design, not specific to Ubuntu... The problem. IoT devices with WiFi has to be configured in some way. WiFi parameters could be hardcoded in the code or there could be a way to configure WiFi in other way, like that device is switched to AP mode and user can connect and configure the device. ESP32 devices have WiFi Manager library for WiFi provisioning https://dronebotworkshop.com/wifimanager/ A nice example of such device is NerdMiner based on ESP32, https://github.com/BitMaker-hub/NerdMiner_v2 NerdMiner in WiFi provisioning mode creates WiFi AP with SSID NerdMinerAP and WiFi password is MineYourCoins. I found it really boring to configure this device manually and I tried to script it. It is boring to wait until user notebook founds WiFi "NerdMinerAP, it can take a minute or two, so I tried to use nmcli to automate the process... Issues: 1) I know I want to connect to AP NerdMinerAP but until notebook founds it, I cannot do that. There is no way to force nmcli to wait for NerdMinerAP: $ nmcli --wait 120 dev wifi connect NerdMinerAP Error: No network with SSID 'NerdMinerAP' found. 2) nmcli dev wifi scan returns always "Success" and error code 10. NerdMinerAP is not available: $ nmcli dev wifi list | grep NerdMinerAP; nmcli dev wifi list bssid NerdMinerAP; echo $? Success 10 NerdMinerAP is visible, error code is 10, again :-(: $ nmcli dev wifi list | grep NerdMinerAP; nmcli dev wifi list bssid NerdMinerAP; echo $? 86:FC:E6:11:22:33 NerdMinerAP Infra 1 135 Mbit/s 90 ▂▄▆█ WPA2 Success 10 --- It is possible to script that action but it is not as easy as it could be. This is a working solution: ``` #!/bin/sh BSSID="NerdMinerAP" [ -n "$1" ] && BSSID="$1" # wait until provisioning AP is visible.. while sleep 2; do echo "Waiting for WiFi $BSSID..." R="$(nmcli dev wifi list 2> /dev/null | grep $BSSID)" [ -n "$R" ] && break #nmcli device wifi rescan 2>/dev/null done # We have found it, connect to it! echo "WiFi $BSSID detected, connecting..." nmcli dev wifi connect "$BSSID" # show connection details nmcli connection show --active nmcli dev wifi show # show QR code!! Shows password... ``` ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Description changed: Ubuntu 20.04, Linux Mint 20.3, amd64 network-manager 1.22.10-1ubuntu2.3 I wanted to script nmcli to make configuration of WiFi of IoT device easy but it is not an easy task. I assume this is a bug in nmcli design, not specific to Ubuntu... The problem. IoT devices with WiFi has to be configured in some way. WiFi parameters could be hardcoded in the code or there could be a way to configure WiFi in other way, like that device is switched to AP mode and user can connect and configure the device. ESP32 devices have WiFi Manager library for WiFi provisioning https://dronebotworkshop.com/wifimanager/ A nice example of such device is NerdMiner based on ESP32, https://github.com/BitMaker-hub/NerdMiner_v2 NerdMiner in WiFi provisioning mode creates WiFi AP with SSID NerdMinerAP and WiFi password is MineYourCoins. I found it really boring to configure this device manually and I tried to script it. It is boring to wait until user notebook founds WiFi "NerdMinerAP, it can take a minute or two, so I tried to use nmcli to automate the process... Issues: 1) I know I want to connect to AP NerdMinerAP but until notebook founds it, I cannot do that. - There is no way to force nmcli to wait for NerMinerAP + There is no way to force nmcli to wait for NerdMinerAP: $ nmcli --wait 120 dev wifi connect NerdMinerAP Error: No network with SSID 'NerdMinerAP' found. 2) nmcli dev wifi scan returns always "Success" and error code 10. NerdMinerAP is not available: $ nmcli dev wifi list | grep NerdMinerAP; nmcli dev wifi list bssid NerdMinerAP; echo $? Success 10 NerdMinerAP is visible, error code is 10, again :-(: $ nmcli dev wifi list | grep NerdMinerAP; nmcli dev wifi list bssid NerdMinerAP; echo $? - 86:FC:E6:11:22:33 NerdMinerAP Infra 1 135 Mbit/s 90 ▂▄▆█ WPA2 + 86:FC:E6:11:22:33 NerdMinerAP Infra 1 135 Mbit/s 90 ▂▄▆█ WPA2 Success 10 --- It is possible to script that action but it is not as easy as it could be. This is a working solution: - ``` #!/bin/sh BSSID="NerdMinerAP" [ -n "$1" ] && BSSID="$1" # wait until provisioning AP is visible.. while sleep 2; do - echo "Waiting for WiFi $BSSID..." - R="$(nmcli dev wifi list 2> /dev/null | grep $BSSID)" - [ -n "$R" ] && break - #nmcli device wifi rescan 2>/dev/null + echo "Waiting for WiFi $BSSID..." +
[Touch-packages] [Bug 2035585] Re: Versions in Ubuntu 20.04, 22.04 and 23.04 are vulnerable to CVE-2023-37329
This bug was fixed in the package gst-plugins-bad1.0 - 1.16.3-0ubuntu1.1 --- gst-plugins-bad1.0 (1.16.3-0ubuntu1.1) focal-security; urgency=medium [ Luís Infante da Câmara ] * SECURITY UPDATE: Heap buffer overflow in dvdspu (LP: #2035585) - debian/patches/CVE-2023-37329-1.patch: Make sure enough data is allocated for the available data. - debian/patches/CVE-2023-37329-2.patch: Avoid integer overflow when checking if enough data is available. - CVE-2023-37329 [ Marc Deslauriers ] * SECURITY UPDATE: integer overflow in MXF file handling - debian/patches/CVE-2023-40474.patch: fix integer overflow causing out of bounds writes when handling invalid uncompressed video in gst/mxf/mxfup.c. - CVE-2023-40474 * SECURITY UPDATE: integer overflow in MXF file handling - debian/patches/CVE-2023-40475.patch: check number of channels for AES3 audio in gst/mxf/mxfd10.c. - CVE-2023-40475 * SECURITY UPDATE: integer overflow in H.265 video parser - debian/patches/CVE-2023-40476.patch: fix possible overflow using max_sub_layers_minus1 in gst-libs/gst/codecparsers/gsth265parser.c. - CVE-2023-40476 * SECURITY UPDATE: MXF demuxer use-after-free - debian/patches/CVE-2023-6.patch: store GstMXFDemuxEssenceTrack in their own fixed allocation in gst/mxf/mxfdemux.*. - CVE-2023-6 -- Marc Deslauriers Tue, 28 Nov 2023 13:33:46 -0500 ** Changed in: gst-plugins-bad1.0 (Ubuntu) Status: Confirmed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-40474 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-40475 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-40476 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-6 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2035585 Title: Versions in Ubuntu 20.04, 22.04 and 23.04 are vulnerable to CVE-2023-37329 Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Bug description: The versions in Ubuntu 20.04, 22.04 and 23.04 are vulnerable to CVE-2023-37329. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/2035585/+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 2037323] Re: gst-plugins-bad1.0 fails to build: netsim test failing
Note to future mdeslaur: re-mashing the retry button will eventually result in the test passing and the build succeeding. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2037323 Title: gst-plugins-bad1.0 fails to build: netsim test failing Status in gst-plugins-bad: New Status in gst-plugins-bad1.0 package in Ubuntu: Triaged Status in gst-plugins-bad1.0 package in Debian: Confirmed Bug description: gst-plugin-bad1.0's elements_netsim build test began failing after July 6 (when 1.22.4 was uploaded) but before August 15. This is a regression caused by a change in one of its build dependencies. === 91/109 === test: elements_netsim start time: 12:04:11 duration: 1.31s result: exit status 2 command: GST_PLUGIN_LOADING_WHITELIST=gstreamer:gst-plugins-base:gst-plugins-good: gst-plugins-ugly:gst-libav:libnice:gst-plugins-bad@/<>/obj-x86_64-linux-gnu GST_PLUGIN_PATH_1_0=/<>/obj-x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu/gstreamer-1.0: /usr/lib/x86_64-linux-gnu/gstreamer-1.0 GST_PLUGIN_SCANNER_1_0=/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner GST_STATE_IGNORE_ELEMENTS='' CK_DEFAULT_TIMEOUT=20 GST_REGISTRY=/<>/obj-x86_64-linux-gnu/tests/check/elements_netsim.registry MALLOC_PERTURB_=119 GST_PLUGIN_SYSTEM_PATH_1_0='' LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/gst-libs/gst/basecamerabinsrc: /<>/obj-x86_64-linux-gnu/gst-libs/gst/uridownloader: /<>/obj-x86_64-linux-gnu/gst-libs/gst/interfaces: /usr/lib/libeatmydata /<>/obj-x86_64-linux-gnu/tests/check/elements_netsim --- stdout --- Running suite(s): netsim Unexpected critical/warning: ../gst/gstpad.c:4427:gst_pad_chain_data_unchecked: Got data flow before stream-start event Stack trace: gst_debug_get_stack_trace (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b3e6db) ?? (/usr/lib/x86_64-linux-gnu/libgstcheck-1.0.so.0.2205.0:0x7f94f8961a9f) g_logv (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f89ddc0c) g_log (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f89ddebf) ?? (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b4a072) ?? (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b4c2c2) gst_pad_push (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b53b44) ?? (/usr/lib/x86_64-linux-gnu/libgstcheck-1.0.so.0.2205.0:0x7f94f8967b62) ?? (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f8a029dd) ?? (/usr/lib/x86_64-linux-gnu/libc.so.6:0x7f94f87fa3e8) ?? (/usr/lib/x86_64-linux-gnu/libc.so.6:0x7f94f887aa28) Unexpected critical/warning: ../gst/gstpad.c:4427:gst_pad_chain_data_unchecked: Got data flow before stream-start event Stack trace: gst_debug_get_stack_trace (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b3e6db) ?? (/usr/lib/x86_64-linux-gnu/libgstcheck-1.0.so.0.2205.0:0x7f94f8961a9f) g_logv (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f89ddc0c) g_log (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f89ddebf) ?? (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b4a072) ?? (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b4c2c2) gst_pad_push (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b53b44) ?? (/usr/lib/x86_64-linux-gnu/libgstcheck-1.0.so.0.2205.0:0x7f94f8967b62) ?? (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f8a029dd) ?? (/usr/lib/x86_64-linux-gnu/libc.so.6:0x7f94f87fa3e8) ?? (/usr/lib/x86_64-linux-gnu/libc.so.6:0x7f94f887aa28) 0%: Checks: 2, Failures: 2, Errors: 0 ../libs/gst/check/gstcheck.c:286:F:general:netsim_stress:0: Unexpected critical/warning: ../gst/gstpad.c:4427:gst_pad_chain_data_unchecked: Got data flow before stream-start event ../libs/gst/check/gstcheck.c:286:F:general:netsim_stress_delayed:0: Unexpected critical/warning: ../gst/gstpad.c:4427:gst_pad_chain_data_unchecked: Got data flow before stream-start event Check suite netsim ran in 0.240s (tests failed: 2) To manage notifications about this bug go to: https://bugs.launchpad.net/gst-plugins-bad/+bug/2037323/+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 1284053] Re: Signature warning should include full repository name/path
*** This bug is a duplicate of bug 1043298 *** https://bugs.launchpad.net/bugs/1043298 ** This bug has been marked a duplicate of bug 1043298 more information about errors on update failure -- 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/1284053 Title: Signature warning should include full repository name/path Status in apt package in Ubuntu: Triaged Bug description: Most people nowadays can collect quite a few APT repositories hosted on the same server (ppa.launchpad.net, for instance). In case the signature check on one of these repositories fails, apt-get just prints this: W: GPG error: http://ppa.launchpad.net saucy Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY Unfortunately, this informs the user only that one of the repositories on ppa.launchpad.net has a missing key. But not which one. It could be any of them. Tracking down the specific signature ( in my example) is difficult so the only practical option is to disable the repositories one by one until the warning disappears. Which is not only annoying to the user but also puts unnecessary load on the servers which get repeatedly hit by 'apt-get update'. I therefore suggest to change the warning to include the full path of the repository. Example: W: GPG error: http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu saucy Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY This would inform the user which repository needs a key. Other options (such as printing the repository's name are also valid, of course). PS: I am aware that apt-add-repository automatically adds the key but this magic only works on Launchpad whereas the problem is one in general. Furthermore, you don't always get to use apt-add-repository for various reasons. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1284053/+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 2044604] Re: package apparmor 2.12-4ubuntu5.3+esm1 installed the 20.04 release, with words, "mer/upgrade: new apparmor package pre-installation script subprocess returned error e
*** This bug is a duplicate of bug 2032851 *** https://bugs.launchpad.net/bugs/2032851 Hi Herb! The fix is already on the way and should be available to you soon. Meanwhile, as a workaround, you can remove the /etc/apparmor.d/cache/e10c1cf9.0 directory with rm -r /etc/apparmor.d/cache/e10c1cf9.0 and try the upgrade again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2044604 Title: package apparmor 2.12-4ubuntu5.3+esm1 installed the 20.04 release, with words, "mer/upgrade: new apparmor package pre-installation script subprocess returned error exit status 1 Status in apparmor package in Ubuntu: New Bug description: rors occurred" did manual reboot. But system just logged out and back in quickly. I pressed start button to reboot, and the system took a half hout to connect until I right clicked the start-page. Then the log-in page appeared and the system came up. h94b@h94b-HP-EliteBook-8460p:~$ dpkg -1 | grep linux-image dpkg: error: unknown option -1 Type dpkg --help for help about installing and deinstalling packages [*]; Use 'apt' or 'aptitude' for user-friendly package management; Type dpkg -Dhelp for a list of dpkg debug flag values; Type dpkg --force-help for a list of forcing options; Type dpkg-deb --help for help about manipulating *.deb files; Options marked [*] produce a lot of output - pipe it through 'less' or 'more' ! h94b@h94b-HP-EliteBook-8460p:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.6 LTS" h94b@h94b-HP-EliteBook-8460p:~$ thank You ProblemType: Package DistroRelease: Ubuntu 20.04 Package: apparmor 2.12-4ubuntu5.3+esm1 ProcVersionSignature: Ubuntu 5.4.0-167.184~18.04.1-generic 5.4.252 Uname: Linux 5.4.0-167-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.29 Architecture: amd64 Date: Sat Nov 25 04:39:23 2023 DuplicateSignature: package:apparmor:2.12-4ubuntu5.3+esm1 Preparing to unpack .../09-apparmor_2.13.3-7ubuntu5.2_amd64.deb ... rm: cannot remove '/etc/apparmor.d/cache/e10c1cf9.0': Is a directory dpkg: error processing archive /tmp/apt-dpkg-install-x2AWLZ/09-apparmor_2.13.3-7ubuntu5.2_amd64.deb (--unpack): new apparmor package pre-installation script subprocess returned error exit status 1 ErrorMessage: new apparmor package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-11-24 (0 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-167-generic root=UUID=4bc5fd69-6854-4ec0-b0bb-a914ce15ecce ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.10 SourcePackage: apparmor Title: package apparmor 2.12-4ubuntu5.3+esm1 failed to install/upgrade: new apparmor package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2023-11-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2044604/+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 2045075] Re: Framework Laptop Expansion Card enabling auto suspend
Since the mentioned commit will be in v255, this will be fixed for Noble when we ship v255. Nothing to do there. I'm just going to mark "invalid" for systemd for that reason. For Jammy, Lunar, and Mantic, we can SRU this change in systemd-hwe. ** Changed in: systemd (Ubuntu) Status: New => Invalid ** Changed in: systemd-hwe (Ubuntu) Status: New => Won't Fix ** Changed in: systemd-hwe (Ubuntu Jammy) Status: New => Triaged ** Changed in: systemd-hwe (Ubuntu Lunar) Status: New => Triaged ** Changed in: systemd-hwe (Ubuntu Mantic) Status: New => Triaged ** Changed in: systemd-hwe (Ubuntu Jammy) Importance: Undecided => Low ** Changed in: systemd-hwe (Ubuntu Lunar) Importance: Undecided => Low ** Changed in: systemd-hwe (Ubuntu Mantic) Importance: Undecided => Low ** Tags added: foundations-todo ** Changed in: systemd-hwe (Ubuntu Jammy) Assignee: (unassigned) => Nick Rosbrook (enr0n) ** Changed in: systemd-hwe (Ubuntu Lunar) Assignee: (unassigned) => Nick Rosbrook (enr0n) ** Changed in: systemd-hwe (Ubuntu Mantic) Assignee: (unassigned) => Nick Rosbrook (enr0n) -- 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/2045075 Title: Framework Laptop Expansion Card enabling auto suspend Status in systemd package in Ubuntu: Invalid Status in systemd-hwe package in Ubuntu: Won't Fix Status in systemd-hwe source package in Jammy: Triaged Status in systemd-hwe source package in Lunar: Triaged Status in systemd-hwe source package in Mantic: Triaged Bug description: Framework provides expansion cards. For the HDMI and DisplayPort, these benefit power management via enabling auto suspend. Ubuntu 22.04.3 LTS 6.1.0-1026-oem systemd 249 (249.11-0ubuntu3.11) # # Framework # # HDMI Expansion Card usb:v32ACp0002* # DisplayPort Expansion Card usb:v32ACp0003* ID_AUTOSUSPEND=1 Commit in question: https://github.com/systemd/systemd/commit/9023630cb7025650aa4d01ee794b0bb68bfdf2c1 When looking at 60-autosuspend.hwdb for Ubuntu 22.04.3, we do not have the additional entry shown above available for HDMI and DisplayPort expansion cards. I'd like to see this added to 22.04 for future inclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2045075/+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 2045159] [NEW] Adt failures for mantic:linux-6.5 kernels
Public bug reported: Investigate why systemds fails for amd64 and armhf. For amd64 https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/s/systemd/20231127_110919_522a6@/log.gz Armfh https://autopkgtest.ubuntu.com/results/autopkgtest- mantic/mantic/armhf/s/systemd/20231127_093549_82e18@/log.gz Note: I have not looked into why it fails, I created the bug ticket so I can come back at it later. Not sure if it's a systemd issue or a kernel issue or both. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Mantic) Importance: Undecided Status: New ** Tags: sru-20231030 ** Tags added: sru-20231030 ** Also affects: systemd (Ubuntu Mantic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2045159 Title: Adt failures for mantic:linux-6.5 kernels Status in systemd package in Ubuntu: New Status in systemd source package in Mantic: New Bug description: Investigate why systemds fails for amd64 and armhf. For amd64 https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/s/systemd/20231127_110919_522a6@/log.gz Armfh https://autopkgtest.ubuntu.com/results/autopkgtest- mantic/mantic/armhf/s/systemd/20231127_093549_82e18@/log.gz Note: I have not looked into why it fails, I created the bug ticket so I can come back at it later. Not sure if it's a systemd issue or a kernel issue or both. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2045159/+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
Re: [Touch-packages] [Bug 2044604] Re: package apparmor 2.12-4ubuntu5.3+esm1 installed the 20.04 release, with words, "mer/upgrade: new apparmor package pre-installation script subprocess returned err
*** This bug is a duplicate of bug 2032851 *** https://bugs.launchpad.net/bugs/2032851 Hi Georgia, Your response is greatly appreciated. Long story short: I have a beautiful dual-boot Ubuntu setup now. I have a 22.04 and an 18.04 on a 500gig hard drive. Really working well. Thanks. HerbPicoski Sent with Proton Mail secure email. On Tuesday, November 28th, 2023 at 6:41 AM, Georgia Garcia <2044...@bugs.launchpad.net> wrote: > *** This bug is a duplicate of bug 2032851 *** > https://bugs.launchpad.net/bugs/2032851 > > ** This bug has been marked a duplicate of bug 2032851 > package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new apparmor > package pre-installation script subprocess returned error exit status 1 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2044604 > > Title: > package apparmor 2.12-4ubuntu5.3+esm1 installed the 20.04 release, > with words, "mer/upgrade: new apparmor package pre-installation script > subprocess returned error exit status 1 > > Status in apparmor package in Ubuntu: > New > > Bug description: > rors occurred" did manual reboot. But system just logged out and back in > quickly. I pressed start button to reboot, and the system took a half hout to > connect until I right clicked the start-page. Then the log-in page appeared > and the system came up. > h94b@h94b-HP-EliteBook-8460p:~$ dpkg -1 | grep linux-image > dpkg: error: unknown option -1 > > Type dpkg --help for help about installing and deinstalling packages [*]; > Use 'apt' or 'aptitude' for user-friendly package management; > Type dpkg -Dhelp for a list of dpkg debug flag values; > Type dpkg --force-help for a list of forcing options; > Type dpkg-deb --help for help about manipulating .deb files; > > Options marked [] produce a lot of output - pipe it through 'less' or 'more' ! > h94b@h94b-HP-EliteBook-8460p:~$ cat /etc/lsb-release > DISTRIB_ID=Ubuntu > DISTRIB_RELEASE=20.04 > DISTRIB_CODENAME=focal > DISTRIB_DESCRIPTION="Ubuntu 20.04.6 LTS" > h94b@h94b-HP-EliteBook-8460p:~$ > > thank You > > ProblemType: Package > DistroRelease: Ubuntu 20.04 > Package: apparmor 2.12-4ubuntu5.3+esm1 > ProcVersionSignature: Ubuntu 5.4.0-167.184~18.04.1-generic 5.4.252 > Uname: Linux 5.4.0-167-generic x86_64 > NonfreeKernelModules: wl > ApportVersion: 2.20.9-0ubuntu7.29 > Architecture: amd64 > Date: Sat Nov 25 04:39:23 2023 > DuplicateSignature: > package:apparmor:2.12-4ubuntu5.3+esm1 > Preparing to unpack .../09-apparmor_2.13.3-7ubuntu5.2_amd64.deb ... > rm: cannot remove '/etc/apparmor.d/cache/e10c1cf9.0': Is a directory > dpkg: error processing archive > /tmp/apt-dpkg-install-x2AWLZ/09-apparmor_2.13.3-7ubuntu5.2_amd64.deb > (--unpack): > new apparmor package pre-installation script subprocess returned error exit > status 1 > ErrorMessage: new apparmor package pre-installation script subprocess > returned error exit status 1 > InstallationDate: Installed on 2023-11-24 (0 days ago) > InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 > (20210915) > ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-167-generic > root=UUID=4bc5fd69-6854-4ec0-b0bb-a914ce15ecce ro quiet splash vt.handoff=1 > Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, > 3.8.2-0ubuntu2 > PythonDetails: N/A > RelatedPackageVersions: > dpkg 1.19.7ubuntu3.2 > apt 2.0.10 > SourcePackage: apparmor > Title: package apparmor 2.12-4ubuntu5.3+esm1 failed to install/upgrade: new > apparmor package pre-installation script subprocess returned error exit > status 1 > UpgradeStatus: Upgraded to focal on 2023-11-25 (0 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2044604/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2044604 Title: package apparmor 2.12-4ubuntu5.3+esm1 installed the 20.04 release, with words, "mer/upgrade: new apparmor package pre-installation script subprocess returned error exit status 1 Status in apparmor package in Ubuntu: New Bug description: rors occurred" did manual reboot. But system just logged out and back in quickly. I pressed start button to reboot, and the system took a half hout to connect until I right clicked the start-page. Then the log-in page appeared and the system came up. h94b@h94b-HP-EliteBook-8460p:~$ dpkg -1 | grep linux-image dpkg: error: unknown option -1 Type dpkg --help for help about installing and deinstalling packages [*]; Use 'apt' or 'aptitude' for user-friendly package management; Type dpkg -Dhelp for a list of dpkg debug flag values; Type dpkg --force-help for a list of forcing options; Type dpkg-deb --help for help about manipulating *.deb files; Options marked [*] produce a lot of output - pipe it through 'less' or 'more' !
[Touch-packages] [Bug 2026230] Re: libnetplan integration breaks "cloned-mac-address" special values
Fixed in v0.107 https://github.com/canonical/netplan/releases/tag/0.107 ** Changed in: netplan Status: Fix Committed => 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/2026230 Title: libnetplan integration breaks "cloned-mac-address" special values Status in netplan: Fix Released Status in netplan.io package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Invalid Bug description: I received an error from apport about a programme not working. I collected the data to submit. Hope this helps. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: network-manager 1.42.6-2ubuntu1 Uname: Linux 6.2.0-24-generic x86_64 Architecture: amd64 Date: Wed Jul 5 23:11:14 2023 ExecutablePath: /usr/sbin/NetworkManager ExecutableTimestamp: 1687429583 ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) Signal: 6 SourcePackage: network-manager UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2026230/+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 2045075] Re: Framework Laptop Expansion Card enabling auto suspend
** Also affects: systemd-hwe (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: systemd-hwe (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: systemd-hwe (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: systemd-hwe (Ubuntu Lunar) Importance: Undecided Status: New ** No longer affects: systemd (Ubuntu Jammy) ** No longer affects: systemd (Ubuntu Lunar) ** No longer affects: systemd (Ubuntu Mantic) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2045075 Title: Framework Laptop Expansion Card enabling auto suspend Status in systemd package in Ubuntu: New Status in systemd-hwe package in Ubuntu: New Status in systemd-hwe source package in Jammy: New Status in systemd-hwe source package in Lunar: New Status in systemd-hwe source package in Mantic: New Bug description: Framework provides expansion cards. For the HDMI and DisplayPort, these benefit power management via enabling auto suspend. Ubuntu 22.04.3 LTS 6.1.0-1026-oem systemd 249 (249.11-0ubuntu3.11) # # Framework # # HDMI Expansion Card usb:v32ACp0002* # DisplayPort Expansion Card usb:v32ACp0003* ID_AUTOSUSPEND=1 Commit in question: https://github.com/systemd/systemd/commit/9023630cb7025650aa4d01ee794b0bb68bfdf2c1 When looking at 60-autosuspend.hwdb for Ubuntu 22.04.3, we do not have the additional entry shown above available for HDMI and DisplayPort expansion cards. I'd like to see this added to 22.04 for future inclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2045075/+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 2036253] Re: FTBFS: missing strl* symbols fail the build
** Changed in: heimdal (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2036253 Title: FTBFS: missing strl* symbols fail the build Status in heimdal package in Ubuntu: In Progress Status in heimdal package in Debian: New Bug description: See ubuntu-devel thread[1] and mantic rebuild report[2]. dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libkafs0-heimdal/DEBIAN/symbols doesn't match completely debian/libkafs0-heimdal.symbols --- debian/libkafs0-heimdal.symbols (libkafs0-heimdal_7.8.git20221117.28daf24+dfsg-3ubuntu1_amd64) +++ dpkg-gensymbolshoPgEa 2023-09-05 02:37:15.654111977 + @@ -12,7 +12,7 @@ _kafs_get_cred@Base 1.4.0+git20110226 _kafs_realm_of_cell@Base 1.4.0+git20110226 _kafs_resolve_debug@Base 1.4.0+git20110226 - _kafs_strlcpy@Base 1.4.0+git20110226 +#MISSING: 7.8.git20221117.28daf24+dfsg-3ubuntu1# _kafs_strlcpy@Base 1.4.0+git20110226 k_afs_cell_of_file@Base 1.4.0+git20110226 k_hasafs@Base 1.4.0+git20110226 k_hasafs_recheck@Base 1.4.0+git20110226 dh_makeshlibs: error: failing due to earlier errors make[1]: *** [debian/rules:18: override_dh_makeshlibs] Error 25 This one might need a fix similar to the krb5 one[3]. 1. https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042784.html 2. https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20230830-mantic-mantic.html#ubuntu-server-team 3. https://launchpad.net/ubuntu/+source/krb5/1.20.1-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2036253/+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 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)
** Tags removed: verification-needed-jammy-linux-lowlatency-hwe-6.5
** Tags added: verification-done-jammy-linux-lowlatency-hwe-6.5
--
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/2016908
Title:
udev fails to make prctl() syscall with apparmor=0 (as used by maas by
default)
Status in AppArmor:
Fix Released
Status in MAAS:
Fix Released
Status in maas-images:
Invalid
Status in apparmor package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Invalid
Status in apparmor source package in Lunar:
Invalid
Status in linux source package in Lunar:
Fix Released
Status in systemd source package in Lunar:
Invalid
Bug description:
I'm assuming the image being used for these deploys is 20230417 or
20230417.1 based on the fact that I saw a 6.2 kernel being used which
I don't believe was part of the 20230319 serial. I don't have access
to the maas server, so I can't directly check any log files.
MAAS Version: 3.3.2
Here's where the serial log indicates it can't download the squashfs. The
full log is attached as scobee-lunar-no-squashfs.log (there are some other
console message intermixed):
no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf
/run/net6
-*.conf
::
root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi
date/squa[ 206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes,
fsverity
=yes
shfs
:: mount_squash downloading
http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0
4/lunar/candidate/squashfs to /root.tmp.img
Connecting to 10.229.32.21:5248 (10.229.32.21:5248)
wget: can't connect to remote host (10.229.32.21): Network is unreachable
:: mount -t squashfs -o loop '/root.tmp.img' '/root.tmp'
mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory
done.
Still gathering logs and info and will update as I go.
Kernel Bug / Apparmor
reproducer
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd
$ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'
#start the VM
Starting systemd-udevd version 252.5-2ubuntu3
Spawning shell within the initramfs
BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) udevadm info --export-db
Failed to set death signal: Invalid argument
Observe that udevadm fails to setup death signal, with in systemd code
is this
https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process-
util.c#L1252
if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT))
if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ?
SIGINT : SIGTERM) < 0) {
log_full_errno(prio, errno, "Failed to set death
signal: %m");
_exit(EXIT_FAILURE);
}
workaround set kernel commandline to `apparmor=1`
MAAS bug
Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor.
Even for deployment and commisioning.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2016908/+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 2038433] Re: systemd autopkgtest regression on arm64 and s390x on mantic
The first container reboot fails because seeding takes too long (which
is bug 1878225). Then the hack kicks in and a second image build is
attempted with also fails. The hack masks the problematic services
9811s Created symlink /etc/systemd/system/snapd.service → /dev/null.
9817s Created symlink /etc/systemd/system/snapd.seeded.service → /dev/null.
but the subsequent reboot still times out. Huh?
--
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/2038433
Title:
systemd autopkgtest regression on arm64 and s390x on mantic
Status in linux package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
New
Status in linux source package in Mantic:
Confirmed
Status in systemd source package in Mantic:
New
Bug description:
tests-in-lxd seems to fail to download the lxd image used for the test (or
something similar), looking at the log:
...
Publishing instance: Image pack: 85% (5.51MB/s)
Instance published with fingerprint:
83b511be44395f2afc7d4d1ee0708cb18834c8b15cb208c9d218964ed8479114
6845s autopkgtest [09:11:14]: starting date and time: 2023-10-03 09:11:14+
6845s autopkgtest [09:11:14]: version 5.28ubuntu1
6845s autopkgtest [09:11:14]: host autopkgtest; command line:
/usr/bin/autopkgtest -U -B . --test-name=unit-tests -- lxd
autopkgtest/ubuntu/mantic/arm64
7063s : failure: (down) ['mktemp', '--directory', '--tmpdir',
'autopkgtest.XX'] failed (exit status 1, stderr '')
7063s autopkgtest [09:14:52]: ERROR: testbed failure: unexpected eof from the
testbed
7063s autopkgtest [09:14:52]: test tests-in-lxd: ---]
7064s autopkgtest [09:14:53]: test tests-in-lxd: - - - - - - - - - - results
- - - - - - - - - -
7064s tests-in-lxd FAIL non-zero exit status 1
2:40 PM
...
This introduces a regression that is blocking the promotion of new
kernels in Mantic.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: systemd 253.5-1ubuntu6
ProcVersionSignature: Ubuntu 6.5.0-5.5.1-lowlatency 6.5.0
Uname: Linux 6.5.0-5-lowlatency x86_64
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 4 14:38:15 2023
InstallationDate: Installed on 2023-09-25 (9 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-lowlatency
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/01/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 2.04
dmi.board.asset.tag: Default string
dmi.board.name: G1621-02
dmi.board.vendor: GPD
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.ec.firmware.release: 2.3
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.04:bd09/01/2022:br5.19:efr2.3:svnGPD:pnG1621-02:pvrDefaultstring:rvnGPD:rnG1621-02:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: G1621-02
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: GPD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038433/+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
Re: [Touch-packages] [Bug 2041830] Re: /usr/bin/gdb:6:dump_core:internal_vproblem:internal_verror:internal_error_loc:objfile::text_section_offset
How about directly sending a SIGSEGV or a SIGABRT to a working teamviewer process using kill(1) ? That's what I usually do when I test apport crash reporting code, this might trigger the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2041830 Title: /usr/bin/gdb:6:dump_core:internal_vproblem:internal_verror:internal_error_loc:objfile::text_section_offset Status in gdb package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gdb. This problem was most recently seen with package version 14.0.50.20230907-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/e052ff0ad61743594bf64a85ca1e18b6e353025d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2041830/+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 2038433] Re: systemd autopkgtest regression on arm64 and s390x on mantic
2023-11-29T11:00:34.713689+00:00 mantic-test systemd[1]: Reached target
cloud-init.target - Cloud-init target.
2023-11-29T11:00:34.713731+00:00 mantic-test systemd[1]: Startup finished in
5.934s.
2023-11-29T11:00:34.766612+00:00 mantic-test systemd[1]: dmesg.service:
Deactivated successfully.
2023-11-29T11:01:00.318282+00:00 mantic-test systemd[1]:
systemd-hostnamed.service: Deactivated successfully.
2023-11-29T11:01:03.018207+00:00 mantic-test systemd[1]:
systemd-timedated.service: Deactivated successfully.
2023-11-29T11:01:51.230419+00:00 mantic-test systemd[1]: Created slice
user-0.slice - User Slice of UID 0.
2023-11-29T11:01:51.231018+00:00 mantic-test systemd[1]: Starting
user-runtime-dir@0.service - User Runtime Directory /run/user/0...
2023-11-29T11:01:51.235439+00:00 mantic-test systemd[1]: Finished
user-runtime-dir@0.service - User Runtime Directory /run/user/0.
2023-11-29T11:01:51.236741+00:00 mantic-test systemd[1]: Starting
user@0.service - User Manager for UID 0...
--
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/2038433
Title:
systemd autopkgtest regression on arm64 and s390x on mantic
Status in linux package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
New
Status in linux source package in Mantic:
Confirmed
Status in systemd source package in Mantic:
New
Bug description:
tests-in-lxd seems to fail to download the lxd image used for the test (or
something similar), looking at the log:
...
Publishing instance: Image pack: 85% (5.51MB/s)
Instance published with fingerprint:
83b511be44395f2afc7d4d1ee0708cb18834c8b15cb208c9d218964ed8479114
6845s autopkgtest [09:11:14]: starting date and time: 2023-10-03 09:11:14+
6845s autopkgtest [09:11:14]: version 5.28ubuntu1
6845s autopkgtest [09:11:14]: host autopkgtest; command line:
/usr/bin/autopkgtest -U -B . --test-name=unit-tests -- lxd
autopkgtest/ubuntu/mantic/arm64
7063s : failure: (down) ['mktemp', '--directory', '--tmpdir',
'autopkgtest.XX'] failed (exit status 1, stderr '')
7063s autopkgtest [09:14:52]: ERROR: testbed failure: unexpected eof from the
testbed
7063s autopkgtest [09:14:52]: test tests-in-lxd: ---]
7064s autopkgtest [09:14:53]: test tests-in-lxd: - - - - - - - - - - results
- - - - - - - - - -
7064s tests-in-lxd FAIL non-zero exit status 1
2:40 PM
...
This introduces a regression that is blocking the promotion of new
kernels in Mantic.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: systemd 253.5-1ubuntu6
ProcVersionSignature: Ubuntu 6.5.0-5.5.1-lowlatency 6.5.0
Uname: Linux 6.5.0-5-lowlatency x86_64
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 4 14:38:15 2023
InstallationDate: Installed on 2023-09-25 (9 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-lowlatency
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/01/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 2.04
dmi.board.asset.tag: Default string
dmi.board.name: G1621-02
dmi.board.vendor: GPD
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.ec.firmware.release: 2.3
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.04:bd09/01/2022:br5.19:efr2.3:svnGPD:pnG1621-02:pvrDefaultstring:rvnGPD:rnG1621-02:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: G1621-02
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: GPD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038433/+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 2038433] Re: systemd autopkgtest regression on arm64 and s390x on mantic
Ok that's not it. It looks like a container reboot takes longer than 1
min with newer kernels resulting in a timeout error and subsequent
failure.
--
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/2038433
Title:
systemd autopkgtest regression on arm64 and s390x on mantic
Status in linux package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
New
Status in linux source package in Mantic:
Confirmed
Status in systemd source package in Mantic:
New
Bug description:
tests-in-lxd seems to fail to download the lxd image used for the test (or
something similar), looking at the log:
...
Publishing instance: Image pack: 85% (5.51MB/s)
Instance published with fingerprint:
83b511be44395f2afc7d4d1ee0708cb18834c8b15cb208c9d218964ed8479114
6845s autopkgtest [09:11:14]: starting date and time: 2023-10-03 09:11:14+
6845s autopkgtest [09:11:14]: version 5.28ubuntu1
6845s autopkgtest [09:11:14]: host autopkgtest; command line:
/usr/bin/autopkgtest -U -B . --test-name=unit-tests -- lxd
autopkgtest/ubuntu/mantic/arm64
7063s : failure: (down) ['mktemp', '--directory', '--tmpdir',
'autopkgtest.XX'] failed (exit status 1, stderr '')
7063s autopkgtest [09:14:52]: ERROR: testbed failure: unexpected eof from the
testbed
7063s autopkgtest [09:14:52]: test tests-in-lxd: ---]
7064s autopkgtest [09:14:53]: test tests-in-lxd: - - - - - - - - - - results
- - - - - - - - - -
7064s tests-in-lxd FAIL non-zero exit status 1
2:40 PM
...
This introduces a regression that is blocking the promotion of new
kernels in Mantic.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: systemd 253.5-1ubuntu6
ProcVersionSignature: Ubuntu 6.5.0-5.5.1-lowlatency 6.5.0
Uname: Linux 6.5.0-5-lowlatency x86_64
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 4 14:38:15 2023
InstallationDate: Installed on 2023-09-25 (9 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-lowlatency
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/01/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 2.04
dmi.board.asset.tag: Default string
dmi.board.name: G1621-02
dmi.board.vendor: GPD
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.ec.firmware.release: 2.3
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.04:bd09/01/2022:br5.19:efr2.3:svnGPD:pnG1621-02:pvrDefaultstring:rvnGPD:rnG1621-02:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: G1621-02
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: GPD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038433/+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 2038433] Re: systemd autopkgtest regression on arm64 and s390x on mantic
>From my limited testing, it looks like it was introduced in 6.5.0-10.10.
--
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/2038433
Title:
systemd autopkgtest regression on arm64 and s390x on mantic
Status in linux package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
New
Status in linux source package in Mantic:
Confirmed
Status in systemd source package in Mantic:
New
Bug description:
tests-in-lxd seems to fail to download the lxd image used for the test (or
something similar), looking at the log:
...
Publishing instance: Image pack: 85% (5.51MB/s)
Instance published with fingerprint:
83b511be44395f2afc7d4d1ee0708cb18834c8b15cb208c9d218964ed8479114
6845s autopkgtest [09:11:14]: starting date and time: 2023-10-03 09:11:14+
6845s autopkgtest [09:11:14]: version 5.28ubuntu1
6845s autopkgtest [09:11:14]: host autopkgtest; command line:
/usr/bin/autopkgtest -U -B . --test-name=unit-tests -- lxd
autopkgtest/ubuntu/mantic/arm64
7063s : failure: (down) ['mktemp', '--directory', '--tmpdir',
'autopkgtest.XX'] failed (exit status 1, stderr '')
7063s autopkgtest [09:14:52]: ERROR: testbed failure: unexpected eof from the
testbed
7063s autopkgtest [09:14:52]: test tests-in-lxd: ---]
7064s autopkgtest [09:14:53]: test tests-in-lxd: - - - - - - - - - - results
- - - - - - - - - -
7064s tests-in-lxd FAIL non-zero exit status 1
2:40 PM
...
This introduces a regression that is blocking the promotion of new
kernels in Mantic.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: systemd 253.5-1ubuntu6
ProcVersionSignature: Ubuntu 6.5.0-5.5.1-lowlatency 6.5.0
Uname: Linux 6.5.0-5-lowlatency x86_64
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 4 14:38:15 2023
InstallationDate: Installed on 2023-09-25 (9 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-lowlatency
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/01/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 2.04
dmi.board.asset.tag: Default string
dmi.board.name: G1621-02
dmi.board.vendor: GPD
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.ec.firmware.release: 2.3
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.04:bd09/01/2022:br5.19:efr2.3:svnGPD:pnG1621-02:pvrDefaultstring:rvnGPD:rnG1621-02:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: G1621-02
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: GPD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038433/+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 2038433] Re: systemd autopkgtest regression on arm64 and s390x on mantic
So the workaround for the above in systemd/debian/tests/tests-in-lxd is
problematic?
--
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/2038433
Title:
systemd autopkgtest regression on arm64 and s390x on mantic
Status in linux package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
New
Status in linux source package in Mantic:
Confirmed
Status in systemd source package in Mantic:
New
Bug description:
tests-in-lxd seems to fail to download the lxd image used for the test (or
something similar), looking at the log:
...
Publishing instance: Image pack: 85% (5.51MB/s)
Instance published with fingerprint:
83b511be44395f2afc7d4d1ee0708cb18834c8b15cb208c9d218964ed8479114
6845s autopkgtest [09:11:14]: starting date and time: 2023-10-03 09:11:14+
6845s autopkgtest [09:11:14]: version 5.28ubuntu1
6845s autopkgtest [09:11:14]: host autopkgtest; command line:
/usr/bin/autopkgtest -U -B . --test-name=unit-tests -- lxd
autopkgtest/ubuntu/mantic/arm64
7063s : failure: (down) ['mktemp', '--directory', '--tmpdir',
'autopkgtest.XX'] failed (exit status 1, stderr '')
7063s autopkgtest [09:14:52]: ERROR: testbed failure: unexpected eof from the
testbed
7063s autopkgtest [09:14:52]: test tests-in-lxd: ---]
7064s autopkgtest [09:14:53]: test tests-in-lxd: - - - - - - - - - - results
- - - - - - - - - -
7064s tests-in-lxd FAIL non-zero exit status 1
2:40 PM
...
This introduces a regression that is blocking the promotion of new
kernels in Mantic.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: systemd 253.5-1ubuntu6
ProcVersionSignature: Ubuntu 6.5.0-5.5.1-lowlatency 6.5.0
Uname: Linux 6.5.0-5-lowlatency x86_64
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 4 14:38:15 2023
InstallationDate: Installed on 2023-09-25 (9 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-lowlatency
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/01/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 2.04
dmi.board.asset.tag: Default string
dmi.board.name: G1621-02
dmi.board.vendor: GPD
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.ec.firmware.release: 2.3
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.04:bd09/01/2022:br5.19:efr2.3:svnGPD:pnG1621-02:pvrDefaultstring:rvnGPD:rnG1621-02:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: G1621-02
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: GPD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038433/+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 2038433] Re: systemd autopkgtest regression on arm64 and s390x on mantic
Oh -> bug 1878225
--
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/2038433
Title:
systemd autopkgtest regression on arm64 and s390x on mantic
Status in linux package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
New
Status in linux source package in Mantic:
Confirmed
Status in systemd source package in Mantic:
New
Bug description:
tests-in-lxd seems to fail to download the lxd image used for the test (or
something similar), looking at the log:
...
Publishing instance: Image pack: 85% (5.51MB/s)
Instance published with fingerprint:
83b511be44395f2afc7d4d1ee0708cb18834c8b15cb208c9d218964ed8479114
6845s autopkgtest [09:11:14]: starting date and time: 2023-10-03 09:11:14+
6845s autopkgtest [09:11:14]: version 5.28ubuntu1
6845s autopkgtest [09:11:14]: host autopkgtest; command line:
/usr/bin/autopkgtest -U -B . --test-name=unit-tests -- lxd
autopkgtest/ubuntu/mantic/arm64
7063s : failure: (down) ['mktemp', '--directory', '--tmpdir',
'autopkgtest.XX'] failed (exit status 1, stderr '')
7063s autopkgtest [09:14:52]: ERROR: testbed failure: unexpected eof from the
testbed
7063s autopkgtest [09:14:52]: test tests-in-lxd: ---]
7064s autopkgtest [09:14:53]: test tests-in-lxd: - - - - - - - - - - results
- - - - - - - - - -
7064s tests-in-lxd FAIL non-zero exit status 1
2:40 PM
...
This introduces a regression that is blocking the promotion of new
kernels in Mantic.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: systemd 253.5-1ubuntu6
ProcVersionSignature: Ubuntu 6.5.0-5.5.1-lowlatency 6.5.0
Uname: Linux 6.5.0-5-lowlatency x86_64
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 4 14:38:15 2023
InstallationDate: Installed on 2023-09-25 (9 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-lowlatency
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/01/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 2.04
dmi.board.asset.tag: Default string
dmi.board.name: G1621-02
dmi.board.vendor: GPD
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.ec.firmware.release: 2.3
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.04:bd09/01/2022:br5.19:efr2.3:svnGPD:pnG1621-02:pvrDefaultstring:rvnGPD:rnG1621-02:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: G1621-02
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: GPD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038433/+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 2038433] Re: systemd autopkgtest regression on arm64 and s390x on mantic
Is seems the container fails to boot. From a bad run:
9109s autopkgtest [10:39:17]: test tests-in-lxd: [---
9145s 2023-11-28T10:39:50Z INFO Waiting for automatic snapd restart...
9259s lxd 5.19-8635f82 from Canonical** installed
9288s Creating autopkgtest-prepare-jhI
9475s Retrieving image: metadata: 100% (323.81MB/s)
Retrieving image: rootfs: 1% (3.53MB/s)
Retrieving image: rootfs: 100% (8.38MB/s)
Retrieving image: Unpack: 100% (226.67MB/s)
Starting autopkgtest-prepare-jhI
9486s Created symlink /etc/systemd/system/serial-getty@getty.service →
/dev/null.
9490s Failed to connect to bus: No such file or directory
9632s Timed out waiting for container to boot
--
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/2038433
Title:
systemd autopkgtest regression on arm64 and s390x on mantic
Status in linux package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
New
Status in linux source package in Mantic:
Confirmed
Status in systemd source package in Mantic:
New
Bug description:
tests-in-lxd seems to fail to download the lxd image used for the test (or
something similar), looking at the log:
...
Publishing instance: Image pack: 85% (5.51MB/s)
Instance published with fingerprint:
83b511be44395f2afc7d4d1ee0708cb18834c8b15cb208c9d218964ed8479114
6845s autopkgtest [09:11:14]: starting date and time: 2023-10-03 09:11:14+
6845s autopkgtest [09:11:14]: version 5.28ubuntu1
6845s autopkgtest [09:11:14]: host autopkgtest; command line:
/usr/bin/autopkgtest -U -B . --test-name=unit-tests -- lxd
autopkgtest/ubuntu/mantic/arm64
7063s : failure: (down) ['mktemp', '--directory', '--tmpdir',
'autopkgtest.XX'] failed (exit status 1, stderr '')
7063s autopkgtest [09:14:52]: ERROR: testbed failure: unexpected eof from the
testbed
7063s autopkgtest [09:14:52]: test tests-in-lxd: ---]
7064s autopkgtest [09:14:53]: test tests-in-lxd: - - - - - - - - - - results
- - - - - - - - - -
7064s tests-in-lxd FAIL non-zero exit status 1
2:40 PM
...
This introduces a regression that is blocking the promotion of new
kernels in Mantic.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: systemd 253.5-1ubuntu6
ProcVersionSignature: Ubuntu 6.5.0-5.5.1-lowlatency 6.5.0
Uname: Linux 6.5.0-5-lowlatency x86_64
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 4 14:38:15 2023
InstallationDate: Installed on 2023-09-25 (9 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-lowlatency
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/01/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 2.04
dmi.board.asset.tag: Default string
dmi.board.name: G1621-02
dmi.board.vendor: GPD
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.ec.firmware.release: 2.3
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.04:bd09/01/2022:br5.19:efr2.3:svnGPD:pnG1621-02:pvrDefaultstring:rvnGPD:rnG1621-02:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: G1621-02
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: GPD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038433/+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 1968912] Re: vim.tiny reports 'E1187: Failed to source defaults.vim' on execution in default install
Looks like we should backport https://salsa.debian.org/vim- team/vim/-/commit/16884ac6857d1499839649f061b966e276122666 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1968912 Title: vim.tiny reports 'E1187: Failed to source defaults.vim' on execution in default install Status in vim package in Ubuntu: Confirmed Bug description: Ubuntu 22.04 When running vim.tiny it says: $ vim.tiny E1187: Failed to source defaults.vim Press ENTER or type command to continue This is due to the defaults.vim file not being available. If you just run it as vi $ vi this message does not appear as vim.tiny runs in compatibility mode. I found mention of this issue in: https://github.com/grml/grml-etc-core/issues/99 The defaults.vim file is provided by the package vim-runtime. I'm unsure what the issue is, if something needs to be in /etc/vim/vimrc.tiny or a /etc/vim/vimrc needs to be provided dpkg claims vimrc is in vim-common, but no file is installed for me from that package, or if vim-runtime needs to be a required package for vim-tiny $ dpkg -S /etc/vim/vimrc vim-common: /etc/vim/vimrc $ ls -al /etc/vim/vimrc ls: cannot access '/etc/vim/vimrc': No such file or directory I discovered this because my .selected-editor was vim.tiny after running crontab -e $ crontab -e Select an editor. To change later, run 'select-editor'. 1. /bin/nano< easiest 2. /usr/bin/vim.tiny 3. /bin/ed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: vim-tiny 2:8.2.3995-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-1005.5-raspi 5.15.30 Uname: Linux 5.15.0-1005-raspi aarch64 ApportVersion: 2.20.11-0ubuntu81 Architecture: arm64 CasperMD5CheckResult: unknown Date: Wed Apr 13 11:56:35 2022 ImageMediaBuild: 20201022 ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1968912/+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
