[Touch-packages] [Bug 2049369] Re: autopkg tests ignored for migration of python3-defaults adding 3.12
There are still regressions in the following packages: cython-legacy/0.29.36-3ubuntu1 (armhf only) cython/3.0.7-2ubuntu1 (armhf only) ipykernel/6.28.0-0ubuntu1 ironic-python-agent/9.1.0-1ubuntu1 (never been in Debian testing) jupyter-client/8.6.0-0ubuntu1 numpy/1:1.24.2-2 python-memory-profiler/0.61-1 python-oslo.versionedobjects/3.2.0-0ubuntu1 (scheduled for auto-removal from Debian testing on 25 January) python-urllib3/2.0.7-1 (armhf only) rich/13.3.1-2 sphinx-autoapi/2.0.0-2 vcr.py/5.1.0-1.1 ** Also affects: cython-legacy (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #1059839 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059839 ** Also affects: cython-legacy (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059839 Importance: Unknown Status: Unknown ** Also affects: cython (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #1059835 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059835 ** Also affects: cython (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059835 Importance: Unknown Status: Unknown ** Also affects: ipykernel (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #1056413 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056413 ** Also affects: ipykernel (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056413 Importance: Unknown Status: Unknown ** Also affects: ironic-python-agent (Ubuntu) Importance: Undecided Status: New ** Also affects: jupyter-client (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #1059658 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059658 ** Also affects: jupyter-client (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059658 Importance: Unknown Status: Unknown ** Also affects: numpy (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #1058456 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058456 ** Also affects: numpy (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058456 Importance: Unknown Status: Unknown ** Also affects: python-memory-profiler (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #1056483 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056483 ** Also affects: python-memory-profiler (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056483 Importance: Unknown Status: Unknown ** Also affects: python-oslo.versionedobjects (Ubuntu) Importance: Undecided Status: New ** Also affects: python-urllib3 (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #1056511 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056511 ** Also affects: python-urllib3 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056511 Importance: Unknown Status: Unknown ** Also affects: rich (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #1056522 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056522 ** Also affects: rich (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056522 Importance: Unknown Status: Unknown ** Also affects: sphinx-autoapi (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #1056529 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056529 ** Also affects: sphinx-autoapi (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056529 Importance: Unknown Status: Unknown ** Also affects: vcr.py (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #1059990 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059990 ** Also affects: vcr.py (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059990 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2049369 Title: autopkg tests ignored for migration of python3-defaults adding 3.12 Status in cython package in Ubuntu: New Status in cython-legacy package in Ubuntu: New Status in ipykernel package in Ubuntu: New Status in ironic-python-agent package in Ubuntu: New Status in jupyter-client package in Ubuntu: New Status in numpy package in Ubuntu: New Status in python-memory-profiler package in Ubuntu: New Status in python-oslo.versionedobjects package in Ubuntu: New Status in python-urllib3 package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Status in rich package in Ubuntu: New Status in sphinx-autoapi package in Ubuntu: New Status in
[Touch-packages] [Bug 2049708] Re: bluez bluetoothd unable to locate executable
Perhaps try a recursive grep for '/usr/lib/bluetooth/bluetoothd' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2049708 Title: bluez bluetoothd unable to locate executable Status in bluez package in Ubuntu: New Bug description: Release: Ubuntu Noble Dev Branch the location of bluetoothd was just changed to /usr/libexec/bluetooth/bluetoothd this causes bluetooth to fail to start since something is still looking for the old location Jan 17 21:23:26 switch systemd[1]: Starting bluetooth.service - Bluetooth service... ░░ Subject: A start job for unit bluetooth.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit bluetooth.service has begun execution. ░░ ░░ The job identifier is 2843. Jan 17 21:23:26 switch (uetoothd)[3245]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDire> Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed to locate executable /usr/lib/bluetooth/bluetoothd: No such file or directory ░░ Subject: Process /usr/lib/bluetooth/bluetoothd could not be executed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The process /usr/lib/bluetooth/bluetoothd could not be executed and failed. ░░ ░░ The error number returned by this process is ERRNO. Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed at step EXEC spawning /usr/lib/bluetooth/bluetoothd: No such file or directory the system service ExecStart location was correctly updated so not sure what still has the old location cat /lib/systemd/system/bluetooth.service [Unit] Description=Bluetooth service Documentation=man:bluetoothd(8) ConditionPathIsDirectory=/sys/class/bluetooth [Service] Type=dbus BusName=org.bluez ExecStart=/usr/libexec/bluetooth/bluetoothd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049708/+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 2043915] Re: Booting into live session results in try/install page white screen
I can't seem to reproduce any such issue with 2024-01-17 here. Please log a new bug, although it might be bug 2049617 as mentioned in https://discourse.ubuntu.com/t/help-with-edubuntu-desktop- installer/41683 -- 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/2043915 Title: Booting into live session results in try/install page white screen Status in ubuntu-desktop-installer: Fix Released Status in mesa package in Ubuntu: Fix Released Bug description: Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into live session results in try/install page white screen.Selecting install from the dash results in same white screen. see the attached screen shot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.487 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Nov 19 07:02:48 2023 LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: subiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+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 2049708] Re: bluez bluetoothd unable to locate executable
You are not. I have rebooted multiple times and continue to get this message in journalctl (yes it's a new entry on each boot). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2049708 Title: bluez bluetoothd unable to locate executable Status in bluez package in Ubuntu: New Bug description: Release: Ubuntu Noble Dev Branch the location of bluetoothd was just changed to /usr/libexec/bluetooth/bluetoothd this causes bluetooth to fail to start since something is still looking for the old location Jan 17 21:23:26 switch systemd[1]: Starting bluetooth.service - Bluetooth service... ░░ Subject: A start job for unit bluetooth.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit bluetooth.service has begun execution. ░░ ░░ The job identifier is 2843. Jan 17 21:23:26 switch (uetoothd)[3245]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDire> Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed to locate executable /usr/lib/bluetooth/bluetoothd: No such file or directory ░░ Subject: Process /usr/lib/bluetooth/bluetoothd could not be executed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The process /usr/lib/bluetooth/bluetoothd could not be executed and failed. ░░ ░░ The error number returned by this process is ERRNO. Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed at step EXEC spawning /usr/lib/bluetooth/bluetoothd: No such file or directory the system service ExecStart location was correctly updated so not sure what still has the old location cat /lib/systemd/system/bluetooth.service [Unit] Description=Bluetooth service Documentation=man:bluetoothd(8) ConditionPathIsDirectory=/sys/class/bluetooth [Service] Type=dbus BusName=org.bluez ExecStart=/usr/libexec/bluetooth/bluetoothd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049708/+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 2043915] Re: Booting into live session results in try/install page white screen
I tried daily build version 2024-01-17, but the bug is still there. Laptop is Fujitsu WUA/H1. The solution is to restart subiquity snap service. https://askubuntu.com/questions/1500457/ubuntu-desktop- installer-24-04-stuck-on- installation?noredirect=1#comment2629138_1500457 -- 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/2043915 Title: Booting into live session results in try/install page white screen Status in ubuntu-desktop-installer: Fix Released Status in mesa package in Ubuntu: Fix Released Bug description: Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into live session results in try/install page white screen.Selecting install from the dash results in same white screen. see the attached screen shot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.487 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Nov 19 07:02:48 2023 LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: subiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+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 2049708] Re: bluez bluetoothd unable to locate executable
Am I correct in assuming the problem goes away after a reboot? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2049708 Title: bluez bluetoothd unable to locate executable Status in bluez package in Ubuntu: New Bug description: Release: Ubuntu Noble Dev Branch the location of bluetoothd was just changed to /usr/libexec/bluetooth/bluetoothd this causes bluetooth to fail to start since something is still looking for the old location Jan 17 21:23:26 switch systemd[1]: Starting bluetooth.service - Bluetooth service... ░░ Subject: A start job for unit bluetooth.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit bluetooth.service has begun execution. ░░ ░░ The job identifier is 2843. Jan 17 21:23:26 switch (uetoothd)[3245]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDire> Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed to locate executable /usr/lib/bluetooth/bluetoothd: No such file or directory ░░ Subject: Process /usr/lib/bluetooth/bluetoothd could not be executed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The process /usr/lib/bluetooth/bluetoothd could not be executed and failed. ░░ ░░ The error number returned by this process is ERRNO. Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed at step EXEC spawning /usr/lib/bluetooth/bluetoothd: No such file or directory the system service ExecStart location was correctly updated so not sure what still has the old location cat /lib/systemd/system/bluetooth.service [Unit] Description=Bluetooth service Documentation=man:bluetoothd(8) ConditionPathIsDirectory=/sys/class/bluetooth [Service] Type=dbus BusName=org.bluez ExecStart=/usr/libexec/bluetooth/bluetoothd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049708/+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 2049708] Re: bluez bluetoothd unable to locate executable
5.71-1ubuntu3: Binary: /usr/libexec/bluetooth/bluetoothd SystemD: system/bluetooth.service:ExecStart=/usr/libexec/bluetooth/bluetoothd So that's consistent, but it sounds like you might have encountered an upgrade bug and your systemd was looking in the old path? I'm guessing there should be a systemd mechanism for refreshing bluetooth.service contents that doesn't require a full system reboot, but also I never encountered this bug in testing recent bluez updates. ** Tags added: noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2049708 Title: bluez bluetoothd unable to locate executable Status in bluez package in Ubuntu: New Bug description: Release: Ubuntu Noble Dev Branch the location of bluetoothd was just changed to /usr/libexec/bluetooth/bluetoothd this causes bluetooth to fail to start since something is still looking for the old location Jan 17 21:23:26 switch systemd[1]: Starting bluetooth.service - Bluetooth service... ░░ Subject: A start job for unit bluetooth.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit bluetooth.service has begun execution. ░░ ░░ The job identifier is 2843. Jan 17 21:23:26 switch (uetoothd)[3245]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDire> Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed to locate executable /usr/lib/bluetooth/bluetoothd: No such file or directory ░░ Subject: Process /usr/lib/bluetooth/bluetoothd could not be executed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The process /usr/lib/bluetooth/bluetoothd could not be executed and failed. ░░ ░░ The error number returned by this process is ERRNO. Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed at step EXEC spawning /usr/lib/bluetooth/bluetoothd: No such file or directory the system service ExecStart location was correctly updated so not sure what still has the old location cat /lib/systemd/system/bluetooth.service [Unit] Description=Bluetooth service Documentation=man:bluetoothd(8) ConditionPathIsDirectory=/sys/class/bluetooth [Service] Type=dbus BusName=org.bluez ExecStart=/usr/libexec/bluetooth/bluetoothd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049708/+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 2049697] Re: GPU not being detected when I try to run any game
Thanks for the bug report. It looks like the i915 kernel graphics driver is crashing a lot, which may or may not be related. Please run these commands in a Terminal: sudo apt install mesa-utils glxinfo > glxinfo.txt and attach the resulting text file here. ** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu) ** Summary changed: - GPU not being detected when I try to run any game + [i915] GPU not being detected when I try to run any game ** Changed in: linux-hwe-6.2 (Ubuntu) Status: New => Incomplete -- 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/2049697 Title: [i915] GPU not being detected when I try to run any game Status in linux-hwe-6.2 package in Ubuntu: Incomplete Bug description: I ran ran apport-bug xorg and it took me here. Trying to figure out an issue where any time I open a game, it crashes and gives the error message "GPU not detected". From everything I've tried it seems like the computer has no problem detecting the GPU and it seems to be working fine, but games are still not working. Any help is appreciated! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-35-generic x86_64 NonfreeKernelModules: wl 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 Jan 17 18:34:19 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: bcmwl/6.30.223.271+bdcom, 6.2.0-35-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:0d22] (rev 08) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:0122] InstallationDate: Installed on 2023-10-25 (84 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Apple Inc. iMac14,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic root=UUID=773b635d-a617-4aa4-8333-273b3ed7b502 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 146.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-031B6874CF7F642A dmi.board.vendor: Apple Inc. dmi.board.version: iMac14,1 dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-031B6874CF7F642A dmi.modalias: dmi:bvnAppleInc.:bvr146.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pniMac14,1:pvr1.0:rvnAppleInc.:rnMac-031B6874CF7F642A:rvriMac14,1:cvnAppleInc.:ct13:cvrMac-031B6874CF7F642A:skuSystemSKU#: dmi.product.family: iMac dmi.product.name: iMac14,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. 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/2049697/+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 2049665] Re: A recent Ubuntu update broke GPU processing in Folding@Home (nVidia GPU)
Thanks for the bug report. It appears you no longer have an nvidia kernel driver for the current kernel version. I'm also not sure if such a newer kernel can be supported by the old nvidia 390 driver. This might just be bug 1975650 so please try reinstalling the driver using the 'Additional Drivers' app or: sudo apt install --reinstall nvidia-driver-390 and reboot. If reinstalling the driver doesn't solve the problem then I wonder if nvidia-390 requires sticking to an older kernel? ** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu) ** Tags added: nvidia ** Tags added: regression-update ** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2049665 Title: A recent Ubuntu update broke GPU processing in Folding@Home (nVidia GPU) Status in linux-hwe-6.5 package in Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: A recent Ubuntu update is keeping the GPU software of Folding at Home (Folding@Home) from working. Past updates have not interfered with it. Expected result: An updated nvidia (proprietary) driver would be installed with the update that continues to work smoothly, provides OpenCL, etc. Actual result: The update caused FAH to disable its GPU processing capabilities. OpenCL is mentioned in the error message, so there may be something wrong with the OpenCL installation in the nVidia v390 package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: wl 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 Jan 17 12:18:33 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: bcmwl/6.30.223.271+bdcom, 6.5.0-14-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK107M [GeForce GT 750M Mac Edition] [10de:0fe9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GK107M [GeForce GT 750M Mac Edition] [106b:011e] InstallationDate: Installed on 2024-01-16 (1 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 05ac:828d Apple, Inc. Bluetooth USB Host Controller Bus 001 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Bus 001 Device 002: ID 05ac:8511 Apple, Inc. FaceTime HD Camera (Built-in) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. iMac14,3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic root=UUID=567a07dc-70f9-441e-a456-151c0da1e7ea ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2022 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 433.140.2.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-77EB7D7DAF985301 dmi.board.vendor: Apple Inc. dmi.board.version: iMac14,3 dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-77EB7D7DAF985301 dmi.modalias: dmi:bvnAppleInc.:bvr433.140.2.0.0:bd04/18/2022:br0.1:svnAppleInc.:pniMac14,3:pvr1.0:rvnAppleInc.:rnMac-77EB7D7DAF985301:rvriMac14,3:cvnAppleInc.:ct13:cvrMac-77EB7D7DAF985301:skuSystemSKU#: dmi.product.family: iMac dmi.product.name: iMac14,3 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. 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.7 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.5/+bug/2049665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 2049712] [NEW] Acer Switch Alpha 12: Keyboard does not wake after suspend
Public bug reported: This is a tablet computer with a detachable keyboard and touchpad. When I close and open the lid, the computer goes to sleep and wakes up as expected, but the entire keyboard portion does not. The backlight stays off, and keys and touchpad are unresponsive. Removing and reattaching the keyboard is the only way to fix the problem. This problem has been present as long as I've had the tablet (2022), with queries on the web going back to when the computer was released (2016). However, I can't find a bug report, so I'm posting one now. Perhaps related: if I try to sleep via the DE (KDE Plasma), command line, or power button, the computer fails to go to sleep. The screen turns back on with the lock screen, and the keyboard backlight does not go off. Release: Kubuntu 23.10 Package version: 1.4.1.19 ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/2049712 Title: Acer Switch Alpha 12: Keyboard does not wake after suspend Status in pm-utils package in Ubuntu: New Bug description: This is a tablet computer with a detachable keyboard and touchpad. When I close and open the lid, the computer goes to sleep and wakes up as expected, but the entire keyboard portion does not. The backlight stays off, and keys and touchpad are unresponsive. Removing and reattaching the keyboard is the only way to fix the problem. This problem has been present as long as I've had the tablet (2022), with queries on the web going back to when the computer was released (2016). However, I can't find a bug report, so I'm posting one now. Perhaps related: if I try to sleep via the DE (KDE Plasma), command line, or power button, the computer fails to go to sleep. The screen turns back on with the lock screen, and the keyboard backlight does not go off. Release: Kubuntu 23.10 Package version: 1.4.1.19 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/2049712/+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 2049708] Re: bluez bluetoothd unable to locate executable
** Description changed: Release: Ubuntu Noble Dev Branch the location of bluetoothd was just changed to /usr/libexec/bluetooth/bluetoothd this causes bluetooth to fail to start since something is still looking for the old location Jan 17 21:23:26 switch systemd[1]: Starting bluetooth.service - Bluetooth service... ░░ Subject: A start job for unit bluetooth.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support - ░░ + ░░ ░░ A start job for unit bluetooth.service has begun execution. - ░░ + ░░ ░░ The job identifier is 2843. Jan 17 21:23:26 switch (uetoothd)[3245]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDire> Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed to locate executable /usr/lib/bluetooth/bluetoothd: No such file or directory ░░ Subject: Process /usr/lib/bluetooth/bluetoothd could not be executed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support - ░░ + ░░ ░░ The process /usr/lib/bluetooth/bluetoothd could not be executed and failed. - ░░ + ░░ ░░ The error number returned by this process is ERRNO. Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed at step EXEC spawning /usr/lib/bluetooth/bluetoothd: No such file or directory + + the system service ExecStart location was correctly updated so not sure + what still has the old location + + cat /lib/systemd/system/bluetooth.service + [Unit] + Description=Bluetooth service + Documentation=man:bluetoothd(8) + ConditionPathIsDirectory=/sys/class/bluetooth + + [Service] + Type=dbus + BusName=org.bluez + ExecStart=/usr/libexec/bluetooth/bluetoothd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2049708 Title: bluez bluetoothd unable to locate executable Status in bluez package in Ubuntu: New Bug description: Release: Ubuntu Noble Dev Branch the location of bluetoothd was just changed to /usr/libexec/bluetooth/bluetoothd this causes bluetooth to fail to start since something is still looking for the old location Jan 17 21:23:26 switch systemd[1]: Starting bluetooth.service - Bluetooth service... ░░ Subject: A start job for unit bluetooth.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit bluetooth.service has begun execution. ░░ ░░ The job identifier is 2843. Jan 17 21:23:26 switch (uetoothd)[3245]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDire> Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed to locate executable /usr/lib/bluetooth/bluetoothd: No such file or directory ░░ Subject: Process /usr/lib/bluetooth/bluetoothd could not be executed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The process /usr/lib/bluetooth/bluetoothd could not be executed and failed. ░░ ░░ The error number returned by this process is ERRNO. Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed at step EXEC spawning /usr/lib/bluetooth/bluetoothd: No such file or directory the system service ExecStart location was correctly updated so not sure what still has the old location cat /lib/systemd/system/bluetooth.service [Unit] Description=Bluetooth service Documentation=man:bluetoothd(8) ConditionPathIsDirectory=/sys/class/bluetooth [Service] Type=dbus BusName=org.bluez ExecStart=/usr/libexec/bluetooth/bluetoothd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049708/+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 2049708] [NEW] bluez bluetoothd unable to locate executable
Public bug reported: Release: Ubuntu Noble Dev Branch the location of bluetoothd was just changed to /usr/libexec/bluetooth/bluetoothd this causes bluetooth to fail to start since something is still looking for the old location Jan 17 21:23:26 switch systemd[1]: Starting bluetooth.service - Bluetooth service... ░░ Subject: A start job for unit bluetooth.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit bluetooth.service has begun execution. ░░ ░░ The job identifier is 2843. Jan 17 21:23:26 switch (uetoothd)[3245]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDire> Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed to locate executable /usr/lib/bluetooth/bluetoothd: No such file or directory ░░ Subject: Process /usr/lib/bluetooth/bluetoothd could not be executed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The process /usr/lib/bluetooth/bluetoothd could not be executed and failed. ░░ ░░ The error number returned by this process is ERRNO. Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed at step EXEC spawning /usr/lib/bluetooth/bluetoothd: No such file or directory the system service ExecStart location was correctly updated so not sure what still has the old location cat /lib/systemd/system/bluetooth.service [Unit] Description=Bluetooth service Documentation=man:bluetoothd(8) ConditionPathIsDirectory=/sys/class/bluetooth [Service] Type=dbus BusName=org.bluez ExecStart=/usr/libexec/bluetooth/bluetoothd ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2049708 Title: bluez bluetoothd unable to locate executable Status in bluez package in Ubuntu: New Bug description: Release: Ubuntu Noble Dev Branch the location of bluetoothd was just changed to /usr/libexec/bluetooth/bluetoothd this causes bluetooth to fail to start since something is still looking for the old location Jan 17 21:23:26 switch systemd[1]: Starting bluetooth.service - Bluetooth service... ░░ Subject: A start job for unit bluetooth.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit bluetooth.service has begun execution. ░░ ░░ The job identifier is 2843. Jan 17 21:23:26 switch (uetoothd)[3245]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDire> Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed to locate executable /usr/lib/bluetooth/bluetoothd: No such file or directory ░░ Subject: Process /usr/lib/bluetooth/bluetoothd could not be executed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The process /usr/lib/bluetooth/bluetoothd could not be executed and failed. ░░ ░░ The error number returned by this process is ERRNO. Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed at step EXEC spawning /usr/lib/bluetooth/bluetoothd: No such file or directory the system service ExecStart location was correctly updated so not sure what still has the old location cat /lib/systemd/system/bluetooth.service [Unit] Description=Bluetooth service Documentation=man:bluetoothd(8) ConditionPathIsDirectory=/sys/class/bluetooth [Service] Type=dbus BusName=org.bluez ExecStart=/usr/libexec/bluetooth/bluetoothd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049708/+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 2049660] Re: screen artifacts especially when changing workspaces
Thanks for the bug report. I've watched the attached screencast a few times and can't see any artifacts in it. This is unsurprising given how screen recording works. You will probably need to take a video of the screen externally, like with a phone. ** Summary changed: - screen artifacts especially when changing workspaces + [HP Pavilion Plus Laptop 14] Screen artifacts especially when changing workspaces ** Summary changed: - [HP Pavilion Plus Laptop 14] Screen artifacts especially when changing workspaces + [amdgpu][HP Pavilion Plus Laptop 14] Screen artifacts especially when changing workspaces ** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu) ** Tags added: amdgpu -- 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/2049660 Title: [amdgpu][HP Pavilion Plus Laptop 14] Screen artifacts especially when changing workspaces Status in linux-hwe-6.5 package in Ubuntu: Incomplete Bug description: Installed fresh, artifacts started after update. Happens when interacting gnome; menus, changing workspaces, etc. Attached screencast ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: zfs 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 Jan 17 17:55:34 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8c21] InstallationDate: Installed on 2024-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: HP HP Pavilion Plus Laptop 14-ey0xxx ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_7trxt5@/vmlinuz-6.5.0-14-generic root=ZFS=rpool/ROOT/ubuntu_7trxt5 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2023 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8C21 dmi.board.vendor: HP dmi.board.version: 87.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 87.27 dmi.modalias: dmi:bvnInsyde:bvrF.02:bd08/10/2023:br15.2:efr87.27:svnHP:pnHPPavilionPlusLaptop14-ey0xxx:pvrType1ProductConfigId:rvnHP:rn8C21:rvr87.27:cvnHP:ct10:cvrChassisVersion:sku8Y7M1EA#ABH: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Plus Laptop 14-ey0xxx dmi.product.sku: 8Y7M1EA#ABH dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7 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.5/+bug/2049660/+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 2049697] [NEW] GPU not being detected when I try to run any game
Public bug reported: I ran ran apport-bug xorg and it took me here. Trying to figure out an issue where any time I open a game, it crashes and gives the error message "GPU not detected". From everything I've tried it seems like the computer has no problem detecting the GPU and it seems to be working fine, but games are still not working. Any help is appreciated! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-35-generic x86_64 NonfreeKernelModules: wl 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 Jan 17 18:34:19 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: bcmwl/6.30.223.271+bdcom, 6.2.0-35-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:0d22] (rev 08) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:0122] InstallationDate: Installed on 2023-10-25 (84 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Apple Inc. iMac14,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic root=UUID=773b635d-a617-4aa4-8333-273b3ed7b502 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 146.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-031B6874CF7F642A dmi.board.vendor: Apple Inc. dmi.board.version: iMac14,1 dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-031B6874CF7F642A dmi.modalias: dmi:bvnAppleInc.:bvr146.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pniMac14,1:pvr1.0:rvnAppleInc.:rnMac-031B6874CF7F642A:rvriMac14,1:cvnAppleInc.:ct13:cvrMac-031B6874CF7F642A:skuSystemSKU#: dmi.product.family: iMac dmi.product.name: iMac14,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. 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 wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2049697 Title: GPU not being detected when I try to run any game Status in xorg package in Ubuntu: New Bug description: I ran ran apport-bug xorg and it took me here. Trying to figure out an issue where any time I open a game, it crashes and gives the error message "GPU not detected". From everything I've tried it seems like the computer has no problem detecting the GPU and it seems to be working fine, but games are still not working. Any help is appreciated! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-35-generic x86_64 NonfreeKernelModules: wl 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 Jan 17 18:34:19 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: bcmwl/6.30.223.271+bdcom, 6.2.0-35-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:0d22] (rev 08) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:0122] InstallationDate: Installed on 2023-10-25 (84 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Apple Inc. iMac14,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic root=UUID=773b635d-a617-4aa4-8333-273b3ed7b502 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 146.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-031B6874CF7F642A dmi.board.vendor: Apple Inc. dmi.board.version:
[Touch-packages] [Bug 2049552] Re: [noble] ftbfs with new zlib 1.3
** Merge proposal linked:
https://code.launchpad.net/~mirespace/ubuntu/+source/openssh/+git/openssh/+merge/458841
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2049552
Title:
[noble] ftbfs with new zlib 1.3
Status in openssh package in Ubuntu:
In Progress
Bug description:
The zlib detection code seems faulty:
checking for possibly buggy zlib... yes
configure: error: *** zlib too old - check config.log ***
Your reported zlib version has known security problems. It's possible your
vendor has fixed these problems without changing the version number. If you
are sure this is the case, you can disable the check by running
"./configure --without-zlib-version-check".
If you are in doubt, upgrade zlib to version 1.2.3 or greater.
See http://www.gzip.org/zlib/ for details.
| #include
| #include
| #include
|
| int
| main (void)
| {
|
| int a=0, b=0, c=0, d=0, n, v;
| n = sscanf(ZLIB_VERSION, "%d.%d.%d.%d", , , , );
| if (n != 3 && n != 4)
| exit(1);
| v = a*100 + b*1 + c*100 + d;
| fprintf(stderr, "found zlib version %s (%d)\n", ZLIB_VERSION, v);
|
| /* 1.1.4 is OK */
| if (a == 1 && b == 1 && c >= 4)
| exit(0);
|
| /* 1.2.3 and up are OK */
| if (v >= 1020300)
| exit(0);
|
| exit(2);
|
| ;
| return 0;
| }
Upstream bug report: https://bugzilla.mindrot.org/show_bug.cgi?id=3604
Upstream fix (untested): https://github.com/openssh/openssh-
portable/commit/cb4ed12ffc332d1f72d054ed92655b5f1c38f621
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2049552/+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 2049552] Re: [noble] ftbfs with new zlib 1.3
Successful building with the fix as patch suggested by Andreas:
https://launchpad.net/~mirespace/+archive/ubuntu/openssh-
lp2049552-ftbfs-with-zlib/+sourcepub/15701298/+listing-archive-extra
Running tests...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2049552
Title:
[noble] ftbfs with new zlib 1.3
Status in openssh package in Ubuntu:
In Progress
Bug description:
The zlib detection code seems faulty:
checking for possibly buggy zlib... yes
configure: error: *** zlib too old - check config.log ***
Your reported zlib version has known security problems. It's possible your
vendor has fixed these problems without changing the version number. If you
are sure this is the case, you can disable the check by running
"./configure --without-zlib-version-check".
If you are in doubt, upgrade zlib to version 1.2.3 or greater.
See http://www.gzip.org/zlib/ for details.
| #include
| #include
| #include
|
| int
| main (void)
| {
|
| int a=0, b=0, c=0, d=0, n, v;
| n = sscanf(ZLIB_VERSION, "%d.%d.%d.%d", , , , );
| if (n != 3 && n != 4)
| exit(1);
| v = a*100 + b*1 + c*100 + d;
| fprintf(stderr, "found zlib version %s (%d)\n", ZLIB_VERSION, v);
|
| /* 1.1.4 is OK */
| if (a == 1 && b == 1 && c >= 4)
| exit(0);
|
| /* 1.2.3 and up are OK */
| if (v >= 1020300)
| exit(0);
|
| exit(2);
|
| ;
| return 0;
| }
Upstream bug report: https://bugzilla.mindrot.org/show_bug.cgi?id=3604
Upstream fix (untested): https://github.com/openssh/openssh-
portable/commit/cb4ed12ffc332d1f72d054ed92655b5f1c38f621
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2049552/+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 2049684] [NEW] libncurses5 missing in mantic/noble
Public bug reported: This package being missing breaks several packages people currently use, and breaks compilation of the Android Open Source Project for every current release. https://answers.launchpad.net/ubuntu/+source/ncurses/+question/707838 Google has started work on deprecating libncurses5 host usage internally (see https://groups.google.com/g/android-building/c/Sv_v2ApJZug), but that will not happen until at least Android 15 (later this year), and does not at all address the previous Android releases that are still supported and get security tags. We need this package to continue building AOSP for those previous releases. ** Affects: ncurses (Ubuntu) Importance: Undecided Status: New ** Tags: mantic noble ** Tags added: mantic noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/2049684 Title: libncurses5 missing in mantic/noble Status in ncurses package in Ubuntu: New Bug description: This package being missing breaks several packages people currently use, and breaks compilation of the Android Open Source Project for every current release. https://answers.launchpad.net/ubuntu/+source/ncurses/+question/707838 Google has started work on deprecating libncurses5 host usage internally (see https://groups.google.com/g/android- building/c/Sv_v2ApJZug), but that will not happen until at least Android 15 (later this year), and does not at all address the previous Android releases that are still supported and get security tags. We need this package to continue building AOSP for those previous releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/2049684/+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 1361131] Re: constantly flashing bright green while typing
** Changed in: nano (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1361131 Title: constantly flashing bright green while typing Status in nano package in Ubuntu: Invalid Bug description: While editing a shell script (.sh file) nano colours trailing spaces bright green. It also considers spaces that have just been typed to be trailing spaces. This results in constant flashing bright green while typing, which is both distracting and annoying. It's at its most ridiculous when typing comments (for which trailing whitespace is obviously completely irrelevant), but is also irritating any time you happen to look at what you're typing. Which for me is, as it happens, all the time. Ideal solution: only display trailing whitespace if the user is not, you know, still typing on that line, with the cursor right there. Easy solution: just shut up about the damn spaces already. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1361131/+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 1539305] Re: package nano 2.4.2-1 failed to install/upgrade: package nano is not ready for configuration cannot configure (current status 'half-installed')
Wily is long gone. ** Changed in: nano (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1539305 Title: package nano 2.4.2-1 failed to install/upgrade: package nano is not ready for configuration cannot configure (current status 'half- installed') Status in nano package in Ubuntu: Invalid Bug description: The program was upgrading to extra package for 15.10 ProblemType: Package DistroRelease: Ubuntu 15.10 Package: nano 2.4.2-1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 Date: Thu Jan 28 17:16:13 2016 DuplicateSignature: package:nano:2.4.2-1:package nano is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package nano is not ready for configuration cannot configure (current status 'half-installed') RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: nano Title: package nano 2.4.2-1 failed to install/upgrade: package nano is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1539305/+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 1998592] Re: in specific situations, nano can eat characters
** Tags added: focal jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1998592 Title: in specific situations, nano can eat characters Status in nano package in Ubuntu: New Bug description: Reproduction recipe: printf "two words\n second line\n" >words nano --ignore --auto --break +,2 words Then press Enter. See how "t" from the first word has *disappeared*. This is wrong. And what is worse: M-U does not bring the eaten letter back. Attached patch has been applied upstream to fix the issue. Please consider applying it to nano-6.2 in Jammy (22.04), and maybe also to nano-4.8 in Focal (20.04). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1998592/+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 782355] Re: Invoke sudo and present password prompt when permission is denied to write to a file
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nano (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/782355 Title: Invoke sudo and present password prompt when permission is denied to write to a file Status in One Hundred Papercuts: Invalid Status in nano: Unknown Status in vim: New Status in nano package in Ubuntu: Confirmed Status in vim package in Ubuntu: Confirmed Bug description: Binary package hint: nano If a user can read but not write a file, as often happens with system configuration files, then they need to be root or use sudo to edit the file. If they forget, they won't notice until they're presented with a permission error when attempting to save. This can result in lost work for new users who don't know how to save the edited file elsewhere. Nano should offer to invoke sudo and present the password prompt to gain the elevated privileges needed in these cases. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/782355/+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 782355] Re: Invoke sudo and present password prompt when permission is denied to write to a file
Upstream Nano doesn't seem interested. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/782355 Title: Invoke sudo and present password prompt when permission is denied to write to a file Status in One Hundred Papercuts: Invalid Status in nano: Unknown Status in vim: New Status in nano package in Ubuntu: Confirmed Status in vim package in Ubuntu: Confirmed Bug description: Binary package hint: nano If a user can read but not write a file, as often happens with system configuration files, then they need to be root or use sudo to edit the file. If they forget, they won't notice until they're presented with a permission error when attempting to save. This can result in lost work for new users who don't know how to save the edited file elsewhere. Nano should offer to invoke sudo and present the password prompt to gain the elevated privileges needed in these cases. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/782355/+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 2026885] Re: nano is not available in Jammy i386
** Tags added: noble ** Summary changed: - nano is not available in Jammy i386 + nano is not available in on i386 ** Summary changed: - nano is not available in on i386 + nano is not available on i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/2026885 Title: nano is not available on i386 Status in nano package in Ubuntu: New Bug description: There is no i386 Nano package in Jammy. I used Nano all the time including in chroots, which is where this reared its ugly head. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/2026885/+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 1922414] Re: Xorg scripts fail with "has_option: command not found"
** Tags removed: 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/1922414 Title: Xorg scripts fail with "has_option: command not found" Status in Light Display Manager: Invalid Status in gdm3 package in Ubuntu: Fix Released Status in lightdm package in Ubuntu: Invalid Status in xorg package in Ubuntu: Confirmed Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1922414/+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 1955136] Re: /etc/X11/Xsession.d/75dbus_dbus-launch: line 9: has_option: command not found
*** This bug is a duplicate of bug 1922414 *** https://bugs.launchpad.net/bugs/1922414 ** This bug has been marked a duplicate of bug 1922414 Xorg scripts fail with "has_option: command not found" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1955136 Title: /etc/X11/Xsession.d/75dbus_dbus-launch: line 9: has_option: command not found Status in dbus package in Ubuntu: Confirmed Bug description: teps to reproduce: 1. Boot 20211217 Ubuntu MATE daily ISO 2. Open ~/.xsession-errors Expected results: * no errors and warnings Actual results: * there are two errors about dbus: /etc/X11/Xsession.d/75dbus_dbus-launch: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dbus-x11 1.12.20-2ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: MATE Date: Fri Dec 17 14:28:01 2021 LiveMediaBuild: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211217) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1955136/+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 2041396] Re: gdb 12.1 generates SIGILL on armhf
Verification Report
===
The test is conducted on an RK3399 device (with 4x ARM Cortex-A53 cores
+ 2x ARM Cortex-A72 cores).
Test (1) original Rust program test (associated-types.rs)
-
GDB 12.1-0ubuntu1~22.04 (unpatched)
Rust 1.70.0+dfsg0ubuntu1~bpo2-0ubuntu0.22.04.2
Test program source: https://github.com/rust-
lang/rust/blob/1.68.2/tests/debuginfo/associated-types.rs
GDB script content:
```
b associated-types.rs:111
r
c
```
Result:
```
Breakpoint 1 at 0x4838: file associated-types.rs, line 111.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
Breakpoint 1, associated_types::assoc_struct (arg=...) at
associated-types.rs:111
111 zzz(); // #break
Program received signal SIGILL, Illegal instruction.
0x00404ec4 in core::slice::cmp::{impl#5}::equal (self=..., other=...)
at library/core/src/slice/cmp.rs:91
91 library/core/src/slice/cmp.rs: No such file or directory.
```
>>> SRU'ed package:
GDB 12.1-0ubuntu1~22.04.1 (patched)
GCC 11.4.0-1ubuntu1~22.04
Result:
```
Breakpoint 1 at 0x4838: file associated-types.rs, line 111.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
Breakpoint 1, associated_types::assoc_struct (arg=...) at
associated-types.rs:111
111 zzz(); // #break
[Inferior 1 (process 3621) exited normally]
```
Test (2) simplified C program test (test.c)
---
GDB 12.1-0ubuntu1~22.04 (unpatched)
GCC 11.4.0-1ubuntu1~22.04
Test program source:
```
__attribute__((target("arm"), noinline))
int thumb_func() {
return 42;
}
__attribute__((target("thumb")))
int main() { return thumb_func(); }
```
Commands:
```
gcc -Og -ggdb3 test.c -o test
printf "b 3\nr\nc\n" > repro
gdb --batch -x ./repro ./test
```
Result:
```
Breakpoint 1 at 0x4d8: file test.c, line 3.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
Breakpoint 1, thumb_func () at test.c:3
3 return 42;
Program received signal SIGILL, Illegal instruction.
0x00401004 in ?? ()
```
Disassembly of the crash site (ARM code):
```
=> 0x004004d8 <+0>: mov r0, #42 ; 0x2a
0x004004dc <+4>: bx lr
```
Disassembly of the call site (Thumb code, +2 bytes):
```
0x004004e0 <+0>: push{r3, lr}
0x004004e2 <+2>: blx 0x4004d8
=> 0x004004e6 <+6>: pop {r3, pc}
```
>>> SRU'ed package:
GDB 12.1-0ubuntu1~22.04.1 (patched)
GCC 11.4.0-1ubuntu1~22.04
Result:
```
Breakpoint 1 at 0x4d8: file test.c, line 3.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
Breakpoint 1, thumb_func () at test.c:3
3 return 42;
[Inferior 1 (process 3611) exited with code 052]
```
Conclusion
--
GDB 12.1-0ubuntu1~22.04.1 package correctly fixed the issue described in the
bug report.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
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/2041396
Title:
gdb 12.1 generates SIGILL on armhf
Status in gdb:
Fix Released
Status in gdb package in Ubuntu:
Fix Released
Status in gdb source package in Jammy:
Fix Committed
Bug description:
[ Impact ]
* GDB 12.1 introduced a regression where it will break program execution
when the program contains mixed ARM code and THUMB code.
* Upstream stated they tested the changes on Ubuntu 20.04 and it went okay.
[ Test Plan ]
Considering the following C program:
```
__attribute__((target("arm"), noinline))
int thumb_func() {
return 42;
}
__attribute__((target("thumb")))
int main() { return thumb_func(); }
```
If you build it using `gcc repro.c -ggdb3 -Og -o repro` and run the
GDB using the following commands ...
```
b 3
r
c
```
(you can save the contents above to a file and run GDB using `gdb -x
script ./repro`)
... you will notice GDB broke the program and threw SIGILL.
If you run the program without GDB, the program exits normally.
[ Where problems could occur ]
* GDB is a complex software. As the patch suggests, it may break other use
cases (like single-stepping) entirely.
* Since this is an ARM-only patch, it's unlikely to affect other CPU
architectures. However, it is possible that this fix may break ARM64 execution.
[ Other Info ]
* This bug has been fixed in GDB 13, but the fix was never backported to GDB
12. You can find the upstream bug in the remote bug watch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/2041396/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
[Touch-packages] [Bug 2049392] Re: Symlink for resolv.conf not working with F5 vpn
This sounds like a bug with your VPN. How is it trying to change the DNS servers? If they are trying to edit /etc/resolv.conf directly, that is not compatible with systemd-resolved. Instead, they should use the DBus API for systemd-resolved, or use `resolvectl`, etc. ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2049392 Title: Symlink for resolv.conf not working with F5 vpn Status in systemd package in Ubuntu: Incomplete Bug description: Hi, I create this bug issue following an advice from Nick Rosbrook in this bug : https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2043234 May be it's a F5 VPN. I haven't found such a bug anywhere. I have an issue when connection to a F5 VPN when /etc/resolv.conf is the symbolic link of ../run/systemd/resolve/stub-resolv.conf ➜ ~ sudo ls -la /etc/resolv.conf lrwxrwxrwx 1 root root 39 juin 23 12:37 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf When F5 is launched, /etc/resolv.conf is not changed. I have to manually set resolv.conf to change the nameserver(s). When I change the symbolic link /etc/resolv.conf to /run/systemd/resolve/resolv.conf sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf When F5 is launched, /etc/resolv.conf is updated whith vpn nameserver(s). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2049392/+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 2037604] Re: Backport packages for 22.04.4 HWE stack
Any testing is helpful, thanks! I've now ran tests on Intel DG2/Arc, and things work fine at least on 6.5 kernel. 6.1 (OEM) fails to start gdm/X with a trace from the DRI driver, need to investigate if that's a regression or not. -- 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/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 2048388] Re: Test suite often fails with "systemd units changed without reload" on s390x
** Merge proposal linked:
https://code.launchpad.net/~ogayot/britney/+git/britney/+merge/458822
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/2048388
Title:
Test suite often fails with "systemd units changed without reload" on
s390x
Status in netplan:
Invalid
Status in netplan.io package in Ubuntu:
Triaged
Status in wpa package in Ubuntu:
New
Bug description:
The "ethernets" autopkgtest for netplan.io 0.107-5ubuntu2 on s390x
often fails with
AssertionError: systemd units changed without reload
Looking at the history of autopkgtest runs, it looks like that the
error does not always occur during execution of a specific test. I've
seen occurrences of this error during the following test-cases:
test_dhcp6 (__main__.TestNetworkd.test_dhcp6) ... FAIL
test_link_local_ipv4 (__main__.TestNetworkd.test_link_local_ipv4) ... FAIL
test_eth_mtu (__main__.TestNetworkd.test_eth_mtu) ... FAIL
Example [1]:
781s FAIL: test_dhcp6 (__main__.TestNetworkd.test_dhcp6)
781s --
781s Traceback (most recent call last):
781s File
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/ethernets.py", line
189, in test_dhcp6
781s self.generate_and_settle([self.state_dhcp6(self.dev_e_client)])
781s File
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/base.py", line 342, in
generate_and_settle
781s self.fail('systemd units changed without reload')
781s AssertionError: systemd units changed without reload
[1] https://autopkgtest.ubuntu.com/results/autopkgtest-
noble/noble/s390x/n/netplan.io/20240105_144627_cb35e@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2048388/+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 2049660] [NEW] screen artifacts especially when changing workspaces
Public bug reported: Installed fresh, artifacts started after update. Happens when interacting gnome; menus, changing workspaces, etc. Attached screencast ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: zfs 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 Jan 17 17:55:34 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8c21] InstallationDate: Installed on 2024-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: HP HP Pavilion Plus Laptop 14-ey0xxx ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_7trxt5@/vmlinuz-6.5.0-14-generic root=ZFS=rpool/ROOT/ubuntu_7trxt5 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2023 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8C21 dmi.board.vendor: HP dmi.board.version: 87.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 87.27 dmi.modalias: dmi:bvnInsyde:bvrF.02:bd08/10/2023:br15.2:efr87.27:svnHP:pnHPPavilionPlusLaptop14-ey0xxx:pvrType1ProductConfigId:rvnHP:rn8C21:rvr87.27:cvnHP:ct10:cvrChassisVersion:sku8Y7M1EA#ABH: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Plus Laptop 14-ey0xxx dmi.product.sku: 8Y7M1EA#ABH dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7 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 corruption jammy ubuntu wayland-session ** Attachment added: "screencast of changing workspaces to cause artificats" https://bugs.launchpad.net/bugs/2049660/+attachment/5740202/+files/Screencast%20from%2017-01-24%2018%3A11%3A51.webm -- 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/2049660 Title: screen artifacts especially when changing workspaces Status in xorg package in Ubuntu: New Bug description: Installed fresh, artifacts started after update. Happens when interacting gnome; menus, changing workspaces, etc. Attached screencast ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: zfs 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 Jan 17 17:55:34 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8c21] InstallationDate: Installed on 2024-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: HP HP Pavilion Plus Laptop 14-ey0xxx ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_7trxt5@/vmlinuz-6.5.0-14-generic root=ZFS=rpool/ROOT/ubuntu_7trxt5 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2023 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8C21 dmi.board.vendor: HP dmi.board.version: 87.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version
[Touch-packages] [Bug 2048388] Re: Test suite often fails with "systemd units changed without reload" on s390x
After further analysis, it looks like the trigger=wpa/2:2.10-21 highly
increases the likeliness of the error to occur.
At this point, I do not think that there is any regression in wpa
2:2.10-21 compared to 2:2.10-20. The changeset is minimal. OTOH I think
the trigger=wpa/... alters the order of events and somehow consequently
makes the race condition more likely to occur.
FWIW, with a trigger=wpa/..., wpasupplicant gets upgraded before running
the ethernets test:
96s Unpacking wpasupplicant (2:2.10-21) over (2:2.10-20) ...
https://autopkgtest.ubuntu.com/results/autopkgtest-noble-ogayot-noble-
proposed//noble/s390x/n/netplan.io/20240109_171235_03058@/log.gz
Whereas. without the trigger, it gets installed:
127s Unpacking wpasupplicant (2:2.10-21) ...
https://autopkgtest.ubuntu.com/results/autopkgtest-noble-ogayot-noble-
proposed//noble/s390x/n/netplan.io/20240109_162248_f656d@/log.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/2048388
Title:
Test suite often fails with "systemd units changed without reload" on
s390x
Status in netplan:
Invalid
Status in netplan.io package in Ubuntu:
Triaged
Status in wpa package in Ubuntu:
New
Bug description:
The "ethernets" autopkgtest for netplan.io 0.107-5ubuntu2 on s390x
often fails with
AssertionError: systemd units changed without reload
Looking at the history of autopkgtest runs, it looks like that the
error does not always occur during execution of a specific test. I've
seen occurrences of this error during the following test-cases:
test_dhcp6 (__main__.TestNetworkd.test_dhcp6) ... FAIL
test_link_local_ipv4 (__main__.TestNetworkd.test_link_local_ipv4) ... FAIL
test_eth_mtu (__main__.TestNetworkd.test_eth_mtu) ... FAIL
Example [1]:
781s FAIL: test_dhcp6 (__main__.TestNetworkd.test_dhcp6)
781s --
781s Traceback (most recent call last):
781s File
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/ethernets.py", line
189, in test_dhcp6
781s self.generate_and_settle([self.state_dhcp6(self.dev_e_client)])
781s File
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/base.py", line 342, in
generate_and_settle
781s self.fail('systemd units changed without reload')
781s AssertionError: systemd units changed without reload
[1] https://autopkgtest.ubuntu.com/results/autopkgtest-
noble/noble/s390x/n/netplan.io/20240105_144627_cb35e@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2048388/+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 1568726] Re: iconv stdio buffering
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: eglibc (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1568726 Title: iconv stdio buffering Status in eglibc package in Ubuntu: Confirmed Bug description: Tool "iconv" suffers from the stdio buffering problem described here: https://stackoverflow.com/questions/14472179/how-do-i-perform-a- streaming-character-conversion Basically, when piping to iconv in an interactive session, output stutters. Tool "stdbuf" does not help. From the page above: "But it looks like iconv is managing the buffering internally itself - it's nothing to do with the Linux pipe buffer." Solutions are described in this page: http://www.pixelbeat.org/programming/stdio_buffering/ iconv should have a command-line switch to help. From the page above: "Note tail's stdout buffer would also have this problem, but tail -f calls fflush on the stdout stream when new data is received to alleviate this (as do tcpdump -l, grep --line-buffered and sed --unbuffered for example)." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1568726/+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 1568726] Re: iconv stdio buffering
This bug was reported more than 15 years ago. https://sourceware.org/bugzilla/show_bug.cgi?id=6050 But there is a patch for it since 2015 https://sourceware.org/legacy-ml/libc-alpha/2015-08/msg00297.html Who maintains libc-bin? Could you please apply these patches? $ iconv -V iconv (Ubuntu GLIBC 2.31-0ubuntu9.14) 2.31 Copyright (C) 2020 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Written by Ulrich Drepper. $ apt-cache policy libc-bin libc-bin: Installed: 2.31-0ubuntu9.14 Candidate: 2.31-0ubuntu9.14 ** Bug watch added: Sourceware.org Bugzilla #6050 https://sourceware.org/bugzilla/show_bug.cgi?id=6050 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1568726 Title: iconv stdio buffering Status in eglibc package in Ubuntu: Confirmed Bug description: Tool "iconv" suffers from the stdio buffering problem described here: https://stackoverflow.com/questions/14472179/how-do-i-perform-a- streaming-character-conversion Basically, when piping to iconv in an interactive session, output stutters. Tool "stdbuf" does not help. From the page above: "But it looks like iconv is managing the buffering internally itself - it's nothing to do with the Linux pipe buffer." Solutions are described in this page: http://www.pixelbeat.org/programming/stdio_buffering/ iconv should have a command-line switch to help. From the page above: "Note tail's stdout buffer would also have this problem, but tail -f calls fflush on the stdout stream when new data is received to alleviate this (as do tcpdump -l, grep --line-buffered and sed --unbuffered for example)." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1568726/+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 2048914] Re: System program problem detected at every login Xubuntu Update Notifier
I have the `thermald` service disabled using the commands you provided, and after 5 reboots and 1 shut down, the problem still persists. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/2048914 Title: System program problem detected at every login Xubuntu Update Notifier Status in update-notifier package in Ubuntu: New Status in whoopsie package in Ubuntu: Incomplete Bug description: Every time I log in to my new installation of Xubuntu 24.04 (daily ISO) after a reboot, I get an error message that says, "System program problem detected." Clicking either Cancel or Report Problem only dismisses the pop-up without any further action. This has occurred on multiple computers. This began with the first boot after installation and occurs at each subsequent reboot upon logging in. Logging out and back in does not cause the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: update-notifier 3.192.66 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Jan 10 09:57:25 2024 ExecutablePath: /usr/bin/update-notifier InstallationDate: Installed on 2024-01-10 (0 days ago) InstallationMedia: Xubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240110) ProcEnviron: LANG=C.UTF-8 LANGUAGE=en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: update-notifier UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/2048914/+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 2035122] Re: Under ubuntu core/core-desktop, /etc/default/locale is not modifiable
Looking at the attached screenshot, it covers everything in the test plan above. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2035122 Title: Under ubuntu core/core-desktop, /etc/default/locale is not modifiable Status in systemd package in Ubuntu: New Status in systemd source package in Jammy: Fix Committed Status in systemd source package in Lunar: Won't Fix Status in systemd source package in Mantic: Won't Fix Bug description: [Impact] When working with ubuntu core or ubuntu core desktop, neither */etc/default/locale* nor */etc/default/keyboard* are modifiable, so it's not possible to set the global keyboard or the global language. This is required to allow to set the GDM language, and the default one during installation. The first half of the solution is to create the folder */etc/writable/default*, and make soft-links from */etc/default/locale* to */etc/writable/default/locale* and from */etc/default/keyboard* to */etc/writable/default/keyboard*, just like it is already being done with */etc/hostname*, */etc/issue*, */etc/localtime*, */etc/motd* and , */etc/timezone*. This solution, unfortunately, isn't complete. Although any application that just reads the files will work, not all of the applications that write to them will; specifically the systemd utilities that set the contents for those files, because they don't open the file directly; instead, they create first the new file in the same folder than the old one, fill its contents, and only then delete the old one and rename the new one. To solve this, systemd in Ubuntu already has several patches that detect if a file is a soft-link, in which case it replaces the old path with the destination one. Currently I have in place a patch for Ubuntu Core Desktop that implements both changes for both */etc/default/locale* and */etc/default/keyboard*. [Test plan] Using *sudo localectl set-locale xx_YY.UTF-8* in an Ubuntu Core or Ubuntu Core Desktop admin terminal must change the locale to the specified one, which can be checked by reading the */etc/default/locale* file. Also, *localectl* must return the new locale. Using *sudo dbus-send --system --print-reply --dest=org.freedesktop.locale1 /org/freedesktop/locale1 org.freedesktop.locale1.SetX11Keyboard string:XX string:pc10Y string: string: boolean:true boolean:false" must change the */etc/default/keyboard* file to layout XX and model PC10Y (being Y either 1, 2, 4 or 5). Reading the file allows to check it. Also, *localectl status* must return the layout and model values in "X11 Layout" and "X11 Model" entries. [Where problems could occur] In general, applications just read the content of the file and use the DBus interface to set the locale, so only those applications that modify by themselves the */etc/default/keyboard* and/or */etc/default/locale* would present a problem, in which case they would require specific patches. Anyway, those applications neither would work with the current state (with those files in a read-only filesystem). [Other info] For Noble, this will be addressed when we merge systemd v255 from Debian. This is only needed on core, so we don't need to fix for Mantic or Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035122/+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 2049552] Re: [noble] ftbfs with new zlib 1.3
** Changed in: openssh (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2049552
Title:
[noble] ftbfs with new zlib 1.3
Status in openssh package in Ubuntu:
In Progress
Bug description:
The zlib detection code seems faulty:
checking for possibly buggy zlib... yes
configure: error: *** zlib too old - check config.log ***
Your reported zlib version has known security problems. It's possible your
vendor has fixed these problems without changing the version number. If you
are sure this is the case, you can disable the check by running
"./configure --without-zlib-version-check".
If you are in doubt, upgrade zlib to version 1.2.3 or greater.
See http://www.gzip.org/zlib/ for details.
| #include
| #include
| #include
|
| int
| main (void)
| {
|
| int a=0, b=0, c=0, d=0, n, v;
| n = sscanf(ZLIB_VERSION, "%d.%d.%d.%d", , , , );
| if (n != 3 && n != 4)
| exit(1);
| v = a*100 + b*1 + c*100 + d;
| fprintf(stderr, "found zlib version %s (%d)\n", ZLIB_VERSION, v);
|
| /* 1.1.4 is OK */
| if (a == 1 && b == 1 && c >= 4)
| exit(0);
|
| /* 1.2.3 and up are OK */
| if (v >= 1020300)
| exit(0);
|
| exit(2);
|
| ;
| return 0;
| }
Upstream bug report: https://bugzilla.mindrot.org/show_bug.cgi?id=3604
Upstream fix (untested): https://github.com/openssh/openssh-
portable/commit/cb4ed12ffc332d1f72d054ed92655b5f1c38f621
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2049552/+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 2049318] Re: [SRU] free(): double free detected in tcache 2
I sponsored the upload of iptables 1.8.7-1ubuntu5.2, now waiting for approval in the Jammy queue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/2049318 Title: [SRU] free(): double free detected in tcache 2 Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Jammy: In Progress Bug description: [ Impact ] iptables is unable to list the iptables rules or save the iptables rules if a nftables ruleset is defined which iptables does not recognize. [ Test Plan ] 1. Simple test plan based on upstream test case: sudo nft -f - < rules.txt * Convert the rule to nftables ruleset - sudo iptables-nft-restore < rules.txt * List the nftables ruleset - sudo nft list ruleset * Also confirm that iptables can list the old rule - sudo iptables -L * Now add another nftables rule (this rule is taken from upstream test case) sudo nft -f -
[Touch-packages] [Bug 2049318] Re: [SRU] free(): double free detected in tcache 2
** Changed in: iptables (Ubuntu Jammy) Assignee: (unassigned) => Graham Inggs (ginggs) ** Changed in: iptables (Ubuntu Jammy) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/2049318 Title: [SRU] free(): double free detected in tcache 2 Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Jammy: In Progress Bug description: [ Impact ] iptables is unable to list the iptables rules or save the iptables rules if a nftables ruleset is defined which iptables does not recognize. [ Test Plan ] 1. Simple test plan based on upstream test case: sudo nft -f - < rules.txt * Convert the rule to nftables ruleset - sudo iptables-nft-restore < rules.txt * List the nftables ruleset - sudo nft list ruleset * Also confirm that iptables can list the old rule - sudo iptables -L * Now add another nftables rule (this rule is taken from upstream test case) sudo nft -f -
[Touch-packages] [Bug 2049630] [NEW] [LE-Beats Studio Pro tilhørende j, playback] Playback problem
Public bug reported: I am no longer able to change pulseaudio card profile from a2dp_sink to handsfree_head_unit It used to work before running apt upgrade where I got a new kernel 6.5.0-14-generic #14~22.04.1-Ubuntu installed. As you can see below - and actual experience with the headphones, there is no problem switching to and from off and a2dp_sink but I can no longer get to the handsfree_head_unit. journalctl -b -f gives the follwing error message when trying to activate the handsfree_head_unit profile: myleno pulseaudio[405145]: Refused to switch profile to handsfree_head_unit: Not connected cut/paste of pacmd command: list-cards: .. . . index: 2 name: driver: owner module: 24 properties: device.description = "Beats Studio Pro tilhørende jan" device.string = "A4:16:C0:63:87:DD" device.api = "bluez" device.class = "sound" device.bus = "bluetooth" device.form_factor = "headphone" bluez.path = "/org/bluez/hci0/dev_A4_16_C0_63_87_DD" bluez.class = "0x240418" bluez.alias = "Beats Studio Pro tilhørende jan" device.icon_name = "audio-headphones-bluetooth" bluetooth.codec = "sbc_xq_453" profiles: a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, available: unknown) handsfree_head_unit: Handsfree Head Unit (HFP) (priority 30, available: no) off: Off (priority 0, available: yes) active profile: sinks: bluez_sink.A4_16_C0_63_87_DD.a2dp_sink/#1: Beats Studio Pro tilhørende jan sources: bluez_sink.A4_16_C0_63_87_DD.a2dp_sink.monitor/#2: Monitor of Beats Studio Pro tilhørende jan ports: headphone-output: Headphone (priority 0, latency offset 10 usec, available: unknown) properties: headphone-input: Bluetooth Input (priority 0, latency offset 0 usec, available: no) properties: >>> set-card-profile 2 handsfree_head_unit Failed to set card profile to 'handsfree_head_unit'. >>> set-card-profile 2 a2dp_sink >>> set-card-profile 2 off >>> set-card-profile 2 a2dp_sink ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jan2314 F pulseaudio /dev/snd/controlC0: jan2314 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Jan 17 14:58:03 2024 InstallationDate: Installed on 2022-12-08 (404 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: LE-Beats Studio Pro tilhørende j Symptom_Type: Only some of outputs are working Title: [LE-Beats Studio Pro tilhørende j, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2022 dmi.bios.release: 1.46 dmi.bios.vendor: LENOVO dmi.bios.version: GLCN46WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76465WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 17ALC6 dmi.ec.firmware.release: 1.46 dmi.modalias: dmi:bvnLENOVO:bvrGLCN46WW:bd03/23/2022:br1.46:efr1.46:svnLENOVO:pn82KV:pvrIdeaPad317ALC6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76465WIN:cvnLENOVO:ct10:cvrIdeaPad317ALC6:skuLENOVO_MT_82KV_BU_idea_FM_IdeaPad317ALC6: dmi.product.family: IdeaPad 3 17ALC6 dmi.product.name: 82KV dmi.product.sku: LENOVO_MT_82KV_BU_idea_FM_IdeaPad 3 17ALC6 dmi.product.version: IdeaPad 3 17ALC6 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2049630 Title: [LE-Beats Studio Pro tilhørende j, playback] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: I am no longer able to change pulseaudio card profile from a2dp_sink to handsfree_head_unit It used to work before running apt upgrade where I got a new kernel 6.5.0-14-generic #14~22.04.1-Ubuntu installed. As you can see below - and actual experience with the headphones, there is no problem switching to and from off and a2dp_sink but I can no longer get to the handsfree_head_unit. journalctl -b -f gives the follwing error message when trying to
[Touch-packages] [Bug 2045033] Re: Merge rsyslog 8.2312.0-2 from Debian
8.2312.0-3ubuntu1 was sponsored, setting status to fix committed and unsubscribing ubuntu-sponsors. ** Changed in: rsyslog (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2045033 Title: Merge rsyslog 8.2312.0-2 from Debian Status in Rsyslog: Unknown Status in rsyslog package in Ubuntu: Fix Committed Bug description: Debian has released rsyslog 8.2310.0-4. Merge it. To manage notifications about this bug go to: https://bugs.launchpad.net/rsyslog/+bug/2045033/+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 2049552] Re: [noble] ftbfs with new zlib 1.3
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) => Miriam España Acebal (mirespace)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2049552
Title:
[noble] ftbfs with new zlib 1.3
Status in openssh package in Ubuntu:
Triaged
Bug description:
The zlib detection code seems faulty:
checking for possibly buggy zlib... yes
configure: error: *** zlib too old - check config.log ***
Your reported zlib version has known security problems. It's possible your
vendor has fixed these problems without changing the version number. If you
are sure this is the case, you can disable the check by running
"./configure --without-zlib-version-check".
If you are in doubt, upgrade zlib to version 1.2.3 or greater.
See http://www.gzip.org/zlib/ for details.
| #include
| #include
| #include
|
| int
| main (void)
| {
|
| int a=0, b=0, c=0, d=0, n, v;
| n = sscanf(ZLIB_VERSION, "%d.%d.%d.%d", , , , );
| if (n != 3 && n != 4)
| exit(1);
| v = a*100 + b*1 + c*100 + d;
| fprintf(stderr, "found zlib version %s (%d)\n", ZLIB_VERSION, v);
|
| /* 1.1.4 is OK */
| if (a == 1 && b == 1 && c >= 4)
| exit(0);
|
| /* 1.2.3 and up are OK */
| if (v >= 1020300)
| exit(0);
|
| exit(2);
|
| ;
| return 0;
| }
Upstream bug report: https://bugzilla.mindrot.org/show_bug.cgi?id=3604
Upstream fix (untested): https://github.com/openssh/openssh-
portable/commit/cb4ed12ffc332d1f72d054ed92655b5f1c38f621
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2049552/+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 2049529] Re: Extra ZFS-related log line with `useradd -m -R /path`
** Description changed: Hi, I was digging into fixing `autopkgtest`'s `unshare` testsuite, and the rabbit hole led me here. Here is a very quick reproducer, first: Start a fresh Ubuntu VM. Here is a quick path, but other ways should do fine: ``` $ cd /tmp $ autopkgtest-buildvm-ubuntu-cloud -a amd64 -r noble $ kvm -m 1G -snapshot -hda autopkgtest-noble-amd64.img ``` Now in the VM: ``` $ sudo apt install -y mmdebstrap $ mmdebstrap noble /tmp/rootfs [...] $ sudo useradd --create-home --root /tmp/rootfs user1 can't open /dev/null: No such file or directory ``` The line `can't open /dev/null: No such file or directory` is printed on `stderr`, and that's unexpected by the part of the code I was debugging in the first place. Digging a bit led me to that line that does the printing: https://git.launchpad.net/ubuntu/+source/shadow/tree/debian/patches/1015_add_zsys_support.patch#n69 There seem to me that there are multiple issues with that patch: * Why try to call `zsysctl` in every case without first checking that it would be relevant: ZFS is not even installed on the VM we just created, less alone it has any ZFS volume/pool/whatever. * Obviously, when creating a user in a `chroot`, `/dev/null` won't exist unless mapped, and `useradd` is perfectly aware of that, because it even does the `chroot` call itself! But why even try to mess with ZFS in the `chroot` case in the first place? From what history @brian-murray told me, this patch was part of some ZFS experimentation in the past. Maybe that experimentation is now finished, and that patch could be dropped? At the very least it needs improvements, imho. + + EDIT: Just for context on why this issue appears only now: I was trying + to fix the `unshare` testsuite in `autopkgtest`, which is pretty recent + (2022) (https://salsa.debian.org/ci- + team/autopkgtest/-/commit/d1671f94f68bce9a0c6793310a9f8b79b4e919a5) even + upstream on Debian, and has never worked yet on Ubuntu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/2049529 Title: Extra ZFS-related log line with `useradd -m -R /path` Status in shadow package in Ubuntu: New Bug description: Hi, I was digging into fixing `autopkgtest`'s `unshare` testsuite, and the rabbit hole led me here. Here is a very quick reproducer, first: Start a fresh Ubuntu VM. Here is a quick path, but other ways should do fine: ``` $ cd /tmp $ autopkgtest-buildvm-ubuntu-cloud -a amd64 -r noble $ kvm -m 1G -snapshot -hda autopkgtest-noble-amd64.img ``` Now in the VM: ``` $ sudo apt install -y mmdebstrap $ mmdebstrap noble /tmp/rootfs [...] $ sudo useradd --create-home --root /tmp/rootfs user1 can't open /dev/null: No such file or directory ``` The line `can't open /dev/null: No such file or directory` is printed on `stderr`, and that's unexpected by the part of the code I was debugging in the first place. Digging a bit led me to that line that does the printing: https://git.launchpad.net/ubuntu/+source/shadow/tree/debian/patches/1015_add_zsys_support.patch#n69 There seem to me that there are multiple issues with that patch: * Why try to call `zsysctl` in every case without first checking that it would be relevant: ZFS is not even installed on the VM we just created, less alone it has any ZFS volume/pool/whatever. * Obviously, when creating a user in a `chroot`, `/dev/null` won't exist unless mapped, and `useradd` is perfectly aware of that, because it even does the `chroot` call itself! But why even try to mess with ZFS in the `chroot` case in the first place? From what history @brian-murray told me, this patch was part of some ZFS experimentation in the past. Maybe that experimentation is now finished, and that patch could be dropped? At the very least it needs improvements, imho. EDIT: Just for context on why this issue appears only now: I was trying to fix the `unshare` testsuite in `autopkgtest`, which is pretty recent (2022) (https://salsa.debian.org/ci- team/autopkgtest/-/commit/d1671f94f68bce9a0c6793310a9f8b79b4e919a5) even upstream on Debian, and has never worked yet on Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2049529/+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 2019856] Autopkgtest regression report (util-linux/2.38.1-4ubuntu1.1)
All autopkgtests for the newly accepted util-linux (2.38.1-4ubuntu1.1) for lunar have finished running. The following regressions have been reported in tests triggered by the package: systemd/252.5-2ubuntu3 (amd64, arm64, ppc64el, s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/lunar/update_excuses.html#util-linux [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2019856 Title: Add missing ARM-cores to support Grace-based systems Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Jammy: Fix Committed Status in util-linux source package in Kinetic: Won't Fix Status in util-linux source package in Lunar: Won't Fix Status in util-linux source package in Mantic: Fix Released Bug description: [Impact] When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't report a model name: Vendor ID: ARM Model: 0 [Fix] Adding the additional arm_part to sys-utils/lscpu-arm.c solves the problem. The commit below adds the specific codes missing from Jammy's version. https://github.com/util-linux/util- linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740 [Test Steps] * Verify whether output of lscpu is correct on new CPUs; eg: Vendor ID: ARM Model name: Neoverse-V2 * Verify whether output of lscpu doesn't change on old CPUs; eg: Vendor ID: ARM Model name: Neoverse-N1 [What Could Go Wrong] The fix only introduces additional model identifiers to match against and print a model name string, thus regression impact should be contained within lscpu and printing cpus model name on ARM systems. Output doesn't change on systems with non-affected CPU models. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+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 2019856] Autopkgtest regression report (util-linux/2.38.1-4ubuntu1.1)
All autopkgtests for the newly accepted util-linux (2.38.1-4ubuntu1.1) for lunar have finished running. The following regressions have been reported in tests triggered by the package: systemd/252.5-2ubuntu3 (amd64, arm64, ppc64el, s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/lunar/update_excuses.html#util-linux [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2019856 Title: Add missing ARM-cores to support Grace-based systems Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Jammy: Fix Committed Status in util-linux source package in Kinetic: Won't Fix Status in util-linux source package in Lunar: Won't Fix Status in util-linux source package in Mantic: Fix Released Bug description: [Impact] When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't report a model name: Vendor ID: ARM Model: 0 [Fix] Adding the additional arm_part to sys-utils/lscpu-arm.c solves the problem. The commit below adds the specific codes missing from Jammy's version. https://github.com/util-linux/util- linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740 [Test Steps] * Verify whether output of lscpu is correct on new CPUs; eg: Vendor ID: ARM Model name: Neoverse-V2 * Verify whether output of lscpu doesn't change on old CPUs; eg: Vendor ID: ARM Model name: Neoverse-N1 [What Could Go Wrong] The fix only introduces additional model identifiers to match against and print a model name string, thus regression impact should be contained within lscpu and printing cpus model name on ARM systems. Output doesn't change on systems with non-affected CPU models. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+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 2019856] Autopkgtest regression report (util-linux/2.38.1-4ubuntu1.1)
All autopkgtests for the newly accepted util-linux (2.38.1-4ubuntu1.1) for lunar have finished running. The following regressions have been reported in tests triggered by the package: systemd/252.5-2ubuntu3 (amd64, arm64, ppc64el, s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/lunar/update_excuses.html#util-linux [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2019856 Title: Add missing ARM-cores to support Grace-based systems Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Jammy: Fix Committed Status in util-linux source package in Kinetic: Won't Fix Status in util-linux source package in Lunar: Won't Fix Status in util-linux source package in Mantic: Fix Released Bug description: [Impact] When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't report a model name: Vendor ID: ARM Model: 0 [Fix] Adding the additional arm_part to sys-utils/lscpu-arm.c solves the problem. The commit below adds the specific codes missing from Jammy's version. https://github.com/util-linux/util- linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740 [Test Steps] * Verify whether output of lscpu is correct on new CPUs; eg: Vendor ID: ARM Model name: Neoverse-V2 * Verify whether output of lscpu doesn't change on old CPUs; eg: Vendor ID: ARM Model name: Neoverse-N1 [What Could Go Wrong] The fix only introduces additional model identifiers to match against and print a model name string, thus regression impact should be contained within lscpu and printing cpus model name on ARM systems. Output doesn't change on systems with non-affected CPU models. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+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 2019856] Re: Add missing ARM-cores to support Grace-based systems
** Changed in: util-linux (Ubuntu Lunar) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2019856 Title: Add missing ARM-cores to support Grace-based systems Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Jammy: Fix Committed Status in util-linux source package in Kinetic: Won't Fix Status in util-linux source package in Lunar: Won't Fix Status in util-linux source package in Mantic: Fix Released Bug description: [Impact] When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't report a model name: Vendor ID: ARM Model: 0 [Fix] Adding the additional arm_part to sys-utils/lscpu-arm.c solves the problem. The commit below adds the specific codes missing from Jammy's version. https://github.com/util-linux/util- linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740 [Test Steps] * Verify whether output of lscpu is correct on new CPUs; eg: Vendor ID: ARM Model name: Neoverse-V2 * Verify whether output of lscpu doesn't change on old CPUs; eg: Vendor ID: ARM Model name: Neoverse-N1 [What Could Go Wrong] The fix only introduces additional model identifiers to match against and print a model name string, thus regression impact should be contained within lscpu and printing cpus model name on ARM systems. Output doesn't change on systems with non-affected CPU models. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+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 2019856] Autopkgtest regression report (util-linux/2.38.1-4ubuntu1.1)
All autopkgtests for the newly accepted util-linux (2.38.1-4ubuntu1.1) for lunar have finished running. The following regressions have been reported in tests triggered by the package: systemd/252.5-2ubuntu3 (amd64, arm64, ppc64el, s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/lunar/update_excuses.html#util-linux [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2019856 Title: Add missing ARM-cores to support Grace-based systems Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Jammy: Fix Committed Status in util-linux source package in Kinetic: Won't Fix Status in util-linux source package in Lunar: Fix Committed Status in util-linux source package in Mantic: Fix Released Bug description: [Impact] When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't report a model name: Vendor ID: ARM Model: 0 [Fix] Adding the additional arm_part to sys-utils/lscpu-arm.c solves the problem. The commit below adds the specific codes missing from Jammy's version. https://github.com/util-linux/util- linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740 [Test Steps] * Verify whether output of lscpu is correct on new CPUs; eg: Vendor ID: ARM Model name: Neoverse-V2 * Verify whether output of lscpu doesn't change on old CPUs; eg: Vendor ID: ARM Model name: Neoverse-N1 [What Could Go Wrong] The fix only introduces additional model identifiers to match against and print a model name string, thus regression impact should be contained within lscpu and printing cpus model name on ARM systems. Output doesn't change on systems with non-affected CPU models. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+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 2047450] Re: tail emits no output for sysfs files when using large page kernels
An upload of coreutils to lunar-proposed has been rejected from the upload queue for the following reason: "lunar EOL in 9 days; no more SRUs". ** Changed in: coreutils (Ubuntu Lunar) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2047450 Title: tail emits no output for sysfs files when using large page kernels Status in coreutils package in Ubuntu: Fix Released Status in coreutils source package in Jammy: In Progress Status in coreutils source package in Lunar: Won't Fix Status in coreutils source package in Mantic: In Progress Status in coreutils source package in Noble: Fix Released Bug description: [Impact] Ubuntu provides 64K page size kernels for ppc64el (always) and arm64 (optional -64k flavors). When booted on 64K kernels, tail emits no output when tailing a sysfs file. The difference in behavior can be a source for bugs in scripts that use tail, and general user confusion. [Test Plan] The upstream fix includes a test case that tails the /sys/kernel/profiling file, if it exists. That case would fail with an unfixed coreutils package as shown below: = When booted on a 4K kernel = ubuntu@gunyolk:~$ tail /sys/kernel/profiling 0 = When booted on a 64K kernel = ubuntu@gunyolk:~$ tail /sys/kernel/profiling ubuntu@gunyolk:~$ Since the upstream test cases are executed at build time, the existing tests and this new test will be used to regression test behavior. This should cover both 4K (!ppc64el) and 64K (ppc64el) cases. We should also do a manual verification on arm64 w/ the 64K kernel since that case is not covered by our builders. [Where Problems Could Occur] The biggest risk for a regression I see is due to the side-effect of the fix now allocating a dynamic buffer instead of the stack. An error in logic there could cause a crash or a memory leak in scenarios undetected during testing. I used valgrind when developing the fix to derisk the memory leak scenario. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2047450/+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
