[Bug 2065300] Re: [SRU] New upstream microrelease .NET 6.0.30 and SDK 6.0.130
I sponsored these uploads. Waiting in the unapproved queue. ** Changed in: dotnet6 (Ubuntu Jammy) Status: New => In Progress ** Changed in: dotnet6 (Ubuntu Mantic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065300 Title: [SRU] New upstream microrelease .NET 6.0.30 and SDK 6.0.130 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2065300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
** Changed in: systemd (Ubuntu Jammy) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2034944] Re: proposed-migration for moc 1:2.6.0~svn-r3005-3build2
** Changed in: moc (Ubuntu) Assignee: Nick Rosbrook (enr0n) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2034944 Title: proposed-migration for moc 1:2.6.0~svn-r3005-3build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/moc/+bug/2034944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060846] Re: lsh-utils 2.1-14build2 FTBFS on armhf
** Changed in: lsh-utils (Ubuntu) Assignee: Nick Rosbrook (enr0n) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060846 Title: lsh-utils 2.1-14build2 FTBFS on armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsh-utils/+bug/2060846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2041833] Re: /lib/systemd/systemd-localed:6:__waitid:wait_for_terminate:wait_for_terminate_and_check:safe_fork_full:safe_fork
** Tags removed: foundations-todo ** Changed in: systemd (Ubuntu) Assignee: Nick Rosbrook (enr0n) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2041833 Title: /lib/systemd/systemd- localed:6:__waitid:wait_for_terminate:wait_for_terminate_and_check:safe_fork_full:safe_fork To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2041833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059044] Re: proposed-migration for sbcl 2:2.3.7-2
** Changed in: sbcl (Ubuntu) Assignee: Nick Rosbrook (enr0n) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059044 Title: proposed-migration for sbcl 2:2.3.7-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sbcl/+bug/2059044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2041834] Re: /lib/systemd/systemd-journald:6:__futex_abstimed_wait_common64:__futex_abstimed_wait_common:__GI___futex_abstimed_wait_cancelable64:__pthread_clockjoin_ex:___pthread_join
** Tags removed: foundations-todo ** Changed in: systemd (Ubuntu) Assignee: Nick Rosbrook (enr0n) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2041834 Title: /lib/systemd/systemd- journald:6:__futex_abstimed_wait_common64:__futex_abstimed_wait_common:__GI___futex_abstimed_wait_cancelable64:__pthread_clockjoin_ex:___pthread_join To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2041834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2020406] Re: Release upgrade fails due to unsupported DKMS modules
** Changed in: ubuntu-release-upgrader (Ubuntu) Assignee: Nick Rosbrook (enr0n) => (unassigned) ** Changed in: ubuntu-release-upgrader (Ubuntu Lunar) Assignee: Nick Rosbrook (enr0n) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2020406 Title: Release upgrade fails due to unsupported DKMS modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2020406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels
** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2037667 Title: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061148] Re: upgrading window shows %s instead of version number
** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061148 Title: upgrading window shows %s instead of version number To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2061148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067603] Re: systemd-pull missing
systemd specifies a Suggests: systemd-container. This is because it is not a hard dependency, but instead something you might want (systemd- sysupdate is a pretty new tool that by default does not have a lot of use on Ubuntu). You can install all such packages with apt install --install-suggests systemd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067603 Title: systemd-pull missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2067603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855140] Re: How to handle tmpfiles.d in non-systemd environments
Please re-open if there is still a relevant task here for systemd. I am taking the age/silence to suggest otherwise. ** Changed in: systemd (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855140 Title: How to handle tmpfiles.d in non-systemd environments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1855140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys
** Changed in: systemd (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718658 Title: ecryptfs-mount-private fails to initialize ecryptfs keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962061] Re: ZFS Key load error: Failed to open key material file: No such file or directory
Closing as per above comment. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962061 Title: ZFS Key load error: Failed to open key material file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963600] Re: On upgrade, systemctl and lightdm stop working, leaving the system in a degraded state
Please open a new bug if this is still observed on newer releases. ** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963600 Title: On upgrade, systemctl and lightdm stop working, leaving the system in a degraded state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1963600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871726] Re: "systemd --user" and child processes fail to exit when user logs out
Please open a new bug if this is still observed on newer releases. ** Changed in: systemd (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871726 Title: "systemd --user" and child processes fail to exit when user logs out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1871726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939196] Re: systemd --user children processes not stopped afer logout
Please open a new bug if this is still observed on newer releases. ** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939196 Title: systemd --user children processes not stopped afer logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1939196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950850] Re: Systemd-resolved gets confused and replies to SOA queries for local breaking mDNS resolution
Please open a new bug if this is still observed on newer releases. ** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950850 Title: Systemd-resolved gets confused and replies to SOA queries for local breaking mDNS resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1950850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951701] Re: systemd-resolved doesn't play well with dnsmasq cname entries
Please open a new bug if this is still observed on newer releases. ** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951701 Title: systemd-resolved doesn't play well with dnsmasq cname entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1951701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952784] Re: systemd-resolved cannot do dns over tls with server using self signed certificates
Thank you for taking the time to report this bug and helping to make Ubuntu better. I suspect a support site would be more appropriate, e.g. https://askubuntu.com, or for more options please look at https://discourse.ubuntu.com/t/community-support/709. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952784 Title: systemd-resolved cannot do dns over tls with server using self signed certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954698] Re: Cannot read exit status/time for type=forking w/ short-lived command
Please open a new bug if this is still observed on newer releases. ** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954698 Title: Cannot read exit status/time for type=forking w/ short-lived command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1954698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954814] Re: systemd.resolved with split domains sends DNS requests to the wrong interface
Please open a new bug if this is still observed on newer releases. ** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954814 Title: systemd.resolved with split domains sends DNS requests to the wrong interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1954814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956447] Re: "No DNS servers known" in /run/systemd/resolve/resolv.conf
Please open a new bug if this is still observed on newer releases. ** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956447 Title: "No DNS servers known" in /run/systemd/resolve/resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1956447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905688] Re: systemd-timesyncd.service: Timed out waiting for reply from NTP server
Closing due to age. ** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905688 Title: systemd-timesyncd.service: Timed out waiting for reply from NTP server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876071] Re: text cursor is moved to start of line even if in login prompt
Closing due to age. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Changed in: util-linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876071 Title: text cursor is moved to start of line even if in login prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1876071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049977] Re: journalctl --follow --grep lists lines in wrong order
I am not seeing this. Please open a new bug with a simple reproducer if it is still an issue on 24.04 or newer. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049977 Title: journalctl --follow --grep lists lines in wrong order To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2049977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2045159] Re: Adt failures for mantic:linux-6.5 kernels
** Changed in: systemd (Ubuntu Mantic) Status: New => Won't Fix ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2045159 Title: Adt failures for mantic:linux-6.5 kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2045159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2004179] Re: neutron-linuxbridge-agent flat network incompatibility with systemd-networkd
Is this fixed in 24.04? KeepMaster= is usable there. Unfortunately, I do not think this would be suitable for SRU to 22.04 given the scope of the new feature. ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2004179 Title: neutron-linuxbridge-agent flat network incompatibility with systemd- networkd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2004179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2041523] Re: /usr/share/apport/whoopsie-upload-all: PermissionError: Permission denied: '/bin/systemctl'
** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2041523 Title: /usr/share/apport/whoopsie-upload-all: PermissionError: Permission denied: '/bin/systemctl' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2041523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920933] Re: live desktop system booted with ip=dhcp has the right lease, hostname not set at all
** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920933 Title: live desktop system booted with ip=dhcp has the right lease, hostname not set at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1920933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2036592] Re: Slow reported boot in VM
Please open a new bug if you observe this on 24.04 or newer. ** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2036592 Title: Slow reported boot in VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038433] Re: systemd autopkgtest regression on arm64 and s390x on mantic
Please open a new bug if this is seen on Noble or newer. ** Changed in: systemd (Ubuntu Mantic) Status: New => Won't Fix ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038433 Title: systemd autopkgtest regression on arm64 and s390x on mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039571] Re: systemd-modules-load fails on Azure 23.10 images on arm64
Please re-open if this is still an issue. ** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid ** Changed in: systemd (Ubuntu Mantic) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2039571 Title: systemd-modules-load fails on Azure 23.10 images on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2039571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062542] Re: systemd-resolved stub gives SERVFAIL for DNSSEC negative response
** Changed in: systemd (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062542 Title: systemd-resolved stub gives SERVFAIL for DNSSEC negative response To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2062542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2035122] Re: Under ubuntu core/core-desktop, /etc/default/locale is not modifiable
I am dropping these patches from systemd in 24.10. We need an upstream solution to this, and there is one in progress. ** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2035122 Title: Under ubuntu core/core-desktop, /etc/default/locale is not modifiable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057768] Re: Unit and its Alias appear to be separate entities when enabling the unit by filepath
This is fixed in v256, which is in oracular-proposed. This won't get closed automatically when it migrates, so I'm just closing it early so I don't forget. ** Changed in: systemd (Ubuntu Jammy) Status: Confirmed => Won't Fix ** Changed in: systemd (Ubuntu Focal) Status: Confirmed => Won't Fix ** Also affects: systemd (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Noble) Status: New => Triaged ** Changed in: systemd (Ubuntu Noble) Importance: Undecided => Wishlist ** Changed in: systemd (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057768 Title: Unit and its Alias appear to be separate entities when enabling the unit by filepath To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2057768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."
** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587142 Title: Shutdown hangs in md kworker after "Reached target Shutdown." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1587142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046486] Re: units with SetCredential= fail in LXD containers
** Changed in: systemd (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046486 Title: units with SetCredential= fail in LXD containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2046486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046488] Re: test-execute fails on arhmf because of exec-basic.service
** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046488 Title: test-execute fails on arhmf because of exec-basic.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2046488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046562] Re: unit-tests fail on armhf because of exec-bindpaths.service in test-execute
** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046562 Title: unit-tests fail on armhf because of exec-bindpaths.service in test- execute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2046562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889068] Re: Improve resolved integration
As far as I know, this stuff has been done already? Not currently tracking anything left to do on systemd, so marking invalid. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889068 Title: Improve resolved integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1889068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791102] Re: udev postinst fails because kvm group already exists and is not a system group
The udev.postinst is completely different in Noble and newer, so I don't *think* there is anything to do in releases newer than Jammy. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Tags added: systemd-sru-next -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791102 Title: udev postinst fails because kvm group already exists and is not a system group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1791102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791102] Re: udev postinst fails because kvm group already exists and is not a system group
I've seen several reports of this for upgrades to Jammy, so it's probably worth fixing in a future SRU. ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Jammy) Status: New => Confirmed ** Changed in: systemd (Ubuntu Jammy) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791102 Title: udev postinst fails because kvm group already exists and is not a system group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1791102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065580] Re: package udev 249.11-0ubuntu3.12 failed to install/upgrade: подпроцесс из пакета udev установлен сценарий post-installation возвратил код ошибки 1
*** This bug is a duplicate of bug 1791102 *** https://bugs.launchpad.net/bugs/1791102 ** This bug has been marked a duplicate of bug 1791102 udev postinst fails because kvm group already exists and is not a system group -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065580 Title: package udev 249.11-0ubuntu3.12 failed to install/upgrade: подпроцесс из пакета udev установлен сценарий post-installation возвратил код ошибки 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2065580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874337] Re: resolvconf should never touch /etc/resolv.conf in Ubuntu; all DNS configuration from resolvconf, ifupdown, and dhclient should always be fed directly to systemd-resolved.
I don't think there is anything left in systemd to do for this. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874337 Title: resolvconf should never touch /etc/resolv.conf in Ubuntu; all DNS configuration from resolvconf, ifupdown, and dhclient should always be fed directly to systemd-resolved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1874337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060790] Re: package udev 249.11-0ubuntu3.12 failed to install/upgrade: subproces van pakket udev werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug
*** This bug is a duplicate of bug 1791102 *** https://bugs.launchpad.net/bugs/1791102 ** This bug is no longer a duplicate of bug 2065580 package udev 249.11-0ubuntu3.12 failed to install/upgrade: подпроцесс из пакета udev установлен сценарий post-installation возвратил код ошибки 1 ** This bug has been marked a duplicate of bug 1791102 udev postinst fails because kvm group already exists and is not a system group -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060790 Title: package udev 249.11-0ubuntu3.12 failed to install/upgrade: subproces van pakket udev werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2060790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870585] Re: Not cleaning /var/tmp by default
Debian is going back to upstream behavior for this, and we will follow (except for extending the clean up age for /tmp to 30d). This will be in the next oracular upload, but we won't backport. ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870585 Title: Not cleaning /var/tmp by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912855] Re: debugfs shouldn't be mounted by default
** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912855 Title: debugfs shouldn't be mounted by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1912855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2042756] Re: package systemd 252.5-2ubuntu3.2 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1
systemd 252 was in Lunar, which is EOL. ** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2042756 Title: package systemd 252.5-2ubuntu3.2 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2042756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2042825] Re: package udev 245.4-4ubuntu3.22 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1
** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Invalid ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2042825 Title: package udev 245.4-4ubuntu3.22 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2042825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054901] Re: Systemd fails to install on Noble arm64
Is this still an issue? My understanding was that there was some debootstrap issue, but that this is not actually related to systemd. Not sure if anything was fixed though. ** Changed in: systemd (Ubuntu) Status: New => Incomplete ** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054901 Title: Systemd fails to install on Noble arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/2054901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060790] Re: package udev 249.11-0ubuntu3.12 failed to install/upgrade: subproces van pakket udev werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug
*** This bug is a duplicate of bug 2065580 *** https://bugs.launchpad.net/bugs/2065580 ** This bug has been marked a duplicate of bug 2065580 package udev 249.11-0ubuntu3.12 failed to install/upgrade: подпроцесс из пакета udev установлен сценарий post-installation возвратил код ошибки 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060790 Title: package udev 249.11-0ubuntu3.12 failed to install/upgrade: subproces van pakket udev werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2060790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061366] Re: Garbage journald files at each boot are created on Ubuntu 24.04
This is just a debug message and can be ignored AFAICT. ** Changed in: systemd (Ubuntu) Status: New => Opinion ** Changed in: systemd (Ubuntu) Status: Opinion => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061366 Title: Garbage journald files at each boot are created on Ubuntu 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2061366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065580] Re: package udev 249.11-0ubuntu3.12 failed to install/upgrade: подпроцесс из пакета udev установлен сценарий post-installation возвратил код ошибки 1
** Tags added: systemd-sru-next -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065580 Title: package udev 249.11-0ubuntu3.12 failed to install/upgrade: подпроцесс из пакета udev установлен сценарий post-installation возвратил код ошибки 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2065580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062126] Re: Booting with laptop lid closed and external monitors on X11 causes the computer to sleep prior to login
Thank you for taking the time to report this bug and helping to make Ubuntu better. I suspect a support site would be more appropriate, e.g. https://askubuntu.com, or for more options please look at https://discourse.ubuntu.com/t/community-support/709. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062126 Title: Booting with laptop lid closed and external monitors on X11 causes the computer to sleep prior to login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2062126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064869] Re: systemd bluetooth not honoring stop service
This sounds like a bluez bug, not systemd. ** Package changed: systemd (Ubuntu) => bluez (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064869 Title: systemd bluetooth not honoring stop service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2064869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065580] Re: package udev 249.11-0ubuntu3.12 failed to install/upgrade: подпроцесс из пакета udev установлен сценарий post-installation возвратил код ошибки 1
** Changed in: systemd (Ubuntu) Importance: Undecided => Low ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Jammy) Status: New => Confirmed ** Changed in: systemd (Ubuntu Jammy) Importance: Undecided => Low ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065580 Title: package udev 249.11-0ubuntu3.12 failed to install/upgrade: подпроцесс из пакета udev установлен сценарий post-installation возвратил код ошибки 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2065580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066344] Re: netplan.io: autopkgtest fails with systemd 256
My understanding from the Debian bug is that this really is a netplan issue, not systemd. Is that accurate? ** Changed in: systemd (Ubuntu) Status: New => Incomplete ** Changed in: systemd (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066344 Title: netplan.io: autopkgtest fails with systemd 256 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2066344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067071] Re: cannot upgrade from 23.10 to 24.04, error in _install_t64_replacement_packages
** Changed in: ubuntu-release-upgrader (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067071 Title: cannot upgrade from 23.10 to 24.04, error in _install_t64_replacement_packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2067071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067603] Re: systemd-pull missing
systemd-pull is provided by the systemd-container package. Please install systemd-container and try again. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067603 Title: systemd-pull missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2067603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066700] Re: systemd-networkd is inactive by default since ubuntu 23.10?
As far as I know, systemd-networkd has never been enabled by default for Desktop installations. It is enabled by default on Server installations. ** Changed in: netplan.io (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066700 Title: systemd-networkd is inactive by default since ubuntu 23.10? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2066700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2047975] Re: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/reso
The autopkgtest regressions were all resolved with retries. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2047975 Title: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2047975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054761] Re: Dist upgrades from Jammy to Noble crash [Oh no! Something has gone wrong.]
The autopkgtest regressions were all resolved with retries. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054761 Title: Dist upgrades from Jammy to Noble crash [Oh no! Something has gone wrong.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2054761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064096] Re: Services fail to start in noble deployed with TPM+FDE
The autopkgtest regressions were all resolved with retries. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064096 Title: Services fail to start in noble deployed with TPM+FDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2064096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065964] Re: test-execute fails because of apparmor unprivileged userns restrictions
The autopkgtest regressions were all resolved with retries. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065964 Title: test-execute fails because of apparmor unprivileged userns restrictions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2065964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067071] Re: cannot upgrade from 23.10 to 24.04, error in _install_t64_replacement_packages
** Tags added: rls-nn-incoming ** Changed in: ubuntu-release-upgrader (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067071 Title: cannot upgrade from 23.10 to 24.04, error in _install_t64_replacement_packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2067071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067333] Re: hostnamectl --set-hostname doesn't update /etc/hosts
You could install libnss-myhostname (provided by systemd) instead of adding the hostname to /etc/hosts. libnss-myhostname takes care of mapping the local hostname to 127.0.0.1, so that listing the hostname explicitly in /etc/hosts is not necessary. See https://github.com/systemd/systemd/issues/12793 for more. Ubuntu does not ship libnss-myhostname by default, so I see why one would end up adding their hostname to /etc/hosts manually. But, from the upstream perspective, it is not necessary for systemd-hostnamed to modify /etc/hosts, so I don't think there is anything to do here. ** Bug watch added: github.com/systemd/systemd/issues #12793 https://github.com/systemd/systemd/issues/12793 ** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067333 Title: hostnamectl --set-hostname doesn't update /etc/hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2067333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065964] Re: test-execute fails because of apparmor unprivileged userns restrictions
This autopkgtest result for systemd 255.4-1ubuntu8.1 shows the unit- tests test now passing: https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/amd64/s/systemd/20240522_201458_f86bd@/log.gz. ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065964 Title: test-execute fails because of apparmor unprivileged userns restrictions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2065964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054761] Re: Dist upgrades from Jammy to Noble crash [Oh no! Something has gone wrong.]
I have verified the fix using systemd 255.4-1ubuntu8.1 from noble- proposed. On a Jammy Desktop system, I simply ran an upgrade: nr@clean-jammy-amd64:~$ wget http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz --2024-05-22 11:45:16-- http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz Resolving archive.ubuntu.com (archive.ubuntu.com)... 91.189.91.82, 185.125.190.36, 91.189.91.83, ... Connecting to archive.ubuntu.com (archive.ubuntu.com)|91.189.91.82|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 1274850 (1.2M) [application/x-gzip] Saving to: \u2018noble.tar.gz\u2019 noble.tar.gz100%[===>] 1.21M --.-KB/sin 0.1s 2024-05-22 11:45:16 (9.20 MB/s) - \u2018noble.tar.gz\u2019 saved [1274850/1274850] nr@clean-jammy-amd64:~$ tar xf noble.tar.gz nr@clean-jammy-amd64:~$ sudo -E ./noble --frontend DistUpgradeViewNonInteractive [ ... ] The upgrade proceeded without issue. Namely, my session was not killed during the upgrade. nr@clean-jammy-amd64:~$ apt policy systemd systemd: Installed: 255.4-1ubuntu8.1 Candidate: 255.4-1ubuntu8.1 Version table: *** 255.4-1ubuntu8.1 500 500 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages 100 /var/lib/dpkg/status 255.4-1ubuntu8 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages ** Tags removed: verification-needed-noble ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054761 Title: Dist upgrades from Jammy to Noble crash [Oh no! Something has gone wrong.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2054761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2047975] Re: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/reso
I have verified the fix using 255.4-1ubuntu8.1 from noble-proposed. I created a LXD jammy container: root@j:~# cat /etc/os-release PRETTY_NAME="Ubuntu 22.04.4 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.4 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy And then disabled the stub-resolver according to the test plan: root@j:~# mkdir -p /etc/systemd/resolved.conf.d/ root@j:~# cat > /etc/systemd/resolved.conf.d/no-stub-resolver.conf << EOF [Resolve] DNSStubListener=no EOF root@j:~# ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf root@j:~# systemctl restart systemd-resolved root@j:~# systemctl status systemd-resolved ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2024-05-22 15:10:08 UTC; 19s ago Docs: man:systemd-resolved.service(8) man:org.freedesktop.resolve1(5) https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Main PID: 1079 (systemd-resolve) Status: "Processing requests..." Tasks: 1 (limit: 18947) Memory: 4.5M CPU: 57ms CGroup: /system.slice/systemd-resolved.service └─1079 /lib/systemd/systemd-resolved May 22 15:10:08 j systemd[1]: Starting Network Name Resolution... May 22 15:10:08 j systemd-resolved[1079]: Positive Trust Anchors: May 22 15:10:08 j systemd-resolved[1079]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7> May 22 15:10:08 j systemd-resolved[1079]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172> May 22 15:10:08 j systemd-resolved[1079]: Using system hostname 'j'. May 22 15:10:08 j systemd[1]: Started Network Name Resolution. Then, started the upgrade (using the tarball for the reasons mentioned in test plan): root@j:~# wget http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz --2024-05-22 15:10:36-- http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz Resolving archive.ubuntu.com (archive.ubuntu.com)... 185.125.190.39, 91.189.91.82, 185.125.190.36, ... Connecting to archive.ubuntu.com (archive.ubuntu.com)|185.125.190.39|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 1274850 (1.2M) [application/x-gzip] Saving to: ‘noble.tar.gz’ noble.tar.gz 100%[>] 1.21M 1.73MB/sin 0.7s 2024-05-22 15:10:37 (1.73 MB/s) - ‘noble.tar.gz’ saved [1274850/1274850] root@j:~# tar xf noble.tar.gz root@j:~# ./noble --frontend DistUpgradeViewNonInteractive [ ... ] After the upgrade was complete: root@j:~# systemctl status systemd-resolved ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled) Active: active (running) since Wed 2024-05-22 15:17:26 UTC; 15min ago Docs: man:systemd-resolved.service(8) man:org.freedesktop.resolve1(5) https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Main PID: 1076 (systemd-resolve) Status: "Processing requests..." Tasks: 1 (limit: 18947) Memory: 4.6M (peak: 5.1M) CPU: 63ms CGroup: /system.slice/systemd-resolved.service └─1076 /lib/systemd/systemd-resolved May 22 15:17:26 j systemd[1]: Starting Network Name Resolution... May 22 15:17:26 j systemd-resolved[1076]: Positive Trust Anchors: May 22 15:17:26 j systemd-resolved[1076]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7> May 22 15:17:26 j systemd-resolved[1076]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172> May 22 15:17:26 j systemd-resolved[1076]: Using system hostname 'j'. May 22 15:17:26 j systemd[1]: Started Network Name Resolution. root@j:~# cat /etc/resolv.conf # This is /run/systemd/resolve/resolv.conf managed by man:systemd-resolved(8). # Do not edit. # # This file might be symlinked as /etc/resolv.conf. If you're looking at # /etc/resolv.conf and seeing this text, you have followed the symlink. # # This is a dynamic resolv.conf file for connecting local clients directly to # all known uplink DNS servers. This file lists all configured search domains. # # Third party programs should typically not access this file directly, but only # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in
[Bug 2064096] Re: Services fail to start in noble deployed with TPM+FDE
I have verified the fix according to the test plan above, using 255.4-1ubuntu8.1 from noble-proposed. Note, as I mentioned in an earlier comment, this fix is NOT available on Desktop with TPM FDE until the appropriate snap is rebuilt. I have previously prepared a noble VM, and installed dracut for generating the initrd, which means running systemd in the initrd. Currently, I can see the AppArmor denials for rsyslog: ubuntu@ubuntu:~$ sudo dmesg | grep rsyslog [2.816998] systemd[1]: unit_file_build_name_map: normal unit file: /usr/lib/systemd/system/rsyslog.service [5.588869] audit: type=1400 audit(1716388183.334:149): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="rsyslogd" pid=993 comm="apparmor_parser" [5.676353] audit: type=1400 audit(1716388183.422:150): apparmor="DENIED" operation="sendmsg" class="file" info="Failed name lookup - disconnected path" error=-13 profile="rsyslogd" name="systemd/notify" pid=1055 comm="rsyslogd" requested_mask="w" denied_mask="w" fsuid=102 ouid=0 [5.676388] audit: type=1400 audit(1716388183.422:151): apparmor="DENIED" operation="sendmsg" class="file" info="Failed name lookup - disconnected path" error=-13 profile="rsyslogd" name="systemd/journal/dev-log" pid=1055 comm="rsyslogd" requested_mask="w" denied_mask="w" fsuid=102 ouid=0 [5.676407] audit: type=1400 audit(1716388183.422:152): apparmor="DENIED" operation="sendmsg" class="file" info="Failed name lookup - disconnected path" error=-13 profile="rsyslogd" name="systemd/journal/dev-log" pid=1055 comm="rsyslogd" requested_mask="w" denied_mask="w" fsuid=102 ouid=0 [5.676425] audit: type=1400 audit(1716388183.422:153): apparmor="DENIED" operation="sendmsg" class="file" info="Failed name lookup - disconnected path" error=-13 profile="rsyslogd" name="systemd/journal/dev-log" pid=1055 comm="rsyslogd" requested_mask="w" denied_mask="w" fsuid=102 ouid=0 [5.676440] audit: type=1400 audit(1716388183.422:154): apparmor="DENIED" operation="sendmsg" class="file" info="Failed name lookup - disconnected path" error=-13 profile="rsyslogd" name="systemd/journal/dev-log" pid=1055 comm="rsyslogd" requested_mask="w" denied_mask="w" fsuid=102 ouid=0 [ 95.610731] audit: type=1400 audit(1716388273.356:166): apparmor="DENIED" operation="sendmsg" class="file" info="Failed name lookup - disconnected path" error=-13 profile="rsyslogd" name="systemd/journal/dev-log" pid=1055 comm="rsyslogd" requested_mask="w" denied_mask="w" fsuid=102 ouid=0 [ 95.974029] audit: type=1400 audit(1716388273.719:167): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="rsyslogd" pid=2072 comm="apparmor_parser" [ 96.010658] audit: type=1400 audit(1716388273.756:168): apparmor="DENIED" operation="sendmsg" class="file" info="Failed name lookup - disconnected path" error=-13 profile="rsyslogd" name="systemd/notify" pid=2073 comm="rsyslogd" requested_mask="w" denied_mask="w" fsuid=102 ouid=0 [ 96.010664] audit: type=1400 audit(1716388273.756:169): apparmor="DENIED" operation="sendmsg" class="file" info="Failed name lookup - disconnected path" error=-13 profile="rsyslogd" name="systemd/journal/dev-log" pid=2073 comm="rsyslogd" requested_mask="w" denied_mask="w" fsuid=102 ouid=0 [ 96.010666] audit: type=1400 audit(1716388273.756:170): apparmor="DENIED" operation="sendmsg" class="file" info="Failed name lookup - disconnected path" error=-13 profile="rsyslogd" name="systemd/journal/dev-log" pid=2073 comm="rsyslogd" requested_mask="w" denied_mask="w" fsuid=102 ouid=0 [ 96.010669] audit: type=1400 audit(1716388273.756:171): apparmor="DENIED" operation="sendmsg" class="file" info="Failed name lookup - disconnected path" error=-13 profile="rsyslogd" name="systemd/journal/dev-log" pid=2073 comm="rsyslogd" requested_mask="w" denied_mask="w" fsuid=102 ouid=0 [ 96.010670] audit: type=1400 audit(1716388273.756:172): apparmor="DENIED" operation="sendmsg" class="file" info="Failed name lookup - disconnected path" error=-13 profile="rsyslogd" name="systemd/journal/dev-log" pid=2073 comm="rsyslogd" requested_mask="w" denied_mask="w" fsuid=102 ouid=0 ubuntu@ubuntu:~$ apt policy systemd systemd: Installed: 255.4-1ubuntu8 Candidate: 255.4-1ubuntu8 Version table: 255.4-1ubuntu8.1 100 100 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages *** 255.4-1ubuntu8 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status Now, I install systemd from noble-proposed, and then re-generate the initrd so that the patched systemd is in the initrd: ubuntu@ubuntu:~$ sudo apt install systemd -y -t noble-proposed [ ... ] ubuntu@ubuntu:~$ sudo dracut --force dracut[I]: Executing: /usr/bin/dracut --force dracut[I]: Module 'mksh' will not be installed, because command 'mksh' could not be found! dracut[I]: Module
[Bug 2064096] Re: Services fail to start in noble deployed with TPM+FDE
@jamesps the affected systemd is the one runnning in the initrd. For desktop running TPM FDE, this will require having the pc-kernel(?) snap updated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064096 Title: Services fail to start in noble deployed with TPM+FDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2064096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065677] Re: package systemd-resolved 253.5-1ubuntu6.1 failed to install/upgrade: 已安装 systemd-resolved 软件包 post-installation 脚本 子进程返回错误状态 1
*** This bug is a duplicate of bug 2047975 *** https://bugs.launchpad.net/bugs/2047975 ** This bug has been marked a duplicate of bug 2047975 package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065677 Title: package systemd-resolved 253.5-1ubuntu6.1 failed to install/upgrade: 已安装 systemd-resolved 软件包 post-installation 脚本 子进程返回错误状态 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2065677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2047975] Re: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/reso
> This is related to https://discourse.ubuntu.com/t/ubuntu- desktop-s-24-10-dev-cycle-the-roadmap/45120 right? I don't see how this is related. > Once I manually installed systemd-resolved, all the above were fixed. This bug is not about systemd-resolved not getting installed on upgrades (that is bug 2063464). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2047975 Title: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2047975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2047975] Re: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/reso
** Changed in: systemd (Ubuntu Noble) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2047975 Title: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2047975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054761] Re: Dist upgrades from Jammy to Noble crash [Oh no! Something has gone wrong.]
This is not a problem for oracular, because no supported upgrade paths to oracular would have an old enough systemd to hit this. ** Also affects: mutter (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Noble) Status: New => In Progress ** Changed in: systemd (Ubuntu Noble) Importance: Undecided => High ** Changed in: systemd (Ubuntu Noble) Assignee: (unassigned) => Nick Rosbrook (enr0n) ** Changed in: systemd (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054761 Title: Dist upgrades from Jammy to Noble crash [Oh no! Something has gone wrong.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2054761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064096] Re: Services fail to start in noble deployed with TPM+FDE
** Changed in: systemd (Ubuntu Noble) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064096 Title: Services fail to start in noble deployed with TPM+FDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2064096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065964] Re: test-execute fails because of apparmor unprivileged userns restrictions
** Changed in: systemd (Ubuntu Noble) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065964 Title: test-execute fails because of apparmor unprivileged userns restrictions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2065964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064096] Re: Services fail to start in noble deployed with TPM+FDE
** Description changed: [Impact] On systems that have systemd in the initrd, after the switch root, services trying to access resources in /run (e.g. /run/systemd/notify) will get AppArmor denials. This is because as a part of the switch root, before the pivot_root(), the /run (and /proc, /sys, /dev) are "moved" with a bind mount. Hence the new /run has a different mount id, and AppArmor thinks that e.g. /run/systemd/notify is disconnected from the current mount tree. [Test Plan] The simplest way to test this is to use dracut on a classic Ubuntu system: 1. Create a VM running Ubuntu 24.04 LTS. The virtualization implementation is not important. 2. Install dracut, and then reboot. $ apt install -y dracut 3. Once rebooted, verify that systemd did a switch root: $ journalctl -b --grep "Switching root" 4. Check for rsyslog AppArmor denials: $ dmesg | grep rsyslog On an affected system, the denials will be present. With the patch, there should be no denials (or at least not related to accessing files in /run). [Where problems could occur] - TODO + Using MS_MOVE rather than MS_BIND for /run during the switch root means that there is a brief time where /run (in the old root) is not available for units running before the pivot_root(). So, if we were to see problems, it would likely + be related to problems with resources in /run, very close to the switch root timeframe. However, before noble, the switch root *is* done using MS_MOVE on /run (and /proc, /sys, and /dev), so have reasonable evidence that this is a safe change. + + [Other information] + + We only change the flags for /run because that is the filesystem that + seems affected in practice. In particular, we leave /proc alone because + code in systemd may use /proc between the time it is moved to the new + root, but before the pivot_root(), which would be a riskier change. [Original Description] What's known so far: - 24.04 desktop deployed with TPM+FDE shows this bug - services confined with apparmor that need to access something in /run/systemd (like the notify socket) fail to do so, even if the apparmor profile is in complain mode. And the apparmor profile does already have rules to allow that access - only after running aa-disable can the service start fine - paths logged by the apparmor DENIED or ALLOWED messages are missing the "/run" prefix from "/run/systemd/..". - When we add rules to the profile using "/systemd/" (i.e., also dropping the /run prefix), then it works - other access in /run/systemd/ are also blocked, but the most noticeable one is the notify mechanism - comment #2 also states that azure CVM images are also impacted - comment #4 has instructions on how to create such a VM locally with LXD vms Original description follows: This might be related to #2064088 The rsyslog service is continually timing out and restarting. If I use a service drop-in file and change the 'Type' from 'notify' to 'simple', the service starts and appears to work normally. In the journal, I can see the attached apparmor errors. I can't make sense of them, but if it's a similar issue to #2064088, then I suspect apparmor is preventing the systemd notify function from alerting systemd that the service is up and running. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: rsyslog 8.2312.0-3ubuntu9 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 10:37:46 2024 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064096 Title: Services fail to start in noble deployed with TPM+FDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2064096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064096] Re: Services fail to start in noble deployed with TPM+FDE
** Description changed: + [Impact] + + On systems that have systemd in the initrd, after the switch root, + services trying to access resources in /run (e.g. /run/systemd/notify) + will get AppArmor denials. This is because as a part of the switch root, + before the pivot_root(), the /run (and /proc, /sys, /dev) are "moved" + with a bind mount. Hence the new /run has a different mount id, and + AppArmor thinks that e.g. /run/systemd/notify is disconnected from the + current mount tree. + + [Test Plan] + + The simplest way to test this is to use dracut on a classic Ubuntu + system: + + 1. Create a VM running Ubuntu 24.04 LTS. The virtualization implementation is not important. + 2. Install dracut, and then reboot. + + $ apt install -y dracut + + 3. Once rebooted, verify that systemd did a switch root: + + $ journalctl -b --grep "Switching root" + + 4. Check for rsyslog AppArmor denials: + + $ dmesg | grep rsyslog + + On an affected system, the denials will be present. With the patch, + there should be no denials (or at least not related to accessing files + in /run). + + [Where problems could occur] + + TODO + + [Original Description] + What's known so far: - 24.04 desktop deployed with TPM+FDE shows this bug - services confined with apparmor that need to access something in /run/systemd (like the notify socket) fail to do so, even if the apparmor profile is in complain mode. And the apparmor profile does already have rules to allow that access - only after running aa-disable can the service start fine - paths logged by the apparmor DENIED or ALLOWED messages are missing the "/run" prefix from "/run/systemd/..". - When we add rules to the profile using "/systemd/" (i.e., also dropping the /run prefix), then it works - other access in /run/systemd/ are also blocked, but the most noticeable one is the notify mechanism - comment #2 also states that azure CVM images are also impacted - comment #4 has instructions on how to create such a VM locally with LXD vms Original description follows: This might be related to #2064088 The rsyslog service is continually timing out and restarting. If I use a service drop-in file and change the 'Type' from 'notify' to 'simple', the service starts and appears to work normally. In the journal, I can see the attached apparmor errors. I can't make sense of them, but if it's a similar issue to #2064088, then I suspect apparmor is preventing the systemd notify function from alerting systemd that the service is up and running. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: rsyslog 8.2312.0-3ubuntu9 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 10:37:46 2024 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064096 Title: Services fail to start in noble deployed with TPM+FDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2064096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054761] Re: Dist upgrades from Jammy to Noble crash [Oh no! Something has gone wrong.]
** Description changed: + [Impact] + During upgrades from Jammy to Noble, systemd.postinst trys to reexec all running user managers. It does so using a feature that was not added until v250, and attempting this against a v249 daemon results in it being killed instead, which brings down all user sessions. + + Hence, during the upgrades, the user session is killed, and the system + is left in a bad state. + + [Test Plan] + + Run an upgrade from Jammy to Noble on Ubuntu desktop. The upgrade should + proceed normally (or at least not have the entire session killed by + systemd.postinst). + + [Where problems could occur] + + The fix is to add a version guard against this logic in + systemd.postinst. If the version string was wrong or typo'd, the fix + would not work as expected. + + [Original Description] + Feb 21 21:39:12 autopkgtest gnome-shell[17945]: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients' Feb 21 21:39:12 autopkgtest gnome-session-binary[17908]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5 Feb 21 21:39:12 autopkgtest gnome-shell[17959]: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients' Feb 21 21:39:12 autopkgtest gnome-session-binary[17908]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5 https://errors.ubuntu.com/problem/bf714caff944bed915a3c4321664107c65547d1f https://errors.ubuntu.com/problem/db8f7e3dfc79e658b9b2aa8c596b014ce4b9f217 https://errors.ubuntu.com/oops/af2e99fc-d101-11ee-8a58-fa163ec8ca8c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054761 Title: Dist upgrades from Jammy to Noble crash [Oh no! Something has gone wrong.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2054761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2047975] Re: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/reso
** Description changed: [Impact] For users that disabled the stub-resolver, and in doing so also created a symlink /etc/resolv.conf -> /run/systemd/resolve/resolv.conf (note this is not the correct way to disable the stub-resolver), upgrading from Jammy to Noble will fail with: cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file This logic in systemd-resolved.postinst is guarded by a version check, and is only run on upgrades from systemd versions before 251.4-2 (which in practice means only upgrades from Jammy), and on new installs. [Test Plan] Start a VM or container running Jammy. Disable the stub-resolver, and create the symlink /etc/resolv.conf -> /run/systemd/resolve/resolv.conf: $ mkdir -p /etc/systemd/resolved.conf.d/ $ cat > /etc/systemd/resolved.conf.d/no-stub-resolver.conf << EOF [Resolve] DNSStubListener=no EOF - $ sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf - $ sudo systemctl restart systemd-resolved + $ ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf + $ systemctl restart systemd-resolved Then, run an upgrade to Noble: $ do-release-upgrade --devel NB that currently, even devel upgrades are disabled to from Jammy to Noble, so the upgrade would need to be run as: - $ wget http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/ $ tar xf noble.tar.gz - $ ./noble + $ wget http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/ + $ tar xf noble.tar.gz + $ ./noble Inspect the relevant output and logs to ensure that systemd-resolved was upgraded successfully during the upgrade. [Where problems could occur] The fix is to make such a failure non-fatal. This is safe because although manually creating this symlink is not necessary, it will not impact the operation of systemd-resolved. Hence, failing to make this cp will not impact the user. Later in the postinst, we force the new symlink anyways. If something was wrong with the change, it would likely cause the systemd-resolved.postinst to fail a different way. [Original Description] upgraded from 22.04 -> 24.04 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: systemd-resolved 253.5-1ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Wed Jan 3 21:06:55 2024 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-02-27 (311 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.1ubuntu5 apt 2.7.6 SourcePackage: systemd Title: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-01-03 (0 days ago) mtime.conffile..etc.systemd.resolved.conf: 2023-02-27T21:16:55.869158 ** Description changed: [Impact] For users that disabled the stub-resolver, and in doing so also created a symlink /etc/resolv.conf -> /run/systemd/resolve/resolv.conf (note this is not the correct way to disable the stub-resolver), upgrading from Jammy to Noble will fail with: cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file This logic in systemd-resolved.postinst is guarded by a version check, and is only run on upgrades from systemd versions before 251.4-2 (which in practice means only upgrades from Jammy), and on new installs. [Test Plan] Start a VM or container running Jammy. Disable the stub-resolver, and create the symlink /etc/resolv.conf -> /run/systemd/resolve/resolv.conf: $ mkdir -p /etc/systemd/resolved.conf.d/ $ cat > /etc/systemd/resolved.conf.d/no-stub-resolver.conf << EOF [Resolve] DNSStubListener=no EOF $ ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf $ systemctl restart systemd-resolved Then, run an upgrade to Noble: $ do-release-upgrade --devel NB that currently, even devel upgrades are disabled to from Jammy to Noble, so the upgrade would need to be run as: - $ wget http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/ + $ wget http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz $ tar xf noble.tar.gz $ ./noble Inspect the relevant output and logs to ensure that systemd-resolved was upgraded successfully during the
[Bug 2065229] Re: Upgrades to 24.04 LTS should be temporarily prevented for TPM FDE systems
I have verified using the upgrader tarball for noble-proposed. To create a VM with Ubuntu Desktop TPM FDE, I did the following: $ lxc storage volume import default ~/downloads/ubuntu-23.10.1-desktop-amd64.iso 23.10-desktop --type=iso $ lxc init --empty --vm lxd-mantic-fde -c limits.memory=6GiB -c limits.cpu=4 -d root,size=32GiB $ lxc config device add lxd-mantic-fde iso-volume disk pool=default source=23.10-desktop boot.priority=10 $ lxc config device add lxd-mantic-fde tpm tpm $ lxc start --console=vga lxd-mantic-fde I went through the installer, and selected TPM FDE from advanced features. Then, after the installation, I ran the following in the VM: ubuntu@ubuntu:~$ wget http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz --2024-05-17 11:02:12-- http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz Resolving archive.ubuntu.com (archive.ubuntu.com)... 185.125.190.39, 91.189.91.82, 185.125.190.36, ... Connecting to archive.ubuntu.com (archive.ubuntu.com)|185.125.190.39|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 1274850 (1.2M) [application/x-gzip] Saving to: \u2018noble.tar.gz\u2019 noble.tar.gz100%[===>] 1.21M 542KB/sin 2.3s 2024-05-17 11:02:14 (542 KB/s) - \u2018noble.tar.gz\u2019 saved [1274850/1274850] ubuntu@ubuntu:~$ tar xf noble.tar.gz ubuntu@ubuntu:~$ sudo ./noble --frontend DistUpgradeViewText Reading cache Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://security.ubuntu.com/ubuntu mantic-security InRelease Hit http://nl.archive.ubuntu.com/ubuntu mantic InRelease Hit http://nl.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://nl.archive.ubuntu.com/ubuntu mantic-backports InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Sorry, cannot upgrade this system to 24.04 LTS Upgrades for desktop systems running TPM FDE are not currently supported. Please see https://launchpad.net/bugs/2065229 for more information. Restoring original system state Aborting Reading package lists... Done Building dependency tree... Done Reading state information... Done So, the upgrade was blocked as expected. I also tested in a container to make sure that upgrades were not prevented there: nr@six:~$ lxc launch ubuntu-daily:mantic mantic Creating mantic Starting mantic nr@six:~$ lxc exec mantic bash root@mantic:~# wget http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz --2024-05-17 09:11:47-- http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz Resolving archive.ubuntu.com (archive.ubuntu.com)... 91.189.91.83, 91.189.91.81, 185.125.190.39, ... Connecting to archive.ubuntu.com (archive.ubuntu.com)|91.189.91.83|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 1274850 (1.2M) [application/x-gzip] Saving to: ‘noble.tar.gz’ noble.tar.gz 100%[>] 1.21M 130KB/sin 9.6s 2024-05-17 09:11:58 (130 KB/s) - ‘noble.tar.gz’ saved [1274850/1274850] root@mantic:~# tar xf noble.tar.gz root@mantic:~# ./noble [ ... ] Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating the changes Calculating the changes Do you want to start the upgrade? 2 installed packages are no longer supported by Canonical. You can still get support from the community. 44 packages are going to be removed. 64 new packages are going to be installed. 492 packages are going to be upgraded. You have to download a total of 194 M. This download will take about 38 seconds with a 40Mbit connection and about 5 minutes with a 5Mbit connection. Fetching and installing the upgrade can take several hours. Once the download has finished, the process cannot be canceled. Continue [yN] Details [d] Hence, I was allowed to complete the upgrade. Finally, I tried an upgrade from a normal (non-TPM FDE) VM: nr@six:~$ lxc launch images:ubuntu/23.10/desktop ubuntu --vm -c limits.cpu=4 -c limits.memory=4GiB --console=vga [...] ubuntu@ubuntu:~$ wget http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz --2024-05-17 09:54:09-- http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz Resolving archive.ubuntu.com (archive.ubuntu.com)... 91.189.91.83, 185.125.190.36, 91.189.91.81, ... Connecting to
[Bug 2047975] Re: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/reso
** Description changed: + [Impact] + + For users that disabled the stub-resolver, and in doing so also created + a symlink /etc/resolv.conf -> /run/systemd/resolve/resolv.conf (note + this is not the correct way to disable the stub-resolver), upgrading + from Jammy to Noble will fail with: + + cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are + the same file + + This logic in systemd-resolved.postinst is guarded by a version check, + and is only run on upgrades from systemd versions before 251.4-2 (which + in practice means only upgrades from Jammy), and on new installs. + + [Test Plan] + + Start a VM or container running Jammy. Disable the stub-resolver, and + create the symlink /etc/resolv.conf -> /run/systemd/resolve/resolv.conf: + + $ mkdir -p /etc/systemd/resolved.conf.d/ + $ cat > /etc/systemd/resolved.conf.d/no-stub-resolver.conf << EOF + [Resolve] + DNSStubListener=no + EOF + + $ sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf + $ sudo systemctl restart systemd-resolved + + Then, run an upgrade to Noble: + + $ do-release-upgrade --devel + + NB that currently, even devel upgrades are disabled to from Jammy to + Noble, so the upgrade would need to be run as: + + $ wget http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/ $ tar xf noble.tar.gz + $ ./noble + + Inspect the relevant output and logs to ensure that systemd-resolved was + upgraded successfully during the upgrade. + + [Where problems could occur] + + The fix is to make such a failure non-fatal. This is safe because + although manually creating this symlink is not necessary, it will not + impact the operation of systemd-resolved. Hence, failing to make this cp + will not impact the user. Later in the postinst, we force the new + symlink anyways. + + If something was wrong with the change, it would likely cause the + systemd-resolved.postinst to fail a different way. + + [Original Description] + upgraded from 22.04 -> 24.04 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: systemd-resolved 253.5-1ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Wed Jan 3 21:06:55 2024 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-02-27 (311 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: - dpkg 1.22.1ubuntu5 - apt 2.7.6 + dpkg 1.22.1ubuntu5 + apt 2.7.6 SourcePackage: systemd Title: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-01-03 (0 days ago) mtime.conffile..etc.systemd.resolved.conf: 2023-02-27T21:16:55.869158 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2047975 Title: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2047975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2047975] Re: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/reso
** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2047975 Title: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2047975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065964] [NEW] test-execute fails because of apparmor unprivileged userns restrictions
Public bug reported: [Impact] unit-tests in noble currently fails because test-execute fails with the following: 1633s exec-basic.service: Child 1934 belongs to exec-basic.service. 1633s exec-basic.service: Control process exited, code=exited, status=0/SUCCESS (success) 1633s exec-basic.service: Got final SIGCHLD for state start-post. 1633s exec-basic.service: Deactivated successfully. 1633s exec-basic.service: Service will not restart (restart setting) 1633s exec-basic.service: Changed start-post -> dead 1633s exec-basic.service: Consumed 49ms CPU time. 1633s Spawning process to nuke '/tmp/systemd-private-dbf1f9a2e08f4741900f145a35ce7e30-exec-basic.service-ItwK5c' 1633s Successfully forked off intermediary '(sd-rmrf)' as PID 1936. 1633s Spawning process to nuke '/var/tmp/systemd-private-dbf1f9a2e08f4741900f145a35ce7e30-exec-basic.service-V50z4Q' 1633s Successfully forked off intermediary '(sd-rmrf)' as PID 1937. 1633s src/test/test-execute.c:1121:test_exec_basic: exec-basic.service: can_unshare=no: exit status 0, expected 226 1633s Skipping PR_SET_MM, as we don't have privileges. 1633s Skipping PR_SET_MM, as we don't have privileges. 1633s (test-execute-unprivileged) terminated by signal ABRT. 1633s Assertion 'r >= 0' failed at src/test/test-execute.c:1412, function prepare_ns(). Aborting. 1633s [...] 1678s [1mOK: 288 SKIP: 6 FAIL: 1[0m 1679s autopkgtest [20:59:40]: test unit-tests: ---] 1679s autopkgtest [20:59:40]: test unit-tests: - - - - - - - - - - results - - - - - - - - - - 1679s unit-tests FAIL non-zero exit status 1 This is because some tests in test-execute run unprivileged, and try to user user namespaces. I fixed this upstream[1], so just backport the patch so that this test case no longer fails. [Test Plan] This only pertains to the unit-tests autopkgtest in systemd. Just check the result of the autopkgtest run. [Where problems could occur] This only changes the test-execute code to skip tests that require unprivileged userns whenever kernel.apparmor_restrict_unprivileged_userns=1. Hence, any problems would be limited to that test case within unit-tests. [Other information] Note that the upstream-2 test still has regular failures which need to be investigated, so this change will not get the systemd autopkgtests back to green. Since I already fixed this upstream, it is easy to backport, so it's worth making the incremental improvement for now. [1] https://github.com/systemd/systemd/commit/70aece819311f7ab76abdf473bc8f316c5bc58c6 ** Affects: systemd (Ubuntu) Importance: Undecided Assignee: Nick Rosbrook (enr0n) Status: Fix Committed ** Affects: systemd (Ubuntu Noble) Importance: Medium Assignee: Nick Rosbrook (enr0n) Status: Triaged ** Tags: systemd-sru-next ** Also affects: systemd (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Committed ** Changed in: systemd (Ubuntu Noble) Status: New => Triaged ** Changed in: systemd (Ubuntu Noble) Assignee: (unassigned) => Nick Rosbrook (enr0n) ** Changed in: systemd (Ubuntu Noble) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065964 Title: test-execute fails because of apparmor unprivileged userns restrictions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2065964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2035122] Re: Under ubuntu core/core-desktop, /etc/default/locale is not modifiable
** Tags removed: systemd-sru-next -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2035122 Title: Under ubuntu core/core-desktop, /etc/default/locale is not modifiable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064096] Re: Services fail to start in noble deployed with TPM+FDE
** Also affects: apparmor (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: rsyslog (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: cups (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: sssd (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Noble) Importance: Undecided => High ** Changed in: systemd (Ubuntu Noble) Assignee: (unassigned) => Nick Rosbrook (enr0n) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064096 Title: Services fail to start in noble deployed with TPM+FDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2064096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054761] Re: gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients'
I believe I figured out what is happening here. In systemd v250, systemd user managers began interpreting the signal RTMIN+25 as a command to daemon-reexec. This was done so that: systemctl kill --kill-whom='main' --signal='SIGRTMIN+25' 'user@*.service' could be used as a way to reexec all user instances at once. So, systemd.postinst now contains such a line so that user managers are also reexec'd during package upgrades. However, since Jammy is running systemd v249, the running user manager at the time of the upgrade does not have this reexec logic, and appears to behave as if it were killed normally. So, the fix should be to not attempt to restart all the user managers if the old version is too old. ** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) ** Changed in: systemd (Ubuntu) Status: New => Triaged ** Tags added: systemd-sru-next -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054761 Title: gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland- allow-byte-swapped-clients' To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061891] Re: Noble upgrade breaks iptables-persistent and netfilter-persistent usage
I re-confirmed the fix using the upgrader tarball for noble-proposed: I have verified using the upgrader tarball for noble-proposed: root@j:~# wget http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz --2024-05-16 13:41:34-- http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz Resolving archive.ubuntu.com (archive.ubuntu.com)... 91.189.91.82, 185.125.190.39, 91.189.91.81, ... Connecting to archive.ubuntu.com (archive.ubuntu.com)|91.189.91.82|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 1274850 (1.2M) [application/x-gzip] Saving to: ‘noble.tar.gz’ noble.tar.gz 100%[>] 1.21M 1.50MB/sin 0.8s 2024-05-16 13:41:35 (1.50 MB/s) - ‘noble.tar.gz’ saved [1274850/1274850] root@j:~# tar xf noble.tar.gz root@j:~# apt install netfilter-persistent iptables-persistent -y Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: iptables-persistent netfilter-persistent 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 13.9 kB of archives. After this operation, 93.2 kB of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu jammy/universe amd64 netfilter-persistent all 1.0.16 [7440 B] Get:2 http://archive.ubuntu.com/ubuntu jammy/universe amd64 iptables-persistent all 1.0.16 [6488 B] Fetched 13.9 kB in 1s (17.8 kB/s) Preconfiguring packages ... Selecting previously unselected package netfilter-persistent. (Reading database ... 33926 files and directories currently installed.) Preparing to unpack .../netfilter-persistent_1.0.16_all.deb ... Unpacking netfilter-persistent (1.0.16) ... Selecting previously unselected package iptables-persistent. Preparing to unpack .../iptables-persistent_1.0.16_all.deb ... Unpacking iptables-persistent (1.0.16) ... Setting up netfilter-persistent (1.0.16) ... Created symlink /etc/systemd/system/multi-user.target.wants/netfilter-persistent.service → /lib/systemd/system/netfilte r-persistent.service. Setting up iptables-persistent (1.0.16) ... update-alternatives: using /lib/systemd/system/netfilter-persistent.service to provide /lib/systemd/system/iptables.ser vice (iptables.service) in auto mode Processing triggers for man-db (2.10.2-1) ... Scanning processes... No services need to be restarted. No containers need to be restarted. No user sessions are running outdated binaries. No VM guests are running outdated hypervisor (qemu) binaries on this host. root@j:~# apt policy ufw iptables-persistent netfilter-persistent ufw: Installed: 0.36.1-4ubuntu0.1 Candidate: 0.36.1-4ubuntu0.1 Version table: *** 0.36.1-4ubuntu0.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.36.1-4build1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages iptables-persistent: Installed: 1.0.16 Candidate: 1.0.16 Version table: *** 1.0.16 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status netfilter-persistent: Installed: 1.0.16 Candidate: 1.0.16 Version table: *** 1.0.16 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status root@j:~# ./noble --frontend DistUpgradeViewNonInteractive [ ... upgrading ... ] root@j:~# apt policy ufw iptables-persistent netfilter-persistent ufw: Installed: (none) Candidate: 0.36.2-6 Version table: 0.36.2-6 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages 0.36.1-4ubuntu0.1 -1 100 /var/lib/dpkg/status iptables-persistent: Installed: 1.0.20 Candidate: 1.0.20 Version table: *** 1.0.20 500 500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages 100 /var/lib/dpkg/status netfilter-persistent: Installed: 1.0.20 Candidate: 1.0.20 Version table: *** 1.0.20 500 500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages 100 /var/lib/dpkg/status ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061891 Title: Noble upgrade breaks iptables-persistent and netfilter-persistent usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2061891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063464] Re: systemd-resolved wasn't installed on upgrade from Jammy to Noble
As the test plan mentions, there is no known reproducer for this at the moment. The best I can do is confirm that the PostUpgradeInstall=systemd-resolved setting is present for upgrades from Jammy: nr@six:/t/tmp.U3JgXkB0Vr$ wget http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz --2024-05-16 15:37:48-- http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz Resolving archive.ubuntu.com (archive.ubuntu.com)... 91.189.91.83, 91.189.91.82, 91.189.91.81, ... Connecting to archive.ubuntu.com (archive.ubuntu.com)|91.189.91.83|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 1274850 (1.2M) [application/x-gzip] Saving to: ‘noble.tar.gz’ noble.tar.gz 100%[>] 1.21M 984KB/sin 1.3s 2024-05-16 15:37:50 (984 KB/s) - ‘noble.tar.gz’ saved [1274850/1274850] nr@six:/t/tmp.U3JgXkB0Vr$ tar xf noble.tar.gz nr@six:/t/tmp.U3JgXkB0Vr$ grep systemd-resolved DistUpgrade.cfg.jammy PostUpgradeInstall=systemd-resolved ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063464 Title: systemd-resolved wasn't installed on upgrade from Jammy to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2063464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064090] Re: Automatically installed bit not transitioned to t64 libraries
I have verified using the upgrader tarball in noble-proposed:
root@m:~# wget
http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz
--2024-05-16 12:44:06--
http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz
Resolving archive.ubuntu.com (archive.ubuntu.com)... 91.189.91.81,
185.125.190.39, 91.189.91.83, ...
Connecting to archive.ubuntu.com (archive.ubuntu.com)|91.189.91.81|:80...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 1274850 (1.2M) [application/x-gzip]
Saving to: ‘noble.tar.gz’
noble.tar.gz
100%[>] 1.21M
1.51MB/sin 0.8s
2024-05-16 12:44:07 (1.51 MB/s) - ‘noble.tar.gz’ saved [1274850/1274850]
root@m:~# tar xvf noble.tar.gz
root@m:~# apt-mark showmanual > manual.before
root@m:~# ./noble
[ ... upgrading ... ]
root@m:~# apt-mark showmanual > manual.after
root@m:~# diff -u manual.{before,after}
--- manual.before 2024-05-16 12:46:58.802671205 +
+++ manual.after2024-05-16 13:00:59.391160334 +
@@ -12,6 +12,7 @@
init
isc-dhcp-client
isc-dhcp-common
+libc6
libeatmydata1
libwrap0
linux-base
root@m:~#
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064090
Title:
Automatically installed bit not transitioned to t64 libraries
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2064090/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059359] Re: autopkgtests fail, maybe due to python-typing-extensions, maybe only on armhf
** Changed in: pydantic (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059359 Title: autopkgtests fail, maybe due to python-typing-extensions, maybe only on armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pydantic/+bug/2059359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065663] [NEW] proposed-migration for android-platform-frameworks-native 1:10.0.0+r36-1.2build1
Public bug reported: android-platform-frameworks-native 1:10.0.0+r36-1.2build1 is stuck in -proposed. It's autopkgtest is failing with: 145s autopkgtest [21:34:07]: test command1: ls -l /usr/include/android/android/*.h /usr/lib/*/android/libETC1.so 145s autopkgtest [21:34:07]: test command1: [--- 145s ls: cannot access '/usr/include/android/android/*.h': No such file or directory 145s lrwxrwxrwx 1 root root 12 Mar 31 17:38 /usr/lib/aarch64-linux-gnu/android/libETC1.so -> libETC1.so.0 145s autopkgtest [21:34:07]: test command1: ---] 146s command1 FAIL non-zero exit status 2 146s autopkgtest [21:34:08]: test command1: - - - - - - - - - - results - - - - - - - - - - 146s autopkgtest [21:34:08]: test command1: - - - - - - - - - - stderr - - - - - - - - - - 146s ls: cannot access '/usr/include/android/android/*.h': No such file or directory 147s autopkgtest [21:34:09]: summary 147s command1 FAIL non-zero exit status 2 ** Affects: android-platform-frameworks-native (Ubuntu) Importance: Low Assignee: Nick Rosbrook (enr0n) Status: In Progress ** Tags: update-excuse ** Changed in: android-platform-frameworks-native (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) ** Description changed: android-platform-frameworks-native 1:10.0.0+r36-1.2build1 is stuck in - -proposed. + -proposed. It's autopkgtest is failing with: + + 145s autopkgtest [21:34:07]: test command1: ls -l /usr/include/android/android/*.h /usr/lib/*/android/libETC1.so + 145s autopkgtest [21:34:07]: test command1: [--- + 145s ls: cannot access '/usr/include/android/android/*.h': No such file or directory + 145s lrwxrwxrwx 1 root root 12 Mar 31 17:38 /usr/lib/aarch64-linux-gnu/android/libETC1.so -> libETC1.so.0 + 145s autopkgtest [21:34:07]: test command1: ---] + 146s command1 FAIL non-zero exit status 2 + 146s autopkgtest [21:34:08]: test command1: - - - - - - - - - - results - - - - - - - - - - + 146s autopkgtest [21:34:08]: test command1: - - - - - - - - - - stderr - - - - - - - - - - + 146s ls: cannot access '/usr/include/android/android/*.h': No such file or directory + 147s autopkgtest [21:34:09]: summary + 147s command1 FAIL non-zero exit status 2 ** Changed in: android-platform-frameworks-native (Ubuntu) Importance: Undecided => Low ** Changed in: android-platform-frameworks-native (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065663 Title: proposed-migration for android-platform-frameworks-native 1:10.0.0+r36-1.2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-platform-frameworks-native/+bug/2065663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065439] Re: default globbed sysctls override linux defaults
These are just defaults. You can override anything you like by specifying your own values in e.g. /etc/sysctl.d/60-my-overrides.conf. See "Configuration Directories and Precedence" in https://www.freedesktop.org/software/systemd/man/latest/sysctl.d.html for more details. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065439 Title: default globbed sysctls override linux defaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2065439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065229] Re: Upgrades to 24.04 LTS should be temporarily prevented for TPM FDE systems
** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Fix Committed ** Changed in: ubuntu-release-upgrader (Ubuntu Noble) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065229 Title: Upgrades to 24.04 LTS should be temporarily prevented for TPM FDE systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2065229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065051] Re: [SRU] Migrate Pi users to KMS
** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: ubuntu-release-upgrader (Ubuntu Noble) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065051 Title: [SRU] Migrate Pi users to KMS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2065051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065229] Re: Upgrades to 24.04 LTS should be temporarily prevented for TPM FDE systems
** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065229 Title: Upgrades to 24.04 LTS should be temporarily prevented for TPM FDE systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2065229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065229] Re: Upgrades to 24.04 LTS should be temporarily prevented for TPM FDE systems
** Description changed: [Impact] - TODO + It is not currently supported to upgrade desktop systems installed with TPM-backed FDE, so we should not allow such upgrades to start. We should notify the user of this and abort the upgrade. [Test Plan] - TODO + + Attempt an upgrade from 23.10 to 24.04 LTS on various types of Ubuntu + installs: + + 1. Desktop with TPM FDE + 2. Desktop classic + 3. LXD Container + + In case (1), the upgrade should be aborted with an appropriate message + to the user. In cases (2) and (3), the upgrade should proceed as + normally. [Where problems could occur] - TODO + The test condition for determining that we are on Desktop with TPM FDE is checking that (a) pc-kernel snap is installed, and (b) ubuntu-desktop-minimal is installed. If the test condition is inadequate in some way, we would see bug reports about upgrades being blocked unnecessarily, or possibly users being allowed to upgrade despite running TPM FDE. + + As always with these kinds of quirks, if any package or snap names were + spelled incorrectly, the quirk would not work correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065229 Title: Upgrades to 24.04 LTS should be temporarily prevented for TPM FDE systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2065229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
