[Touch-packages] [Bug 2013257] Re: two-finger-zoom not working on Elan touchpad
** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Summary changed: - two-finger-zoom not working on Elan touchpad + Multi-touch gestures don't work in Xorg sessions ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Tags added: multitouch ** Summary changed: - Multi-touch gestures don't work in Xorg sessions + Multi-touch touchpad gestures don't work in Xorg sessions ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/2013257 Title: Multi-touch touchpad gestures don't work in Xorg sessions Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: On my Elan touchpad, using the two finger pinch zoom gesture does not work, neither in Firefox nor in LibreOffice. Other gestures like two- finger-scrolling work fine. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.157 Wed Oct 12 09:19:07 UTC 2022 GCC version: ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 30 04:09:14 2023 DistUpgraded: 2023-03-17 13:44:54,645 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] 3rd Gen Core processor Graphics Controller [1462:10d7] NVIDIA Corporation GK107M [GeForce GTX 660M] [10de:0fd4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK107M [GeForce GTX 660M] [1462:10d7] InstallationDate: Installed on 2023-02-24 (33 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Micro-Star International Co., Ltd. GE60 0NC\0ND ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=c297f9ee-3b13-4ae2-a84f-5197cc9c13d4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-03-17 (12 days ago) dmi.bios.date: 11/08/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16GAIMS.513 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16GA dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16GAIMS.513:bd11/08/2012:br4.6:svnMicro-StarInternationalCo.,Ltd.:pnGE600NC\0ND:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GA:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GE60 0NC\0ND dmi.product.sku: To be filled by O.E.M. dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 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.4-2ubuntu1.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/+bug/2013257/+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 1895486] Re: [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll Lock" keyboards
Continued in bug 1892747. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1895486 Title: [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll Lock" keyboards Status in GNOME Shell: New Status in xkeyboard-config package in Ubuntu: Fix Released Bug description: I use Ubuntu 20.04.1. After some use, I noticed a delay when using keyboard media controls (for example: increase volume audio). The first time I push these key Gnome hangs for a short time before display the action on the screen. (This problem is still happening in Ubuntu 18.04 too. Even worse some times, the system crashes when using media keys.) For some reason, my Gnome freezes when using Fn keys, or when I try to use two keyboards. A friend of mine pointed to me that it occurs when switching to a keyboard layout that has Scroll Lock enabled, so I disabled it in the X11 keyboard layout file for my language, and it solved the problem. A workaround to solve the problem is: 1) Opened the keyboard layout file for my language, in my case: sudo nano /usr/share/X11/xkb/symbols/br 2) Commented the line: modifier_map Mod3 { Scroll_Lock }; 3) Logged out and logged in again or run command setxkbmap. These steps are specific for the Brazilian Portuguese ABNT2 Layout and may not work for other layouts, but it can help you find a similar solution. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: x11-xkb-utils 7.7+5 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .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 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Sep 13 21:52:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Subsystem: Dell UHD Graphics 630 (Desktop) [1028:0859] NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107 [GeForce GTX 1050 Ti] [1028:3512] InstallationDate: Installed on 2020-08-15 (29 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) MachineType: Dell Inc. XPS 8930 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=706721d5-f527-41fe-98ca-96706a36bb42 ro quiet splash SourcePackage: x11-xkb-utils UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.15 dmi.board.name: 0T88YD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.15:bd07/01/2020:svnDellInc.:pnXPS8930:pvr1.1.15:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.15 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 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:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1895486/+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 2013255] Re: changing screen brightness with keyboard hotkeys reacts very slow
*** This bug is a duplicate of bug 1892747 *** https://bugs.launchpad.net/bugs/1892747 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1892747, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** This bug has been marked a duplicate of bug 1892747 GNOME hangs while changing display brightness from keyboard shortcut -- 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/2013255 Title: changing screen brightness with keyboard hotkeys reacts very slow Status in gnome-shell package in Ubuntu: Confirmed Bug description: Using "Fn" key + brightness up/down (arrow up/down) keys reacts very delayed (up to 2 seconds) and system freezes enirely during these brightness-changes being applied by the system. It however works flawless in the brightness slider menu in the top right. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.157 Wed Oct 12 09:19:07 UTC 2022 GCC version: ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 30 03:38:51 2023 DistUpgraded: 2023-03-17 13:44:54,645 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] 3rd Gen Core processor Graphics Controller [1462:10d7] NVIDIA Corporation GK107M [GeForce GTX 660M] [10de:0fd4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK107M [GeForce GTX 660M] [1462:10d7] InstallationDate: Installed on 2023-02-24 (33 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Micro-Star International Co., Ltd. GE60 0NC\0ND ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=c297f9ee-3b13-4ae2-a84f-5197cc9c13d4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-03-17 (12 days ago) dmi.bios.date: 11/08/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16GAIMS.513 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16GA dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16GAIMS.513:bd11/08/2012:br4.6:svnMicro-StarInternationalCo.,Ltd.:pnGE600NC\0ND:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GA:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GE60 0NC\0ND dmi.product.sku: To be filled by O.E.M. dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 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.4-2ubuntu1.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/+bug/2013255/+subscripti
[Touch-packages] [Bug 2013128] Re: [feature request] Upgrade libglx-mesa0
would've been best to just add the info from the question instead, as your request didn't even contain the link to the fix ** Description changed: + I have a bug that occurs in Ubuntu 22.04's most up to date libmesa + related packages (=22.2.5-0ubuntu0.1~22.04.1) that was not there in + =22.0.1-1ubuntu2. It has since been solved in mesa's repo and pulled + into debian's repo. I do not know the proper way to request an updated + version be made for Ubuntu. I've manually installed many different + versions of libmesa to test on my own that it was working in an older + version, is broken in this update, and was fixed again in 22.3.4 and + 22.3.5. + + The one-line fix is implemented here in libmesa's repo: + https://gitlab.freedesktop.org/mesa/mesa/-/commit/7e68cf91d74e6bd9a88c2b52417451d9afec4782/pipelines + + -- + Feature Request: Upgrade mesa libraries to apply upstream bugfix to a bug introduced in 22.2.5-0ubuntu0.1~22.04.1. I was directed to report this bug via my question at answers.launchpad.net/ubuntu: https://answers.launchpad.net/ubuntu/+question/705988 Please let me know if you need further information. Thanks! - - > lsb_release -rd + > lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 - > apt-cache policy libglx-mesa0 + > apt-cache policy libglx-mesa0 libglx-mesa0: - Installed: 22.2.5-0ubuntu0.1~22.04.1 - Candidate: 22.2.5-0ubuntu0.1~22.04.1 - Version table: - *** 22.2.5-0ubuntu0.1~22.04.1 500 - 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 22.0.1-1ubuntu2 500 - 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages + Installed: 22.2.5-0ubuntu0.1~22.04.1 + Candidate: 22.2.5-0ubuntu0.1~22.04.1 + Version table: + *** 22.2.5-0ubuntu0.1~22.04.1 500 + 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 22.0.1-1ubuntu2 500 + 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libglx-mesa0 22.2.5-0ubuntu0.1~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: i3 Date: Tue Mar 28 15:30:59 2023 InstallationDate: Installed on 2022-04-28 (334 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2022-04-29T14:47:14.568862 ** Also affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Fix Released ** Also affects: mesa (Ubuntu Kinetic) 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/2013128 Title: [feature request] Upgrade libglx-mesa0 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: New Status in mesa source package in Kinetic: New Bug description: I have a bug that occurs in Ubuntu 22.04's most up to date libmesa related packages (=22.2.5-0ubuntu0.1~22.04.1) that was not there in =22.0.1-1ubuntu2. It has since been solved in mesa's repo and pulled into debian's repo. I do not know the proper way to request an updated version be made for Ubuntu. I've manually installed many different versions of libmesa to test on my own that it was working in an older version, is broken in this update, and was fixed again in 22.3.4 and 22.3.5. The one-line fix is implemented here in libmesa's repo: https://gitlab.freedesktop.org/mesa/mesa/-/commit/7e68cf91d74e6bd9a88c2b52417451d9afec4782/pipelines -- Feature Request: Upgrade mesa libraries to apply upstream bugfix to a bug introduced in 22.2.5-0ubuntu0.1~22.04.1. I was directed to report this bug via my question at answers.launchpad.net/ubuntu: https://answers.launchpad.net/ubuntu/+question/705988 Please let me know if you need further information. Thanks! > lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 > apt-cache policy libglx-mesa0 libglx-mesa0: Installed: 22.2.5-0ubuntu0.1~22.04.1 Candidate: 22.2.5-0ubuntu0.1~22.04.1 Version table: *** 22.2.5-0ubuntu0.1~22.04.1
[Touch-packages] [Bug 2008952] Re: DNS failure while trying to fetch user-data
This bug was fixed in the package livecd-rootfs - 2.817 --- livecd-rootfs (2.817) lunar; urgency=medium [ John Chittum ] * revert ipc change. kernel 6.2 will have the correct setting -- Steve Langasek Mon, 27 Mar 2023 12:11:06 -0700 ** Changed in: livecd-rootfs (Ubuntu) Status: Fix Committed => Fix Released -- 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/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: In Progress Status in netplan: Invalid Status in subiquity: New Status in livecd-rootfs package in Ubuntu: Fix Released Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+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 2013255] Re: changing screen brightness with keyboard hotkeys reacts very slow
** 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/2013255 Title: changing screen brightness with keyboard hotkeys reacts very slow Status in xorg package in Ubuntu: New Bug description: Using "Fn" key + brightness up/down (arrow up/down) keys reacts very delayed (up to 2 seconds) and system freezes enirely during these brightness-changes being applied by the system. It however works flawless in the brightness slider menu in the top right. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.157 Wed Oct 12 09:19:07 UTC 2022 GCC version: ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 30 03:38:51 2023 DistUpgraded: 2023-03-17 13:44:54,645 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] 3rd Gen Core processor Graphics Controller [1462:10d7] NVIDIA Corporation GK107M [GeForce GTX 660M] [10de:0fd4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK107M [GeForce GTX 660M] [1462:10d7] InstallationDate: Installed on 2023-02-24 (33 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Micro-Star International Co., Ltd. GE60 0NC\0ND ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=c297f9ee-3b13-4ae2-a84f-5197cc9c13d4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-03-17 (12 days ago) dmi.bios.date: 11/08/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16GAIMS.513 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16GA dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16GAIMS.513:bd11/08/2012:br4.6:svnMicro-StarInternationalCo.,Ltd.:pnGE600NC\0ND:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GA:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GE60 0NC\0ND dmi.product.sku: To be filled by O.E.M. dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 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.4-2ubuntu1.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/2013255/+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 2013257] Re: two-finger-zoom not working on Elan touchpad
** 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/2013257 Title: two-finger-zoom not working on Elan touchpad Status in xorg package in Ubuntu: New Bug description: On my Elan touchpad, using the two finger pinch zoom gesture does not work, neither in Firefox nor in LibreOffice. Other gestures like two- finger-scrolling work fine. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.157 Wed Oct 12 09:19:07 UTC 2022 GCC version: ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 30 04:09:14 2023 DistUpgraded: 2023-03-17 13:44:54,645 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] 3rd Gen Core processor Graphics Controller [1462:10d7] NVIDIA Corporation GK107M [GeForce GTX 660M] [10de:0fd4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK107M [GeForce GTX 660M] [1462:10d7] InstallationDate: Installed on 2023-02-24 (33 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Micro-Star International Co., Ltd. GE60 0NC\0ND ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=c297f9ee-3b13-4ae2-a84f-5197cc9c13d4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-03-17 (12 days ago) dmi.bios.date: 11/08/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16GAIMS.513 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16GA dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16GAIMS.513:bd11/08/2012:br4.6:svnMicro-StarInternationalCo.,Ltd.:pnGE600NC\0ND:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GA:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GE60 0NC\0ND dmi.product.sku: To be filled by O.E.M. dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 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.4-2ubuntu1.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/2013257/+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 2013255] [NEW] changing screen brightness with keyboard hotkeys reacts very slow
You have been subscribed to a public bug: Using "Fn" key + brightness up/down (arrow up/down) keys reacts very delayed (up to 2 seconds) and system freezes enirely during these brightness-changes being applied by the system. It however works flawless in the brightness slider menu in the top right. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.157 Wed Oct 12 09:19:07 UTC 2022 GCC version: ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 30 03:38:51 2023 DistUpgraded: 2023-03-17 13:44:54,645 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] 3rd Gen Core processor Graphics Controller [1462:10d7] NVIDIA Corporation GK107M [GeForce GTX 660M] [10de:0fd4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK107M [GeForce GTX 660M] [1462:10d7] InstallationDate: Installed on 2023-02-24 (33 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Micro-Star International Co., Ltd. GE60 0NC\0ND ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=c297f9ee-3b13-4ae2-a84f-5197cc9c13d4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-03-17 (12 days ago) dmi.bios.date: 11/08/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16GAIMS.513 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16GA dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16GAIMS.513:bd11/08/2012:br4.6:svnMicro-StarInternationalCo.,Ltd.:pnGE600NC\0ND:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GA:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GE60 0NC\0ND dmi.product.sku: To be filled by O.E.M. dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 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.4-2ubuntu1.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic performance ubuntu -- changing screen brightness with keyboard hotkeys reacts very slow https://bugs.launchpad.net/bugs/2013255 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2013257] [NEW] two-finger-zoom not working on Elan touchpad
You have been subscribed to a public bug: On my Elan touchpad, using the two finger pinch zoom gesture does not work, neither in Firefox nor in LibreOffice. Other gestures like two- finger-scrolling work fine. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.157 Wed Oct 12 09:19:07 UTC 2022 GCC version: ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 30 04:09:14 2023 DistUpgraded: 2023-03-17 13:44:54,645 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] 3rd Gen Core processor Graphics Controller [1462:10d7] NVIDIA Corporation GK107M [GeForce GTX 660M] [10de:0fd4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK107M [GeForce GTX 660M] [1462:10d7] InstallationDate: Installed on 2023-02-24 (33 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Micro-Star International Co., Ltd. GE60 0NC\0ND ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=c297f9ee-3b13-4ae2-a84f-5197cc9c13d4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-03-17 (12 days ago) dmi.bios.date: 11/08/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16GAIMS.513 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16GA dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16GAIMS.513:bd11/08/2012:br4.6:svnMicro-StarInternationalCo.,Ltd.:pnGE600NC\0ND:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GA:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GE60 0NC\0ND dmi.product.sku: To be filled by O.E.M. dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 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.4-2ubuntu1.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic ubuntu -- two-finger-zoom not working on Elan touchpad https://bugs.launchpad.net/bugs/2013257 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2012599] Re: tzdata 2023a/2023b/2023c release - Egypt restoring DST
** Description changed: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a * python: test_2023c * python: test_systemv_timezones (for releases <= 20.04 LTS) * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. This is done by the test_systemv_timezones test case or can be checked manually with the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) [ Where problems could occur ] * Systems with incorrect timezone set (e.g. located outside of Egypt but still using Egyptian time) may observe unexpected time shift. [ Other Info ] The autopkgtest for chrony is flaky on jammy and kinetic (see bug #2002910). * More information with sources: https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023. The SRUs to the stable releases include the recent changes for generating the debconf template (switching from shell code to Python) and the timezone mappings in convert_timezone(). This is done to ease future tzdata updates since those parts of the packaging need to be updated when timezone are added, renamed, or removed. Having the same code in that part makes backporting the changes easier. I added a consistency check to generate_debconf_templates in 2023c-2 which I want to backport in a future SRU. Previous SRUs did sometimes forget to update convert_timezone or the exclusion list for the debconf template for the changes from upstream. All added tests (for testing the debconf template and convert_timezone) were also backported to catch missing those changes. The sorting change of the debconf template was included in the SRU to allow taking the debconf translations from later releases. + + debian/test_timezone_conversions finds following issues in the kinetic + packaging 2022g-0ubuntu0.22.10.1: + + ``` + ERROR: Following 14 timezones can be selected, but will be converted: + Asia/Rangoon + Europe/Uzhgorod + Europe/Zaporozhye + US/Alaska + US/Aleutian + US/Arizona + US/Central + US/Eastern + US/Hawaii + US/Indiana-Starke + US/Michigan + US/Mountain + US/Pacific + US/Samoa + ERROR: Following 5 timezones cannot be selected, but are not converted: + America/Fort_Wayne + America/Indianapolis + America/Knox_IN + America/Louisville + Pacific/Enderbury + ERROR: Following 3 timezones are conversion targets, but are not available: + Asia/Riyadh87 + Asia/Riyadh88 + Asia/Riyadh89 + ERROR: Following 4 timezones are conversion targets, but are not selectable: + America/Indianapolis + Asia/Riyadh87 + Asia/Riyadh88 + Asia/Riyadh89 + ``` -- 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/2012599 Title: tzdata 2023a/2023b/2023c release - Egypt restoring DST Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Kinetic: Fix Committed Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the
[Touch-packages] [Bug 2012599] Re: tzdata 2023a/2023b/2023c release - Egypt restoring DST
** Description changed: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a * python: test_2023c * python: test_systemv_timezones (for releases <= 20.04 LTS) * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. This is done by the test_systemv_timezones test case or can be checked manually with the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) [ Where problems could occur ] * Systems with incorrect timezone set (e.g. located outside of Egypt but still using Egyptian time) may observe unexpected time shift. [ Other Info ] The autopkgtest for chrony is flaky on jammy and kinetic (see bug #2002910). * More information with sources: https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023. The SRUs to the stable releases include the recent changes for generating the debconf template (switching from shell code to Python) and the timezone mappings in convert_timezone(). This is done to ease future tzdata updates since those parts of the packaging need to be updated when timezone are added, renamed, or removed. Having the same - code in that part makes backporting the changes easier. + code in that part makes backporting the changes easier. I added a + consistency check to generate_debconf_templates in 2023c-2 which I want + to backport in a future SRU. Previous SRUs did sometimes forget to update convert_timezone or the exclusion list for the debconf template for the changes from upstream. All added tests (for testing the debconf template and convert_timezone) were also backported to catch missing those changes. The sorting change of the debconf template was included in the SRU to allow taking the debconf translations from later releases. -- 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/2012599 Title: tzdata 2023a/2023b/2023c release - Egypt restoring DST Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Kinetic: Fix Committed Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a * python: test_2023c * python: test_systemv_timezones (for releases <= 20.04 LTS) * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. This is done by the test_systemv_timezones test case or can be checked manually with the following: diff <
[Touch-packages] [Bug 2012788] Re: Entering Unicode characters with code points broken
** Changed in: ibus Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2012788 Title: Entering Unicode characters with code points broken Status in ibus: Fix Released Status in ibus package in Ubuntu: In Progress Bug description: On an updated lunar, following this instruction: https://help.ubuntu.com/stable/ubuntu-help/tips- specialchars.html#ctrlshiftu no longer works. If I press for instance Ctrl+Shift+U followed by 2014 I see u2014 (underlined) on the screen. But it's not replaced with the expected character (in this case an Em Dash) when I confirm with Space or Enter — it just disappears. To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/2012788/+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 2012599] Re: tzdata 2023a/2023b/2023c release - Egypt restoring DST
** Description changed: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a * python: test_2023c * python: test_systemv_timezones (for releases <= 20.04 LTS) * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. This is done by the test_systemv_timezones test case or can be checked manually with the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) [ Where problems could occur ] * Systems with incorrect timezone set (e.g. located outside of Egypt but still using Egyptian time) may observe unexpected time shift. [ Other Info ] The autopkgtest for chrony is flaky on jammy and kinetic (see bug #2002910). * More information with sources: https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023. - The SRUs to the stable include the recent changes for generating the - debconf template (switching from shell code to Python) and the timezone - mappings in convert_timezone(). Previous SRUs did forget to update them - for the changes from upstream. All added tests (for testing the debconf - template and convert_timezone) were also backported. + The SRUs to the stable releases include the recent changes for + generating the debconf template (switching from shell code to Python) + and the timezone mappings in convert_timezone(). This is done to ease + future tzdata updates since those parts of the packaging need to be + updated when timezone are added, renamed, or removed. Having the same + code in that part makes backporting the changes easier. + + Previous SRUs did sometimes forget to update convert_timezone or the + exclusion list for the debconf template for the changes from upstream. + All added tests (for testing the debconf template and convert_timezone) + were also backported to catch missing those changes. ** Description changed: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a * python: test_2023c * python: test_systemv_timezones (for releases <= 20.04 LTS) * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. This is done by the test_systemv_timezones test case or can be checked manually with the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) [ Where problems could occur ] * Systems with incorrect timezone set (e.g. located outside of Egypt but still using Egyptian time) may observe unexpected time shift. [ Other Info ] The autopkgtest for chrony is flaky on jammy and kinetic (see bug #2002910). * More information with sources: https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,
[Touch-packages] [Bug 1856871] Re: i/o error if next unused loop device is queried
** Description changed: - This is reproducible in Bionic and late. - Here's an example running 'focal': + [Impact] - $ lsb_release -cs - focal + * There's an I/O error on fsync() in a detached loop device if it has + been previously attached. The issue is that write cache is enabled in + the attach path in loop_configure() but it isn't disabled in the detach + path; thus it remains enabled in the block device regardless of whether + it is attached or not. - $ uname -r - 5.3.0-24-generic + * fsync() on detached loop devices can be called by partition tools and + commands run by sosreport, so the unexpected kernel error message might + surprise users or even distract from the actual issue being + investigatedr. It might also trigger alerts in + logging/monitoring/alerting stacks - The error is: - blk_update_request: I/O error, dev loop2, sector 0 + [Fix] - and on more recent kernel: + * Disable write cache in the detach path - kernel: [18135.185709] blk_update_request: I/O error, dev loop18, sector - 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 + [Test Plan] + * Attach and detach an image to a loop device and test fsync return + value aterwards - How to trigger it: - $ sosreport -o block + # DEV=/dev/loop7 - or more precisely the cmd causing the situation inside the block plugin: - $ parted -s $(losetup -f) unit s print + # IMG=/tmp/image + # truncate --size 1M $IMG - https://github.com/sosreport/sos/blob/master/sos/plugins/block.py#L52 + # losetup $DEV $IMG + # losetup -d $DEV - but if I run it on the next next unused loop device, in this case - /dev/loop3 (which is also unused), no errors. + Before: + # strace -e fsync parted -s $DEV print 2>&1 | grep fsync + fsync(3)= -1 EIO (Input/output error) + Warning: Error fsyncing/closing /dev/loop7: Input/output error + [ 982.529929] blk_update_request: I/O error, dev loop7, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 - While I agree that sosreport shouldn't query unused loop devices, there - is definitely something going on with the next unused loop device. + After: + # strace -e fsync parted -s $DEV print 2>&1 | grep fsync + fsync(3)= 0 - What is differentiate loop2 and loop3 and any other unused ones ? + [Where problems could occur] - 3 things so far I have noticed: - * loop2 is the next unused loop device (losetup -f) - * A reboot is needed (if some loop modification (snap install, mount loop, ...) has been made at runtime - * I have also noticed that loop2 (or whatever the next unused one is) have some stat as oppose to other unused loop devices. The stat exist already right after the system boot for the next unused loop device. - - /sys/block/loop2/stat - :: - 2 0 10 0 1 0 0 0 0 0 0 - - 2 = number of read I/Os processed - 10 = number of sectors read - 1 = number of write I/Os processed - - Explanation of each column: - https://www.kernel.org/doc/html/latest/block/stat.html - - while /dev/loop3 doesn't - - /sys/block/loop3/stat - :: - 0 0 0 0 0 0 0 0 0 0 0 - - Which tells me that something during the boot process most likely - acquired (on purpose or not) the next unused loop and possibly didn't - released it well enough. - - If loop2 is generating errors, and I install a snap, the snap squashfs - will take loop2, making loop3 the next unused loop device. - - If I query loop3 with 'parted' right after, no errors. - - If I reboot, and query loop3 again, then no I'll have an error. - - To triggers the errors it need to be after a reboot and it only impact - the first unused loop device available (losetup -f). - - This was tested with focal/systemd whic his very close to latest - upstream code. - - This has been test with latest v5.5 mainline kernel as well. - - For now, I don't think it's a kernel problem, I'm more thinking of a - userspace misbehaviour dealing with loop device (or block device) at - boot. + * The detach path for block devices is modified. Worst case scenario + would be an error when detaching loop devices. ** Also affects: parted (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: udev (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: udev (Ubuntu Focal) ** No longer affects: systemd (Ubuntu Focal) ** No longer affects: snapd (Ubuntu Focal) ** No longer affects: parted (Ubuntu Focal) ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Jorge Merlino (jorge-merlino) -- You received this bug notification because you are a member of Ubuntu Touch seeded packag
[Touch-packages] [Bug 2012298] Re: PasswordAuthenticaion in sshd_config.d
I don't think it's a duplicate of 2002994. I tried moving the Include line in the main sshd_config to the end of the file and the behavior was unaffected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2012298 Title: PasswordAuthenticaion in sshd_config.d Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Focal: Confirmed Bug description: The stanza Match User PasswordAuthentication no in /etc/ssh/sshd_config works as expected. The same stanza in /etc/ssh/sshd_config.d/username.conf does not work. The Include in /etc/ssh/sshd_config is not commented out, and /usr/sbin/sshd -D -ddd shows the username.config file being parsed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4ubuntu0.5 ProcVersionSignature: Ubuntu 5.4.0-131.147-generic 5.4.210 Uname: Linux 5.4.0-131-generic x86_64 NonfreeKernelModules: falcon_lsm_serviceable falcon_nf_netcontain falcon_kal falcon_lsm_pinned_14713 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Mar 20 13:34:14 2023 InstallationDate: Installed on 2022-11-04 (136 days ago) InstallationMedia: SSHDConfig: Error: command ['pkexec', '/usr/sbin/sshd', '-T'] failed with exit code 127: pkexec must be setuid root SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2012298/+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 2004092] Re: casper fails to add any users because GID 999 is already taken
** Changed in: systemd (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2004092 Title: casper fails to add any users because GID 999 is already taken Status in casper package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Status in systemd package in Debian: New Bug description: This bug is due to the latest systemd upload in Ubuntu. systemd- journald now uses GID 999, when casper explicitly sets the live user to that UID and GID. Rather than going through the painstaking task of updating systemd to use a *different* user, let's just update casper to use 1000, which is the first dynamically-allocated user account per Debian Policy[1]. [1] https://www.debian.org/doc/debian-policy/ch-opersys.html#uid-and- gid-classes [ Original Report ] Normally, when one first boots a live ISO, a desktop automatically appears, asking users if they want to try or install Ubuntu (or, in the case of Lubuntu, they are simply dropped into a working desktop with an installation desktop icon available). As of the Lubuntu ISO on January 27, 2023, this has stopped occuring. Plymouth shows the initial boot animation, but the user is then dropped to a solid black screen. No user input is accepted. Attempting to switch to a TTY and sign in fails with the default "lubuntu" username and a blank password (the error "Login incorrect" is displayed). On Ubuntu Desktop, the behavior is even stranger. Rather than being shown a "Try or Install Ubuntu" screen, an initial system setup wizard appears that takes the user through the process of creating a user account. On a live ISO. Only after this wizard is finished does the "Try or Install Ubuntu" screen appear. Attempting to log into a TTY using the default "ubuntu" username and a blank password fails the same way as Lubuntu does, if done before the wizard is finished. However, one can log into a TTY if they finish the wizard and then attempt to log into the TTY using the credentials provided during user account setup. This issue affects at least the Lubuntu ISOs as of January 27, 2023, and the Ubuntu Desktop ISO at least as of January 28, 2023 (it is assumed that the 27th ISO for Ubuntu Desktop is also broken). The ISO from the 26th is most likely unaffected as there is successful testing information for Lubuntu on the 26th, so something likely happened between the 26th and the 27th to cause this breakage. Steps to reproduce: 1. Download the latest Lunar daily ISO of Ubuntu Desktop or Lubuntu. 2. Boot the ISO (hardware is irrelevant - this appears to occur on both physical and virtual hardware). For Lubuntu: 3. Wait until you are dropped to a black, blank screen. 4. Wait a while, then attempt to switch to a TTY and attempt to log in using "lubuntu" as the username and a blank password. The login attempt will be denied. For Ubuntu Desktop: 3. Wait until you are provided with an initial system setup wizard. 4. Switch to a TTY and attempt to log in using "ubuntu" as the username and a blank password. The login attempt will be denied. 5. Switch back to the system setup wizard, and complete it. 6. After completing the wizard, switch to a TTY again and attempt to log in using the credentials provided to the wizard. The login attempt will be successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/2004092/+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 1988270] Re: AppArmor fails to start with Yoga UCA libvirt profile on Focal
** Also affects: cloud-archive/xena Importance: Undecided Status: New ** Also affects: cloud-archive/antelope Importance: Undecided Assignee: Heather Lemon (hypothetical-lemon) Status: Confirmed ** No longer affects: cloud-archive/xena -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1988270 Title: AppArmor fails to start with Yoga UCA libvirt profile on Focal Status in Ubuntu Cloud Archive: Confirmed Status in Ubuntu Cloud Archive antelope series: Confirmed Status in Ubuntu Cloud Archive yoga series: Confirmed Status in Ubuntu Cloud Archive zed series: Confirmed Status in apparmor package in Ubuntu: Invalid Status in apparmor source package in Focal: Confirmed Status in apparmor source package in Jammy: Confirmed Bug description: [ Impact ] AppArmor fails to start with yoga-focal uca libvirt profile [ Test Plan ] generate yoga-focal openstack instance juju ssh nova-compute/0 sudo systemctl restart apparmor journalctl -xe # Error message ct 04 15:55:32 juju-6d4862-apparmorbug-9 apparmor.systemd[94081]: AppArmor parser error for /etc/apparmor.d/usr.sbin.libvirtd in /etc/apparmor.d/usr.sbin.li> Oct 04 15:55:32 juju-6d4862-apparmorbug-9 apparmor.systemd[94082]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Oct 04 15:55:32 juju-6d4862-apparmorbug-9 audit[94084]: AVC apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="u> Oct 04 15:55:32 juju-6d4862-apparmorbug-9 apparmor.systemd[94005]: Error: At least one profile failed to load [ Other Notes ] On a fully patched Ubuntu Focal with Yoga UCA enabled, after installation of libvirt-daemon-system, restarting apparmor would fail with error: Aug 31 07:40:52 ubuntu2004.localdomain apparmor.systemd[6335]: Restarting AppArmor Aug 31 07:40:52 ubuntu2004.localdomain apparmor.systemd[6335]: Reloading AppArmor profiles Aug 31 07:40:52 ubuntu2004.localdomain apparmor.systemd[6341]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Aug 31 07:40:52 ubuntu2004.localdomain apparmor.systemd[6348]: AppArmor parser error for /etc/apparmor.d in /etc/apparmor.d/usr.sbin.libvirtd at line 29: Invalid capability bpf. Aug 31 07:40:52 ubuntu2004.localdomain apparmor.systemd[6413]: AppArmor parser error for /etc/apparmor.d/usr.sbin.libvirtd in /etc/apparmor.d/usr.sbin.libvirtd at line 29: Invalid capability bpf. Aug 31 07:40:52 ubuntu2004.localdomain apparmor.systemd[6418]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Aug 31 07:40:52 ubuntu2004.localdomain apparmor.systemd[6335]: Error: At least one profile failed to load Aug 31 07:40:52 ubuntu2004.localdomain systemd[1]: apparmor.service: Main process exited, code=exited, status=1/FAILURE Aug 31 07:40:52 ubuntu2004.localdomain systemd[1]: apparmor.service: Failed with result 'exit-code'. Aug 31 07:40:52 ubuntu2004.localdomain systemd[1]: Failed to start Load AppArmor profiles. In addition to bpf, perfmon capability, which is also enabled in /etc/apparmor.d/usr.sbin.libvirtd profile, would lead to the same error. System information: root@ubuntu2004:~# uname -a Linux ubuntu2004.localdomain 5.4.0-125-generic #141-Ubuntu SMP Wed Aug 10 13:42:03 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu2004:~# dpkg -l libvirt\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--= ii libvirt-clients8.0.0-1ubuntu7.1~cloud0 amd64 Programs for the libvirt library ii libvirt-daemon 8.0.0-1ubuntu7.1~cloud0 amd64 Virtualization daemon ii libvirt-daemon-config-network 8.0.0-1ubuntu7.1~cloud0 all Libvirt daemon configuration files (default network) ii libvirt-daemon-config-nwfilter 8.0.0-1ubuntu7.1~cloud0 all Libvirt daemon configuration files (default network filters) un libvirt-daemon-driver-lxc (no description available) ii libvirt-daemon-driver-qemu 8.0.0-1ubuntu7.1~cloud0 amd64 Virtualization daemon QEMU connection driver un libvirt-daemon-driver-storage-gluster (no description available) un libvirt-daemon-driver-storage-iscsi-direct (no description available) un libvirt-daemon-driver-storage-rbd (no description available) u
[Touch-packages] [Bug 2013217] Re: package libpam0g:amd64 1.3.1-5ubuntu4.6 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken
"broken pipe" means the maintainer script died because the debconf frontend exited abnormally (this is the only pipe we wait for). This isn't a bug in pam, it can't proceed with configuration if it doesn't get sane answers for debconf. What was the context in which you were running the package upgrade? ** Changed in: pam (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2013217 Title: package libpam0g:amd64 1.3.1-5ubuntu4.6 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe) Status in pam package in Ubuntu: Incomplete Bug description: not sure why the problem ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam0g:amd64 1.3.1-5ubuntu4.6 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_tg ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Mar 25 07:27:49 2023 DpkgTerminalLog: Preparing to unpack .../libpam0g_1.3.1-5ubuntu4.6_amd64.deb ... Unpacking libpam0g:amd64 (1.3.1-5ubuntu4.6) over (1.3.1-5ubuntu4.3) ... Setting up libpam0g:amd64 (1.3.1-5ubuntu4.6) ... dpkg: error processing package libpam0g:amd64 (--configure): installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe) DuplicateSignature: package:libpam0g:amd64:1.3.1-5ubuntu4.6 Setting up libpam0g:amd64 (1.3.1-5ubuntu4.6) ... dpkg: error processing package libpam0g:amd64 (--configure): installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe) ErrorMessage: installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe) InstallationDate: Installed on 2020-08-07 (964 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: pam Title: package libpam0g:amd64 1.3.1-5ubuntu4.6 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2013217/+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 1960736] Re: Libnss3 doesn't log SEC_ERROR_UNKNOWN_PKCS11_ERROR properly ( NSS error code: -8018 )
Based on the latest upstream comment, I am marking this one as invalid as well. If you disagree with the assessment, please, set this back to new and state why you believe this is indeed a bug in the Ubuntu package. ** Changed in: nss (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1960736 Title: Libnss3 doesn't log SEC_ERROR_UNKNOWN_PKCS11_ERROR properly ( NSS error code: -8018 ) Status in NSS: Invalid Status in nss package in Ubuntu: Invalid Bug description: I've got the issue with Google Chrome not recognizing any of SSL/TSL certificates as trusted. When I look into certificate checksums it's renders all bytes of it as NULL bytes. I'm aware Google Chrome is proprietary but it depends on ubuntu provided libnss3-package. And libnss provides very nigmatic error code -8018: `/opt/google/chrome$ google-chrome [23391:23426:0213/133531.202486:ERROR:nss_util.cc(286)] After loading Root Certs, loaded==false: NSS error code: -8018 [23434:23434:0213/133531.266711:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process. [23391:23427:0213/133531.313065:ERROR:cert_verify_proc_builtin.cc(681)] CertVerifyProcBuiltin for accounts.google.com failed: - Certificate i=3 (CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE) - ERROR: No matching issuer found ' When trying to enter this particular error code into search engine nothing is found. So my suggestion with this bug is to make it more transparent by providing information to what happened - it seems other bug codes has better error messages. To get SEC_ERROR_UNKNOWN_PKCS11_ERROR string I was force to download source code and manually calculate offsets. Another issue is if failing to initialize PKCS11 token should make whole SSL/TLS crypto invalid ? I'm not sure if this is libnss or Google Chrome issue but it behaves differently in Chromium browser with same libnss so I assume either of two is doing better - it's worth to review this from security perspective. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libnss3 2:3.35-2ubuntu2.13 Uname: Linux 5.10.0-051000rc6-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 13 13:33:51 2022 Dependencies: gcc-8-base 8.4.0-1ubuntu1~18.04 libc6 2.27-3ubuntu1.5 [origin: LP-PPA-ubuntu-security-proposed] libgcc1 1:8.4.0-1ubuntu1~18.04 libnspr4 2:4.18-1ubuntu1 libsqlite3-0 3.22.0-1ubuntu0.4 InstallationDate: Installed on 2015-05-08 (2473 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: nss UpgradeStatus: Upgraded to bionic on 2018-08-26 (1266 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nss/+bug/1960736/+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 2012298] Re: PasswordAuthenticaion in sshd_config.d
FYI: might be related (or even dup) of bug 2002994 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2012298 Title: PasswordAuthenticaion in sshd_config.d Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Focal: Confirmed Bug description: The stanza Match User PasswordAuthentication no in /etc/ssh/sshd_config works as expected. The same stanza in /etc/ssh/sshd_config.d/username.conf does not work. The Include in /etc/ssh/sshd_config is not commented out, and /usr/sbin/sshd -D -ddd shows the username.config file being parsed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4ubuntu0.5 ProcVersionSignature: Ubuntu 5.4.0-131.147-generic 5.4.210 Uname: Linux 5.4.0-131-generic x86_64 NonfreeKernelModules: falcon_lsm_serviceable falcon_nf_netcontain falcon_kal falcon_lsm_pinned_14713 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Mar 20 13:34:14 2023 InstallationDate: Installed on 2022-11-04 (136 days ago) InstallationMedia: SSHDConfig: Error: command ['pkexec', '/usr/sbin/sshd', '-T'] failed with exit code 127: pkexec must be setuid root SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2012298/+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 2013217] Re: package libpam0g:amd64 1.3.1-5ubuntu4.6 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2013217 Title: package libpam0g:amd64 1.3.1-5ubuntu4.6 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe) Status in pam package in Ubuntu: New Bug description: not sure why the problem ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam0g:amd64 1.3.1-5ubuntu4.6 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_tg ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Mar 25 07:27:49 2023 DpkgTerminalLog: Preparing to unpack .../libpam0g_1.3.1-5ubuntu4.6_amd64.deb ... Unpacking libpam0g:amd64 (1.3.1-5ubuntu4.6) over (1.3.1-5ubuntu4.3) ... Setting up libpam0g:amd64 (1.3.1-5ubuntu4.6) ... dpkg: error processing package libpam0g:amd64 (--configure): installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe) DuplicateSignature: package:libpam0g:amd64:1.3.1-5ubuntu4.6 Setting up libpam0g:amd64 (1.3.1-5ubuntu4.6) ... dpkg: error processing package libpam0g:amd64 (--configure): installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe) ErrorMessage: installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe) InstallationDate: Installed on 2020-08-07 (964 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: pam Title: package libpam0g:amd64 1.3.1-5ubuntu4.6 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2013217/+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 2013217] [NEW] package libpam0g:amd64 1.3.1-5ubuntu4.6 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broke
Public bug reported: not sure why the problem ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam0g:amd64 1.3.1-5ubuntu4.6 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_tg ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Mar 25 07:27:49 2023 DpkgTerminalLog: Preparing to unpack .../libpam0g_1.3.1-5ubuntu4.6_amd64.deb ... Unpacking libpam0g:amd64 (1.3.1-5ubuntu4.6) over (1.3.1-5ubuntu4.3) ... Setting up libpam0g:amd64 (1.3.1-5ubuntu4.6) ... dpkg: error processing package libpam0g:amd64 (--configure): installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe) DuplicateSignature: package:libpam0g:amd64:1.3.1-5ubuntu4.6 Setting up libpam0g:amd64 (1.3.1-5ubuntu4.6) ... dpkg: error processing package libpam0g:amd64 (--configure): installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe) ErrorMessage: installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe) InstallationDate: Installed on 2020-08-07 (964 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: pam Title: package libpam0g:amd64 1.3.1-5ubuntu4.6 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe) UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pam (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2013217 Title: package libpam0g:amd64 1.3.1-5ubuntu4.6 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe) Status in pam package in Ubuntu: New Bug description: not sure why the problem ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam0g:amd64 1.3.1-5ubuntu4.6 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_tg ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Mar 25 07:27:49 2023 DpkgTerminalLog: Preparing to unpack .../libpam0g_1.3.1-5ubuntu4.6_amd64.deb ... Unpacking libpam0g:amd64 (1.3.1-5ubuntu4.6) over (1.3.1-5ubuntu4.3) ... Setting up libpam0g:amd64 (1.3.1-5ubuntu4.6) ... dpkg: error processing package libpam0g:amd64 (--configure): installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe) DuplicateSignature: package:libpam0g:amd64:1.3.1-5ubuntu4.6 Setting up libpam0g:amd64 (1.3.1-5ubuntu4.6) ... dpkg: error processing package libpam0g:amd64 (--configure): installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe) ErrorMessage: installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe) InstallationDate: Installed on 2020-08-07 (964 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: pam Title: package libpam0g:amd64 1.3.1-5ubuntu4.6 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2013217/+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 2000817] Re: Wrong SHA256-value computed on kinetic
I'm able to reproduce the exim4 dep8 error on kinetic ppc64el with the updated libldap packages, investigating... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/2000817 Title: Wrong SHA256-value computed on kinetic Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Jammy: In Progress Status in openldap source package in Kinetic: Fix Committed Status in openldap source package in Lunar: Fix Released Status in openldap package in Debian: Fix Released Bug description: [ Impact ] OpenLDAP deployments using the contrib pw-sha2 module are not able to authenticate their users because the SHA2 calculation is done incorrectly. Even though this is a contrib module, from an upstream PoV, it is shipped in the Ubuntu (and Debian) OpenLDAP packages, and available for use. Some fix possibilities were discussed in comment #5, and we selected the one with the least impact to OpenLDAP users at large, which is to recompile that module only without the strict-aliasing optimization. This update makes that change, and also includes a DEP8 change to verify it. We didn't use a patch for the pw-sha2 Makefile because d/rules overrides the OPT variable in the make command line (https://git.launchpad.net/~ahasenack/ubuntu/+source/openldap/tree/debian/rules?h=lunar- slapd-sha2-2000817#n44) [ Test Plan ] # Install slapd and openssl $ sudo apt install slapd openssl # Run the following script #!/bin/bash reference_hash="{SHA256}$(echo -n secret | openssl dgst -sha256 -binary | openssl enc -base64)" test_hash=$(slappasswd -s secret -h '{SHA256}' -o module-load=pw-sha2) echo "Reference hash of \"secret\" (openssl): ${reference_hash}" echo "slapd's pw-sha2 hash: ${test_hash}" if [ "${reference_hash}" != "${test_hash}" ]; then echo "ERROR: hashes differ" exit 1 else echo "PASS: hashes are identical" fi With the affected openldap package installed, the script should print an error. With the packages from proposed, the hashes should be identical. [ Where problems could occur ] The fix is a change of a compiler option strictly when building only the pw-sha2 module, so it's very localized. It could affect the performance of this module (for the worse), but it's already not working correctly. [ Other Info ] Not at this time. [Original Description] The OpenLDAP-contrib module sha2 (located in contrib/slapd- modules/passwd/sha2/) computes a wrong SHA256/SSHA256-hash on Ubuntu kinetic. This breaks our current password-authentication in ldap. The problematic computation: $ slappasswd -s secret -h '{SHA256}' -o module-load=pw-sha2 {SHA256}WIrrpN3OjEVOUf6yrH1j+o+ODuUuNBo979Od4UXnu54= The (correct) reference-value on the same system (or older ubuntu Versions): $ echo -n "secret" | openssl dgst -sha256 -binary | openssl enc -base64 K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols= We nailed the problem down to a bug in the gcc-optimizer for strict- aliasing. so most probably the gcc-version on kinetic (v12.2.0) is the reason. The workaround is to compile the sha2-Module with the flag "-fno-strict-aliasing". Then the correct value is computed. An example taken from a git-compiled version of OpenLDAP 2.5.13: $ ./servers/slapd/slappasswd -T passwd -s secret -h '{SHA256}' -o module-load=pw-sha2 -o module-path=contrib/slapd-modules/passwd/sha2/.libs {SHA256}K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols= Ubuntu: Description:Ubuntu 22.10 Release:22.10 OpenLDAP-Package: 2.5.13+dfsg-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2000817/+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 2012788] Re: Entering Unicode characters with code points broken
This is under control now. An upstream ibus commit fixes it (see discussion at upstream issue). Fix uploaded to Debian experimental. ** Changed in: ibus (Ubuntu) Status: Confirmed => In Progress ** Changed in: ibus (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) ** No longer affects: glib2.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2012788 Title: Entering Unicode characters with code points broken Status in ibus: New Status in ibus package in Ubuntu: In Progress Bug description: On an updated lunar, following this instruction: https://help.ubuntu.com/stable/ubuntu-help/tips- specialchars.html#ctrlshiftu no longer works. If I press for instance Ctrl+Shift+U followed by 2014 I see u2014 (underlined) on the screen. But it's not replaced with the expected character (in this case an Em Dash) when I confirm with Space or Enter — it just disappears. To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/2012788/+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 2012599] Re: tzdata 2023a/2023b/2023c release - Egypt restoring DST
** Description changed: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a * python: test_2023c * python: test_systemv_timezones (for releases <= 20.04 LTS) * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. This is done by the test_systemv_timezones test case or can be checked manually with the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) [ Where problems could occur ] * Systems with incorrect timezone set (e.g. located outside of Egypt but still using Egyptian time) may observe unexpected time shift. [ Other Info ] The autopkgtest for chrony is flaky on jammy and kinetic (see bug #2002910). * More information with sources: https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023. The SRUs to the stable include the recent changes for generating the - debconf template and the timezone mappings in convert_timezone(). - Previous SRUs did forget to update them for the changes from upstream. - All added tests were also backported. + debconf template (switching from shell code to Python) and the timezone + mappings in convert_timezone(). Previous SRUs did forget to update them + for the changes from upstream. All added tests (for testing the debconf + template and convert_timezone) were also backported. -- 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/2012599 Title: tzdata 2023a/2023b/2023c release - Egypt restoring DST Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Kinetic: Fix Committed Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a * python: test_2023c * python: test_systemv_timezones (for releases <= 20.04 LTS) * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. This is done by the test_systemv_timezones test case or can be checked manually with the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) [ Where problems could occur ] * Systems with incorrect timezone set (e.g. located outside of Egypt but still using Egyptian time) may observe unexpected time shift. [ Other Info ] The autopkgtest for chrony is flaky on jammy and kinetic (see bug #2002910). * More information with sources: https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:
[Touch-packages] [Bug 2013211] [NEW] Forward-port security fixes to Lunar
Public bug reported: There's been a bunch of security patches to the Kinetic version of vim, those need to be applied to Lunar as well: * CVE-2033-0433 * CVE-2023-1170 * CVE-2023-1175 * CVE-2023-1264 In addition, the following only affect the version in Lunar: * CVE-2023-0512 * CVE-2023-1127 ** Affects: vim (Ubuntu) Importance: Critical Status: In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/2013211 Title: Forward-port security fixes to Lunar Status in vim package in Ubuntu: In Progress Bug description: There's been a bunch of security patches to the Kinetic version of vim, those need to be applied to Lunar as well: * CVE-2033-0433 * CVE-2023-1170 * CVE-2023-1175 * CVE-2023-1264 In addition, the following only affect the version in Lunar: * CVE-2023-0512 * CVE-2023-1127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/2013211/+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 1991285] Re: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144
This autopkgtest run for systemd from 245.4-4ubuntu3.21 focal-proposed shows that armhf is passing again: https://autopkgtest.ubuntu.com/results/autopkgtest- focal/focal/armhf/s/systemd/20230327_104352_bc3ad@/log.gz. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1991285 Title: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144 Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Status in linux source package in Focal: New Status in systemd source package in Focal: Fix Committed Bug description: [Impact] The armhf autopkgtests currently fail in Focal due to this, and failures are not marked as regressions. This limits our ability to catch other regressions on armhf. [Test Plan] The boot-and-services autopkgtest should not fail on armhf. Specifically, the test_no_failed test should ignore systemd-remount-fs.service failures on armhf only. [Where problems could occur] The fix is limited to the boot-and-services autopkgtest, so there is limited risk. Any bugs would show up in that test. [Original Description] This is a scripted bug report about ADT failures while running systemd tests for linux/5.4.0-128.144 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991285/+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 2002445] Re: udev NIC renaming race with mlx5_core driver
I used the test script to verify that 245.4-4ubuntu3.21 from focal- proposed fixes the issue: - Test run complete: 29 attempted - Successes without rename race: 27 Successes with rename race and preserved altname: 2 Failures due to network delay: 0 Failures due to no altnames persisted: 0 === See attached log for full output. The customer tested systemd and udev from 245.4-4ubuntu3.21 in their own environment and confirmed the fix as well. ** Attachment added: "sru-systemd-focal.log" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2002445/+attachment/5658701/+files/sru-systemd-focal.log ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/2002445 Title: udev NIC renaming race with mlx5_core driver Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Jammy: Fix Committed Status in systemd source package in Kinetic: Fix Committed Status in systemd source package in Lunar: Fix Released Bug description: [Impact] On systems with mellanox NICs, udev's NIC renaming races with the mlx5_core driver's own configuration of subordinate interfaces. When the kernel wins this race, the device cannot be renamed as udev has attempted, and this causes systemd-network-online.target to timeout waiting for links to be configured. This ultimately results in boot being delayed by about 2 minutes. [Test Plan] Repeated launches of Standard_D8ds_v5 instance types will generally hit this race around 1 in 10 runs. Create a vm snapshot with updated systemd from ppa:enr0n/systemd-245. Launch 100 Standard_D8ds_v5 instances with updated systemd. Assert not failure in cloud-init status and no 2 minute delay in network-online.target. To check for failure symptom: - Assert that network-online.target isn't the longest pole from systemd-analyze blame. To assert success condition during net rename busy race: - assert when "eth1" is still the primary device name, that two altnames are listed (preserving the altname due to the primary NIC rename being hit). Sample script uses pycloudlib to create modified base image for test and launches 100 VMs of type Standard_D8ds_v5, counting both successes and any failures seen. #!/usr/bin/env python3 # This file is part of pycloudlib. See LICENSE file for license information. """Basic examples of various lifecycle with an Azure instance.""" import json import logging import os import sys from enum import Enum import pycloudlib LOG = logging.getLogger() base_cfg = """#cloud-config ssh-import-id: [chad.smith, enr0n, falcojr, holmanb, aciba] """ #source: "deb [allow-insecure=yes] https://ppa.launchpadcontent.net/enr0n/systemd-245/ubuntu focal main" # - apt install systemd udev -y --allow-unauthenticated apt_cfg = """ # Add developer PPA apt: sources: systemd-testing: source: {source} # upgrade systemd after cloud-init is nearly done runcmd: - apt install systemd udev -y --allow-unauthenticated """ debug_systemd_cfg = """ # Create systemd-udev debug override.conf in base image write_files: - path: /etc/systemd/system/systemd-networkd.service.d/override.conf owner: root:root defer: {defer} content: | [Service] Environment=SYSTEMD_LOG_LEVEL=debug - path: /etc/systemd/system/systemd-udevd.service.d/override.conf owner: root:root defer: {defer} content: | [Service] Environment=SYSTEMD_LOG_LEVEL=debug LogRateLimitIntervalSec=0 """ cloud_config = base_cfg + apt_cfg + debug_systemd_cfg cloud_config2 = base_cfg + debug_systemd_cfg class BootCondition(Enum): SUCCESS_WITHOUT_RENAME_RACE = "network bringup success without rename race" SUCCESS_WITH_RENAME_RACE = "network bringup success rename race condition" ERROR_NETWORK_TIMEOUT = "error: timeout on systemd-networkd-wait-online" def batch_launch_vm( client, instance_type, image_id, user_data, instance_count=5 ): instances = [] while len(instances) < instance_count: instances.append( client.launch( image_id=image_id, instance_type=instance_type, user_data=user_data, ) ) return instances def get_boot_condition(test_idx, instance): blame = instance.execute("systemd-analyze blame").splitlines() try: LOG.info( f"--- Attempt {test_idx} ssh ubuntu@{instance.ip} Blame: {blame[0]}" ) except IndexError: LOG.warning("--- Attempt {test_idx} Empty blame {b
[Touch-packages] [Bug 2012599] Re: tzdata 2023a/2023b/2023c release - Egypt restoring DST
Attached 2022c SRU for bionic and pushed the changes to https://code.launchpad.net/~ubuntu-core- dev/ubuntu/+source/tzdata/+git/tzdata/+ref/ubuntu/bionic ** Description changed: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a * python: test_2023c + * python: test_systemv_timezones (for releases <= 20.04 LTS) * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] - Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: + Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. This is done by the test_systemv_timezones test case or can be checked manually with the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) [ Where problems could occur ] * Systems with incorrect timezone set (e.g. located outside of Egypt but still using Egyptian time) may observe unexpected time shift. [ Other Info ] The autopkgtest for chrony is flaky on jammy and kinetic (see bug #2002910). * More information with sources: https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023. The SRUs to the stable include the recent changes for generating the debconf template and the timezone mappings in convert_timezone(). Previous SRUs did forget to update them for the changes from upstream. All added tests were also backported. ** Patch added: "tzdata_2023c-0ubuntu0.18.04.0.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+attachment/5658652/+files/tzdata_2023c-0ubuntu0.18.04.0.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2012599 Title: tzdata 2023a/2023b/2023c release - Egypt restoring DST Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Kinetic: Fix Committed Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a * python: test_2023c * python: test_systemv_timezones (for releases <= 20.04 LTS) * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. This is done by the test_systemv_timezones test case or can be checked manually with the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) [ Where problems could occur ] * Systems with incorrect timezone set (e.g. lo
[Touch-packages] [Bug 2012599] Re: tzdata 2023a/2023b/2023c release - Egypt restoring DST
Attached 2023c SRU for focal and pushed the changes to https://code.launchpad.net/~ubuntu-core- dev/ubuntu/+source/tzdata/+git/tzdata/+ref/ubuntu/focal ** Patch added: "tzdata_2023c-0ubuntu0.20.04.0.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+attachment/5658647/+files/tzdata_2023c-0ubuntu0.20.04.0.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2012599 Title: tzdata 2023a/2023b/2023c release - Egypt restoring DST Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Kinetic: Fix Committed Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a * python: test_2023c * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) [ Where problems could occur ] * Systems with incorrect timezone set (e.g. located outside of Egypt but still using Egyptian time) may observe unexpected time shift. [ Other Info ] The autopkgtest for chrony is flaky on jammy and kinetic (see bug #2002910). * More information with sources: https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023. The SRUs to the stable include the recent changes for generating the debconf template and the timezone mappings in convert_timezone(). Previous SRUs did forget to update them for the changes from upstream. All added tests were also backported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+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 2012599] Re: tzdata 2023a/2023b/2023c release - Egypt restoring DST
Attached 2023c SRU for jammy and pushed the changes to https://code.launchpad.net/~ubuntu-core- dev/ubuntu/+source/tzdata/+git/tzdata/+ref/ubuntu/jammy ** Patch added: "tzdata_2023c-0ubuntu0.22.04.0.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+attachment/5658646/+files/tzdata_2023c-0ubuntu0.22.04.0.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2012599 Title: tzdata 2023a/2023b/2023c release - Egypt restoring DST Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Kinetic: Fix Committed Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a * python: test_2023c * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) [ Where problems could occur ] * Systems with incorrect timezone set (e.g. located outside of Egypt but still using Egyptian time) may observe unexpected time shift. [ Other Info ] The autopkgtest for chrony is flaky on jammy and kinetic (see bug #2002910). * More information with sources: https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023. The SRUs to the stable include the recent changes for generating the debconf template and the timezone mappings in convert_timezone(). Previous SRUs did forget to update them for the changes from upstream. All added tests were also backported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+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 2012599] Re: tzdata 2023a/2023b/2023c release - Egypt restoring DST
Attached 2022c SRU for kinetic and pushed the changes to https://code.launchpad.net/~ubuntu-core- dev/ubuntu/+source/tzdata/+git/tzdata/+ref/ubuntu/kinetic ** Patch added: "tzdata_2023c-0ubuntu0.22.10.0.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+attachment/5658645/+files/tzdata_2023c-0ubuntu0.22.10.0.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2012599 Title: tzdata 2023a/2023b/2023c release - Egypt restoring DST Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Kinetic: Fix Committed Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a * python: test_2023c * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) [ Where problems could occur ] * Systems with incorrect timezone set (e.g. located outside of Egypt but still using Egyptian time) may observe unexpected time shift. [ Other Info ] The autopkgtest for chrony is flaky on jammy and kinetic (see bug #2002910). * More information with sources: https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023. The SRUs to the stable include the recent changes for generating the debconf template and the timezone mappings in convert_timezone(). Previous SRUs did forget to update them for the changes from upstream. All added tests were also backported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+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 1979610] Re: armhf: perl modules not rebuild? Loadable Library and Binary mismatch for pspp build.
** Changed in: pspp (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1979610 Title: armhf: perl modules not rebuild? Loadable Library and Binary mismatch for pspp build. Status in pspp: Unknown Status in perl package in Ubuntu: Fix Released Status in pspp package in Ubuntu: Fix Released Status in pspp package in Debian: Fix Released Bug description: During the build of the pspp 1.6.0-1 package for kinetic the regression fails for the armhf architecture in the perl module tests. The reported error is: +PSPP.c: loadable library and perl binaries are mismatched (got handshake key 0xa480080, needed 0xa380080) This happens only for the armhf architecture. The package build status of the pspp 1.6.0-1 package is here: https://launchpad.net/ubuntu/+source/pspp/1.6.0-1 You can also find the buildlogs for armhf and the architectures there. Is it possible that some perl modules have not been recompiled with the current perl version? Or is there any idea why this could fail only on armhf? Regards Friedrich To manage notifications about this bug go to: https://bugs.launchpad.net/pspp/+bug/1979610/+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 2012599] Re: tzdata 2023a/2023b/2023c release - Egypt restoring DST
** Summary changed: - tzdata 2023a/2023b release - Egypt restoring DST + tzdata 2023a/2023b/2023c release - Egypt restoring DST ** Description changed: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. + The 2023c release reverts the changes done in 2023b. + [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a - * python: test_2023b + * python: test_2023c * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) [ Where problems could occur ] * Systems with incorrect timezone set (e.g. located outside of Egypt but still using Egyptian time) may observe unexpected time shift. [ Other Info ] * More information with sources: https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023. The SRUs to the stable include the recent changes for generating the debconf template and the timezone mappings in convert_timezone(). Previous SRUs did forget to update them for the changes from upstream. All added tests were also backported. ** Description changed: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a * python: test_2023c * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) [ Where problems could occur ] * Systems with incorrect timezone set (e.g. located outside of Egypt but still using Egyptian time) may observe unexpected time shift. [ Other Info ] + The autopkgtest for chrony is flaky on jammy and kinetic (see bug + #2002910). + * More information with sources: https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023. The SRUs to the stable include the recent changes for generating the debconf template and the timezone mappings in convert_timezone(). Previous SRUs did forget to update them for the changes from upstream. All added tests were also backported. -- 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/2012599 Title: tzdata 2023a/2023b/2023c release - Egypt restoring DST Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Kinetic: Fix Committed Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recently th
[Touch-packages] [Bug 1994936] Re: initramfs need to mount efivarfs because kernel 6.0 deprecated 'efivars' sysfs interface
** Changed in: initramfs-tools (Debian) Status: New => Fix Released -- 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/1994936 Title: initramfs need to mount efivarfs because kernel 6.0 deprecated 'efivars' sysfs interface Status in OEM Priority Project: In Progress Status in initramfs-tools package in Ubuntu: New Status in initramfs-tools package in Debian: Fix Released Bug description: [ Impact ] kernel 6.0 deprecated efivars sysfs interface [1]. For Intel VROC RAID, mdadm needs initramfs to mount efivarfs instead. [1] The commit: commit 0f5b2c69a4cbe4166ca24b76d5ada98ed2867741 Author: Ard Biesheuvel Date: Mon Jun 20 13:34:03 2022 +0200 efi: vars: Remove deprecated 'efivars' sysfs interface [ Test Plan ] 1. Install initramfs-tools 2. update-initramfs -u 3. unmkinitramfs initrd.img-`uname -r` /tmp/extract-initramfs 4. Check if boot script 00_mount_efivarfs exists in directory /tmp/extract-initramfs/main/scripts/init-top/ 5. Check /tmp/extract-initramfs/main/scripts/init-top/ORDER if the boot script 00_mount_efivarfs will be execute before udev. [ Where problems could occur ] Not sure if there any other tools/utilities also need to mount efivarfs as early as mdadm but the probability of file conflict should be very low. Also, there are no impact mounting efivarfs multiple times. mount: /sys/firmware/efi/efivars: efivarfs already mounted on /sys/firmware/efi/efivars. [ Scope ] Jammy, Kinetic [ Other Info ] The private bug link https://bugs.launchpad.net/somerville/+bug/1990231 debian MR: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/66 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994936/+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 1599646] Re: E-mail report contains repeated "Reading database ... NN%" lines
** Changed in: apt (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1599646 Title: E-mail report contains repeated "Reading database ... NN%" lines Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Cosmic: Fix Released Status in apt package in Debian: Fix Released Bug description: [Impact] * Unattended-upgrades sends the following repeating dpkg progress lines with almost no informational value in the email report: ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 60486 files and directories currently installed.) ... * This makes the report email too verbose and makes harder to spot real problems. [Test Case] * Run package autopkgtest and observe no such lines in the echoed email in upgrade-all-security and upgrade-between-snapshots tests. [Regression Potential] * The fix filters dpkg's output only and in the worst case other lines could be missing or u-u could crash. Since the applied hard- coded regex pattern is fairly simple and we observed no crashes in the tests those regressions are unlikey to occur. [Originial Bug Text] This concerns unattended-upgrades 0.90 in Xenial. Here is an excerpt from an e-mail report sent out by u-u after the upgrade process is completed: Package installation log: Log started: 2016-07-06 17:24:21 Preconfiguring packages ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 314949 files and directories currently installed.) Preparing to unpack .../tzdata_2016f-0ubuntu0.16.04_all.deb ... Unpacking tzdata (2016f-0ubuntu0.16.04) over (2016d-0ubuntu0.16.04) ... Preparing to unpack .../libgimp2.0_2.8.16-1ubuntu1.1_i386.deb ... All but the last "Reading database ..." line should be elided from the message. As a matter of fact, those lines do not appear in messages mailed out from current Trusty systems (u-u version 0.82.1ubuntu2.4), so this appears to be a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1599646/+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 1807440] Re: sensible-browser cannot process $BROWSER variable when it contains a whitespace character
** Changed in: sensible-utils (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sensible-utils in Ubuntu. https://bugs.launchpad.net/bugs/1807440 Title: sensible-browser cannot process $BROWSER variable when it contains a whitespace character Status in sensible-utils package in Ubuntu: Triaged Status in sensible-utils package in Debian: Fix Released Bug description: If path to a browser defined via the $BROWSER environment variable contains a whitespace character, running sensible-browser should launch browser defined by $BROWSER. If path to a browser defined via the $BROWSER environment variable contains a whitespace character, running sensible-browser will not parse the whitespace characters and therefore not load the browser defined by $BROWSER. Bug can be fixed by updating line 8 in /usr/bin/sensible-browser: ${BROWSER} "$@" > "${BROWSER}" "$@" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: sensible-utils 0.0.12 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 7 11:05:17 2018 Dependencies: InstallationDate: Installed on 2018-12-06 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: sensible-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sensible-utils/+bug/1807440/+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 2009543] Re: network-manager nm.py autopkgtest needs to be updated for 1.42
This bug was fixed in the package network-manager - 1.42.4-1ubuntu2 --- network-manager (1.42.4-1ubuntu2) lunar; urgency=medium * d/t/nm.py: Fix autopkgtests with NM-1.42's 'lo' connection (LP: #2009543) -- Lukas Märdian Tue, 28 Mar 2023 15:13:56 +0200 ** Changed in: network-manager (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2009543 Title: network-manager nm.py autopkgtest needs to be updated for 1.42 Status in network-manager package in Ubuntu: Fix Released Bug description: Ubuntu's network-manager package includes several autopkgtest. (Debian's network-manager package does not have any autopkgtests.) One of those, nm.py needs to be updated for changes in the new network-manager 1.42 series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2009543/+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