[Touch-packages] [Bug 2060206] [NEW] No Sound on my Samsung NP950QED Laptop Speakers
Public bug reported: Hello, Yesterday I have installed Ubuntu 23.10 on my laptop Samsung Galaxy Book2 Pro NP950QED for the first time. I never heard any sound from my laptop since the installation of Ubuntu. It worked with Microsoft Windows. I spent the whole day on many forums, alsa-project.org... Nothing worked yet. Every time I try a new configuration, I test both left and right speakers in the Settings application. You can find my Ubuntu Alsa configuration in the file attached generared by alsa-info.sh Thank you for your help ! ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thierry2651 F pipewire thierry2657 F wireplumber /dev/snd/seq:thierry2651 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 4 16:24:59 2024 InstallationDate: Installed on 2024-04-03 (1 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) PackageArchitecture: all ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/03/2023 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P10AKK.730.230203.SH dmi.board.asset.tag: No Asset Tag dmi.board.name: NP950QED-KA1FR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLB182A1Z-C01-G002-S0002+10.0.22000 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP10AKK.730.230203.SH:bd02/03/2023:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950QED:pvrP10AKK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP950QED-KA1FR:rvrSGLB182A1Z-C01-G002-S0002+10.0.22000:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PAKK: dmi.product.family: Galaxy Book2 Pro 360 dmi.product.name: 950QED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PAKK dmi.product.version: P10AKK dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session ** Attachment added: "alsa-info.sh Generated File" https://bugs.launchpad.net/bugs/2060206/+attachment/5761575/+files/alsa-info.txt.blWk58tjXY -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2060206 Title: No Sound on my Samsung NP950QED Laptop Speakers Status in alsa-driver package in Ubuntu: New Bug description: Hello, Yesterday I have installed Ubuntu 23.10 on my laptop Samsung Galaxy Book2 Pro NP950QED for the first time. I never heard any sound from my laptop since the installation of Ubuntu. It worked with Microsoft Windows. I spent the whole day on many forums, alsa-project.org... Nothing worked yet. Every time I try a new configuration, I test both left and right speakers in the Settings application. You can find my Ubuntu Alsa configuration in the file attached generared by alsa-info.sh Thank you for your help ! ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thierry2651 F pipewire thierry2657 F wireplumber /dev/snd/seq:thierry2651 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 4 16:24:59 2024 InstallationDate: Installed on 2024-04-03 (1 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) PackageArchitecture: all ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/03/2023 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P10AKK.730.230203.SH dmi.board.asset.tag: No Asset Tag dmi.board.name: NP950QED-KA1FR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
[Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
Thanks for the bug report, unfortunately this has become quite convoluted and I've identified at least 3 different strands of discussion in here that are not related. Some stuff, like "runuser" in a cron job is clearly never going to work, but I don't know how the other two instances - sessions without session busses and issues with VNC connections are affected. I'd advise filing clear succinct reproducible issues for those cases, but I don't think there's much that can be done with this bug anymore. ** Changed in: x2goserver (Ubuntu) Status: Confirmed => Incomplete ** Changed in: snapd (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1951491 Title: Can't run snaps: .slice/session-1.scope is not a snap cgroup Status in X2Go: New Status in Xpra Terminal Server: New Status in snapd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Status in x2goserver package in Ubuntu: Incomplete Status in snapd package in Debian: New Status in snapd package in Fedora: New Bug description: I just upgraded from hirsute to impish using do-release-upgrade. On the upgraded system, I can't run either firefox or chromium (both of which worked fine under hirsute). Both fail with: /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where NNN is my uid With firefox, I was able to fix the problem with: snap remove --purge firefox apt purge firefox apt install firefox Now firefox works. But I tried the same thing substituting chromium- browser for firefox, and it didn't help: chromium fails with the same error message. I guess there must be something left over from the hirsute version of snapd that isn't getting noticed or cleared by the impish version? Someone suggested this might be related to bug 1850667, but that bug is marked fixed as of a couple months ago, and I just did this upgrade today. Also, it doesn't mention the error message I'm seeing. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: snapd 2.53+21.10ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Nov 18 18:12:45 2021 InstallationDate: Installed on 2020-04-29 (568 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snapd UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/x2go/+bug/1951491/+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 2060204] Re: Resolution drop on third monitor on USB C
** 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/2060204 Title: Resolution drop on third monitor on USB C Status in xorg package in Ubuntu: New Bug description: I have a laptop with an integrated intel intel gpu, 2/3 days ago it was working fine; I have 1 monitor plugged with hdmi and the other one with USB-c Now, the one plugged with USB-C get a lower resolution 1024*768 (not changeable) if the HDMI is plugged at the same time (it works well if I only have the USB c plugged) Feel free to ask if you need information cat /var/log/apt/history.log (relevant lines) Start-Date: 2024-03-29 14:21:01 Commandline: apt upgrade -y Requested-By: roudonro (1000) Upgrade: snapd:amd64 (2.58+22.04.1, 2.61.3+22.04) End-Date: 2024-03-29 14:21:15 Start-Date: 2024-04-02 16:06:48 Commandline: apt upgrade gnome-calendar Requested-By: roudonro (1000) Upgrade: coreutils:amd64 (8.32-4.1ubuntu1.1, 8.32-4.1ubuntu1.2), apt:amd64 (2.4.11, 2.4.12), libapt-pkg6.0:amd64 (2.4.11, 2.4.12), libmutter-10-0:amd64 (42.9-0ubuntu5, 42.9-0ubuntu7), libwbclient0:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 2:4.15.13+dfsg-0ubuntu1.6), libsmbclient:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 2:4.15.13+dfsg-0ubuntu1.6), mutter-common:amd64 (42.9-0ubuntu5, 42.9-0ubuntu7), update-notifier:amd64 (3.192.54.6, 3.192.54.8), gir1.2-mutter-10:amd64 (42.9-0ubuntu5, 42.9-0ubuntu7), samba-libs:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 2:4.15.13+dfsg-0ubuntu1.6), apt-utils:amd64 (2.4.11, 2.4.12), update-notifier-common:amd64 (3.192.54.6, 3.192.54.8) End-Date: 2024-04-02 16:06:51 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 4 09:15:15 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell TigerLake-LP GT2 [Iris Xe Graphics] [1028:0a21] InstallationDate: Installed on 2024-03-27 (7 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) MachineType: Dell Inc. Latitude 5520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic root=UUID=d63caf0d-f785-49dd-94e1-518dc8a874be ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2023 dmi.bios.release: 1.31 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.31.0 dmi.board.name: 0DPC2R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.31.0:bd08/08/2023:br1.31:svnDellInc.:pnLatitude5520:pvr:rvnDellInc.:rn0DPC2R:rvrA00:cvnDellInc.:ct10:cvr:sku0A21: dmi.product.family: Latitude dmi.product.name: Latitude 5520 dmi.product.sku: 0A21 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2060204/+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 2060358] [NEW] Please add German (Noted) layout
Public bug reported: Please add the newest layout of the German Neo keyboard layout family. Noted is a layout designed to make typing as comfortable and efficient as possible in both German and English. It was developed with the help of a layout optimizer, which is based on the metrics and concepts of ArneBab's optimizer and adapts and extends them. I switched from Neo 2 via Mine to Noted and I like to see this variant to be available out of the box in Ubuntu. Sources: * https://neo-layout.org/Layouts/noted/ * https://dariogoetz.github.io/noted-layout/ Forwarded upstream: https://gitlab.freedesktop.org/xkeyboard- config/xkeyboard-config/-/merge_requests/681 ** Affects: xkeyboard-config (Ubuntu) Importance: Undecided Status: New ** Description changed: Please add the newest layout of the German Neo keyboard layout family. Noted is a layout designed to make typing as comfortable and efficient as possible in both German and English. It was developed with the help of a layout optimizer, which is based on the metrics and concepts of ArneBab's optimizer and adapts and extends them. I switched from Neo 2 via Mine to Noted and I like to see this variant to be available out of the box in Ubuntu. + + Sources: + + * https://neo-layout.org/Layouts/noted/ + * https://dariogoetz.github.io/noted-layout/ + + Forwarded upstream: https://gitlab.freedesktop.org/xkeyboard- + config/xkeyboard-config/-/merge_requests/681 -- 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/2060358 Title: Please add German (Noted) layout Status in xkeyboard-config package in Ubuntu: New Bug description: Please add the newest layout of the German Neo keyboard layout family. Noted is a layout designed to make typing as comfortable and efficient as possible in both German and English. It was developed with the help of a layout optimizer, which is based on the metrics and concepts of ArneBab's optimizer and adapts and extends them. I switched from Neo 2 via Mine to Noted and I like to see this variant to be available out of the box in Ubuntu. Sources: * https://neo-layout.org/Layouts/noted/ * https://dariogoetz.github.io/noted-layout/ Forwarded upstream: https://gitlab.freedesktop.org/xkeyboard- config/xkeyboard-config/-/merge_requests/681 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/2060358/+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 2060221] Re: nm_netplan.py autopkgtest fails with ModuleNotFoundError: No module named 'gi'
This bug was fixed in the package network-manager - 1.46.0-1ubuntu2 --- network-manager (1.46.0-1ubuntu2) noble; urgency=medium * debian/tests/control: add Depends: python3-gi for nm_netplan.py (LP: #2060221) -- Nick Rosbrook Thu, 04 Apr 2024 15:11:48 -0400 ** Changed in: network-manager (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2060221 Title: nm_netplan.py autopkgtest fails with ModuleNotFoundError: No module named 'gi' Status in network-manager package in Ubuntu: Fix Released Bug description: Example log: https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/amd64/n/network-manager/20240404_183130_7a1cc@/log.gz The relevant part is: 3988s autopkgtest [18:31:02]: test nm_netplan.py: [--- 3988s Traceback (most recent call last): 3988s File "/tmp/autopkgtest.Q1jKoU/build.9D4/src/debian/tests/nm_netplan.py", line 18, in 3988s import gi 3988s ModuleNotFoundError: No module named 'gi' 3988s autopkgtest [18:31:02]: test nm_netplan.py: ---] 3989s autopkgtest [18:31:03]: test nm_netplan.py: - - - - - - - - - - results - - - - - - - - - - 3989s nm_netplan.pyFAIL non-zero exit status 1 It seems that nm_netplan.py needs to depend on python3-gi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2060221/+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 2060010] Re: apport-bug fails for libglapi-mesa (= 24.0.3-1ubuntu3)
This could be a fallout of the xz rebuild. Do you have packages on your system that cannot be found in any repository any more? What does `apt policy libglapi-mesa` say? ** Changed in: apport (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2060010 Title: apport-bug fails for libglapi-mesa (= 24.0.3-1ubuntu3) Status in apport package in Ubuntu: Incomplete Bug description: Running apport-bug for libglapi-mesa (= 24.0.3-1ubuntu3) results in a message: The problem cannot be reported: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. apt-get update && apt-get dist-upgrade does not resolve the problem. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: apport 2.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-20.20-generic 6.8.1 Uname: Linux 6.8.0-20-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Apr 2 09:35:33 2024 InstallationDate: Installed on 2021-07-01 (1006 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2060010/+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 2051672] Re: Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)
** Changed in: iproute2 (Ubuntu) Milestone: ubuntu-24.04-feature-freeze => ubuntu-24.04-beta -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) Status in iproute2 package in Ubuntu: Confirmed Bug description: A few versions have been released and Ubuntu Noble still has the 6.1 version (6.1.0-1ubuntu2) from one year ago. Could it be possible to import the latest version from Debian unstable fixing a bunch of issues and supporting features from more recent kernels? Please note that Ubuntu Noble 24.04 will probably be shipped with the v6.8 kernel [1]. IPRoute v6.1 supports features added up to the v6.1 kernel, so missing the ones added to earlier versions. Switching to the v6.7 now should ease the upgrade to the v6.8 later. [1] https://discourse.ubuntu.com/t/introducing-kernel-6-8-for- the-24-04-noble-numbat-release/41958 Upstream ChangeLog: - 6.2: https://lore.kernel.org/netdev/20230220105811.674bd304@hermes.local/ - 6.3: https://lore.kernel.org/netdev/20230427090253.7a92616b@hermes.local/ - 6.4: https://lore.kernel.org/netdev/20230626093137.2f302acc@hermes.local/ - 6.5: https://lore.kernel.org/netdev/20230906093918.394a1b1d@hermes.local/ - 6.6: https://lore.kernel.org/netdev/20231106090325.07092c87@hermes.local/ - 6.7: https://lore.kernel.org/netdev/20240108094709.050e22bc@hermes.local/ - 6.8: https://lore.kernel.org/netdev/20240311094432.16bf9516@hermes.local/ (Previous changelog: https://lore.kernel.org/netdev/?q=s%3A%22%5BANNOUNCE%5D+iproute2%22+AND+NOT+s%3A%22Re%3A%22 ) ChangeLog from Debian: iproute2 (6.8.0-1) unstable; urgency=medium [ Ceppo ] * Update Italian po-debconf translation (Closes: #1063002) [ Luca Boccassi ] * Add build dependency on libnsl-dev (Closes: #1065214) * Switch to pkgconf * Update upstream source from tag 'upstream/6.8.0' * Drop 0002-ss-show-extra-info-when-processes-is-not-used.patch, merged upstream * Drop iproute2-doc package * Drop tc/m_xt.so and tc/m_ipt.so, removed upstream -- Luca Boccassi <> Tue, 12 Mar 2024 14:02:38 + iproute2 (6.7.0-2) unstable; urgency=medium * Backport fix for 'ss' output -- Luca Boccassi <> Mon, 22 Jan 2024 12:24:29 + iproute2 (6.7.0-1) unstable; urgency=medium * Add Italian debconf translation (Closes: #1056582) * Update upstream source from tag 'upstream/6.7.0' * Bump copyright year ranges in d/copyright * Drop 0002-Revert-Makefile-ensure-CONF_USR_DIR-honours-the-libd.patch, merged upstream * Default config files moved from /usr/lib to /usr/share -- Luca Boccassi <> Fri, 12 Jan 2024 21:47:59 + iproute2 (6.6.0-1) unstable; urgency=medium * Update upstream source from tag 'upstream/6.6.0' * Backport patch to fix configuration installation * Remove handling of qt_atm.so, dropped upstream -- Luca Boccassi <> Sun, 05 Nov 2023 22:46:20 + iproute2 (6.5.0-5) unstable; urgency=medium * Use dh-sequence-movetousr -- Luca Boccassi <> Tue, 24 Oct 2023 15:24:01 +0100 iproute2 (6.5.0-4) unstable; urgency=medium * postinst: handle legacy config files only when upgrading from previous versions that shipped them * postinst: ensure that locally modified legacy config files are preserved as overrides on upgrade (Closes: #1051577) * Note configuration files location changes in NEWS -- Luca Boccassi <> Sat, 16 Sep 2023 18:58:51 +0100 iproute2 (6.5.0-3) unstable; urgency=medium * Remove further leftovers as part of upstream's move of config to /usr (Closes: #1051577) -- Luca Boccassi <> Mon, 11 Sep 2023 09:42:12 +0100 iproute2 (6.5.0-2) unstable; urgency=medium * Add maintscript to remove conffiles that upstream has moved to /usr (Closes: #1051577) -- Luca Boccassi <> Sun, 10 Sep 2023 21:28:28 +0100 iproute2 (6.5.0-1) unstable; urgency=medium [ Luca Boccassi ] * Use wildcard for Lintian overrides [ Peter Kvillegård ] * Add Swedish translation of debconf messages (Closes: #1050442) [ Luca Boccassi ] * Update upstream source from tag 'upstream/6.5.0' * Use cap_bpf instead of cap_sys_admin for ip vrf-exec * Package-provided config files are now shipped in /usr/iproute2 instead of /etc/iproute2 -- Luca Boccassi <> Sat, 09 Sep 2023 16:32:54 +0100 iproute2 (6.4.0-1) unstable; urgency=medium * Fix patch header Forwarded field * Enable ELF metadata stamping * Update upstream source from tag 'upstream/6.4.0' * Update Lintian overrides -- Luca Boccassi <> Fri, 30 Jun 2023 12:16:40 +0100 iproute2 (6.3.0-1) unstable; urgency=medium * Drop obsolete conflicts/replaces * Update upstream source from tag
[Touch-packages] [Bug 2060319] Re: tracker failing autopkgtest on noble
** Bug watch added: Debian Bug tracker #1068468 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068468 ** Also affects: tracker (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068468 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/2060319 Title: tracker failing autopkgtest on noble Status in Tracker: New Status in tracker package in Ubuntu: Triaged Status in tracker package in Debian: Unknown Bug description: tracker's autopkgtest is failing. I have reported this issue upstream. Our autopkgtest configuration is similar but not identical to our build test configuration which does pass. To manage notifications about this bug go to: https://bugs.launchpad.net/tracker/+bug/2060319/+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 2060335] Re: upower/1.90.2-8build3 autopkgtest failure on arm64
I estimate another ncr could fix the issue. Building and testing in a ppa. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/2060335 Title: upower/1.90.2-8build3 autopkgtest failure on arm64 Status in upower package in Ubuntu: In Progress Bug description: autopkgtests fail, only on arm64, after a no-change-rebuild, with the following output: 689s [32mTI:22:39:23 [34mHandling SIGTERM 689s [0m. 689s == 689s ERROR: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/lib/python3.12/shutil.py", line 785, in rmtree 689s _rmtree_safe_fd(fd, path, onexc) 689s File "/usr/lib/python3.12/shutil.py", line 717, in _rmtree_safe_fd 689s onexc(os.unlink, fullname, err) 689s File "/usr/lib/python3.12/shutil.py", line 715, in _rmtree_safe_fd 689s os.unlink(entry.name, dir_fd=topfd) 689s FileNotFoundError: [Errno 2] No such file or directory: 'history-time-full-G935_Gaming_Headset.dat.KL0SL2' 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 2558, in test_daemon_restart 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 173, in tearDown 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 689s 689s -- 689s Ran 66 tests in 194.378s 689s 689s FAILED (failures=2, errors=1) full log: https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/arm64/u/upower/20240405_224518_5cff1@/log.gz These test passed in the previous version: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/arm64/u/upower/20240405_224754_d187c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/2060335/+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 2060358] Re: [FFe] Please add German (Noted) layout
Here is the debdiff. I tested this change and the layout on noble (via https://launchpad.net/~bdrung/+archive/ubuntu/staging). This feature should have a low regression risk since it just add a new keyboard layout. This layout is added to the "exotic" list. ** Summary changed: - Please add German (Noted) layout + [FFe] Please add German (Noted) layout ** Patch added: "xkeyboard-config_2.41-2ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/2060358/+attachment/5761852/+files/xkeyboard-config_2.41-2ubuntu1.debdiff -- 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/2060358 Title: [FFe] Please add German (Noted) layout Status in xkeyboard-config package in Ubuntu: New Bug description: Please add the newest layout of the German Neo keyboard layout family. Noted is a layout designed to make typing as comfortable and efficient as possible in both German and English. It was developed with the help of a layout optimizer, which is based on the metrics and concepts of ArneBab's optimizer and adapts and extends them. I switched from Neo 2 via Mine to Noted and I like to see this variant to be available out of the box in Ubuntu. Sources: * https://neo-layout.org/Layouts/noted/ * https://dariogoetz.github.io/noted-layout/ Forwarded upstream: https://gitlab.freedesktop.org/xkeyboard- config/xkeyboard-config/-/merge_requests/681 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/2060358/+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 2056556] Re: apt-add-repository incorrectly forces lowercase
Could you use a lower case suite in your local apt repository as a workaround for this issue? I feel like it's a bit of a standard to have lowercase: jammy, bookworm, virginia etc. ** Changed in: software-properties (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2056556 Title: apt-add-repository incorrectly forces lowercase Status in software-properties package in Ubuntu: New Bug description: I have a local APT repository with a non-lowercase suite identifier. apt-add-repository always forces it into lowercase, which causes apt to emit warnings when it notices the mismatch: $ sudo apt-add-repository "deb http://example.com/deb FooBar Baz" Repository: 'deb http://example.com/ foobar Baz' Description: Archive for codename: foobar components: Baz More info: http://example.com/ Adding repository. Press [ENTER] to continue or Ctrl-c to cancel. (...) $ sudo apt update (...) W: Conflicting distribution: http://example.com/deb foobar InRelease (expected foobar but got FooBar) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2056556/+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 2059258] Re: conntrack-tools: FTBFS: configure: error: Package requirements (libtirpc) were not met
This bug was fixed in the package conntrack-tools - 1:1.4.8-1ubuntu1 --- conntrack-tools (1:1.4.8-1ubuntu1) noble; urgency=medium * debian/control: add Build-Depends: libtirpc-dev (LP: #2059258) -- Nick Rosbrook Thu, 04 Apr 2024 14:28:25 -0400 ** Changed in: conntrack-tools (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/2059258 Title: conntrack-tools: FTBFS: configure: error: Package requirements (libtirpc) were not met Status in conntrack-tools package in Ubuntu: Fix Released Status in kmod package in Ubuntu: New Status in conntrack-tools package in Debian: Fix Released Bug description: Imported from Debian bug http://bugs.debian.org/1066476: Source: conntrack-tools Version: 1:1.4.8-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for byacc... no > checking for pkg-config... /usr/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking for rpc/rpc_msg.h... no > checking for libtirpc... no > configure: error: Package requirements (libtirpc) were not met > > Package 'libtirpc', required by 'virtual:world', not found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables LIBTIRPC_CFLAGS > and LIBTIRPC_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2024/03/13/conntrack-tools_1.4.8-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/conntrack-tools/+bug/2059258/+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 2055718] Re: timezone changed unexpectedly from EST to America/Adak or America/Indiana/Indianapolis
** Tags added: patch -- 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/2055718 Title: timezone changed unexpectedly from EST to America/Adak or America/Indiana/Indianapolis Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Mantic: New Bug description: [ Impact ] On every tzdata package upgrade the configured timezone might be updated to an incorrect one. I enhanced debian/test_timezone_conversions to detect those inconsistencies and fixed everything that was found by this check. The SRUs contain a backport of the script from noble. [ Test Plan ] debian/test_timezone_conversions is enhanced to check the timezone conversions for consistency to prevent such kind of issues in the future. debian/test_timezone_conversions is run during built and as autopkgtest. In addition, manual check can be done. The following test should stay at `EST` (and not update to `America/Adak`): ``` ln -sf /usr/share/zoneinfo/EST /etc/localtime dpkg-reconfigure --frontend noninteractive tzdata ls -alh /etc/localtime ``` `US/East-Indiana` should be updated to `America/Indiana/Indianapolis` and not to `America/Adak`: ``` ln -sf /usr/share/zoneinfo/US/East-Indiana /etc/localtime dpkg-reconfigure --frontend noninteractive tzdata ``` `America/Louisville` should be updated to `America/Kentucky/Louisville` and not to `America/Adak`: ``` ln -sf /usr/share/zoneinfo/America/Louisville /etc/localtime dpkg-reconfigure --frontend noninteractive tzdata ``` [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). [ Regression potential ] The patch ziguard.awk-Move-link-to-link-feature-from-vanguard-to- ma.patch moves the link to link feature from vanguard to main dataform to produce correct symlinks. This results in symlinks that can point to symlinks. The zic from glibc that we use can handle that, but there might be other parsers that read /usr/share/zoneinfo/tzdata.zi directly and could fail to handle symlinks to symlinks. [ Original report ] A user reported this regression on https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739: UPDATE: I don't think it's a regression anymore, see comment #5 """ Hello. After automatic upgrade of tzdata from 2023c-0ubuntu0.22.04.2 to 2024a-0ubuntu0.22.04 the previously set EST time zone was automatically changed to "America/Adak" or "America/Indiana/Indianapolis" on all our servers (50+). Look like a bug in tzdata configure script. """ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2055718/+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 2060150] Re: openssh sets PAM_RHOST to UNKNOWN causing slow logins
I was preparing a bug fix upload, so I have picked this up as well. ** Changed in: openssh (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) ** Changed in: openssh (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2060150 Title: openssh sets PAM_RHOST to UNKNOWN causing slow logins Status in openssh package in Ubuntu: In Progress Bug description: When using sshd's -i option with stdio that is not a AF_INET/AF_INET6 socket, auth_get_canonical_hostname() returns "UNKNOWN" which is then set as the value of PAM_RHOST, causing pam to try to do a reverse DNS query of "UNKNOWN", which times out multiple times, causing a substantial slowdown when logging in. upstream PR: https://github.com/openssh/openssh-portable/pull/388 upstream email: https://lists.mindrot.org/pipermail/openssh-unix-dev/2024-April/041289.html Fedora backport: https://src.fedoraproject.org/rpms/openssh/pull-request/71 Debian backport: https://salsa.debian.org/ssh-team/openssh/-/merge_requests/25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2060150/+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 2053146] Please test proposed package
Hello ake, or anyone else affected,
Accepted openssh into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:8.9p1-3ubuntu0.7 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2053146
Title:
openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is
slightly wrong
Status in openssh package in Ubuntu:
Fix Released
Status in openssh source package in Jammy:
Fix Committed
Status in openssh source package in Mantic:
Fix Committed
Status in openssh source package in Noble:
Fix Released
Bug description:
[ Impact ]
The gssapi-keyex authentication mechanism has been inadvertently
broken in openssh. It comes from a distro patch[1], and while the
patch still applied, it was no longer correct.
Without the fix, sshd will fail to start if gssapi-keyex is listed in
the AuthenticationMethods of the server, and if not, sshd will still
start, but gssapi-keyex will not be available.
[ Test Plan ]
This update adds a new autopkgtest to the package, which tests both
gssapi-with-mic ("normal" gssapi, which is not affected by this bug),
and gssapi-keyex, which, before this update, does not work.
The test plan is to run the new ssh-gssapi autopkgtest and verify it
succeeds.
[ Where problems could occur ]
ssh is a critical piece of infrastructure, and problems with it could
have catastrophic consequences. The service itself has a test command
before it starts up to verify the syntax of the config file, but that
test is not applied on shutdown, so a restart with an invalid config
file could still leave sshd dead.
The patch adds a change to an authentication structure, but that
change is already present in the upstream code, and we are just
updating it in the new gssapi-keyex code (introduced by the distro[1]
patch, already present). Therefore, mistakes here should manifest
themselves just in the gssapi-keyex code, which wasn't working anyway.
Effectively, though, we are enabling a new authentication mechanism in
sshd, one that was not supposed to have been removed, but was broken
by mistake.
[ Other Info ]
The fact no-one noticed this problem for more than two years could be
telling that there are not many users of this authentication mechanism
out there. The same applies to debian: it has also been broken for a
while there. Maybe we should drop it for future ubuntu releases, since
upstream refuses to take it in.
[ Original Description ]
The Authmethod struct now have 4 entries but the initialization of the
method_gsskeyex in the debian/patches/gssapi.patch only have 3
entries.
The struct was changed in upstream commit
dbb339f015c33d63484261d140c84ad875a9e548 as
===
@@ -104,7 +104,8 @@ struct Authctxt {
struct Authmethod {
char*name;
- int (*userauth)(struct ssh *);
+ char*synonym;
+ int (*userauth)(struct ssh *, const char *);
int *enabled;
};
===
The incorrect code does
===
+Authmethod method_gsskeyex = {
+ "gssapi-keyex",
+ userauth_gsskeyex,
+ _authentication
+};
===
but should have a NULL between the "gssapi-keyex" string and userauth_gsskeyex
This is now (change from Focal) causing gssapi-keyex to be disabled.
===
lsb_release -rd
Description: Ubuntu 22.04.3 LTS
Release: 22.04
===
apt-cache policy openssh-server
openssh-server:
Installed: 1:8.9p1-3ubuntu0.6
Candidate: 1:8.9p1-3ubuntu0.6
Version table:
*** 1:8.9p1-3ubuntu0.6 500
500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu
jammy-updates/main amd64 Packages
500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu
jammy-security/main amd64
[Touch-packages] [Bug 2055397] Re: netplan/systemd-networkd: route metric not applied to routes to the local subnet
** Merge proposal linked: https://code.launchpad.net/~joalif/ubuntu/+source/systemd/+git/systemd/+merge/463755 -- 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/2055397 Title: netplan/systemd-networkd: route metric not applied to routes to the local subnet Status in cloud-init package in Ubuntu: Invalid Status in netplan.io package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Bug description: Cloud-init introduced a feature to configure policy routing on AWS EC2 instances with multiple NICs in https://github.com/canonical/cloud-init/commit/0ca5f31043e2d98eab31a43d9dde9bdaef1435cb targeting v24.1. Cloud-init generates the following netplan config: ``` $ cat /etc/netplan/50-cloud-init.yaml network: ethernets: ens5: dhcp4: true dhcp4-overrides: route-metric: 100 dhcp6: true dhcp6-overrides: *id001 match: macaddress: 0a:c8:ab:90:c2:fb set-name: ens5 ens6: dhcp4: true dhcp4-overrides: route-metric: 200 use-routes: true dhcp6: false match: macaddress: 0a:c6:55:a1:dc:3b routes: - table: 101 to: 0.0.0.0/0 via: 192.168.0.1 - table: 101 to: 192.168.0.0/20 routing-policy: - from: 192.168.10.212 table: 101 set-name: ens6 version: 2 ``` Which renders the following systemd-networkd config files: ``` $ cat 10-netplan-ens5.link [Match] MACAddress=0a:c8:ab:90:c2:fb [Link] Name=ens5 WakeOnLan=off $ cat 10-netplan-ens5.network [Match] MACAddress=0a:c8:ab:90:c2:fb Name=ens5 [Network] DHCP=yes LinkLocalAddressing=ipv6 [DHCP] RouteMetric=100 UseMTU=true $ cat 10-netplan-ens6.link [Match] MACAddress=0a:c6:55:a1:dc:3b [Link] Name=ens6 WakeOnLan=off $ cat 10-netplan-ens6.network [Match] MACAddress=0a:c6:55:a1:dc:3b Name=ens6 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 [Route] Destination=0.0.0.0/0 Gateway=192.168.0.1 Table=101 [Route] Destination=192.168.0.0/20 Scope=link Table=101 [RoutingPolicyRule] From=192.168.10.212 Table=101 [DHCP] RouteMetric=200 UseMTU=true ``` Which configures the instance with the following state in Ubuntu Focal: ``` $ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens5: mtu 9001 qdisc mq state UP group default qlen 1000 link/ether 0a:c8:ab:90:c2:fb brd ff:ff:ff:ff:ff:ff inet 192.168.12.94/20 brd 192.168.15.255 scope global dynamic ens5 valid_lft 2087sec preferred_lft 2087sec inet6 2a05:d012:ea0:c500:6d12:2b20:5fef:a502/128 scope global dynamic noprefixroute valid_lft 440sec preferred_lft 130sec inet6 fe80::8c8:abff:fe90:c2fb/64 scope link valid_lft forever preferred_lft forever 3: ens6: mtu 9001 qdisc mq state UP group default qlen 1000 link/ether 0a:c6:55:a1:dc:3b brd ff:ff:ff:ff:ff:ff inet 192.168.10.212/20 brd 192.168.15.255 scope global dynamic ens6 valid_lft 2083sec preferred_lft 2083sec inet6 fe80::8c6:55ff:fea1:dc3b/64 scope link valid_lft forever preferred_lft forever $ ip route show default via 192.168.0.1 dev ens5 proto dhcp src 192.168.12.94 metric 100 default via 192.168.0.1 dev ens6 proto dhcp src 192.168.10.212 metric 200 192.168.0.0/20 dev ens5 proto kernel scope link src 192.168.12.94 192.168.0.0/20 dev ens6 proto kernel scope link src 192.168.10.212 192.168.0.1 dev ens5 proto dhcp scope link src 192.168.12.94 metric 100 192.168.0.1 dev ens6 proto dhcp scope link src 192.168.10.212 metric 200 $ ip rule show 0: from all lookup local 0: from 192.168.10.212 lookup 101 32766: from all lookup main 32767: from all lookup default $ ip route show table 101 default via 192.168.0.1 dev ens6 proto static onlink 192.168.0.0/20 dev ens6 proto static scope link ``` The issue here is that the instance is not reachable from the same subnet via the private ipv4 of the primary NIC, packets are routed to egress via ens6 and dropped. The cause is that interface metrics are not applied to local subnet routes with systemd 245 (245.4-4ubuntu3.23). On newer systemd versions, as in Jammy, the metrics are correctly applied.
[Touch-packages] [Bug 2058720] Re: 'Other Software' section displays verbose ubuntu.sources comment
*** This bug is a duplicate of bug 2059797 *** https://bugs.launchpad.net/bugs/2059797 ** This bug has been marked a duplicate of bug 2059797 Other Software shows extra comment for Ubuntu distribution repository -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2058720 Title: 'Other Software' section displays verbose ubuntu.sources comment Status in software-properties package in Ubuntu: New Bug description: With software-properties-gtk (0.99.44), the 'Other Software' section displays the full multi-line comment from the new ubuntu.sources file. This creates an unpleasant looking entry in the list. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2058720/+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 2060319] [NEW] tracker failing autopkgtest on noble
Public bug reported: tracker's autopkgtest is failing. I have reported this issue upstream. Our autopkgtest configuration is similar but not identical to our build test configuration which does pass. ** Affects: tracker Importance: Unknown Status: New ** Affects: tracker (Ubuntu) Importance: High Status: Triaged ** Tags: noble update-excuse ** Bug watch added: gitlab.gnome.org/GNOME/tracker/-/issues #434 https://gitlab.gnome.org/GNOME/tracker/-/issues/434 ** Also affects: tracker via https://gitlab.gnome.org/GNOME/tracker/-/issues/434 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/2060319 Title: tracker failing autopkgtest on noble Status in Tracker: New Status in tracker package in Ubuntu: Triaged Bug description: tracker's autopkgtest is failing. I have reported this issue upstream. Our autopkgtest configuration is similar but not identical to our build test configuration which does pass. To manage notifications about this bug go to: https://bugs.launchpad.net/tracker/+bug/2060319/+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 1982935] Re: Selecting "restore defaults" in software-properties-qt has no effect
This affects everything from Jammy to Noble. No output suggesting it's related to bug 1795278, though. ** Changed in: software-properties (Ubuntu) Status: New => Triaged ** Also affects: software-properties Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1982935 Title: Selecting "restore defaults" in software-properties-qt has no effect Status in Software Properties: New Status in software-properties package in Ubuntu: Triaged Bug description: Testing Lubuntu Kinetic daily ISO 26-07-2022 1. Open "Software Sources" from "Preferences menu 2. Select "Authentication" 3. Delete the keys from "Trusted Service Providers" 4. Select "Restore Defaults" 5. After selecting "Restore Defaults" - nothing happens i.e the keys are not restored resulting in the user being unable to perform updates to the system. This bug is most likely related to bug 11795278 https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278 Attached is a screenshot after removing the keys re: step #3 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: software-properties-qt 0.99.25 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Wed Jul 27 09:19:33 2022 InstallationDate: Installed on 2022-07-27 (0 days ago) InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220726) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/software-properties/+bug/1982935/+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 2060311] Re: Setting "optional: true" to overcome he timeout "Job systemd-networkd-wait-online" does no longer work with latest noble image
I see (deep in my mind I remember that such a discussion happened or at
least started somewhere).
Just notice that one interface is still _not_ optional, here in my case:
encc000
And the behavior changed recently, with the above config I didn not hit
the timeout in the past (even with earlier noble daily images).
--
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/2060311
Title:
Setting "optional: true" to overcome he timeout "Job systemd-networkd-
wait-online" does no longer work with latest noble image
Status in Netplan:
New
Status in Ubuntu on IBM z Systems:
New
Status in systemd package in Ubuntu:
New
Bug description:
Especially on s390x (but not limited to s390x) it's often the case that a
system has network devices that are not necessarily connected during boot-up
and one gets such a 2 min timeout:
"Job systemd-networkd-wait-online. Start running (1min 59s / no limit)"
In the past I could avoid that by setting "optional: true" post-install (no
perfect, but worked),
but this does no longer seem to work using the latest noble ISO image (Apr
5th).
Setting 'optional: true' in /etc/netplan/50-cloud-init.yaml looks like
this for me:
# This file is generated from information provided by the datasource. Changes
# to it will not persist across an instance reboot. To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
ethernets:
enP1p0s0:
optional: true
dhcp4: true
enP1p0s0d1:
optional: true
dhcp4: true
enP2p0s0:
optional: true
dhcp4: true
enP2p0s0d1:
optional: true
dhcp4: true
encc000: {}
version: 2
vlans:
encc000.2653:
addresses:
- 10.11.12.15/24
gateway4: 10.11.12.1
id: 2653
link: encc000
nameservers:
addresses:
- 10.11.12.1
... can be set fine (also --dry-run does not moan, except about
dhcp4).
This worked in the past on noble, but also on older Ubuntu releases
like jammy.
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2060311/+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 2058628] Re: initramfs-tools dhcpcd timeout
initramfs-tools 0.142ubuntu23 landed in noble.
** Changed in: initramfs-tools (Ubuntu)
Status: Fix Committed => Confirmed
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => 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/2058628
Title:
initramfs-tools dhcpcd timeout
Status in initramfs-tools package in Ubuntu:
Fix Released
Bug description:
Hi,
We found an issue in `initramfs-tools-core` (noble,now 0.142ubuntu20
all) related to this change :
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2024164
(dhclient replaced by dhcpcd).
dhclient was faster to give an IP. In the `initramfs-tools-core`
scripts, in **/usr/share/initramfs-tools/scripts/functions**, the
ROUNDTTT iterations at _2, 3, 4 or even 6 seconds_ fail. This delays
obtaining an IPv4 by at least 20 seconds.
```
# support ip options see linux sources
# Documentation/filesystems/nfs/nfsroot.txt
# Documentation/frv/booting.txt
for ROUNDTTT in 2 3 4 6 9 16 25 36 64 100; do
local iter_entry_time iter_exit_time
iter_entry_time=$(time_elapsed)
if [ -z "${DEVICE}" ]; then
_set_available_devices_to_up
fi
case ${IP} in
none|done|off)
# Do nothing
IP="done"
;;
""|on|any|dhcp|bootp|both)
dhcpcd -1 -t $ROUNDTTT -4 ${DEVICE:+"${DEVICE}"}
;;
*)
ipconfig -t ${ROUNDTTT} -d "$IP"
```
dhcpcd takes at least 5/6 seconds to give an ipv4 because of the arp
probbing to check that the ip is not already in use.
**Possible Fixes**: `dhcpcd --noarp` prevents waiting, otherwise
redistribute the ROUNDTTT iterations by deleting the iterations at 2 3
4 or even 6 seconds.
NB: this problem probably only concerns obtaining an IP in IPv4, I
have not checked if the problem also arises in IPv6.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2058628/+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 2059797] Re: Other Software shows extra comment for Ubuntu distribution repository
** Attachment added: "Screenshot from 2024-03-22 10-38-59.png" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2059797/+attachment/5761695/+files/Screenshot%20from%202024-03-22%2010-38-59.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2059797 Title: Other Software shows extra comment for Ubuntu distribution repository Status in software-properties package in Ubuntu: Confirmed Bug description: Test Case - - Open the Software & Updates tab - Switch to the Other Software tab There is an entry for ## Ubuntu distribution repository ## ## The following settings can be adjusted to configure which packages to use from Ubuntu. etc. What I Expected --- That comment should not show. Selecting the entry and clicking Edit allows adjusting the main Ubuntu repository source settings which should not be allowed there since it is already possible to do that from the Ubuntu Software tab. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: software-properties-gtk 0.99.44 ProcVersionSignature: Ubuntu 6.8.0-20.20-generic 6.8.1 Uname: Linux 6.8.0-20-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 12:10:24 2024 InstallationDate: Installed on 2022-04-06 (723 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: software-properties UpgradeStatus: Upgraded to noble on 2023-12-09 (111 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2059797/+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 1795278] Re: software-properties-{qt, kde} attempts to use KUrl but it doesn't exist
Assigned to you, Aaron :)
** Changed in: software-properties (Ubuntu Jammy)
Assignee: (unassigned) => Aaron Rainbolt (arraybolt3)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1795278
Title:
software-properties-{qt,kde} attempts to use KUrl but it doesn't exist
Status in software-properties package in Ubuntu:
Fix Released
Status in software-properties source package in Focal:
Won't Fix
Status in software-properties source package in Jammy:
Triaged
Status in software-properties source package in Kinetic:
Won't Fix
Status in software-properties source package in Lunar:
Triaged
Bug description:
Release: Kubuntu 18.04
Version: 0.96.24.32.1
When clicking the "Import Key" button in the "Authentication" section
of the panel it throws this error:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/kde/SoftwarePropertiesKDE.py",
line 667, in add_key_clicked
url = KUrl.fromPath(home)
NameError: name 'KUrl' is not defined
While this doesn't crash the program it causes nothing to happen when
clicking the button. Running the program in a terminal reveals the
error being printed to stderr.
After debugging it appears KUrl doesn't exist anywhere and I'm not
sure if's a python module that has changed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278/+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 2060311] Re: Setting "optional: true" to overcome he timeout "Job systemd-networkd-wait-online" does no longer work with latest noble image
There has been confusion in this area in the past. But the stance of
upstream is that RequiredForOnline=no => "interface is _ignored_ by
systemd-networkd-wait-online". Hence, if every interface is optional:
true, it is expected that systemd-networkd-wait-online will timeout.
I have recently suggested that netplan moves to a strategy where if
interface ethX is optional:false, then enable systemd-networkd-wait-
online@ethX.service. And, if ethX has optional: true, then do nothing
(namely do _not_ set RequiredForOnline=no). We probably need to then
either disable systemd-networkd-wait-online.service by default, or
change the default flags.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags added: rls-nn-incoming
--
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/2060311
Title:
Setting "optional: true" to overcome he timeout "Job systemd-networkd-
wait-online" does no longer work with latest noble image
Status in Netplan:
New
Status in Ubuntu on IBM z Systems:
New
Status in systemd package in Ubuntu:
New
Bug description:
Especially on s390x (but not limited to s390x) it's often the case that a
system has network devices that are not necessarily connected during boot-up
and one gets such a 2 min timeout:
"Job systemd-networkd-wait-online. Start running (1min 59s / no limit)"
In the past I could avoid that by setting "optional: true" post-install (no
perfect, but worked),
but this does no longer seem to work using the latest noble ISO image (Apr
5th).
Setting 'optional: true' in /etc/netplan/50-cloud-init.yaml looks like
this for me:
# This file is generated from information provided by the datasource. Changes
# to it will not persist across an instance reboot. To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
ethernets:
enP1p0s0:
optional: true
dhcp4: true
enP1p0s0d1:
optional: true
dhcp4: true
enP2p0s0:
optional: true
dhcp4: true
enP2p0s0d1:
optional: true
dhcp4: true
encc000: {}
version: 2
vlans:
encc000.2653:
addresses:
- 10.11.12.15/24
gateway4: 10.11.12.1
id: 2653
link: encc000
nameservers:
addresses:
- 10.11.12.1
... can be set fine (also --dry-run does not moan, except about
dhcp4).
This worked in the past on noble, but also on older Ubuntu releases
like jammy.
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2060311/+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 2058415] Re: Reading binary data in paraview broken by libexpat1 update
** Also affects: dune-grid (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to expat in Ubuntu. https://bugs.launchpad.net/bugs/2058415 Title: Reading binary data in paraview broken by libexpat1 update Status in dune-grid package in Ubuntu: New Status in expat package in Ubuntu: Confirmed Status in paraview package in Ubuntu: Confirmed Bug description: The recent update of libexpat1 to version 2.5.0-2ubuntu0.1 broke Paraview. In particular reading vtu files containing binary data fails since this update. When trying to open files that worked fine before, Paraview now reports a parsing error like this one: ERROR: In vtkXMLParser.cxx, line 376 vtkXMLDataParser (0x5b0ac36fc970): Error parsing XML in stream at line 21, column 0, byte index 1036: not well-formed (invalid token) ERROR: In vtkXMLReader.cxx, line 521 vtkXMLUnstructuredGridReader (0x5b0ac3d3b670): Error parsing input file. ReadXMLInformation aborting. The problem disappears when reverting libexpat1 to version 2.5.0-2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dune-grid/+bug/2058415/+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 2060331] Re: add-apt-repository --list not returning any deb822 repositories
In case anyone else comes across this bug, the following workaround to
create the old style '.list' file works well:
---
1. Create an 'aptaddppa' function (ZSH):
---
aptaddppa () {
curl -fsSL
"https://keyserver.ubuntu.com/pks/lookup?op=get=0x${4}; | sudo
gpg --dearmor -o /etc/apt/trusted.gpg.d/"${1}".gpg
echo "deb [arch=$(dpkg --print-architecture)] ${2} $(lsb_release
-cs) ${3}" | sudo tee /etc/apt/sources.list.d/"${1}".list
sudo apt update
}
---
2. From the command line:
---
$ aptaddppa flacon https://ppa.launchpadcontent.net/flacon/ppa/ubuntu
main 0606FBEA73863686801BE20ED5790E4FF2A61FE5
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2060331
Title:
add-apt-repository --list not returning any deb822 repositories
Status in software-properties package in Ubuntu:
New
Bug description:
Recreating the following bug report (#2052851) with a new title per
Jeremy Bícha's (jbicha) request:
https://bugs.launchpad.net/ubuntu/+source/software-
properties/+bug/2052851
---
On Ubuntu 23.10:
* When adding a PPA, 'add-apt-repository' will add the repository in
the new deb822 format as a '.sources' file in
'/etc/apt/sources.list.d'
* However, 'add-apt-repository --list' cannot see/understand the new
'.sources' file
For example, with the flacon ppa
(https://launchpad.net/~flacon/+archive/ubuntu/ppa):
1. 'sudo add-apt-repository ppa:flacon/ppa' adds the flacon repo as
'/etc/apt/sources.list.d/flacon-ubuntu-ppa-mantic.sources'
2. apt can install and update from the new repo, as expected. you can
also remove the repo, as expected, by running 'sudo add-apt-repository
--remove ppa:flacon/ppa'
3. However, 'add-apt-repository --list' does not list the repo as it
should. GUI package managers such as Muon and Synaptic also do not see
the new repo.
It makes working with packages frustrating, and unfortunately, per
Julian Andres Klode (juliank), there seems to be no plan to fix the
broken 'software-properties-common' any time soon. See here:
https://bugs.launchpad.net/ubuntu/+source/software-
properties/+bug/2033949
Also see related issues:
https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2037210
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2036288
https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042791.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2060331/+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 2053146] Re: openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is slightly wrong
Hello ake, or anyone else affected,
Accepted openssh into mantic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:9.3p1-1ubuntu3.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
mantic to verification-done-mantic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-mantic. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: openssh (Ubuntu Mantic)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-mantic
** Changed in: openssh (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Tags added: verification-needed-jammy
--
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/2053146
Title:
openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is
slightly wrong
Status in openssh package in Ubuntu:
Fix Released
Status in openssh source package in Jammy:
Fix Committed
Status in openssh source package in Mantic:
Fix Committed
Status in openssh source package in Noble:
Fix Released
Bug description:
[ Impact ]
The gssapi-keyex authentication mechanism has been inadvertently
broken in openssh. It comes from a distro patch[1], and while the
patch still applied, it was no longer correct.
Without the fix, sshd will fail to start if gssapi-keyex is listed in
the AuthenticationMethods of the server, and if not, sshd will still
start, but gssapi-keyex will not be available.
[ Test Plan ]
This update adds a new autopkgtest to the package, which tests both
gssapi-with-mic ("normal" gssapi, which is not affected by this bug),
and gssapi-keyex, which, before this update, does not work.
The test plan is to run the new ssh-gssapi autopkgtest and verify it
succeeds.
[ Where problems could occur ]
ssh is a critical piece of infrastructure, and problems with it could
have catastrophic consequences. The service itself has a test command
before it starts up to verify the syntax of the config file, but that
test is not applied on shutdown, so a restart with an invalid config
file could still leave sshd dead.
The patch adds a change to an authentication structure, but that
change is already present in the upstream code, and we are just
updating it in the new gssapi-keyex code (introduced by the distro[1]
patch, already present). Therefore, mistakes here should manifest
themselves just in the gssapi-keyex code, which wasn't working anyway.
Effectively, though, we are enabling a new authentication mechanism in
sshd, one that was not supposed to have been removed, but was broken
by mistake.
[ Other Info ]
The fact no-one noticed this problem for more than two years could be
telling that there are not many users of this authentication mechanism
out there. The same applies to debian: it has also been broken for a
while there. Maybe we should drop it for future ubuntu releases, since
upstream refuses to take it in.
[ Original Description ]
The Authmethod struct now have 4 entries but the initialization of the
method_gsskeyex in the debian/patches/gssapi.patch only have 3
entries.
The struct was changed in upstream commit
dbb339f015c33d63484261d140c84ad875a9e548 as
===
@@ -104,7 +104,8 @@ struct Authctxt {
struct Authmethod {
char*name;
- int (*userauth)(struct ssh *);
+ char*synonym;
+ int (*userauth)(struct ssh *, const char *);
int *enabled;
};
===
The incorrect code does
===
+Authmethod method_gsskeyex = {
+ "gssapi-keyex",
+ userauth_gsskeyex,
+ _authentication
+};
===
but should have a NULL between the "gssapi-keyex" string and userauth_gsskeyex
This is now (change from Focal) causing gssapi-keyex to be disabled.
===
lsb_release -rd
Description: Ubuntu 22.04.3 LTS
Release: 22.04
===
apt-cache policy openssh-server
openssh-server:
Installed: 1:8.9p1-3ubuntu0.6
[Touch-packages] [Bug 2060319] Re: tracker failing autopkgtest on noble
** Changed in: tracker (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/2060319 Title: tracker failing autopkgtest on noble Status in Tracker: New Status in tracker package in Ubuntu: Triaged Status in tracker package in Debian: Confirmed Bug description: tracker's autopkgtest is failing. I have reported this issue upstream. Our autopkgtest configuration is similar but not identical to our build test configuration which does pass. To manage notifications about this bug go to: https://bugs.launchpad.net/tracker/+bug/2060319/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record
On Thu, 28 Mar 2024, Ashish upara wrote: > Date: Thu, 28 Mar 2024 13:24:55 > From: Ashish upara <1586...@bugs.launchpad.net> > To: gra...@bozikins.free-online.co.uk > Subject: [Bug 1586528] Re: Avahi-daemon withdraws address record > > Is this issue solved till now? > Also are these solutions applicable for Ubuntu 20.04.6 LTS or not. > > Hello, I am sorry that I had not noticed your question earlier. It would be better if you sent your question to the "Launchpad" discussion, where there are many more people who have much more knowledge than I have. Yours, -- Graham "What's the difference between a 'hippo' and a 'Zippo'? One is really heavy, the other is a little lighter" -- Masai Graham http://english-1329209197.spampoison.com;>Get free spam bait here. -- 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/1586528 Title: Avahi-daemon withdraws address record Status in avahi package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Bug description: For some reason, if I leave my Ubuntu VM up for a prolonged period of time the machine will lose connection to the network. ip addr shows that the nic port no longer has an address and an examination of the syslog shows this: May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record for 10.0.2.15 on enp0s3. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast group on interface enp0s3.IPv4 with address 10.0.2.15. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no longer relevant for mDNS. for no known reason. The only reliable way to get the network to come back (that I have found) is a full reboot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 27 15:11:34 2016 InstallationDate: Installed on 2015-10-22 (218 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: avahi UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+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 2060326] [NEW] unnattended upgrades stuck burning 100% cpu
Public bug reported: For the last hour or so, unattended upgrades has been stuck burning 100% of a cpu. series: noble version: 2.9.1+nmu4ubuntu1 ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New -- 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/2060326 Title: unnattended upgrades stuck burning 100% cpu Status in unattended-upgrades package in Ubuntu: New Bug description: For the last hour or so, unattended upgrades has been stuck burning 100% of a cpu. series: noble version: 2.9.1+nmu4ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2060326/+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 2060319] Re: tracker failing autopkgtest on noble
** Changed in: tracker Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/2060319 Title: tracker failing autopkgtest on noble Status in Tracker: New Status in tracker package in Ubuntu: Triaged Status in tracker package in Debian: Unknown Bug description: tracker's autopkgtest is failing. I have reported this issue upstream. Our autopkgtest configuration is similar but not identical to our build test configuration which does pass. To manage notifications about this bug go to: https://bugs.launchpad.net/tracker/+bug/2060319/+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 2060326] Re: unnattended upgrades stuck burning 100% cpu
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unattended-upgrades (Ubuntu) Status: New => Confirmed -- 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/2060326 Title: unnattended upgrades stuck burning 100% cpu Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: For the last hour or so, unattended upgrades has been stuck burning 100% of a cpu. series: noble version: 2.9.1+nmu4ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2060326/+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 2052851] Re: add-apt-repository Cannot Manage deb822 Repository Sources
*** This bug is a duplicate of bug 2033949 *** https://bugs.launchpad.net/bugs/2033949 I marked this as a duplicate because Ubuntu 24.04 LTS does handle PPAs now. I recommend trying Ubuntu 24.04 LTS Beta when it is released soon. Could you open a separate issue for add-apt-repository --list not returning any deb822 repositories? ** This bug has been marked a duplicate of bug 2033949 Does not work with Ubuntu sources in deb822 format -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2052851 Title: add-apt-repository Cannot Manage deb822 Repository Sources Status in software-properties package in Ubuntu: New Bug description: On Ubuntu 23.10... * When adding a PPA, 'add-apt-repository' will add the repository in the new deb822 format as a '.sources' file in '/etc/apt/sources.list.d' * However, 'add-apt-repository --list' cannot see/understand the new '.sources' file For example, with the flacon ppa (https://launchpad.net/~flacon/+archive/ubuntu/ppa): 1. 'sudo add-apt-repository ppa:flacon/ppa' adds the flacon repo as '/etc/apt/sources.list.d/flacon-ubuntu-ppa-mantic.sources' 2. apt can install and update from the new repo, as expected. you can also remove the repo, as expected, by running 'sudo add-apt-repository --remove ppa:flacon/ppa' 3. However, 'add-apt-repository --list' does not list the repo as it should. GUI package managers such as Muon and Synaptic also do not see the new repo. It makes working with packages quite frustrating, and unfortunately, per Julian Andres Klode (juliank), there seems to be no plan to fix the broken 'software-properties-common' any time soon. See here: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2033949 Also see related issues: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761 https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2037210 https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2036288 https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042791.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2052851/+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 2059078] Re: proposed-migration for faketime 0.9.10-2.1ubuntu1
I added an sssd task due to the workaround we had to add to it in https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2058576 (we don't install faketime). Should faketime be fixed, then we can revert that change in sssd. ** Also affects: sssd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/2059078 Title: proposed-migration for faketime 0.9.10-2.1ubuntu1 Status in bash package in Ubuntu: New Status in faketime package in Ubuntu: New Status in sssd package in Ubuntu: New Bug description: faketime 0.9.10-2.1ubuntu1 is stuck in -proposed with build failures on armhf. On armhf, the testsuite confusingly fails with a stack smash error. But this error happens in bash, which isn't even meant to be the process under test. Minimal reproducer: # LD_PRELOAD=./src/libfaketime.so.1 bash -c 'exit 0' *** stack smashing detected ***: terminated Aborted (core dumped) # Confusingly, ltrace shows different results for the newly-built binary than from one built without 64-bit time_t. # LD_PRELOAD=./src/libfaketime.so.1 ltrace --library '*faketime*' bash -c 'exit 0' bash->getrandom(0x1f3bf08, 1, 0x9683b0, 0) = 0xc8202 bash->getrandom(0xc8203, 0xf7fad53c, 1023, 0xf7eef801) = 0xc8202 *** stack smashing detected ***: terminated --- SIGABRT (Aborted) --- +++ killed by SIGABRT +++ # LD_PRELOAD=/usr/lib/arm-linux-gnueabihf/faketime/libfaketime.so.1 ltrace --library '*faketime*' bash -c 'exit 0' bash->gettimeofday(0x8b07a0, 0) = 0 bash->getpid() = 819717 bash->gettimeofday(0xffb88714, 0)= 0 bash->getpid() = 819717 bash->gettimeofday(0xffb8871c, 0)= 0 bash->getpid() = 819717 +++ exited (status 0) +++ # Unsetting -DFAKE_RANDOM in debian/rules does not fix the problem however. So simply loading the LD_PRELOAD library without executing it seems to be enough to break bash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/2059078/+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 1964579] Re: Pulseaudio fails to detect /enable Intel SST sound card
Are you sure this isn't because of requiring proprietary drivers? ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1964579 Title: Pulseaudio fails to detect /enable Intel SST sound card Status in pulseaudio package in Ubuntu: Incomplete Bug description: Testing Live session and also full install Ubuntu Mate Jammy daily ISO 11-03-2022 The machine tested - AEROFARA Aero2 Pro, N5105,8GB,Ethernet GB,WiFi,Bluetooth 4.0,128GB SSD,Intel UHD Graphics The audio card is not detected - entering sound preferences settings - "output" only shows dummy output stereo - under "hardware" is no entry available ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass CasperVersion: 1.467 CurrentDesktop: MATE Date: Fri Mar 11 09:25:31 2022 LiveMediaBuild: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220311) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Digital Out, HDMI Title: [AERO 2 Pro, Intel Jasperlake HDMI, Digital Out, HDMI] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: JB1006 dmi.board.asset.tag: Default string dmi.board.name: AERO 2 Pro dmi.board.vendor: Shenzhen Wangang Technology Co., Ltd dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 0.7 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrJB1006:bd12/13/2021:br5.19:efr0.7:svnShenzhenWangangTechnologyCo.,Ltd:pnAERO2Pro:pvrDefaultstring:rvnShenzhenWangangTechnologyCo.,Ltd:rnAERO2Pro:rvrDefaultstring:cvnDefaultstring:ct35:cvrDefaultstring:skuAERO2Pro: dmi.product.family: Windows 10 Pro dmi.product.name: AERO 2 Pro dmi.product.sku: AERO 2 Pro dmi.product.version: Default string dmi.sys.vendor: Shenzhen Wangang Technology Co., Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1964579/+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 2051895] Re: Lenovo XT99 BT headset can't work in HFP profile
This bug was fixed in the package pulseaudio - 1:16.1+dfsg1-2ubuntu10 --- pulseaudio (1:16.1+dfsg1-2ubuntu10) noble; urgency=medium * debian/patches/git_tests_alignment.patch: - cherrypick an upstream change to fix a test failure with the new orc version -- Sebastien Bacher Wed, 03 Apr 2024 10:18:51 +0200 ** Changed in: pulseaudio (Ubuntu Noble) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2051895 Title: Lenovo XT99 BT headset can't work in HFP profile Status in HWE Next: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Jammy: Fix Released Status in pulseaudio source package in Mantic: Fix Released Status in pulseaudio source package in Noble: Fix Released Bug description: [Summary] When use the ThinkPluse xt99 bluetooth head set to run the test com.canonical.certification::bluetooth/audio_record_playback, it cannot record the sound and playback. It seems this device cannot switch to Hand free mode in this platform. [Steps to reproduce] Connect the ThinkPluse xt99, use the Handfree mode, then try to record some voice. [Expected result] The bluetooth headset ThinkPluse xt99 can use as a MIC to input sound. [Actual result] The bluetooth headset xt99 cannot work in the Handfree mode. [Failure rate] 100% [Impact] With the current Ubuntu 22.04 oem image, we try to connect the LENOVO XT99 bt headset and let it work in HFP mode, we select HFP profile from gnome sound-setting, but the microphone will not auto change to bt microphone and the bt output could not work too. So this BT headset could only work in A2DP mode with the current 22.04 OEM image. And we tried ubuntu 22.04 generic image, mantic image and noble image, none of them could make the headset work in HFP mode. [Fix] Cherry-pick a pulseaudio commit from upstream. [Test] I installed ubuntu 22.04 and 23.10 on 2 different Thinkpad laptops, then upgraded the pulseaudio from my ppa (ppa:hui.wang/pa-testing), in theory my change only affects bluetooth audio devices, it will not bring any impact to non-audio bluetooth devices, here I did the test with 7 bluetooth audio devices and 2 non-audio devices: BT audio devices (pairing, connection, re-connection, playback and capture all worked well): PLT_BBTGO2 (headset) Xiaomi Air3 SE (headset) Crusher Wireless (headset) SOAIY S18 (sound box) HK Soho Wireless (headset) Thinkplus XT99 (headset) Wl-1000X (headset) BT non-audio devices (pairing, connection, re-connection, key input all worked well): BT3.0 Keyboard The Pinao 2 keyboard [Where problems could occur] This change will impact bt headset negotiation process in the pulseaudio, so the possiblity of regression is limited to bt headset, it could make the bt headset fail to connect, but this possibility is very low, we tested the patch with different bt headset and bt speaker, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051895/+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 2059797] Re: Other Software shows extra comment for Ubuntu distribution repository
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2059797 Title: Other Software shows extra comment for Ubuntu distribution repository Status in software-properties package in Ubuntu: Confirmed Bug description: Test Case - - Open the Software & Updates tab - Switch to the Other Software tab There is an entry for ## Ubuntu distribution repository ## ## The following settings can be adjusted to configure which packages to use from Ubuntu. etc. What I Expected --- That comment should not show. Selecting the entry and clicking Edit allows adjusting the main Ubuntu repository source settings which should not be allowed there since it is already possible to do that from the Ubuntu Software tab. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: software-properties-gtk 0.99.44 ProcVersionSignature: Ubuntu 6.8.0-20.20-generic 6.8.1 Uname: Linux 6.8.0-20-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 12:10:24 2024 InstallationDate: Installed on 2022-04-06 (723 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: software-properties UpgradeStatus: Upgraded to noble on 2023-12-09 (111 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2059797/+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 2060326] Re: unnattended upgrades stuck burning 100% cpu
Same here, `unattended-upgrade` hogging CPU for 10hours straight already. -- 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/2060326 Title: unnattended upgrades stuck burning 100% cpu Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: For the last hour or so, unattended upgrades has been stuck burning 100% of a cpu. series: noble version: 2.9.1+nmu4ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2060326/+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 2056187] Re: fails to configure BOOTIF when using iscsi
clevis/18-1ubuntu1 ran into a timeout. I retried the test.
--
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/2056187
Title:
fails to configure BOOTIF when using iscsi
Status in initramfs-tools package in Ubuntu:
Fix Released
Status in open-iscsi package in Ubuntu:
Invalid
Status in initramfs-tools source package in Focal:
Fix Committed
Status in open-iscsi source package in Focal:
New
Status in initramfs-tools source package in Jammy:
Fix Committed
Status in open-iscsi source package in Jammy:
New
Bug description:
[ Impact ]
* MAAS cannot PXE-boot a machine that has iSCSI disks
* Focal is the default Ubuntu distribution deployed by MAAS, so we should
back-port this to ensure it works out-of-the-box.
[ Test Plan ]
* reproducing this issue requires a machine with iSCSI disks (Cisco UCS
Manager
in the original report), and a MAAS controller (3.4 or better)
* the issue can be observed by simply enlisting the machine in MAAS. It will
fail to boot due to the missing BOOTIF configuration.
[ Where problems could occur ]
* the problematic code was an attempt to fix LP#2037202, so we should watch
out
for regressions.
[ Original report ]
we have a bad interaction between initramfs-tools and open-iscsi,
resulting in the boot interface not being configured.
when the iscsi has a static address, the script `local-top/iscsi` from
open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi
interface. The existence of this file makes configure_networking()
skip configuring the BOOTIF later due to this code in
`scripts/functions`:
for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
if [ -e "$x" ]; then
IP=done
break
fi
done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 772024] Re: tzdata update keeps changing my timezone
** Changed in: tzdata (Ubuntu Kinetic) Status: New => Won't Fix ** No longer affects: tzdata (Ubuntu Kinetic) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/772024 Title: tzdata update keeps changing my timezone Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata package in Debian: Fix Released Bug description: [ Impact ] Users can select some time zones in debconf that the tzdata debconf script will replace on the next run. See "Original report" for more explanation. Either those time zones should not be selectable in debconf or they should not be replaced. [ Test Plan ] Select US/Central as time zone and run dpkg-reconfigure: ``` sudo ln -sf /usr/share/zoneinfo/US/Central /etc/localtime echo "US/Central" | sudo tee /etc/timezone sudo dpkg-reconfigure -fnoninteractive tzdata ``` The output of dpkg-reconfigure should say that the current default time zone is still US/Central. Besides this manual test, test_timezone_conversions is backported to check that there are no timezones which can be selected, but will be converted. [ Where problems could occur ] Besides added tests, the debconf part of tzdata is touched and could cause issues. The change does not touch the actual timezones. [ Original report ] Other than the fact that Chicago, Illinois is in US Central Timezone, I have no relationship to Chicago. I am not in Chicago. I do not want to be in Chicago. I am in the Central Timezone. I am physically closer to other cities mentioned in tzdata. Selecting America/Chicago versus US/Central is not easier for me nor is it more intuitive. I understand that the upstream tzdata package goes a long way in documenting all of the weirdness associated with timezones and different localities' treatment of timezones and daylight "savings" time. However, from an end-user perspective, the distribution should place no special importance or preference on one timezone specification or another. Likewise, if a user chooses a timezone, the system should never change it. To reproduce the issue: # Manually select US/Central me@ubuntu:~$ sudo dpkg-reconfigure tzdata [sudo] password for me: Current default time zone: 'US/Central' Local time is now: Wed Apr 27 16:05:02 CDT 2011. Universal Time is now: Wed Apr 27 21:05:02 UTC 2011. # Validation that selection was accepted me@ubuntu:~$ cat /etc/timezone US/Central me@ubuntu:~$ md5sum /etc/localtime /usr/share/zoneinfo/US/Central 6540624294b1193e22ed7a15692f2de7 /etc/localtime 6540624294b1193e22ed7a15692f2de7 /usr/share/zoneinfo/US/Central me@ubuntu:~$ debconf-show tzdata debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied tzdata/Zones/Australia: * tzdata/Zones/US: Central tzdata/Zones/Asia: * tzdata/Zones/Etc: UTC tzdata/Zones/SystemV: tzdata/Zones/Arctic: tzdata/Zones/Pacific: tzdata/Zones/Antarctica: tzdata/Zones/Europe: tzdata/Zones/Africa: * tzdata/Zones/America: Chicago * tzdata/Areas: US tzdata/Zones/Atlantic: tzdata/Zones/Indian: # Force the package to reinstall me@ubuntu:~$ aptitude reinstall tzdata The following packages will be REINSTALLED: tzdata 0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/658 kB of archives. After unpacking 0 B will be used. Preconfiguring packages ... (Reading database ... 168356 files and directories currently installed.) Preparing to replace tzdata 2011g-0ubuntu0.11.04 (using .../tzdata_2011g-0ubuntu0.11.04_all.deb) ... Unpacking replacement tzdata ... Setting up tzdata (2011g-0ubuntu0.11.04) ... Current default time zone: 'America/Chicago' Local time is now: Wed Apr 27 16:05:22 CDT 2011. Universal Time is now: Wed Apr 27 21:05:22 UTC 2011. Run 'dpkg-reconfigure tzdata' if you wish to change it. # Now previous indicators are reset to America/Chicago instead of US/Central ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: tzdata 2011g-0ubuntu0.11.04 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Wed Apr 27 15:54:33 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 LANGUAGE=en_US:en SourcePackage: tzdata UpgradeStatus: Upgraded to natty on 2011-04-10 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/772024/+subscriptions -- Mailing
[Touch-packages] [Bug 2057836] Re: gst-python1.0 fails to build: test failures
** Changed in: pygobject Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/2057836 Title: gst-python1.0 fails to build: test failures Status in pygobject: Fix Released Status in gst-python1.0 package in Ubuntu: Triaged Status in pygobject package in Ubuntu: Triaged Status in gst-python1.0 package in Debian: Confirmed Bug description: gst-python1.0 fails to build because of test failures. https://launchpad.net/ubuntu/+source/gst-python1.0/1.22.10-1build1 https://launchpad.net/ubuntu/+source/gst-python1.0/1.24.0-1 I have reported the issue to the upstream developers https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353 To manage notifications about this bug go to: https://bugs.launchpad.net/pygobject/+bug/2057836/+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 2059739] Re: initramfs-tools 0.142ubuntu23 copies host /etc/passwd into initramfs
** Tags added: patch -- 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/2059739 Title: initramfs-tools 0.142ubuntu23 copies host /etc/passwd into initramfs Status in initramfs-tools package in Ubuntu: In Progress Bug description: Recent changes to the dhcpd hook shipped with dhcpdinitramfs-tools 0.142ubuntu23 (noble-dev) copy the host /etc/passwd into the initramfs-image: https://git.launchpad.net/ubuntu/+source/initramfs-tools/commit/hooks/dhcpcd?h=applied/ubuntu/noble=73c865b9d234087d977d7baa20852639746567fd This has multiple problems: * The passwd file is copied without checking if the dhcpcd user actually exists (which is created by dhcpcd package, but only dhcpcd-base is installed via dependencies) * The change breaks dropbear-initramfs because the passwd file contains a root user with a non existing home directory * leaking user information into initramfs (which may or may not be a problem on fully encrypted systems) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2059739/+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 2060291] Re: Horizonral line artifact/ghosting when scaling windows to a certain width
Some similar issues involve a stripe of corrupted graphics memory along
the entire width of the framebuffer. THIS IS NOT THAT ISSUE. It's more
like a bunch of 1px lines are spilling an image from somewhere else on
the screen. In particular one of the screenshots shows the taskbar
spilling on top of the desktop background by way of a nautilus window.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2060291
Title:
Horizonral line artifact/ghosting when scaling windows to a certain
width
Status in nautilus package in Ubuntu:
New
Status in xorg package in Ubuntu:
New
Bug description:
When scaling some windows in some programs down horizontal lines
appear that seem to be part of the texture memory somewhere else on
the screen.
This only occurs in some programs like nautilus and gedit, but not in
others like terminal or Firefox.
It did however occur when I opened the dialog in firefox to attach the
screen capture.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 5 03:44:15 2024
DistUpgraded: 2024-04-04 22:25:39,405 DEBUG icon theme changed, re-reading
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
nvidia/470.239.06, 5.15.0-101-generic, x86_64: installed
nvidia/470.239.06, 6.5.0-26-generic, x86_64: installed
GraphicsCard:
Intel Corporation Alder Lake-N [UHD Graphics] [8086:46d2] (prog-if 00 [VGA
controller])
Subsystem: Intel Corporation Alder Lake-N [UHD Graphics] [8086:7270]
InstallationDate: Installed on 2022-12-15 (477 days ago)
InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64
(20210915)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 001 Device 003: ID 0461:4e8d Primax Electronics, Ltd HP USB Optical Mouse
Bus 001 Device 002: ID 04f3:0103 Elan Microelectronics Corp. ActiveJet
K-2024 Multimedia Keyboard
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic
root=UUID=7e20054f-50f7-4011-8c9c-516960719274 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2024-04-05 (0 days ago)
dmi.bios.date: 02/06/2023
dmi.bios.release: 5.26
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: ADLNV104
dmi.board.asset.tag: Default string
dmi.board.name: MINI S
dmi.board.vendor: AZW
dmi.board.version: 10
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrADLNV104:bd02/06/2023:br5.26:svnAZW:pnMINIS:pvrDefaultstring:rvnAZW:rnMINIS:rvr10:cvnDefaultstring:ct3:cvrDefaultstring:sku01:
dmi.product.family: Default string
dmi.product.name: MINI S
dmi.product.sku: 01
dmi.product.version: Default string
dmi.sys.vendor: AZW
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.8
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/nautilus/+bug/2060291/+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 2055200] Re: tests-in-lxd is broken with latest autopkgtest version
Why is Mantic won't fix? This could potentially break a lot of kernel ADT testing for Mantic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2055200 Title: tests-in-lxd is broken with latest autopkgtest version Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Triaged Status in systemd source package in Mantic: Won't Fix Bug description: With autopkgtest 5.32 being SRU'd to Jammy[1], `tests-in-lxd` breaks because it can't patch `autopkgtest-build-lxd` anymore. Please find a debdiff attached to fix that issue. [1]: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2051939 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2055200/+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 2058242] Re: Demote isc-dhcp to universe
Uploaded avahi 0.8-13ubuntu6 to demote isc-dhcp-client from Recommends to Suggests ** Changed in: avahi (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/2058242 Title: Demote isc-dhcp to universe Status in avahi package in Ubuntu: Fix Committed Bug description: Following the replacement of dhclient by dhcpcd as new DHCP client tool, it is now time to demote isc-dhcp-client. After demoting isc- dhcp-server (bug # 2045577) the complete isc-dhcp can be demoted. ``` $ reverse-depends -c main,restricted isc-dhcp-client $ reverse-depends -c main,restricted -b isc-dhcp-client ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/2058242/+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 2060326] Re: unnattended upgrades stuck burning 100% cpu
** Attachment added: "strace.40801" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2060326/+attachment/5761743/+files/strace.40801 -- 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/2060326 Title: unnattended upgrades stuck burning 100% cpu Status in unattended-upgrades package in Ubuntu: New Bug description: For the last hour or so, unattended upgrades has been stuck burning 100% of a cpu. series: noble version: 2.9.1+nmu4ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2060326/+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 2054902] Re: apport test error: /bin/bash not found
https://github.com/canonical/apport/pull/308 got merged.
** Changed in: apport
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2054902
Title:
apport test error: /bin/bash not found
Status in Apport:
Fix Committed
Status in apport package in Ubuntu:
New
Bug description:
This looks like fallout from the completion of usrmerge.
https://autopkgtest.ubuntu.com/packages/apport
=== FAILURES
===
367s ___ T.test_get_file_package
367s
367s self =
367s
367s def test_get_file_package(self):
367s """get_file_package() on installed files."""
367s > self.assertEqual(impl.get_file_package("/bin/bash"), "bash")
367s E AssertionError: None != 'bash'
367s
367s tests/integration/test_packaging_apt_dpkg.py:158: AssertionError
367s ___ T.test_get_files
___
367s
367s self =
367s
367s def test_get_files(self):
367s """get_files()."""
367s self.assertRaises(ValueError, impl.get_files, "nonexisting")
367s > self.assertIn("/bin/bash", impl.get_files("bash"))
367s E AssertionError: '/bin/bash' not found in ['/.', '/etc',
'/etc/bash.bashrc', '/etc/skel', '/etc/skel/.bash_logout', '/etc/skel/.bashrc',
'/etc/skel/.profile', '/usr', '/usr/bin', '/usr/bin/bash', '/usr/bin/bashbug',
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2054902/+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 2060291] [NEW] Horizonral line artifact/ghosting when scaling windows to a certain width
Public bug reported:
When scaling some windows in some programs down horizontal lines appear
that seem to be part of the texture memory somewhere else on the screen.
This only occurs in some programs like nautilus and gedit, but not in
others like terminal or Firefox.
It did however occur when I opened the dialog in firefox to attach the
screen capture.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 5 03:44:15 2024
DistUpgraded: 2024-04-04 22:25:39,405 DEBUG icon theme changed, re-reading
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
nvidia/470.239.06, 5.15.0-101-generic, x86_64: installed
nvidia/470.239.06, 6.5.0-26-generic, x86_64: installed
GraphicsCard:
Intel Corporation Alder Lake-N [UHD Graphics] [8086:46d2] (prog-if 00 [VGA
controller])
Subsystem: Intel Corporation Alder Lake-N [UHD Graphics] [8086:7270]
InstallationDate: Installed on 2022-12-15 (477 days ago)
InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 001 Device 003: ID 0461:4e8d Primax Electronics, Ltd HP USB Optical Mouse
Bus 001 Device 002: ID 04f3:0103 Elan Microelectronics Corp. ActiveJet K-2024
Multimedia Keyboard
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic
root=UUID=7e20054f-50f7-4011-8c9c-516960719274 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2024-04-05 (0 days ago)
dmi.bios.date: 02/06/2023
dmi.bios.release: 5.26
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: ADLNV104
dmi.board.asset.tag: Default string
dmi.board.name: MINI S
dmi.board.vendor: AZW
dmi.board.version: 10
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrADLNV104:bd02/06/2023:br5.26:svnAZW:pnMINIS:pvrDefaultstring:rvnAZW:rnMINIS:rvr10:cvnDefaultstring:ct3:cvrDefaultstring:sku01:
dmi.product.family: Default string
dmi.product.name: MINI S
dmi.product.sku: 01
dmi.product.version: Default string
dmi.sys.vendor: AZW
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.8
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: nautilus (Ubuntu)
Importance: Undecided
Status: New
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug corruption mantic ubuntu
** Attachment added: "A screenshot showing the corruption"
https://bugs.launchpad.net/bugs/2060291/+attachment/5761662/+files/Screenshot%20from%202024-04-05%2003-47-22.png
** Also affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2060291
Title:
Horizonral line artifact/ghosting when scaling windows to a certain
width
Status in nautilus package in Ubuntu:
New
Status in xorg package in Ubuntu:
New
Bug description:
When scaling some windows in some programs down horizontal lines
appear that seem to be part of the texture memory somewhere else on
the screen.
This only occurs in some programs like nautilus and gedit, but not in
others like terminal or Firefox.
It did however occur when I opened the dialog in firefox to attach the
screen capture.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 5 03:44:15 2024
DistUpgraded: 2024-04-04 22:25:39,405 DEBUG icon theme changed, re-reading
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
nvidia/470.239.06,
[Touch-packages] [Bug 2060273] [NEW] secondary users are not listed in polkit graphical prompt
Public bug reported: Tested with 124-1ubuntu1 on noble 1. Create 3 users on the machine: - sudo-user1, part of sudo group - sudo-user2, part of sudo group - normal-user, not part of the sudo group 2. Login with normal-user 3. Try to execute pkexec or any other command prompting for polkit -> only sudo-user1 password auth is proposed, before, we had a listbox to select all eligible user 4. Remove sudo-user1 5. Try pkexec again: -> now sudo-user2 is proposed, showing that the configuration for this user is correct. It seems that only the first "admin" of the machine is taken into account. However, as normal-user, I may not have sudo-user1 around, but only sudo-user2. ** Affects: policykit-1 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/2060273 Title: secondary users are not listed in polkit graphical prompt Status in policykit-1 package in Ubuntu: New Bug description: Tested with 124-1ubuntu1 on noble 1. Create 3 users on the machine: - sudo-user1, part of sudo group - sudo-user2, part of sudo group - normal-user, not part of the sudo group 2. Login with normal-user 3. Try to execute pkexec or any other command prompting for polkit -> only sudo-user1 password auth is proposed, before, we had a listbox to select all eligible user 4. Remove sudo-user1 5. Try pkexec again: -> now sudo-user2 is proposed, showing that the configuration for this user is correct. It seems that only the first "admin" of the machine is taken into account. However, as normal-user, I may not have sudo-user1 around, but only sudo-user2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2060273/+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 2060291] Re: Horizonral line artifact/ghosting when scaling windows to a certain width
Problem did not occur on prior Ubuntu 20.04. I upgraded because the
intel graphics acceleration for Intel N95 chipset was not supported.
Thus the system used software rendering.
--
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/2060291
Title:
Horizonral line artifact/ghosting when scaling windows to a certain
width
Status in nautilus package in Ubuntu:
New
Status in xorg package in Ubuntu:
New
Bug description:
When scaling some windows in some programs down horizontal lines
appear that seem to be part of the texture memory somewhere else on
the screen.
This only occurs in some programs like nautilus and gedit, but not in
others like terminal or Firefox.
It did however occur when I opened the dialog in firefox to attach the
screen capture.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 5 03:44:15 2024
DistUpgraded: 2024-04-04 22:25:39,405 DEBUG icon theme changed, re-reading
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
nvidia/470.239.06, 5.15.0-101-generic, x86_64: installed
nvidia/470.239.06, 6.5.0-26-generic, x86_64: installed
GraphicsCard:
Intel Corporation Alder Lake-N [UHD Graphics] [8086:46d2] (prog-if 00 [VGA
controller])
Subsystem: Intel Corporation Alder Lake-N [UHD Graphics] [8086:7270]
InstallationDate: Installed on 2022-12-15 (477 days ago)
InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64
(20210915)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 001 Device 003: ID 0461:4e8d Primax Electronics, Ltd HP USB Optical Mouse
Bus 001 Device 002: ID 04f3:0103 Elan Microelectronics Corp. ActiveJet
K-2024 Multimedia Keyboard
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic
root=UUID=7e20054f-50f7-4011-8c9c-516960719274 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2024-04-05 (0 days ago)
dmi.bios.date: 02/06/2023
dmi.bios.release: 5.26
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: ADLNV104
dmi.board.asset.tag: Default string
dmi.board.name: MINI S
dmi.board.vendor: AZW
dmi.board.version: 10
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrADLNV104:bd02/06/2023:br5.26:svnAZW:pnMINIS:pvrDefaultstring:rvnAZW:rnMINIS:rvr10:cvnDefaultstring:ct3:cvrDefaultstring:sku01:
dmi.product.family: Default string
dmi.product.name: MINI S
dmi.product.sku: 01
dmi.product.version: Default string
dmi.sys.vendor: AZW
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.8
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/nautilus/+bug/2060291/+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 2055718] Re: timezone changed unexpectedly from EST to America/Adak or America/Indiana/Indianapolis
Debdiff for mantic. ** Changed in: tzdata (Ubuntu) Status: Triaged => Fix Committed ** Patch added: "tzdata_2024a-0ubuntu0.23.10.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2055718/+attachment/5761746/+files/tzdata_2024a-0ubuntu0.23.10.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2055718 Title: timezone changed unexpectedly from EST to America/Adak or America/Indiana/Indianapolis Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Mantic: New Bug description: A user reported this regression on https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739: UPDATE: I don't think it's a regression anymore, see comment #5 """ Hello. After automatic upgrade of tzdata from 2023c-0ubuntu0.22.04.2 to 2024a-0ubuntu0.22.04 the previously set EST time zone was automatically changed to "America/Adak" or "America/Indiana/Indianapolis" on all our servers (50+). Look like a bug in tzdata configure script. """ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2055718/+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 1965328] Re: transient scope could not be started error in bionic lxd container
-- 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/1965328 Title: transient scope could not be started error in bionic lxd container Status in snapd: New Status in systemd package in Ubuntu: Invalid Status in systemd source package in Bionic: New Bug description: On my impish development host machine I tend to use lxd containers to support snap building and other tasks targeting different releases. Today I came to use a bionic container as per usual and found that I could not invoke any snap applications. I installed hello-world as the most simple test of running a snap app: ``` ubuntu@b:~$ hello-world internal error, please report: running "hello-world" failed: transient scope could not be started, job /org/freedesktop/systemd1/job/44 finished with result failed ``` I made sure the container had up to date packages in it (apt & snaps) and rebooted it. But the problem persisted. I then created a second container and installed hello-world in it and again the problem was reproducible. At the time of producing the following attachments I had not attempted to reboot the host. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1965328/+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 2055718] Re: timezone changed unexpectedly from EST to America/Adak or America/Indiana/Indianapolis
The debdiff for focal is similar to the debdiff for jammy. Only debian/test_timezone_conversions needed some modification to work with the older Python version. ** Patch added: "tzdata_2024a-0ubuntu0.20.04.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2055718/+attachment/5761753/+files/tzdata_2024a-0ubuntu0.20.04.1.debdiff ** Description changed: + [ Impact ] + + On every tzdata package upgrade the configured timezone might be updated + to an incorrect one. + + I enhanced debian/test_timezone_conversions to detect those + inconsistencies and fixed everything that was found by this check. The + SRUs contain a backport of the script from noble. + + [ Test Plan ] + + debian/test_timezone_conversions is enhanced to check the timezone + conversions for consistency to prevent such kind of issues in the + future. debian/test_timezone_conversions is run during built and as + autopkgtest. + + In addition, manual check can be done. The following test should stay at + `EST` (and not update to `America/Adak`): + + ``` + ln -sf /usr/share/zoneinfo/EST /etc/localtime + dpkg-reconfigure --frontend noninteractive tzdata + ls -alh /etc/localtime + ``` + + `US/East-Indiana` should be updated to `America/Indiana/Indianapolis` + and not to `America/Adak`: + + ``` + ln -sf /usr/share/zoneinfo/US/East-Indiana /etc/localtime + dpkg-reconfigure --frontend noninteractive tzdata + ``` + + `America/Louisville` should be updated to `America/Kentucky/Louisville` + and not to `America/Adak`: + + ``` + ln -sf /usr/share/zoneinfo/America/Louisville /etc/localtime + dpkg-reconfigure --frontend noninteractive tzdata + ``` + + [ Other Info ] + + The autopkgtest for chrony is flaky on jammy and newer (see bug + #2002910). + + [ Regression potential ] + + The patch ziguard.awk-Move-link-to-link-feature-from-vanguard-to- + ma.patch moves the link to link feature from vanguard to main dataform + to produce correct symlinks. This results in symlinks that can point to + symlinks. The zic from glibc that we use can handle that, but there + might be other parsers that read /usr/share/zoneinfo/tzdata.zi directly + and could fail to handle symlinks to symlinks. + + [ Original report ] + A user reported this regression on https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739: UPDATE: I don't think it's a regression anymore, see comment #5 """ Hello. After automatic upgrade of tzdata from 2023c-0ubuntu0.22.04.2 to 2024a-0ubuntu0.22.04 the previously set EST time zone was automatically changed to "America/Adak" or "America/Indiana/Indianapolis" on all our servers (50+). Look like a bug in tzdata configure script. """ -- 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/2055718 Title: timezone changed unexpectedly from EST to America/Adak or America/Indiana/Indianapolis Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Mantic: New Bug description: [ Impact ] On every tzdata package upgrade the configured timezone might be updated to an incorrect one. I enhanced debian/test_timezone_conversions to detect those inconsistencies and fixed everything that was found by this check. The SRUs contain a backport of the script from noble. [ Test Plan ] debian/test_timezone_conversions is enhanced to check the timezone conversions for consistency to prevent such kind of issues in the future. debian/test_timezone_conversions is run during built and as autopkgtest. In addition, manual check can be done. The following test should stay at `EST` (and not update to `America/Adak`): ``` ln -sf /usr/share/zoneinfo/EST /etc/localtime dpkg-reconfigure --frontend noninteractive tzdata ls -alh /etc/localtime ``` `US/East-Indiana` should be updated to `America/Indiana/Indianapolis` and not to `America/Adak`: ``` ln -sf /usr/share/zoneinfo/US/East-Indiana /etc/localtime dpkg-reconfigure --frontend noninteractive tzdata ``` `America/Louisville` should be updated to `America/Kentucky/Louisville` and not to `America/Adak`: ``` ln -sf /usr/share/zoneinfo/America/Louisville /etc/localtime dpkg-reconfigure --frontend noninteractive tzdata ``` [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). [ Regression potential ] The patch ziguard.awk-Move-link-to-link-feature-from-vanguard-to- ma.patch moves the link to link feature from vanguard to main dataform to produce correct symlinks. This results in symlinks that can point to symlinks. The zic from glibc that we use can handle that, but there might be other parsers that read /usr/share/zoneinfo/tzdata.zi directly and could fail to handle symlinks to symlinks. [ Original
[Touch-packages] [Bug 2060331] [NEW] add-apt-repository --list not returning any deb822 repositories
Public bug reported: Recreating the following bug report (#2052851) with a new title per Jeremy Bícha's (jbicha) request: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2052851 --- On Ubuntu 23.10: * When adding a PPA, 'add-apt-repository' will add the repository in the new deb822 format as a '.sources' file in '/etc/apt/sources.list.d' * However, 'add-apt-repository --list' cannot see/understand the new '.sources' file For example, with the flacon ppa (https://launchpad.net/~flacon/+archive/ubuntu/ppa): 1. 'sudo add-apt-repository ppa:flacon/ppa' adds the flacon repo as '/etc/apt/sources.list.d/flacon-ubuntu-ppa-mantic.sources' 2. apt can install and update from the new repo, as expected. you can also remove the repo, as expected, by running 'sudo add-apt-repository --remove ppa:flacon/ppa' 3. However, 'add-apt-repository --list' does not list the repo as it should. GUI package managers such as Muon and Synaptic also do not see the new repo. It makes working with packages frustrating, and unfortunately, per Julian Andres Klode (juliank), there seems to be no plan to fix the broken 'software-properties-common' any time soon. See here: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2033949 Also see related issues: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761 https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2037210 https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2036288 https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042791.html ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2060331 Title: add-apt-repository --list not returning any deb822 repositories Status in software-properties package in Ubuntu: New Bug description: Recreating the following bug report (#2052851) with a new title per Jeremy Bícha's (jbicha) request: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2052851 --- On Ubuntu 23.10: * When adding a PPA, 'add-apt-repository' will add the repository in the new deb822 format as a '.sources' file in '/etc/apt/sources.list.d' * However, 'add-apt-repository --list' cannot see/understand the new '.sources' file For example, with the flacon ppa (https://launchpad.net/~flacon/+archive/ubuntu/ppa): 1. 'sudo add-apt-repository ppa:flacon/ppa' adds the flacon repo as '/etc/apt/sources.list.d/flacon-ubuntu-ppa-mantic.sources' 2. apt can install and update from the new repo, as expected. you can also remove the repo, as expected, by running 'sudo add-apt-repository --remove ppa:flacon/ppa' 3. However, 'add-apt-repository --list' does not list the repo as it should. GUI package managers such as Muon and Synaptic also do not see the new repo. It makes working with packages frustrating, and unfortunately, per Julian Andres Klode (juliank), there seems to be no plan to fix the broken 'software-properties-common' any time soon. See here: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2033949 Also see related issues: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761 https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2037210 https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2036288 https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042791.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2060331/+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 2055718] Re: timezone changed unexpectedly from EST to America/Adak or America/Indiana/Indianapolis
Here is the debdiff for jammy. debian/test_timezone_conversions found even more inconsistencies in jammy: ERROR: Following 4 timezones cannot be selected, but are not converted: America/Fort_Wayne America/Indianapolis America/Knox_IN America/Louisville 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 ERROR: Following 1 timezones are converted, but they do not match their symlink targets: US/Indiana-Starke ** Patch added: "tzdata_2024a-0ubuntu0.22.04.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2055718/+attachment/5761748/+files/tzdata_2024a-0ubuntu0.22.04.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2055718 Title: timezone changed unexpectedly from EST to America/Adak or America/Indiana/Indianapolis Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Mantic: New Bug description: A user reported this regression on https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739: UPDATE: I don't think it's a regression anymore, see comment #5 """ Hello. After automatic upgrade of tzdata from 2023c-0ubuntu0.22.04.2 to 2024a-0ubuntu0.22.04 the previously set EST time zone was automatically changed to "America/Adak" or "America/Indiana/Indianapolis" on all our servers (50+). Look like a bug in tzdata configure script. """ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2055718/+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
