** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2080257
Title:
[WSL] systemd fails to upgrade on WSL1
Public bug reported:
E.g.: https://autopkgtest.ubuntu.com/results/autopkgtest-
oracular/oracular/amd64/s/systemd/20241003_175213_c04ab@/log.gz
Debian already skips this test due to https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1075733. Let's do the same for Ubuntu.
** Affects: systemd (Ubun
Public bug reported:
During an archive rebuild, rsyslog FTBFS on s390x only:
https://launchpadlibrarian.net/751879056/buildlog_ubuntu-
oracular-s390x.rsyslog_8.2406.0-1ubuntu2_BUILDING.txt.gz
The build fails due to two tests:
FAIL: gzipwr_flushInterval
==
testbench: TZ e
** Changed in: openssh (Ubuntu Noble)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2069041
Title:
Changing Port in sshd_config requ
** Changed in: openssh (Ubuntu Noble)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2076023
Title:
Failed to apply 'Match' directive
** Changed in: openssh (Ubuntu Noble)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2080216
Title:
sshd cannot bind to IPv4 interfaces
** Changed in: openssh (Ubuntu Noble)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2071815
Title:
Investigate ASLR re-randomization bei
** Description changed:
[Impact]
When users have a Match section in their sshd config, their
configuration cannot be parsed by the sshd-socket-generator (because
there is no connection, hence no connection spec to be matched), and the
generator fails. This means no custom config is ap
** Description changed:
+ [Impact]
+
The systemd-socket-activation.patch patch has an Ubuntu delta to fix bug
2011458, but this results in ASLR not being re-randomized for children
because the patch delta does "rexec_flag = 0;".
This was discovered as part of the CVE-2024-6387 discover
** Changed in: openssh (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2080216
Title:
sshd cannot bind to IPv4 interfaces
** Description changed:
+ [Impact]
+
+ The default listening sockets for sshd are different depending on
+ whether socket activation is used or not, even when /etc/ssh/sshd_config
+ is the default. E.g.:
+
+ # Socket-activated
+
+ root@n2:~# systemctl status ssh.socket
+ ● ssh.socket - OpenBSD
** Description changed:
+ [Impact]
+
+ When users have a Match section in their sshd config, their
+ configuration cannot be parsed by the sshd-socket-generator (because
+ there is no connection, hence no connection spec to be matched), and the
+ generator fails. This means no custom config is ap
** Changed in: openssh (Ubuntu)
Status: Confirmed => Triaged
** Also affects: openssh (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https:
Okay, I am not sure why the ipv6 socket is not accepting ipv4, because
AFAICT (and when I test on my machine) the way IPV6_V6ONLY is being set
in the default case, it should allow ipv4.
However, I do think there is a case to be made about the socket unit
being more aligned with the contents of /et
** Also affects: openssh (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: openssh (Ubuntu Noble)
Importance: Undecided => Medium
** Tags removed: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: openssh (Ubuntu Noble)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2069041
Title:
Changing Port in sshd_config requ
Ah sorry, I missed that. Can you please do the following then:
1. Enable debug logs on systemd-networkd-wait-online.service:
$ mkdir -p /etc/systemd/system/systemd-networkd-wait-online.d/
$ cat > /etc/systemd/system/systemd-networkd-wait-online.d/debug.conf << EOF
[Service]
Environment=SYSTEMD_LO
It looks like bind9 (named.service) is able to bind to the address just
fine after systemd-networkd reports the address is configured. Is named
maybe not setting SO_REUSEADDR/SO_REUSEPORT or something? Or (as an
experiment) does disabling named.service allow the others to start?
** Changed in: sys
*** This bug is a duplicate of bug 2054761 ***
https://bugs.launchpad.net/bugs/2054761
@mchelen Please open a new bug report by running `ubuntu-bug ubuntu-
release-upgrader-core` on the affected system. This will attach the
necessary logs to investigate your upgrade issue.
--
You received th
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
** Changed in: systemd (Ubuntu Noble)
Status: New => Triaged
** Changed in: systemd (Ubuntu Noble)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Changed in: systemd (Ubuntu Noble)
Importance:
I'm sorry to hear about your upgrade troubles. If you have logs from the
the boot where the upgrade occurred, please open a different bug with
those logs so that the root cause for the hang can be investigated.
But, if you unplugged your machine during the upgrade because it was
unresponsive, I am
It appears to be a known issue that WSL1 does not support F_OFD_SETLKW,
which is what systemd is using here. I could add a fallback to use
F_SETLKW instead, but according to [1], it sounds like the locking is
just broken on WSL1? So the "fallback" would probably lead to even more
issues.
Do you ge
Re-adding a Linux task to see if anyone can confirm whether kernel
interface naming was changed between these two kernel versions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/b
By default, the NamePolicy=[1] (as configured in
/usr/lib/systemd/network/99-default.link) is:
[Link]
NamePolicy=keep kernel database onboard slot path
This means that if the kernel claims to assign a predictable name, then
that will take precedence over other policies, including the "onboard"
po
This error is coming from systemd-sysusers in systemd.postinst. To
isolate the failing call, can you share the output of:
$ SYSTEMD_LOG_LEVEL=debug systemd-sysusers basic.conf systemd-
journal.conf systemd-network.conf
Looking at the code, this is either failing on an open() or flock(), so
likely
I am tracking this for future SRUs, so unsubscribing sponsors.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/209
Title:
PTP device symlink missing after running udeva
To be specific, the override I would suggest is:
$ mkdir -p /etc/tmpfiles.d
$ cat > /etc/tmpfiles.d/tmp.conf << EOF
D /tmp 1777 root root 10d
q /var/tmp 1777 root root 30d
EOF
In particular, this is flipping the 'q' to a 'D' for the /tmp line.
--
You received this bug notification because you a
This is expected behavior.
Since /tmp is a tmpfs by default, the default
/usr/lib/tmpfiles.d/tmp.conf is configured with a 10d cleanup age for
/tmp, but it is *not* configured to clean /tmp at boot, because that is
unnecessary for a tmpfs.
If you want to clean /tmp at boot *and* have your tmp.mou
** Tags added: foundations-todo
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2080
Are you able to run unprivileged containers instead? That would be the
suggested configuration from upstream LXD.
There are many things that do not work with systemd in privileged LXD
containers due to AppArmor etc. Upstream systemd does not like adding
workarounds for issues caused by AppArmor ru
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
** Changed in: systemd (Ubuntu Focal)
Status: In Progress => Triaged
** Changed in: systemd (Ubuntu Jammy)
Status: In Progress => Triaged
** Changed in: systemd (Ubuntu Noble)
Status: In Progress => Triaged
** Changed in: systemd (Ubuntu Focal)
Importance: Undecided => Lo
systemd-binfmt should just exit when /proc/sys/fs/binfmt_misc is not
mounted rw, which I thought was usually the case in LXD containers.
Are you running a privileged or unprivileged container?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
** Changed in: systemd (Ubuntu)
Imp
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
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2051407
Title:
qemu-net autopkgtest fails: Failed to s
Is sshd not accessible at all over ipv4? How did you notice that sshd
was not listening on ipv4?
In the default case, we should end up with ssh.socket listening on
[::]:22, but with IPV6_V6ONLY=0 so that sshd is still accessible over
ipv4.
> Setting net.ipv6.bindv6only=0 also helps, but that's no
Public bug reported:
E.g. https://autopkgtest.ubuntu.com/results/autopkgtest-
oracular/oracular/s390x/i/initramfs-tools/20240909_091354_592dd@/log.gz
1489s autopkgtest [09:13:45]: summary
1489s qemu-ata-onlySKIP Test lists explicitly supported architectures,
but the
This patch is in v256.5, which I prepared and uploaded today.
** Changed in: systemd (Ubuntu Oracular)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bug
** Tags added: systemd-sru-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/209
Title:
PTP device symlink missing after running udevadm trigger command
Status in s
*** This bug is a duplicate of bug 2078555 ***
https://bugs.launchpad.net/bugs/2078555
Thanks for your bug report. As you noted, this is the same issue as bug
2078555 so I am marking this as a duplicate to consolidate.
** This bug has been marked a duplicate of bug 2078555
Upgrading from 2
I am planning an SRU for noble in the next couple weeks.
** Tags removed: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2076023
Title:
Failed to apply '
** Changed in: openssh (Ubuntu Oracular)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2076023
Title:
Failed to apply 'Match' dire
ged in: openssh (Ubuntu Noble)
Status: New => Triaged
** Changed in: openssh (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: openssh (Ubuntu Noble)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug notification because you are a memb
@corradoventu - the output you shared demonstrates that you are *not*
seeing this issue on 24.10.
@sunneyxue- likewise, your output demonstrates that the issue is fixed
on this system.
Note that it is possible at the time when you run `apt update`, that a
daemon-reload actually is needed, and the
The non-linux autopkgtest regressions were resolved with test
retries/baseline tests. As previously stated, the linux-* tests should
be ignored as they are denylisted. With, I believe the update could be
released.
--
You received this bug notification because you are a member of Ubuntu
Touch seed
@sunneyxue, can you share the output of the following?
$ apt policy systemd
$ sudo systemctl daemon-reload
$ sudo systemctl enable somethingthatdefinitelydoesnotexist.service
$ sudo apt update
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which i
I checked that the build flags for systemd on s390x and ppc64el in
noble-proposed look correct:
https://launchpadlibrarian.net/743007715/buildlog_ubuntu-noble-ppc64el.systemd_255.4-1ubuntu8.4_BUILDING.txt.gz
https://launchpadlibrarian.net/743006792/buildlog_ubuntu-noble-s390x.systemd_255.4-1ubuntu
@corradoventu, can you provide some evidence of that? I cannot reproduce
this on 24.10.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2055239
Title:
Warning: The unit fil
*** This bug is a duplicate of bug 2076882 ***
https://bugs.launchpad.net/bugs/2076882
** This bug has been marked a duplicate of bug 2076882
package systemd-resolved 255.4-1ubuntu8.2 failed to install/upgrade:
installed systemd package pre-removal script subprocess returned error exit
st
According to the DpkgTerminalLog.txt, your system is not /usr-merged:
**
*
* The systemd package cannot be installed because this system does
* not have a merged /usr.
*
* Please install the usrmerge package to convert th
As can be seen here, it's skipped because ConditionFirstBoot=yes fails
(i.e. the boot does not meat the "first boot semantics[1][2]).
Essentially, this is determined by /etc/machine-id.
I *believe* on Ubuntu, our images are configured with an empty
/etc/machine-id, so as defined by [2], a "first b
The new upload is just a no-change rebuild for new build flags, so my
previous verification stands.
** 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
Tou
I dug into this a bit more, and it seems this issue occurs specifically
for the user `ubuntu`. Before the upgrade, I copied the contents of
/etc/shadow, and compared them to /etc/shadow after the first reboot
after the upgrade.
$ diff -u <(/etc/shadow) /home/ubuntu/before/shadow
--- /dev/fd/63 20
I have verified the fix using systemd 255.4-1ubuntu3.3 from noble-
proposed.
In a new container, I can see the issue at first:
nr@six:~$ lxc launch ubuntu:noble lp2055239
Launching lp2055239
nr@six:~$ lxc exec lp2055239 bash
root@lp2055239:~# systemctl enable somethingthatdefinitelydoesnotexist.s
** Changed in: procps (Ubuntu Oracular)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/2003027
Title:
fq_codel qdisc compiled bu
** Changed in: systemd (Ubuntu Noble)
Status: Triaged => In Progress
** Changed in: systemd (Ubuntu Noble)
Milestone: None => ubuntu-24.04.1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https:
** Description changed:
+ [Impact]
+
+ systemd may incorrectly mark units as needing a daemon reload, therefore
+ unnecessarily printing the warning that a daemon-reload is needed for
+ the changes to take effect. This is misleading to users, and
+ particularly visible in cases like running apt u
** Changed in: systemd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2067907
Title:
systemd tools fail to mount disk
We currently have:
```
Include /etc/ssh/sshd_config.d/*.conf
# When systemd socket activation is used (the default), the socket
# configuration must be re-generated after changing Port, AddressFamily, or
# ListenAddress.
#
# For changes to take effect, run:
#
# systemctl daemon-reload
# syste
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2073356
Title:
Choose password for new keyring the first time
This does not sound like a systemd bug, but more like kernel or the
nouveau driver. From the attached CurrentDmesg.txt:
[ 248.207134] nouveau :01:00.0: Enabling HDA controller
[ 248.310486] [ cut here ]
[ 248.310488] WARNING: CPU: 0 PID: 1530 at kernel/workqueue.c:17
penssh (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2076023
Title:
Failed
No it was not.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/2075968
Title:
cannot login after upgrade from xubuntu 22.04 to 24.04
Status in pam package in Ubuntu:
New
Sta
** Changed in: systemd (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2075104
Title:
user session is randomly terminated by syste
This issue can be seen with any actual unit after e.g. enabling or
disabling a non-existent unit. For example,
root@n:~# systemctl status ssh.socket
● ssh.socket - OpenBSD Secure Shell server socket
Loaded: loaded (/usr/lib/systemd/system/ssh.socket; enabled; preset:
enabled)
Active: ac
)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
** Changed in: systemd (Ubuntu Noble)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Changed in: systemd (Ubuntu Noble)
Status: New => Triaged
** Changed i
** Changed in: systemd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2065964
Title:
test-execute fails because of ap
** Changed in: systemd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2067922
Title:
on WSL systemd status fails outp
Public bug reported:
After performing an upgrade, and then rebooting, I am no longer able to
login with my user "ubuntu". I get an authentication failure with both
the graphical login screen, and when attempting to login on a non-
graphical tty.
Dropping to a rescue shell, I can see this in the l
stemd sd_listen_fds() code, as refactored by Colin
Watson.
- d/control: Remove dependencies on libsystemd-dev | libelogind-dev
- d/rules: Drop --with-systemd flag (new options are used by default)
[ Nick Rosbrook ]
* debian/patches: only set PAM_RHOST if remote host i
isten_fds() code, as refactored by Colin
Watson.
- d/control: Remove dependencies on libsystemd-dev | libelogind-dev
- d/rules: Drop --with-systemd flag (new options are used by default)
[ Nick Rosbrook ]
* debian/patches: only set PAM_RHOST if remote host is not '
Can you share the journal output that you're describing? And, can you
share the output of the following commands?
$ oomctl
$ systemd-analyze cat-config systemd/oomd.conf
$ systemctl cat -- '-.slice'
$ systemctl cat -- user@$(id -u).service
** Changed in: systemd (Ubuntu)
Status: New => Inc
I have context for most of the delta here, so I will take this merge.
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubu
** Changed in: openssh (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2071815
Title:
Investigate ASLR re-randomization
Yeah, you need an entry enabling noble-updates for universe.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/b
** Tags added: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2055239
Title:
Warning: The unit file, source configuration file or drop-ins of {apt-
news,
This sounds like your apt sources are messed up. Do you have noble-
updates enabled for universe?
Can you share the output of:
$ apt policy systemd-coredump systemd
$ cat /etc/apt/sources.list.d/*
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
** Changed in: systemd (Ubuntu)
I don't think those *help*, but that's good to know for when we merge an
upstream version that includes those patches.
** Changed in: openssh (Ubuntu)
Status: Confirmed => In Progress
** Changed in: openssh (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification
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 many
** Tags removed: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2047975
Title:
package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade:
instal
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 ma
*** 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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchp
*** 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
Touch seeded packages, which is s
** 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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs
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 (Ubun
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2063464
Title:
Package wasn't installed on upgrade from Jammy to Noble
Status in systemd package in Ubuntu:
Incomplete
Sta
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 Ub
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 a
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
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/
*** 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 duplic
*** 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 receiv
** Changed in: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2055012
Title:
When I upgraded from 22.
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 a
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
Touch seeded packages, which is subscribed to systemd in Ubun
** Changed in: systemd (Ubuntu Noble)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2058179
Title:
Kernel 6.8 + zfs-2.2.2: cop
This is probably a hwdb issue. Can you share the output of dmidecode -s
system-product-name? And can you try and figure out what keycode is
issued by the rotation? The evtest command should help with that.
** Also affects: systemd-hwe (Ubuntu)
Importance: Undecided
Status: New
--
You r
itical
** Changed in: systemd (Ubuntu Noble)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Tags removed: systemd-sru-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad
** Tags added: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Status in Nat
Fix for systemd to work around this:
https://github.com/systemd/systemd/pull/32341.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** T
1 - 100 of 1028 matches
Mail list logo
