[Touch-packages] [Bug 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.
You mention snap update in the title. What specific snap are you referring to, Chromium, Cups or Snapd? The output of "snap changes" could be useful. If you roll it back with "snap revert ", does it work again? > Launching chrome from menu shortcut that is managed by the snap works > and it using this location /snap/bin/chromium > > Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome > Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Indeed, you should let the snap manage the shortcut, as the one you used in 20.04 invokes the binary directly, out of the snap sandbox. Do you get issues with that in place? Please attach the output of snap connections chromium snap connections cups ** Also affects: cups (Ubuntu) Importance: Undecided Status: New ** Changed in: cups (Ubuntu) Status: New => Incomplete ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2026200 Title: Snap update broke launching and printing on 20.04 Ubuntu. Status in chromium-browser package in Ubuntu: Incomplete Status in cups package in Ubuntu: Incomplete Bug description: Two deployed ubuntu images, 20.04 and 22.04. Both images are fully updated. Issue appears to only impact 20.04. chrome snap version 2529 Launching chrome from menu shortcut that is managed by the snap works and it using this location /snap/bin/chromium Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Try and print from the browser, print dialog in chrome does not list any system printers, only shows PDF. Doing the same on 22.04 image, I get a list of printers. CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No such file or directory" I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 100% failure rate on 20.04. I get this error when running chrome from cli from this path on 20.04 /snap/chromium/current/usr/lib/chromium-browser which points to 2529 snap image. /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922414] Re: ssh-agent fails to start (has_option: command not found)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in Light Display Manager: New Status in gdm3 package in Ubuntu: Fix Released Status in lightdm package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1922414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922414] Re: ssh-agent fails to start (has_option: command not found)
** Also affects: lightdm (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/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in Light Display Manager: New Status in gdm3 package in Ubuntu: Fix Released Status in lightdm package in Ubuntu: New Status in xorg package in Ubuntu: Confirmed Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1922414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2026230] Re: error when setting up after upgrading
** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2026230 Title: error when setting up after upgrading Status in network-manager package in Ubuntu: New Bug description: I received an error from apport about a programme not working. I collected the data to submit. Hope this helps. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: network-manager 1.42.6-2ubuntu1 Uname: Linux 6.2.0-24-generic x86_64 Architecture: amd64 Date: Wed Jul 5 23:11:14 2023 ExecutablePath: /usr/sbin/NetworkManager ExecutableTimestamp: 1687429583 ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) Signal: 6 SourcePackage: network-manager UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2026230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2026230] Re: error when setting up after upgrading
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2026230 Title: error when setting up after upgrading Status in network-manager package in Ubuntu: New Bug description: I received an error from apport about a programme not working. I collected the data to submit. Hope this helps. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: network-manager 1.42.6-2ubuntu1 Uname: Linux 6.2.0-24-generic x86_64 Architecture: amd64 Date: Wed Jul 5 23:11:14 2023 ExecutablePath: /usr/sbin/NetworkManager ExecutableTimestamp: 1687429583 ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) Signal: 6 SourcePackage: network-manager UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2026230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2026227] [NEW] Backport 4.0 ABI for AppArmor 3 in mantic
Public bug reported: To support the use of AppArmor policies that specify features like userns, add the new 4.0 ABI from upstream https://gitlab.com/apparmor/apparmor/-/merge_requests/1061. Note this should not be enabled by default (as the existing AppArmor profiles have not been updated to account for this) but it will allow easier testing of profiles that want to support this new ABI. Also note this ABI is identical to that provided by the kernel in mantic and lunar currently: # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Mantic Minotaur (development branch) Release:23.10 Codename: mantic # uname -a Linux sec-mantic-amd64 6.3.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Jun 8 16:02:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux # diff /etc/apparmor.d/abi/4.0 <(aa-features-abi -x) # md5sum /etc/apparmor.d/abi/4.0 <(aa-features-abi -x) f17b0a97806d733b5b884d8a1c2fea37 /etc/apparmor.d/abi/4.0 f17b0a97806d733b5b884d8a1c2fea37 /dev/fd/63 ** Affects: apparmor (Ubuntu) Importance: Undecided Assignee: Alex Murray (alexmurray) Status: New ** Affects: apparmor (Ubuntu Mantic) Importance: Undecided Assignee: Alex Murray (alexmurray) Status: New ** Changed in: apparmor (Ubuntu) Assignee: (unassigned) => Alex Murray (alexmurray) ** Also affects: apparmor (Ubuntu Mantic) Importance: Undecided Assignee: Alex Murray (alexmurray) Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2026227 Title: Backport 4.0 ABI for AppArmor 3 in mantic Status in apparmor package in Ubuntu: New Status in apparmor source package in Mantic: New Bug description: To support the use of AppArmor policies that specify features like userns, add the new 4.0 ABI from upstream https://gitlab.com/apparmor/apparmor/-/merge_requests/1061. Note this should not be enabled by default (as the existing AppArmor profiles have not been updated to account for this) but it will allow easier testing of profiles that want to support this new ABI. Also note this ABI is identical to that provided by the kernel in mantic and lunar currently: # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Mantic Minotaur (development branch) Release: 23.10 Codename: mantic # uname -a Linux sec-mantic-amd64 6.3.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Jun 8 16:02:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux # diff /etc/apparmor.d/abi/4.0 <(aa-features-abi -x) # md5sum /etc/apparmor.d/abi/4.0 <(aa-features-abi -x) f17b0a97806d733b5b884d8a1c2fea37 /etc/apparmor.d/abi/4.0 f17b0a97806d733b5b884d8a1c2fea37 /dev/fd/63 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2026227/+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 2023771] Re: package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned erro
I also got this error when I tried to upgrade. Upon trying 'apt reinstall linux-firmware' I get the following: # apt reinstall linux-firmware The following packages will be REINSTALLED: linux-firmware 0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 3 not upgraded. Need to get 0 B of archives. After unpacking 0 B will be used. E: Internal Error, No file name for linux-firmware:amd64 I am running on a relatively new GIGABYTE B650M AORUS ELITE AX AM5 motherboard with an AMD 7900 CPU and am configured using a bootable ZFS configuration that was updating fine, previously. 'dpkg -l' shows the offending package version info as: iF linux-firmware 20220329.git681281e4-0ubuntu3.14 all Firmware for Linux kernel drivers -- 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/2023771 Title: package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Unable to upgrade my pc due to this any others bugs. E: /usr/share/initramfs-tools/hooks/zz-busybox-initramfs failed with return 1. update-initramfs: failed for /boot/initrd.img-5.19.0-32-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abi1571 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Wed Jun 14 17:31:44 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-06-14 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Dell Inc. Inspiron 5570 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=9279cb9d-233d-4c02-84d4-2c665027abca ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 SourcePackage: initramfs-tools Title: package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2023 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0GHXK4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/06/2023:br1.14:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0GHXK4:rvrA00:cvnDellInc.:ct10:cvr:sku0810: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2023771/+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 2025982] Re: Warning 'failed to get driver name for fd 0' fails gtk tests
** Changed in: mesa (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2025982 Title: Warning 'failed to get driver name for fd 0' fails gtk tests Status in Mesa: New Status in mesa package in Ubuntu: Fix Committed Status in mesa package in Debian: New Bug description: The new version displays that warning which makes the gtk autopkgtest red Upstream https://gitlab.freedesktop.org/mesa/mesa/-/issues/9199 Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039922 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2025982/+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 1839156] Re: TCP/IP connection stuck when called from UDEV rule
udev restricts this sort of thing for security reasons, so this is
working as expected.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
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/1839156
Title:
TCP/IP connection stuck when called from UDEV rule
Status in systemd package in Ubuntu:
Invalid
Bug description:
It seems that in Eoan there is a lock/any other issue preventing
particular system calls to be executed by the triggered action
handler. I have an action executing wget when USB-serial adapter is
plugged:
SUBSYSTEM=="tty", ACTION=="add", ATTRS{idVendor}=="1a86",
ATTRS{idProduct}=="7523", MODE="0666", RUN+="/usr/bin/wget -v --method=POST
http://127.0.0.1:4000/udev_trigger/add;
This action works perfectly in a prior versions - but in Eoan Ermine it hangs
for ~30s and fails on a timeout. Analysis with strace shows that execution is
stuck on connect() syscall - until it returns with ETIMEDOUT.
Same Wget command, being run from a command line, works perfectly.
The issue doesn't seem to be related to a particular IP
(localhost/remote) and/or the status of a listener process - execution
hangs also when listener is not running and port is free.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1839156/+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 1958590] Re: systemd-shutdown hangs on "Failed to finalize DM devices, ignoring"
Sorry this was not looked at sooner. Is this still using the latest systemd on your re-installed system? ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1958590 Title: systemd-shutdown hangs on "Failed to finalize DM devices, ignoring" Status in systemd package in Ubuntu: Incomplete Bug description: I'm using KDE neon, ubuntu 20.04. This started happening after I upgraded to the 245.4-4ubuntu3.15 version. After reaching targer power-off, it hangs on: systemd-shutdown[1]: Failed to finalize DM devices, ignoring And it doesn't shut down, I have to force it by long-pressing the power button. EDIT: This happens if / is in a luks partition, regardless of the luks version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1958590/+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 1961418] Re: snap failed to run with '/usr/bin/snap wait system seed.loaded'
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
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/1961418
Title:
snap failed to run with '/usr/bin/snap wait system seed.loaded'
Status in snapd package in Ubuntu:
Won't Fix
Status in systemd package in Ubuntu:
Invalid
Bug description:
I tried to enable livepatch without any success. ([Bug 1960689] )
support suggested me report a bug for snapd.
root@plis231v:~# sudo ua enable livepatch
One moment, checking your subscription first
Unexpected error(s) occurred.
For more details, see the log: /var/log/ubuntu-advantage.log
To file a bug run: ubuntu-bug ubuntu-advantage-tools
>> logs
22-02-11 22:27:00,410 - util.py:(429) [DEBUG]: Reading file:
/var/lib/ubuntu-advantage/notices.json
2022-02-11 22:27:00,410 - util.py:(700) [DEBUG]: Writing file:
/var/lib/ubuntu-advantage/notices.json
2022-02-11 22:27:00,411 - cli.py:(1499) [ERROR]: Unhandled exception,
please file a bug
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1458, in
wrapper
return func(*args, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1544, in main
return args.action(args, cfg=cfg)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 166, in new_f
return f(*args, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 189, in new_f
return f(args, cfg=cfg, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 147, in new_f
retval = f(*args, cfg=cfg, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 888, in
action_enable
ent_ret, reason = entitlement.enable()
File "/usr/lib/python3/dist-packages/uaclient/entitlements/base.py", line
197, in enable
ret = self._perform_enable(silent=silent)
File "/usr/lib/python3/dist-packages/uaclient/entitlements/livepatch.py",
line 160, in _perform_ena
[snap.SNAP_CMD, "wait", "system", "seed.loaded"], capture=True
File "/usr/lib/python3/dist-packages/uaclient/util.py", line 662, in subp
out, err = _subp(args, rcs, capture, timeout, env=env)
File "/usr/lib/python3/dist-packages/uaclient/util.py", line 619, in _subp
stderr=err.decode("utf-8"),
uaclient.util.ProcessExecutionError: Failed running command '/usr/bin/snap
wait system seed.loaded' [sage: error: cannot communicate with server: Get
http://localhost/v2/snaps/system/conf?keys=seed.load /run/snapd.socket:
connect: no such file or directory
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-advantage-tools 27.4.1~16.04.1
ProcVersionSignature: Ubuntu 4.15.0-167.175~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-167-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.30+esm3
Architecture: amd64
Date: Fri Feb 11 23:01:08 2022
InstallationDate: Installed on 2010-12-02 (4089 days ago)
InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64
(20100816.2)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-advantage-tools
UpgradeStatus: Upgraded to xenial on 2017-01-21 (1847 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961418/+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 1969365] Re: focal: backport kexec fallback patch
The patch for this is indeed present in Jammy and newer. I don't currently see a strong enough reason to SRU this to Focal, but if you or someone else thinks it's important, feel free to explain here. ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1969365 Title: focal: backport kexec fallback patch Status in systemd package in Ubuntu: Fix Released Bug description: It would be great if focal's systemd could have https://github.com/systemd/systemd/commit/71180f8e57f8fbb55978b00a13990c79093ff7b3 backported to it. [Impact] We have observed that kexec'ing to another kernel will fail as the drive containing the `kexec` binary has been unmounted by the time systemd attempts to do so, indicated in the console: Starting Reboot via kexec... [ 163.960938] shutdown[1]: (sd-kexec) failed with exit status 1. [ 163.963463] reboot: Restarting system [Test Plan] 1) Launch a 20.04 instance 2) `apt-get install kexec-tools` 3) In `/boot`, filling in whatever needed in your environment: kexec -l vmlinuz --initrd initrd.img --append '' 4) `reboot` (I have reproduced this in a single-disk VM, so I assume it reproduces ~everywhere: if not, `apt-get remove kexec-tools` before the `reboot` could be used to emulate the unmounting.) [Where problems could occur] Users could inadvertently be relying on the current behaviour: if they have configured their systems to kexec, they currently will be rebooting normally, and this patch would cause them to start actually kexec'ing. [Other info] We're currently maintaining a systemd tree with only this patch added to focal's tree: this patch has received a bunch of testing from us in focal. This patch landed in v246, so it's already present in supported releases later than focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969365/+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 1981983] Re: systemd-network changes MAC of interfaces belonging to a bond
Can you share the generated networkd files from /run/systemd/network? Also, 99-default.link is not the correct place to change these values - you should set MACAddressPolicy in specific link files, e.g. 10-eth0.link. I am not sure off the top of my head of netplan.io has a config option that maps to this .link option. ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1981983 Title: systemd-network changes MAC of interfaces belonging to a bond Status in systemd package in Ubuntu: Incomplete Bug description: 1) Description:Ubuntu 20.04.4 LTS Release:20.04 2) systemd: Installed: 245.4-4ubuntu3.15 3) What you expected to happen Interfaces in the bond keep their real "hardware" mac addresses. bond0 takes MAC from first interface of the bond when not explicitly set. 4) What happened instead I wanted to change from ifupdown back to netplan/systemd-networkd. Thus I installed netplan.io, delete /etc/network/interfaces, purged ifupdown and wrote an yaml for netplan. My Yaml looks as following network: version: 2 renderer: networkd ethernets: em1: dhcp4: false dhcp6: false optional: true em3: dhcp4: false dhcp6: false optional: true bonds: bond-new: interfaces: [em1, em3] dhcp4: true dhcp6: false accept-ra: true link-local: [ ipv6 ] parameters: mode: 802.3ad mii-monitor-interval: 1 Netplan applies it without errors. Also, this represents the (working) configuration I had with ifupdown. Now when I apply this config, bond0 gets the following (random?) MAC address: c2:ba:f9:db:xx:xx (xx for privacy) Also, both interfaces em1 and em3 belonging to that bond get the same MAC address. This actual "hardware" MAC address is obviously another. Strangely, all interfaces get the same MAC address: # ip a | grep c2:ba:f9:db:ed:4b -B 1 2: em1: mtu 1500 qdisc mq master bond-new state UP group default qlen 1000 link/ether c2:ba:f9:db:xx:xx brd ff:ff:ff:ff:ff:ff 4: em3: mtu 1500 qdisc mq master bond-new state UP group default qlen 1000 link/ether c2:ba:f9:db:xx:xx brd ff:ff:ff:ff:ff:ff -- 8: bond-new: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether c2:ba:f9:db:xx:xx brd ff:ff:ff:ff:ff:ff Additionally every device added to this bond will get the same MAC address, e. g. em2: 3: em2: mtu 1500 qdisc mq master bond-new state DOWN group default qlen 1000 link/ether c2:ba:f9:db:xx:xx brd ff:ff:ff:ff:ff:ff I already set MACAddressPolicy=none in /lib/systemd/network/99-default.link, but it does no change this behavior. Removing an interface from the bond, does not revert the MAC. When I purge netplan.io and install ifupdown, the real MAC address is set to interfaces again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981983/+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 1982563] Re: sbat-distro should be set
Looking at a recent build log, this seems to be set already in newer releases https://launchpadlibrarian.net/656923986/buildlog_ubuntu-lunar- amd64.systemd_252.5-2ubuntu3_BUILDING.txt.gz. Notably, it does not appear to be set in Jammy. Is this needed there? ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1982563 Title: sbat-distro should be set Status in systemd package in Ubuntu: Fix Released Bug description: -Dsbat-distro should be set so that the systemd efi stub gets a .sbat section. This is needed for secure boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982563/+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 1988023] Re: Could not switch uppercase/lowercase by using keyboard of laptop
Re-assigning since it sounds like this is not a systemd issue. ** Package changed: systemd (Ubuntu) => linux (Ubuntu) -- 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/1988023 Title: Could not switch uppercase/lowercase by using keyboard of laptop Status in linux package in Ubuntu: New Bug description: 1. Fresh install ubuntu server 22.04.1 on Lenovo server. 2. Install console-data package 3. Get locale status: # localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 4. Fail to ist and set keymap with command "localectl", but the kmap file can be found in the /usr/share./keymaps/ #localectl list-keymaps Failed to read list of keymaps: No such file or directory # localectl set-keymap us Failed to set keymap: Keymap us is not installed. # find /usr/ -name us.kmap.gz /usr/share/keymaps/i386/qwerty/us.kmap.gz 5. It need type "CapsLock" twice when want to switch uppercase/lowercase by using keyboard of laptop, not once, the other keyboard has no issue about it. # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". Please help check why need type twice "CapsLock" for switching uppercase/lowercase and how to fix it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) MachineType: Lenovo ThinkSystem SR630 V2 Package: systemd 249.11-0ubuntu3.4 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: jammy uec-images Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE118I-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z70CTO1WW dmi.board.vendor: Lenovo dmi.board.version: 05 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE118I-1.30:bd04/21/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR630V2:pvr05:rvnLenovo:rn7Z70CTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7Z70CTO1WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR630 V2 dmi.product.sku: 7Z70CTO1WW dmi.product.version: 05 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988023/+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 1990740] Re: laptop wouldn't wake from sleep
Is this still an issue for you? If so, what release are you running now? We would also need some logs to investigate further. This sounds like a kernel issue rather than systemd, but it would be helpful if you provided some logs. Specifically: 1. Enable debug logging in systemd-logind: $ mkdir -p /etc/systemd/system/systemd-logind.service.d/ $ cat > /etc/systemd/system/systemd-logind.service.d/debug.conf << EOF [Service] Environment=SYSTEMD_LOG_LEVEL=debug EOF 2. Reboot for this to take effect properly. 3. Try to reproduce the issue. 4. Attach logs from this boot: $ journalctl -u systemd-logind.service -b > logind-logs.txt $ journalctl -t kernel -b > kernel-logs.txt ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1990740 Title: laptop wouldn't wake from sleep Status in systemd package in Ubuntu: Incomplete Bug description: Shortly after upgrading from Jammy to Kinetic my laptop went to sleep after I was idle for 20 minutes, as it is configured to do. The lid was closed when the laptop went to sleep. I was unable to wake up the laptop. Opening the lid back up should have caused it to wake up but did not. Pressing the power button should have caused it to wake up but did not. Both the LED on the lid and the power button light were cycling on and off as they do when the laptop is sleeping. I had to hold down the power button for five seconds to power off the laptop completely and then power it back on to get it to come back up. Never saw this behavior even once with Jammy. After rebooting and logging in, I put the laptop to sleep by selecting Suspend from the menu, and after _that_ it woke up immediately when I pushed the power button. I am not sure yet how reproducible this is, but I thought that even a single incidence of something like this was worth reporting. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: systemd 251.4-1ubuntu6 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Sep 24 17:29:50 2022 InstallationDate: Installed on 2019-08-16 (1135 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20KHCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago) dmi.bios.date: 04/20/2019 dmi.bios.release: 1.38 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET63W (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrN23ET63W(1.38):bd04/20/2019:br1.38:efr1.13:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KH_BU_Think_FM_ThinkPadX1Carbon6th: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO modified.conffile..etc.systemd.logind.conf: [modified] mtime.conffile..etc.systemd.logind.conf: 2022-09-24T15:20:56.088250 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990740/+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 2026199] Re: Please merge 3.137 into mantic
** Description changed: The upstream version 3.137 should be merged into mantic. The current version is 3.134ubuntu1. + * PPA for review: https://launchpad.net/~mateus-morais/+archive/ubuntu/adduser-merge-lp2026199 + * Git rebase of Ubuntu delta available at: https://code.launchpad.net/~mateus-morais/ubuntu/+source/adduser/+git/adduser-devel/+ref/ubuntu/devel + Note: this is a tracking bug - - PPA for review: https://launchpad.net/~mateus- - morais/+archive/ubuntu/adduser-merge-lp2026199 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/2026199 Title: Please merge 3.137 into mantic Status in adduser package in Ubuntu: In Progress Bug description: The upstream version 3.137 should be merged into mantic. The current version is 3.134ubuntu1. * PPA for review: https://launchpad.net/~mateus-morais/+archive/ubuntu/adduser-merge-lp2026199 * Git rebase of Ubuntu delta available at: https://code.launchpad.net/~mateus-morais/ubuntu/+source/adduser/+git/adduser-devel/+ref/ubuntu/devel Note: this is a tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/2026199/+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 2026199] Re: Please merge 3.137 into mantic
** Description changed: The upstream version 3.137 should be merged into mantic. The current version is 3.134ubuntu1. Note: this is a tracking bug + + PPA for review: https://launchpad.net/~mateus- + morais/+archive/ubuntu/adduser-merge-lp2026199 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/2026199 Title: Please merge 3.137 into mantic Status in adduser package in Ubuntu: In Progress Bug description: The upstream version 3.137 should be merged into mantic. The current version is 3.134ubuntu1. Note: this is a tracking bug PPA for review: https://launchpad.net/~mateus- morais/+archive/ubuntu/adduser-merge-lp2026199 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/2026199/+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 2025563] Re: System can not shutdown if system has multiple VROC RAID arrays
Hi Cyrus, thanks for the patch! As per the SRU guidelines in https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template, regarding the "[ Where problems could occur ]" section, > * This must '''never''' be "None" or "Low", or entirely an argument as to why your upload is low risk. Describing where problems could occur and how they would manifest is a nice way to show to the SRU team that we did consider possible unwanted outcomes for the SRU and that we'd be ready to address them in case they do occur. It also helps people testing the SRU, guiding them on what to look for when checking for regressions. -- 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/2025563 Title: System can not shutdown if system has multiple VROC RAID arrays Status in OEM Priority Project: In Progress Status in systemd package in Ubuntu: Confirmed Bug description: [ Impact ] The system can not shutdown if the system has multiple VROC RAID arrays. Intel has fixed it in systemd v251 [1]. Need to cherry-pick the commit to ubuntu-jammy systemd 249.11-0ubuntu3.9. [1] The commit fixes the issue: commit 3a3b022d2cc112803ea7b9beea98bbcad110368a Author: Mariusz Tkaczyk Date: Tue Mar 29 12:49:54 2022 +0200 shutdown: get only active md arrays. Current md_list_get() implementation filters all block devices, started from "md*". This is ambiguous because list could contain: - partitions created upon md device (mdXpY) - external metadata container- specific type of md array. For partitions there is no issue, because they aren't handle STOP_ARRAY ioctl sent later. It generates misleading errors only. Second case is more problematic because containers are not locked in kernel. They are stopped even if container member array is active. For that reason reboot or shutdown flow could be blocked because metadata manager cannot be restarted after switch root on shutdown. Add filters to remove partitions and containers from md_list. Partitions can be excluded by DEVTYPE. Containers are determined by MD_LEVEL property, we are excluding all with "container" value. Signed-off-by: Mariusz Tkaczyk [ Test Plan ] 1. Build two VROC RAID. One RAID 0 for System volume, another RAID 10 for Data volume. 2. Install system on System volume. 3. Update systemd. 4. Reboot the system. 5. Verify if the system can reboot. [ Where problems could occur ] Low, upstream fix. [ Scope ] Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2025563/+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 2025655] Re: Please merge 1.9.13p3-3 into mantic
Thanks, Danilo. I am removing ubuntu-sponsors to avoid duplication in the sponsoring queue. Your MP is already being tracked there. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/2025655 Title: Please merge 1.9.13p3-3 into mantic Status in sudo package in Ubuntu: New Bug description: PPA: https://launchpad.net/~danilogondolfo/+archive/ubuntu/sudo2 Autopkgtests https://autopkgtest.ubuntu.com/results/autopkgtest- mantic-danilogondolfo- sudo2/mantic/s390x/s/sudo/20230705_144943_c8ec0@/log.gz This merge includes a workaround for a problem with autopkgtest affecting s390x for a long while. See https://git.launchpad.net/~danilogondolfo/ubuntu/+source/sudo/commit/?id=ad1796726eb71d17d4ef983c96735092b522a3dd See the history of tests on s390x https://autopkgtest.ubuntu.com/packages/sudo/mantic/s390x It's not reproducible locally though. Sleeping for a couple of seconds between the start of the ldap server and the first ldapmodify command seems to fix the problem reliably for us. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2025655/+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 2026199] [NEW] Please merge 3.137 into mantic
Public bug reported: The upstream version 3.137 should be merged into mantic. The current version is 3.134ubuntu1. Note: this is a tracking bug ** Affects: adduser (Ubuntu) Importance: Undecided Assignee: Mateus Rodrigues de Morais (mateus-morais) Status: In Progress ** Changed in: adduser (Ubuntu) Assignee: (unassigned) => Mateus Rodrigues de Morais (mateus-morais) ** Changed in: adduser (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/2026199 Title: Please merge 3.137 into mantic Status in adduser package in Ubuntu: In Progress Bug description: The upstream version 3.137 should be merged into mantic. The current version is 3.134ubuntu1. Note: this is a tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/2026199/+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 2025980] Re: can not configure keyboard and mouse separately
also FYI: solaar detects my mouse properly -- 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/2025980 Title: can not configure keyboard and mouse separately Status in upower package in Ubuntu: New Bug description: I have Logitech wireless keyboard and wireless mouse, coonnected to the same Unifying receiver. battery level of these devices is reported correctly, but both are listed in power settings as a keyboard, making me a bit confusing, which device is ran out of power, when I get 'low keyboard battery' message. trying to set correct device type via modaliases for mouse changes nothing, but when I change my keyboard to 'a mouse', I get two mice in power settings! (and no keyboard) thus, I can not configure these devices separately, to get 1 keyboard and 1 mouse, but only can see 2 keyboards or 2 mice. ubuntu unity 23.04 UPower client version 0.99.20 UPower daemon version 0.99.20 output of 'upower -d': Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_0 native-path: hidpp_battery_0 model:K800 serial: b2-69-6e-91 power supply: no updated: Wed 05 Jul 2023 10:57:43 (2 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: discharging warning-level: low battery-level: low percentage: 10% (should be ignored) icon-name: 'battery-caution-symbolic' Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_1 native-path: hidpp_battery_1 model:Performance MX serial: 04-81-33-3a power supply: no updated: Wed 05 Jul 2023 10:57:37 (8 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: discharging warning-level: none battery-level: high percentage: 70% (should be ignored) icon-name: 'battery-good-symbolic' Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: no updated: Wed 05 Jul 2023 10:48:37 (548 seconds ago) has history: no has statistics: no unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' Daemon: daemon-version: 0.99.20 on-battery: no lid-is-closed: no lid-is-present: no critical-action: HybridSleep modaliases in 61-input-id-local.hwdb: id-input:modalias:input:b0003v046Dp101Ae0111* ID_INPUT_MOUSE=1 ID_INPUT=1 id-input:modalias:input:b0003v046Dp2010e0111* ID_INPUT_KEYBOARD=1 ID_INPUT=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/2025980/+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 2025980] Re: can not setup keyboard and mouse separately
** Description changed: - I have Logitech wireless keyboard and wireless mouse, coonnected to the same Unifying receiver. - battery level of these devices is reported correctly, but both are listed in power settings as a keyboard, making me a bit confusing, which device is run out of power, when I get 'low keyboard battery' message. + I have Logitech wireless keyboard and wireless mouse, coonnected to the same Unifying receiver. + battery level of these devices is reported correctly, but both are listed in power settings as a keyboard, making me a bit confusing, which device is ran out of power, when I get 'low keyboard battery' message. - trying to set correct device type via modaliases for mouse changes nothing, but when I change my keyboard to 'a mouse', I get two mice in power settings! - thus, I can not setup these devices separately, to get 1 keyboard and 1 mouse, but only 2 keyboards or 2 mice. + trying to set correct device type via modaliases for mouse changes nothing, but when I change my keyboard to 'a mouse', I get two mice in power settings! + thus, I can not setup these devices separately, to get 1 keyboard and 1 mouse, but only 2 keyboards or 2 mice. ubuntu unity 23.04 UPower client version 0.99.20 UPower daemon version 0.99.20 - - output of 'upower -d': + output of 'upower -d': Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_0 - native-path: hidpp_battery_0 - model:K800 - serial: b2-69-6e-91 - power supply: no - updated: Wed 05 Jul 2023 10:57:43 (2 seconds ago) - has history: yes - has statistics: yes - keyboard - present: yes - rechargeable:yes - state: discharging - warning-level: low - battery-level: low - percentage: 10% (should be ignored) - icon-name: 'battery-caution-symbolic' + native-path: hidpp_battery_0 + model:K800 + serial: b2-69-6e-91 + power supply: no + updated: Wed 05 Jul 2023 10:57:43 (2 seconds ago) + has history: yes + has statistics: yes + keyboard + present: yes + rechargeable:yes + state: discharging + warning-level: low + battery-level: low + percentage: 10% (should be ignored) + icon-name: 'battery-caution-symbolic' Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_1 - native-path: hidpp_battery_1 - model:Performance MX - serial: 04-81-33-3a - power supply: no - updated: Wed 05 Jul 2023 10:57:37 (8 seconds ago) - has history: yes - has statistics: yes - keyboard - present: yes - rechargeable:yes - state: discharging - warning-level: none - battery-level: high - percentage: 70% (should be ignored) - icon-name: 'battery-good-symbolic' + native-path: hidpp_battery_1 + model:Performance MX + serial: 04-81-33-3a + power supply: no + updated: Wed 05 Jul 2023 10:57:37 (8 seconds ago) + has history: yes + has statistics: yes + keyboard + present: yes + rechargeable:yes + state: discharging + warning-level: none + battery-level: high + percentage: 70% (should be ignored) + icon-name: 'battery-good-symbolic' Device: /org/freedesktop/UPower/devices/DisplayDevice - power supply: no - updated: Wed 05 Jul 2023 10:48:37 (548 seconds ago) - has history: no - has statistics: no - unknown - warning-level: none - percentage: 0% - icon-name: 'battery-missing-symbolic' + power supply: no + updated: Wed 05 Jul 2023 10:48:37 (548 seconds ago) + has history: no + has statistics: no + unknown + warning-level: none + percentage: 0% + icon-name: 'battery-missing-symbolic' Daemon: - daemon-version: 0.99.20 - on-battery: no - lid-is-closed: no - lid-is-present: no - critical-action: HybridSleep - + daemon-version: 0.99.20 + on-battery: no + lid-is-closed: no + lid-is-present: no + critical-action: HybridSleep modaliases in 61-input-id-local.hwdb: id-input:modalias:input:b0003v046Dp101Ae0111* - ID_INPUT_MOUSE=1 - ID_INPUT=1 + ID_INPUT_MOUSE=1 + ID_INPUT=1 id-input:modalias:input:b0003v046Dp2010e0111* - ID_INPUT_KEYBOARD=1 - ID_INPUT=1 + ID_INPUT_KEYBOARD=1 + ID_INPUT=1 ** Summary changed: - can not setup keyboard and mouse separately + can not configure keyboard and mouse
[Touch-packages] [Bug 1974056] Comment bridged from LTC Bugzilla
--- Comment From wint...@de.ibm.com 2023-07-05 12:00 EDT--- Is this a new testcase, or did it work before? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1974056 Title: iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless- bitwise_0 fails on s390x Status in iptables: Unknown Status in Ubuntu on IBM z Systems: In Progress Status in iptables package in Ubuntu: New Bug description: In Ubuntu, we execute the full iptables shell testcases across all architectures. They seem to all pass everywhere, however iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless- bitwise_0 is currently failing on s390x like so: command17FAIL stderr: W: [FAILED] ././testcases/nft- only/0009-needless-bitwise_0: expected 0 but got 1 i wonder if there is some endian bug, as this is currently Ubuntu's only big-endian architecture. this can be reproduced with: pull-lp-source iptables cd iptables-1.8.7/ chmod +x ./iptables/tests/shell/testcases/iptables/0007-zero-counters_0 cd iptables/tests/shell sudo ./run-tests.sh --host To manage notifications about this bug go to: https://bugs.launchpad.net/iptables/+bug/1974056/+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 2007913] Re: HDMI Output sound has disappeared after Ubuntu update
I see that this looks like a kernel problem. One of my computers was without sound in the last 5 months, so I had to use a small screen laptop to watch movies or listen audio, but I lost patience in the process. Is there any GUI centric Linux distro, which fixes this problem? -- 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/2007913 Title: HDMI Output sound has disappeared after Ubuntu update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After months using the HDMI output without problems, it has stopped working after a system update two days ago. HDMI output is not listed in the list of available output devices. Same computer works with this sound output perfectly when booting with Windows or an older installation of Ubuntu (18.04). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 21 08:12:58 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-30 (296 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M01EWR120 dmi.board.asset.tag: OEM Default string000 dmi.board.name: OEM Default string000 dmi.board.vendor: OEM Default string000 dmi.board.version: OEM Default string000 dmi.chassis.asset.tag: OEM Default string000 dmi.chassis.type: 10 dmi.chassis.vendor: OEM Default string000 dmi.chassis.version: OEM Default string000 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000: dmi.product.family: OEM Default string000 dmi.product.name: CoreBox dmi.product.sku: OEM Default string000 dmi.product.version: OEM Default string000 dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+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 2004649] Re: Regression bug with mesa backport and ogre rendering
could you check if the backport from lunar in jammy-proposed fixes this? ** Also affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu Jammy) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2004649 Title: Regression bug with mesa backport and ogre rendering Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Jammy: Incomplete Bug description: We found a breaking change with https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1991761 when running an application that relies on ogre 1.9 for rendering inside a Docker container based on the ubuntu:jammy image. We could confirm that the upgrade causing this was as follows, because the issue goes away when downgrading versions: [UPGRADE] libegl-mesa0:amd64 22.0.1-1ubuntu2 -> 22.2.5-0ubuntu0.1~22.04.1 [UPGRADE] libgbm-dev:amd64 22.0.1-1ubuntu2 -> 22.2.5-0ubuntu0.1~22.04.1 [UPGRADE] libgbm1:amd64 22.0.1-1ubuntu2 -> 22.2.5-0ubuntu0.1~22.04.1 [UPGRADE] libgl1-mesa-dri:amd64 22.0.1-1ubuntu2 -> 22.2.5-0ubuntu0.1~22.04.1 [UPGRADE] libglapi-mesa:amd64 22.0.1-1ubuntu2 -> 22.2.5-0ubuntu0.1~22.04.1 [UPGRADE] libglx-mesa0:amd64 22.0.1-1ubuntu2 -> 22.2.5-0ubuntu0.1~22.04.1 For completeness, the full stack trace is: Stack trace (most recent call last) in thread 18237: #25 Object "[0x]", at 0x, in #24 Object "/lib/x86_64-linux-gnu/libc.so.6", at 0x7f2ba75089ff, in #23 Object "/lib/x86_64-linux-gnu/libc.so.6", at 0x7f2ba7476b42, in #22 Object "/lib/x86_64-linux-gnu/libstdc++.so.6", at 0x7f2ba3a4d2b2, in #21 Object "/usr/lib/x86_64-linux-gnu/ign-gazebo-6/plugins/libignition-gazebo-sensors-system.so", at 0x7f2b6456b2bf, in ignition::gazebo::v6::systems::SensorsPrivate::RenderThread() #20 Object "/usr/lib/x86_64-linux-gnu/ign-gazebo-6/plugins/libignition-gazebo-sensors-system.so", at 0x7f2b6456aba6, in ignition::gazebo::v6::systems::SensorsPrivate::RunOnce() #19 Object "/opt/underlay_ws/install/lib/libignition-sensors6.so.6", at 0x7f2b76db113e, in ignition::sensors::v6::Manager::RunOnce(std::chrono::duration > const&, bool) #18 Object "/opt/underlay_ws/install/lib/libignition-sensors6.so.6", at 0x7f2b76db95b5, in ignition::sensors::v6::Sensor::Update(std::chrono::duration > const&, bool) #17 Object "/opt/underlay_ws/install/lib/libignition-sensors6-rgbd_camera.so.6", at 0x7f2b6436a020, in ignition::sensors::v6::RgbdCameraSensor::Update(std::chrono::duration > const&) #16 Object "/opt/underlay_ws/install/lib/libignition-sensors6-rendering.so.6", at 0x7f2b64282a6d, in ignition::sensors::v6::RenderingSensor::Render() #15 Object "/usr/lib/x86_64-linux-gnu/ign-rendering-6/engine-plugins/libignition-rendering-ogre.so", at 0x7f2b5c6adc85, in ignition::rendering::v6::OgreDepthCamera::PostRender() #14 Object "/usr/lib/x86_64-linux-gnu/ign-rendering-6/engine-plugins/libignition-rendering-ogre.so", at 0x7f2b5c71d743, in ignition::rendering::v6::OgreRenderTexture::Buffer(float*) #13 Object "/lib/x86_64-linux-gnu/libOgreMain.so.1.9.0", at 0x7f2b5c32c90a, in Ogre::RenderTexture::copyContentsToMemory(Ogre::PixelBox const&, Ogre::RenderTarget::FrameBuffer) #12 Object "/usr/lib/x86_64-linux-gnu/OGRE-1.9.0/RenderSystem_GL.so", at 0x7f2aeac67a85, in Ogre::GLTextureBuffer::download(Ogre::PixelBox const&) #11 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b26225cdd, in #10 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b262246ae, in #9 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b262244b0, in #8 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b26082975, in #7 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b26224a86, in #6 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b260800a8, in #5 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b260a3f19, in #4 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b26c77f37, in #3 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b25fa88b6, in #2 Object "/lib/x86_64-linux-gnu/libc.so.6", at 0x7f2ba740a7f2, in abort #1 Object "/lib/x86_64-linux-gnu/libc.so.6", at 0x7f2ba7424475, in raise #0 Object "/lib/x86_64-linux-gnu/libc.so.6", at 0x7f2ba7478a7c, in pthread_kill Aborted (Signal sent by tkill() 17739 0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2004649/+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 2008159] Re: `shutdown --show` says suspend is scheduled for (null) after system has suspended and been woken back up
I tested this on Lunar and saw the same behavior. ** Changed in: systemd (Ubuntu) Status: New => Confirmed ** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2008159 Title: `shutdown --show` says suspend is scheduled for (null) after system has suspended and been woken back up Status in systemd package in Ubuntu: Confirmed Bug description: If you suspend from GNOME, wake your machine back up, and then once it's totally back up, run `shutdown --show` as root, it says "syspend is scheduled for (null)". It shouldn't say (null) there, which I suppose is a different bug, but the bug I'm concerned about is that the message doesn't clear when the system is woken back up after the suspend. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: systemd-sysv 252.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Feb 22 21:56:45 2023 InstallationDate: Installed on 2019-08-16 (1286 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: systemd UpgradeStatus: Upgraded to lunar on 2022-11-24 (90 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2008159/+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 2019212] Re: Backport packages for 22.04.3 HWE stack
** Description changed: [Impact] The graphics HWE stack from lunar needs to be backported to jammy for 22.04.3 mesa - new major release (23.0.4) + mesa-amber + - a minor update from upstream mesa (21.3.7 -> 21.3.9), though there were no + changes to the classic dri drivers + - drops old i915 driver, while mesa provides the more modern i915_dri.so called + i915g + - fixes installation (LP: #2006744) and image build + [Test case] + mesa: Install the new mesa on various hw configs, check that everything still works like before or better. + + mesa-amber: + no need to test anything besides checking that the packages can be installed next to mesa and image build is fixed [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 23.0.x in order to minimize the chance for those. ** Changed in: mesa-amber (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2019212 Title: Backport packages for 22.04.3 HWE stack Status in mesa package in Ubuntu: Invalid Status in mesa-amber package in Ubuntu: Invalid Status in mesa source package in Jammy: Fix Committed Status in mesa-amber source package in Jammy: New Bug description: [Impact] The graphics HWE stack from lunar needs to be backported to jammy for 22.04.3 mesa - new major release (23.0.4) mesa-amber - a minor update from upstream mesa (21.3.7 -> 21.3.9), though there were no changes to the classic dri drivers - drops old i915 driver, while mesa provides the more modern i915_dri.so called i915g - fixes installation (LP: #2006744) and image build [Test case] mesa: Install the new mesa on various hw configs, check that everything still works like before or better. mesa-amber: no need to test anything besides checking that the packages can be installed next to mesa and image build is fixed [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 23.0.x in order to minimize the chance for those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2019212/+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 2025980] Re: can not setup keyboard and mouse separately
probably it's due to the single path for both devices?.. udevadm info /dev/input/event3 P: /devices/pci:00/:00:14.0/usb3/3-6/3-6:1.2/0003:046D:C52B.0004/0003:046D:2010.0007/input/input18/event3 M: event3 R: 3 U: input D: c 13:67 N: input/event3 L: 0 S: input/by-id/usb-Logitech_USB_Receiver-if02-event-kbd S: input/by-path/pci-:00:14.0-usb-0:6:1.2-event-kbd E: DEVPATH=/devices/pci:00/:00:14.0/usb3/3-6/3-6:1.2/0003:046D:C52B.0004/0003:046D:2010.0007/input/input18/event3 E: DEVNAME=/dev/input/event3 E: MAJOR=13 E: MINOR=67 E: SUBSYSTEM=input E: USEC_INITIALIZED=4130304 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_INPUT_KEYBOARD=1 E: ID_BUS=usb E: ID_MODEL=USB_Receiver E: ID_MODEL_ENC=USB\x20Receiver E: ID_MODEL_ID=c52b E: ID_SERIAL=Logitech_USB_Receiver E: ID_VENDOR=Logitech E: ID_VENDOR_ENC=Logitech E: ID_VENDOR_ID=046d E: ID_REVISION=1210 E: ID_TYPE=hid E: ID_USB_MODEL=USB_Receiver E: ID_USB_MODEL_ENC=USB\x20Receiver E: ID_USB_MODEL_ID=c52b E: ID_USB_SERIAL=Logitech_USB_Receiver E: ID_USB_VENDOR=Logitech E: ID_USB_VENDOR_ENC=Logitech E: ID_USB_VENDOR_ID=046d E: ID_USB_REVISION=1210 E: ID_USB_TYPE=hid E: ID_USB_INTERFACES=:030101:030102:03: E: ID_USB_INTERFACE_NUM=02 E: ID_USB_DRIVER=usbhid E: ID_PATH=pci-:00:14.0-usb-0:6:1.2 E: ID_PATH_TAG=pci-_00_14_0-usb-0_6_1_2 E: XKBMODEL=pc105 E: XKBLAYOUT=us,rud E: XKBVARIANT=dvorak, E: XKBOPTIONS=grp:shift_caps_toggle E: KMAP=/etc/console/boottime.kmap.gz E: BACKSPACE=guess E: LIBINPUT_DEVICE_GROUP=3/46d/2010:usb-:00:14.0-6 E: DEVLINKS=/dev/input/by-id/usb-Logitech_USB_Receiver-if02-event-kbd /dev/input/by-path/pci-:00:14.0-usb-0:6:1.2-event-kbd E: TAGS=:power-switch: E: CURRENT_TAGS=:power-switch: udevadm info /dev/input/event4 P: /devices/pci:00/:00:14.0/usb3/3-6/3-6:1.2/0003:046D:C52B.0004/0003:046D:101A.0008/input/input19/event4 M: event4 R: 4 U: input D: c 13:68 N: input/event4 L: 0 S: input/by-path/pci-:00:14.0-usb-0:6:1.2-event-mouse S: input/by-id/usb-Logitech_USB_Receiver-if02-event-mouse E: DEVPATH=/devices/pci:00/:00:14.0/usb3/3-6/3-6:1.2/0003:046D:C52B.0004/0003:046D:101A.0008/input/input19/event4 E: DEVNAME=/dev/input/event4 E: MAJOR=13 E: MINOR=68 E: SUBSYSTEM=input E: USEC_INITIALIZED=4122172 E: ID_INPUT=1 E: ID_INPUT_MOUSE=1 E: ID_BUS=usb E: ID_MODEL=USB_Receiver E: ID_MODEL_ENC=USB\x20Receiver E: ID_MODEL_ID=c52b E: ID_SERIAL=Logitech_USB_Receiver E: ID_VENDOR=Logitech E: ID_VENDOR_ENC=Logitech E: ID_VENDOR_ID=046d E: ID_REVISION=1210 E: ID_TYPE=hid E: ID_USB_MODEL=USB_Receiver E: ID_USB_MODEL_ENC=USB\x20Receiver E: ID_USB_MODEL_ID=c52b E: ID_USB_SERIAL=Logitech_USB_Receiver E: ID_USB_VENDOR=Logitech E: ID_USB_VENDOR_ENC=Logitech E: ID_USB_VENDOR_ID=046d E: ID_USB_REVISION=1210 E: ID_USB_TYPE=hid E: ID_USB_INTERFACES=:030101:030102:03: E: ID_USB_INTERFACE_NUM=02 E: ID_USB_DRIVER=usbhid E: ID_PATH=pci-:00:14.0-usb-0:6:1.2 E: ID_PATH_TAG=pci-_00_14_0-usb-0_6_1_2 E: MOUSE_DPI=1000@166 E: LIBINPUT_DEVICE_GROUP=3/46d/101a:usb-:00:14.0-6 E: DEVLINKS=/dev/input/by-path/pci-:00:14.0-usb-0:6:1.2-event-mouse /dev/input/by-id/usb-Logitech_USB_Receiver-if02-event-mouse -- 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/2025980 Title: can not setup keyboard and mouse separately Status in upower package in Ubuntu: New Bug description: I have Logitech wireless keyboard and wireless mouse, coonnected to the same Unifying receiver. battery level of these devices is reported correctly, but both are listed in power settings as a keyboard, making me a bit confusing, which device is run out of power, when I get 'low keyboard battery' message. trying to set correct device type via modaliases for mouse changes nothing, but when I change my keyboard to 'a mouse', I get two mice in power settings! thus, I can not setup these devices separately, to get 1 keyboard and 1 mouse, but only 2 keyboards or 2 mice. ubuntu unity 23.04 UPower client version 0.99.20 UPower daemon version 0.99.20 output of 'upower -d': Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_0 native-path: hidpp_battery_0 model:K800 serial: b2-69-6e-91 power supply: no updated: Wed 05 Jul 2023 10:57:43 (2 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: discharging warning-level: low battery-level: low percentage: 10% (should be ignored) icon-name: 'battery-caution-symbolic' Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_1 native-path: hidpp_battery_1 model:Performance MX serial: 04-81-33-3a power supply: no updated:
[Touch-packages] [Bug 2019212] Re: Backport packages for 22.04.3 HWE stack
** Also affects: mesa-amber (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2019212 Title: Backport packages for 22.04.3 HWE stack Status in mesa package in Ubuntu: Invalid Status in mesa-amber package in Ubuntu: New Status in mesa source package in Jammy: Fix Committed Status in mesa-amber source package in Jammy: New Bug description: [Impact] The graphics HWE stack from lunar needs to be backported to jammy for 22.04.3 mesa - new major release (23.0.4) [Test case] Install the new mesa on various hw configs, check that everything still works like before or better. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 23.0.x in order to minimize the chance for those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2019212/+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 2023401] Re: [Dell XPS 17 9700] Upon shutdown, shutdown process doesn't complete and the computer stays on
** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/2023401 Title: [Dell XPS 17 9700] Upon shutdown, shutdown process doesn't complete and the computer stays on Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: When I want to shutdown my computer, very often since last Ubuntu version, the process seems not to go to the end, and the computer never shuts down. I used not to notice it, physically close my laptop and put it back in my bag, then hours later find it very hot and with fans going at full speed. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 9 16:35:50 2023 DistUpgraded: 2023-04-21 10:53:49,032 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f] Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f] InstallationDate: Installed on 2021-04-12 (787 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 17 9700 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to lunar on 2023-04-21 (49 days ago) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.24.0 dmi.board.name: 0PV91W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.24.0:bd03/14/2023:br1.24:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0PV91W:rvrA00:cvnDellInc.:ct10:cvr:sku098F: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023401/+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 1983100] Re: dotnet build intermittently crashes with segfault on Ubuntu 18.04
** Also affects: ubuntu-pro
Importance: Undecided
Status: New
** Changed in: ubuntu-pro
Assignee: (unassigned) => Tom Moyer (tom-tom)
** Also affects: ubuntu-pro/18.04
Importance: Undecided
Assignee: Tom Moyer (tom-tom)
Status: New
** Changed in: ubuntu-pro/18.04
Importance: Undecided => Medium
** Changed in: ubuntu-pro/18.04
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1983100
Title:
dotnet build intermittently crashes with segfault on Ubuntu 18.04
Status in Ubuntu Pro:
In Progress
Status in Ubuntu Pro 18.04 series:
In Progress
Status in openssl package in Ubuntu:
Fix Released
Status in openssl source package in Bionic:
Incomplete
Bug description:
[Impact]
Bionic's OpenSSL 1.1.1 package
(https://launchpad.net/ubuntu/bionic/+source/openssl) is the only
version of openssl 1.1.1 on any distro that we've encountered that
does not have support for the OPENSSL_NO_ATEXIT functionality from
1.1.1b (openssl/openssl@c2b3db2).
The threading model in .NET has the possibility that background
threads are still running when exit() is called, which can cause
SIGSEGV if a background thread interacts with OpenSSL after/while it
has unloaded. For that reason, we always initialize OpenSSL 1.1.1 with
the OPENSSL_NO_ATEXIT flag (which, of all the distros we run on only
has no effect on Bionic).
We feel that the stability of applications on Ubuntu 18.04 would be
improved if the functionality of OPENSSL_NO_ATEXIT was merged into the
bionic openssl 1.1.1 package, even if the constant isn't published
into the header for the dev package.
Context:
https://github.com/dotnet/runtime/issues/48411#issuecomment-1178405101
[Test Plan]
The described behavior can be reproduced by passing the
OPENSSL_NO_ATEXIT to the OPENSSL_init_ssl() call. The application will
terminate with a SEGFAULT. More concretely, a minimal reproducer is:
#include
#include
#include
#ifndef OPENSSL_INIT_NO_ATEXIT
#define OPENSSL_INIT_NO_ATEXIT 0x0008L
#endif
static void print_error_string()
{
printf("print_error_string:\n");
printf("ERR_reason_error_string(0) => %s\n", ERR_reason_error_string(0));
}
int main(int argc, char* argv[])
{
// register this handler first, so it runs last.
atexit(print_error_string);
OPENSSL_init_ssl(
OPENSSL_INIT_ADD_ALL_CIPHERS |
OPENSSL_INIT_ADD_ALL_DIGESTS |
OPENSSL_INIT_LOAD_CONFIG |
OPENSSL_INIT_NO_ATEXIT |
OPENSSL_INIT_LOAD_CRYPTO_STRINGS |
OPENSSL_INIT_LOAD_SSL_STRINGS,
NULL);
print_error_string();
return 0;
}
Building
$ sudo apt install libssl-dev
$ gcc test.c -lssl -lcrypto
$ ./a.out
print_error_string:
ERR_reason_error_string(0) => (null)
print_error_string:
Segmentation fault (core dumped)
[Other Info]
All of these patches are included in upstream release 1.1.1b
- lp1983100-0001-Fix-shlibloadtest-to-properly-execute-the-dso_ref-te.patch
Fixes the shlibloadtest that was updated as part of #0005
- lp1983100-0002-Implement-OPENSSL_INIT_NO_ATEXIT.patch
Patch adds the OPENSSL_INIT_NO_ATEXIT option
- lp1983100-0003-Don-t-link-shlibloadtest-against-libcrypto.patch
Additional fixes for shlibloadtest
- lp1983100-0004-Fix-rpath-related-Linux-test_shlibload-failure.patch
Additional fixes for shlibloadtest
- lp1983100-0005-Test-atexit-handlers.patch
Adds test for OPENSSL_INIT_NO_ATEXIT option and updates the shlibloadtest
- lp1983100-0006-Introduce-a-no-pinshared-option.patch
This patch includes tests to ensure that if OPENSSL_INIT_NO_ATEXIT is not
defined then the atexit() handler is run
- lp1983100-0007-Support-_onexit-in-preference-to-atexit-on-Windows.patch
This patch ensures that atexit() is only called when on non-Windows systems
as Windows uses _onexit() during library unloading
All seven patches are required to ensure the correct logic and
operation of the OPENSSL_INIT_NO_ATEXIT option.
[Where problems could occur]
The patches adds an option to the OPENSSL_init_crypto() function to
disable the default behavior of calling of a cleanup function on
application exit. The patch also includes a few bug fixes around
various initializations that were supposed to happen once when running
threaded but were not.
These changes have the potential for regressions and it is conceivable
that they lead to incorrect behavior. However, I have also backported
and included all new testing functions in the hope that the changed
behavior will get appropriate testing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-pro/+bug/1983100/+subscriptions
--
Mailing list:
[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
** Changed in: keepalived (Ubuntu Xenial)
Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro)
** Changed in: keepalived (Ubuntu Bionic)
Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro)
** No longer affects: keepalived (Ubuntu Xenial)
** Changed in: keepalived (Ubuntu Focal)
Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro)
--
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/1815101
Title:
[master] Restarting systemd-networkd breaks keepalived, heartbeat,
corosync, pacemaker (interface aliases are restarted)
Status in netplan:
Triaged
Status in heartbeat package in Ubuntu:
Won't Fix
Status in keepalived package in Ubuntu:
In Progress
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
Won't Fix
Status in keepalived source package in Bionic:
Confirmed
Status in systemd source package in Bionic:
Fix Released
Status in systemd source package in Disco:
Won't Fix
Status in systemd source package in Eoan:
Fix Released
Status in keepalived source package in Focal:
Confirmed
Status in systemd source package in Focal:
Fix Released
Bug description:
[impact]
- ALL related HA software has a small problem if interfaces are being
managed by systemd-networkd: nic restarts/reconfigs are always going
to wipe all interfaces aliases when HA software is not expecting it to
(no coordination between them.
- keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is
smarter in this case because it has a service monitor that will
restart the virtual IP resource, in affected node & nic, before
considering a real failure, but other HA service might consider a real
failure when it is not.
[test case]
- comment #14 is a full test case: to have 3 node pacemaker, in that
example, and cause a networkd service restart: it will trigger a
failure for the virtual IP resource monitor.
- other example is given in the original description for keepalived.
both suffer from the same issue (and other HA softwares as well).
[regression potential]
- this backports KeepConfiguration parameter, which adds some
significant complexity to networkd's configuration and behavior, which
could lead to regressions in correctly configuring the network at
networkd start, or incorrectly maintaining configuration at networkd
restart, or losing network state at networkd stop.
- Any regressions are most likely to occur during networkd start,
restart, or stop, and most likely to involve missing or incorrect ip
address(es).
- the change is based in upstream patches adding the exact feature we
needed to fix this issue & it will be integrated with a netplan change
to add the needed stanza to systemd nic configuration file
(KeepConfiguration=)
[other info]
original description:
---
Configure netplan for interfaces, for example (a working config with
IP addresses obfuscated)
network:
ethernets:
eth0:
addresses: [192.168.0.5/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth2:
addresses:
- 12.13.14.18/29
- 12.13.14.19/29
gateway4: 12.13.14.17
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth3:
addresses: [10.22.11.6/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth4:
addresses: [10.22.14.6/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth7:
addresses: [9.5.17.34/29]
dhcp4: false
optional: true
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
version: 2
Configure keepalived (again, a working config with IP addresses
obfuscated)
global_defs # Block id
{
notification_email {
sysadm...@blah.com
}
notification_email_from keepali...@system3.hq.blah.com
smtp_server 10.22.11.7 # IP
smtp_connect_timeout 30 # integer, seconds
router_id system3 # string identifying the machine,
# (doesn't have to be hostname).
vrrp_mcast_group4 224.0.0.18 #
[Touch-packages] [Bug 2025655] Re: Please merge 1.9.13p3-3 into mantic
** Description changed: - [placeholder] + + PPA: https://launchpad.net/~danilogondolfo/+archive/ubuntu/sudo2 + + Autopkgtests https://autopkgtest.ubuntu.com/results/autopkgtest-mantic- + danilogondolfo-sudo2/mantic/s390x/s/sudo/20230705_144943_c8ec0@/log.gz + + This merge includes a workaround for a problem with autopkgtest + affecting s390x for a long while. See + https://git.launchpad.net/~danilogondolfo/ubuntu/+source/sudo/commit/?id=ad1796726eb71d17d4ef983c96735092b522a3dd + + See the history of tests on s390x + https://autopkgtest.ubuntu.com/packages/sudo/mantic/s390x + + It's not reproducible locally though. Sleeping for a couple of seconds + between the start of the ldap server and the first ldapmodify command + seems to fix the problem reliably for us. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/2025655 Title: Please merge 1.9.13p3-3 into mantic Status in sudo package in Ubuntu: New Bug description: PPA: https://launchpad.net/~danilogondolfo/+archive/ubuntu/sudo2 Autopkgtests https://autopkgtest.ubuntu.com/results/autopkgtest- mantic-danilogondolfo- sudo2/mantic/s390x/s/sudo/20230705_144943_c8ec0@/log.gz This merge includes a workaround for a problem with autopkgtest affecting s390x for a long while. See https://git.launchpad.net/~danilogondolfo/ubuntu/+source/sudo/commit/?id=ad1796726eb71d17d4ef983c96735092b522a3dd See the history of tests on s390x https://autopkgtest.ubuntu.com/packages/sudo/mantic/s390x It's not reproducible locally though. Sleeping for a couple of seconds between the start of the ldap server and the first ldapmodify command seems to fix the problem reliably for us. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2025655/+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 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10
@Federico: Thanks for testing and reporting that observation! I can't reproduce it (on mantic), though. Dead keys work as expected for me, also with the keyboard layout you mentioned. Are you sure that the issue is related to the proposed ibus version? Does the issue go away if you downgrade to the released version? Are you testing on lunar or mantic? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1996652 Title: Nautilus search is slow and jumbles keyboard input on 22.10 Status in ibus: New Status in ibus package in Ubuntu: Confirmed Bug description: Since my upgrade to 22.10, I've found the search box in Nautilus (files) essentially unusable. It is notably sluggish to launch and browse in general. But most detrimental to the usability is this: The characters do not appear in real time as I type. When they do appear, they are sometimes jumbled or in reverse (consistently reproducible). As I type in the file search box, the circular cursor spins intermittently, then the UI catches up and it's not what I typed. For example, I just typed "umbrella" into the search box, and Nautilus searched for: "umballer" Off-the-cuff test #2, searched for "Ubuntu" and I ended up with "Ubunut" ... you can't make this up. :-) Test #3, typed Launchpad, ended up with a search for "Laudaphcn". Keyboard input everywhere else on the system is otherwise normal and snappy. No pun intended, really. FWIW Nautilus files preferences are as default (Search in subfolders, Show thumbnails, File count == This computer only). $ apt-cache policy nautilus nautilus: Installed: 1:43.0-1ubuntu1 Candidate: 1:43.0-1ubuntu1 Version table: *** 1:43.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status $ uname -r 5.19.0-23-generic $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 $ snap list Name Version RevTracking Publisher Notes bare 1.0 5 latest/stable canonical✓ base core 16-2.57.2 13886 latest/stable canonical✓ core core18 20221027 2620 latest/stable canonical✓ base core20 20221027 1695 latest/stable canonical✓ base gnome-3-34-18040+git.3556cb3 77 latest/stable/… canonical✓ - gnome-3-38-20040+git.6f39565 119latest/stable canonical✓ - google-cloud-sdk 409.0.0 298latest/stable google-cloud-sdk✓ classic gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - snap-store 41.3-64-g512c0ff 599latest/stable/… canonical✓ - snapd 2.57.417336 latest/stable canonical✓ snapd snapd-desktop-integration 0.1 14 latest/stable/… canonical✓ - Side question: Since this system has transitioned across several upgrades from 20.04 to 22.10, do I really need all of these core* and gnome* snaps? To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1996652/+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 1990755] Re: HYPHEN character escaped in filenames with BACKSLASH
Is this actually causing you problems somewhere? Or do you just disagree with this concept? Please see https://www.freedesktop.org/software/systemd/man/systemd.unit.html#String%20Escaping%20for%20Inclusion%20in%20Unit%20Names for an explanation of this naming. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1990755 Title: HYPHEN character escaped in filenames with BACKSLASH Status in systemd package in Ubuntu: Invalid Bug description: current Ubuntu 22.04 LTS shows oot@prod:~# find / -xdev -name '*\\x*' /usr/lib/systemd/system/system-systemd\x2dcryptsetup.slice /etc/systemd/system/snap-gtk\x2dcommon\x2dthemes-1535.mount /etc/systemd/system/snap-gnome\x2d3\x2d38\x2d2004-115.mount /etc/systemd/system/multi-user.target.wants/snap-gtk\x2dcommon\x2dthemes-1535.mount /etc/systemd/system/multi-user.target.wants/snap-gnome\x2d3\x2d38\x2d2004-115.mount /etc/systemd/system/multi-user.target.wants/snap-snapd\x2ddesktop\x2dintegration-14.mount /etc/systemd/system/multi-user.target.wants/snap-snap\x2dstore-592.mount /etc/systemd/system/multi-user.target.wants/var-snap-firefox-common-host\x2dhunspell.mount /etc/systemd/system/multi-user.target.wants/snap-snap\x2dstore-599.mount /etc/systemd/system/snap-snapd\x2ddesktop\x2dintegration-14.mount /etc/systemd/system/snap-snap\x2dstore-592.mount /etc/systemd/system/var-snap-firefox-common-host\x2dhunspell.mount /etc/systemd/system/snap-snap\x2dstore-599.mount /etc/systemd/system/default.target.wants/snap-gnome\x2d3\x2d38\x2d2004-115.mount /etc/systemd/system/default.target.wants/snap-snap\x2dstore-592.mount /etc/systemd/system/default.target.wants/var-snap-firefox-common-host\x2dhunspell.mount /etc/systemd/system/default.target.wants/snap-snap\x2dstore-599.mount HYPHEN is normal ASCII character or escaped by "\x2d" HYPHEN needs no escape , but the BACKSLASH is making troubles. no BACKSLASH allowed in filenames and directory names. seems to be a bad habit of "systemd" and "snap" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990755/+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 2025666] Re: Please merge 1.225-1 into mantic
** Changed in: netcat-openbsd (Ubuntu) Assignee: Benjamin Drung (bdrung) => (unassigned) ** Changed in: netcat-openbsd (Ubuntu) Importance: Undecided => Wishlist ** Changed in: netcat-openbsd (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu. https://bugs.launchpad.net/bugs/2025666 Title: Please merge 1.225-1 into mantic Status in netcat-openbsd package in Ubuntu: Fix Committed Bug description: PPA https://launchpad.net/~danilogondolfo/+archive/ubuntu/netcat- openbsd Autopkgtest https://autopkgtest.ubuntu.com/results/autopkgtest-mantic- danilogondolfo-netcat-openbsd/mantic/amd64/n/netcat- openbsd/20230703_202110_fccf3@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/2025666/+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 2025666] Re: Please merge 1.225-1 into mantic
Thanks. Uploaded netcat-openbsd 1.225-1ubuntu1. ** Changed in: netcat-openbsd (Ubuntu) Assignee: (unassigned) => Benjamin Drung (bdrung) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu. https://bugs.launchpad.net/bugs/2025666 Title: Please merge 1.225-1 into mantic Status in netcat-openbsd package in Ubuntu: Fix Committed Bug description: PPA https://launchpad.net/~danilogondolfo/+archive/ubuntu/netcat- openbsd Autopkgtest https://autopkgtest.ubuntu.com/results/autopkgtest-mantic- danilogondolfo-netcat-openbsd/mantic/amd64/n/netcat- openbsd/20230703_202110_fccf3@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/2025666/+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 1997542] Re: DNS fails with "Using degraded feature set" in logs until resolved is restarted
** Changed in: systemd Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1997542 Title: DNS fails with "Using degraded feature set" in logs until resolved is restarted Status in systemd: New Status in systemd package in Ubuntu: New Bug description: This issue in systemd-resolved which is part of Ubuntu 22.04 causes syslog to be flooded causing periodic storage writes (power overhead). It is reported here: https://github.com/systemd/systemd/issues/13432 . There is no resolution yet. Hence, filing this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1997542/+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 1997542] Re: DNS fails with "Using degraded feature set" in logs until resolved is restarted
** Changed in: systemd (Ubuntu) Importance: Undecided => Low ** Bug watch added: github.com/systemd/systemd/issues #13432 https://github.com/systemd/systemd/issues/13432 ** Also affects: systemd via https://github.com/systemd/systemd/issues/13432 Importance: Unknown Status: Unknown -- 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/1997542 Title: DNS fails with "Using degraded feature set" in logs until resolved is restarted Status in systemd: Unknown Status in systemd package in Ubuntu: New Bug description: This issue in systemd-resolved which is part of Ubuntu 22.04 causes syslog to be flooded causing periodic storage writes (power overhead). It is reported here: https://github.com/systemd/systemd/issues/13432 . There is no resolution yet. Hence, filing this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1997542/+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 2025982] Re: Warning 'failed to get driver name for fd 0' fails gtk tests
** Changed in: mesa (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2025982 Title: Warning 'failed to get driver name for fd 0' fails gtk tests Status in Mesa: New Status in mesa package in Ubuntu: In Progress Status in mesa package in Debian: New Bug description: The new version displays that warning which makes the gtk autopkgtest red Upstream https://gitlab.freedesktop.org/mesa/mesa/-/issues/9199 Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039922 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2025982/+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 2025980] Re: can not setup keyboard and mouse separately
device models are listed in the log above: model: K800 (this is keyboard) model: Performance MX (mouse) their product codes are 046D:2010 and 046D:101A it really seems similar to the issue #215, but that fix didn't help me. I cloned git version of upower, compiled and installed. now I see: UPower client version 1.90.1 UPower daemon version 1.90.1 unfortunalely, the problem still persists. -- 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/2025980 Title: can not setup keyboard and mouse separately Status in upower package in Ubuntu: New Bug description: I have Logitech wireless keyboard and wireless mouse, coonnected to the same Unifying receiver. battery level of these devices is reported correctly, but both are listed in power settings as a keyboard, making me a bit confusing, which device is run out of power, when I get 'low keyboard battery' message. trying to set correct device type via modaliases for mouse changes nothing, but when I change my keyboard to 'a mouse', I get two mice in power settings! thus, I can not setup these devices separately, to get 1 keyboard and 1 mouse, but only 2 keyboards or 2 mice. ubuntu unity 23.04 UPower client version 0.99.20 UPower daemon version 0.99.20 output of 'upower -d': Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_0 native-path: hidpp_battery_0 model:K800 serial: b2-69-6e-91 power supply: no updated: Wed 05 Jul 2023 10:57:43 (2 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: discharging warning-level: low battery-level: low percentage: 10% (should be ignored) icon-name: 'battery-caution-symbolic' Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_1 native-path: hidpp_battery_1 model:Performance MX serial: 04-81-33-3a power supply: no updated: Wed 05 Jul 2023 10:57:37 (8 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: discharging warning-level: none battery-level: high percentage: 70% (should be ignored) icon-name: 'battery-good-symbolic' Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: no updated: Wed 05 Jul 2023 10:48:37 (548 seconds ago) has history: no has statistics: no unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' Daemon: daemon-version: 0.99.20 on-battery: no lid-is-closed: no lid-is-present: no critical-action: HybridSleep modaliases in 61-input-id-local.hwdb: id-input:modalias:input:b0003v046Dp101Ae0111* ID_INPUT_MOUSE=1 ID_INPUT=1 id-input:modalias:input:b0003v046Dp2010e0111* ID_INPUT_KEYBOARD=1 ID_INPUT=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/2025980/+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 2025982] Re: Warning 'failed to get driver name for fd 0' fails gtk tests
** Changed in: mesa Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2025982 Title: Warning 'failed to get driver name for fd 0' fails gtk tests Status in Mesa: New Status in mesa package in Ubuntu: In Progress Status in mesa package in Debian: Unknown Bug description: The new version displays that warning which makes the gtk autopkgtest red Upstream https://gitlab.freedesktop.org/mesa/mesa/-/issues/9199 Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039922 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2025982/+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 2025695] Re: systemd-resolved: manually dhclient ethx，dns nameserver in the /etc/resolve.conf will be written duplicate
dhclient is not part of the systemd package, so I will re-assign this bug. ** Package changed: systemd (Ubuntu) => isc-dhcp (Ubuntu) ** Summary changed: - systemd-resolved: manually dhclient ethx，dns nameserver in the /etc/resolve.conf will be written duplicate + manually dhclient ethx，dns nameserver in the /etc/resolve.conf will be written duplicate -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/2025695 Title: manually dhclient ethx，dns nameserver in the /etc/resolve.conf will be written duplicate Status in isc-dhcp package in Ubuntu: New Bug description: systemd version the issue has been seen with 249 Used distribution ubuntu22 Linux kernel version used 5.15.0-72-generic CPU architectures issue was seen on None Component systemd-resolved Unexpected behaviour you saw https://github.com/systemd/systemd/issues/28055 not this problem when I was on ubuntu20. The version of systemd is 245 this problem when I was on ubuntu22. The systemd version is 249 I compared the codes and suspected that v248 commit cbf23f3 caused by I saw this issuse about netplan on ubuntu https://superuser.com/questions/1721017/remove-redundant-dns-servers-in-ubuntu-22-04 But it doesn't work for dhclient (why I use dhclient, because I found it out of curiosity) Steps to reproduce the problem 1: Start a virtual machine on the cloud 2: Insert multiple network cards (auxiliary network card) 3: Manually use dhclient to start ethx (except eth0) dhclient -v -d eth1 4: View /etc/resolve.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2025695/+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 2009743] Re: networkd: classless routes served by DHCP are created incorrectly
Hi Pedro, Can you please try this with the latest version of systemd? We have 249.11-0ubuntu3.9 which has a patch for a similar sounding bug (I don't *think* it's the same thing, but just to be sure). Assuming that does not resolve the issue, can you please provide debug- level logs from systemd-networkd during a span where the routes would be created? You can enable debug logging by doing: $ mkdir -p /etc/systemd/system/systemd-networkd.service.d $ cat > /etc/systemd/system/systemd-networkd.service.d << EOF [Service] Environment=SYSTEMD_LOG_LEVEL=debug EOF $ systemctl daemon-reload $ systemctl restart systemd-networkd Then grab some logs from an appropriate timespan. I think networkctl forcerenew should do the trick: $ networkctl forcerenew $ journalctl -u systemd-networkd --since "5min ago" > logs.txt ** Changed in: systemd (Ubuntu) Status: Confirmed => Incomplete ** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2009743 Title: networkd: classless routes served by DHCP are created incorrectly Status in systemd package in Ubuntu: Incomplete Bug description: After upgrading 20.04 systems to 22.04, the classless routes served via DHCP are not being registered correctly - they are missing the gateway address. Expected routes - these are taken from a 20.04 system on the same network: $ ip route default via 10.10.1.1 dev enp24s0 proto dhcp src 10.10.64.12 metric 100 10.0.0.0/8 dev enp24s0 proto kernel scope link src 10.10.64.12 10.88.88.0/24 via 10.10.1.2 dev enp24s0 proto dhcp src 10.10.64.12 metric 100 10.96.0.0/11 via 10.10.1.2 dev enp24s0 proto dhcp src 10.10.64.12 metric 100 Actual routes - these are the routes created in one of the affected 22.04 systems: $ ip route default via 10.10.1.1 dev bond0 proto dhcp src 10.10.48.20 metric 100 8.8.8.8 via 10.10.1.1 dev bond0 proto dhcp src 10.10.48.20 metric 100 10.0.0.0/8 dev bond0 proto kernel scope link src 10.10.48.20 metric 100 10.10.1.1 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100 10.10.1.2 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100 10.88.88.0/24 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100 10.96.0.0/11 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100 Note the routes for 10.88.88.0/24 and 10.96.0.0/11 are missing the "via" gateway address, and therefore don't work. (For some reason there are also static routes created for DNS server (8.8.8.8) and known gateways (10.10.1.1 and 10.10.1.2). These are redundant but harmless.) Both the working and non-working systems are being managed by netplan. The non-working system has a bonded interface but I have checked that is not the cause of the problem - using a physical interface directly has the same result. I have attached the files /etc/netplan/00-installer-config.yaml and /run/systemd/network/10-netplan-bond0.network of the affected system. Affected system: Ubuntu version: Ubuntu 22.04.2 LTS systemd version: 249.11-0ubuntu3.6 Older system not affected: Ubuntu version: Ubuntu 20.04.5 LTS systemd version: 245.4-4ubuntu3.19 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2009743/+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 2025363] Re: Merge console-setup 1.222 into mantic
I'll unsubscribe ~ubuntu-sponsors for now. Please re-subscribe once the merge is ready again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/2025363 Title: Merge console-setup 1.222 into mantic Status in console-setup package in Ubuntu: Incomplete Bug description: The Debian package has been upgraded to release 1.222. According to the changelog this is just a rebuild. Rebuilding will update the keyboard names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/2025363/+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 1641272] Re: Debug symbols package doesnt exist
I made a comment in the Debian bug above expressing interest in working on this if Simon gives his approval, since it is more critical as the package is synced with Debian at the moment. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1641272 Title: Debug symbols package doesnt exist Status in dnsmasq package in Ubuntu: New Status in dnsmasq package in Debian: New Bug description: On Yakkety with ddebs repos enabled there is no debug packages for dnsmasq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1641272/+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 2025655] Re: Please merge 1.9.13p3-3 into mantic
** Merge proposal linked: https://code.launchpad.net/~danilogondolfo/ubuntu/+source/sudo/+git/sudo/+merge/446052 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/2025655 Title: Please merge 1.9.13p3-3 into mantic Status in sudo package in Ubuntu: New Bug description: [placeholder] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2025655/+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 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10
On 04/07/23 08:23, Gunnar Hjalmarsson wrote: > My first upload to the PPA proved to not be complete. Corrected now. > (Wait for the builds to finish and the packages to be published before > updating). I have installed the new proposed version, but I have a regression with deadkeys: pressing altgr+', then e used to insert the letter é, now it doesn't anymore. My keyboard layout is us_intl_altgr. Thanks for your work! Federico -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1996652 Title: Nautilus search is slow and jumbles keyboard input on 22.10 Status in ibus: New Status in ibus package in Ubuntu: Confirmed Bug description: Since my upgrade to 22.10, I've found the search box in Nautilus (files) essentially unusable. It is notably sluggish to launch and browse in general. But most detrimental to the usability is this: The characters do not appear in real time as I type. When they do appear, they are sometimes jumbled or in reverse (consistently reproducible). As I type in the file search box, the circular cursor spins intermittently, then the UI catches up and it's not what I typed. For example, I just typed "umbrella" into the search box, and Nautilus searched for: "umballer" Off-the-cuff test #2, searched for "Ubuntu" and I ended up with "Ubunut" ... you can't make this up. :-) Test #3, typed Launchpad, ended up with a search for "Laudaphcn". Keyboard input everywhere else on the system is otherwise normal and snappy. No pun intended, really. FWIW Nautilus files preferences are as default (Search in subfolders, Show thumbnails, File count == This computer only). $ apt-cache policy nautilus nautilus: Installed: 1:43.0-1ubuntu1 Candidate: 1:43.0-1ubuntu1 Version table: *** 1:43.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status $ uname -r 5.19.0-23-generic $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 $ snap list Name Version RevTracking Publisher Notes bare 1.0 5 latest/stable canonical✓ base core 16-2.57.2 13886 latest/stable canonical✓ core core18 20221027 2620 latest/stable canonical✓ base core20 20221027 1695 latest/stable canonical✓ base gnome-3-34-18040+git.3556cb3 77 latest/stable/… canonical✓ - gnome-3-38-20040+git.6f39565 119latest/stable canonical✓ - google-cloud-sdk 409.0.0 298latest/stable google-cloud-sdk✓ classic gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - snap-store 41.3-64-g512c0ff 599latest/stable/… canonical✓ - snapd 2.57.417336 latest/stable canonical✓ snapd snapd-desktop-integration 0.1 14 latest/stable/… canonical✓ - Side question: Since this system has transitioned across several upgrades from 20.04 to 22.10, do I really need all of these core* and gnome* snaps? To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1996652/+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 2025571] Re: kde frontend crashed
** Summary changed: - System program problem + kde frontend crashed ** Information type changed from Private to Public -- 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/2025571 Title: kde frontend crashed Status in software-properties package in Ubuntu: New Bug description: I had a window pop up reporting a system program problem. I have stability issues, although I don't know if it has to do with this bug. lsb_release -rd No LSB modules are available. Description:Ubuntu Mantic Minotaur (development branch) Release:23.10 apt-cache policy pkgname N: Unable to locate package pkgname (N/A) ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: software-properties-qt 0.99.37 Uname: Linux 6.3.0-7-generic x86_64 Architecture: amd64 CurrentDesktop: LXQt Date: Sun Jul 2 13:00:52 2023 ExecutablePath: /usr/bin/software-properties-qt ExecutableTimestamp: 1684227455 InterpreterPath: /usr/bin/python3.11 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-kde --attach 73400326 --dont-update ProcCwd: /home/jamescw Signal: 11 SourcePackage: software-properties UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2025571/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
Do we need evince to be reuploaded for jammy there since the previous upload was rejected by Steve? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Fix Released Status in evince package in Ubuntu: Fix Released Status in apparmor source package in Jammy: Fix Committed Status in evince source package in Jammy: In Progress Status in apparmor source package in Lunar: Fix Committed Status in evince source package in Lunar: Fix Committed Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 2025666] Re: Please merge 1.225-1 into mantic
Thank you, Lucas. I split that merge commit. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu. https://bugs.launchpad.net/bugs/2025666 Title: Please merge 1.225-1 into mantic Status in netcat-openbsd package in Ubuntu: New Bug description: PPA https://launchpad.net/~danilogondolfo/+archive/ubuntu/netcat- openbsd Autopkgtest https://autopkgtest.ubuntu.com/results/autopkgtest-mantic- danilogondolfo-netcat-openbsd/mantic/amd64/n/netcat- openbsd/20230703_202110_fccf3@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/2025666/+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 2025980] Re: can not setup keyboard and mouse separately
Thank you for your bug report. Which mouse model do you have? It looks similar to https://gitlab.freedesktop.org/upower/upower/-/issues/215 ** Bug watch added: gitlab.freedesktop.org/upower/upower/-/issues #215 https://gitlab.freedesktop.org/upower/upower/-/issues/215 ** Changed in: upower (Ubuntu) Importance: Undecided => Low -- 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/2025980 Title: can not setup keyboard and mouse separately Status in upower package in Ubuntu: New Bug description: I have Logitech wireless keyboard and wireless mouse, coonnected to the same Unifying receiver. battery level of these devices is reported correctly, but both are listed in power settings as a keyboard, making me a bit confusing, which device is run out of power, when I get 'low keyboard battery' message. trying to set correct device type via modaliases for mouse changes nothing, but when I change my keyboard to 'a mouse', I get two mice in power settings! thus, I can not setup these devices separately, to get 1 keyboard and 1 mouse, but only 2 keyboards or 2 mice. ubuntu unity 23.04 UPower client version 0.99.20 UPower daemon version 0.99.20 output of 'upower -d': Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_0 native-path: hidpp_battery_0 model:K800 serial: b2-69-6e-91 power supply: no updated: Wed 05 Jul 2023 10:57:43 (2 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: discharging warning-level: low battery-level: low percentage: 10% (should be ignored) icon-name: 'battery-caution-symbolic' Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_1 native-path: hidpp_battery_1 model:Performance MX serial: 04-81-33-3a power supply: no updated: Wed 05 Jul 2023 10:57:37 (8 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: discharging warning-level: none battery-level: high percentage: 70% (should be ignored) icon-name: 'battery-good-symbolic' Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: no updated: Wed 05 Jul 2023 10:48:37 (548 seconds ago) has history: no has statistics: no unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' Daemon: daemon-version: 0.99.20 on-battery: no lid-is-closed: no lid-is-present: no critical-action: HybridSleep modaliases in 61-input-id-local.hwdb: id-input:modalias:input:b0003v046Dp101Ae0111* ID_INPUT_MOUSE=1 ID_INPUT=1 id-input:modalias:input:b0003v046Dp2010e0111* ID_INPUT_KEYBOARD=1 ID_INPUT=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/2025980/+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 1974056] Re: iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless-bitwise_0 fails on s390x
Note this is still an issue, we just marked the given test case as ignored on s390x going forward. The https://launchpad.net/ubuntu/+source/iptables/1.8.7-1ubuntu6 upload: * disabled 0002-ebtables-save-restore_0 on x86 * disabled 0009-needless-bitwise_0 on s390x See the diff at http://launchpadlibrarian.net/599916663/iptables_1.8.7-1ubuntu5_1.8.7-1ubuntu6.diff.gz I will check again once we have newer iptables available. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1974056 Title: iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless- bitwise_0 fails on s390x Status in iptables: Unknown Status in Ubuntu on IBM z Systems: In Progress Status in iptables package in Ubuntu: New Bug description: In Ubuntu, we execute the full iptables shell testcases across all architectures. They seem to all pass everywhere, however iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless- bitwise_0 is currently failing on s390x like so: command17FAIL stderr: W: [FAILED] ././testcases/nft- only/0009-needless-bitwise_0: expected 0 but got 1 i wonder if there is some endian bug, as this is currently Ubuntu's only big-endian architecture. this can be reproduced with: pull-lp-source iptables cd iptables-1.8.7/ chmod +x ./iptables/tests/shell/testcases/iptables/0007-zero-counters_0 cd iptables/tests/shell sudo ./run-tests.sh --host To manage notifications about this bug go to: https://bugs.launchpad.net/iptables/+bug/1974056/+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 2025982] [NEW] Warning 'failed to get driver name for fd 0' fails gtk tests
Public bug reported: The new version displays that warning which makes the gtk autopkgtest red Upstream https://gitlab.freedesktop.org/mesa/mesa/-/issues/9199 Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039922 ** Affects: mesa Importance: Unknown Status: Unknown ** Affects: mesa (Ubuntu) Importance: High Assignee: Timo Aaltonen (tjaalton) Status: In Progress ** Affects: mesa (Debian) Importance: Unknown Status: Unknown ** Tags: update-excuse ** Changed in: mesa (Ubuntu) Status: New => In Progress ** Changed in: mesa (Ubuntu) Importance: Undecided => High ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #9199 https://gitlab.freedesktop.org/mesa/mesa/-/issues/9199 ** Also affects: mesa via https://gitlab.freedesktop.org/mesa/mesa/-/issues/9199 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #1039922 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039922 ** Also affects: mesa (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039922 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2025982 Title: Warning 'failed to get driver name for fd 0' fails gtk tests Status in Mesa: Unknown Status in mesa package in Ubuntu: In Progress Status in mesa package in Debian: Unknown Bug description: The new version displays that warning which makes the gtk autopkgtest red Upstream https://gitlab.freedesktop.org/mesa/mesa/-/issues/9199 Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039922 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2025982/+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 2025980] [NEW] can not setup keyboard and mouse separately
Public bug reported: I have Logitech wireless keyboard and wireless mouse, coonnected to the same Unifying receiver. battery level of these devices is reported correctly, but both are listed in power settings as a keyboard, making me a bit confusing, which device is run out of power, when I get 'low keyboard battery' message. trying to set correct device type via modaliases for mouse changes nothing, but when I change my keyboard to 'a mouse', I get two mice in power settings! thus, I can not setup these devices separately, to get 1 keyboard and 1 mouse, but only 2 keyboards or 2 mice. ubuntu unity 23.04 UPower client version 0.99.20 UPower daemon version 0.99.20 output of 'upower -d': Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_0 native-path: hidpp_battery_0 model:K800 serial: b2-69-6e-91 power supply: no updated: Wed 05 Jul 2023 10:57:43 (2 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: discharging warning-level: low battery-level: low percentage: 10% (should be ignored) icon-name: 'battery-caution-symbolic' Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_1 native-path: hidpp_battery_1 model:Performance MX serial: 04-81-33-3a power supply: no updated: Wed 05 Jul 2023 10:57:37 (8 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: discharging warning-level: none battery-level: high percentage: 70% (should be ignored) icon-name: 'battery-good-symbolic' Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: no updated: Wed 05 Jul 2023 10:48:37 (548 seconds ago) has history: no has statistics: no unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' Daemon: daemon-version: 0.99.20 on-battery: no lid-is-closed: no lid-is-present: no critical-action: HybridSleep modaliases in 61-input-id-local.hwdb: id-input:modalias:input:b0003v046Dp101Ae0111* ID_INPUT_MOUSE=1 ID_INPUT=1 id-input:modalias:input:b0003v046Dp2010e0111* ID_INPUT_KEYBOARD=1 ID_INPUT=1 ** Affects: upower (Ubuntu) Importance: Undecided Status: New ** Tags: battery modalias ** Tags removed: modaliases ** Tags added: modalias -- 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/2025980 Title: can not setup keyboard and mouse separately Status in upower package in Ubuntu: New Bug description: I have Logitech wireless keyboard and wireless mouse, coonnected to the same Unifying receiver. battery level of these devices is reported correctly, but both are listed in power settings as a keyboard, making me a bit confusing, which device is run out of power, when I get 'low keyboard battery' message. trying to set correct device type via modaliases for mouse changes nothing, but when I change my keyboard to 'a mouse', I get two mice in power settings! thus, I can not setup these devices separately, to get 1 keyboard and 1 mouse, but only 2 keyboards or 2 mice. ubuntu unity 23.04 UPower client version 0.99.20 UPower daemon version 0.99.20 output of 'upower -d': Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_0 native-path: hidpp_battery_0 model:K800 serial: b2-69-6e-91 power supply: no updated: Wed 05 Jul 2023 10:57:43 (2 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: discharging warning-level: low battery-level: low percentage: 10% (should be ignored) icon-name: 'battery-caution-symbolic' Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_1 native-path: hidpp_battery_1 model:Performance MX serial: 04-81-33-3a power supply: no updated: Wed 05 Jul 2023 10:57:37 (8 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: discharging warning-level: none battery-level: high percentage: 70% (should be ignored) icon-name: 'battery-good-symbolic' Device: /org/freedesktop/UPower/devices/DisplayDevice power
[Touch-packages] [Bug 2025965] Re: aptsources deb822 Section constructor fails on valid .sources file
** No longer affects: command-not-found (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2025965 Title: aptsources deb822 Section constructor fails on valid .sources file Status in python-apt package in Ubuntu: New Bug description: When attempting to parse (what I believe is) a perfectly valid deb822-formated `.sources` file, the library's `_deb822.Section` constructor parses my file incorrectly, resulting in an exception being thrown. At a low level, the error is `ValueError: Unable to parse section data` and is thrown in the `_deb822.Section` constructor, located at line 41 of `aptsources/_deb822.py`. The error was caused by the evaluation of `apt_pkg.TagSection(trimmed_section)` on that line with `trimmed_section` being an empty string. At a high level, based on a cursory debug, it seems the parser incorrectly considers the first three lines of my `.sources` file -- which are, in fact, comments -- to be a stanza, and is trying to instantiate an object for them, despite them having no non-ignored content. Notably, -- supporting my conclusion -- this issue disappears entirely if I remove the first blank line in the file (located after those comments and before the first stanza). I am attaching my .sources file for reference. Notes: - FWIW, I don't use this library directly; the code at issue gets invoked by the `command-not-found` package/bash handler. (The warnings therefore show up every time I mistype a command.) In any case, I traced the issue down to this package. - My python3-apt package is version 2.5.3ubuntu1 from lunar/main. - This error began for me upon an upgrade from jammy to lunar. This sources file was unchanged during the upgrade (except for renaming `jammy` to `lunar`, and changing `Enabled` to `no` in the `partner` stanza). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2025965/+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 2025695] Re: systemd-resolved: manually dhclient ethx，dns nameserver in the /etc/resolve.conf will be written duplicate
** Information type changed from Public to Public Security -- 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/2025695 Title: systemd-resolved: manually dhclient ethx，dns nameserver in the /etc/resolve.conf will be written duplicate Status in systemd package in Ubuntu: New Bug description: systemd version the issue has been seen with 249 Used distribution ubuntu22 Linux kernel version used 5.15.0-72-generic CPU architectures issue was seen on None Component systemd-resolved Unexpected behaviour you saw https://github.com/systemd/systemd/issues/28055 not this problem when I was on ubuntu20. The version of systemd is 245 this problem when I was on ubuntu22. The systemd version is 249 I compared the codes and suspected that v248 commit cbf23f3 caused by I saw this issuse about netplan on ubuntu https://superuser.com/questions/1721017/remove-redundant-dns-servers-in-ubuntu-22-04 But it doesn't work for dhclient (why I use dhclient, because I found it out of curiosity) Steps to reproduce the problem 1: Start a virtual machine on the cloud 2: Insert multiple network cards (auxiliary network card) 3: Manually use dhclient to start ethx (except eth0) dhclient -v -d eth1 4: View /etc/resolve.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2025695/+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 1992688] Update Released
The verification of the Stable Release Update for ubuntu-meta has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1992688 Title: firefox deb not installed Status in firefox package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Status in firefox source package in Jammy: Invalid Status in ubuntu-meta source package in Jammy: Fix Released Bug description: Impact -- Applications which use x-www-browser to launch a browser will not work on a freshly installed Ubuntu 22.04 system as the firefox deb (which provides x-www-browser) is not installed. Test Plan - 1) Install Ubuntu 22.04.2 using an amd64 desktop iso image 2) Open a terminal 3) Run x-www-browser www.ubuntu.com 4) Observe a command not found message which recommends installing firefox Installing of a daily build of Ubuntu 22.04 with -proposed enabled and ubuntu-desktop version 1.481.1 will not exhibit the above problem. Where problems could occur -- Other Info -- I tested an upgrade from Ubuntu 20.04 to Ubuntu 22.04 and the firefox deb was not removed during the upgrade process so upgrades are a non-issue. Original Description Bug 1964036 leads me to believe that the firefox deb provides some important functionality (the firefox favourite icon in the gnome shell dock) but there is nothing that would require the deb to be installed (it is not seeded nor has an rdep) and the package description indicates that it can be safely removed. Is there some important functionality that it provides? ProblemType: BugDistroRelease: Ubuntu 22.10 Package: ubuntu-release-upgrader-core 1:22.10.8 ProcVersionSignature: User Name 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Oct 12 11:30:46 2022 InstallationDate: Installed on 2022-04-27 (167 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992688/+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 1992688] Re: firefox deb not installed
This bug was fixed in the package ubuntu-meta - 1.481.1 --- ubuntu-meta (1.481.1) jammy; urgency=medium * Refreshed dependencies * Added firefox to desktop-minimal-recommends [amd64 arm64 armhf], desktop-recommends [amd64 arm64 armhf] as it provides dpkg alternatives for x-www-browser and gnome-www-browser. (LP: #1992688) -- Brian Murray Thu, 27 Apr 2023 01:17:57 -0700 ** Changed in: ubuntu-meta (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1992688 Title: firefox deb not installed Status in firefox package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Status in firefox source package in Jammy: Invalid Status in ubuntu-meta source package in Jammy: Fix Released Bug description: Impact -- Applications which use x-www-browser to launch a browser will not work on a freshly installed Ubuntu 22.04 system as the firefox deb (which provides x-www-browser) is not installed. Test Plan - 1) Install Ubuntu 22.04.2 using an amd64 desktop iso image 2) Open a terminal 3) Run x-www-browser www.ubuntu.com 4) Observe a command not found message which recommends installing firefox Installing of a daily build of Ubuntu 22.04 with -proposed enabled and ubuntu-desktop version 1.481.1 will not exhibit the above problem. Where problems could occur -- Other Info -- I tested an upgrade from Ubuntu 20.04 to Ubuntu 22.04 and the firefox deb was not removed during the upgrade process so upgrades are a non-issue. Original Description Bug 1964036 leads me to believe that the firefox deb provides some important functionality (the firefox favourite icon in the gnome shell dock) but there is nothing that would require the deb to be installed (it is not seeded nor has an rdep) and the package description indicates that it can be safely removed. Is there some important functionality that it provides? ProblemType: BugDistroRelease: Ubuntu 22.10 Package: ubuntu-release-upgrader-core 1:22.10.8 ProcVersionSignature: User Name 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Oct 12 11:30:46 2022 InstallationDate: Installed on 2022-04-27 (167 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992688/+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 1971715] Update Released
The verification of the Stable Release Update for libidn has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libidn in Ubuntu. https://bugs.launchpad.net/bugs/1971715 Title: 22.04 idn -a domain.com idn: could not convert from ASCII to UTF-8 Status in libidn package in Ubuntu: Fix Released Status in libidn source package in Jammy: Fix Released Status in libidn source package in Kinetic: Fix Released Bug description: [ Impact ] idn cannot handle non-ASCII characters [ Test Plan ] Existing state in 22.04: $ echo ü | idn idn: could not convert from ASCII to UTF-8 Fixed output: $ echo ü | idn xn--tda [ Where problems could occur ] The patch enables an extra autotools features, so the most likely problem is a build failure. Currently non-ASCII characters are entirely unhandled, so there's no risk of regression there, but this could potentially turn clean failures into crashes or incorrect output. [Original report] On Ubuntu 22.04 Jammy: idn -a "xxx-tést.eu" idn: could not convert from ASCII to UTF-8 And idn -u "xn--xxx-tst-fya.eu" idn: could not convert from UTF-8 to ASCII Expected: Successfully conversion from ASCII to UTF-8 Ubuntu 20.04 / 18.04 it works fine Also with idn2 from UTF-8 to ASCII works as expected how ever support lacks from ASCII to UTF-8 Description: Ubuntu 22.04 LTS Release: 22.04 root@test:~# echo $LC_ALL C.UTF-8 root@test:~# apt-cache policy idn idn: Installed: 1.38-4build1 Candidate: 1.38-4build1 Version table: *** 1.38-4build1 500 500 https://mirror.hetzner.com/ubuntu/packages jammy/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1971715/+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 1971715] Re: 22.04 idn -a domain.com idn: could not convert from ASCII to UTF-8
This bug was fixed in the package libidn - 1.38-4ubuntu1 --- libidn (1.38-4ubuntu1) jammy; urgency=medium * debian/patches/initialise_langinfo_codeset.patch: - Fix handling of non-ASCII characters (LP: #1971715) -- Christopher James Halse Rogers Tue, 01 Nov 2022 16:40:24 +0100 ** Changed in: libidn (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libidn in Ubuntu. https://bugs.launchpad.net/bugs/1971715 Title: 22.04 idn -a domain.com idn: could not convert from ASCII to UTF-8 Status in libidn package in Ubuntu: Fix Released Status in libidn source package in Jammy: Fix Released Status in libidn source package in Kinetic: Fix Released Bug description: [ Impact ] idn cannot handle non-ASCII characters [ Test Plan ] Existing state in 22.04: $ echo ü | idn idn: could not convert from ASCII to UTF-8 Fixed output: $ echo ü | idn xn--tda [ Where problems could occur ] The patch enables an extra autotools features, so the most likely problem is a build failure. Currently non-ASCII characters are entirely unhandled, so there's no risk of regression there, but this could potentially turn clean failures into crashes or incorrect output. [Original report] On Ubuntu 22.04 Jammy: idn -a "xxx-tést.eu" idn: could not convert from ASCII to UTF-8 And idn -u "xn--xxx-tst-fya.eu" idn: could not convert from UTF-8 to ASCII Expected: Successfully conversion from ASCII to UTF-8 Ubuntu 20.04 / 18.04 it works fine Also with idn2 from UTF-8 to ASCII works as expected how ever support lacks from ASCII to UTF-8 Description: Ubuntu 22.04 LTS Release: 22.04 root@test:~# echo $LC_ALL C.UTF-8 root@test:~# apt-cache policy idn idn: Installed: 1.38-4build1 Candidate: 1.38-4build1 Version table: *** 1.38-4build1 500 500 https://mirror.hetzner.com/ubuntu/packages jammy/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1971715/+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 2025965] Re: aptsources deb822 Section constructor fails on valid .sources file
Also, if it helps, here's a minimal example python file, triggering the error (requires attached `00ubuntu.sources` to be in cwd) ** Attachment added: "Minimal example of error (requires other attached `00ubuntu.sources` file)" https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2025965/+attachment/5683961/+files/cnf-debug.py ** Also affects: command-not-found (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2025965 Title: aptsources deb822 Section constructor fails on valid .sources file Status in command-not-found package in Ubuntu: New Status in python-apt package in Ubuntu: New Bug description: When attempting to parse (what I believe is) a perfectly valid deb822-formated `.sources` file, the library's `_deb822.Section` constructor parses my file incorrectly, resulting in an exception being thrown. At a low level, the error is `ValueError: Unable to parse section data` and is thrown in the `_deb822.Section` constructor, located at line 41 of `aptsources/_deb822.py`. The error was caused by the evaluation of `apt_pkg.TagSection(trimmed_section)` on that line with `trimmed_section` being an empty string. At a high level, based on a cursory debug, it seems the parser incorrectly considers the first three lines of my `.sources` file -- which are, in fact, comments -- to be a stanza, and is trying to instantiate an object for them, despite them having no non-ignored content. Notably, -- supporting my conclusion -- this issue disappears entirely if I remove the first blank line in the file (located after those comments and before the first stanza). I am attaching my .sources file for reference. Notes: - FWIW, I don't use this library directly; the code at issue gets invoked by the `command-not-found` package/bash handler. (The warnings therefore show up every time I mistype a command.) In any case, I traced the issue down to this package. - My python3-apt package is version 2.5.3ubuntu1 from lunar/main. - This error began for me upon an upgrade from jammy to lunar. This sources file was unchanged during the upgrade (except for renaming `jammy` to `lunar`, and changing `Enabled` to `no` in the `partner` stanza). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/2025965/+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 2025965] Re: aptsources deb822 Section constructor fails on valid .sources file
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2025965 Title: aptsources deb822 Section constructor fails on valid .sources file Status in command-not-found package in Ubuntu: New Status in python-apt package in Ubuntu: New Bug description: When attempting to parse (what I believe is) a perfectly valid deb822-formated `.sources` file, the library's `_deb822.Section` constructor parses my file incorrectly, resulting in an exception being thrown. At a low level, the error is `ValueError: Unable to parse section data` and is thrown in the `_deb822.Section` constructor, located at line 41 of `aptsources/_deb822.py`. The error was caused by the evaluation of `apt_pkg.TagSection(trimmed_section)` on that line with `trimmed_section` being an empty string. At a high level, based on a cursory debug, it seems the parser incorrectly considers the first three lines of my `.sources` file -- which are, in fact, comments -- to be a stanza, and is trying to instantiate an object for them, despite them having no non-ignored content. Notably, -- supporting my conclusion -- this issue disappears entirely if I remove the first blank line in the file (located after those comments and before the first stanza). I am attaching my .sources file for reference. Notes: - FWIW, I don't use this library directly; the code at issue gets invoked by the `command-not-found` package/bash handler. (The warnings therefore show up every time I mistype a command.) In any case, I traced the issue down to this package. - My python3-apt package is version 2.5.3ubuntu1 from lunar/main. - This error began for me upon an upgrade from jammy to lunar. This sources file was unchanged during the upgrade (except for renaming `jammy` to `lunar`, and changing `Enabled` to `no` in the `partner` stanza). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/2025965/+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 2025965] [NEW] aptsources deb822 Section constructor fails on valid .sources file
Public bug reported: When attempting to parse (what I believe is) a perfectly valid deb822-formated `.sources` file, the library's `_deb822.Section` constructor parses my file incorrectly, resulting in an exception being thrown. At a low level, the error is `ValueError: Unable to parse section data` and is thrown in the `_deb822.Section` constructor, located at line 41 of `aptsources/_deb822.py`. The error was caused by the evaluation of `apt_pkg.TagSection(trimmed_section)` on that line with `trimmed_section` being an empty string. At a high level, based on a cursory debug, it seems the parser incorrectly considers the first three lines of my `.sources` file -- which are, in fact, comments -- to be a stanza, and is trying to instantiate an object for them, despite them having no non-ignored content. Notably, -- supporting my conclusion -- this issue disappears entirely if I remove the first blank line in the file (located after those comments and before the first stanza). I am attaching my .sources file for reference. Notes: - FWIW, I don't use this library directly; the code at issue gets invoked by the `command-not-found` package/bash handler. (The warnings therefore show up every time I mistype a command.) In any case, I traced the issue down to this package. - My python3-apt package is version 2.5.3ubuntu1 from lunar/main. - This error began for me upon an upgrade from jammy to lunar. This sources file was unchanged during the upgrade (except for renaming `jammy` to `lunar`, and changing `Enabled` to `no` in the `partner` stanza). ** Affects: command-not-found (Ubuntu) Importance: Undecided Status: New ** Affects: python-apt (Ubuntu) Importance: Undecided Status: New ** Attachment added: "The .sources file causing this error." https://bugs.launchpad.net/bugs/2025965/+attachment/5683960/+files/00ubuntu.sources -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2025965 Title: aptsources deb822 Section constructor fails on valid .sources file Status in command-not-found package in Ubuntu: New Status in python-apt package in Ubuntu: New Bug description: When attempting to parse (what I believe is) a perfectly valid deb822-formated `.sources` file, the library's `_deb822.Section` constructor parses my file incorrectly, resulting in an exception being thrown. At a low level, the error is `ValueError: Unable to parse section data` and is thrown in the `_deb822.Section` constructor, located at line 41 of `aptsources/_deb822.py`. The error was caused by the evaluation of `apt_pkg.TagSection(trimmed_section)` on that line with `trimmed_section` being an empty string. At a high level, based on a cursory debug, it seems the parser incorrectly considers the first three lines of my `.sources` file -- which are, in fact, comments -- to be a stanza, and is trying to instantiate an object for them, despite them having no non-ignored content. Notably, -- supporting my conclusion -- this issue disappears entirely if I remove the first blank line in the file (located after those comments and before the first stanza). I am attaching my .sources file for reference. Notes: - FWIW, I don't use this library directly; the code at issue gets invoked by the `command-not-found` package/bash handler. (The warnings therefore show up every time I mistype a command.) In any case, I traced the issue down to this package. - My python3-apt package is version 2.5.3ubuntu1 from lunar/main. - This error began for me upon an upgrade from jammy to lunar. This sources file was unchanged during the upgrade (except for renaming `jammy` to `lunar`, and changing `Enabled` to `no` in the `partner` stanza). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/2025965/+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
