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,
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:
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.]
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
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
** 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
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
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:
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--
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
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
@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.
*** 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
> 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
** Changed in: nfs-ganesha (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/2065856
Title:
SEGFAULTs in v4.3 with GlusterFS
To manage notifications about
** Changed in: glusterfs (Ubuntu Noble)
Assignee: Nick O'Connor (nick-oconnor) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064843
Title:
Brick SEGFAULTs in 11.1
To man
** 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
signed) => 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 Nob
** 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
** 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
** 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
** 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
** 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
** 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:
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
** 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:
+
+
** 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
rt, 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 (
** 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
)
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)
-
This is ready for review/sponsorship.
** Description changed:
[ Impact ]
* Users experience SEGFAULTs when Ganesha fails to communicate with
Gluster, causing the NFS share to disappear.
* The patch refactors how free_space() is called to avoid the null
pointer deference.
[
This is ready for review/sponsorship
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064843
Title:
Brick SEGFAULTs in 11.1
To manage notifications about this bug go to:
My initial patch missed a line from the original commit (which doesn't
cleanly apply to v4.3). I've fixed the patch and it resolves the issue.
** Summary changed:
- SEGFAULTs in v4.3 with Gluster
+ SEGFAULTs in v4.3 with GlusterFS
--
You received this bug notification because you are a member
** Description changed:
[ Impact ]
* Users experience SEGFAULTs when Ganesha fails to communicate with
Gluster, causing the NFS share to disappear.
* The patch refactors how free_space() is called to avoid the null
- pointer deference, but it doesn't seem to fix the issue on v4.3.
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 (
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--
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
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--
** Description changed:
[ Impact ]
- * Users experience SEGFAULTs when Ganesha fails to communicate with
+ * Users experience SEGFAULTs when Ganesha fails to communicate with
Gluster, causing the NFS share to disappear.
- * The patch refactors how free_space() is called to avoid the
** Patch added: "fix-null-ptr-ref-in-free-space.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nfs-ganesha/+bug/2065856/+attachment/5778939/+files/fix-null-ptr-ref-in-free-space.debdiff
** Patch removed: "fix-sigsev-in-free-space.debdiff"
** Patch added: "fix-stack-overflow-in-inode-destroy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/2064843/+attachment/5778935/+files/fix-stack-overflow-in-inode-destroy.debdiff
** Patch removed: "fix-stack-overflow-in-inode-destroy.debdiff"
** Patch added: "fix-stack-overflow-in-inode-destroy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/2064843/+attachment/5778934/+files/fix-stack-overflow-in-inode-destroy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Patch added: "fix-sigsev-in-free-space.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nfs-ganesha/+bug/2065856/+attachment/5778936/+files/fix-sigsev-in-free-space.debdiff
** Patch removed: "fix-sigsev-in-free-space.debdiff"
Public bug reported:
[ Impact ]
* Users experience SEGFAULTs when Ganesha fails to communicate with
Gluster, causing the NFS share to disappear.
* The patch refactors how free_space() is called to avoid the null
pointer deference.
[ Test Plan ]
* The triggers for the issue are difficult to
** Patch added: "fix-sigsev-in-free-space.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nfs-ganesha/+bug/2065856/+attachment/5778933/+files/fix-sigsev-in-free-space.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- Gluster 11.1 brick SEGFAULT
+ Brick SEGFAULTs in 11.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064843
Title:
Brick SEGFAULTs in 11.1
To manage notifications about this
** 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-typ
ile 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-exc
Thanks for checking, just looking through your output, you have the same
issue as me (just before the Processing.theiggers for man-db) you have
the message 'Could not execute systemctl: at /usr/bin/deb-systemd-invoke
line 148.'
Having dug a bit further, this is because dnsmasq cannot listen on
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
** Changed in: glusterfs (Ubuntu Noble)
Status: Triaged => In Progress
** Changed in: glusterfs (Ubuntu Noble)
Assignee: (unassigned) => Nick O'Connor (nick-oconnor)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[ Impact ]
* Users experience brick SEGFAULTs under certain not-yet-understood
scenarios. Some reports include a high percentage of small file I/O. I
encountered the issue roughly every hour with Minio backed by GlusterFS
on ZFS.
* This bug introduces
** Patch added: "fix-stack-overflow-in-inode-destroy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/2064843/+attachment/5777078/+files/fix-stack-overflow-in-inode-destroy.debdiff
** Patch removed: "fix-stack-overflow-in-inode-destroy.debdiff"
** Patch added: "fix-stack-overflow-in-inode-destroy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/2064843/+attachment/5777077/+files/fix-stack-overflow-in-inode-destroy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** 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.
** 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.
** 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
** 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
** Description changed:
[ Impact ]
- * Users experience brick SEGFAULTs under certain not-yet-understood
+ * Users experience brick SEGFAULTs under certain not-yet-understood
scenarios. Some reports include a high percentage of small file I/O. I
encountered the issue roughly every hour
** Description changed:
- GlusterFS version 11.1 contains a recursion bug
- (https://github.com/gluster/glusterfs/issues/4295) which results in
- bricks SEGFAULTing. The issue was fixed upstream by
- https://github.com/gluster/glusterfs/pull/4302, but the fix has yet to
- be included in a
Public bug reported:
[Impact]
TODO
[Test Plan]
TODO
[Where problems could occur]
TODO
** Affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: ubuntu-release-upgrader (Ubuntu Noble)
Importance: High
Assignee: Nick Rosbrook (enr0n
SGTM. I can drive this. Let me know what needs to be done.
** Description changed:
GlusterFS version 11.1 contains a recursion bug
(https://github.com/gluster/glusterfs/issues/4295) which results in
bricks SEGFAULTing. The issue was fixed upstream by
-
** Changed in: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can you share the contents of your sources.list file? Also, what version
of distro-info-data do you have installed (apt policy distro-info-data)?
The error message suggests to me that that /usr/share/distro-
info/ubuntu.csv is messed up some how.
** Changed in: ubuntu-release-upgrader (Ubuntu)
** Description changed:
GlusterFS version 11.1 contains a recursion bug
(https://github.com/gluster/glusterfs/issues/4295) which results in
bricks SEGFAULTing. The issue was fixed upstream by
https://github.com/gluster/glusterfs/pull/4302, but the fix yet to be
included in a release. I
Yes, I found that systemd switched from using MS_MOVE to MS_BIND |
MS_REC when moving /run (and other filesystems) during the switch root.
Although this is ultimately a shortcoming in AppArmor, this change in
systemd is why we are seeing the issue now.
Discussing with upstream in
dhcpd is provided by isc-dhcp, not systemd.
** Package changed: systemd (Ubuntu) => isc-dhcp (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064804
Title:
waits for minutes for a dhcp
I've recompiled glusterfs locally with the changes. The upstream fix
appears to address the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064843
Title:
Gluster 11.1 brick SEGFAULT
To
Public bug reported:
Using Ubuntu 24.04 I get a 'could not execute error:
sudo apt install dnsmasq
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed
dnsmasq
0 to upgrade, 1 to newly install, 0 to remove
Hi all,
I didn't see a response to the workaround, so just dropping a message.
I had the same issue. Confirming that workaround - configuring my
`/etc/netplan/50-cloud-init.yaml` to match the network interface based
on macaddress (`ip a`), and applying the change (`netplan generate &&
netplan
Public bug reported:
GlusterFS version 11.1 contains a recursion bug
(https://github.com/gluster/glusterfs/issues/4295) which results in
bricks SEGFAULTing. The issue was fixed upstream by
https://github.com/gluster/glusterfs/pull/4302, but the fix yet to be
included in a release. I encountered
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug notification because you are a member of Ub
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
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
This report raises an important question about the defaults and setup
for systemd-resolved. This was first raised in the following post a year
ago: https://lists.ubuntu.com/archives/ubuntu-
devel/2023-March/042499.html but as far as I can see remains unresolved.
This is an important issue for
** Tags removed: foundations-todo
--
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
emd/resolve/resolv.conf.
** Also affects: systemd (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Noble)
Status: New => Triaged
** Changed in: systemd (Ubuntu Noble)
Importance: Undecided => High
** Changed in: systemd (Ubuntu Noble)
A
*** This bug is a duplicate of bug 2047975 ***
https://bugs.launchpad.net/bugs/2047975
Ah, I see. Thanks for that link. The issue is that it is not actually
necessary to make the /etc/resolv.conf ->
/run/systemd/resolve/resolv.conf symlink. systemd-resolved will handle
DNSStubListener=no by
*** This bug is a duplicate of bug 2047975 ***
https://bugs.launchpad.net/bugs/2047975
And, if you still have an affected system in this state, what does
readlink /etc/resolv.conf show?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 2047975 ***
https://bugs.launchpad.net/bugs/2047975
How exactly did you disable the stub resolver?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063533
Title:
** Description changed:
- [Impact]
- ufw and -persistent packages both manage the firewall, hence they conflict
but they accidentally had no conflicts in jammy. If both are installed,
persistent packages will store and restore firewall configuration, so ufw
cannot really be used.
+ [Impact /
*** This bug is a duplicate of bug 1889250 ***
https://bugs.launchpad.net/bugs/1889250
Reviewing the files from your upgrade attempt, you have installed nodejs
from the nodesource PPA. This version of nodejs is greater than the one
in the official archive and is keeping some packages
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: ubuntu-release-upgrader
** Changed in: systemd (Ubuntu)
Status: Incomplete => New
** Changed in: ubuntu-release-upgrader (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/2063464
Sorry for the previous noise, I was on the wrong page. Can you please
run apport-collect -p ubuntu-release-upgrader 2063464 so that upgrade
logs are attached?
** Also affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-release-upgrader
--
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:
Package wasn't installed on upgrade from Jammy to Noble
To manage notifications about this bug go to:
Okay. The title should be changed then -- systemd-coredump on the host
attempts to forward the crash to the container, but finds that systemd-
coredump is not present in the container, so it falls back to keeping it
on the host.
--
You received this bug notification because you are a member of
root@selected-slug:~# machinectl pull-raw
"http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img;
noble
Enqueued transfer job 1. Press C-c to continue download in background.
Pulling
'http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img',
saving
Did you verify that systemd-coredump is installed in the container?
** Changed in: apport (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/2063349
Title:
-release-upgrader (Ubuntu)
Status: Incomplete => Opinion
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Opinion => Confirmed
** Changed in: ubuntu-release-upgrader (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Tags added: foundations-todo
--
You
** Changed in: ubuntu-release-upgrader (Ubuntu Noble)
Status: Fix Released => 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/2061891
Title:
Noble upgrade breaks
*** This bug is a duplicate of bug 2054761 ***
https://bugs.launchpad.net/bugs/2054761
Adding my journal from the crash.
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2055012/+attachment/5769751/+files/journal.txt
--
You
*** This bug is a duplicate of bug 2054761 ***
https://bugs.launchpad.net/bugs/2054761
The problem is that gnome-shell crashes during the upgrade, so packages
including systemd-resolved never finish getting installed. Marking as a
duplicate of bug 2054761.
** This bug has been marked a
** Changed in: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055012
Title:
When I upgraded from 22.04 to 24.04, DNS resolution
I attempted an upgrade from a clean Jammy install to Noble so that I
could gather upgrade logs. I have attached them here.
** Attachment added: "dist-upgrade.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+attachment/5769726/+files/dist-upgrade.tar.gz
** Also
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: ubuntu-release-upgrader
*** This bug is a duplicate of bug 1970018 ***
https://bugs.launchpad.net/bugs/1970018
Reviewing the files from your upgrade attempt, you have installed
packages from the deadsnakes PPA. Some of the packages installed are
newer than those in the official archive, which is keeping some python
*** This bug is a duplicate of bug 1874272 ***
https://bugs.launchpad.net/bugs/1874272
** This bug has been marked a duplicate of bug 1874272
Stage "searching for obsolete software" takes a very long time (30 minutes)
--
You received this bug notification because you are a member of
This seems to be a problem with the mirror:
2024-04-19 09:51:50,487 DEBUG examining: 'deb
http://mirror.amsiohosting.net/archive.ubuntu.com/ focal main restricted'
2024-04-19 09:51:50,489 DEBUG verifySourcesListEntry: deb
http://mirror.amsiohosting.net/archive.ubuntu.com/ jammy main restricted
What version of Ubuntu is this?
** 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.
** Changed in: apt-clone (Ubuntu)
Status: New => 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/2062622
Title:
autopkgtest broken on deb822 only testbeds
To manage
1 - 100 of 9969 matches
Mail list logo
