** Patch added: "dh-python_5.20220819ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1990562/+attachment/5618100/+files/dh-python_5.20220819ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
tatus: Confirmed
** Changed in: dh-python (Ubuntu)
Importance: Undecided => Medium
** Changed in: dh-python (Ubuntu)
Status: New => In Progress
** Changed in: dh-python (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug notification because you
** Bug watch added: Debian Bug tracker #1020528
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020528
** Also affects: dh-python (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020528
Importance: Unknown
Status: Unknown
--
You received this bug notification
** Changed in: dh-python (Ubuntu)
Status: In Progress => Confirmed
** Changed in: dh-python (Ubuntu)
Assignee: Nick Rosbrook (enr0n) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dh-
No, I should have marked it invalid earlier as this bug was specifically
a follow-up for the jammy SRU.
** 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
You could try opening a bug for the linux package
(https://launchpad.net/ubuntu/+source/linux), but I'm not sure it is a
bug exactly. Other tools like depmod may add files to
/lib/modules/$version, which causes apt to not remove the
/lib/modules/$version directory so that it does not accidentally
Also, I believe a simple workaround for this is to add a drop-in to
/etc/kernel/install.d that fixes what is missing from
/usr/lib/kernel/install.d/50-depmod.install. See [1] for more details.
[1] https://man7.org/linux/man-pages/man8/kernel-install.8.html
--
You received this bug notification
Okay, thanks for the additional info. So, you are correct that the red
hat bug does currently apply to 22.04, because we do not have this
upstream commit [1]. However, that bug pertains only to kernel-install,
which is not called in your script. It is also not invoked by apt or the
linux package's
Since the 249.11-0ubuntu3.6 upload of systemd only contains a change to
skip an autopkgtest, Alfonso's previous verification on jammy using
249.11-0ubuntu3.6 is still valid
(https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982462/comments/11).
** Tags removed: verification-needed
The autopkgtest regressions for systemd 249.11-0ubuntu3.6 in jammy-
proposed were all resolved with retries.
--
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/1988994
Title:
The autopkgtest regressions for systemd 249.11-0ubuntu3.6 in jammy-
proposed were all resolved with retries.
--
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/1975667
Title:
The autopkgtest regressions for systemd 249.11-0ubuntu3.6 in jammy-
proposed were all resolved with retries.
--
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/1981042
Title:
The autopkgtest regressions for systemd 249.11-0ubuntu3.6 in jammy-
proposed were all resolved with retries.
--
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/1979952
Title:
The autopkgtest regressions for systemd 249.11-0ubuntu3.6 in jammy-
proposed were all resolved with retries.
--
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/1897932
Title:
The autopkgtest regressions for systemd 249.11-0ubuntu3.6 in jammy-
proposed were all resolved with retries.
--
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/1979951
Title:
The autopkgtest regressions for systemd 249.11-0ubuntu3.6 in jammy-
proposed were all resolved with retries.
--
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/1982462
Title:
The autopkgtest regressions for systemd 249.11-0ubuntu3.6 in jammy-
proposed were all resolved with retries.
--
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/1981622
Title:
The autopkgtest regressions for systemd 249.11-0ubuntu3.6 in jammy-
proposed were all resolved with retries.
--
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/1988078
Title:
systemd-resolved was previously shipped in the systemd package, and
became a separate binary package during the kinetic cycle. This package
provides the default DNS resolver for Ubuntu, so we want it in ubuntu-
minimal.
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
** Changed
Public bug reported:
By default, i.e. with no --variant specified, debootstrap will only pull
in packages with Priority: required or important. Before the systemd-
resolved package split, resolved would be included because it was
shipped with the systemd binary package, which is Priority:
Thanks, Onuh. It looks like you have overridden the systemd-
pstore.service file with one in /etc/systemd/system/systemd-
pstore.service, so the one shipped by the systemd package
(/lib/systemd/system/systemd-pstore.service) is not being used. Please
remove the one in /etc/, and run systemctl
** Changed in: systemd (Ubuntu Focal)
Status: In Progress => 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/1981622
Title:
mtd device must be supplied
** This bug is no longer a duplicate of bug 1988473
[SRU] VirtualBox 6.1.34 guests crash with kernel 5.15.0-47
** Package changed: systemd (Ubuntu) => gdm3 (Ubuntu)
** Changed in: gdm3 (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of
Are you missing a linker flag, i.e. -ludev, or did you forget to include
libudev.h?
If it's not either of those, please provide some more information such
as your current Ubuntu release, and what version of libudev-dev is
installed on your system:
$ apt-cache policy libudev-dev
** Changed in:
Typically, when a version of a package is in -proposed for a stable
release, that is because it is going through the SRU process and is in
the minimum 7-day aging period [1].
In this case, systemd 237-3ubuntu10.54 was removed from -security due to
a serious regression [2]. A fix is being worked
The TEST-58-REPART test was skipped in the ppc64el autopkgtest run of
systemd 249.11-0ubuntu3.6:
https://autopkgtest.ubuntu.com/results/autopkgtest-
jammy/jammy/ppc64el/s/systemd/20220912_215034_cf2f5@/log.gz.
This demonstrates the fix works as intended.
** Tags removed: verification-needed
Please turn on debug-level logging for systemd-resolved by running
`systemctl edit systemd-resolved`, and add the following line to the
[Service] section:
Environment=SYSTEMD_LOG_LEVEL=debug
Then `systemctl daemon-reload && systemctl restart systemd-resolved`.
Once you have some debug-level
Are you invoking kernel-install to remove kernels? Or what action did
you perform exactly? It appears there is a lot more than
modules.builtin.alias.bin leftover in your
/lib/modules/5.15.0-41-generic/.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug
Upon further investigation, the apport exception is caused by ubuntu-
release-upgrader not passing open files to apport correctly.
** Package changed: apport (Ubuntu) => ubuntu-release-upgrader (Ubuntu)
** Changed in: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided => Medium
**
Thanks for the strace output. Can you please also attach journal and
dmesg output for a time range that captures this issue?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I think systemd-resolved should have already been managing
/etc/resolv.conf on 20.04. Did you disable it on your server before? Can
you provide more context on how exactly your DNS was configured before
the upgrade?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You
** Package changed: ubuntu-release-upgrader (Ubuntu) => systemd (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/1991658
Title:
22.04 upgrade left DNS broken,
I think one problem with changing this in systemd is that generators are
allowed to be placed in /run [1]. While mounting /run noexec would not
affect interpreted generators like bash scripts, it would prevent binary
executable generators from being placed in /run.
If we find it necessary, we
My first guess is that there is an inhibitor lock for "handle-lid-
switch" in place which is blocking or delaying the screen lock.
Jonathan - Can you please enable debug level logging on systemd-
logind.service by doing the following?
$ systemctl edit systemd-logind.service
In the editor, add a
FWIW upstream systemd removed the MS_NOEXEC flag from /dev in
https://github.com/systemd/systemd/commit/4eb105fa4aae30566d23382e8c9430eddf1a3dd4.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
When I configure my systemd to lock on lid switch, I do see this debug-
level message:
Oct 12 16:19:45 six systemd-logind[1173]: Inhibitor GNOME Shell (GNOME
needs to lock the screen) pid=2894 uid=1000 mode=delay started.
I am not sure exactly how GNOME handles locking the screen, but maybe
the
Here's a bit more information about the service failure:
-- Logs begin at Sun 2022-09-25 00:05:05 UTC, end at Thu 2022-09-29 12:03:20
UTC. --
Sep 29 12:02:57 autopkgtest-lxd-fexenj systemd-remount-fs[74]: mount: /: can't
find LABEL=cloudimg-rootfs.
Sep 29 12:02:57 autopkgtest-lxd-fexenj
** Tags removed: foundations-triage-discuss
--
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/1990742
Title:
screen not consistently locking when lid is closed
Status in
It seems like for some reason systemd-machine-id-setup was not unpacked
correctly? It's trying to link against libsystemd-shared-245.so, which
is from focal. It should be linking against libsystemd-shared-249.so
instead.
It's called in systemd.postinst, so by that point the new version of the
Public bug reported:
I believe this started early in the kinetic cycle, cf.
https://autopkgtest.ubuntu.com/packages/systemd/kinetic/ppc64el vs
https://autopkgtest.ubuntu.com/packages/systemd/jammy/ppc64el. Timeouts
in the upstream tests have been an issue for a while, but kinetic on
ppc64el
** Summary changed:
- autopkgtest: upstream tests that run in qemu hang on ppc64l
+ autopkgtest: upstream tests that run in qemu hang on ppc64el
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Public bug reported:
Imported from Debian bug http://bugs.debian.org/1021109:
Package: libc6
Version: 2.35-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: kos...@debian.org
Dear maintainer,
After upgrading to libc6 2.35-1 (or 2.36-1 in experimental), nonexistent locale
I came across this today debugging the recent TEST-69-SHUTDOWN failures
in systemd autopkgtest[1]. That test automates a login, which due to the
test environment triggers this segfault and causes the test to fail.
[1] https://autopkgtest.ubuntu.com/results/autopkgtest-
** Patch added: "bash_5.2-1ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1992206/+attachment/5622152/+files/bash_5.2-1ubuntu2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
This bug is the cause of recent systemd autopkgtest failures,
specifically the TEST-69-SHUTDOWN test:
https://autopkgtest.ubuntu.com/results/autopkgtest-
kinetic/kinetic/amd64/s/systemd/20221003_103148_cc8ac@/log.gz. I
confirmed in a local autopkgtest run that this patch fixes the test.
** Also
-in-readline-when-started-.diff (LP:#1992206)
-- Nick Rosbrook Fri, 07 Oct 2022
17:03:05 -0400
** Changed in: bash (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: systemd (Ubuntu)
Status: Fix Committed => Fix Released
** Tags removed: foundations-todo
--
You re
I also confirmed this by testing a 22.04 VM with QEMU/KVM. I agree with
Alkis that this is agetty, so util-linux would be the appropriate
package.
** Changed in: shadow (Ubuntu)
Status: New => Invalid
** Changed in: util-linux (Ubuntu)
Status: New => Confirmed
** Changed in:
Please run apport-collect 1979352 so that the appropriate logs are
attached to the bug. Without proper logs, we will not be able to
investigate this issue.
** Changed in: ubuntu-mate
Status: Confirmed => Incomplete
** Changed in: acpid (Ubuntu)
Status: Confirmed => Incomplete
**
It looks like you're running Raspbian, not Ubuntu. Please open a bug
with Raspbian instead.
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
** Changed in: bash (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1097467
Title:
bash does not fulfill --rcfile option properly
Lowell - Thank you for testing and confirming that the gdb SRU[1] fixes
this!
[1] https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1971474
** Changed in: gdb (Ubuntu)
Status: New => Fix Committed
** Changed in: gdb (Ubuntu)
Importance: Undecided => Low
--
You received this bug
Can you please provide some specific examples of the errors you are
seeing, as well as some instructions to try and reproduce your setup?
** Changed in: initramfs-tools (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch
This drop-in is generated by openssh-server.postinst, and systemd is
correctly rejecting the drop-in without a [Socket] section.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I see the problem in openssh-server.postinst. When only a non-default
Port is used (and ListenAddress is left alone), the temporary
addresses.conf.new file is never moved to it's final location. So, when
the ListenStream= line is appended to the final file, the
'[Socket] ...' portion is not there.
** Patch added: "openssh_9.0p1-1ubuntu7.debdiff"
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991199/+attachment/5620047/+files/openssh_9.0p1-1ubuntu7.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** 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/1975667
Title:
systemd-resolved does not reset DNS server and search domain list
** 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/1959475
Title:
"machinectl shell" connections immediately terminated
Status in systemd
This is because the PPA you are trying to access does not have any
information for xenial (or any release newer than that):
http://ppa.launchpad.net/takluyver/matplotlib-daily/ubuntu/dists/.
Unfortunately you will just need to disable this PPA.
** Changed in: apt (Ubuntu)
Status: New =>
** 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/1979951
Title:
127.0.0.1/::1 removed from loopback interface if you configure extra
IPs
** 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/bugs/1991143
Title:
Systemd reboot halt Lenovo ThinkPad
I did some testing to confirm this is present in jammy (the offending
code is also in kinetic). I will test the upstream fix soon.
** Tags added: rls-jj-incoming rls-kk-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
> if a fix was released how is it broken again?
The fix has not been released to 22.04 yet, it has only been fixed in
the development release.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Hi Ruben,
I have tried to reproduce this by duplicating your config as best I can,
but I have not been able to trigger the issue. Can you please try and
provide a minimal reproducer that can be demonstrated on another
machine?
** Changed in: systemd (Ubuntu Focal)
Status: Triaged =>
This upstream fix for this was backported to 251.4, which I am currently
working on merging from Debian.
** Changed in: systemd (Ubuntu Kinetic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Description changed:
+ [Impact]
+ Some NFS setups that have worked on previous versions of Ubuntu are now
broken. Specifically, when creating a bind mount, systemd will fail if the
directory already exists on NFS.
+
+ [Test Plan]
+ This test plan requires an NFS server to be in place. The
It seems that systemd-oomd is doing what it is supposed to do -- you're
running a memory stress test that is exceeding the memory pressure
limits set by systemd-oomd, so it is killing the offending cgroup(s). If
you want to run the stress tests in a separate cgroup, try making a
script called e.g.
Public bug reported:
[Impact]
If a user a has an existing drop-in config for ssh.socket in
/etc/systemd/system/ssh.socket.d upgrades to kinetic, and openssh-
server.postint determines it should *not* perform migration to socket-
activated ssh, they will receive an error from dpkg:
Errors were
** Tags removed: foundations-triage-discuss
--
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/1992979
Title:
kinetic ppc64le reporting Failed to send WATCHDOG=1 notification
** Changed in: systemd (Ubuntu)
Status: New => 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/1988010
Title:
systemd ignoring DHCP DNS servers and DNS
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
** Changed in: systemd (Ubuntu)
Status: Won't Fix => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Public bug reported:
[Impact]
On systems with mellanox NICs, udev's NIC renaming races with the mlx5_core
driver's own configuration of subordinate interfaces. When the kernel wins this
race, the device cannot be renamed as udev has attempted, and this causes
systemd-network-online.target to
I confirmed this patch is not present in kinetic, but it will be in
lunar.
** Also affects: e2fsprogs (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: logrotate (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: man-db (Ubuntu Kinetic)
Public bug reported:
The systemd-binfmt.service requires read-write access to
/proc/sys/fs/binfmt_misc, but this is not possible in unprivileged LXD
containers without binfmt_misc namespace support in the kernel [1]. When
this service is triggered, we get the following failure from
test_no_failed
These packages are updated at the same time (they are both built from
src:systemd). Please make sure your sources are up to date first with
`sudo apt update`.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of
This has been resolved upstream[1] and I will bring the patches into
lunar.
[1] https://github.com/systemd/systemd/pull/25693
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification
** Package changed: ubuntu-release-upgrader (Ubuntu) => mesa (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1998639
Title:
MESA-INTEL: warning:
Status in mesa
Ah yeah, this would do it:
E: Release file for
http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease is not valid
yet (invalid for another 10h 24min 10s). Updates for this repository will not
be applied.
E: Release file for
The command-not-found package is responsible for showing that
information. I'm not sure how the internals work though, so it's
possible there's something wonky with the systemd package that confuses
command-not-found.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
** Also
The autopkgtest failures in kinetic have all been resolved with retries
and/or hinting.
--
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/1995294
Title:
rmdir: failed to
The autopkgtest failures in kinetic have all been resolved with retries
and/or hinting.
--
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/1993478
Title:
package
It seems like your apt sources or local package information is out of
date. The libsystemd-dev package depends on libsystemd0 such that they
have the same version:
$ apt-cache show libsystemd-dev
Package: libsystemd-dev
Architecture: amd64
Version: 249.11-0ubuntu3.6
Multi-Arch: same
Priority:
The util-linux package is responsible for
/lib/systemd/system/fstrim.{timer,service}.
** Package changed: systemd (Ubuntu) => util-linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
There have been several updates on the upstream bug, so I have opened a
task for jammy.
** Also affects: systemd via
https://github.com/systemd/systemd/issues/25091
Importance: Unknown
Status: Unknown
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status:
Thanks for the update. I'll mark this as invalid since there is nothing
to do.
** 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.
Since this is link-specific DNS, isn't the scope ID implied?
I do see the odd formatting issue in the 'DNS Servers' list:
$ resolvectl status wlp0s20f3
Link 4 (wlp0s20f3)
Current Scopes: DNS
Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server:
Right, I understand why it would be needed in a ping. But since the DNS
server config in systemd-resolved applies to a specific link, the scope
ID is implied.
As far as your desktop vs server systems, maybe it's the difference
between the interfaces available on each system? If you only have one
** Also affects: ubuntu-power-systems
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/1992178
Title:
autopkgtest: upstream
The option doesn't literally get appended to the original file, but when
the settings are applied it will use the drop-in conf as well. What does
resolvectl mdns show? The rest of your output looks expected (networkctl
status won't mention the use of the drop-in config). I have tested this
on
Are there any errors in your journal about the config? Check journalctl
-b 0 --grep eno1 for starters. Also just to double check, you are
running the latest version of systemd in jammy, right? It should be
249.11-0ubuntu3.6.
--
You received this bug notification because you are a member of
You can use a drop-in configuration to achieve this:
$ cat /etc/systemd/network/10-netplan-eth0.network.d/mdns.conf
[Match]
Name=eth0
[Network]
MulticastDNS=yes
This will basically append the MulticastDNS option to the existing
netplan-generated network configuration. Does that solve your
> I think it is a bug in systemd to be bypassing the process
> specified in Debian Policy.
Note that systemd specifies its own UID/GID "spec" here:
https://systemd.io/UIDS-GIDS/.
I think assigning 999 to systemd-journald conforms with both systemd's
and Debian's policy, no? The systemd-journal
I have not taken a close look at the man pages to see if it mentions
this, but systemd-cryptenroll dlopen()'s the libraries needed for TPM2
support. So the message "TPM2 support is not installed." means the
binary was compiled with TPM2 support, but you need to install the
libraries. On the other
** Tags removed: verification-needed-kinetic
** Tags added: verification-done-kinetic
--
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/1995294
Title:
rmdir: failed to
I have verified the fix using openssh-server from kinetic-proposed:
root@jammy:~# grep "^ListenAddress" /etc/ssh/sshd_config
ListenAddress 0.0.0.0
ListenAddress ::
root@jammy:~# systemctl edit ssh.socket
root@jammy:~# cat /etc/systemd/system/ssh.socket.d/override.conf
[Unit]
Description=SRU
I have verified each test case using openssh-server 1:9.0p1-1ubuntu7.1
from kinetic-proposed:
Test #1:
root@jammy:~# grep "^ListenAddress" /etc/ssh/sshd_config
ListenAddress 0.0.0.0:1234
root@jammy:~# systemctl status ssh
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
** Tags removed: foundations-triage-discuss
--
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/1993318
** Description changed:
[Impact]
Users with /etc/ssh/sshd_config's that contain ListenAddress entries
with the port specified will not be migrated to socket-activated ssh
correctly, or may be migrated when they should not be (e.g. if
ListenAddress, with a port number, is specified
This revised patch addresses Steve's review comments.
** Patch added: "openssh_9.0p1-1ubuntu8-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478/+attachment/5628224/+files/openssh_9.0p1-1ubuntu8-v2.debdiff
--
You received this bug notification because you are a
** Also affects: openssh (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Changed in: openssh (Ubuntu Kinetic)
Status: New => Triaged
** Changed in: openssh (Ubuntu Kinetic)
Importance: Undecided => Low
** Changed in: openssh (Ubuntu)
Status: New => Triaged
**
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2009317
Title:
All Snaps Broken After
201 - 300 of 823 matches
Mail list logo
