[Touch-packages] [Bug 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)
I actually failed to mention that before the update I was experiencing the crash. Not instead of the crashing UI is freezing. -- 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/2003339 Title: kwin_x11: The X11 connection broke: I/O error (code 1) Status in KDE Base Workspace: Fix Released Status in Mesa: Fix Released Status in kwin package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in kwin source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Released Status in kwin package in Debian: New Bug description: [Impact] kwin might crash after running some time Two commits have been reverted upstream since 22.2.x branch was closed, needs those backported to fix this. [Test case] Run kwin for a day or so, which is usually enough time to hit this. Crash happens mostly on a notification popups, so system must be actively receiving notifications to test the crash. Without that crash may not happen even in a week of runtime. [Where things could go wrong] This just reverts two commits, and they have been upstream for a few months now, so these causing a regression is unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+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 2021915] Re: dock overlays the rename box
Sounds like another fix similar to bug 1983456 will be required. ** Package changed: xorg (Ubuntu) => gnome-shell-extension-ubuntu-dock (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/2021915 Title: dock overlays the rename box Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: ubuntu 23.04 wayland and xorg have the same bug https://imgur.com/chWxw27 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 31 04:29:44 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu GraphicsCard: Subsystem: Acer Incorporated [ALI] GA107M [GeForce RTX 3050 Ti Mobile] [1025:1524] Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Lucienne [1025:1524] InstallationDate: Installed on 2023-05-30 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Acer Aspire A715-42G ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=5c2a9ea0-07a7-4edf-82d7-b8daefb3a66b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/28/2022 dmi.bios.release: 1.10 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Azalea_CAS dmi.board.vendor: LN dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd07/28/2022:br1.10:efr1.3:svnAcer:pnAspireA715-42G:pvrV1.10:rvnLN:rnAzalea_CAS:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku: dmi.product.family: Aspire 7 dmi.product.name: Aspire A715-42G dmi.product.sku: dmi.product.version: V1.10 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2021915/+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 2021915] Re: dock overlays the rename box
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2021915 Title: dock overlays the rename box Status in xorg package in Ubuntu: New Bug description: ubuntu 23.04 wayland and xorg have the same bug https://imgur.com/chWxw27 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 31 04:29:44 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu GraphicsCard: Subsystem: Acer Incorporated [ALI] GA107M [GeForce RTX 3050 Ti Mobile] [1025:1524] Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Lucienne [1025:1524] InstallationDate: Installed on 2023-05-30 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Acer Aspire A715-42G ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=5c2a9ea0-07a7-4edf-82d7-b8daefb3a66b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/28/2022 dmi.bios.release: 1.10 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Azalea_CAS dmi.board.vendor: LN dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd07/28/2022:br1.10:efr1.3:svnAcer:pnAspireA715-42G:pvrV1.10:rvnLN:rnAzalea_CAS:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku: dmi.product.family: Aspire 7 dmi.product.name: Aspire A715-42G dmi.product.sku: dmi.product.version: V1.10 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2021915/+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 2021929] [NEW] upgrade to exiv2 0.28.0
Public bug reported: The latest release is 0.28.0 and fixes some bugs I've encountered https://github.com/Exiv2/exiv2/releases/tag/v0.28.0 ** Affects: exiv2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/2021929 Title: upgrade to exiv2 0.28.0 Status in exiv2 package in Ubuntu: New Bug description: The latest release is 0.28.0 and fixes some bugs I've encountered https://github.com/Exiv2/exiv2/releases/tag/v0.28.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/2021929/+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 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency
Given that python-tz is just a test update I think we should leave that in -proposed and tag this bug block-proposed-lunar. ** Tags added: block-proposed-lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017999 Title: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency Status in python-tz package in Ubuntu: Fix Released Status in tzdata package in Ubuntu: Fix Released Status in python-tz source package in Focal: Invalid Status in tzdata source package in Focal: Fix Released Status in python-tz source package in Jammy: Invalid Status in tzdata source package in Jammy: Fix Released Status in python-tz source package in Kinetic: Invalid Status in tzdata source package in Kinetic: Fix Released Status in python-tz source package in Lunar: Fix Committed Status in tzdata source package in Lunar: Fix Released Bug description: [ Impact ] Recent updates have been using `PACKRATDATA=backzone` in order to add all out-of-scope lower-quality pre-1970 data back that existed in earlier tzadata releases (see bug #2003797). However it also leads to time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol, and Pacific/Enderbury to change: compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown [ Test Plan ] Add an autopkgtest test case for post-1970 symlink consistency: Check that the timezones for today and in half a year (= to cover DST changes) do not change compared to building them without `PACKRATDATA=backzone`. The mentioned timezones that differed can also be tested manually. Running following commands should have the same output (the output mentioned here is from tzdata 2023c-0ubuntu0.22.04.0): ``` $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z" Fri Apr 28 06:49:00 PDT 2023 $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z" Fri Apr 28 15:49:00 CEST 2023 $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z" Fri Apr 28 16:49:00 EEST 2023 ``` [ Where problems could occur ] Timezone data could be wrong. Systems with incorrect timezone set may observe unexpected time shift when updating the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency
This bug was fixed in the package tzdata - 2023c-0ubuntu0.22.04.2 --- tzdata (2023c-0ubuntu0.22.04.2) jammy; urgency=medium * Build tzdata with PACKRATLIST=zone.tab. In combination with PACKRATDATA=backzone (which is used since 2023c-0ubuntu0.22.04.1), time zones that differ pre-1970 and had been resurrected will not incur changes to data from 1970 on. This also removes Asia/Hanoi again. Upgrade Pacific/Enderbury to Pacific/Kanton again. (LP: #2017999) * Add an autopkgtest test case for post-1970 symlink consistency * Update debconf template and translations -- Benjamin Drung Sat, 20 May 2023 01:26:56 +0200 ** Changed in: tzdata (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017999 Title: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency Status in python-tz package in Ubuntu: Fix Released Status in tzdata package in Ubuntu: Fix Released Status in python-tz source package in Focal: Invalid Status in tzdata source package in Focal: Fix Released Status in python-tz source package in Jammy: Invalid Status in tzdata source package in Jammy: Fix Released Status in python-tz source package in Kinetic: Invalid Status in tzdata source package in Kinetic: Fix Released Status in python-tz source package in Lunar: Fix Committed Status in tzdata source package in Lunar: Fix Released Bug description: [ Impact ] Recent updates have been using `PACKRATDATA=backzone` in order to add all out-of-scope lower-quality pre-1970 data back that existed in earlier tzadata releases (see bug #2003797). However it also leads to time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol, and Pacific/Enderbury to change: compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown [ Test Plan ] Add an autopkgtest test case for post-1970 symlink consistency: Check that the timezones for today and in half a year (= to cover DST changes) do not change compared to building them without `PACKRATDATA=backzone`. The mentioned timezones that differed can also be tested manually. Running following commands should have the same output (the output mentioned here is from tzdata 2023c-0ubuntu0.22.04.0): ``` $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z" Fri Apr 28 06:49:00 PDT 2023 $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z" Fri Apr 28 15:49:00 CEST 2023 $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z" Fri Apr 28 16:49:00 EEST 2023 ``` [ Where problems could occur ] Timezone data could be wrong. Systems with incorrect timezone set may observe unexpected time shift when updating the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency
This bug was fixed in the package tzdata - 2023c-0ubuntu0.20.04.2 --- tzdata (2023c-0ubuntu0.20.04.2) focal; urgency=medium * Build tzdata with PACKRATLIST=zone.tab. In combination with PACKRATDATA=backzone (which is used since 2023c-0ubuntu0.20.04.1), time zones that differ pre-1970 and had been resurrected will not incur changes to data from 1970 on. This also removes Asia/Hanoi again. (LP: #2017999) * Add an autopkgtest test case for post-1970 symlink consistency * Update debconf template and translations -- Benjamin Drung Sat, 20 May 2023 01:32:19 +0200 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017999 Title: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency Status in python-tz package in Ubuntu: Fix Released Status in tzdata package in Ubuntu: Fix Released Status in python-tz source package in Focal: Invalid Status in tzdata source package in Focal: Fix Released Status in python-tz source package in Jammy: Invalid Status in tzdata source package in Jammy: Fix Released Status in python-tz source package in Kinetic: Invalid Status in tzdata source package in Kinetic: Fix Released Status in python-tz source package in Lunar: Fix Committed Status in tzdata source package in Lunar: Fix Released Bug description: [ Impact ] Recent updates have been using `PACKRATDATA=backzone` in order to add all out-of-scope lower-quality pre-1970 data back that existed in earlier tzadata releases (see bug #2003797). However it also leads to time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol, and Pacific/Enderbury to change: compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown [ Test Plan ] Add an autopkgtest test case for post-1970 symlink consistency: Check that the timezones for today and in half a year (= to cover DST changes) do not change compared to building them without `PACKRATDATA=backzone`. The mentioned timezones that differed can also be tested manually. Running following commands should have the same output (the output mentioned here is from tzdata 2023c-0ubuntu0.22.04.0): ``` $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z" Fri Apr 28 06:49:00 PDT 2023 $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z" Fri Apr 28 15:49:00 CEST 2023 $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z" Fri Apr 28 16:49:00 EEST 2023 ``` [ Where problems could occur ] Timezone data could be wrong. Systems with incorrect timezone set may observe unexpected time shift when updating the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency
This bug was fixed in the package tzdata - 2023c-0ubuntu0.22.10.2 --- tzdata (2023c-0ubuntu0.22.10.2) kinetic; urgency=medium * Build tzdata with PACKRATLIST=zone.tab. In combination with PACKRATDATA=backzone (which is used since 2023c-0ubuntu0.22.10.1), time zones that differ pre-1970 and had been resurrected will not incur changes to data from 1970 on. This also removes Asia/Hanoi again. Upgrade Pacific/Enderbury to Pacific/Kanton again. (LP: #2017999) * Add an autopkgtest test case for post-1970 symlink consistency * Update debconf template and translations -- Benjamin Drung Sat, 20 May 2023 01:17:08 +0200 ** Changed in: tzdata (Ubuntu Kinetic) Status: Fix Committed => Fix Released ** Changed in: tzdata (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017999 Title: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency Status in python-tz package in Ubuntu: Fix Released Status in tzdata package in Ubuntu: Fix Released Status in python-tz source package in Focal: Invalid Status in tzdata source package in Focal: Fix Released Status in python-tz source package in Jammy: Invalid Status in tzdata source package in Jammy: Fix Released Status in python-tz source package in Kinetic: Invalid Status in tzdata source package in Kinetic: Fix Released Status in python-tz source package in Lunar: Fix Committed Status in tzdata source package in Lunar: Fix Released Bug description: [ Impact ] Recent updates have been using `PACKRATDATA=backzone` in order to add all out-of-scope lower-quality pre-1970 data back that existed in earlier tzadata releases (see bug #2003797). However it also leads to time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol, and Pacific/Enderbury to change: compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown [ Test Plan ] Add an autopkgtest test case for post-1970 symlink consistency: Check that the timezones for today and in half a year (= to cover DST changes) do not change compared to building them without `PACKRATDATA=backzone`. The mentioned timezones that differed can also be tested manually. Running following commands should have the same output (the output mentioned here is from tzdata 2023c-0ubuntu0.22.04.0): ``` $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z" Fri Apr 28 06:49:00 PDT 2023 $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z" Fri Apr 28 15:49:00 CEST 2023 $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z" Fri Apr 28 16:49:00 EEST 2023 ``` [ Where problems could occur ] Timezone data could be wrong. Systems with incorrect timezone set may observe unexpected time shift when updating the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 2017999] Update Released
The verification of the Stable Release Update for tzdata has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017999 Title: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency Status in python-tz package in Ubuntu: Fix Released Status in tzdata package in Ubuntu: Fix Released Status in python-tz source package in Focal: Invalid Status in tzdata source package in Focal: Fix Released Status in python-tz source package in Jammy: Invalid Status in tzdata source package in Jammy: Fix Released Status in python-tz source package in Kinetic: Invalid Status in tzdata source package in Kinetic: Fix Released Status in python-tz source package in Lunar: Fix Committed Status in tzdata source package in Lunar: Fix Released Bug description: [ Impact ] Recent updates have been using `PACKRATDATA=backzone` in order to add all out-of-scope lower-quality pre-1970 data back that existed in earlier tzadata releases (see bug #2003797). However it also leads to time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol, and Pacific/Enderbury to change: compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown [ Test Plan ] Add an autopkgtest test case for post-1970 symlink consistency: Check that the timezones for today and in half a year (= to cover DST changes) do not change compared to building them without `PACKRATDATA=backzone`. The mentioned timezones that differed can also be tested manually. Running following commands should have the same output (the output mentioned here is from tzdata 2023c-0ubuntu0.22.04.0): ``` $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z" Fri Apr 28 06:49:00 PDT 2023 $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z" Fri Apr 28 15:49:00 CEST 2023 $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z" Fri Apr 28 16:49:00 EEST 2023 ``` [ Where problems could occur ] Timezone data could be wrong. Systems with incorrect timezone set may observe unexpected time shift when updating the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency
This bug was fixed in the package tzdata - 2023c-2exp1ubuntu1.1 --- tzdata (2023c-2exp1ubuntu1.1) lunar; urgency=medium * Build tzdata with PACKRATLIST=zone.tab. In combination with PACKRATDATA=backzone (which is used since 2022g-3), time zones that differ pre-1970 and had been resurrected will not incur changes to data from 1970 on. (LP: #2017999) This also removes Asia/Hanoi again. * Add an autopkgtest test case for post-1970 symlink consistency * Update debconf template and translations -- Benjamin Drung Fri, 19 May 2023 12:05:31 +0200 ** Changed in: tzdata (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017999 Title: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency Status in python-tz package in Ubuntu: Fix Released Status in tzdata package in Ubuntu: Fix Released Status in python-tz source package in Focal: Invalid Status in tzdata source package in Focal: Fix Released Status in python-tz source package in Jammy: Invalid Status in tzdata source package in Jammy: Fix Released Status in python-tz source package in Kinetic: Invalid Status in tzdata source package in Kinetic: Fix Released Status in python-tz source package in Lunar: Fix Committed Status in tzdata source package in Lunar: Fix Released Bug description: [ Impact ] Recent updates have been using `PACKRATDATA=backzone` in order to add all out-of-scope lower-quality pre-1970 data back that existed in earlier tzadata releases (see bug #2003797). However it also leads to time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol, and Pacific/Enderbury to change: compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown [ Test Plan ] Add an autopkgtest test case for post-1970 symlink consistency: Check that the timezones for today and in half a year (= to cover DST changes) do not change compared to building them without `PACKRATDATA=backzone`. The mentioned timezones that differed can also be tested manually. Running following commands should have the same output (the output mentioned here is from tzdata 2023c-0ubuntu0.22.04.0): ``` $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z" Fri Apr 28 06:49:00 PDT 2023 $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z" Fri Apr 28 15:49:00 CEST 2023 $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z" Fri Apr 28 16:49:00 EEST 2023 ``` [ Where problems could occur ] Timezone data could be wrong. Systems with incorrect timezone set may observe unexpected time shift when updating the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 1983359] Re: hwrng drivers missing in initrd.img
** Tags removed: rls-kk-incoming ** Also affects: initramfs-tools (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu Kinetic) Status: New => Fix Released ** Description changed: - The initialization of the entropy buffer of the urandom device is - critical for security. + [Impact] + The initialization of the entropy buffer of the urandom device is critical for security. + [Test case] When booting Jammy 22.04.1 on QEMU riscv64 I see the following warnings: [ 14.654546] random: lvm: uninitialized urandom read (4 bytes read) [ 15.247995] random: lvm: uninitialized urandom read (2 bytes read) [ 22.484719] random: lvm: uninitialized urandom read (4 bytes read) [ 43.161846] random: lvmconfig: uninitialized urandom read (4 bytes read) [ 48.862281] random: lvm: uninitialized urandom read (4 bytes read) Module virtio-rng.ko is missing in initrd.img. Adding virtio_rng to /etc/initramfs-tools/modules avoids the warnings. Hardware RNG drivers should generally be included in the initrd to provide early entropy. Best regards Heinrich -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1983359 Title: hwrng drivers missing in initrd.img Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Jammy: New Status in initramfs-tools source package in Kinetic: Fix Released Bug description: [Impact] The initialization of the entropy buffer of the urandom device is critical for security. [Test case] When booting Jammy 22.04.1 on QEMU riscv64 I see the following warnings: [ 14.654546] random: lvm: uninitialized urandom read (4 bytes read) [ 15.247995] random: lvm: uninitialized urandom read (2 bytes read) [ 22.484719] random: lvm: uninitialized urandom read (4 bytes read) [ 43.161846] random: lvmconfig: uninitialized urandom read (4 bytes read) [ 48.862281] random: lvm: uninitialized urandom read (4 bytes read) Module virtio-rng.ko is missing in initrd.img. Adding virtio_rng to /etc/initramfs-tools/modules avoids the warnings. Hardware RNG drivers should generally be included in the initrd to provide early entropy. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1983359/+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 2021894] [NEW] PCI/internal sound card not detected
Public bug reported: After Software Updater performed updates and reboot sound no longer works. I don't know what updates were performed because I didn't check. In sound settings only Dummy Output is available. When searching the internet for solutions I couldn't find any posts with the exact same problem as me. For me the lspci-command doesn't list any Kernel drivers or Kernel modules, which I think might be the problem. However, I have not managed to install any drivers. I have, among several other things, tried the instructions here: https://help.ubuntu.com/community/SoundTroubleshooting $ sudo aplay -l aplay: device_list:274: no soundcards found... $ sudo apt-get install linux-restricted-modules-`uname -r` linux-generic Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package linux-restricted-modules-5.19.0-42-generic E: Couldn't find any package by glob 'linux-restricted-modules-5.19.0-42-generic' E: Couldn't find any package by regex 'linux-restricted-modules-5.19.0-42-generic' $ lspci -v | grep -A7 -i "audio" 0b:00.1 Audio device: NVIDIA Corporation GP102 HDMI Audio Controller (rev a1) Subsystem: ASUSTeK Computer Inc. GP102 HDMI Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 10, IOMMU group 16 Memory at fc08 (32-bit, non-prefetchable) [size=16K] Capabilities: 0c:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function Subsystem: ASUSTeK Computer Inc. Starship/Matisse PCIe Dummy Function Flags: fast devsel, IOMMU group 17 -- 0d:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller Subsystem: ASUSTeK Computer Inc. Starship/Matisse HD Audio Controller Flags: fast devsel, IRQ 4, IOMMU group 21 Memory at fca0 (32-bit, non-prefetchable) [disabled] [size=32K] Capabilities: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:louise 2387 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 30 20:29:36 2023 InstallationDate: Installed on 2022-08-14 (289 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 8601 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR VI HERO (WI-FI AC) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr8601:bd07/25/2022:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIHERO(WI-FIAC):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS ** 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/2021894 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: After Software Updater performed updates and reboot sound no longer works. I don't know what updates were performed because I didn't check. In sound settings only Dummy Output is available. When searching the internet for solutions I couldn't find any posts with the exact same problem as me. For me the lspci-command doesn't list any Kernel drivers or Kernel modules, which I think might be the problem. However, I have not managed to install any drivers. I have, among several other things, tried the instructions here: https://help.ubuntu.com/community/SoundTroubleshooting $ sudo aplay -l aplay: device_list:274: no soundcards found... $ sudo apt-get install linux-restricted-modules-`uname -r` linux-generic Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package linux-restricted-modules-5.19.0-42-generic E: Couldn't find any package by glob 'linux-restricted-modules-5.19.0-42-generic' E: Couldn't
[Touch-packages] [Bug 1992454] Re: iptables: segfault when renaming a chain
This bug was fixed in the package iptables - 1.8.4-3ubuntu2.1 --- iptables (1.8.4-3ubuntu2.1) focal; urgency=medium [ Louis Bouchard ] * d/p/0001-libiptc-Fix-for-segfault-when-renaming-a-chain.patch: apply upstream fix for segfault when renaming a chain. Includes a test case (LP: #1992454) [ Andreas Hasenack ] * Fix shell tests, and run them as DEP8 (LP: #2019023): - d/p/0501-fix-firewalld-shell-test.patch: fix the globbing expression which was used to decide whether to sort the restore output or not before comparing it to the good case - d/t/control: run all shell tests as DEP8 -- Andreas Hasenack Tue, 09 May 2023 15:39:57 -0300 ** Changed in: iptables (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1992454 Title: iptables: segfault when renaming a chain Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Bionic: Fix Released Status in iptables source package in Focal: Fix Released Status in iptables source package in Jammy: Fix Committed Status in iptables source package in Kinetic: Fix Committed Bug description: [ Impact ] * An explanation of the effects of the bug on users This is the description for the upstream fix of this bug[1] : This is an odd bug: If the number of chains is right and one renames the last one in the list, libiptc dereferences a NULL pointer. * justification for backporting the fix to the stable release. Without this patch, users may experience segmentation fault when using the following versions of iptables : - Bionic : iptables - Focal : iptables - Jammy : iptables-legacy - Kinetic: iptables-legacy * In addition, it is helpful, but not required, to include an explanation of how the upload fixes this bug. The upstream fix adjust the size of the chain_index if the element is the last chain in the list. [1] http://git.netfilter.org/iptables/commit/?id=97bf4e68fc0794adba3243fd96f40f4568e7216f [ Test Plan ] * detailed instructions how to reproduce the bug The following code (adapted from the upstream commit to work on Kinetic) may be used to reproduce the issue : 8< #!/bin/bash # # Cover for a bug in libiptc: # - the chain 'node-98-tmp' is the last in the list sorted by name # - there are 81 chains in total, so three chain index buckets # - the last index bucket contains only the 'node-98-tmp' chain # => rename temporarily removes it from the bucket, leaving a NULL bucket # behind which is dereferenced later when inserting the chain again with new # name again ( echo "*filter" for chain in node-1 node-10 node-101 node-102 node-104 node-107 node-11 node-12 node-13 node-14 node-15 node-16 node-17 node-18 node-19 node-2 node-20 node-21 node-22 node-23 node-25 node-26 node-27 node-28 node-29 node-3 node-30 node-31 node-32 node-33 node-34 node-36 node-37 node-39 node-4 node-40 node-41 node-42 node-43 node-44 node-45 node-46 node-47 node-48 node-49 node-5 node-50 node-51 node-53 node-54 node-55 node-56 node-57 node-58 node-59 node-6 node-60 node-61 node-62 node-63 node-64 node-65 node-66 node-68 node-69 node-7 node-70 node-71 node-74 node-75 node-76 node-8 node-80 node-81 node-86 node-89 node-9 node-92 node-93 node-95 node-98-tmp; do echo ":$chain - [0:0]" done echo "COMMIT" ) | $XT_MULTI iptables-legacy-restore $XT_MULTI iptables-legacy -E node-98-tmp node-98 exit $? >8 Alternatively, this test has been added to the DEP8 list of tests, and will be executed automatically once the package is accepted into proposed. The DEP8 logs can be inspected for its run. Look for a test named "0006rename-segfault". [ Where problems could occur ] For Jammy and onward, only users of the -legacy commands may be affected. Since Jammy, iptables uses the new nft libraries which are not affected by the bug. For Bionic and Focal users, the regular iptables command is affected by the change. As stated in the manpage : E, --rename-chain old-chain new-chain Rename the user specified chain to the user supplied name. This is cosmetic, and has no effect on the structure of the table. In case of a problem, only the modification of the name would be affected as this is clearly outlined as a cosmetic only change. [ Other Info ] The patch is also applied to lunar and mantic, but is fixed in upstream's 1.8.9 release which so far is only in debian testing/unstable. This is being uploaded together with test fixes from bug #1992454 (bionic-specific) and bug #2019023 (focal-specific), which were found and
[Touch-packages] [Bug 2019023] Update Released
The verification of the Stable Release Update for iptables has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/2019023 Title: Fix shell test suite Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Focal: Fix Released Bug description: [ Impact ] The shell test suite (iptables/tests/shell/run-tests.sh) is currently failing on the firewalld tests in focal only: W: [FAILED] ././testcases/firewalld-restore/0001-firewalld_0: expected 0 but got 1 W: [FAILED] ././testcases/firewalld-restore/0002-firewalld-restart_0: expected 0 but got 1 After some troubleshooting, it turns out this is happening because of an unsorted order in the output of iptables-save, which was fixed[1] in later releases of iptables. The code was trying to compensate for that, but there was a small mistake[2] in a case/esac globbing: case "$XT_MULTI" in -*/xtables-nft-multi) +*xtables-nft-multi) The upstream fix includes other similar changes in other tests, but in the case of focal, the above is the minimal fix needed. Note that this shell test suite is not being run in focal, just in later ubuntu releases. But since the fix for #1992454 is adding such a test, I decided to fix the shell test run and add it to the existing DEP8 tests for focal via this bug, so we have test parity between focal and later ubuntu releases. 1. https://git.netfilter.org/iptables/commit/?id=e28cf12cf50b9e2e0114f04331635fc122cb8aef 2. https://git.netfilter.org/iptables/commit/?id=2b2b7948c1960ba4680677664ff58477be869de6 [ Test Plan ] Verify that the DEP8 tests now include a run-tests.sh test suite, and that it passes. [ Where problems could occur ] If the fix is incorrect, it would affect only the already-failing firewalld test. But in addition to fixing that test, we are now also including a full test run of all shell tests, something which wasn't being done for focal until now. While these tests are passing now, they could fail in a future iptables SRU, or turn out to be flaky. They are being run in ubuntu releases after focal, though, so that is a good sign. [ Other Info ] This fix is being included in the same upload as bug #1992454. [ Original Description ] The shell test suite (iptables/tests/shell/run-tests.sh) is currently failing on the firewalld tests: W: [FAILED] ././testcases/firewalld-restore/0001-firewalld_0: expected 0 but got 1 W: [FAILED] ././testcases/firewalld-restore/0002-firewalld-restart_0: expected 0 but got 1 After some troubleshooting, it turns out this is happening because of an unsorted order in the output of iptables-save, which was fixed[1] in later releases of iptables. The code was trying to compensate for that, but there was a small mistake[2] in a case/esac globbing: case "$XT_MULTI" in -*/xtables-nft-multi) +*xtables-nft-multi) 1. https://git.netfilter.org/iptables/commit/?id=e28cf12cf50b9e2e0114f04331635fc122cb8aef 2. https://git.netfilter.org/iptables/commit/?id=2b2b7948c1960ba4680677664ff58477be869de6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/2019023/+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 2019023] Re: Fix shell test suite
This bug was fixed in the package iptables - 1.8.4-3ubuntu2.1 --- iptables (1.8.4-3ubuntu2.1) focal; urgency=medium [ Louis Bouchard ] * d/p/0001-libiptc-Fix-for-segfault-when-renaming-a-chain.patch: apply upstream fix for segfault when renaming a chain. Includes a test case (LP: #1992454) [ Andreas Hasenack ] * Fix shell tests, and run them as DEP8 (LP: #2019023): - d/p/0501-fix-firewalld-shell-test.patch: fix the globbing expression which was used to decide whether to sort the restore output or not before comparing it to the good case - d/t/control: run all shell tests as DEP8 -- Andreas Hasenack Tue, 09 May 2023 15:39:57 -0300 ** Changed in: iptables (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/2019023 Title: Fix shell test suite Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Focal: Fix Released Bug description: [ Impact ] The shell test suite (iptables/tests/shell/run-tests.sh) is currently failing on the firewalld tests in focal only: W: [FAILED] ././testcases/firewalld-restore/0001-firewalld_0: expected 0 but got 1 W: [FAILED] ././testcases/firewalld-restore/0002-firewalld-restart_0: expected 0 but got 1 After some troubleshooting, it turns out this is happening because of an unsorted order in the output of iptables-save, which was fixed[1] in later releases of iptables. The code was trying to compensate for that, but there was a small mistake[2] in a case/esac globbing: case "$XT_MULTI" in -*/xtables-nft-multi) +*xtables-nft-multi) The upstream fix includes other similar changes in other tests, but in the case of focal, the above is the minimal fix needed. Note that this shell test suite is not being run in focal, just in later ubuntu releases. But since the fix for #1992454 is adding such a test, I decided to fix the shell test run and add it to the existing DEP8 tests for focal via this bug, so we have test parity between focal and later ubuntu releases. 1. https://git.netfilter.org/iptables/commit/?id=e28cf12cf50b9e2e0114f04331635fc122cb8aef 2. https://git.netfilter.org/iptables/commit/?id=2b2b7948c1960ba4680677664ff58477be869de6 [ Test Plan ] Verify that the DEP8 tests now include a run-tests.sh test suite, and that it passes. [ Where problems could occur ] If the fix is incorrect, it would affect only the already-failing firewalld test. But in addition to fixing that test, we are now also including a full test run of all shell tests, something which wasn't being done for focal until now. While these tests are passing now, they could fail in a future iptables SRU, or turn out to be flaky. They are being run in ubuntu releases after focal, though, so that is a good sign. [ Other Info ] This fix is being included in the same upload as bug #1992454. [ Original Description ] The shell test suite (iptables/tests/shell/run-tests.sh) is currently failing on the firewalld tests: W: [FAILED] ././testcases/firewalld-restore/0001-firewalld_0: expected 0 but got 1 W: [FAILED] ././testcases/firewalld-restore/0002-firewalld-restart_0: expected 0 but got 1 After some troubleshooting, it turns out this is happening because of an unsorted order in the output of iptables-save, which was fixed[1] in later releases of iptables. The code was trying to compensate for that, but there was a small mistake[2] in a case/esac globbing: case "$XT_MULTI" in -*/xtables-nft-multi) +*xtables-nft-multi) 1. https://git.netfilter.org/iptables/commit/?id=e28cf12cf50b9e2e0114f04331635fc122cb8aef 2. https://git.netfilter.org/iptables/commit/?id=2b2b7948c1960ba4680677664ff58477be869de6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/2019023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1992454] Update Released
The verification of the Stable Release Update for iptables has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1992454 Title: iptables: segfault when renaming a chain Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Bionic: Fix Released Status in iptables source package in Focal: Fix Released Status in iptables source package in Jammy: Fix Committed Status in iptables source package in Kinetic: Fix Committed Bug description: [ Impact ] * An explanation of the effects of the bug on users This is the description for the upstream fix of this bug[1] : This is an odd bug: If the number of chains is right and one renames the last one in the list, libiptc dereferences a NULL pointer. * justification for backporting the fix to the stable release. Without this patch, users may experience segmentation fault when using the following versions of iptables : - Bionic : iptables - Focal : iptables - Jammy : iptables-legacy - Kinetic: iptables-legacy * In addition, it is helpful, but not required, to include an explanation of how the upload fixes this bug. The upstream fix adjust the size of the chain_index if the element is the last chain in the list. [1] http://git.netfilter.org/iptables/commit/?id=97bf4e68fc0794adba3243fd96f40f4568e7216f [ Test Plan ] * detailed instructions how to reproduce the bug The following code (adapted from the upstream commit to work on Kinetic) may be used to reproduce the issue : 8< #!/bin/bash # # Cover for a bug in libiptc: # - the chain 'node-98-tmp' is the last in the list sorted by name # - there are 81 chains in total, so three chain index buckets # - the last index bucket contains only the 'node-98-tmp' chain # => rename temporarily removes it from the bucket, leaving a NULL bucket # behind which is dereferenced later when inserting the chain again with new # name again ( echo "*filter" for chain in node-1 node-10 node-101 node-102 node-104 node-107 node-11 node-12 node-13 node-14 node-15 node-16 node-17 node-18 node-19 node-2 node-20 node-21 node-22 node-23 node-25 node-26 node-27 node-28 node-29 node-3 node-30 node-31 node-32 node-33 node-34 node-36 node-37 node-39 node-4 node-40 node-41 node-42 node-43 node-44 node-45 node-46 node-47 node-48 node-49 node-5 node-50 node-51 node-53 node-54 node-55 node-56 node-57 node-58 node-59 node-6 node-60 node-61 node-62 node-63 node-64 node-65 node-66 node-68 node-69 node-7 node-70 node-71 node-74 node-75 node-76 node-8 node-80 node-81 node-86 node-89 node-9 node-92 node-93 node-95 node-98-tmp; do echo ":$chain - [0:0]" done echo "COMMIT" ) | $XT_MULTI iptables-legacy-restore $XT_MULTI iptables-legacy -E node-98-tmp node-98 exit $? >8 Alternatively, this test has been added to the DEP8 list of tests, and will be executed automatically once the package is accepted into proposed. The DEP8 logs can be inspected for its run. Look for a test named "0006rename-segfault". [ Where problems could occur ] For Jammy and onward, only users of the -legacy commands may be affected. Since Jammy, iptables uses the new nft libraries which are not affected by the bug. For Bionic and Focal users, the regular iptables command is affected by the change. As stated in the manpage : E, --rename-chain old-chain new-chain Rename the user specified chain to the user supplied name. This is cosmetic, and has no effect on the structure of the table. In case of a problem, only the modification of the name would be affected as this is clearly outlined as a cosmetic only change. [ Other Info ] The patch is also applied to lunar and mantic, but is fixed in upstream's 1.8.9 release which so far is only in debian testing/unstable. This is being uploaded together with test fixes from bug #1992454 (bionic-specific) and bug #2019023 (focal-specific), which were found and fixed while trying out the DEP8 runs for this package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1992454/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1992454] Re: iptables: segfault when renaming a chain
This bug was fixed in the package iptables - 1.6.1-2ubuntu2.1 --- iptables (1.6.1-2ubuntu2.1) bionic; urgency=medium [ Louis Bouchard ] * d/patches: 0001-libiptc-Fix-for-segfault-when-renaming-a-chain.patch Apply upstream fix: - libiptc: Fix for segfault when renaming a chain (LP: #1992454) - include new test for this issue in the DEP8 run [ Andreas Hasenack ] * d/t/control: fix DEP8 tests (LP: #2019022) -- Andreas Hasenack Tue, 09 May 2023 15:42:18 -0300 ** Changed in: iptables (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1992454 Title: iptables: segfault when renaming a chain Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Bionic: Fix Released Status in iptables source package in Focal: Fix Released Status in iptables source package in Jammy: Fix Committed Status in iptables source package in Kinetic: Fix Committed Bug description: [ Impact ] * An explanation of the effects of the bug on users This is the description for the upstream fix of this bug[1] : This is an odd bug: If the number of chains is right and one renames the last one in the list, libiptc dereferences a NULL pointer. * justification for backporting the fix to the stable release. Without this patch, users may experience segmentation fault when using the following versions of iptables : - Bionic : iptables - Focal : iptables - Jammy : iptables-legacy - Kinetic: iptables-legacy * In addition, it is helpful, but not required, to include an explanation of how the upload fixes this bug. The upstream fix adjust the size of the chain_index if the element is the last chain in the list. [1] http://git.netfilter.org/iptables/commit/?id=97bf4e68fc0794adba3243fd96f40f4568e7216f [ Test Plan ] * detailed instructions how to reproduce the bug The following code (adapted from the upstream commit to work on Kinetic) may be used to reproduce the issue : 8< #!/bin/bash # # Cover for a bug in libiptc: # - the chain 'node-98-tmp' is the last in the list sorted by name # - there are 81 chains in total, so three chain index buckets # - the last index bucket contains only the 'node-98-tmp' chain # => rename temporarily removes it from the bucket, leaving a NULL bucket # behind which is dereferenced later when inserting the chain again with new # name again ( echo "*filter" for chain in node-1 node-10 node-101 node-102 node-104 node-107 node-11 node-12 node-13 node-14 node-15 node-16 node-17 node-18 node-19 node-2 node-20 node-21 node-22 node-23 node-25 node-26 node-27 node-28 node-29 node-3 node-30 node-31 node-32 node-33 node-34 node-36 node-37 node-39 node-4 node-40 node-41 node-42 node-43 node-44 node-45 node-46 node-47 node-48 node-49 node-5 node-50 node-51 node-53 node-54 node-55 node-56 node-57 node-58 node-59 node-6 node-60 node-61 node-62 node-63 node-64 node-65 node-66 node-68 node-69 node-7 node-70 node-71 node-74 node-75 node-76 node-8 node-80 node-81 node-86 node-89 node-9 node-92 node-93 node-95 node-98-tmp; do echo ":$chain - [0:0]" done echo "COMMIT" ) | $XT_MULTI iptables-legacy-restore $XT_MULTI iptables-legacy -E node-98-tmp node-98 exit $? >8 Alternatively, this test has been added to the DEP8 list of tests, and will be executed automatically once the package is accepted into proposed. The DEP8 logs can be inspected for its run. Look for a test named "0006rename-segfault". [ Where problems could occur ] For Jammy and onward, only users of the -legacy commands may be affected. Since Jammy, iptables uses the new nft libraries which are not affected by the bug. For Bionic and Focal users, the regular iptables command is affected by the change. As stated in the manpage : E, --rename-chain old-chain new-chain Rename the user specified chain to the user supplied name. This is cosmetic, and has no effect on the structure of the table. In case of a problem, only the modification of the name would be affected as this is clearly outlined as a cosmetic only change. [ Other Info ] The patch is also applied to lunar and mantic, but is fixed in upstream's 1.8.9 release which so far is only in debian testing/unstable. This is being uploaded together with test fixes from bug #1992454 (bionic-specific) and bug #2019023 (focal-specific), which were found and fixed while trying out the DEP8 runs for this package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1992454/+subscriptions -- Mailing
[Touch-packages] [Bug 2019022] Update Released
The verification of the Stable Release Update for iptables has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/2019022 Title: Bionic dep8 tests are failing Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Bionic: Fix Released Bug description: [ Impact ] This bug does not affect users directly, but it's a problem everytime iptables is SRUed to Bionic. We could hint the DEP8 tests, in which case they would all be ignored (uncluding the ones that actually work), or fix it. By itself, fixing DEP8 is not worth an SRU, but since we are fixing a segfault (in #1992454), we can ship the DEP8 fixes with it and make future SRUs easier and of better quality (since the tests now run correctly). The actual fixes are two: - since many iptables commands exit non-zero when the help parameter is given (-h/--help), instead of relying on that, we grep the output. Since bash's pipefail option is not set, it's the grep exit status that will be checked. - the iptables-compat-save is now being called with the -d (dump) option, which works for what the test wants, and doesn't exit 1 for no reason. Later versions of iptables have either flipped the exit status of the -h option (but not for all commands, annoyingly), so this fix is not needed after bionic. In other cases, the problematic test was just removed from d/t/control. [ Test Plan ] Verify in the autopkgtest report that the DEP8 tests ran and are all green. [ Where problems could occur ] This is fixing the existing DEP8 tests, which have been red for bionic since ever. If the fix fails, the tests will remain red, so no change. I'm assuming that the test goal of the multiple calls to iptables binaries with just the "-h/--help" option is to see if they run and don't crash. This is now being wrapped by a grep filter. If the iptables binary crashes, but still produces the expected help output, then it will be considered a green run, even though there was a problem. [ Other Info ] This fix is being included in the same upload as bug #1992454. [ Original Description] The Bionic DEP8 tests for iptables are in bad shape[1], even in the migration-reference/0 run. There are two types of failures: a) some commands have an exit status of 1 when called with the -h (for help) option, which is what some tests do b) iptables-compat-save (and its IPv6 counterpart) also exit with status 1, even when there are chains/tables to save I'll propose: a) grep the help output instead of relying on the exit status b) call the command with the -d (dump) option. That doesn't exit 0 in the success case, and actually dumps data when there are tables to do so 1. https://autopkgtest.ubuntu.com/packages/i/iptables/bionic/amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/2019022/+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 2019022] Re: Bionic dep8 tests are failing
This bug was fixed in the package iptables - 1.6.1-2ubuntu2.1 --- iptables (1.6.1-2ubuntu2.1) bionic; urgency=medium [ Louis Bouchard ] * d/patches: 0001-libiptc-Fix-for-segfault-when-renaming-a-chain.patch Apply upstream fix: - libiptc: Fix for segfault when renaming a chain (LP: #1992454) - include new test for this issue in the DEP8 run [ Andreas Hasenack ] * d/t/control: fix DEP8 tests (LP: #2019022) -- Andreas Hasenack Tue, 09 May 2023 15:42:18 -0300 ** Changed in: iptables (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/2019022 Title: Bionic dep8 tests are failing Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Bionic: Fix Released Bug description: [ Impact ] This bug does not affect users directly, but it's a problem everytime iptables is SRUed to Bionic. We could hint the DEP8 tests, in which case they would all be ignored (uncluding the ones that actually work), or fix it. By itself, fixing DEP8 is not worth an SRU, but since we are fixing a segfault (in #1992454), we can ship the DEP8 fixes with it and make future SRUs easier and of better quality (since the tests now run correctly). The actual fixes are two: - since many iptables commands exit non-zero when the help parameter is given (-h/--help), instead of relying on that, we grep the output. Since bash's pipefail option is not set, it's the grep exit status that will be checked. - the iptables-compat-save is now being called with the -d (dump) option, which works for what the test wants, and doesn't exit 1 for no reason. Later versions of iptables have either flipped the exit status of the -h option (but not for all commands, annoyingly), so this fix is not needed after bionic. In other cases, the problematic test was just removed from d/t/control. [ Test Plan ] Verify in the autopkgtest report that the DEP8 tests ran and are all green. [ Where problems could occur ] This is fixing the existing DEP8 tests, which have been red for bionic since ever. If the fix fails, the tests will remain red, so no change. I'm assuming that the test goal of the multiple calls to iptables binaries with just the "-h/--help" option is to see if they run and don't crash. This is now being wrapped by a grep filter. If the iptables binary crashes, but still produces the expected help output, then it will be considered a green run, even though there was a problem. [ Other Info ] This fix is being included in the same upload as bug #1992454. [ Original Description] The Bionic DEP8 tests for iptables are in bad shape[1], even in the migration-reference/0 run. There are two types of failures: a) some commands have an exit status of 1 when called with the -h (for help) option, which is what some tests do b) iptables-compat-save (and its IPv6 counterpart) also exit with status 1, even when there are chains/tables to save I'll propose: a) grep the help output instead of relying on the exit status b) call the command with the -d (dump) option. That doesn't exit 0 in the success case, and actually dumps data when there are tables to do so 1. https://autopkgtest.ubuntu.com/packages/i/iptables/bionic/amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/2019022/+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 2021889] Re: error OSSL_CMP_MSG_update_recipNonce on base64 decoding
Oh, I found out it was another image in CI/CD setup. Sorry, my bad. ** Changed in: openssl (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2021889 Title: error OSSL_CMP_MSG_update_recipNonce on base64 decoding Status in openssl package in Ubuntu: Invalid Bug description: $ echo "$SSH_PRIVATE_KEY" | openssl base64 -A -d Error relocating /usr/bin/openssl: OSSL_CMP_MSG_update_recipNonce: symbol not found Error loading key "(stdin)": error in libcrypto --- works with openssl Version: 3.0.2-0ubuntu1.9. version 3.0.2-0ubuntu1.10 is broken. private key was: DEK-Info: AES-128-CBC $lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 Policy is from server where I did NOT upgrade (not wanted things to be broken). $apt-cache policy openssl openssl: Installed: 3.0.2-0ubuntu1.9 Candidate: 3.0.2-0ubuntu1.10 Version table: 3.0.2-0ubuntu1.10 500 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages *** 3.0.2-0ubuntu1.9 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.0.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2021889/+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 2021889] Re: error OSSL_CMP_MSG_update_recipNonce on base64 decoding
Yes, I did upgrade of all packages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2021889 Title: error OSSL_CMP_MSG_update_recipNonce on base64 decoding Status in openssl package in Ubuntu: New Bug description: $ echo "$SSH_PRIVATE_KEY" | openssl base64 -A -d Error relocating /usr/bin/openssl: OSSL_CMP_MSG_update_recipNonce: symbol not found Error loading key "(stdin)": error in libcrypto --- works with openssl Version: 3.0.2-0ubuntu1.9. version 3.0.2-0ubuntu1.10 is broken. private key was: DEK-Info: AES-128-CBC $lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 Policy is from server where I did NOT upgrade (not wanted things to be broken). $apt-cache policy openssl openssl: Installed: 3.0.2-0ubuntu1.9 Candidate: 3.0.2-0ubuntu1.10 Version table: 3.0.2-0ubuntu1.10 500 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages *** 3.0.2-0ubuntu1.9 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.0.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2021889/+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 2021889] Re: error OSSL_CMP_MSG_update_recipNonce on base64 decoding
Nope, only distribution packages. I noted it first in my CI/CD setup where I install fresh docker image ubuntu:22.04 and then apt-get update && apt-get upgrade -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2021889 Title: error OSSL_CMP_MSG_update_recipNonce on base64 decoding Status in openssl package in Ubuntu: New Bug description: $ echo "$SSH_PRIVATE_KEY" | openssl base64 -A -d Error relocating /usr/bin/openssl: OSSL_CMP_MSG_update_recipNonce: symbol not found Error loading key "(stdin)": error in libcrypto --- works with openssl Version: 3.0.2-0ubuntu1.9. version 3.0.2-0ubuntu1.10 is broken. private key was: DEK-Info: AES-128-CBC $lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 Policy is from server where I did NOT upgrade (not wanted things to be broken). $apt-cache policy openssl openssl: Installed: 3.0.2-0ubuntu1.9 Candidate: 3.0.2-0ubuntu1.10 Version table: 3.0.2-0ubuntu1.10 500 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages *** 3.0.2-0ubuntu1.9 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.0.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2021889/+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 2021889] Re: error OSSL_CMP_MSG_update_recipNonce on base64 decoding
OSSL_CMP_MSG_update_recipNonce was added in OpenSSL 3.0.9...did you perhaps install from source, or a package that didn't come from Ubuntu? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2021889 Title: error OSSL_CMP_MSG_update_recipNonce on base64 decoding Status in openssl package in Ubuntu: New Bug description: $ echo "$SSH_PRIVATE_KEY" | openssl base64 -A -d Error relocating /usr/bin/openssl: OSSL_CMP_MSG_update_recipNonce: symbol not found Error loading key "(stdin)": error in libcrypto --- works with openssl Version: 3.0.2-0ubuntu1.9. version 3.0.2-0ubuntu1.10 is broken. private key was: DEK-Info: AES-128-CBC $lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 Policy is from server where I did NOT upgrade (not wanted things to be broken). $apt-cache policy openssl openssl: Installed: 3.0.2-0ubuntu1.9 Candidate: 3.0.2-0ubuntu1.10 Version table: 3.0.2-0ubuntu1.10 500 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages *** 3.0.2-0ubuntu1.9 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.0.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2021889/+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 2021889] Re: error OSSL_CMP_MSG_update_recipNonce on base64 decoding
Thanks for reporting this issue. Did you also upgrade the libssl3 package too? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2021889 Title: error OSSL_CMP_MSG_update_recipNonce on base64 decoding Status in openssl package in Ubuntu: New Bug description: $ echo "$SSH_PRIVATE_KEY" | openssl base64 -A -d Error relocating /usr/bin/openssl: OSSL_CMP_MSG_update_recipNonce: symbol not found Error loading key "(stdin)": error in libcrypto --- works with openssl Version: 3.0.2-0ubuntu1.9. version 3.0.2-0ubuntu1.10 is broken. private key was: DEK-Info: AES-128-CBC $lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 Policy is from server where I did NOT upgrade (not wanted things to be broken). $apt-cache policy openssl openssl: Installed: 3.0.2-0ubuntu1.9 Candidate: 3.0.2-0ubuntu1.10 Version table: 3.0.2-0ubuntu1.10 500 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages *** 3.0.2-0ubuntu1.9 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.0.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2021889/+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 2021890] Re: package linux-image-5.19.0-1025-aws 5.19.0-1025.26~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2021890 Title: package linux-image-5.19.0-1025-aws 5.19.0-1025.26~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: I upgraded from Ubuntu 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1025-aws 5.19.0-1025.26~22.04.1 ProcVersionSignature: Ubuntu 5.15.0-1036.40~20.04.1-aws 5.15.98 Uname: Linux 5.15.0-1036-aws x86_64 NonfreeKernelModules: aufs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue May 30 16:21:29 2023 Ec2AMI: ami-b9daeddc Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2a Ec2InstanceType: t2.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: initramfs-tools Title: package linux-image-5.19.0-1025-aws 5.19.0-1025.26~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to jammy on 2023-05-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2021890/+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 2021890] [NEW] package linux-image-5.19.0-1025-aws 5.19.0-1025.26~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: I upgraded from Ubuntu 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1025-aws 5.19.0-1025.26~22.04.1 ProcVersionSignature: Ubuntu 5.15.0-1036.40~20.04.1-aws 5.15.98 Uname: Linux 5.15.0-1036-aws x86_64 NonfreeKernelModules: aufs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue May 30 16:21:29 2023 Ec2AMI: ami-b9daeddc Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2a Ec2InstanceType: t2.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: initramfs-tools Title: package linux-image-5.19.0-1025-aws 5.19.0-1025.26~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to jammy on 2023-05-30 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package ec2-images jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2021890 Title: package linux-image-5.19.0-1025-aws 5.19.0-1025.26~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: I upgraded from Ubuntu 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1025-aws 5.19.0-1025.26~22.04.1 ProcVersionSignature: Ubuntu 5.15.0-1036.40~20.04.1-aws 5.15.98 Uname: Linux 5.15.0-1036-aws x86_64 NonfreeKernelModules: aufs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue May 30 16:21:29 2023 Ec2AMI: ami-b9daeddc Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2a Ec2InstanceType: t2.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: initramfs-tools Title: package linux-image-5.19.0-1025-aws 5.19.0-1025.26~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to jammy on 2023-05-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2021890/+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 2021889] [NEW] error OSSL_CMP_MSG_update_recipNonce on base64 decoding
Public bug reported: $ echo "$SSH_PRIVATE_KEY" | openssl base64 -A -d Error relocating /usr/bin/openssl: OSSL_CMP_MSG_update_recipNonce: symbol not found Error loading key "(stdin)": error in libcrypto --- works with openssl Version: 3.0.2-0ubuntu1.9. version 3.0.2-0ubuntu1.10 is broken. private key was: DEK-Info: AES-128-CBC $lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 Policy is from server where I did NOT upgrade (not wanted things to be broken). $apt-cache policy openssl openssl: Installed: 3.0.2-0ubuntu1.9 Candidate: 3.0.2-0ubuntu1.10 Version table: 3.0.2-0ubuntu1.10 500 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages *** 3.0.2-0ubuntu1.9 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.0.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages ** Affects: openssl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2021889 Title: error OSSL_CMP_MSG_update_recipNonce on base64 decoding Status in openssl package in Ubuntu: New Bug description: $ echo "$SSH_PRIVATE_KEY" | openssl base64 -A -d Error relocating /usr/bin/openssl: OSSL_CMP_MSG_update_recipNonce: symbol not found Error loading key "(stdin)": error in libcrypto --- works with openssl Version: 3.0.2-0ubuntu1.9. version 3.0.2-0ubuntu1.10 is broken. private key was: DEK-Info: AES-128-CBC $lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 Policy is from server where I did NOT upgrade (not wanted things to be broken). $apt-cache policy openssl openssl: Installed: 3.0.2-0ubuntu1.9 Candidate: 3.0.2-0ubuntu1.10 Version table: 3.0.2-0ubuntu1.10 500 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages *** 3.0.2-0ubuntu1.9 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.0.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2021889/+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 2015355] Re: Please backport patches for false atari partition detection to Ubuntu 20.04
This bug is not present in Jammy or newer. ** Changed in: util-linux (Ubuntu) Status: New => Fix Released ** Description changed: + [Impact] + + The partition detection logic in libblkid1 can falsely report the + presence of an atari partition. One place where this has a practical + impact is in kubernetes where mount-utils will refuse to format the + device (https://github.com/kubernetes/mount- + utils/blob/732a08ae47571516020ef99c303c70c1fa5b3e6c/mount_linux.go#L437-L441). + + [Test Plan] + + * Create a new qcow2 disk image: + + $ qemu-img create -f qcow2 test.img 20G + + * Boot a focal ISO with QEMU/KVM as if installing to test.img: + + $ qemu-system-x86_64 -enable-kvm -m 4096 -name test -drive + file=test.img,format=qcow2 -net nic,model=virtio -net + user,hostfwd=tcp::1022-:22 -vga virtio -cdrom ubuntu-20.04.6-desktop- + amd64.iso + + * Using the live environment, format the empty disk. These particular + commands were given as a reproducer on the upstream bug report + (https://github.com/util-linux/util-linux/issues/1116). + + $ parted -s /dev/sda -- mklabel msdos + $ parted -s /dev/sda -- mkpart primary 0% 10% mkpart primary 10% 30% + + * Run wipefs on /dev/sda to list partitions. On an affected machine, an + atari partition will be listed. On a fixed machine, the incorrect atari + listing will be gone. + + $ wipefs /dev/sda + DEVICE OFFSET TYPE UUID LABEL + sda0x1fe dos + sda0x1d2 atari + + [Where problems could occur] + + These patches specifically address the atari prober logic in libblkid. + Therefore, if we saw regressions it would be related to detecting atari + partitions with libblkid. This would potentially impact tools such as + wipefs and blkid, or any other tool that uses libblkid1 for this + purpose. + + [Original Description] + There are three patches in util-linux upstream that were released in util-linux 2.37 and prevent false detection of the atari partition table with blkid and wipefs. We see this mostly on LUKS devices initialised via luksFormat reporting there is an atari partition table on the device when it is empty. This causes issues in various places, but one key example for us is in kubernetes where mount-utils will refuse to format the device (https://github.com/kubernetes/mount- utils/blob/732a08ae47571516020ef99c303c70c1fa5b3e6c/mount_linux.go#L437-L441) RedHat backported these fixes to RHEL 8 under https://bugzilla.redhat.com/show_bug.cgi?id=2060030 and it would be helpful if Ubuntu also backported them to Ubuntu 20.04 which is still running util-linux 2.34 The request is to backport patches based on the https://github.com/util- linux/util-linux/issues/1159 upstream report. - Upstream commits to cherry-pick the changes to libblkid/src/partitions/atari.c from: + Upstream commits to cherry-pick the changes to libblkid/src/partitions/atari.c from: 2cc76d50d7a14bef8e7b07fab11b26c9e49d36a2 282ceadc3a72fc07dd0388b8880fd751490bb87f c70b4f2a5b99876d230b8f4f413c3bb3ee6647f1 # lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 20.04.6 LTS Release:20.04 Codename: focal # blkid -V blkid from util-linux 2.34 (libblkid 2.34.0, 14-Jun-2019) # blkid -p -s TYPE -s PTTYPE -o export /dev/mapper/pvc-7b331195-cd5a-4ab6-8fdc-552af4b9139d_encrypted DEVNAME=dev/mapper/pvc-7b331195-cd5a-4ab6-8fdc-552af4b9139d_encrypted PTTYPE=atari # lsblk ... - sdccrypto_LUKS a79d2982-74f2-44c7-bb29-460768ebfe64 - `-3600a09803830474a735d4c63744c4a56crypto_LUKS a79d2982-74f2-44c7-bb29-460768ebfe64 - `-pvc-7b331195-cd5a-4ab6-8fdc-552af4b9139d_encrypted + sdccrypto_LUKS a79d2982-74f2-44c7-bb29-460768ebfe64 + `-3600a09803830474a735d4c63744c4a56crypto_LUKS a79d2982-74f2-44c7-bb29-460768ebfe64 + `-pvc-7b331195-cd5a-4ab6-8fdc-552af4b9139d_encrypted ** Changed in: util-linux (Ubuntu Focal) Status: New => In Progress ** Changed in: util-linux (Ubuntu Focal) Importance: Undecided => Low ** Changed in: util-linux (Ubuntu Focal) Assignee: (unassigned) => Nick Rosbrook (enr0n) -- 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/2015355 Title: Please backport patches for false atari partition detection to Ubuntu 20.04 Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Focal: In Progress Bug description: [Impact] The partition detection logic in libblkid1 can falsely report the presence of an atari partition. One place where this has a practical impact is in kubernetes where mount-utils will refuse to format the device
[Touch-packages] [Bug 2021881] Re: Kwin and plasmashell freeze randomly
Hardware info: CPU: Intel core i7-12800H 00:00.0 Host bridge: Intel Corporation 12th Gen Core Processor Host Bridge/DRAM Registers (rev 02) 00:01.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x16 Controller #1 (rev 02) 00:02.0 VGA compatible controller: Intel Corporation Alder Lake-P Integrated Graphics Controller (rev 0c) 00:04.0 Signal processing controller: Intel Corporation Alder Lake Innovation Platform Framework Processor Participant (rev 02) 00:06.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x4 Controller #0 (rev 02) 00:07.0 PCI bridge: Intel Corporation Alder Lake-P Thunderbolt 4 PCI Express Root Port #0 (rev 02) 00:07.1 PCI bridge: Intel Corporation Alder Lake-P Thunderbolt 4 PCI Express Root Port #1 (rev 02) 00:08.0 System peripheral: Intel Corporation 12th Gen Core Processor Gaussian & Neural Accelerator (rev 02) 00:0d.0 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 USB Controller (rev 02) 00:0d.2 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 NHI #0 (rev 02) 00:12.0 Serial controller: Intel Corporation Device 51fc (rev 01) 00:14.0 USB controller: Intel Corporation Alder Lake PCH USB 3.2 xHCI Host Controller (rev 01) 00:14.2 RAM memory: Intel Corporation Alder Lake PCH Shared SRAM (rev 01) 00:14.3 Network controller: Intel Corporation Alder Lake-P PCH CNVi WiFi (rev 01) 00:15.0 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #0 (rev 01) 00:15.1 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #1 (rev 01) 00:16.0 Communication controller: Intel Corporation Alder Lake PCH HECI Controller (rev 01) 00:16.3 Serial controller: Intel Corporation Device 51e3 (rev 01) 00:1c.0 PCI bridge: Intel Corporation Device 51bb (rev 01) 00:1f.0 ISA bridge: Intel Corporation Alder Lake PCH eSPI Controller (rev 01) 00:1f.3 Audio device: Intel Corporation Alder Lake PCH-P High Definition Audio Controller (rev 01) 00:1f.4 SMBus: Intel Corporation Alder Lake PCH-P SMBus Host Controller (rev 01) 00:1f.5 Serial bus controller: Intel Corporation Alder Lake-P PCH SPI Controller (rev 01) 01:00.0 3D controller: NVIDIA Corporation Device 25ba (rev a1) 02:00.0 Non-Volatile memory controller: Sandisk Corp WD PC SN810 / Black SN850 NVMe SSD (rev 01) a5:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5260 PCI Express Card Reader (rev 01) Ubuntu 22.04 KDE Plasma Version: 5.24.7 mesa version: 22.2.5-0ubuntu0.1~22.04.2 -- 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/2021881 Title: Kwin and plasmashell freeze randomly Status in kwin package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: kwin and plasmashell randomly freeze usually when there is a notification window pop up. I have to use kwin_x11 --replace or plasmashell --replace in order to make screen responsive. Please note I can still type to the app that currently is open (let's say FeatherPad) but things are stuck and I cannot switch tasks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/2021881/+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
Uploaded for Mantic, thanks! ** Changed in: util-linux (Ubuntu Mantic) Status: In Progress => Fix Committed -- 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 Committed Status in util-linux source package in Jammy: In Progress Status in util-linux source package in Kinetic: Won't Fix Status in util-linux source package in Lunar: In Progress Status in util-linux source package in Mantic: Fix Committed 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 2021881] [NEW] Kwin and plasmashell freeze randomly
Public bug reported: kwin and plasmashell randomly freeze usually when there is a notification window pop up. I have to use kwin_x11 --replace or plasmashell --replace in order to make screen responsive. Please note I can still type to the app that currently is open (let's say FeatherPad) but things are stuck and I cannot switch tasks. ** Affects: kwin (Ubuntu) Importance: Undecided Status: New ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Description changed: kwin and plasmashell randomly freeze usually when there is a - notification window pop up. + notification window pop up. I have to use kwin_x11 --replace or + plasmashell --replace in order to make screen responsive. Please note I + can still type to the app that currently is open (let's say FeatherPad) + but things are stuck and I cannot switch tasks. ** Also affects: kwin (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2021881 Title: Kwin and plasmashell freeze randomly Status in kwin package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: kwin and plasmashell randomly freeze usually when there is a notification window pop up. I have to use kwin_x11 --replace or plasmashell --replace in order to make screen responsive. Please note I can still type to the app that currently is open (let's say FeatherPad) but things are stuck and I cannot switch tasks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/2021881/+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 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)
Yes Gunter you might be correct. For me it is a freeze but seems related since other people have reported the same issue stating the revert of the two commits solved the freeze issue. There are no GPU hangs in the kernel logs (I just wanted to stress that out). I guess I will open a new bug report. -- 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/2003339 Title: kwin_x11: The X11 connection broke: I/O error (code 1) Status in KDE Base Workspace: Fix Released Status in Mesa: Fix Released Status in kwin package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in kwin source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Released Status in kwin package in Debian: New Bug description: [Impact] kwin might crash after running some time Two commits have been reverted upstream since 22.2.x branch was closed, needs those backported to fix this. [Test case] Run kwin for a day or so, which is usually enough time to hit this. Crash happens mostly on a notification popups, so system must be actively receiving notifications to test the crash. Without that crash may not happen even in a week of runtime. [Where things could go wrong] This just reverts two commits, and they have been upstream for a few months now, so these causing a regression is unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+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 Mantic) Assignee: Mauricio Faria de Oliveira (mfo) => Dan Bungert (dbungert) ** Changed in: util-linux (Ubuntu Mantic) Importance: Undecided => Wishlist -- 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: In Progress Status in util-linux source package in Jammy: In Progress Status in util-linux source package in Kinetic: Won't Fix Status in util-linux source package in Lunar: In Progress Status in util-linux source package in Mantic: In Progress 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 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)
On my machine the crashes also seem to be solved. I was using Intel driver until the weekend (since I use this laptop) and then switched to the nVidia binary drivers because I wanted to use CUDA for some experiments. kwin seems to run properly with both so far. @Konstantin Petrov: You write about a "hang", even referring to "GPU hangs" in the logs, which sometimes happen with Intel cards but on my system then actually cause a "hang" / "freeze", not a crash with kwin disappearing. This issue here is about kwin suddenly just quitting / disappearing, not about kwin freezing. Are we talking about the same symptoms? -- 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/2003339 Title: kwin_x11: The X11 connection broke: I/O error (code 1) Status in KDE Base Workspace: Fix Released Status in Mesa: Fix Released Status in kwin package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in kwin source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Released Status in kwin package in Debian: New Bug description: [Impact] kwin might crash after running some time Two commits have been reverted upstream since 22.2.x branch was closed, needs those backported to fix this. [Test case] Run kwin for a day or so, which is usually enough time to hit this. Crash happens mostly on a notification popups, so system must be actively receiving notifications to test the crash. Without that crash may not happen even in a week of runtime. [Where things could go wrong] This just reverts two commits, and they have been upstream for a few months now, so these causing a regression is unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+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 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04
Hi there, I see this with "lunar" Xubuntu 23.04 bernie@prod:~/Desktop$ journalctl -b |grep 'exit code 1' Mai 30 17:16:45 prod systemd-udevd[246]: sda: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda' failed with exit code 1. Mai 30 17:16:45 prod systemd-udevd[234]: sr0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1. Mai 30 17:16:46 prod systemd-udevd[230]: sda2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda2' failed with exit code 1. Mai 30 17:16:46 prod systemd-udevd[243]: sda11: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda11' failed with exit code 1. Mai 30 17:16:46 prod systemd-udevd[232]: sda9: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda9' failed with exit code 1. Mai 30 17:16:46 prod systemd-udevd[237]: sda7: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda7' failed with exit code 1. Mai 30 17:16:46 prod systemd-udevd[227]: sda4: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda4' failed with exit code 1. Mai 30 17:16:46 prod systemd-udevd[245]: sda10: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda10' failed with exit code 1. Mai 30 17:16:46 prod systemd-udevd[236]: sda6: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda6' failed with exit code 1. Mai 30 17:16:46 prod systemd-udevd[231]: sda3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda3' failed with exit code 1. Mai 30 17:16:46 prod systemd-udevd[246]: sda1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda1' failed with exit code 1. Mai 30 17:16:46 prod systemd-udevd[234]: sda5: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda5' failed with exit code 1. Mai 30 17:16:46 prod systemd-udevd[235]: sda8: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda8' failed with exit code 1. bernie@prod:~/Desktop$ cd /etc bernie@prod:/etc$ ls *rel* lsb-release os-release bernie@prod:/etc$ cat lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=23.04 DISTRIB_CODENAME=lunar DISTRIB_DESCRIPTION="Ubuntu 23.04" bernie@prod:/etc$ cat os-release PRETTY_NAME="Ubuntu 23.04" NAME="Ubuntu" VERSION_ID="23.04" VERSION="23.04 (Lunar Lobster)" VERSION_CODENAME=lunar ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=lunar LOGO=ubuntu-logo bernie@prod:/etc$ uname -a Linux prod 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1966203 Title: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04 Status in snapd: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Configuration: OS:jammy-live-server20220320-amd64.iso CPU:AMD EPYC 7702 64-Core Processor UEFI Version:D8E119A BMC Version:D8BT19I SSD:Intel 1.60TB NVMe SSD Boot mode:legacy Reproduce Steps: 1.Boot into BIOS and set boot mode to legacy 2.install ubuntu 22.04 on NVMe SSD 3.Check syslog log Current behaviors: syslog shows systemd-udevd errors in Ubuntu 22.04 Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1966203/+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 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)
Perhaps every 2 days. Initially it is working find (let's say 2-3 days) and once it hangs (note no GPU hang kernel logs) perhaps every day. I have teams open in chrome browser with notifications on. -- 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/2003339 Title: kwin_x11: The X11 connection broke: I/O error (code 1) Status in KDE Base Workspace: Fix Released Status in Mesa: Fix Released Status in kwin package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in kwin source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Released Status in kwin package in Debian: New Bug description: [Impact] kwin might crash after running some time Two commits have been reverted upstream since 22.2.x branch was closed, needs those backported to fix this. [Test case] Run kwin for a day or so, which is usually enough time to hit this. Crash happens mostly on a notification popups, so system must be actively receiving notifications to test the crash. Without that crash may not happen even in a week of runtime. [Where things could go wrong] This just reverts two commits, and they have been upstream for a few months now, so these causing a regression is unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+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 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)
How often does it happen for you? i'm currently running 4days without the bug. previously it was consistently happening every 24 hours at least once -- 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/2003339 Title: kwin_x11: The X11 connection broke: I/O error (code 1) Status in KDE Base Workspace: Fix Released Status in Mesa: Fix Released Status in kwin package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in kwin source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Released Status in kwin package in Debian: New Bug description: [Impact] kwin might crash after running some time Two commits have been reverted upstream since 22.2.x branch was closed, needs those backported to fix this. [Test case] Run kwin for a day or so, which is usually enough time to hit this. Crash happens mostly on a notification popups, so system must be actively receiving notifications to test the crash. Without that crash may not happen even in a week of runtime. [Where things could go wrong] This just reverts two commits, and they have been upstream for a few months now, so these causing a regression is unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+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 2021805] [NEW] Setting up libxt-dev:amd64 (1:1.2.1-1) ... Errors were encountered while processing: linux-firmware
Public bug reported: unable to install default jdk and jre. These errors were encountered while doing the same. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.12 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: osboxes1406 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Tue May 30 19:55:29 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-04-23 (402 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M MachineType: innotek GmbH VirtualBox PackageArchitecture: all ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-40-generic root=UUID=b67edd03-5aa9-4826-add9-3de240b4c108 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.1 RfKill: SourcePackage: initramfs-tools Title: package linux-firmware 20220329.git681281e4-0ubuntu3.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2021805 Title: Setting up libxt-dev:amd64 (1:1.2.1-1) ... Errors were encountered while processing: linux-firmware Status in initramfs-tools package in Ubuntu: New Bug description: unable to install default jdk and jre. These errors were encountered while doing the same. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.12 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: osboxes1406 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Tue May 30 19:55:29 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-04-23 (402 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M MachineType: innotek GmbH VirtualBox PackageArchitecture: all ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-40-generic root=UUID=b67edd03-5aa9-4826-add9-3de240b4c108 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A
[Touch-packages] [Bug 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)
Unfortunately this is still happening for me - though in much lower rate. My vga is: VGA compatible controller: Intel Corporation Alder Lake-P Integrated Graphics Controller (rev 0c) -- 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/2003339 Title: kwin_x11: The X11 connection broke: I/O error (code 1) Status in KDE Base Workspace: Fix Released Status in Mesa: Fix Released Status in kwin package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in kwin source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Released Status in kwin package in Debian: New Bug description: [Impact] kwin might crash after running some time Two commits have been reverted upstream since 22.2.x branch was closed, needs those backported to fix this. [Test case] Run kwin for a day or so, which is usually enough time to hit this. Crash happens mostly on a notification popups, so system must be actively receiving notifications to test the crash. Without that crash may not happen even in a week of runtime. [Where things could go wrong] This just reverts two commits, and they have been upstream for a few months now, so these causing a regression is unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+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 2021498] Re: Please merge 3.134 into mantic
** Description changed: - Tracking bug + The upstream version 3.134 should be merged into mantic. The current + version is 3.129ubuntu1. + + See the merge conflict report: + https://merges.ubuntu.com/u/adduser/REPORT + + Note: this is a tracking bug ** Description changed: The upstream version 3.134 should be merged into mantic. The current version is 3.129ubuntu1. See the merge conflict report: - https://merges.ubuntu.com/u/adduser/REPORT + https://merges.ubuntu.com/a/adduser/REPORT Note: this is a tracking bug ** Changed in: adduser (Ubuntu) Assignee: (unassigned) => Mateus Rodrigues de Morais (mateus-morais) ** Changed in: adduser (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/2021498 Title: Please merge 3.134 into mantic Status in adduser package in Ubuntu: In Progress Bug description: The upstream version 3.134 should be merged into mantic. The current version is 3.129ubuntu1. See the merge conflict report: https://merges.ubuntu.com/a/adduser/REPORT Note: this is a tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/2021498/+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 1977630] Re: machinectl pull-tar/pull-raw Operation not permitted
** Changed in: systemd (Ubuntu Jammy) Importance: High => Low -- 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/1977630 Title: machinectl pull-tar/pull-raw Operation not permitted Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Triaged Bug description: [impact] machinectl pull-tar does not work, ever [test case] see comment 2 [regression potential] problems/failures during pull-tar operation [scope] needed only in j fixed (indirectly) by upstream commit referenced in original description, which is included in v250, so fixed already in k pull-tar does not fail on f; no fix needed there [original description] There is a bug in systemd 249, where one can't pull any images. This was fixed in version 250, and never got backported. (FIX: https://github.com/systemd/systemd/commit/c40d82abf7b23803aa7394a7a7e24c40c32af851) Hopefully this can be addressed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd-container 249.11-0ubuntu3.1 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 4 04:51:42 2022 InstallationDate: Installed on 2022-06-01 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1977630/+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 2003996] Autopkgtest regression report (software-properties/0.96.24.32.22)
All autopkgtests for the newly accepted software-properties (0.96.24.32.22) for bionic have finished running. The following regressions have been reported in tests triggered by the package: crash/7.2.8-1ubuntu0.18.04.2 (i386) 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/bionic/update_excuses.html#software-properties [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 software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2003996 Title: /usr/bin/software-properties- gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_open:do_open:getresponse:begin:_read_status:readinto:recv_into:read Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Jammy: Fix Released Bug description: * Impact An error is triggered when opening the 'Enable Ubuntu Pro' dialog on a system not connected to internet * Test case Start software-properties-gtk on a offline system, go to the Ubuntu Pro tab, click 'Enable Ubuntu Pro', check that no error report dialog is displayed Verify the error track to ensure there is no report with the new version https://errors.ubuntu.com/problem/032c1f3f3d9b9b05e5087f7e37a05a3d0d40e699 * Regression potential The fix is making the magic token request conditional to the connectivity status, if that was wrong we could end up in a situation where we should display a pincode but don't. --- The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/032c1f3f3d9b9b05e5087f7e37a05a3d0d40e699 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogUaAttach.py", line 144, in poll_for_magic_token response = wait(options) File "/usr/lib/python3/dist-packages/uaclient/api/u/pro/attach/magic/wait/v1.py", line 57, in wait return _wait(options, UAConfig()) File "/usr/lib/python3/dist-packages/uaclient/api/u/pro/attach/magic/wait/v1.py", line 73, in _wait wait_resp = contract.get_magic_attach_token_info( File "/usr/lib/python3/dist-packages/uaclient/contract.py", line 202, in get_magic_attach_token_info response, _ = self.request_url( File "/usr/lib/python3/dist-packages/uaclient/serviceclient.py", line 72, in request_url response, headers = util.readurl( File "/usr/lib/python3/dist-packages/uaclient/util.py", line 324, in readurl resp = request.urlopen(req, timeout=timeout) File "/usr/lib/python3.10/urllib/request.py", line 216, in urlopen return opener.open(url, data, timeout) File "/usr/lib/python3.10/urllib/request.py", line 519, in open response = self._open(req, data) File "/usr/lib/python3.10/urllib/request.py", line 536, in _open result = self._call_chain(self.handle_open, protocol, protocol + File "/usr/lib/python3.10/urllib/request.py", line 496, in _call_chain result = func(*args) File "/usr/lib/python3.10/urllib/request.py", line 1391, in https_open return self.do_open(http.client.HTTPSConnection, req, File "/usr/lib/python3.10/urllib/request.py", line 1352, in do_open r = h.getresponse() File "/usr/lib/python3.10/http/client.py", line 1374, in getresponse response.begin() File "/usr/lib/python3.10/http/client.py", line 318, in begin version, status, reason = self._read_status() File "/usr/lib/python3.10/http/client.py", line 279, in _read_status line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1") File "/usr/lib/python3.10/socket.py", line 705, in readinto return self._sock.recv_into(b) File "/usr/lib/python3.10/ssl.py", line 1274, in recv_into return self.read(nbytes, buffer) File "/usr/lib/python3.10/ssl.py", line 1130, in read return self._sslobj.read(len, buffer) TimeoutError: The read operation timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003996/+subscriptions -- Mailing
[Touch-packages] [Bug 2004245] Autopkgtest regression report (software-properties/0.96.24.32.22)
All autopkgtests for the newly accepted software-properties (0.96.24.32.22) for bionic have finished running. The following regressions have been reported in tests triggered by the package: crash/7.2.8-1ubuntu0.18.04.2 (i386) 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/bionic/update_excuses.html#software-properties [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 software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2004245 Title: /usr/bin/software-properties- gtk:AttributeError:on_radio_toggled:update_state Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Jammy: Fix Released Bug description: * Impact An error is triggered when fetching a pin from the Ubuntu Pro server is failing * Test case Start software-properties-gtk on a system offline or having internet connectivity issue, go to the Ubuntu Pro tab, click 'Enable Ubuntu Pro', check that no error report dialog is displayed Verify the error track to ensure there is no report with the new version https://errors.ubuntu.com/problem/0d4bb9d499df175309552a99a411e2909a88fab1 * Regression potential The fix for that specific issue is to set an initial value to the pin label. If the change of value would confuse some code it would be visible in the Pin section of the Ubuntu Pro tab not reflected the pin code from the server as expected --- The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/0d4bb9d499df175309552a99a411e2909a88fab1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2004245/+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 2004634] Autopkgtest regression report (software-properties/0.96.24.32.22)
All autopkgtests for the newly accepted software-properties (0.96.24.32.22) for bionic have finished running. The following regressions have been reported in tests triggered by the package: crash/7.2.8-1ubuntu0.18.04.2 (i386) 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/bionic/update_excuses.html#software-properties [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 software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2004634 Title: Disable Ubuntu Pro registration when not online Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Jammy: Fix Released Bug description: * Impact The current UI allows the user to try to register to Ubuntu Pro even when the system isn't online, which eventually leads to an error since the client fails to contact the server. The updated design disable the registration UI in those cases and inform the user they need to get online to be able to register which is a better experience. * Test Case - ensure that the machine isn't attached to ubuntu pro (otherwise the screen would not be displayed) and is online $ pro status and `$ pro detach` if needed - disconnect the system, using for example the top panel indicator - start software-properties-gtk and select the Ubuntu Pro tab - click 'Enable Ubuntu Pro' - The dialog controls should be disabled and a string 'Unable to connect to Ubuntu Pro servers. Check your internet connection.' displayed at the bottom - reconnect the system - the dialog control should become active and the label be removed - register to Ubuntu Pro, that should be working * Regression potential If the connectivity check was wrong or not reliable it could be that the dialog controls would be disabled even if the system is online, or that it would fail to detect that the system isn't connected and let the user try to register anyway. The change also adds a new translatable string. Since currently we don't include translations for that new UI it isn't really a regression. We still plan to fix that by the next languagepack update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2004634/+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 2021505] Re: Flaky DEP8 test: saslauthd
** Changed in: cyrus-sasl2 (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/2021505
Title:
Flaky DEP8 test: saslauthd
Status in cyrus-sasl2 package in Ubuntu:
Triaged
Status in cyrus-sasl2 package in Debian:
New
Bug description:
It looks like the saslauthd test is a bit flaky, and more so in
platforms like arm64[1]:
autopkgtest [15:14:52]: test saslauthd: [---
Setting up saslauthd with mecanism sasldb
Authentication of user user1887 with correct password should succeed... FAIL
exit status: 255
output:
connect() : No such file or directory
0:
autopkgtest [15:14:53]: test saslauthd: ---]
autopkgtest [15:14:53]: test saslauthd: - - - - - - - - - - results - - - -
- - - - - -
saslauthdFAIL non-zero exit status 1
The "connect()" error looks like the saslauthd unix socket isn't ready
yet. That test happens right after a saslauthd restart:
echo "Setting up saslauthd with mecanism ${mech}"
setup_saslauthd ${mech} <--- restart happens here
# test correct credentials
echo -n "Authentication of user ${sasluser} with correct password should
succeed... "
result=0
output=$(testsaslauthd -u "${sasluser}" -p "${saslpass}" 2>&1) ||
result=$? <--- this is the authentication test
Maybe we should loop for a few times in a check for the socket, and if
it still fails, add extra logging to the output so it can be
troubleshooted better.
1. https://autopkgtest.ubuntu.com/packages/c/cyrus-sasl2/mantic/arm64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2021505/+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 1848587] Autopkgtest regression report (lxc/3.0.3-0ubuntu1~18.04.3)
All autopkgtests for the newly accepted lxc (3.0.3-0ubuntu1~18.04.3) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxd/3.0.3-0ubuntu1~18.04.2 (i386) 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/bionic/update_excuses.html#lxc [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 lxc in Ubuntu. https://bugs.launchpad.net/bugs/1848587 Title: lxc 3.0.4-0ubuntu1 ADT test failure with linux 5.4.0-1.2 Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Bionic: Fix Committed Bug description: [ Impact ] * Test suite fails due to inexistent device (/dev/network_latency). [ Test Plan ] * Run the test suite. * The test should pass. [ Where problems could occur ] * The regression risk is very low, and the changes only affect the tests, so the regression scope is minimal. [ Other Info ] Original bug report: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/amd64/l/lxc/20191016_150939_0f81d@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/arm64/l/lxc/20191016_152027_0f81d@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/ppc64el/l/lxc/20191016_150251_0f81d@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/s390x/l/lxc/20191016_150201_0f81d@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1848587/+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 1886790] Autopkgtest regression report (lxc/3.0.3-0ubuntu1~18.04.3)
All autopkgtests for the newly accepted lxc (3.0.3-0ubuntu1~18.04.3) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxd/3.0.3-0ubuntu1~18.04.2 (i386) 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/bionic/update_excuses.html#lxc [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 lxc in Ubuntu. https://bugs.launchpad.net/bugs/1886790 Title: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test) Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Bionic: Fix Committed Bug description: [ Impact ] * The device_add_remove_test test fails on the affected series (e.g. Bionic). * Having the test fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for this test. [ Test Plan ] * Run the affected test on an affected series (e.g. Bionic). * The test should pass. [ Where problems could occur ] * The regression risk is very low, and the changes only affect the tests, so the regression scope is minimal. [ Other Info ] Upstream drop of network_latency: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c3082a674f46fe49383b157882c41dfabaa37113 Related to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1848587 Original bug report: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz The failing test seems to be: FAIL: lxc-tests: lxc-test-device-add-remove (0s) --- Adding /dev/network_latency to the container (device_add_remove_test) failed... --- This is a regression from the 4.15/5.3 to 5.4 kernels in Bionic. Note that this testcase is successful on Focal with the same kernel version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1886790/+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 1939537] Autopkgtest regression report (lxc/3.0.3-0ubuntu1~18.04.3)
All autopkgtests for the newly accepted lxc (3.0.3-0ubuntu1~18.04.3) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxd/3.0.3-0ubuntu1~18.04.2 (i386) 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/bionic/update_excuses.html#lxc [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 lxc in Ubuntu. https://bugs.launchpad.net/bugs/1939537 Title: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Confirmed Status in lxc source package in Bionic: Fix Committed Bug description: [ Impact ] * The following tests fail as they try to use inexistent LXC images: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic * Having them fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for these tests. [ Test Plan ] * Run the affected tests on an affected series (e.g. Bionic). * The tests should pass. [ Where problems could occur ] * The regression risk is very low and the changes only affect the tests so the regression scope is minimal. [Other info] Original bug report: Issue found on node onibi 4.15.0-142-generic #146~16.04.1 With bug 1916087 resolved, the following tests: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic Are now failing with: ERROR: Couldn't find a matching image. This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target release is "trusty" or the system release if supported. It will be checked with: ubuntu-distro-info --supported However Xenial is an ESM series now, it won't use xenial as the target release but use trusty instead. The attempt to download trusty image will fail with this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1939537/+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 2004245] Re: /usr/bin/software-properties-gtk:AttributeError:on_radio_toggled:update_state
Testing 0.96.24.32.22 on a bionic system while beeing offline the warning is correctly display and no error prompt is triggered ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2004245 Title: /usr/bin/software-properties- gtk:AttributeError:on_radio_toggled:update_state Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Jammy: Fix Released Bug description: * Impact An error is triggered when fetching a pin from the Ubuntu Pro server is failing * Test case Start software-properties-gtk on a system offline or having internet connectivity issue, go to the Ubuntu Pro tab, click 'Enable Ubuntu Pro', check that no error report dialog is displayed Verify the error track to ensure there is no report with the new version https://errors.ubuntu.com/problem/0d4bb9d499df175309552a99a411e2909a88fab1 * Regression potential The fix for that specific issue is to set an initial value to the pin label. If the change of value would confuse some code it would be visible in the Pin section of the Ubuntu Pro tab not reflected the pin code from the server as expected --- The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/0d4bb9d499df175309552a99a411e2909a88fab1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2004245/+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 2003996] Re: /usr/bin/software-properties-gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_op
Testing 0.96.24.32.22 on a bionic system while beeing offline the warning is correctly display and no error prompt is triggered ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2003996 Title: /usr/bin/software-properties- gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_open:do_open:getresponse:begin:_read_status:readinto:recv_into:read Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Jammy: Fix Released Bug description: * Impact An error is triggered when opening the 'Enable Ubuntu Pro' dialog on a system not connected to internet * Test case Start software-properties-gtk on a offline system, go to the Ubuntu Pro tab, click 'Enable Ubuntu Pro', check that no error report dialog is displayed Verify the error track to ensure there is no report with the new version https://errors.ubuntu.com/problem/032c1f3f3d9b9b05e5087f7e37a05a3d0d40e699 * Regression potential The fix is making the magic token request conditional to the connectivity status, if that was wrong we could end up in a situation where we should display a pincode but don't. --- The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/032c1f3f3d9b9b05e5087f7e37a05a3d0d40e699 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogUaAttach.py", line 144, in poll_for_magic_token response = wait(options) File "/usr/lib/python3/dist-packages/uaclient/api/u/pro/attach/magic/wait/v1.py", line 57, in wait return _wait(options, UAConfig()) File "/usr/lib/python3/dist-packages/uaclient/api/u/pro/attach/magic/wait/v1.py", line 73, in _wait wait_resp = contract.get_magic_attach_token_info( File "/usr/lib/python3/dist-packages/uaclient/contract.py", line 202, in get_magic_attach_token_info response, _ = self.request_url( File "/usr/lib/python3/dist-packages/uaclient/serviceclient.py", line 72, in request_url response, headers = util.readurl( File "/usr/lib/python3/dist-packages/uaclient/util.py", line 324, in readurl resp = request.urlopen(req, timeout=timeout) File "/usr/lib/python3.10/urllib/request.py", line 216, in urlopen return opener.open(url, data, timeout) File "/usr/lib/python3.10/urllib/request.py", line 519, in open response = self._open(req, data) File "/usr/lib/python3.10/urllib/request.py", line 536, in _open result = self._call_chain(self.handle_open, protocol, protocol + File "/usr/lib/python3.10/urllib/request.py", line 496, in _call_chain result = func(*args) File "/usr/lib/python3.10/urllib/request.py", line 1391, in https_open return self.do_open(http.client.HTTPSConnection, req, File "/usr/lib/python3.10/urllib/request.py", line 1352, in do_open r = h.getresponse() File "/usr/lib/python3.10/http/client.py", line 1374, in getresponse response.begin() File "/usr/lib/python3.10/http/client.py", line 318, in begin version, status, reason = self._read_status() File "/usr/lib/python3.10/http/client.py", line 279, in _read_status line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1") File "/usr/lib/python3.10/socket.py", line 705, in readinto return self._sock.recv_into(b) File "/usr/lib/python3.10/ssl.py", line 1274, in recv_into return self.read(nbytes, buffer) File "/usr/lib/python3.10/ssl.py", line 1130, in read return self._sslobj.read(len, buffer) TimeoutError: The read operation timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003996/+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 2004634] Re: Disable Ubuntu Pro registration when not online
Testing 0.96.24.32.22 on bionic, the 'Unable to connect to Ubuntu Pro servers. Check your internet connection.' warning is correctly displayed when disconnected and goes away after reconnecting. The error which existed in .22 about the non existing API is also resolved ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2004634 Title: Disable Ubuntu Pro registration when not online Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Jammy: Fix Released Bug description: * Impact The current UI allows the user to try to register to Ubuntu Pro even when the system isn't online, which eventually leads to an error since the client fails to contact the server. The updated design disable the registration UI in those cases and inform the user they need to get online to be able to register which is a better experience. * Test Case - ensure that the machine isn't attached to ubuntu pro (otherwise the screen would not be displayed) and is online $ pro status and `$ pro detach` if needed - disconnect the system, using for example the top panel indicator - start software-properties-gtk and select the Ubuntu Pro tab - click 'Enable Ubuntu Pro' - The dialog controls should be disabled and a string 'Unable to connect to Ubuntu Pro servers. Check your internet connection.' displayed at the bottom - reconnect the system - the dialog control should become active and the label be removed - register to Ubuntu Pro, that should be working * Regression potential If the connectivity check was wrong or not reliable it could be that the dialog controls would be disabled even if the system is online, or that it would fail to detect that the system isn't connected and let the user try to register anyway. The change also adds a new translatable string. Since currently we don't include translations for that new UI it isn't really a regression. We still plan to fix that by the next languagepack update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2004634/+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 1848587] Re: lxc 3.0.4-0ubuntu1 ADT test failure with linux 5.4.0-1.2
** Description changed: + [ Impact ] + + * Test suite fails due to inexistent device (/dev/network_latency). + + [ Test Plan ] + + * Run the test suite. + * The test should pass. + + [ Where problems could occur ] + + * The regression risk is very low, and the changes only affect the + tests, so the regression scope is minimal. + + [ Other Info ] + + Original bug report: + Testing failed on: - amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/amd64/l/lxc/20191016_150939_0f81d@/log.gz - arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/arm64/l/lxc/20191016_152027_0f81d@/log.gz - ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/ppc64el/l/lxc/20191016_150251_0f81d@/log.gz - s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/s390x/l/lxc/20191016_150201_0f81d@/log.gz + amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/amd64/l/lxc/20191016_150939_0f81d@/log.gz + arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/arm64/l/lxc/20191016_152027_0f81d@/log.gz + ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/ppc64el/l/lxc/20191016_150251_0f81d@/log.gz + s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/s390x/l/lxc/20191016_150201_0f81d@/log.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1848587 Title: lxc 3.0.4-0ubuntu1 ADT test failure with linux 5.4.0-1.2 Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Bionic: Fix Committed Bug description: [ Impact ] * Test suite fails due to inexistent device (/dev/network_latency). [ Test Plan ] * Run the test suite. * The test should pass. [ Where problems could occur ] * The regression risk is very low, and the changes only affect the tests, so the regression scope is minimal. [ Other Info ] Original bug report: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/amd64/l/lxc/20191016_150939_0f81d@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/arm64/l/lxc/20191016_152027_0f81d@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/ppc64el/l/lxc/20191016_150251_0f81d@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/s390x/l/lxc/20191016_150201_0f81d@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1848587/+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 1886790] Re: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test)
** Description changed: + [ Impact ] + + * The device_add_remove_test test fails on the affected series (e.g. Bionic). + * Having the test fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for this test. + + [ Test Plan ] + + * Run the affected test on an affected series (e.g. Bionic). + * The test should pass. + + [ Other Info ] + + Upstream drop of network_latency: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c3082a674f46fe49383b157882c41dfabaa37113 + Related to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1848587 + Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz The failing test seems to be: FAIL: lxc-tests: lxc-test-device-add-remove (0s) --- Adding /dev/network_latency to the container (device_add_remove_test) failed... --- This is a regression from the 4.15/5.3 to 5.4 kernels in Bionic. Note that this testcase is successful on Focal with the same kernel version. ** Description changed: [ Impact ] - * The device_add_remove_test test fails on the affected series (e.g. Bionic). - * Having the test fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for this test. + * The device_add_remove_test test fails on the affected series (e.g. Bionic). + * Having the test fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for this test. [ Test Plan ] - * Run the affected test on an affected series (e.g. Bionic). - * The test should pass. + * Run the affected test on an affected series (e.g. Bionic). + * The test should pass. [ Other Info ] Upstream drop of network_latency: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c3082a674f46fe49383b157882c41dfabaa37113 Related to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1848587 + + Original bug report: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz The failing test seems to be: FAIL: lxc-tests: lxc-test-device-add-remove (0s) --- Adding /dev/network_latency to the container (device_add_remove_test) failed... --- This is a regression from the 4.15/5.3 to 5.4 kernels in Bionic. Note that this testcase is successful on Focal with the same kernel version. ** Description changed: [ Impact ] * The device_add_remove_test test fails on the affected series (e.g. Bionic). * Having the test fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for this test. [ Test Plan ] * Run the affected test on an affected series (e.g. Bionic). * The test should pass. + + [ Where problems could occur ] + + * The regression risk is very low, and the changes only affect the + tests, so the regression scope is minimal. [ Other Info ] Upstream drop of network_latency: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c3082a674f46fe49383b157882c41dfabaa37113 Related to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1848587 Original bug report: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz ppc64el:
[Touch-packages] [Bug 1939537] Re: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases
** Description changed: [ Impact ] - * The following tests fail as they try to use inexistent LXC images: -* lxc-test-apparmor-mount - * lxc-test-autostart - * lxc-test-unpriv - * lxc-test-usernic + * The following tests fail as they try to use inexistent LXC images: + * lxc-test-apparmor-mount + * lxc-test-autostart + * lxc-test-unpriv + * lxc-test-usernic - * Having them fixed for the affected series (for example Bionic) will allow us to run the LXC test suite without maintaining local changes. - + * Having them fixed for the affected series (for example, Bionic) will + allow us to run the LXC test suite without maintaining local changes for + these tests. [ Test Plan ] - * Run the affected tests on an affected series (e.g. Bionic). + * Run the affected tests on an affected series (e.g. Bionic). [ Where problems could occur ] - * The regression risk is very low and the changes only affect the tests + * The regression risk is very low and the changes only affect the tests so the regression scope is minimal. [Other info] Original bug report: Issue found on node onibi 4.15.0-142-generic #146~16.04.1 With bug 1916087 resolved, the following tests: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic Are now failing with: ERROR: Couldn't find a matching image. This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target release is "trusty" or the system release if supported. It will be checked with: ubuntu-distro-info --supported However Xenial is an ESM series now, it won't use xenial as the target release but use trusty instead. The attempt to download trusty image will fail with this error. ** Description changed: [ Impact ] * The following tests fail as they try to use inexistent LXC images: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic * Having them fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for these tests. [ Test Plan ] * Run the affected tests on an affected series (e.g. Bionic). + * The tests should pass. [ Where problems could occur ] * The regression risk is very low and the changes only affect the tests so the regression scope is minimal. [Other info] Original bug report: Issue found on node onibi 4.15.0-142-generic #146~16.04.1 With bug 1916087 resolved, the following tests: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic Are now failing with: ERROR: Couldn't find a matching image. This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target release is "trusty" or the system release if supported. It will be checked with: ubuntu-distro-info --supported However Xenial is an ESM series now, it won't use xenial as the target release but use trusty instead. The attempt to download trusty image will fail with this error. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1939537 Title: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Confirmed Status in lxc source package in Bionic: Fix Committed Bug description: [ Impact ] * The following tests fail as they try to use inexistent LXC images: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic * Having them fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for these tests. [ Test Plan ] * Run the affected tests on an affected series (e.g. Bionic). * The tests should pass. [ Where problems could occur ] * The regression risk is very low and the changes only affect the tests so the regression scope is minimal. [Other info] Original bug report: Issue found on node onibi 4.15.0-142-generic #146~16.04.1 With bug 1916087 resolved, the following tests: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic Are now failing with: ERROR: Couldn't find a matching image. This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target release is "trusty" or the system release if supported. It will be checked with: ubuntu-distro-info --supported However Xenial is an ESM series now, it won't use xenial as the target release but use trusty instead. The attempt to download trusty image will fail with this error. To manage notifications about this bug go to:
[Touch-packages] [Bug 2004245] Please test proposed package
Hello errors.ubuntu.com, or anyone else affected, Accepted software-properties into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/software-properties/0.96.24.32.22 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2004245 Title: /usr/bin/software-properties- gtk:AttributeError:on_radio_toggled:update_state Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Jammy: Fix Released Bug description: * Impact An error is triggered when fetching a pin from the Ubuntu Pro server is failing * Test case Start software-properties-gtk on a system offline or having internet connectivity issue, go to the Ubuntu Pro tab, click 'Enable Ubuntu Pro', check that no error report dialog is displayed Verify the error track to ensure there is no report with the new version https://errors.ubuntu.com/problem/0d4bb9d499df175309552a99a411e2909a88fab1 * Regression potential The fix for that specific issue is to set an initial value to the pin label. If the change of value would confuse some code it would be visible in the Pin section of the Ubuntu Pro tab not reflected the pin code from the server as expected --- The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/0d4bb9d499df175309552a99a411e2909a88fab1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2004245/+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 2004634] Re: Disable Ubuntu Pro registration when not online
Hello Sebastien, or anyone else affected, Accepted software-properties into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/software-properties/0.96.24.32.22 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-failed-bionic ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2004634 Title: Disable Ubuntu Pro registration when not online Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Jammy: Fix Released Bug description: * Impact The current UI allows the user to try to register to Ubuntu Pro even when the system isn't online, which eventually leads to an error since the client fails to contact the server. The updated design disable the registration UI in those cases and inform the user they need to get online to be able to register which is a better experience. * Test Case - ensure that the machine isn't attached to ubuntu pro (otherwise the screen would not be displayed) and is online $ pro status and `$ pro detach` if needed - disconnect the system, using for example the top panel indicator - start software-properties-gtk and select the Ubuntu Pro tab - click 'Enable Ubuntu Pro' - The dialog controls should be disabled and a string 'Unable to connect to Ubuntu Pro servers. Check your internet connection.' displayed at the bottom - reconnect the system - the dialog control should become active and the label be removed - register to Ubuntu Pro, that should be working * Regression potential If the connectivity check was wrong or not reliable it could be that the dialog controls would be disabled even if the system is online, or that it would fail to detect that the system isn't connected and let the user try to register anyway. The change also adds a new translatable string. Since currently we don't include translations for that new UI it isn't really a regression. We still plan to fix that by the next languagepack update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2004634/+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 2003996] Please test proposed package
Hello errors.ubuntu.com, or anyone else affected, Accepted software-properties into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/software-properties/0.96.24.32.22 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2003996 Title: /usr/bin/software-properties- gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_open:do_open:getresponse:begin:_read_status:readinto:recv_into:read Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Jammy: Fix Released Bug description: * Impact An error is triggered when opening the 'Enable Ubuntu Pro' dialog on a system not connected to internet * Test case Start software-properties-gtk on a offline system, go to the Ubuntu Pro tab, click 'Enable Ubuntu Pro', check that no error report dialog is displayed Verify the error track to ensure there is no report with the new version https://errors.ubuntu.com/problem/032c1f3f3d9b9b05e5087f7e37a05a3d0d40e699 * Regression potential The fix is making the magic token request conditional to the connectivity status, if that was wrong we could end up in a situation where we should display a pincode but don't. --- The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/032c1f3f3d9b9b05e5087f7e37a05a3d0d40e699 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogUaAttach.py", line 144, in poll_for_magic_token response = wait(options) File "/usr/lib/python3/dist-packages/uaclient/api/u/pro/attach/magic/wait/v1.py", line 57, in wait return _wait(options, UAConfig()) File "/usr/lib/python3/dist-packages/uaclient/api/u/pro/attach/magic/wait/v1.py", line 73, in _wait wait_resp = contract.get_magic_attach_token_info( File "/usr/lib/python3/dist-packages/uaclient/contract.py", line 202, in get_magic_attach_token_info response, _ = self.request_url( File "/usr/lib/python3/dist-packages/uaclient/serviceclient.py", line 72, in request_url response, headers = util.readurl( File "/usr/lib/python3/dist-packages/uaclient/util.py", line 324, in readurl resp = request.urlopen(req, timeout=timeout) File "/usr/lib/python3.10/urllib/request.py", line 216, in urlopen return opener.open(url, data, timeout) File "/usr/lib/python3.10/urllib/request.py", line 519, in open response = self._open(req, data) File "/usr/lib/python3.10/urllib/request.py", line 536, in _open result = self._call_chain(self.handle_open, protocol, protocol + File "/usr/lib/python3.10/urllib/request.py", line 496, in _call_chain result = func(*args) File "/usr/lib/python3.10/urllib/request.py", line 1391, in https_open return self.do_open(http.client.HTTPSConnection, req, File "/usr/lib/python3.10/urllib/request.py", line 1352, in do_open r = h.getresponse() File "/usr/lib/python3.10/http/client.py", line 1374, in getresponse response.begin() File "/usr/lib/python3.10/http/client.py", line 318, in begin
[Touch-packages] [Bug 1939537] Re: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases
** Description changed: + [ Impact ] + + * The following tests fail as they try to use inexistent LXC images: +* lxc-test-apparmor-mount + * lxc-test-autostart + * lxc-test-unpriv + * lxc-test-usernic + + * Having them fixed for the affected series (for example Bionic) will allow us to run the LXC test suite without maintaining local changes. + + + [ Test Plan ] + + * Run the affected tests on an affected series (e.g. Bionic). + + [ Where problems could occur ] + + * The regression risk is very low and the changes only affect the tests + so the regression scope is minimal. + + [Other info] + + Original bug report: + Issue found on node onibi 4.15.0-142-generic #146~16.04.1 With bug 1916087 resolved, the following tests: - * lxc-test-apparmor-mount - * lxc-test-autostart - * lxc-test-unpriv - * lxc-test-usernic + * lxc-test-apparmor-mount + * lxc-test-autostart + * lxc-test-unpriv + * lxc-test-usernic Are now failing with: - ERROR: Couldn't find a matching image. - + ERROR: Couldn't find a matching image. + This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target release is "trusty" or the system release if supported. It will be checked with: - ubuntu-distro-info --supported + ubuntu-distro-info --supported However Xenial is an ESM series now, it won't use xenial as the target release but use trusty instead. The attempt to download trusty image will fail with this error. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1939537 Title: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Confirmed Status in lxc source package in Bionic: Fix Committed Bug description: [ Impact ] * The following tests fail as they try to use inexistent LXC images: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic * Having them fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for these tests. [ Test Plan ] * Run the affected tests on an affected series (e.g. Bionic). [ Where problems could occur ] * The regression risk is very low and the changes only affect the tests so the regression scope is minimal. [Other info] Original bug report: Issue found on node onibi 4.15.0-142-generic #146~16.04.1 With bug 1916087 resolved, the following tests: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic Are now failing with: ERROR: Couldn't find a matching image. This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target release is "trusty" or the system release if supported. It will be checked with: ubuntu-distro-info --supported However Xenial is an ESM series now, it won't use xenial as the target release but use trusty instead. The attempt to download trusty image will fail with this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1939537/+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 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency
I saw nothing specific to tzdata in 180_ecpg.t. I tried 180_ecpg.t from postgresql-12 locally and it succeeded. Then I retried the autopkgtest and it succeeded as well. So all autopkgtest issues are resolved now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017999 Title: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency Status in python-tz package in Ubuntu: Fix Released Status in tzdata package in Ubuntu: Fix Released Status in python-tz source package in Focal: Invalid Status in tzdata source package in Focal: Fix Committed Status in python-tz source package in Jammy: Invalid Status in tzdata source package in Jammy: Fix Committed Status in python-tz source package in Kinetic: Invalid Status in tzdata source package in Kinetic: Fix Committed Status in python-tz source package in Lunar: Fix Committed Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recent updates have been using `PACKRATDATA=backzone` in order to add all out-of-scope lower-quality pre-1970 data back that existed in earlier tzadata releases (see bug #2003797). However it also leads to time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol, and Pacific/Enderbury to change: compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown [ Test Plan ] Add an autopkgtest test case for post-1970 symlink consistency: Check that the timezones for today and in half a year (= to cover DST changes) do not change compared to building them without `PACKRATDATA=backzone`. The mentioned timezones that differed can also be tested manually. Running following commands should have the same output (the output mentioned here is from tzdata 2023c-0ubuntu0.22.04.0): ``` $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z" Fri Apr 28 06:49:00 PDT 2023 $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z" Fri Apr 28 15:49:00 CEST 2023 $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z" Fri Apr 28 16:49:00 EEST 2023 ``` [ Where problems could occur ] Timezone data could be wrong. Systems with incorrect timezone set may observe unexpected time shift when updating the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency
Looking at the autopkgtest, several of the failing ones got resolved (e.g. all for python-tz on lunar). Remaining failing ones: * tzdata on lunar: - chrony/4.3-1ubuntu4 on armhf: Flaky test case (see bug #2002910) * tzdata on focal: - postgresql-12/12.14-0ubuntu0.20.04.1 on amd64: test 8 of 180_ecpg.t -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017999 Title: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency Status in python-tz package in Ubuntu: Fix Released Status in tzdata package in Ubuntu: Fix Released Status in python-tz source package in Focal: Invalid Status in tzdata source package in Focal: Fix Committed Status in python-tz source package in Jammy: Invalid Status in tzdata source package in Jammy: Fix Committed Status in python-tz source package in Kinetic: Invalid Status in tzdata source package in Kinetic: Fix Committed Status in python-tz source package in Lunar: Fix Committed Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recent updates have been using `PACKRATDATA=backzone` in order to add all out-of-scope lower-quality pre-1970 data back that existed in earlier tzadata releases (see bug #2003797). However it also leads to time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol, and Pacific/Enderbury to change: compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown [ Test Plan ] Add an autopkgtest test case for post-1970 symlink consistency: Check that the timezones for today and in half a year (= to cover DST changes) do not change compared to building them without `PACKRATDATA=backzone`. The mentioned timezones that differed can also be tested manually. Running following commands should have the same output (the output mentioned here is from tzdata 2023c-0ubuntu0.22.04.0): ``` $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z" Fri Apr 28 06:49:00 PDT 2023 $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z" Fri Apr 28 15:49:00 CEST 2023 $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z" Fri Apr 28 16:49:00 EEST 2023 ``` [ Where problems could occur ] Timezone data could be wrong. Systems with incorrect timezone set may observe unexpected time shift when updating the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 1886790] Re: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test)
Hello Kleber, or anyone else affected, Accepted lxc into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxc/3.0.3-0ubuntu1~18.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: lxc (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1886790 Title: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test) Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Bionic: Fix Committed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz The failing test seems to be: FAIL: lxc-tests: lxc-test-device-add-remove (0s) --- Adding /dev/network_latency to the container (device_add_remove_test) failed... --- This is a regression from the 4.15/5.3 to 5.4 kernels in Bionic. Note that this testcase is successful on Focal with the same kernel version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1886790/+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 1848587] Re: lxc 3.0.4-0ubuntu1 ADT test failure with linux 5.4.0-1.2
Hello Seth, or anyone else affected, Accepted lxc into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxc/3.0.3-0ubuntu1~18.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: lxc (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1848587 Title: lxc 3.0.4-0ubuntu1 ADT test failure with linux 5.4.0-1.2 Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Bionic: Fix Committed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/amd64/l/lxc/20191016_150939_0f81d@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/arm64/l/lxc/20191016_152027_0f81d@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/ppc64el/l/lxc/20191016_150251_0f81d@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/s390x/l/lxc/20191016_150201_0f81d@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1848587/+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 1939537] Re: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases
Hello Po-Hsu, or anyone else affected, Accepted lxc into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxc/3.0.3-0ubuntu1~18.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: lxc (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1939537 Title: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Confirmed Status in lxc source package in Bionic: Fix Committed Bug description: Issue found on node onibi 4.15.0-142-generic #146~16.04.1 With bug 1916087 resolved, the following tests: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic Are now failing with: ERROR: Couldn't find a matching image. This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target release is "trusty" or the system release if supported. It will be checked with: ubuntu-distro-info --supported However Xenial is an ESM series now, it won't use xenial as the target release but use trusty instead. The attempt to download trusty image will fail with this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1939537/+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 2020838] Re: [regression][jammy] augenrules Error sending add rule data request (No such file or directory)
Hi Seth, Thank you for the advice of "-i". It works if I append "-i" into the problematic line. It's strange that: 1) I can not see any difference between /home/ubuntu/test.sh, / opt/test.sh, /etc/test.sh and /usr/bin/test.sh, as there is no separated partition lsblk vda 252:0020G 0 disk ├─vda1 252:10 19.9G 0 part / ├─vda14 252:14 0 4M 0 part └─vda15 252:15 0 106M 0 part /boot/efi 2) Focal can not reproduce the issue. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/2020838 Title: [regression][jammy] augenrules Error sending add rule data request (No such file or directory) Status in audit package in Ubuntu: New Bug description: The rule '-a always,exit -F path=/home/ubuntu/test.sh -F perm=x -F auid>=1000 -F auid!=unset -k privileged' can not be loaded during system boot up. # lsb_release -rc Release: 22.04 Codename: jammy # dpkg -l|grep audit ii auditd 1:3.0.7-1build1 amd64User space tools for security auditing ii libaudit-common 1:3.0.7-1build1 all Dynamic library for security auditing - common files ii libaudit1:amd64 1:3.0.7-1build1 amd64Dynamic library for security auditing ii libauparse0:amd64 1:3.0.7-1build1 amd64Dynamic library for parsing security auditing # cat /etc/audit/rules.d/audit.rules|grep -v ^#|grep -v ^$ -D -a always,exit -F path=/home/ubuntu/test.sh -F perm=x -F auid>=1000 -F auid!=unset -k privileged -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=unset -k mounts -b 8192 --backlog_wait_time 6 -f 1 # ls -l /home/ubuntu/test.sh -rwxr-xr-x 1 root ubuntu 19 May 25 14:19 /home/ubuntu/test.sh # cat /home/ubuntu/test.sh #!/bin/bash echo 1 # >/etc/audit/audit.rules reboot the system, no rule can be loaded # auditctl -l No rules syslog: May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: Error sending add rule data request (No such file or directory) May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: There was an error in line 5 of /etc/audit/audit.rules May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: No rules May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: enabled 1 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: failure 1 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: pid 476 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: rate_limit 0 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_limit 8192 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: lost 0 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog 0 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_wait_time 15000 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_wait_time_actual 0 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: enabled 1 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: failure 1 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: pid 476 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: rate_limit 0 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_limit 8192 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: lost 0 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog 0 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_wait_time 15000 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_wait_time_actual 0 # cat /etc/audit/audit.rules ## This file is automatically generated from /etc/audit/rules.d -D -b 8192 -f 1 -a always,exit -F path=/home/ubuntu/test.sh -F perm=x -F auid>=1000 -F auid!=unset -k privileged -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=unset -k mounts --backlog_wait_time 6 But I can manually load the rule file. Seems this issue only happen during system boot up. # auditctl -R /etc/audit/audit.rules No rules enabled 1 failure 1 pid 476 rate_limit 0 backlog_limit 8192 lost 0 backlog 4 backlog_wait_time 15000 backlog_wait_time_actual 0 enabled 1 failure 1 pid 476 rate_limit 0 backlog_limit 8192 lost 0 backlog 4 backlog_wait_time 15000 backlog_wait_time_actual 0 enabled 1 failure 1 pid 476 rate_limit 0 backlog_limit 8192 lost 0 backlog 14 backlog_wait_time 6 backlog_wait_time_actual 0 # auditctl -l -a always,exit -S all -F path=/home/ubuntu/test.sh -F perm=x -F auid>=1000 -F auid!=-1 -F key=privileged -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=-1 -F key=mounts If I move the file /home/ubuntu/test.sh to / opt/test.sh or /etc/test.sh /usr/bin/test.sh, then I can not reproduce the issue. Additionally, I have ruled out AppArmor as a
