I am seeing the same crash with systemd 253.5-1ubuntu1 upstream-{1,2}
tests and qemu 1:8.0.2+dfsg-2ubuntu1[1]. However, the systemd
252.5-2ubuntu3 upstream-{1,2} tests pass against the same version of
qemu[2].
[1]
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/s/systemd/20
** Changed in: systemd (Ubuntu Kinetic)
Status: New => Won't Fix
--
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/2028180
Title:
[SRU][Ubuntu 22.04] Duplicate link fo
** Tags added: 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/1977630
Title:
machinectl pull-tar/pull-raw Operation not permitted
Status in systemd packa
** Tags added: 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/2023462
Title:
chromeos_pstore.service started on non chrome platform hardware.
Status in s
** Tags added: 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/2025563
Title:
System can not shutdown if system has multiple VROC RAID arrays
Status in OE
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Lunar)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Jammy)
Status: New => Triaged
** Changed in: systemd (Ubuntu Lunar)
Status: New =>
** Also affects: systemd (Ubuntu Lunar)
Importance: Undecided
Status: 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/2025382
Title:
22.04 DHCPv6 IPv6 broken
** Also affects: systemd (Ubuntu Lunar)
Importance: Undecided
Status: 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/2013543
Title:
systemctl daemon-reexec f
** Also affects: systemd (Ubuntu Lunar)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Lunar)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
http
** Tags added: systemd-sru-next
** Changed in: systemd (Ubuntu Kinetic)
Status: Triaged => Won't Fix
--
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/2023229
Title:
** Bug watch added: github.com/systemd/systemd/issues #28495
https://github.com/systemd/systemd/issues/28495
** Also affects: systemd via
https://github.com/systemd/systemd/issues/28495
Importance: Unknown
Status: Unknown
** Changed in: systemd (Ubuntu)
Status: Confirmed =>
Looking at the test history for systemd
(https://autopkgtest.ubuntu.com/packages/systemd), tests-in-lxd is
passing on all arches for 252.5-2ubuntu3.1 (Lunar), and for
249.11-0ubuntu3.10 (Jammy).
** Tags removed: verification-needed verification-needed-jammy
verification-needed-lunar
** Tags added
The ppc64el build of systemd 252.5-2ubuntu3.1
(https://launchpad.net/ubuntu/+source/systemd/252.5-2ubuntu3.1/+build/26537841
succeeded), with all built-time tests and fuzzers passing.
** Tags removed: verification-needed verification-needed-lunar
** Tags added: verification-done verification-done-
I have verified the fix on Lunar using 252.5-2ubuntu3.1 from lunar-
proposed:
nr@clean-lunar-amd64:~$ apt-cache policy systemd
systemd:
Installed: 252.5-2ubuntu3
Candidate: 252.5-2ubuntu3.1
Version table:
252.5-2ubuntu3.1 500
500 http://archive.ubuntu.com/ubuntu lunar-proposed/m
I have verified the fix on Jammy using systemd 249.11-0ubuntu3.10 from
jammy-proposed:
nr@clean-jammy-amd64:~$ apt-cache policy systemd
systemd:
Installed: 249.11-0ubuntu3.9
Candidate: 249.11-0ubuntu3.10
Version table:
249.11-0ubuntu3.10 500
500 http://archive.ubuntu.com/ubuntu
I have verified the fix using udev 249.11-0ubuntu3.10 from jammy-
proposed:
ubuntu@ubuntu:~$ apt-cache policy udev
udev:
Installed: 249.11-0ubuntu3.10
Candidate: 249.11-0ubuntu3.10
Version table:
*** 249.11-0ubuntu3.10 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd
I have verified the fix on Lunar using systemd 252.5-2ubuntu3.1 from
lunar-proposed:
root@clean-lunar-amd64:/home/nr# apt-cache policy systemd
systemd:
Installed: 252.5-2ubuntu3.1
Candidate: 252.5-2ubuntu3.1
Version table:
*** 252.5-2ubuntu3.1 500
500 http://archive.ubuntu.com/ubunt
I have verified the fix on Jammy using systemd 249.11-0ubuntu3.10 from
jammy-proposed:
root@clean-jammy-amd64:/home/nr# apt-cache policy systemd
systemd:
Installed: 249.11-0ubuntu3.10
Candidate: 249.11-0ubuntu3.10
Version table:
*** 249.11-0ubuntu3.10 500
500 http://archive.ubuntu.c
I have verified the fix on Lunar using udev 252.5-2ubuntu3.1 from lunar-
proposed:
ubuntu@ubuntu:~$ apt-cache policy udev
udev:
Installed: 252.5-2ubuntu3.1
Candidate: 252.5-2ubuntu3.1
Version table:
*** 252.5-2ubuntu3.1 500
500 http://archive.ubuntu.com/ubuntu lunar-proposed/main am
I have verified the fix using systemd 249.11-0ubuntu3.10 from jammy-
proposed:
The VM and test networks are already configured on my system:
nr@six:/t/tmp.jTS3wdPdT3$ virsh list
Id NameState
---
8clean-jammy-amd64 running
nr@six:/t/tmp.j
I have verified the fix using systemd 252.5-2ubuntu3.1 from lunar-
proposed:
The VM and test networks are already configured on my system:
nr@six:/t/tmp.jTS3wdPdT3$ virsh list
Id NameState
---
9clean-lunar-amd64 running
nr@six:/t/tmp.jTS
I have verified the fix using systemd 249.11-0ubuntu3.10 from jammy-
proposed:
1. Verified that boot-and-services is passing on all arches for
249.11-0ubuntu3.10: https://autopkgtest.ubuntu.com/packages/systemd.
2. Manual test:
root@jammy:~# systemd-detect-virt
lxc
root@jammy:~# apt-cache polic
I verified the fix using systemd-container 249.11-0ubuntu3.10 from
jammy-proposed:
nr@clean-jammy-amd64:~$ apt-cache policy systemd-container
systemd-container:
Installed: 249.11-0ubuntu3.10
Candidate: 249.11-0ubuntu3.10
Version table:
*** 249.11-0ubuntu3.10 500
500 http://archive.u
I have verified the fix using systemd-container 249.11-0ubuntu3.10 from
jammy-proposed:
nr@clean-jammy-amd64:~$ apt-cache policy systemd-container
systemd-container:
Installed: 249.11-0ubuntu3.10
Candidate: 249.11-0ubuntu3.10
Version table:
*** 249.11-0ubuntu3.10 500
500 http://arch
** 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 tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/2030684
Title:
tzname[1] empty after tzset() with env TZ="UTC"
This was indeed fixed in v253.6, so let's cherry pick the patch.
https://github.com/systemd/systemd-
stable/commit/f29f0877c5abfd03060838d1812ea6fdff3b0b37
** Changed in: systemd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touc
Can you please elaborate on the issue you are experiencing, and provide
steps for someone else to reproduce the problem?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because
I believe this is the relevant part from test-execute:
1739s exec-dynamicuser-statedir.service: About to execute: /usr/bin/sh -x -c
'test $$(find / \( -path /var/tmp -o -path /tmp -o -path /proc -o -path
/dev/mqueue -o -path /dev/shm -o -path /sys/fs/bpf -o -path /dev/.lxc \) -prune
-o -type d
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
--
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/2034068
Title:
Ubuntu 22.04.3 linux 6.2 fails to autodetect nvidia ad
The deprecation of systemd-udev-settle.service has been in place since
at least v243[1], and upstream OpenZFS has been tracking this for a few
years[2].
I don't think anything should change in systemd WRT the deprecation
notice.
[1]
https://github.com/systemd/systemd/commit/1662732768d4846805bb0
The support for deb822 in software-properties is actively being
developed.
** Changed in: software-properties (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Changed in: systemd (Ubuntu)
Status: Confirmed => 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/2030505
Title:
on ubuntu 22.04 systemd fails with per interf
> All I am asking is to add the patch/fix to the latest LTS ubuntu
version.
In order to be able to help with that and prioritize this, we need to
know exactly what your trouble is and how to reproduce it.
> For the exact problem statement and steps to reproduce plz use this
ticket https://github.
We are well past feature freeze for Mantic
(https://wiki.ubuntu.com/ManticMinotaur/ReleaseSchedule). We will have
v254 (or potentially v255) for 24.04.
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch s
This looks like a user/privileges issue:
Setting up systemd-oomd (249.11-0ubuntu3.9) ...
Your account has expired; please contact your system administrator.
chfn: PAM: Authentication failure
adduser: `/bin/chfn -f systemd Userspace OOM Killer systemd-oom' returned error
code 1. Exiting.
[1mdpkg:
We should really address the root of this problem instead of continuing
to patch src:systemd.
--
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/2035122
Title:
Under ubuntu co
** Changed in: systemd (Ubuntu)
Status: Triaged => 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/2033325
Title:
systemd fails to set unit as inactive
We will definitely need to fix this in Jammy, but I am not sure it makes
sense to do so in Mantic given the state of x11 keymap support (see bug
2030788).
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Jammy)
Importance: Undec
Okay, so looking again at the diff from 249.11-0ubuntu3.9 to
249.11-0ubuntu3.10[1], the only udev change is a new symlink for nvme
devices. It seems very unlikely that this is related. The only other
change that would be suspicious to me is the systemd.postinst change,
i.e. requesting a reboot for
: systemd (Ubuntu)
Importance: High
Assignee: Nick Rosbrook (enr0n)
Status: New
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug notification becau
The Europe/Kiev symlink is now in tzdata-legacy, so we can just depend
on that for these autopkgtests.
** Changed in: systemd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in U
If you are using NetworkManager, then systemd-networkd.service (and
associated units like systemd-networkd-wait-online.service) should NOT
be enabled. With the caveat that I am not sure why you have systemd-
networkd enabled in the first place, I would recommend that you simply
disable it:
$ syste
the wwan device), then I recommend that you simply
disable systemd-networkd:
$ systemctl disable --now systemd-networkd.service
This will also disable associated units such as systemd-networkd-wait-
online.target.
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Nick Rosbr
Thanks for your report. We have seen a similar report in bug 2036358.
Before I mark it as duplicate, can you please provide output from the
following commands:
$ networkctl
$ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10
** Changed in: systemd (Ubuntu)
Importan
*** This bug is a duplicate of bug 2036358 ***
https://bugs.launchpad.net/bugs/2036358
Thanks for the additional information. I am going to mark this bug as a
duplicate to consolidate.
** This bug has been marked a duplicate of bug 2036358
systemd wait-online now times out after jammy and
ee: (unassigned) => Nick Rosbrook (enr0n)
** Changed in: systemd (Ubuntu Lunar)
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.ne
I will work on re-instating the previous patch in some fashion to fix
this bug without regressing 1982218.
--
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/2036358
Title:
sy
** Description changed:
+ [Impact]
+
+ When all interfaces "not required for online", e.g. when they are marked
+ "optional: true" in netplan, systemd-networkd-wait-online will timeout.
+ Or, in other words, systemd-networkd-wait-online will timeout even
+ though all interfaces are ignored, hence
** Changed in: systemd (Ubuntu)
Status: Triaged => 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/2035778
Title:
upstream autopkgtests fail to build t
** Description changed:
[Impact]
- When all interfaces "not required for online", e.g. when they are marked
- "optional: true" in netplan, systemd-networkd-wait-online will timeout.
- Or, in other words, systemd-networkd-wait-online will timeout even
- though all interfaces are ignored, hence
This behavior is not present in Mantic, so nothing to do there. I have
staged fixes for Jammy and Lunar.
** Changed in: systemd (Ubuntu Jammy)
Status: Triaged => In Progress
** Changed in: systemd (Ubuntu Lunar)
Status: Triaged => In Progress
** Changed in: systemd (Ubuntu)
Robert - are you on on desktop or server? If the links are not managed
by systemd-networkd, it seems like you would be running NetworkManager?
What does this show for you?
$ systemctl status systemd-networkd
$ systemctl status NetworkManager
--
You received this bug notification because you are
Tais - you should not have both services running. For you the solution
should be:
$ systemctl disable --now systemd-networkd.service
This will also disable associated units, including systemd-networkd-
wait-online.service.
** Description changed:
+ [NOTE]
+
+ If you are running a desktop syste
** Description changed:
[NOTE]
If you are running a desktop system and you see this issue, you should
run:
$ systemctl disable --now systemd-networkd.service
This will disable systemd-networkd and associated units, including
systemd-networkd-wait-online.service. NetworkManager
I have verified the fix using systemd 252.5-2ubuntu3.2 in lunar-
proposed:
Creating a fresh container:
nr@six:~$ lxc launch ubuntu-daily:lunar lunar
Creating lunar
Starting lunar
nr@six:~$ lxc exec lunar bash
In the container, after enabling -proposed:
root@lunar
I have verified the fix using systemd 249.11-0ubuntu3.11 from jammy-
proposed:
Creating a fresh container:
nr@six:~$ lxc launch ubuntu-daily:jammy jammy
Creating jammy
Starting jammy
nr@six:~$ lxc exec jammy bash
Within the container, after enabling -proposed:
root
** Description changed:
[NOTE]
If you are running a desktop system and you see this issue, you should
run:
$ systemctl disable --now systemd-networkd.service
This will disable systemd-networkd and associated units, including
systemd-networkd-wait-online.service. NetworkManager
*** This bug is a duplicate of bug 2036358 ***
https://bugs.launchpad.net/bugs/2036358
** This bug has been marked a duplicate of bug 2036358
systemd wait-online now times out after jammy and lunar upgrade
--
You received this bug notification because you are a member of Ubuntu
Touch seed
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Focal)
Importance: Undecided => High
** Changed in: systemd (Ubuntu Jammy)
Importance: Unde
** Tags added: foundations-todo
** Changed in: systemd (Ubuntu Focal)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Changed in: systemd (Ubuntu Jammy)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug notification because you are a member of Ubuntu
Is this affecting your system in any way? Or are you just reporting the
fact that a message is logged?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member
The issue is that those flags are pretty new, so v253 does not make use
of them. Current upstream systemd will try to use them if available[1].
Since this is just a warning from the kernel[2], and since we are late
in the Mantic cycle, I do not think there is justification to fix this
in systemd.
For the near term, I am working on adapting Gunnar's existing work in a
way that we restore the font on the next boot after the upgrade.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launc
** Merge proposal linked:
https://code.launchpad.net/~enr0n/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/452304
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.n
This is a result of us moving PPA sources to deb822 for this cycle. As a
workaround, please use this syntax instead:
$ apt-add-repository ppa:nrbrtx/vte
This is really much nicer than specifying the whole deb line anyways. I
think we should just remove support for the "add by line" syntax since
i
I have uploaded the fix. I am adding block-proposed so that I can do
another test, i.e. do-release-upgrade -d -p, just because the manual way
of testing differs slightly.
** Changed in: ubuntu-release-upgrader (Ubuntu Mantic)
Status: In Progress => Fix Committed
** Tags added: block-propos
I believe the remaining autopkgtest failures are unrelated.
For lunar[1], we have ubuntu-drivers-common failing on ppc64el[2]. We
can see the same failure on a different test run without a systemd
trigger[3].
For jammy[4], we have linux-nvidia[5] and linux-nvidia-tegra-igx[6],
each failing their
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986
Title:
some text became unreadable during a distribution upgrade
Status in ubun
** Tags removed: rls-mm-incoming
** Tags added: foundations-todo
** Tags added: rls-mm-incoming
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) =
Taking a quick look at the logs for arm64,
https://autopkgtest.ubuntu.com/packages/systemd/mantic/arm64, I only see
this specific failure for newer kernels. Have you tried to reproduce
this locally to see if it is in fact introduced by a kernel change?
--
You received this bug notification becaus
Dave - yeah that's the expect outcome with this patch.
--
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/2036358
Title:
systemd wait-online now times out after jammy and luna
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: 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/2038433
Title:
systemd autopkgtest regression on
Werner - it sounds like you might have been having a different issue.
Without the debug level output from systemd-networkd-wait-online, it's
hard to tell what caused the timeout. Glad you have a workaround,
though.
--
You received this bug notification because you are a member of Ubuntu
Touch see
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Tags added: foundations-todo
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received th
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
*** 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
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
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
** 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:
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
** 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
** 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
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
** 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:
** 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 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
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
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
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
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
** 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]
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 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
** 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
A few questions regarding the test plan:
> 1. Create a VM on Azure.
Is chrony the default NTP server on Azure images? It seems we could test
this without Azure if so. Is there a specific chrony.conf needed to see
this issue?
> 2. Run the `udevadm trigger` command.
> 3. Restart the chronyd servic
** 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.net/bugs/1791102
Title:
udev postinst fails because kvm group already exists and is not a
system
801 - 900 of 987 matches
Mail list logo
