[Touch-packages] [Bug 2033569] [NEW] suddenly choked on multiseat config in a way that survives reboots and even purging it
Public bug reported: I have a bog-standard loginctl multiseat setup, using lightdm because of #2033323. Except for the lack of session locking, it worked beautifully, across multiple reboots. Until it didn't. Box woke from suspend, and to be fair was acting strangely even then (Steam suddenly tried to launch using the iGPU), so suspend may well be broken on this box, but if so, that's a separate issue. Anyway, I rebooted, no lightdm greeter to be seen, the screen on seat1 was black. I did not have easy access to seat0 at the time. The journal has, looping: systemd[1]: Failed to start Detect the available GPUs and deal with any system changes. systemd[1]: lightdm.service: Start request repeated too quickly. token systemd[1]: lightdm.service: Failed with result 'exit-code'. token systemd[1]: Failed to start Light Display Manager. The first line is from gpu-manager.service, whose log contains Vendor/Device Id: 1002:164e BusID "PCI:110@0:0:0" Is boot vga? no Error: can't access /sys/bus/pci/devices/:6e:00.0/driver The device is not bound to any driver. Vendor/Device Id: 1002:73ff BusID "PCI:3@0:0:0" Is boot vga? yes Error : Failed to open /dev/dri Error : Failed to open /dev/dri Error : Failed to open /dev/dri Error : Failed to open /dev/dri x-0 log has vesa: Ignoring device with a bound kernel driver vesa: Ignoring device with a bound kernel driver (EE) Fatal server error: (EE) no screens found(EE) Scary. Thing is, both the iGPU and the dGPU are claimed by amdgpu, their "driver" symlink is accessible just fine. Switch back to gdm via dpkg- reconfigure, it boots up fine again. It's just lightdm that's hosed. I tried purging lightdm and lightdm-gtk-greeter, along with and /var/lib/lightdm, and reinstalling the packages, but no dice. What does work is starting lightdm.service manually over ssh: It takes about 1-4 tries for both gpu-manager and lightdm to successfully launch and bring up both greeters. Reboot, and it fails again. Some kind of race condition due to too lax timing and/or dependencies in the lightdm service file? Something unrelated changed the order and or speed at which systemd executes the service files, i.e. it worked by accident before and now it doesn't? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: lightdm 1.30.0-0ubuntu5 Uname: Linux 6.4.12-060412-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Aug 31 03:16:56 2023 InstallationDate: Installed on 2023-08-25 (5 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/2033569 Title: suddenly choked on multiseat config in a way that survives reboots and even purging it Status in lightdm package in Ubuntu: New Bug description: I have a bog-standard loginctl multiseat setup, using lightdm because of #2033323. Except for the lack of session locking, it worked beautifully, across multiple reboots. Until it didn't. Box woke from suspend, and to be fair was acting strangely even then (Steam suddenly tried to launch using the iGPU), so suspend may well be broken on this box, but if so, that's a separate issue. Anyway, I rebooted, no lightdm greeter to be seen, the screen on seat1 was black. I did not have easy access to seat0 at the time. The journal has, looping: systemd[1]: Failed to start Detect the available GPUs and deal with any system changes. systemd[1]: lightdm.service: Start request repeated too quickly. token systemd[1]: lightdm.service: Failed with result 'exit-code'. token systemd[1]: Failed to start Light Display Manager. The first line is from gpu-manager.service, whose log contains Vendor/Device Id: 1002:164e BusID "PCI:110@0:0:0" Is boot vga? no Error: can't access /sys/bus/pci/devices/:6e:00.0/driver The device is not bound to any driver. Vendor/Device Id: 1002:73ff BusID "PCI:3@0:0:0" Is boot vga? yes Error : Failed to open /dev/dri Error : Failed to open /dev/dri Error : Failed to open /dev/dri Error : Failed to open /dev/dri x-0 log has vesa: Ignoring device with a bound kernel driver vesa: Ignoring device with a bound kernel driver (EE) Fatal server error: (EE) no screens found(EE) Scary. Thing is, both the iGPU and the dGPU are claimed by amdgpu, their "driver" symlink is accessible just fine. Switch back to gdm via dpkg- reconfigure, it boots up fine again. It's just lightdm that's hosed. I tried purging lightdm and lightdm-gtk-greeter, along with and /var/lib/lightdm, and reinstalling the packages, but no dice. What does wor
[Touch-packages] [Bug 1978079] Re: EFI pstore not cleared on boot
This bug is awaiting verification that the linux-bluefield/5.4.0-1070.76 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-bluefield' to 'verification-done- focal-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-focal-linux-bluefield' to 'verification-failed- focal-linux-bluefield'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-bluefield-v2 verification-needed-focal-linux-bluefield -- 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/1978079 Title: EFI pstore not cleared on boot Status in linux-bluefield package in Ubuntu: New Status in systemd package in Ubuntu: Fix Released Status in linux-bluefield source package in Focal: Fix Committed Status in systemd source package in Focal: Fix Released Status in systemd source package in Impish: Won't Fix Status in linux-bluefield source package in Jammy: Fix Committed Status in systemd source package in Jammy: Fix Released Status in systemd source package in Kinetic: Fix Released Bug description: [Impact] Systemd has a systemd-pstore component that scans the pstore on boot and if non-empty, takes all previously created dumps, transfers them into its journal and removes the pstore elements. This is very important on UEFI systems, which only have a limited amount of space for variables. In Ubuntu, the kernel is configured with CONFIG_EFI_VARS_PSTORE=m which means the EFI pstore support gets loaded dynamically. In all of my boots, this dynamic module loading happened *after* systemd tried to check for pstore variables. So systemd-pstore never starts and never clears the UEFI variable store. I see this happening in AWS on Graviton instances, which eventually run out of space to store the dumps. On real hardware, this behavior may lead to unbootable systems. ``` $ systemctl status systemd-pstore ○ systemd-pstore.service - Platform Persistent Storage Archival Loaded: loaded (/lib/systemd/system/systemd-pstore.service; enabled; vendor preset: enabled) Active: inactive (dead) Condition: start condition failed at Thu 2022-06-09 09:11:41 UTC; 29min ago └─ ConditionDirectoryNotEmpty=/sys/fs/pstore was not met Docs: man:systemd-pstore(8) Jun 09 09:11:41 ip-172-31-0-61 systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. $ ls -la /sys/fs/pstore total 0 drwxr-x--- 2 root root0 Jun 9 09:11 . drwxr-xr-x 8 root root0 Jun 9 09:11 .. -r--r--r-- 1 root root 1803 Jun 9 09:07 dmesg-efi-165476562001001 -r--r--r-- 1 root root 1777 Jun 9 09:07 dmesg-efi-165476562002001 -r--r--r-- 1 root root 1773 Jun 9 09:07 dmesg-efi-165476562003001 -r--r--r-- 1 root root 1815 Jun 9 09:07 dmesg-efi-165476562004001 -r--r--r-- 1 root root 1826 Jun 9 09:07 dmesg-efi-165476562005001 -r--r--r-- 1 root root 1754 Jun 9 09:07 dmesg-efi-165476562006001 -r--r--r-- 1 root root 1821 Jun 9 09:07 dmesg-efi-165476562007001 -r--r--r-- 1 root root 1767 Jun 9 09:07 dmesg-efi-165476562008001 -r--r--r-- 1 root root 1729 Jun 9 09:07 dmesg-efi-165476562009001 -r--r--r-- 1 root root 1819 Jun 9 09:07 dmesg-efi-165476562010001 -r--r--r-- 1 root root 1767 Jun 9 09:07 dmesg-efi-165476562011001 -r--r--r-- 1 root root 1775 Jun 9 09:07 dmesg-efi-165476562012001 -r--r--r-- 1 root root 1802 Jun 9 09:07 dmesg-efi-165476562013001 -r--r--r-- 1 root root 1812 Jun 9 09:07 dmesg-efi-165476562014001 -r--r--r-- 1 root root 1764 Jun 9 09:07 dmesg-efi-165476562015001 -r--r--r-- 1 root root 1795 Jun 9 09:11 dmesg-efi-165476589801001 -r--r--r-- 1 root root 1785 Jun 9 09:11 dmesg-efi-165476589802001 -r--r--r-- 1 root root 1683 Jun 9 09:11 dmesg-efi-165476589803001 -r--r--r-- 1 root root 1785 Jun 9 09:11 dmesg-efi-165476589804001 -r--r--r-- 1 root root 1771 Jun 9 09:11 dmesg-efi-165476589805001 -r--r--r-- 1 root root 1797 Jun 9 09:11 dmesg-efi-165476589806001 -r--r--r-- 1 root root 1805 Jun 9 09:11 dmesg-efi-165476589807001 -r--r--r-- 1 root root 1781 Jun 9 09:11 dmesg-efi-165476589808001 -r--r--r-- 1 root root 1806 Jun 9 09:11 dmesg-efi-165476589809001 -r--r--r-- 1 root root 1821 Jun 9 09:11 dmesg-efi-165476589810001 -r--r--r-- 1 root root 1763 Jun 9 09:11 dmesg-efi-165476589811001 -r--r--r-- 1 root root 1783 Jun 9 09:11 dmesg-efi-165476589812001 -r--r--r-- 1 root root 1788 Jun 9 09:11 dmesg-efi-165476589813001 -r--r--r-- 1 root root 1788 Jun 9 09:11 dmesg-efi-165476589814001 -r--r--r-
[Touch-packages] [Bug 2033560] [NEW] package ufw 0.36.1-4ubuntu0.1 failed to install/upgrade: o subprocesso instalado, do pacote ufw, o script post-installation retornou erro do status de saída 10
Public bug reported: Erros foram encontrados durante o processamento de: ufw E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: ufw 0.36.1-4ubuntu0.1 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: net-tools:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 29 21:05:48 2023 ErrorMessage: o subprocesso instalado, do pacote ufw, o script post-installation retornou erro do status de saída 10 InstallationDate: Installed on 2023-07-10 (50 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.12, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: ufw Title: package ufw 0.36.1-4ubuntu0.1 failed to install/upgrade: o subprocesso instalado, do pacote ufw, o script post-installation retornou erro do status de saída 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ufw (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/2033560 Title: package ufw 0.36.1-4ubuntu0.1 failed to install/upgrade: o subprocesso instalado, do pacote ufw, o script post-installation retornou erro do status de saída 10 Status in ufw package in Ubuntu: New Bug description: Erros foram encontrados durante o processamento de: ufw E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: ufw 0.36.1-4ubuntu0.1 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: net-tools:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 29 21:05:48 2023 ErrorMessage: o subprocesso instalado, do pacote ufw, o script post-installation retornou erro do status de saída 10 InstallationDate: Installed on 2023-07-10 (50 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.12, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: ufw Title: package ufw 0.36.1-4ubuntu0.1 failed to install/upgrade: o subprocesso instalado, do pacote ufw, o script post-installation retornou erro do status de saída 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/2033560/+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 2031352] Re: Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
yes I'm experiencing the same issue. -- 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/2031352 Title: Ubuntu 22.04.3 LTS stuck on power-off/reboot screen Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux-hwe-6.2 source package in Jammy: Confirmed Bug description: After updating to Kernel 6.2 a few days ago, I have been experiencing issues with my system's shutdown and reboot functions. During these processes, the system becomes unresponsive and hangs on a black screen, which displays both the Dell and Ubuntu logos. This issue is inconsistent; it happens sporadically. Currently, the only workaround I've found to successfully shut down the system is to forcibly power off the machine by holding down the power button for 5 seconds. I've also tested a fresh installation of Ubuntu 22.04.3. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.9 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 14 22:41:14 2023 InstallationDate: Installed on 2023-08-14 (1 days ago) InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813) MachineType: Dell Inc. XPS 8930 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.30 dmi.board.name: 0T88YD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.30 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-08-13T20:57:27 mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2031352/+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 2028935] Re: Merge rsyslog 8.2306.0-2
** Changed in: rsyslog (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2028935 Title: Merge rsyslog 8.2306.0-2 Status in rsyslog package in Ubuntu: Incomplete Bug description: Debian has upgraded rsyslog to 8.2306.0-2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2028935/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2009743] Re: networkd: classless routes served by DHCP are created incorrectly
This bug was fixed in the package systemd - 253.5-1ubuntu4 --- systemd (253.5-1ubuntu4) mantic; urgency=medium * Revert "Drop Provides: time-daemon for bin:systemd-timesyncd" File: debian/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=e88d9f0241a307a3c1b4bcaf4bf29799d984aa3c -- Nick Rosbrook Fri, 25 Aug 2023 16:36:26 -0400 ** Changed in: systemd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2009743 Title: networkd: classless routes served by DHCP are created incorrectly Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Committed Status in systemd source package in Lunar: Fix Committed Bug description: [Impact] Classless static routes served by DHCP are ignored by networkd in some cases. Specifically, the gateway is not being set for routes whenever the route destination is in the assigned network. This is a regression in behavior since Focal. [Test Plan] This is basically taken from systemd-networkd-tests.py. Using a veth pair, setup dnsmasq to serve the problematic routes: $ cat > /etc/systemd/network/25-dhcp-server-veth-peer.network << EOF [Match] Name=veth-peer [Network] IPv6AcceptRA=no Address=2600::1/0 Address=192.168.5.1/24 EOF $ cat > /etc/systemd/network/25-test.network << EOF [Match] Name=veth99 [Network] DHCP=ipv4 IPv6AcceptRA=false [DHCPv4] UseRoutes=yes EOF $ cat > /etc/systemd/network/25-veth.netdev << EOF [NetDev] Name=veth99 Kind=veth MACAddress=12:34:56:78:9a:bc [Peer] Name=veth-peer MACAddress=12:34:56:78:9a:bd EOF $ mkdir -p /etc/systemd/system/systemd-networkd.service.d/ $ cat > /etc/systemd/system/systemd-networkd.service.d/debug.conf << EOF [Service] Environment=SYSTEMD_LOG_LEVEL=debug EOF $ systemctl daemon-reload $ systemctl restart systemd-networkd $ mkdir -p /run/networkd-ci $ dnsmasq --log-facility=/run/networkd-ci/test-dnsmasq.log --log-queries=extra --log-dhcp --pid-file=/run/networkd-ci/test-dnsmasq.pid --conf-file=/dev/null --bind-interfaces --interface=veth-peer --dhcp-leasefile=/run/networkd-ci/test-dnsmasq.lease --enable-ra --dhcp-range=2600::10,2600::20,2m --dhcp-range=192.168.5.10,192.168.5.200,2m --dhcp-option=option:mtu,1492 --dhcp-option=option:router,192.168.5.1 --port=0 --no-resolv --dhcp-option=option:classless-static-route,0.0.0.0/0,192.168.5.4,8.0.0.0/8,192.168.5.5,192.168.5.64/26,192.168.5.5 & $ systemctl restart systemd-networkd On an affected machine, the route to 192.168.5.64 on veth99 will be missing it's gateway address: $ ip r show dev veth99 192.168.5.64/26 192.168.5.64/26 proto dhcp scope link src 192.168.5.181 metric 1024 And, there will be a log message explaining that this was done intentionally: $ journalctl -u systemd-networkd --grep="veth99.*assigned network" Aug 03 16:58:49 mantic2 systemd-networkd[1418]: veth99: DHCP: requested route destination 192.168.5.64/26 is in the assigned network 192.168.5.0/24, ignoring gateway address 192.168.5.5 On a fixed machine, the route for to 192.168.5.64 will correctly have its gateway configured: $ ip r show dev veth99 192.168.5.64/26 192.168.5.64/26 via 192.168.5.5 proto dhcp src 192.168.5.181 metric 1024 [Where problems could occur] The patch is in the DHCPv4 client code for handling routes from the DHCP server. It adds a flag, force_use_gw, to an internal function that essentially overrides the "ignore" behavior whenever classless static routes have been given. If we saw regressions, it would be related to creation of static routes handed down by DHCPv4 servers. [Original Description] After upgrading 20.04 systems to 22.04, the classless routes served via DHCP are not being registered correctly - they are missing the gateway address. Expected routes - these are taken from a 20.04 system on the same network: $ ip route default via 10.10.1.1 dev enp24s0 proto dhcp src 10.10.64.12 metric 100 10.0.0.0/8 dev enp24s0 proto kernel scope link src 10.10.64.12 10.88.88.0/24 via 10.10.1.2 dev enp24s0 proto dhcp src 10.10.64.12 metric 100 10.96.0.0/11 via 10.10.1.2 dev enp24s0 proto dhcp src 10.10.64.12 metric 100 Actual routes - these are the routes created in one of the affected 22.04 systems: $ ip route default via 10.10.1.1 dev bond0 proto dhcp src 10.10.48.20 metric 100 8.8.8.8 via 10.10.1.1 dev bond0 proto dhcp src 10.10.48.20 metric 100 10.0.0.0/8 dev bond0 proto kernel scope link src 10.10.48.20 metric 100 10.10.1.1 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100 10.10.1.2 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100 10.88.88.0/24 dev bond0 proto dhcp scope
[Touch-packages] [Bug 2012437] Re: Ship a static libsystemd.a
This bug was fixed in the package systemd - 253.5-1ubuntu4 --- systemd (253.5-1ubuntu4) mantic; urgency=medium * Revert "Drop Provides: time-daemon for bin:systemd-timesyncd" File: debian/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=e88d9f0241a307a3c1b4bcaf4bf29799d984aa3c -- Nick Rosbrook Fri, 25 Aug 2023 16:36:26 -0400 ** Changed in: systemd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2012437 Title: Ship a static libsystemd.a Status in systemd package in Ubuntu: Fix Released Bug description: More and more things are requiring linking against libsystemd. In particular, because dbus is now linked against libsystemd, anything that wants to make a dbus client call needs it. By not shipping a static libsystemd.a, all such users are prevented from building statically. This includes tools like the lxc-init container init, and stacker container build tool, which both want to be re-execed inside a container which may have completely different - or no - distro. With the attached debdiff, libsystemd-dev ships a libsystem.a so tools can be built statically. The package has been built (for lunar) with this debdiff at ppa:serge- hallyn/systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2012437/+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 2013543] Re: systemctl daemon-reexec forgets running services and starts everything new
This bug was fixed in the package systemd - 253.5-1ubuntu4 --- systemd (253.5-1ubuntu4) mantic; urgency=medium * Revert "Drop Provides: time-daemon for bin:systemd-timesyncd" File: debian/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=e88d9f0241a307a3c1b4bcaf4bf29799d984aa3c -- Nick Rosbrook Fri, 25 Aug 2023 16:36:26 -0400 ** Changed in: systemd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2013543 Title: systemctl daemon-reexec forgets running services and starts everything new Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Committed Status in systemd source package in Lunar: Fix Committed Bug description: [Impact] Depending on the contents of /proc/cmdline, when systemd is re- executed with systemctl daemon-reexec, the --deserialize flag may be ignored because it was added after the other arguments. For example, if /proc/cmdline contains ---, then the re-exec cmdline might look like: $ cat /proc/1/cmdline | tr '\0' '\n' /lib/systemd/systemd --- splash --system --deserialize 54 This causes systemd not to process the --deserialize 54 argument, causing it to start with a fresh state. This can cause all kinds of problems, and one easy symptom to see is many lines in the journal like: "$service.service: Found left-over process $pid ($service) in control group while starting unit. Ignoring." [Test Plan] 1. (Only needed if your test system is not already affected) Edit the kernel command line to contain '---' at the end, which would trigger the bug. This can be done by appending '---' to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, running update-grub, and then rebooting. 2. After enabling -proposed, install systemd: $ apt install systemd -y 3. Check that the systemd.postinst script skipped the daemon-reexec call, and instead indicated a reboot is required: $ grep -Fsx systemd /run/reboot-required.pkgs systemd 4. Reboot. 5. Try to re-exec systemd, and check that there are not tons of "left- over process" log messages: $ systemctl daemon-reexec $ journalctl --grep "Found left-over process" -b 0 6. Also confirm that the ordering of /proc/1/cmdline is correct, i.e. that --deserialize $fd comes before args from /proc/cmdline: $ cat /proc/1/cmdline | tr '\0' '\n' [Where problems could occur] There are two changes for this bug. First is the patch against systemd itself, which changes the ordering of arguments on the systemd commandline. This change simply makes it so that systemd's own arguments are always put first on it's re-exec commandline, and that anything from /proc/cmdline is appended after. Any regressions caused by this would also be seen in systemctl daemon-reexec invocations. The second change is in systemd.postinst, which skips the systemctl daemon-reexec call when upgrading from versions of systemd that could hit this bug. Regressions caused by this would be seen during package upgrades. [Original Description] # Our problem # During a regular update of our container environment, `systemd` (and the related packages libpam-systemd, libsystemd0, libudev1, systemd- sysv and udev) were updated from `249.11-0ubuntu3.6` to `249.11-0ubuntu3.7`. We're talking only about Ubuntu 22.04. Our Ubuntu 20.04 is working fine with `systemctl daemon-reexec`. In my opinion, the update was not the problem because we've tried downgrading and tried these versions: (current) `249.11-0ubuntu3.7`, `249.11-0ubuntu3.6`, `249.11-0ubuntu3.4` and `249.11-0ubuntu3.3`. The symptoms were the same. # Symptoms # The `/var/lib/dpkg/info/systemd.postinst` executes a `systemctl daemon-reexec` and that ended in a disaster. It seems that `systemd` is forgetting all it started children and tries to start nearly every configured service again. Naturally, the old services are still running, and the ports can't be opened twice and `systemd` won't give up. Here are some(!) of the logfiles: Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Starting Create Volatile Files and Directories... Mar 31 12:51:39 FQDN_REDACTED systemd[1]: systemd-udevd.service: Found left-over process 130 (systemd-udevd) in control group while starting unit. Ignoring. Mar 31 12:51:39 FQDN_REDACTED systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mar 31 12:51:39 FQDN_REDACTED systemd[1]: systemd-udevd.service: Found left-over process 31475 (systemd-udevd) in control group while starting unit. Ignoring. Mar 31 12:51:39 FQDN_REDACTED systemd[1]: This usually indicates unclean termination of a previous
[Touch-packages] [Bug 2018060] Re: Merge bridge-utils from Debian unstable for mantic
** Changed in: bridge-utils (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/2018060 Title: Merge bridge-utils from Debian unstable for mantic Status in bridge-utils package in Ubuntu: Expired Bug description: Scheduled-For: Backlog Upstream: tbd Debian: 1.7.1-1 Ubuntu: 1.7.1-1ubuntu1 There is nothing yet to merge for bridge-utils currently, but this ticket is filed prospectfully for tracking purposes in case a merge does become available later this cycle. If it turns out this needs a sync rather than a merge, please change the tag 'needs-merge' to 'needs-sync', and (optionally) update the title as desired. ### New Debian Changes ### bridge-utils (1.7.1-1) unstable; urgency=low * New upstream version. Only some fixes for compilation warnings and the man page. * Update standards version to 4.6.1, no changes needed. * Set debhelper-compat version in Build-Depends. * Trim trailing whitespace. -- Santiago García Mantiñán Wed, 25 Jan 2023 22:11:52 +0100 bridge-utils (1.7-2) unstable; urgency=medium * Add BRIDGE_DISABLE_LINKLOCAL_IPV6_ALSO_PHYS to /etc/default/bridge-utils to stop disabling IPv6 on physical interfaces of vlan ports if set to no. Closes: #989162. * Update interfaces man page, IPv6 works with STP on after DAD was fixed. Closes: #980507. * Treat vlan ports the same as ifupdown, avoid octal vlans. Closes: #995627. * Update NEWS file to fix us blaming the kernel for the MAC address selection that is really overridden by systemd. -- Santiago García Mantiñán Mon, 03 Oct 2022 23:11:46 +0200 bridge-utils (1.7-1) unstable; urgency=medium * New upstream version. Only messages related changes and compilation fixes. * Remove preserve_gcc_flags patch (in upstream now). * Bump standards, no change needed. * Clarify portprio and fix example. * Update upstream url. * Fix NEWS versioning of last entry :-? -- Santiago Garcia Mantinan Wed, 24 Feb 2021 12:34:03 +0100 bridge-utils (1.6-6) unstable; urgency=medium * Fix IPv6 address getting assigned on hotplug devices. Closes: #980752. * Fix waiting so that DAD works again. Closes: #982943. * Move mac setting before brctl addif to ensure mac setting. Closes: #980856. * Update documentation and add examples. Closes: #765098. * Update manpages. Closes: #981253. * Add a note on MTU settings. Closes: #292088. * Hook also on down to recreate the bridge so that multiple stanzas work Ok on ifdown. Closes: #319832. -- Santiago Garcia Mantinan Tue, 16 Feb 2021 13:29:04 +0100 bridge-utils (1.6-5) unstable; urgency=low * Overload bridge_hw to allow do specify an interface as well as the MAC address. Closes: #966244. * Change man page for bridge-utils-interfaces and news fileto document this overloading. -- Santiago Garcia Mantinan Fri, 22 Jan 2021 11:08:47 +0100 bridge-utils (1.6-4) unstable; urgency=low * Add en* to the device regex so that all catches them. Closes: #966319. * Document MAC address changes on news. Closes: #980505. -- Santiago Garcia Mantinan Thu, 21 Jan 2021 10:51:31 +0100 bridge-utils (1.6-3) unstable; urgency=medium * Support VLAN aware setups where we need vlan filtering. Thanks Benedikt Spranger for the patch. Closes: #950879. * Clarify on manual page that stp will get IPv6 lost. Closes: #736336. * Add a 1 second sleep if hw address needs to be changed. Closes: #945466. -- Santiago Garcia Mantinan Thu, 30 Apr 2020 10:06:38 +0200 bridge-utils (1.6-2) unstable; urgency=medium * Bump Standards-Version. * Preserve gcc flags set when building the lib. -- Santiago Garcia Mantinan Mon, 28 Jan 2019 00:25:14 +0100 bridge-utils (1.6-1) unstable; urgency=low * New upstream version. * Change default back to not hotplug. Closes: #892277. * Allow mtu to be set on the bridge by propagating it to the bridged interfaces. Closes: #661711. * Remove kernel headers from the package. -- Santiago Garcia Mantinan Tue, 15 Jan 2019 13:18:33 +0100 bridge-utils (1.5-16) unstable; urgency=medium * Don't set dev globally at bridge-utils.sh. Closes: #873086. -- Santiago Garcia Mantinan Sun, 08 Apr 2018 23:06:30 +0200 bridge-utils (1.5-15) unstable; urgency=medium ### Old Ubuntu Delta ### bridge-utils (1.7.1-1ubuntu1) lunar; urgency=medium * Merge from Debian unstable, remaining changes: - Don't call ifup from bridge-network-interface, instead just call brctl and let udev/upstart bring the interface up. - debian/ifupdown.sh: Handle bridge params which use port and value - debian/bridge-utils-interfa
[Touch-packages] [Bug 2018079] Re: Merge libmnl from Debian unstable for mantic
** Changed in: libmnl (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libmnl in Ubuntu. https://bugs.launchpad.net/bugs/2018079 Title: Merge libmnl from Debian unstable for mantic Status in libmnl package in Ubuntu: Expired Bug description: Scheduled-For: Backlog Upstream: tbd Debian: 1.0.4-3 Ubuntu: 1.0.4-3ubuntu1 There is nothing yet to merge for libmnl currently, but this ticket is filed prospectfully for tracking purposes in case a merge does become available later this cycle. If it turns out this needs a sync rather than a merge, please change the tag 'needs-merge' to 'needs-sync', and (optionally) update the title as desired. ### Old Ubuntu Delta ### libmnl (1.0.4-3ubuntu1) kinetic; urgency=medium * Static build does not work for libmnl (-lmnl) (LP: #1971523) -- Michal Maloszewski Thu, 21 Jul 2022 14:02:16 +0200 libmnl (1.0.4-3build2) jammy; urgency=high * No change rebuild for ppc64el baseline bump. -- Julian Andres Klode Thu, 24 Mar 2022 13:13:28 +0100 libmnl (1.0.4-3build1) impish; urgency=medium * No-change rebuild to build packages with zstd compression. -- Matthias Klose Thu, 07 Oct 2021 12:16:42 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmnl/+bug/2018079/+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 2018081] Re: Merge libseccomp from Debian unstable for mantic
** Changed in: libseccomp (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/2018081 Title: Merge libseccomp from Debian unstable for mantic Status in libseccomp package in Ubuntu: Expired Bug description: Scheduled-For: Backlog Upstream: tbd Debian: 2.5.4-1 Ubuntu: 2.5.4-1ubuntu3 The NOT SERVER TEAM team has maintained this package in the past and may be handling this merge. If it turns out this needs a sync rather than a merge, please change the tag 'needs-merge' to 'needs-sync', and (optionally) update the title as desired. ### Old Ubuntu Delta ### libseccomp (2.5.4-1ubuntu3) lunar; urgency=medium * Rebuild to drop Python 3.10 extension -- Jeremy Bicha Tue, 28 Feb 2023 17:23:34 -0500 libseccomp (2.5.4-1ubuntu2) lunar; urgency=medium * No-change rebuild with Python 3.11 as supported -- Graham Inggs Wed, 02 Nov 2022 10:24:36 + libseccomp (2.5.4-1ubuntu1) kinetic; urgency=medium * Merge from Debian unstable; remaining changes: - Add autopkgtests -- Alex Murray Tue, 03 May 2022 11:43:10 +0930 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/2018081/+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 2031416] Re: libsystemd.a missing symbols on armhf
This bug was fixed in the package systemd - 253.5-1ubuntu4 --- systemd (253.5-1ubuntu4) mantic; urgency=medium * Revert "Drop Provides: time-daemon for bin:systemd-timesyncd" File: debian/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=e88d9f0241a307a3c1b4bcaf4bf29799d984aa3c -- Nick Rosbrook Fri, 25 Aug 2023 16:36:26 -0400 ** Changed in: systemd (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2031416 Title: libsystemd.a missing symbols on armhf Status in systemd package in Ubuntu: Fix Released Bug description: There are two symptoms to observe here. First is that build-with- static-libsystemd fails on armhf[1]: 2733s autopkgtest [10:52:05]: test build-with-static-libsystemd: [--- 2735s /usr/bin/ld: /tmp/ccRhNQ82.o: in function `main': 2735s uuid-gen.c:(.text+0x20): undefined reference to `sd_id128_randomize' 2735s /usr/bin/ld: uuid-gen.c:(.text+0x5c): undefined reference to `sd_id128_to_string' 2735s collect2: error: ld returned 1 exit status 2735s autopkgtest [10:52:07]: test build-with-static-libsystemd: ---] Second is this dh_strip warning from the armhf build log[2]: dh_strip: warning: lto-no-text-in-archive: debian/libsystemd- dev/usr/lib/arm-linux-gnueabihf/libsystemd.a This is caused by building with -flto=auto, but without -ffat-lto- objects[3], which appears to be enabled for all arches except armhf. [1] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/armhf/s/systemd/20230815_105221_65d03@/log.gz [2] https://launchpadlibrarian.net/681945377/buildlog_ubuntu-mantic-armhf.systemd_253.5-1ubuntu2_BUILDING.txt.gz [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977596 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2031416/+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 2033129] Re: hplip is in universe and was dropped from Recommends
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2033129 Title: hplip is in universe and was dropped from Recommends Status in hplip package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: When preparing the upload of ubuntu-meta 1.516 I wasn't enough attentive. Only afterwards I noticed that the update script had caused hplip to be removed from the meta packages, even if it is still here: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/platform/tree/desktop-common#n69 I don't know how to properly correct this. Please help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/2033129/+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 2033129] Re: hplip is in universe and was dropped from Recommends
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: hplip (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2033129 Title: hplip is in universe and was dropped from Recommends Status in hplip package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: When preparing the upload of ubuntu-meta 1.516 I wasn't enough attentive. Only afterwards I noticed that the update script had caused hplip to be removed from the meta packages, even if it is still here: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/platform/tree/desktop-common#n69 I don't know how to properly correct this. Please help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/2033129/+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 645404] Re: Support Private PPAs
software-properties (0.99.39) mantic; urgency=medium * Add cjwatson patch to use getArchiveSubscriptionURL() for private PPAs * Fix getArchiveSubscriptionURL() API call and tests * Resolve adding private PPAs, which do not yet have a token LP: #1991553 -- Dimitri John Ledkov Fri, 25 Aug 2023 22:17:31 +0100 ** Changed in: software-properties (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/645404 Title: Support Private PPAs Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Won't Fix Status in software-properties source package in Cosmic: Won't Fix Status in software-properties source package in Disco: Won't Fix Status in software-properties source package in Eoan: Won't Fix Status in software-properties source package in Focal: Won't Fix Bug description: Software properties add-apt-repository currently does not support adding private PPAs. software-properties should connect to the API and observe that it gets permission denied trying to read the ppa. Then it can reconnect to the API asking for authentication, which will open a browser window where you can do the openid ritual. Then using that token it ought to be possible for it to get the password etc. ProblemType: BugDistroRelease: Ubuntu 12.04 Package: python-software-properties 0.82.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/645404/+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 1297025] Re: Either the changelog.gz is missing or there is an erroneous link in the libssl1.0.0 package
This seems to be caused by #1895799 which would be a bug in pkgstripfiles. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1297025 Title: Either the changelog.gz is missing or there is an erroneous link in the libssl1.0.0 package Status in openssl package in Ubuntu: In Progress Bug description: In libssl-dev for both Precise and Saucy packages for libssl-dev, there is a broken link: # ls -l /usr/share/doc/libssl-dev/changelog.gz lrwxrwxrwx 1 root root 27 Jan 8 12:48 /usr/share/doc/libssl-dev/changelog.gz -> ../libssl1.0.0/changelog.gz # ls -l /usr/share/doc/libssl1.0.0/changelog.gz ls: cannot access /usr/share/doc/libssl1.0.0/changelog.gz: No such file or directory I have verified this in both releases while trying to debug a failing build of a 3rd party library that links against these. Build works in Precise, fails in Saucy. Was looking to see what changed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1297025/+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 2028935] Re: Merge rsyslog 8.2306.0-2
As Debian has a new version I need to respin again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2028935 Title: Merge rsyslog 8.2306.0-2 Status in rsyslog package in Ubuntu: Confirmed Bug description: Debian has upgraded rsyslog to 8.2306.0-2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2028935/+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 2018060] Re: Merge bridge-utils from Debian unstable for mantic
** Changed in: bridge-utils (Ubuntu) Status: Expired => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/2018060 Title: Merge bridge-utils from Debian unstable for mantic Status in bridge-utils package in Ubuntu: Incomplete Bug description: Scheduled-For: Backlog Upstream: tbd Debian: 1.7.1-1 Ubuntu: 1.7.1-1ubuntu1 There is nothing yet to merge for bridge-utils currently, but this ticket is filed prospectfully for tracking purposes in case a merge does become available later this cycle. If it turns out this needs a sync rather than a merge, please change the tag 'needs-merge' to 'needs-sync', and (optionally) update the title as desired. ### New Debian Changes ### bridge-utils (1.7.1-1) unstable; urgency=low * New upstream version. Only some fixes for compilation warnings and the man page. * Update standards version to 4.6.1, no changes needed. * Set debhelper-compat version in Build-Depends. * Trim trailing whitespace. -- Santiago García Mantiñán Wed, 25 Jan 2023 22:11:52 +0100 bridge-utils (1.7-2) unstable; urgency=medium * Add BRIDGE_DISABLE_LINKLOCAL_IPV6_ALSO_PHYS to /etc/default/bridge-utils to stop disabling IPv6 on physical interfaces of vlan ports if set to no. Closes: #989162. * Update interfaces man page, IPv6 works with STP on after DAD was fixed. Closes: #980507. * Treat vlan ports the same as ifupdown, avoid octal vlans. Closes: #995627. * Update NEWS file to fix us blaming the kernel for the MAC address selection that is really overridden by systemd. -- Santiago García Mantiñán Mon, 03 Oct 2022 23:11:46 +0200 bridge-utils (1.7-1) unstable; urgency=medium * New upstream version. Only messages related changes and compilation fixes. * Remove preserve_gcc_flags patch (in upstream now). * Bump standards, no change needed. * Clarify portprio and fix example. * Update upstream url. * Fix NEWS versioning of last entry :-? -- Santiago Garcia Mantinan Wed, 24 Feb 2021 12:34:03 +0100 bridge-utils (1.6-6) unstable; urgency=medium * Fix IPv6 address getting assigned on hotplug devices. Closes: #980752. * Fix waiting so that DAD works again. Closes: #982943. * Move mac setting before brctl addif to ensure mac setting. Closes: #980856. * Update documentation and add examples. Closes: #765098. * Update manpages. Closes: #981253. * Add a note on MTU settings. Closes: #292088. * Hook also on down to recreate the bridge so that multiple stanzas work Ok on ifdown. Closes: #319832. -- Santiago Garcia Mantinan Tue, 16 Feb 2021 13:29:04 +0100 bridge-utils (1.6-5) unstable; urgency=low * Overload bridge_hw to allow do specify an interface as well as the MAC address. Closes: #966244. * Change man page for bridge-utils-interfaces and news fileto document this overloading. -- Santiago Garcia Mantinan Fri, 22 Jan 2021 11:08:47 +0100 bridge-utils (1.6-4) unstable; urgency=low * Add en* to the device regex so that all catches them. Closes: #966319. * Document MAC address changes on news. Closes: #980505. -- Santiago Garcia Mantinan Thu, 21 Jan 2021 10:51:31 +0100 bridge-utils (1.6-3) unstable; urgency=medium * Support VLAN aware setups where we need vlan filtering. Thanks Benedikt Spranger for the patch. Closes: #950879. * Clarify on manual page that stp will get IPv6 lost. Closes: #736336. * Add a 1 second sleep if hw address needs to be changed. Closes: #945466. -- Santiago Garcia Mantinan Thu, 30 Apr 2020 10:06:38 +0200 bridge-utils (1.6-2) unstable; urgency=medium * Bump Standards-Version. * Preserve gcc flags set when building the lib. -- Santiago Garcia Mantinan Mon, 28 Jan 2019 00:25:14 +0100 bridge-utils (1.6-1) unstable; urgency=low * New upstream version. * Change default back to not hotplug. Closes: #892277. * Allow mtu to be set on the bridge by propagating it to the bridged interfaces. Closes: #661711. * Remove kernel headers from the package. -- Santiago Garcia Mantinan Tue, 15 Jan 2019 13:18:33 +0100 bridge-utils (1.5-16) unstable; urgency=medium * Don't set dev globally at bridge-utils.sh. Closes: #873086. -- Santiago Garcia Mantinan Sun, 08 Apr 2018 23:06:30 +0200 bridge-utils (1.5-15) unstable; urgency=medium ### Old Ubuntu Delta ### bridge-utils (1.7.1-1ubuntu1) lunar; urgency=medium * Merge from Debian unstable, remaining changes: - Don't call ifup from bridge-network-interface, instead just call brctl and let udev/upstart bring the interface up. - debian/ifupdown.sh: Handle bridge params which use port and value - debian/bridge-utils-inte
[Touch-packages] [Bug 2018081] Re: Merge libseccomp from Debian unstable for mantic
** Changed in: libseccomp (Ubuntu) Status: Expired => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/2018081 Title: Merge libseccomp from Debian unstable for mantic Status in libseccomp package in Ubuntu: Incomplete Bug description: Scheduled-For: Backlog Upstream: tbd Debian: 2.5.4-1 Ubuntu: 2.5.4-1ubuntu3 The NOT SERVER TEAM team has maintained this package in the past and may be handling this merge. If it turns out this needs a sync rather than a merge, please change the tag 'needs-merge' to 'needs-sync', and (optionally) update the title as desired. ### Old Ubuntu Delta ### libseccomp (2.5.4-1ubuntu3) lunar; urgency=medium * Rebuild to drop Python 3.10 extension -- Jeremy Bicha Tue, 28 Feb 2023 17:23:34 -0500 libseccomp (2.5.4-1ubuntu2) lunar; urgency=medium * No-change rebuild with Python 3.11 as supported -- Graham Inggs Wed, 02 Nov 2022 10:24:36 + libseccomp (2.5.4-1ubuntu1) kinetic; urgency=medium * Merge from Debian unstable; remaining changes: - Add autopkgtests -- Alex Murray Tue, 03 May 2022 11:43:10 +0930 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/2018081/+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 2018079] Re: Merge libmnl from Debian unstable for mantic
** Changed in: libmnl (Ubuntu) Status: Expired => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libmnl in Ubuntu. https://bugs.launchpad.net/bugs/2018079 Title: Merge libmnl from Debian unstable for mantic Status in libmnl package in Ubuntu: Incomplete Bug description: Scheduled-For: Backlog Upstream: tbd Debian: 1.0.4-3 Ubuntu: 1.0.4-3ubuntu1 There is nothing yet to merge for libmnl currently, but this ticket is filed prospectfully for tracking purposes in case a merge does become available later this cycle. If it turns out this needs a sync rather than a merge, please change the tag 'needs-merge' to 'needs-sync', and (optionally) update the title as desired. ### Old Ubuntu Delta ### libmnl (1.0.4-3ubuntu1) kinetic; urgency=medium * Static build does not work for libmnl (-lmnl) (LP: #1971523) -- Michal Maloszewski Thu, 21 Jul 2022 14:02:16 +0200 libmnl (1.0.4-3build2) jammy; urgency=high * No change rebuild for ppc64el baseline bump. -- Julian Andres Klode Thu, 24 Mar 2022 13:13:28 +0100 libmnl (1.0.4-3build1) impish; urgency=medium * No-change rebuild to build packages with zstd compression. -- Matthias Klose Thu, 07 Oct 2021 12:16:42 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmnl/+bug/2018079/+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 2033440] Re: ubuntustudio-installer: error occurred while applying changes
Thank you for updating the documentation, that's exactly what was misleading. Just as a feedback: installing manually the metapackages listed in the ubuntustudio-installer worked fine. The ubuntu-desktop metapackage was probably automatically uninstalled (it is no more instlled in my system), but during the manual installation process I did not notice any removal of other critical system packages. So now I have an Ubuntu Studio over a Vanilla Ubuntu Gnome, with pulse-audio + jack, and a low latency kernel. To me, your answer closes the issue. Thanks a lot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2033440 Title: ubuntustudio-installer: error occurred while applying changes Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Lunar: New Status in ubuntu-meta source package in Mantic: New Bug description: I have installed successfully the standard Ubuntu 23.04 (on a 500 GB external USB drive). Immediately after the installation, I have also installed with apt the "ubuntustudio-installer" package. In the dialog provided by the ubuntustudio-installer, I have selected the following metapackages: - linux-lowlatency - ubuntustudio-lowlatency-settings - ubuntustudio-performance-tweaks - ubuntustudio-audio - ubuntu-pulseaudio-config and pressed "Modify installed Package Selection" After a while a "qaptbatch" dialog has appeared with title "Commit Error" and message "An error occurred while applying changes" So the installation has failed. Then I have tried to manually install each metapackage in the list above with apt and every package was installed successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2033440/+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 2028935] Re: Merge rsyslog 8.2306.0-2
I suppose the new merge is https://code.launchpad.net/~xypron/ubuntu/+source/rsyslog/+git/rsyslog/+merge/449720, is this right? I linked it to this bug. ** Merge proposal linked: https://code.launchpad.net/~xypron/ubuntu/+source/rsyslog/+git/rsyslog/+merge/449720 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2028935 Title: Merge rsyslog 8.2306.0-2 Status in rsyslog package in Ubuntu: Confirmed Bug description: Debian has upgraded rsyslog to 8.2306.0-2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2028935/+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 2029100] Re: general protection fault when detaching a gnome-terminal
Hello I don't know if those details are relevant for the problem : /usr/bin/gnome-terminal.real sudo gdb /usr/libexec/gnome-terminal-server 4876 [...] (gdb) c Continuing. [Detaching after fork from child process 48892] [New Thread 0x7f8dfabfd6c0 (LWP 48893)] [Detaching after fork from child process 48899] [Detaching after fork from child process 48905] Thread 1 "gnome-terminal-" received signal SIGSEGV, Segmentation fault. 0x7f8e00541d41 in gtk_widget_queue_draw () from /lib/x86_64-linux-gnu/libgtk-3.so.0 (gdb) bt #0 0x7f8e00541d41 in gtk_widget_queue_draw () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #1 0x7f8e00bba010 in g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #2 0x7f8e00be73d6 in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #3 0x7f8e00bd769a in g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #4 0x7f8e00bd7923 in g_signal_emit () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #5 0x7f8e00bc4dc4 in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x7f8e00bcb09f in g_object_notify () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #7 0x55e93ecaba0f in () #8 0x55e93ecac05d in () #9 0x7f8e00bd783c in g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #10 0x7f8e00bd7923 in g_signal_emit () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #11 0x7f8e00bd783c in g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #12 0x7f8e00bd7923 in g_signal_emit () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #13 0x7f8e004a7195 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #14 0x7f8e00350cc9 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #15 0x7f8e0032f3ea in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #16 0x7f8e0032f41b in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #17 0x7f8e0032f41b in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #18 0x7f8e0032f41b in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #19 0x7f8e0032f41b in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #20 0x7f8e0032f41b in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #21 0x7f8e0032f41b in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 21 0x7f8e0032f41b in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #22 0x7f8e003110b3 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #23 0x7f8e00bd783c in g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #24 0x7f8e00bd7923 in g_signal_emit () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #25 0x7f8e0014a6e9 in () at /lib/x86_64-linux-gnu/libgdk-3.so.0 #26 0x7f8e001375fb in () at /lib/x86_64-linux-gnu/libgdk-3.so.0 #27 0x7f8e00ab9a42 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7f8e00ab936f in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7f8e00b14178 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x7f8e00ab81b0 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x7f8e00ce4c5d in g_application_run () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #32 0x55e93ec9f165 in () #33 0x7f8dff623a90 in __libc_start_call_main (main=main@entry=0x55e93ec9ef70, argc=argc@entry=1, argv=argv@entry=0x7ffe8e7ce5b8) at ../sysdeps/nptl/libc_start_call_main.h:58 #34 0x7f8dff623b49 in __libc_start_main_impl (main=0x55e93ec9ef70, argc=1, argv=0x7ffe8e7ce5b8, init=, fini=, rtld_fini=, stack_end=0x7ffe8e7ce5a8) at ../csu/libc-start.c:360 #35 0x55e93ec9f395 in () -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2029100 Title: general protection fault when detaching a gnome-terminal Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: On Ubuntu 23.04 (I haven't had this bug in earlier releases) when detaching a gnome terminal tab most of the time (but not always) all open instances of the gnome terminal crash with the following dmesg: gnome-terminal-[3639] general protection fault ip:7f35f3341d41 sp:7fffe4f846b0 error:0 in libgtk-3.so.0.2405.32[7f35f3083000+38e000] Not sure whether this is relevant but I'm using the NVIDIA 535.54.03 proprietary drivers on X11 libgtk-3-0: Installed: 3.24.37-1ubuntu1 Candidate: 3.24.37-1ubuntu1 Version table: *** 3.24.37-1ubuntu1 500 500 http://nl.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2029100/+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 1297025] Re: Either the changelog.gz is missing or there is an erroneous link in the libssl1.0.0 package
** Changed in: openssl (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1297025 Title: Either the changelog.gz is missing or there is an erroneous link in the libssl1.0.0 package Status in openssl package in Ubuntu: In Progress Bug description: In libssl-dev for both Precise and Saucy packages for libssl-dev, there is a broken link: # ls -l /usr/share/doc/libssl-dev/changelog.gz lrwxrwxrwx 1 root root 27 Jan 8 12:48 /usr/share/doc/libssl-dev/changelog.gz -> ../libssl1.0.0/changelog.gz # ls -l /usr/share/doc/libssl1.0.0/changelog.gz ls: cannot access /usr/share/doc/libssl1.0.0/changelog.gz: No such file or directory I have verified this in both releases while trying to debug a failing build of a 3rd party library that links against these. Build works in Precise, fails in Saucy. Was looking to see what changed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1297025/+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 2033391] Re: Some Netplan-related autopkgtests are failing on armhf
Both tests that require building a kernel module are failing due to the new default gcc 794s autopkgtest [10:41:29]: test killswitches-no-urfkill: [--- 794s make -C /lib/modules/6.3.0-7-generic/build KBUILD_SRC=/lib/modules/6.3.0-7-generic/build M=/tmp/autopkgtest.6Iru72/build.A2V/src/debian/tests 794s make[1]: Entering directory '/usr/src/linux-headers-6.3.0-7-generic' 794s warning: the compiler differs from the one used to build the kernel 794s The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1) 12.3.0 794s You are using: 794s CC [M] /tmp/autopkgtest.6Iru72/build.A2V/src/debian/tests/fake-rfkill.o 794s /bin/sh: 1: gcc-12: not found 794s make[2]: *** [scripts/Makefile.build:260: /tmp/autopkgtest.6Iru72/build.A2V/src/debian/tests/fake-rfkill.o] Error 127 794s make[1]: *** [Makefile:2030: /tmp/autopkgtest.6Iru72/build.A2V/src/debian/tests] Error 2 794s make[1]: Leaving directory '/usr/src/linux-headers-6.3.0-7-generic' 794s make: *** [debian/tests/Makefile:5: fake-rfkill] Error 2 -- 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/2033391 Title: Some Netplan-related autopkgtests are failing on armhf Status in netplan.io package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in netplan.io source package in Mantic: New Status in network-manager source package in Mantic: New Bug description: The root cause appears to be NM not being ready yet when the test starts. # /usr/bin/python3 /tmp/autopkgtest.kW7u4i/build.K7E/src/debian/tests/nm_netplan.py test_nmcli_add_device_and_change_it (__main__.TestNetplan.test_nmcli_add_device_and_change_it) Uses the nmcli to add a connection and validates if the ... Warning: nmcli (1.44.0) and NetworkManager (Unknown) versions don't match. Restarting NetworkManager is advised. Error: NetworkManager is not running. FAIL We need to wait until Network Manager is ready before starting the test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2033391/+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 2032851] Re: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new apparmor package pre-installation script subprocess returned error exit status 1
I'm not sure if G is saying something similar above, but I found that performing the following steps when still on Ubuntu 18.04 allows for do- release-upgrade to complete successfully: sudo rm -r /etc/apparmor.d/cache/87595f25.0/ sudo rm -r /etc/apparmor.d/cache/bf9d6da9.0/ I think that these were the only subfolders in cache. There were other files in the cache folder, but I assume that rm can handle those. I wasn't sure if it was safe to delete the cache folder, but it didn't appear to be present after do-release-upgrade completed. -- 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/2032851 Title: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new apparmor package pre-installation script subprocess returned error exit status 1 Status in apparmor package in Ubuntu: Confirmed Bug description: package install error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: apparmor 2.12-4ubuntu5.3 ProcVersionSignature: Ubuntu 4.15.0-213.224-generic 4.15.18 Uname: Linux 4.15.0-213-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Aug 24 02:35:35 2023 DuplicateSignature: package:apparmor:2.12-4ubuntu5.3 Preparing to unpack .../16-apparmor_2.13.3-7ubuntu5.2_amd64.deb ... rm: cannot remove '/etc/apparmor.d/cache/bf9d6da9.0': Is a directory dpkg: error processing archive /tmp/apt-dpkg-install-InP0fz/16-apparmor_2.13.3-7ubuntu5.2_amd64.deb (--unpack): new apparmor package pre-installation script subprocess returned error exit status 1 ErrorMessage: new apparmor package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-08-22 (1 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-213-generic root=UUID=c5495aa8-cf2c-4042-a2ea-4533e9343808 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: apparmor Syslog: Aug 24 02:04:25 adminn-Lenovo-V110-15ISK dbus-daemon[4678]: [session uid=1000 pid=4678] AppArmor D-Bus mediation is enabled Aug 24 02:05:26 adminn-Lenovo-V110-15ISK dbus-daemon[856]: [system] AppArmor D-Bus mediation is enabled Aug 24 02:05:31 adminn-Lenovo-V110-15ISK dbus-daemon[1021]: [session uid=124 pid=1021] AppArmor D-Bus mediation is enabled Aug 24 02:06:04 adminn-Lenovo-V110-15ISK dbus-daemon[1506]: [session uid=1000 pid=1506] AppArmor D-Bus mediation is enabled Aug 24 03:39:11 adminn-Lenovo-V110-15ISK dbus-daemon[9963]: [session uid=0 pid=9956] AppArmor D-Bus mediation is enabled Title: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new apparmor package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2032851/+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 2029473] Re: Backport Ubuntu Pro to Xenial
** Description changed: + * Impact + + We want desktop integration with Ubuntu Pro + + * Test case + + - ensure that the machine isn't attached to ubuntu pro (otherwise the screen would not be displayed) and is online + $ pro status + and `$ pro detach` if needed + + - $ software-properties-gtk + -> the list of tabs should include an 'Ubuntu Pro' one + + The Ubuntu Pro tab should state 'This machine is not covered by an + Ubuntu Pro subscription', display a 'Enable Ubuntu Pro' button and have + other controls inactive + + - click 'Enable Ubuntu Pro' + -> A dialog 'Enable Ubuntu Pro' opens + -> the first option 'Enter code on ubuntu.com/pro/attach' is selected + -> a pincode is displayed under the option + + - go to http//ubuntu.com/pro/attach and enter the pincode + -> after some seconds the software-properties UI should update and display a green mark and 'Valid token' label on the right of the pincode + + - click 'Confirm' + -> you should get an authentification prompt + + - enter your password + -> a spinner starts animating instead of the 'Valid token' label + -> once the attachment job is done the dialog is autoclosed + -> the UI should now state 'Ubuntu Pro support is enabled', under Security 'ESM Infra', 'ESM Apps' and 'Kernel Livepatch' should be displayed an enabled + (or without 'ESM Apps' if you don't have the current ubuntu-advantage-tools) + + - check that the '$ pro status' output matches the UI one + + - try enabling/disable options + -> verify that the 'pro status' change accordingly + + - Click 'Disable Ubuntu Pro' + -> you get asked for confirmation and password + -> confirm that the UI is back to the original state and that 'pro status' confirm the system isn't attached to Ubuntu Pro anymore + + - Go through the testcase again but selecting the 'Or add token + manually' option, the steps should be similar + + * Regression Potential + + There could be problems in the UI + The new service could be not working as expected + Strings are new and currently have no translations + + The livepatch checkbox is also inactive because the current update- + notifier version in xenial doesn't include livepatch support + + + - + Ubuntu Pro enables extended support for 10 years for long term support Ubuntu series. Xenial is therefore currently also supported under Ubuntu Pro. Xenial's software-properties-gtk, however, doesn't have the Ubuntu Pro functionality that exists in Bionic, Focal etc. Thus this request to backport the Ubuntu Pro functionality to Xenial. This depends on LP:2029089. ** Changed in: software-properties (Ubuntu) Status: New => Fix Released ** Changed in: software-properties (Ubuntu Xenial) Status: In Progress => Fix Committed -- 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/2029473 Title: Backport Ubuntu Pro to Xenial Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: Fix Committed Bug description: * Impact We want desktop integration with Ubuntu Pro * Test case - ensure that the machine isn't attached to ubuntu pro (otherwise the screen would not be displayed) and is online $ pro status and `$ pro detach` if needed - $ software-properties-gtk -> the list of tabs should include an 'Ubuntu Pro' one The Ubuntu Pro tab should state 'This machine is not covered by an Ubuntu Pro subscription', display a 'Enable Ubuntu Pro' button and have other controls inactive - click 'Enable Ubuntu Pro' -> A dialog 'Enable Ubuntu Pro' opens -> the first option 'Enter code on ubuntu.com/pro/attach' is selected -> a pincode is displayed under the option - go to http//ubuntu.com/pro/attach and enter the pincode -> after some seconds the software-properties UI should update and display a green mark and 'Valid token' label on the right of the pincode - click 'Confirm' -> you should get an authentification prompt - enter your password -> a spinner starts animating instead of the 'Valid token' label -> once the attachment job is done the dialog is autoclosed -> the UI should now state 'Ubuntu Pro support is enabled', under Security 'ESM Infra', 'ESM Apps' and 'Kernel Livepatch' should be displayed an enabled (or without 'ESM Apps' if you don't have the current ubuntu-advantage-tools) - check that the '$ pro status' output matches the UI one - try enabling/disable options -> verify that the 'pro status' change accordingly - Click 'Disable Ubuntu Pro' -> you get asked for confirmation and password -> confirm that the UI is back to the original state and that 'pro status' confirm the system isn't attached to Ubuntu Pro anymore - Go through the testcase again but selecting the 'Or add token manually' option, the steps should be similar * R
[Touch-packages] [Bug 2033391] Re: Some Netplan-related autopkgtests are failing on armhf
I'm running some tests with the linked MP. ** Merge proposal linked: https://code.launchpad.net/~danilogondolfo/network-manager/+git/network-manager/+merge/450220 -- 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/2033391 Title: Some Netplan-related autopkgtests are failing on armhf Status in netplan.io package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in netplan.io source package in Mantic: New Status in network-manager source package in Mantic: New Bug description: The root cause appears to be NM not being ready yet when the test starts. # /usr/bin/python3 /tmp/autopkgtest.kW7u4i/build.K7E/src/debian/tests/nm_netplan.py test_nmcli_add_device_and_change_it (__main__.TestNetplan.test_nmcli_add_device_and_change_it) Uses the nmcli to add a connection and validates if the ... Warning: nmcli (1.44.0) and NetworkManager (Unknown) versions don't match. Restarting NetworkManager is advised. Error: NetworkManager is not running. FAIL We need to wait until Network Manager is ready before starting the test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2033391/+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 2030353] Re: Add infrastructure to support enabling userns restrictions via sysctl.d file
This bug was fixed in the package apparmor - 4.0.0~alpha2-0ubuntu2 --- apparmor (4.0.0~alpha2-0ubuntu2) mantic; urgency=medium * Fix invalid JSON output from aa-status --json via upstream patch (LP: #2032994) - d/p/u/binutils-aa_status.c-quiet-verbose-outputs-when-json.patch -- Alex Murray Fri, 25 Aug 2023 09:48:24 +0930 ** Changed in: apparmor (Ubuntu) Status: In Progress => Fix Released -- 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/2030353 Title: Add infrastructure to support enabling userns restrictions via sysctl.d file Status in apparmor package in Ubuntu: Fix Released Bug description: As per https://discourse.ubuntu.com/t/spec-unprivileged-user- namespace-restrictions-via-apparmor-in-ubuntu-23-10/37626, the apparmor binary package should provide a file named /usr/lib/sysctl.d/10-apparmor.conf that contains the following contents: # AppArmor restrictions of unprivileged user namespaces # Restrict the use of unprivileged user namespaces to applications # which have an AppArmor profile loaded which specifies the userns # permission. All other applications (whether confined by AppArmor # or not) will be denied the use of unprivileged user namespaces. # # See https://gitlab.com/apparmor/apparmor/-/wikis/unprivileged_userns_restriction # # If it is desired to disable this restriction, it is preferable to # create an additional file named /etc/sysctl.d/20-apparmor.conf # which will override this current file and sets this value to 0 # rather than editing this current file # THIS IS CURRENTLY DISABLED BUT WILL BE ENABLED IN A FUTURE UPLOAD # AS DETAILED ABOVE kernel.apparmor_restrict_unprivileged_userns = 0 If we enable this currently it would then cause existing applications which use unprivileged user namespaces in Ubuntu to fail - as such, this file will set the sysctl to 0 for now and will be updated in a future upload to enable it, along with a set of apparmor profiles for the various applications in the Ubuntu archive which require the use of unprivileged user namespaces. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2030353/+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 2032602] Re: [FFe] apparmor-4.0.0-alpha2 for unprivileged user namespace restrictions in mantic
This bug was fixed in the package apparmor - 4.0.0~alpha2-0ubuntu2 --- apparmor (4.0.0~alpha2-0ubuntu2) mantic; urgency=medium * Fix invalid JSON output from aa-status --json via upstream patch (LP: #2032994) - d/p/u/binutils-aa_status.c-quiet-verbose-outputs-when-json.patch -- Alex Murray Fri, 25 Aug 2023 09:48:24 +0930 ** Changed in: apparmor (Ubuntu) Status: Triaged => Fix Released -- 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/2032602 Title: [FFe] apparmor-4.0.0-alpha2 for unprivileged user namespace restrictions in mantic Status in apparmor package in Ubuntu: Fix Released Bug description: As per the spec documented at https://discourse.ubuntu.com/t/spec- unprivileged-user-namespace-restrictions-via-apparmor-in- ubuntu-23-10/37626 the Security team is enhancing AppArmor to allow the use of unprivileged user namespaces to be restricted to only those packages which require this. This change requires changes in both AppArmor within the kernel, as well as the apparmor package in the Ubuntu archive to ensure it supports the new syntax required. This has been extensively tested via the AppArmor regression test script in the QA Regression Testing repo: https://git.launchpad.net/qa-regression-testing/tree/scripts/test- apparmor.py This script runs various tests against the installed apparmor package, as well as building and running the various upstream regression and other test suites against this installed package: - https://gitlab.com/apparmor/apparmor/-/tree/master/tests/regression/apparmor?ref_type=heads - https://gitlab.com/apparmor/apparmor/-/tree/master/utils/test?ref_type=heads - https://gitlab.com/apparmor/apparmor/-/tree/master/parser/tst?ref_type=heads - https://gitlab.com/apparmor/apparmor/-/tree/master/libraries/libapparmor/testsuite?ref_type=heads The package can be found in https://launchpad.net/~alexmurray/+archive/ubuntu/apparmor-4.0.0-alpha2-for- mantic-take2 This includes build logs etc (e.g. for amd64 this is found at https://launchpad.net/~alexmurray/+archive/ubuntu/apparmor-4.0.0-alpha2-for- mantic-take2/+build/26530996) Note there is no ChangeLog file in upstream apparmor so instead I am attaching the git history between the current version of apparmor in mantic (3.0.8) and 4.0.0-alpha2. Also note that this new version of apparmor does not actually enable the user namespaces restriction yet - that is planned for a future upload (and hence a future FFe) - however, it lays all the groundwork to enable this, once sufficient testing and integration has been done across the rest of the Ubuntu archive and package ecosystem. As such, there is no risk of regression at this time due to that change - and the extensive regression testing also supports this conclusion as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2032602/+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 2032994] Re: apparmor 4.0.0~alpha2-0ubuntu1 has extra content in aa-status --json output
This bug was fixed in the package apparmor - 4.0.0~alpha2-0ubuntu2
---
apparmor (4.0.0~alpha2-0ubuntu2) mantic; urgency=medium
* Fix invalid JSON output from aa-status --json via upstream patch
(LP: #2032994)
- d/p/u/binutils-aa_status.c-quiet-verbose-outputs-when-json.patch
-- Alex Murray Fri, 25 Aug 2023 09:48:24
+0930
** Changed in: apparmor (Ubuntu)
Status: In Progress => Fix Released
--
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/2032994
Title:
apparmor 4.0.0~alpha2-0ubuntu1 has extra content in aa-status --json
output
Status in apparmor package in Ubuntu:
Fix Released
Bug description:
aa-status --json now includes an extra line of output before the
actual json output which breaks tools like jq:
$ sudo aa-status --json
apparmor module is loaded.
{"version": "2", "profiles": {"/snap/snapd/19993/usr/lib/snapd/snap-confine":
"enforce",
"/snap/snapd/19993/usr/lib/snapd/snap-confine//mount-namespace-capture-helper":
"enforce", "/usr/bin/man": "enforce", "/usr/bin/pidgin": "enforce",
"/usr/bin/pidgin//sanitized_helper": "enforce", "/usr/bin/totem": "enforce",
"/usr/bin/totem-audio-preview": "enforce", "/usr/bin/totem-video-thumbnailer":
"enforce", "/usr/bin/totem//sanitized_helper": "enforce",
"/usr/lib/NetworkManager/nm-dhcp-client.action": "enforce",
"/usr/lib/NetworkManager/nm-dhcp-helper": "enforce",
"/usr/lib/connman/scripts/dhclient-script": "enforce",
"/usr/lib/snapd/snap-confine": "enforce",
"/usr/lib/snapd/snap-confine//mount-namespace-capture-helper": "enforce",
"/{,usr/}sbin/dhclient": "enforce", "apt-cacher-ng": "enforce", "lsb_release":
"enforce", "man_filter": "enforce", "man_groff": "enforce", "nvidia_modprobe":
"enforce", "nvidia_modprobe//kmod": "enforce", "rsyslogd": "enforce",
"snap-update-ns.lxd": "enforce",
"snap.lxd.activate": "enforce", "snap.lxd.benchmark": "enforce",
"snap.lxd.buginfo": "enforce", "snap.lxd.check-kernel": "enforce",
"snap.lxd.daemon": "enforce", "snap.lxd.hook.configure": "enforce",
"snap.lxd.hook.install": "enforce", "snap.lxd.hook.remove": "enforce",
"snap.lxd.lxc": "enforce", "snap.lxd.lxc-to-lxd": "enforce", "snap.lxd.lxd":
"enforce", "snap.lxd.migrate": "enforce", "snap.lxd.user-daemon": "enforce",
"tcpdump": "enforce", "/usr/bin/irssi": "complain", "/usr/bin/ch-checkns":
"unconfined", "/usr/bin/ch-run": "unconfined", "/usr/bin/crun": "unconfined",
"/usr/bin/flatpak": "unconfined"}, "processes": {"/usr/sbin/rsyslogd":
[{"profile": "rsyslogd", "pid": "583", "status": "enforce"}]}
}
$ sudo aa-status --json | jq .
parse error: Invalid numeric literal at line 1, column 9
Proposed fix upstreeam
https://gitlab.com/apparmor/apparmor/-/merge_requests/1097
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2032994/+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 2033495] [NEW] [Z490 UD, Nvidia GPU 99 HDMI/DP, Digital Out, HDMI] No sound at all
Public bug reported: At some point, the hdmi sound card disappeared in the settings and I can’t restore it ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mea2375 F pulseaudio /dev/snd/controlC1: mea2375 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Aug 30 11:28:47 2023 InstallationDate: Installed on 2023-04-18 (133 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: TU116 High Definition Audio Controller - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mea2375 F pulseaudio /dev/snd/controlC1: mea2375 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [Z490 UD, Nvidia GPU 99 HDMI/DP, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22b dmi.board.asset.tag: Default string dmi.board.name: Z490 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22b:bd03/14/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnZ490UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ490UD:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Z490 MB dmi.product.name: Z490 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2033495 Title: [Z490 UD, Nvidia GPU 99 HDMI/DP, Digital Out, HDMI] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: At some point, the hdmi sound card disappeared in the settings and I can’t restore it ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mea2375 F pulseaudio /dev/snd/controlC1: mea2375 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Aug 30 11:28:47 2023 InstallationDate: Installed on 2023-04-18 (133 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: TU116 High Definition Audio Controller - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mea2375 F pulseaudio /dev/snd/controlC1: mea2375 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [Z490 UD, Nvidia GPU 99 HDMI/DP, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22b dmi.board.asset.tag: Default string dmi.board.name: Z490 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22b:bd03/14/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnZ490UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ490UD:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Z490 MB dmi.product.name: Z490 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2033495/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net
[Touch-packages] [Bug 1995790] Re: ?garbage does not work correctly in install commands
I can confirm that ?garbage does not work correctly in install commands (install, remove, purge, etc). Presumably the pattern is evaluated while an action group is preventing the cache from updating the garbage state and hence it evaluates to nothing. I can confirm that this works in focal but not in jammy, with those test cases: podman run --rm -it ubuntu:focal bash -c "apt update && apt install hello && apt-mark auto hello && apt remove ?garbage -y" podman run --rm -it ubuntu:jammy bash -c "apt update && apt install hello && apt-mark auto hello && apt remove ?garbage -y" Not sure when it regressed ** Summary changed: - apt-patterns does not work as described in man pages + ?garbage does not work correctly in install commands ** Changed in: apt (Ubuntu) Importance: Undecided => High ** Changed in: apt (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Tags added: foundations-todo ** Summary changed: - ?garbage does not work correctly in install commands + regression: ?garbage does not work correctly in install commands ** Also affects: apt (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Mantic) Importance: High Assignee: Julian Andres Klode (juliank) Status: Confirmed ** Also affects: apt (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Jammy) Status: New => Confirmed ** Changed in: apt (Ubuntu Lunar) Status: New => Confirmed ** Changed in: apt (Ubuntu Mantic) Status: Confirmed => 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/1995790 Title: regression: ?garbage does not work correctly in install commands Status in apt package in Ubuntu: Triaged Status in apt source package in Jammy: Confirmed Status in apt source package in Lunar: Confirmed Status in apt source package in Mantic: Triaged 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 1995790] Re: regression: ?garbage does not work correctly in install commands
I think this is a regression of "Call MarkAndSweep only manually in apt- get for autoremove" -- 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: Triaged Status in apt source package in Jammy: Confirmed Status in apt source package in Lunar: Confirmed Status in apt source package in Mantic: Triaged 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
