[Touch-packages] [Bug 2052489] Re: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration
This still needs "LightDM" to work with this for Noble. That is the default DM for Mate. This is still broken in the Noble Mate Dailys, and is not close yet. Is there something else you all want us to test, try, or tweak to help get this fixed? We are willing to help, if you direct us in a direction. We have also tried other things to try to get this to work in Mate. RE: https://ubuntuforums.org/showthread.php?t=2495023 It's not like the Noble 'lightdm' package is completely broken. It works with other flavors, such as (straight-up) Ubuntu. I've installed it on Noble Ubuntu with gnome-sessions, and that works fine, with no errors. This has something to do with the combination of LightDM and the Noble Mate Desktop image. If I toggle over to a vtty, and give it startx, it brings up the Mate Desktop. -- 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/2052489 Title: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration Status in apparmor package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: New Bug description: Noble Mate Daily 20230205 ISO Boots up past Splash to black screen. Last errors in logs are about apparmor denied on snap desktop integration... So the graphics layer is being denied because of an apparmor error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+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 2022927] Re: Busybox mount fails to mount Snaps
[Expired for busybox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: busybox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/2022927 Title: Busybox mount fails to mount Snaps Status in busybox package in Ubuntu: Expired Bug description: Snapd tries to mount squashfs Snaps with non-standard mount flags like "x-gdu.hide" and "x-gvfs-hide", both of which are used to indicate to userspace programs that a given mount should not be shown in a list of mounted partitions/filesystems. Busybox does not support these flags, and so fails with "Invalid argument". $ sudo busybox mount -t tmpfs -o x-gdu-hide test /tmp/test mount: mounting test on /tmp/test failed: Invalid argument These flags can likely be be safely ignored, as they don't actually affect the functionality of the mount. This goes for all mount options starting with "x-", as these generally denote non-standard mount option "extensions". I've created a patch against Busybox which adds an optional configuration item to ignore all mount options beginning with "x-". An additional verbose option has also been added to enable the ability to report that the mount flags have been ignored, rather than silently ignoring them. This is a requirement for a customer project, where we are limited to using Busybox (due to coreutils' GPL-3.0 licence) but would also require using Snaps like checkbox for testing and verification. This was posted on the Busybox mailing list a few months ago (http://lists.busybox.net/pipermail/busybox/2023-March/090202.html) but patch acceptance there seems to take quite a long time, and we need this for the customer. A PPA containing the patched Busybox version is available on the project's Launchpad team: https://launchpad.net/~nemos- team/+archive/ubuntu/ppa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2022927/+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 2052982] Re: regression in debconf-copydb when writing to stdout
** Changed in: debconf (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/2052982 Title: regression in debconf-copydb when writing to stdout Status in debconf package in Ubuntu: Fix Committed Status in ubiquity package in Ubuntu: Invalid Status in debconf package in Debian: New Bug description: While debugging a FTBFS in Ubiquity, I observed that the usage of debconf-copydb regressed when using version 1.5.85 of debconf. The previous-in-ubuntu version 1.5.82 of debconf was OK. That invocation looks roughly like: debconf-copydb templatedb pipe --config=Name:pipe --config=Driver:Pipe --config=InFd:none ... Bisecting debconf from there found commit 5db857ade00953496bfdb7edb884296bebc41885: "Avoid two-argument open" Further tracing found the following change to Debconf/DbDriver/Pipe.pm around line 120: - open ($fh, '>-'); + open ($fh, '>', \*STDOUT); An additional symptom of this problem is GLOB files with names that look like: GLOB(0x0123456789ab) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/2052982/+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 2052982] Re: regression in debconf-copydb when writing to stdout
** Bug watch added: Debian Bug tracker #1063817 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063817 ** Also affects: debconf (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063817 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/2052982 Title: regression in debconf-copydb when writing to stdout Status in debconf package in Ubuntu: Fix Committed Status in ubiquity package in Ubuntu: Invalid Status in debconf package in Debian: Unknown Bug description: While debugging a FTBFS in Ubiquity, I observed that the usage of debconf-copydb regressed when using version 1.5.85 of debconf. The previous-in-ubuntu version 1.5.82 of debconf was OK. That invocation looks roughly like: debconf-copydb templatedb pipe --config=Name:pipe --config=Driver:Pipe --config=InFd:none ... Bisecting debconf from there found commit 5db857ade00953496bfdb7edb884296bebc41885: "Avoid two-argument open" Further tracing found the following change to Debconf/DbDriver/Pipe.pm around line 120: - open ($fh, '>-'); + open ($fh, '>', \*STDOUT); An additional symptom of this problem is GLOB files with names that look like: GLOB(0x0123456789ab) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/2052982/+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 2052982] Re: regression in debconf-copydb when writing to stdout
** Changed in: debconf (Ubuntu) Status: New => In Progress ** Changed in: ubiquity (Ubuntu) Status: New => In Progress ** Changed in: ubiquity (Ubuntu) Status: In Progress => Invalid ** Changed in: debconf (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 debconf in Ubuntu. https://bugs.launchpad.net/bugs/2052982 Title: regression in debconf-copydb when writing to stdout Status in debconf package in Ubuntu: Fix Committed Status in ubiquity package in Ubuntu: Invalid Bug description: While debugging a FTBFS in Ubiquity, I observed that the usage of debconf-copydb regressed when using version 1.5.85 of debconf. The previous-in-ubuntu version 1.5.82 of debconf was OK. That invocation looks roughly like: debconf-copydb templatedb pipe --config=Name:pipe --config=Driver:Pipe --config=InFd:none ... Bisecting debconf from there found commit 5db857ade00953496bfdb7edb884296bebc41885: "Avoid two-argument open" Further tracing found the following change to Debconf/DbDriver/Pipe.pm around line 120: - open ($fh, '>-'); + open ($fh, '>', \*STDOUT); An additional symptom of this problem is GLOB files with names that look like: GLOB(0x0123456789ab) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/2052982/+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 2052982] [NEW] regression in debconf-copydb when writing to stdout
Public bug reported: While debugging a FTBFS in Ubiquity, I observed that the usage of debconf-copydb regressed when using version 1.5.85 of debconf. The previous-in-ubuntu version 1.5.82 of debconf was OK. That invocation looks roughly like: debconf-copydb templatedb pipe --config=Name:pipe --config=Driver:Pipe --config=InFd:none ... Bisecting debconf from there found commit 5db857ade00953496bfdb7edb884296bebc41885: "Avoid two-argument open" Further tracing found the following change to Debconf/DbDriver/Pipe.pm around line 120: - open ($fh, '>-'); + open ($fh, '>', \*STDOUT); An additional symptom of this problem is GLOB files with names that look like: GLOB(0x0123456789ab) ** Affects: debconf (Ubuntu) Importance: Undecided Status: New ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/2052982 Title: regression in debconf-copydb when writing to stdout Status in debconf package in Ubuntu: New Status in ubiquity package in Ubuntu: New Bug description: While debugging a FTBFS in Ubiquity, I observed that the usage of debconf-copydb regressed when using version 1.5.85 of debconf. The previous-in-ubuntu version 1.5.82 of debconf was OK. That invocation looks roughly like: debconf-copydb templatedb pipe --config=Name:pipe --config=Driver:Pipe --config=InFd:none ... Bisecting debconf from there found commit 5db857ade00953496bfdb7edb884296bebc41885: "Avoid two-argument open" Further tracing found the following change to Debconf/DbDriver/Pipe.pm around line 120: - open ($fh, '>-'); + open ($fh, '>', \*STDOUT); An additional symptom of this problem is GLOB files with names that look like: GLOB(0x0123456789ab) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/2052982/+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 2033892] Re: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled
** Description changed: - Release: 22.04.3 LTS - coreutils 8.32-4.1ubuntu1 + [Impact] - ls triggers unwanted mounts of autofs filesystems + Issuing a 'ls -l' or a 'stat' on an autofs share when you have set + --ghost in the auto.master file, or browse_mode=yes in autofs.conf will + lead to the shares being mounted, when they didn't previously. - cause: coreutils 8.32.4.1ubuntu1 uses statx which not pass the - AT_NO_AUTOMOUNT flag + Disks / shares may not be present and the mounts may fail, leading to + errors in your output. - This bug is also known (and fixed) at Redhat - https://bugzilla.redhat.com/show_bug.cgi?id=2044981 + This is a behaviour change in autofs 8.32, which occurred in the + transition to using statx() instead of stat()/lstat() in previous + releases. - upstream commits: - https://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v9.0-177-g85c975df2c2 - https://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v9.0-178-g92cb8427c53 + There doesn't seem to be any workarounds, apart from not running a 'ls + -l' in your autofs share directory. - fedora commit - https://src.fedoraproject.org/rpms/coreutils/c/d736cafa20f13eeb037a3950bdbb4b63dc39b7e3?branch=f35 + [Testcase] + + Start two Jammy VMs. One will be a NFS server, the other, the client. + + NFS server: + + Server VM: + $ sudo hostnamectl set-hostname jammy-nfs-server + $ sudo apt update && sudo apt upgrade -y + $ sudo apt install nfs-kernel-server + $ sudo mkdir /export + $ sudo mkdir /export/users + $ sudo vi /etc/exports # add the following lines: + /export 192.168.122.0/24(rw,fsid=0,no_subtree_check,sync) + /export/users 192.168.122.0/24(rw,nohide,insecure,no_subtree_check,sync) + $ sudo systemctl restart nfs-server.service + + AutoFS Client: + $ sudo apt update + $ sudo apt install autofs + $ sudo vim /etc/autofs.conf + browse_mode = yes + $ sudo mkdir /mnt2 + $ sudo vim /etc/auto.master + /mnt2 /etc/auto.indirect + $ sudo vim /etc/auto.indirect + export 192.168.122.18:/export + export-missing 192.168.122.18:/export-missing + $ sudo reboot + $ cd /mnt2 + $ ls -l + ls: cannot access 'export-missing': No such file or directory + total 4 + drwxr-xr-x 3 root root 4096 Feb 12 21:48 export + d? ? ?? ?? export-missing + $ mount -l | grep /mnt2 + /etc/auto.indirect on /mnt2 type autofs (rw,relatime,fd=6,pgrp=634,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=21561) + 192.168.122.18:/export on /mnt2/export type nfs (rw,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.122.18,mountvers=3,mountport=35786,mountproto=udp,local_lock=none,addr=192.168.122.18) + + We see the mount for export occurred, and export-missing was attempted, + but it was either bogus or the disk was not present, leading to a "No + such file or directory" error. + + There are test packages available in the following ppa: + + https://launchpad.net/~mruffell/+archive/ubuntu/sf378489-test + + If you install them, this is what should occur: + + $ ls -l + total 0 + drwxr-xr-x 2 root root 0 Feb 12 22:01 export + drwxr-xr-x 2 root root 0 Feb 12 22:01 export-missing + $ mount -l | grep /mnt2 + /etc/auto.indirect on /mnt2 type autofs (rw,relatime,fd=6,pgrp=636,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=18346) + + No mounts happen, and no errors either. + + [Where problems could occur] + + We are changing the behaviour of core utilities, ls and stat, such that + they no longer attempt to mount autofs shares when --ghost option is + present or browse_mode is enabled. + + This is the intended behaviour in the first place, and has been this way + for at least a decade prior, and was changed to return to this behaviour + shortly after the release of coreutils that introduced statx() that + caused automounts to occur. + + It is unlikely any system administrators are relying on the behaviour + found in jammy in any scripts or day to day operations that would be + adversely affected by the change. The worst case scenario is that a user + doing an 'ls -l' on an unmounted disk finds the mount doesn't + automatically occur, and they have to attach the disk and issue the + mount themselves. + + If a regression were to occur, it would be limited to the ls and stat + commands, specifically when listing directories linked to autofs + mountpoints. + + [Other info] + + The automount behaviour change was introduced upstream in version 8.32, + with the introduction of the statx() call. This means only Jammy is + affected. + + It was quickly reverted back to how it was originally in version 9.1, + which is already available in Mantic and onward. + + The commits that solve the issue are: + + commit 85c975df2c25bd799370b04bb294e568e001102f + From: Rohan Sable + Date: Mon, 7 Mar 2022 14:14:13 + + Subject: ls: avoid triggering automounts + Link:
[Touch-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
kgeotag is also affected by #2052491 -- 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/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: In Progress Status in apparmor package in Ubuntu: Confirmed Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Confirmed Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in falkon package in Ubuntu: Fix Released Status in freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kgeotag package in Ubuntu: Confirmed Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: In Progress Status in kontact package in Ubuntu: In Progress Status in marble package in Ubuntu: In Progress Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Confirmed Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Confirmed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: In Progress Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akregator/+bug/2046844/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
** Also affects: kgeotag (Ubuntu) Importance: Undecided Status: New ** Changed in: kgeotag (Ubuntu) Status: New => Confirmed -- 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/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: In Progress Status in apparmor package in Ubuntu: Confirmed Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Confirmed Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in falkon package in Ubuntu: Fix Released Status in freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kgeotag package in Ubuntu: Confirmed Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: In Progress Status in kontact package in Ubuntu: In Progress Status in marble package in Ubuntu: In Progress Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Confirmed Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Confirmed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: In Progress Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akregator/+bug/2046844/+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 2051541] Re: unattended-upgrades ftbfs with Python 3.12 as default
This bug was fixed in the package unattended-upgrades - 2.9.1+nmu4ubuntu1 --- unattended-upgrades (2.9.1+nmu4ubuntu1) noble; urgency=medium * Merge from Debian unstable. Remaining changes: - kernel/postinst.d/unattended-upgrades: check to see if canonical- livepatch is installed and enabled. In the event that it is and it says a reboot is required do not update reboot-required files so that only one reboot message appears in the message of the day. - d/t/control: Restrict kernel-patterns test to isolation-machine as the test assumes a meaningful link between the running kernel and the archive - Make debian/tests/test-systemd.py and test/autopkgtest_kernel_patterns.py executable again * tests/test_pep484.py, tests/test_pyflakes.py: Add a faux test to make sure we don't fail the test suite because the only test in the file was skipped... (LP: #2051541) unattended-upgrades (2.9.1+nmu4) unstable; urgency=medium * Non-maintainer upload. * Don't run pyflakes, it dropped support for type comments. (Closes: #1058172) -- Julian Andres Klode Mon, 12 Feb 2024 18:50:35 +0100 ** Changed in: unattended-upgrades (Ubuntu Noble) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/2051541 Title: unattended-upgrades ftbfs with Python 3.12 as default Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Noble: Fix Released Bug description: [...] Running ./test_pep484.py with python3 s -- Ran 0 tests in 0.000s NO TESTS RAN (skipped=1) make[2]: *** [Makefile:9: check] Error 5 make[2]: Leaving directory '/<>/test' make[1]: *** [debian/rules:16: override_dh_auto_test] Error 2 5 is a new exit value when all tests are skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2051541/+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 2051181] Re: apt cannot upgrade packages if the current security version is same as updates
** Tags added: foundations-todo ** Changed in: apt (Ubuntu) Importance: Undecided => Critical ** Changed in: apt (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: apt (Ubuntu) Status: New => In Progress ** Changed in: apt (Ubuntu) Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2051181 Title: apt cannot upgrade packages if the current security version is same as updates Status in apt package in Ubuntu: Triaged Bug description: When I finished installation with Jammy 22.04.3, I noticed that nvidia-driver-535 cannot be upgrade by either `apt upgrade` nor `apt dist-upgrade`. Below is the log of apt upgrade: ubuntu@ubuntu:~$ sudo apt -o Debug::pkgProblemResolver=1 upgrade --dry-run [2/1878] Reading package lists... Done Building dependency tree... Done Reading state information... Done Entering ResolveByKeep 10% Dependencies are not satisfied for nvidia-driver-535:amd64 < 535.129.03-0ubuntu0.22.04.1 | 535.154.05-0ubuntu0.22.04.1 @ii pumH NPb Ib > Package nvidia-driver-535:amd64 nvidia-driver-535:amd64 Depends on nvidia-dkms-535:amd64 < none | 535.154.05-0ubuntu0.22.04.1 @un umH > (<= 535.129.03-1) Keeping Package linux-modules-nvidia-535-oem-22.04c:amd64 due to Depends Dependencies are not satisfied for linux-modules-nvidia-535-oem-22.04c:amd64 < 6.1.0-1027.27 | 6.1.0-1028.28+2 @ii umH Ib > Keeping package linux-modules-nvidia-535-oem-22.04c:amd64 Dependencies are not satisfied for linux-modules-nvidia-535-oem-22.04c:amd64 < 6.1.0-1027.27 | 6.1.0-1028.28+2 @ii umH Ib > Package linux-modules-nvidia-535-oem-22.04c:amd64 linux-modules-nvidia-535-oem-22.04c:amd64 Depends on linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 -> 6.1.0-1027.27+1 @ii umU Ib > (= 6.1.0-1027.27) Keeping Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 due to Depends Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1028-oem:amd64 < none -> 6.1.0-1028.28+2 @un uN Ib > Keeping package linux-modules-nvidia-535-6.1.0-1028-oem:amd64 Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib > Keeping package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib > Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 linux-modules-nvidia-535-6.1.0-1027-oem:amd64 Depends on linux-signatures-nvidia-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 -> 6.1.0-1027.27+1 @ii umU > (= 6.1.0-1027.27) Keeping Package linux-signatures-nvidia-6.1.0-1027-oem:amd64 due to Depends Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib > Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib > Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib > Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 linux-modules-nvidia-535-6.1.0-1027-oem:amd64 Depends on linux-objects-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 -> 6.1.0-1027.27+1 @ii umU > (= 6.1.0-1027.27) Keeping Package linux-objects-nvidia-535-6.1.0-1027-oem:amd64 due to Depends https://pastebin.canonical.com/p/7frwTKZG6D/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2051181/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
John, The version in the PPA is now older than the version in the repository so no further testing can be done unless the changes in the PPA have now been uploaded (?). That said, regarding electron apps, it does appear as though the .deb versions of Visual Studio Code and Element Desktop are affected. Granted, those are installed from outside the repository, but I'd contend those are applications a gigantic part of the user base depends on. In fact, for Element, that's something the Ubuntu Community will be relying on in short order. The only workarounds for these are to install the snap versions or launch with `--no-sandbox`. In Element's case, it's maintained by a third party, so that's the only factor I can see as being problematic. -- 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/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: In Progress Status in apparmor package in Ubuntu: Confirmed Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Confirmed Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in falkon package in Ubuntu: Fix Released Status in freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: In Progress Status in kontact package in Ubuntu: In Progress Status in marble package in Ubuntu: In Progress Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Confirmed Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Confirmed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: In Progress Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akregator/+bug/2046844/+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 2052959] [NEW] FTBFS when rebuilding 1.44
Public bug reported: FTBFS due to test failure after an unrelated autopkgtest change was uploaded (https://launchpad.net/ubuntu/+source/network- manager/1.44.2-7ubuntu2). ok 7 /config/warnings PASS: src/core/tests/config/test-config 7 /config/warnings # (src/core/tests/config/test-config.c:1107) invalid value in config-data .intern.with-whitespace.key2 = (null) (instead of " b c\, d ") exec "./src/core/tests/config/test-config" failed with exit code 133 ERROR: src/core/tests/config/test-config - too few tests run (expected 14, got 7) ERROR: src/core/tests/config/test-config - exited with status 5 See upstream bug report: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1465 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse -- 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/2052959 Title: FTBFS when rebuilding 1.44 Status in network-manager package in Ubuntu: New Bug description: FTBFS due to test failure after an unrelated autopkgtest change was uploaded (https://launchpad.net/ubuntu/+source/network- manager/1.44.2-7ubuntu2). ok 7 /config/warnings PASS: src/core/tests/config/test-config 7 /config/warnings # (src/core/tests/config/test-config.c:1107) invalid value in config-data .intern.with-whitespace.key2 = (null) (instead of " b c\, d ") exec "./src/core/tests/config/test-config" failed with exit code 133 ERROR: src/core/tests/config/test-config - too few tests run (expected 14, got 7) ERROR: src/core/tests/config/test-config - exited with status 5 See upstream bug report: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1465 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2052959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051672] Re: Merge iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable (main)
I hope that's OK if I put the 24.04's feature freeze as milestone. ** Changed in: iproute2 (Ubuntu) Milestone: None => ubuntu-24.04-feature-freeze -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: Merge iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable (main) Status in iproute2 package in Ubuntu: New Bug description: A few versions have been released and Ubuntu Noble still has the 6.1 version (6.1.0-1ubuntu2) from one year ago. Could it be possible to import the latest version from Debian unstable fixing a bunch of issues and supporting features from more recent kernels? Please note that Ubuntu Noble 24.04 will probably be shipped with the v6.8 kernel [1]. IPRoute v6.1 supports features added up to the v6.1 kernel, so missing the ones added to earlier versions. Switching to the v6.7 now should ease the upgrade to the v6.8 later. [1] https://discourse.ubuntu.com/t/introducing-kernel-6-8-for- the-24-04-noble-numbat-release/41958 Upstream ChangeLog: - 6.2: https://lore.kernel.org/netdev/20230220105811.674bd304@hermes.local/ - 6.3: https://lore.kernel.org/netdev/20230427090253.7a92616b@hermes.local/ - 6.4: https://lore.kernel.org/netdev/20230626093137.2f302acc@hermes.local/ - 6.5: https://lore.kernel.org/netdev/20230906093918.394a1b1d@hermes.local/ - 6.6: https://lore.kernel.org/netdev/20231106090325.07092c87@hermes.local/ - 6.7: https://lore.kernel.org/netdev/20240108094709.050e22bc@hermes.local/ (Previous changelog: https://lore.kernel.org/netdev/?q=s%3A%22%5BANNOUNCE%5D+iproute2%22+AND+NOT+s%3A%22Re%3A%22 ) ChangeLog from Debian: iproute2 (6.7.0-2) unstable; urgency=medium * Backport fix for 'ss' output -- Luca Boccassi <> Mon, 22 Jan 2024 12:24:29 + iproute2 (6.7.0-1) unstable; urgency=medium * Add Italian debconf translation (Closes: #1056582) * Update upstream source from tag 'upstream/6.7.0' * Bump copyright year ranges in d/copyright * Drop 0002-Revert-Makefile-ensure-CONF_USR_DIR-honours-the-libd.patch, merged upstream * Default config files moved from /usr/lib to /usr/share -- Luca Boccassi <> Fri, 12 Jan 2024 21:47:59 + iproute2 (6.6.0-1) unstable; urgency=medium * Update upstream source from tag 'upstream/6.6.0' * Backport patch to fix configuration installation * Remove handling of qt_atm.so, dropped upstream -- Luca Boccassi <> Sun, 05 Nov 2023 22:46:20 + iproute2 (6.5.0-5) unstable; urgency=medium * Use dh-sequence-movetousr -- Luca Boccassi <> Tue, 24 Oct 2023 15:24:01 +0100 iproute2 (6.5.0-4) unstable; urgency=medium * postinst: handle legacy config files only when upgrading from previous versions that shipped them * postinst: ensure that locally modified legacy config files are preserved as overrides on upgrade (Closes: #1051577) * Note configuration files location changes in NEWS -- Luca Boccassi <> Sat, 16 Sep 2023 18:58:51 +0100 iproute2 (6.5.0-3) unstable; urgency=medium * Remove further leftovers as part of upstream's move of config to /usr (Closes: #1051577) -- Luca Boccassi <> Mon, 11 Sep 2023 09:42:12 +0100 iproute2 (6.5.0-2) unstable; urgency=medium * Add maintscript to remove conffiles that upstream has moved to /usr (Closes: #1051577) -- Luca Boccassi <> Sun, 10 Sep 2023 21:28:28 +0100 iproute2 (6.5.0-1) unstable; urgency=medium [ Luca Boccassi ] * Use wildcard for Lintian overrides [ Peter Kvillegård ] * Add Swedish translation of debconf messages (Closes: #1050442) [ Luca Boccassi ] * Update upstream source from tag 'upstream/6.5.0' * Use cap_bpf instead of cap_sys_admin for ip vrf-exec * Package-provided config files are now shipped in /usr/iproute2 instead of /etc/iproute2 -- Luca Boccassi <> Sat, 09 Sep 2023 16:32:54 +0100 iproute2 (6.4.0-1) unstable; urgency=medium * Fix patch header Forwarded field * Enable ELF metadata stamping * Update upstream source from tag 'upstream/6.4.0' * Update Lintian overrides -- Luca Boccassi <> Fri, 30 Jun 2023 12:16:40 +0100 iproute2 (6.3.0-1) unstable; urgency=medium * Drop obsolete conflicts/replaces * Update upstream source from tag 'upstream/6.3.0' -- Luca Boccassi <> Tue, 13 Jun 2023 23:49:37 +0100 iproute2 (6.1.0-3) unstable; urgency=medium * Ensure 'ip mo' resolves to 'ip monitor' (Closes: #1036534) -- Luca Boccassi <> Mon, 22 May 2023 14:19:52 +0100 iproute2 (6.1.0-2) unstable; urgency=medium * Add Romanian language translation for debconf (Closes: #1031917) * Bump Standards-Version to 4.6.2, no changes * Bump d/copyright year range -- Luca Boccassi <> Sat, 25 Feb 2023 19:46:35 + To manage notifications about this bug go to:
[Touch-packages] [Bug 2036761] Re: [mantic] ppa-purge no longer purges what add-apt-repository adds
I wrote a fix and did a merge request adding deb822 support for ppa-purge. I did a test using the oibaf ppa in a mantic lxc container to verify the fix. Also this issue should also be affecting noble but I only tested the fix on mantic for now. ** Changed in: ppa-purge (Ubuntu) Assignee: (unassigned) => Ghadi Rahme (ghadi-rahme) ** Changed in: ppa-purge (Ubuntu Mantic) Assignee: (unassigned) => Ghadi Rahme (ghadi-rahme) -- 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/2036761 Title: [mantic] ppa-purge no longer purges what add-apt-repository adds Status in ppa-purge package in Ubuntu: Triaged Status in software-properties package in Ubuntu: Confirmed Status in ppa-purge source package in Mantic: Triaged Status in software-properties source package in Mantic: Confirmed Bug description: Test Case - From Ubuntu 23.10: sudo apt install hello sudo add-apt-repository ppa:jbicha/temp sudo apt upgrade apt policy hello sudo ppa-purge ppa:jbicha/temp apt policy hello reveals that the PPA version of hello is still installed Also /etc/apt/sources.list.d/jbicha-ubuntu-temp-mantic.sources is still present and active What Should Happen -- ppa-purge should disable the PPA and reinstall any PPA packages with the version apt currently sees. Background -- add-apt-repository creates deb822 sources lists, starting in Ubuntu 23.10 https://discourse.ubuntu.com/t/spec-apt-deb822-sources-by- default/29333 Other Info -- add-apt-repository has a --remove option But it does not do the reinstall part which is important Honestly, that feature is so important, I suggest that add-apt-repository take over the functionality of ppa-purge so that we always get the ppa-purge behavior To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761/+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 2036761] Re: [mantic] ppa-purge no longer purges what add-apt-repository adds
** Merge proposal linked: https://code.launchpad.net/~ghadi-rahme/ubuntu/+source/ppa-purge/+git/ppa-purge/+merge/460394 -- 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/2036761 Title: [mantic] ppa-purge no longer purges what add-apt-repository adds Status in ppa-purge package in Ubuntu: Triaged Status in software-properties package in Ubuntu: Confirmed Status in ppa-purge source package in Mantic: Triaged Status in software-properties source package in Mantic: Confirmed Bug description: Test Case - From Ubuntu 23.10: sudo apt install hello sudo add-apt-repository ppa:jbicha/temp sudo apt upgrade apt policy hello sudo ppa-purge ppa:jbicha/temp apt policy hello reveals that the PPA version of hello is still installed Also /etc/apt/sources.list.d/jbicha-ubuntu-temp-mantic.sources is still present and active What Should Happen -- ppa-purge should disable the PPA and reinstall any PPA packages with the version apt currently sees. Background -- add-apt-repository creates deb822 sources lists, starting in Ubuntu 23.10 https://discourse.ubuntu.com/t/spec-apt-deb822-sources-by- default/29333 Other Info -- add-apt-repository has a --remove option But it does not do the reinstall part which is important Honestly, that feature is so important, I suggest that add-apt-repository take over the functionality of ppa-purge so that we always get the ppa-purge behavior To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761/+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 2052930] Re: liblocale-gettext-perl autopkgtests fail against glibc 2.39
Cf. the upstream issue for Perl-Locale-gettext at https://github.com/vandry/Perl-Locale-gettext/issues/7 ** No longer affects: glibc -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to liblocale-gettext-perl in Ubuntu. https://bugs.launchpad.net/bugs/2052930 Title: liblocale-gettext-perl autopkgtests fail against glibc 2.39 Status in glibc package in Ubuntu: Triaged Status in liblocale-gettext-perl package in Ubuntu: New Bug description: The autopkgtests for liblocale-gettext-perl fail against glibc 2.39 with the following errors: autopkgtest [15:27:03]: test autodep8-perl-build-deps: [--- 243s t/bind.t ... 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:02 2024 243s # Current time GMT: Wed Feb 7 15:27:02 2024 243s # Using Test.pm version 1.31 243s ok 1 243s ok 243s t/frconvert.t .. 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:02 2024 243s # Current time GMT: Wed Feb 7 15:27:02 2024 243s # Using Test.pm version 1.31 243s not ok 1 243s # Failed test 1 in t/frconvert.t at line 22 243s # t/frconvert.t line 22 is: ok(0); 243s Failed 1/1 subtests 243s t/jaconvert.t .. 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s test 243s not ok 1 243s # Failed test 1 in t/jaconvert.t at line 23 243s # t/jaconvert.t line 23 is: ok(0); 243s Failed 1/1 subtests 243s t/raw.t 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s not ok 1 243s # Failed test 1 in t/raw.t at line 14 243s # t/raw.t line 14 is: ok(0); 243s Failed 1/1 subtests 243s t/use.t 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s ok 1 243s ok 243s 243s Test Summary Report 243s --- 243s t/frconvert.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s t/jaconvert.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s t/raw.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s Files=5, Tests=5, 1 wallclock secs ( 0.03 usr 0.01 sys + 0.09 cusr 0.07 csys = 0.20 CPU) 243s Result: FAIL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2052930/+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 2052930] Re: liblocale-gettext-perl autopkgtests fail against glibc 2.39
** Bug watch added: github.com/vandry/Perl-Locale-gettext/issues #7 https://github.com/vandry/Perl-Locale-gettext/issues/7 ** Also affects: glibc via https://github.com/vandry/Perl-Locale-gettext/issues/7 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to liblocale-gettext-perl in Ubuntu. https://bugs.launchpad.net/bugs/2052930 Title: liblocale-gettext-perl autopkgtests fail against glibc 2.39 Status in glibc package in Ubuntu: Triaged Status in liblocale-gettext-perl package in Ubuntu: New Bug description: The autopkgtests for liblocale-gettext-perl fail against glibc 2.39 with the following errors: autopkgtest [15:27:03]: test autodep8-perl-build-deps: [--- 243s t/bind.t ... 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:02 2024 243s # Current time GMT: Wed Feb 7 15:27:02 2024 243s # Using Test.pm version 1.31 243s ok 1 243s ok 243s t/frconvert.t .. 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:02 2024 243s # Current time GMT: Wed Feb 7 15:27:02 2024 243s # Using Test.pm version 1.31 243s not ok 1 243s # Failed test 1 in t/frconvert.t at line 22 243s # t/frconvert.t line 22 is: ok(0); 243s Failed 1/1 subtests 243s t/jaconvert.t .. 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s test 243s not ok 1 243s # Failed test 1 in t/jaconvert.t at line 23 243s # t/jaconvert.t line 23 is: ok(0); 243s Failed 1/1 subtests 243s t/raw.t 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s not ok 1 243s # Failed test 1 in t/raw.t at line 14 243s # t/raw.t line 14 is: ok(0); 243s Failed 1/1 subtests 243s t/use.t 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s ok 1 243s ok 243s 243s Test Summary Report 243s --- 243s t/frconvert.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s t/jaconvert.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s t/raw.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s Files=5, Tests=5, 1 wallclock secs ( 0.03 usr 0.01 sys + 0.09 cusr 0.07 csys = 0.20 CPU) 243s Result: FAIL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2052930/+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 2052722] Re: systemd should package libnss-myhostname
libnss-myhostname is packaged in Ubuntu. It's just not installed by default. ** 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/2052722 Title: systemd should package libnss-myhostname Status in systemd package in Ubuntu: Invalid Bug description: Ubuntu generally decided not to use libnss-myhostname in 2014, due to: https://bugs.launchpad.net/ubuntu/+source/libnss- myhostname/+bug/1162478/comments/6 which says "I don't agree that libnss-myhostname is a technically sound approach, *period*; it works at cross-purposes to the existing Debian handling of the hostname being resolved to 127.0.1.1 via /etc/hosts. There should be a plan for aligning these, across *all* systems, not just desktop systems." While this may well have made sense in 2014, I think it's no longer the right decision in light of widespread adoption of containers. Container managers (Docker, Podman, systemd-nspawm, etc) generally set the container's hostname from _outside_ the container, either by bind- mounting over /etc/hostname or by simply not having /etc/hostname. In either case, the hostname of the container cannot be reliably predicted based on the contents of the container image, and editing /etc/hosts inside the container to make the hostname resolvable is fragile at best. While other solutions exist (arranging for the container manager to make sure that the container's hostname is resolvable from inside the container), libnss-myhostname offers users a straightforward way to allow the container's hostname to be resolved. Please reconsider packaging it. Debian packages libnss-myhostname. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2052722/+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 2052951] Re: ncurses/i386 autopkgtest failure
This test is new in the latest proposed version, and is incompatible with cross-arch Ubuntu i386 autopkgtest, so the following patch just disables it. ** Patch added: "1-6.4+20240113-1ubuntu1.diff" https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/2052951/+attachment/5745955/+files/1-6.4+20240113-1ubuntu1.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/2052951 Title: ncurses/i386 autopkgtest failure Status in ncurses package in Ubuntu: New Bug description: ncurses fails to pass its autopkgtests on i386: https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- noble/noble/i386/n/ncurses/20240212_101858_8f6ad@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/2052951/+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 2052951] [NEW] ncurses/i386 autopkgtest failure
Public bug reported: ncurses fails to pass its autopkgtests on i386: https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- noble/noble/i386/n/ncurses/20240212_101858_8f6ad@/log.gz ** Affects: ncurses (Ubuntu) Importance: Undecided Status: New ** Description changed: - ncurses fails to pass it's autopkgtests on i386: + ncurses fails to pass its autopkgtests on i386: https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- noble/noble/i386/n/ncurses/20240212_101858_8f6ad@/log.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/2052951 Title: ncurses/i386 autopkgtest failure Status in ncurses package in Ubuntu: New Bug description: ncurses fails to pass its autopkgtests on i386: https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- noble/noble/i386/n/ncurses/20240212_101858_8f6ad@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/2052951/+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 2052137] Re: bonded link goes down on reconfigure
Looks like this has been fixed in upstream systemd, so there's probably not a lot that we can do on the Netplan side. ** Changed in: netplan.io (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/2052137 Title: bonded link goes down on reconfigure Status in systemd: Fix Released Status in netplan.io package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: systemd-networkd brings down member interfaces of a bond when they get reconfigured Jan 31 15:43:46 unique-slug systemd-networkd[2430]: pn1: Bringing link down This has a result that a server has complete downtime for a few seconds, this has also been reported upstream https://github.com/systemd/systemd/issues/31165. A pull request has been opened to fix this https://github.com/systemd/systemd/pull/31172 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/2052137/+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 1995790] Re: regression: ?garbage does not work correctly in install commands
** Tags removed: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1995790 Title: regression: ?garbage does not work correctly in install commands Status in apt package in Ubuntu: Fix Released Status in apt source package in Jammy: Triaged Status in apt source package in Lunar: Won't Fix Status in apt source package in Mantic: Triaged Status in apt source package in Noble: Fix Released Bug description: The awesome apt has a some wonderful tips on their EXAMPLES section (printed below). The choice of name to "garbage" might not have been the best but the function is extremely useful. $ man apt-patterns | sed '/EXAMPLES/,/^[^ ]/!d;/^[^ ]/d' apt remove ?garbage Remove all packages that are automatically installed and no longer needed - same as apt autoremove apt purge ?config-files Purge all packages that only have configuration files left apt list '~i !~M (~slibs|~sperl|~spython)' List all manually-installed packages in sections matching libs, perl, or python. Lets mark a package as automatically installed, and use the examples. $ sudo apt-mark auto shotwell shotwell set to automatically installed. $ sudo apt remove ?garbage Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: libraw20 shotwell shotwell-common Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt autoremove Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: libraw20 shotwell shotwell-common 0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded. After this operation, 9.806 kB disk space will be freed. Do you want to continue? [Y/n] N Abort. Apt-patterns works as it should everywhere else, as far as I can see, it works wonders with ie `apt list '~g|~c'` and many other applications. I used `apt purge '~g|~c'` successfully in Ubuntu 20.04 for years, so I feel this is a regression. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apt 2.4.8 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 6 10:57:52 2022 SourcePackage: apt UpgradeStatus: Upgraded to jammy on 2022-03-26 (224 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1995790/+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 2046336] Re: initramfs-tools: After updating coreutils cp: not replacing in console when running update-initramfs
** Changed in: klibc (Debian) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/2046336 Title: initramfs-tools: After updating coreutils cp: not replacing in console when running update-initramfs Status in klibc package in Ubuntu: Fix Released Status in klibc package in Debian: Fix Committed Bug description: Imported from Debian bug http://bugs.debian.org/1055694: Package: initramfs-tools Version: 0.142 Severity: normal X-Debbugs-Cc: konomikit...@gmail.com Dear Maintainer, After updating coreutils from 9.1-1 to 9.4-1+b1 the following lines appear when running update-initramfs -u: cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/cat' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/cpio' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/dd' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/dmesg' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/false' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/gunzip' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/kill' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/ln' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/ls' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mkdir' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mkfifo' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mknod' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mount' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mv' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/nuke' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/readlink' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/resume' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sh' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sleep' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sync' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/true' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/umount' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/uname' The lines seem to be a cosmetic issue only, but I cannot be entirely sure. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 78M Nov 10 19:13 /boot/initrd.img-6.5.0-3-amd64 -rw-r--r-- 1 root root 78M Nov 10 19:13 /boot/initrd.img-6.5.0-4-amd64 -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.5.0-4-amd64 root=UUID=e7b71052-3dff-454b-9730-7b146ebdf115 ro preempt=full quiet -- /proc/filesystems btrfs fuseblk vfat -- lsmod Module Size Used by tcp_diag 12288 0 inet_diag 28672 1 tcp_diag vboxnetadp 28672 0 vboxnetflt 40960 0 vboxdrv 716800 2 vboxnetadp,vboxnetflt nvme_fabrics 32768 0 ccm20480 9 rfcomm102400 16 snd_seq_dummy 12288 0 snd_hrtimer12288 1 snd_seq 114688 7 snd_seq_dummy qrtr 57344 4 cmac 12288 3 algif_hash 12288 1 algif_skcipher 12288 1 af_alg 36864 6 algif_hash,algif_skcipher bnep 36864 2 zstd 12288 12 zram 40960 2 zsmalloc 36864 1 zram btusb 81920 0 btrtl 28672 1 btusb btbcm 24576 1 btusb intel_rapl_msr 20480 0 btintel57344 1 btusb intel_rapl_common 36864 1 intel_rapl_msr btmtk 12288 1 btusb binfmt_misc28672 1 bluetooth1126400 44 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm edac_mce_amd 40960 0 kvm_amd 184320 0 iwlmvm589824 0 kvm 1359872 1 kvm_amd mac80211 1392640 1 iwlmvm sha3_generic 16384 1 jitterentropy_rng 20480 1 snd_hda_codec_realtek 192512 1 irqbypass 12288 1 kvm snd_hda_codec_generic 114688 1 snd_hda_codec_realtek ledtrig_audio 12288 1 snd_hda_codec_generic snd_hda_codec_hdmi 90112 1 libarc412288 1 mac80211 ghash_clmulni_intel16384 0 sha512_ssse3 53248 1 snd_hda_intel 61440 4 sha512_generic 16384 1 sha512_ssse3 snd_usb_audio 417792 3 ctr12288 3 snd_intel_dspcfg 32768 1 snd_hda_intel snd_usbmidi_lib49152 1 snd_usb_audio snd_intel_sdw_acpi 16384 1 snd_intel_dspcfg drbg 49152 1 snd_rawmidi53248 1 snd_usbmidi_lib aesni_intel 360448 10 ansi_cprng 12288 0 iwlwifi 544768 1 iwlmvm snd_hda_codec 225280 4
[Touch-packages] [Bug 1956110] Re: upower requires libimobiledevice6 as a dependency
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: libimobiledevice (Ubuntu) Status: New => Incomplete ** Changed in: upower (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1956110 Title: upower requires libimobiledevice6 as a dependency Status in libimobiledevice package in Ubuntu: Incomplete Status in upower package in Ubuntu: Incomplete Bug description: An iPhone library is required to have power management required by Gnome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1956110/+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 2052930] Re: liblocale-gettext-perl autopkgtests fail against glibc 2.39
** Tags added: foundations-todo ** Changed in: glibc (Ubuntu) Assignee: (unassigned) => Simon Chopin (schopin) ** Changed in: glibc (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to liblocale-gettext-perl in Ubuntu. https://bugs.launchpad.net/bugs/2052930 Title: liblocale-gettext-perl autopkgtests fail against glibc 2.39 Status in glibc package in Ubuntu: Triaged Status in liblocale-gettext-perl package in Ubuntu: New Bug description: The autopkgtests for liblocale-gettext-perl fail against glibc 2.39 with the following errors: autopkgtest [15:27:03]: test autodep8-perl-build-deps: [--- 243s t/bind.t ... 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:02 2024 243s # Current time GMT: Wed Feb 7 15:27:02 2024 243s # Using Test.pm version 1.31 243s ok 1 243s ok 243s t/frconvert.t .. 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:02 2024 243s # Current time GMT: Wed Feb 7 15:27:02 2024 243s # Using Test.pm version 1.31 243s not ok 1 243s # Failed test 1 in t/frconvert.t at line 22 243s # t/frconvert.t line 22 is: ok(0); 243s Failed 1/1 subtests 243s t/jaconvert.t .. 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s test 243s not ok 1 243s # Failed test 1 in t/jaconvert.t at line 23 243s # t/jaconvert.t line 23 is: ok(0); 243s Failed 1/1 subtests 243s t/raw.t 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s not ok 1 243s # Failed test 1 in t/raw.t at line 14 243s # t/raw.t line 14 is: ok(0); 243s Failed 1/1 subtests 243s t/use.t 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s ok 1 243s ok 243s 243s Test Summary Report 243s --- 243s t/frconvert.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s t/jaconvert.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s t/raw.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s Files=5, Tests=5, 1 wallclock secs ( 0.03 usr 0.01 sys + 0.09 cusr 0.07 csys = 0.20 CPU) 243s Result: FAIL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2052930/+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 2052930] [NEW] liblocale-gettext-perl autopkgtests fail against glibc 2.39
Public bug reported: The autopkgtests for liblocale-gettext-perl fail against glibc 2.39 with the following errors: autopkgtest [15:27:03]: test autodep8-perl-build-deps: [--- 243s t/bind.t ... 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:02 2024 243s # Current time GMT: Wed Feb 7 15:27:02 2024 243s # Using Test.pm version 1.31 243s ok 1 243s ok 243s t/frconvert.t .. 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:02 2024 243s # Current time GMT: Wed Feb 7 15:27:02 2024 243s # Using Test.pm version 1.31 243s not ok 1 243s # Failed test 1 in t/frconvert.t at line 22 243s # t/frconvert.t line 22 is: ok(0); 243s Failed 1/1 subtests 243s t/jaconvert.t .. 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s test 243s not ok 1 243s # Failed test 1 in t/jaconvert.t at line 23 243s # t/jaconvert.t line 23 is: ok(0); 243s Failed 1/1 subtests 243s t/raw.t 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s not ok 1 243s # Failed test 1 in t/raw.t at line 14 243s # t/raw.t line 14 is: ok(0); 243s Failed 1/1 subtests 243s t/use.t 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s ok 1 243s ok 243s 243s Test Summary Report 243s --- 243s t/frconvert.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s t/jaconvert.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s t/raw.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s Files=5, Tests=5, 1 wallclock secs ( 0.03 usr 0.01 sys + 0.09 cusr 0.07 csys = 0.20 CPU) 243s Result: FAIL ** Affects: glibc (Ubuntu) Importance: Undecided Status: Triaged ** Affects: liblocale-gettext-perl (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Also affects: liblocale-gettext-perl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to liblocale-gettext-perl in Ubuntu. https://bugs.launchpad.net/bugs/2052930 Title: liblocale-gettext-perl autopkgtests fail against glibc 2.39 Status in glibc package in Ubuntu: Triaged Status in liblocale-gettext-perl package in Ubuntu: New Bug description: The autopkgtests for liblocale-gettext-perl fail against glibc 2.39 with the following errors: autopkgtest [15:27:03]: test autodep8-perl-build-deps: [--- 243s t/bind.t ... 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:02 2024 243s # Current time GMT: Wed Feb 7 15:27:02 2024 243s # Using Test.pm version 1.31 243s ok 1 243s ok 243s t/frconvert.t .. 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:02 2024 243s # Current time GMT: Wed Feb 7 15:27:02 2024 243s # Using Test.pm version 1.31 243s not ok 1 243s # Failed test 1 in t/frconvert.t at line 22 243s # t/frconvert.t line 22 is: ok(0); 243s Failed 1/1 subtests 243s t/jaconvert.t .. 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s test 243s not ok 1 243s # Failed test 1 in t/jaconvert.t at line 23 243s # t/jaconvert.t line 23 is: ok(0); 243s Failed 1/1 subtests 243s t/raw.t 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s not ok 1 243s # Failed test 1 in t/raw.t at line 14 243s # t/raw.t line 14 is: ok(0); 243s Failed 1/1 subtests 243s t/use.t 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s ok 1 243s ok 243s 243s Test Summary Report 243s --- 243s t/frconvert.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s t/jaconvert.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s t/raw.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s Files=5,
[Touch-packages] [Bug 2047450] Re: tail emits no output for sysfs files when using large page kernels
This bug was fixed in the package coreutils - 9.1-1ubuntu2.23.10.1 --- coreutils (9.1-1ubuntu2.23.10.1) mantic; urgency=medium * d/p/tail-fix-tailing-sysfs-files-where-PAGE_SIZE-BUFSIZ.patch: Fix tailing of sysfs files on systems using a 64K page size. (LP: #2047450) -- dann frazier Sat, 06 Jan 2024 11:28:58 -0700 ** Changed in: coreutils (Ubuntu Mantic) Status: Fix Committed => Fix Released ** Changed in: coreutils (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 coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2047450 Title: tail emits no output for sysfs files when using large page kernels Status in coreutils package in Ubuntu: Fix Released Status in coreutils source package in Jammy: Fix Released Status in coreutils source package in Lunar: Won't Fix Status in coreutils source package in Mantic: Fix Released Status in coreutils source package in Noble: Fix Released Bug description: [Impact] Ubuntu provides 64K page size kernels for ppc64el (always) and arm64 (optional -64k flavors). When booted on 64K kernels, tail emits no output when tailing a sysfs file. The difference in behavior can be a source for bugs in scripts that use tail, and general user confusion. [Test Plan] The upstream fix includes a test case that tails the /sys/kernel/profiling file, if it exists. That case would fail with an unfixed coreutils package as shown below: = When booted on a 4K kernel = ubuntu@gunyolk:~$ tail /sys/kernel/profiling 0 = When booted on a 64K kernel = ubuntu@gunyolk:~$ tail /sys/kernel/profiling ubuntu@gunyolk:~$ Since the upstream test cases are executed at build time, the existing tests and this new test will be used to regression test behavior. This should cover both 4K (!ppc64el) and 64K (ppc64el) cases. We should also do a manual verification on arm64 w/ the 64K kernel since that case is not covered by our builders. [Where Problems Could Occur] The biggest risk for a regression I see is due to the side-effect of the fix now allocating a dynamic buffer instead of the stack. An error in logic there could cause a crash or a memory leak in scenarios undetected during testing. I used valgrind when developing the fix to derisk the memory leak scenario. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2047450/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2047450] Re: tail emits no output for sysfs files when using large page kernels
This bug was fixed in the package coreutils - 8.32-4.1ubuntu1.1 --- coreutils (8.32-4.1ubuntu1.1) jammy; urgency=medium * d/p/assure-new-macro-affirm.patch, d/p/tail-fix-tailing-sysfs-files-where-PAGE_SIZE-BUFSIZ.patch: Fix tailing of sysfs files on systems using a 64K page size. (LP: #2047450) -- dann frazier Mon, 08 Jan 2024 07:56:36 -0700 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2047450 Title: tail emits no output for sysfs files when using large page kernels Status in coreutils package in Ubuntu: Fix Released Status in coreutils source package in Jammy: Fix Released Status in coreutils source package in Lunar: Won't Fix Status in coreutils source package in Mantic: Fix Released Status in coreutils source package in Noble: Fix Released Bug description: [Impact] Ubuntu provides 64K page size kernels for ppc64el (always) and arm64 (optional -64k flavors). When booted on 64K kernels, tail emits no output when tailing a sysfs file. The difference in behavior can be a source for bugs in scripts that use tail, and general user confusion. [Test Plan] The upstream fix includes a test case that tails the /sys/kernel/profiling file, if it exists. That case would fail with an unfixed coreutils package as shown below: = When booted on a 4K kernel = ubuntu@gunyolk:~$ tail /sys/kernel/profiling 0 = When booted on a 64K kernel = ubuntu@gunyolk:~$ tail /sys/kernel/profiling ubuntu@gunyolk:~$ Since the upstream test cases are executed at build time, the existing tests and this new test will be used to regression test behavior. This should cover both 4K (!ppc64el) and 64K (ppc64el) cases. We should also do a manual verification on arm64 w/ the 64K kernel since that case is not covered by our builders. [Where Problems Could Occur] The biggest risk for a regression I see is due to the side-effect of the fix now allocating a dynamic buffer instead of the stack. An error in logic there could cause a crash or a memory leak in scenarios undetected during testing. I used valgrind when developing the fix to derisk the memory leak scenario. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2047450/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2049318] Update Released
The verification of the Stable Release Update for iptables has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/2049318 Title: [SRU] free(): double free detected in tcache 2 Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Jammy: Fix Released Bug description: [ Impact ] iptables is unable to list the iptables rules or save the iptables rules if a nftables ruleset is defined which iptables does not recognize. [ Test Plan ] 1. Simple test plan based on upstream test case: sudo nft -f - < rules.txt * Convert the rule to nftables ruleset - sudo iptables-nft-restore < rules.txt * List the nftables ruleset - sudo nft list ruleset * Also confirm that iptables can list the old rule - sudo iptables -L * Now add another nftables rule (this rule is taken from upstream test case) sudo nft -f -
[Touch-packages] [Bug 2049318] Re: [SRU] free(): double free detected in tcache 2
This bug was fixed in the package iptables - 1.8.7-1ubuntu5.2 --- iptables (1.8.7-1ubuntu5.2) jammy; urgency=medium * Apply upstream patch to fix a double free of unrecognized base-chains. (LP: #2049318) -- Sudip Mukherjee Tue, 16 Jan 2024 21:14:30 + ** Changed in: iptables (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 iptables in Ubuntu. https://bugs.launchpad.net/bugs/2049318 Title: [SRU] free(): double free detected in tcache 2 Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Jammy: Fix Released Bug description: [ Impact ] iptables is unable to list the iptables rules or save the iptables rules if a nftables ruleset is defined which iptables does not recognize. [ Test Plan ] 1. Simple test plan based on upstream test case: sudo nft -f - < rules.txt * Convert the rule to nftables ruleset - sudo iptables-nft-restore < rules.txt * List the nftables ruleset - sudo nft list ruleset * Also confirm that iptables can list the old rule - sudo iptables -L * Now add another nftables rule (this rule is taken from upstream test case) sudo nft -f -
[Touch-packages] [Bug 2039873] Re: [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases
This bug was fixed in the package lxc - 1:5.0.0~git2209-g5a7b9ce67-0ubuntu1.1 --- lxc (1:5.0.0~git2209-g5a7b9ce67-0ubuntu1.1) jammy; urgency=medium [ Dave Jones ] * Fix the LXC_DEVEL value to be 0 (LP: #2039873) - d/p/0002-Set-DEVEL-flag-post-release.patch added to force this value in the autoconf script [ Alexander Mikhalitsyn ] * Added autopkgtest to ensure that LXC_DEVEL is always 0 - debian/tests/no-devel: add "no-devel" autopkgtest script - debian/tests/control: declare "no-devel" autopkgtest -- Dave Jones Wed, 24 Jan 2024 16:26:06 + ** Changed in: lxc (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 lxc in Ubuntu. https://bugs.launchpad.net/bugs/2039873 Title: [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Jammy: Fix Released Status in lxc source package in Mantic: Fix Released Status in lxc source package in Noble: Fix Released Bug description: [ Impact ] LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release build we should have LXC_DEVEL=0. LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h and then can be (and actually it is) used by other projects to detect if liblxc-dev is a development build or stable. Having LXC_DEVEL=1 makes problems for the users who want to build projects those are depend on liblxc from source (for example, LXD, go-lxc: https://github.com/canonical/lxd/pull/12420). Q: Why it was not a problem for so long? A: Because LXC API was stable for a long time, but recently we have extended liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc was updated too (https://github.com/lxc/go-lxc/pull/166). This change was developed properly to be backward compatible with the old versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro check VERSION_AT_LEAST (https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7) is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release build of LXC. [ Test Plan ] Install liblxc-dev package and check /usr/include/lxc/version.h file LXC_DEVEL should be 0 [ Where problems could occur ] Theoretically, build of a software which depends on liblxc-dev may start to fail if it assumes that LXC_DEVEL is 1. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2047450] Update Released
The verification of the Stable Release Update for coreutils 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 coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2047450 Title: tail emits no output for sysfs files when using large page kernels Status in coreutils package in Ubuntu: Fix Released Status in coreutils source package in Jammy: Fix Committed Status in coreutils source package in Lunar: Won't Fix Status in coreutils source package in Mantic: Fix Released Status in coreutils source package in Noble: Fix Released Bug description: [Impact] Ubuntu provides 64K page size kernels for ppc64el (always) and arm64 (optional -64k flavors). When booted on 64K kernels, tail emits no output when tailing a sysfs file. The difference in behavior can be a source for bugs in scripts that use tail, and general user confusion. [Test Plan] The upstream fix includes a test case that tails the /sys/kernel/profiling file, if it exists. That case would fail with an unfixed coreutils package as shown below: = When booted on a 4K kernel = ubuntu@gunyolk:~$ tail /sys/kernel/profiling 0 = When booted on a 64K kernel = ubuntu@gunyolk:~$ tail /sys/kernel/profiling ubuntu@gunyolk:~$ Since the upstream test cases are executed at build time, the existing tests and this new test will be used to regression test behavior. This should cover both 4K (!ppc64el) and 64K (ppc64el) cases. We should also do a manual verification on arm64 w/ the 64K kernel since that case is not covered by our builders. [Where Problems Could Occur] The biggest risk for a regression I see is due to the side-effect of the fix now allocating a dynamic buffer instead of the stack. An error in logic there could cause a crash or a memory leak in scenarios undetected during testing. I used valgrind when developing the fix to derisk the memory leak scenario. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2047450/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2039873] Update Released
The verification of the Stable Release Update for lxc 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 lxc in Ubuntu. https://bugs.launchpad.net/bugs/2039873 Title: [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Jammy: Fix Committed Status in lxc source package in Mantic: Fix Released Status in lxc source package in Noble: Fix Released Bug description: [ Impact ] LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release build we should have LXC_DEVEL=0. LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h and then can be (and actually it is) used by other projects to detect if liblxc-dev is a development build or stable. Having LXC_DEVEL=1 makes problems for the users who want to build projects those are depend on liblxc from source (for example, LXD, go-lxc: https://github.com/canonical/lxd/pull/12420). Q: Why it was not a problem for so long? A: Because LXC API was stable for a long time, but recently we have extended liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc was updated too (https://github.com/lxc/go-lxc/pull/166). This change was developed properly to be backward compatible with the old versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro check VERSION_AT_LEAST (https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7) is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release build of LXC. [ Test Plan ] Install liblxc-dev package and check /usr/include/lxc/version.h file LXC_DEVEL should be 0 [ Where problems could occur ] Theoretically, build of a software which depends on liblxc-dev may start to fail if it assumes that LXC_DEVEL is 1. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2039873] Re: [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases
This bug was fixed in the package lxc - 1:5.0.1-0ubuntu8~23.10.1 --- lxc (1:5.0.1-0ubuntu8~23.10.1) mantic; urgency=medium [ Alexander Mikhalitsyn ] * Fix the LXC_DEVEL value to be 0 (LP: #2039873) - d/p/0003-meson-Set-DEVEL-flag-post-release.patch was dropped as it should not be in the production builds * Added autopkgtest to ensure that LXC_DEVEL is always 0 - debian/tests/no-devel: add "no-devel" autopkgtest script - debian/tests/control: declare "no-devel" autopkgtest -- Dave Jones Wed, 24 Jan 2024 16:25:47 + ** Changed in: lxc (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2039873 Title: [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Jammy: Fix Committed Status in lxc source package in Mantic: Fix Released Status in lxc source package in Noble: Fix Released Bug description: [ Impact ] LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release build we should have LXC_DEVEL=0. LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h and then can be (and actually it is) used by other projects to detect if liblxc-dev is a development build or stable. Having LXC_DEVEL=1 makes problems for the users who want to build projects those are depend on liblxc from source (for example, LXD, go-lxc: https://github.com/canonical/lxd/pull/12420). Q: Why it was not a problem for so long? A: Because LXC API was stable for a long time, but recently we have extended liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc was updated too (https://github.com/lxc/go-lxc/pull/166). This change was developed properly to be backward compatible with the old versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro check VERSION_AT_LEAST (https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7) is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release build of LXC. [ Test Plan ] Install liblxc-dev package and check /usr/include/lxc/version.h file LXC_DEVEL should be 0 [ Where problems could occur ] Theoretically, build of a software which depends on liblxc-dev may start to fail if it assumes that LXC_DEVEL is 1. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2052925] Re: lpoptions -d as root
Thanks, I'm closing for the current serie since it's fixed in Noble but we added it to the team backlog to SRU to Jammy ** Tags added: udeng-2281 ** Changed in: cups (Ubuntu) Status: New => Fix Released ** Changed in: cups (Ubuntu) Importance: Undecided => Low -- 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/2052925 Title: lpoptions -d as root Status in cups package in Ubuntu: Fix Released Bug description: Copied from https://github.com/OpenPrinting/cups/issues/454 Yair Yarom submitted Debian bug 1008053 and observed that running lpoptions as root does not update /etc/cups/lpoptions but /root/.cups/lpoptions. Running lpoptions as root (e.g. "lpoptions -d HP-OfficeJet") should update /etc/cups/lpoptions to be the defaults for all users. But instead it tries to update /root/.cups/lpoptions. This has been fixed upstream in cups, in debian sid, and mantic. Proposing to add this change in jammy and older (still supported) series as well. The fix is a one line change in https://github.com/OpenPrinting/cups/pull/456 Thanks. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu ubuntu@jammy-vm:~$ lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ubuntu@jammy-vm:~$ apt-cache policy cups cups: Installed: 2.4.1op1-1ubuntu4.7 Candidate: 2.4.1op1-1ubuntu4.7 Version table: *** 2.4.1op1-1ubuntu4.7 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 2.4.1op1-1ubuntu4 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What you expected to happen: root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color printer-commands=none printer-info=HP-Officejet-Pro-8710 printer-is-accepting-jobs=true printer-is-shared=true printer-is-temporary=false printer-location printer-make-and-model='HP Officejet Pro 8710, hpcups 3.21.12' printer-state=3 printer-state-change-time=1706800669 printer-state-reasons=none printer-type=4124 printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /etc/cups/lpoptions Default HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /root/.cups/lpoptions cat: /etc/cups/lpoptions: No such file or directory root@jammy-vm:~# 4) What happened instead: root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color printer-commands=none printer-info=HP-Officejet-Pro-8710 printer-is-accepting-jobs=true printer-is-shared=true printer-is-temporary=false printer-location printer-make-and-model='HP Officejet Pro 8710, hpcups 3.21.12' printer-state=3 printer-state-change-time=1706800669 printer-state-reasons=none printer-type=4124 printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /etc/cups/lpoptions cat: /etc/cups/lpoptions: No such file or directory root@jammy-vm:~# root@jammy-vm:~# cat /root/.cups/lpoptions Default HP-Officejet-Pro-8710 root@jammy-vm:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2052925/+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 2052925] Re: lpoptions -d as root
Upstream fix in debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008053 -- 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/2052925 Title: lpoptions -d as root Status in cups package in Ubuntu: Fix Released Bug description: Copied from https://github.com/OpenPrinting/cups/issues/454 Yair Yarom submitted Debian bug 1008053 and observed that running lpoptions as root does not update /etc/cups/lpoptions but /root/.cups/lpoptions. Running lpoptions as root (e.g. "lpoptions -d HP-OfficeJet") should update /etc/cups/lpoptions to be the defaults for all users. But instead it tries to update /root/.cups/lpoptions. This has been fixed upstream in cups, in debian sid, and mantic. Proposing to add this change in jammy and older (still supported) series as well. The fix is a one line change in https://github.com/OpenPrinting/cups/pull/456 Thanks. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu ubuntu@jammy-vm:~$ lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ubuntu@jammy-vm:~$ apt-cache policy cups cups: Installed: 2.4.1op1-1ubuntu4.7 Candidate: 2.4.1op1-1ubuntu4.7 Version table: *** 2.4.1op1-1ubuntu4.7 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 2.4.1op1-1ubuntu4 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What you expected to happen: root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color printer-commands=none printer-info=HP-Officejet-Pro-8710 printer-is-accepting-jobs=true printer-is-shared=true printer-is-temporary=false printer-location printer-make-and-model='HP Officejet Pro 8710, hpcups 3.21.12' printer-state=3 printer-state-change-time=1706800669 printer-state-reasons=none printer-type=4124 printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /etc/cups/lpoptions Default HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /root/.cups/lpoptions cat: /etc/cups/lpoptions: No such file or directory root@jammy-vm:~# 4) What happened instead: root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color printer-commands=none printer-info=HP-Officejet-Pro-8710 printer-is-accepting-jobs=true printer-is-shared=true printer-is-temporary=false printer-location printer-make-and-model='HP Officejet Pro 8710, hpcups 3.21.12' printer-state=3 printer-state-change-time=1706800669 printer-state-reasons=none printer-type=4124 printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /etc/cups/lpoptions cat: /etc/cups/lpoptions: No such file or directory root@jammy-vm:~# root@jammy-vm:~# cat /root/.cups/lpoptions Default HP-Officejet-Pro-8710 root@jammy-vm:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2052925/+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 2052925] [NEW] lpoptions -d as root
Public bug reported: Copied from https://github.com/OpenPrinting/cups/issues/454 Yair Yarom submitted Debian bug 1008053 and observed that running lpoptions as root does not update /etc/cups/lpoptions but /root/.cups/lpoptions. Running lpoptions as root (e.g. "lpoptions -d HP-OfficeJet") should update /etc/cups/lpoptions to be the defaults for all users. But instead it tries to update /root/.cups/lpoptions. This has been fixed upstream in cups, in debian sid, and mantic. Proposing to add this change in jammy and older (still supported) series as well. The fix is a one line change in https://github.com/OpenPrinting/cups/pull/456 Thanks. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu ubuntu@jammy-vm:~$ lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ubuntu@jammy-vm:~$ apt-cache policy cups cups: Installed: 2.4.1op1-1ubuntu4.7 Candidate: 2.4.1op1-1ubuntu4.7 Version table: *** 2.4.1op1-1ubuntu4.7 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 2.4.1op1-1ubuntu4 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What you expected to happen: root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color printer-commands=none printer-info=HP-Officejet-Pro-8710 printer-is-accepting-jobs=true printer-is-shared=true printer-is-temporary=false printer-location printer-make-and-model='HP Officejet Pro 8710, hpcups 3.21.12' printer-state=3 printer-state-change-time=1706800669 printer-state-reasons=none printer-type=4124 printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /etc/cups/lpoptions Default HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /root/.cups/lpoptions cat: /etc/cups/lpoptions: No such file or directory root@jammy-vm:~# 4) What happened instead: root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color printer-commands=none printer-info=HP-Officejet-Pro-8710 printer-is-accepting-jobs=true printer-is-shared=true printer-is-temporary=false printer-location printer-make-and-model='HP Officejet Pro 8710, hpcups 3.21.12' printer-state=3 printer-state-change-time=1706800669 printer-state-reasons=none printer-type=4124 printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /etc/cups/lpoptions cat: /etc/cups/lpoptions: No such file or directory root@jammy-vm:~# root@jammy-vm:~# cat /root/.cups/lpoptions Default HP-Officejet-Pro-8710 root@jammy-vm:~# ** Affects: cups (Ubuntu) Importance: Low Status: Fix Released ** Tags: udeng-2281 ** Attachment added: "strace of `lpoptions -d` as root" https://bugs.launchpad.net/bugs/2052925/+attachment/5745886/+files/strace.txt ** Description changed: Copied from https://github.com/OpenPrinting/cups/issues/454 - Yair Yarom submitted Debian bug #1008053 and observed that running + Yair Yarom submitted Debian bug 1008053 and observed that running lpoptions as root does not update /etc/cups/lpoptions but /root/.cups/lpoptions. - - Running lpoptions as root (e.g. "lpoptions -d HP-OfficeJet") should update /etc/cups/lpoptions to be the defaults for all users. But instead it tries to update /root/.cups/lpoptions. + Running lpoptions as root (e.g. "lpoptions -d HP-OfficeJet") should + update /etc/cups/lpoptions to be the defaults for all users. But instead + it tries to update /root/.cups/lpoptions. This has been fixed upstream in cups, in debian sid, and mantic. Proposing to add this change in jammy and older (still supported) series as well. The fix is a one line change in https://github.com/OpenPrinting/cups/pull/456 - Thanks. - 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu ubuntu@jammy-vm:~$ lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ubuntu@jammy-vm:~$ apt-cache policy
[Touch-packages] [Bug 2051358] Re: Start of systemd service on physical network devices using a udev rule has stopped working
After additional investigation our udev rule is installed in the initramfs and
with patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=00f86f0b20f794f30aabe7181912d2ec2207e292
the associated systemd service is never started when the OS starts.
We have created an initramfs hook script to remove our udev rule and now our
custom systemd service is starting properly when the OS starts.
Is this a side effect of above patch or is it something expected ?
--
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/2051358
Title:
Start of systemd service on physical network devices using a udev rule
has stopped working
Status in systemd package in Ubuntu:
New
Bug description:
Hi everyone,
We have an issue with latest version of systemd on Ubuntu 22.04
(249.11-0ubuntu3.12).
We have a udev rule running a service (custom wpa supplicant) on physical
wired network devices that is not working during boot process anymore.
The same rule works fine with a usb dongle when I unplug it and plug it back
after the machine has started.
```
ACTION=="add|move", SUBSYSTEM=="net", TAG+="systemd", ENV{DEVTYPE}!="wlan",
DEVPATH!="/devices/virtual/*",\
ENV{SYSTEMD_WANTS}+="supplicant-wired@$name.service"
```
A colleague has rebuilt systemd package by reverting below patch and
everything started working again:
core/device: ignore DEVICE_FOUND_UDEV bit on switching root (LP: #2037281)
File:
debian/patches/lp2037281-core-device-ignore-DEVICE_FOUND_UDEV-bit-on-switching-roo.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=00f86f0b20f794f30aabe7181912d2ec2207e292
This is causing us an issue to access network when the machine is
starting.
Does above patch requires a change in the udev rule we are using ?
Thanks in advance for your help.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2051358/+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
