** Changed in: systemd (Ubuntu)
Status: New => 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/1895528
Title:
Setting in manpage of resolved.conf does n
** Changed in: systemd (Ubuntu)
Importance: Undecided => Wishlist
--
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/1870585
Title:
Not cleaning /var/tmp by default
Status
** Changed in: systemd (Ubuntu)
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/1405199
Title:
Using open() on an optical drive with its tra
** Changed in: systemd (Ubuntu Impish)
Status: New => Won't Fix
** Changed in: systemd (Ubuntu)
Status: New => 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.launchp
I have verified that systemd-repart is available in jammy-proposed, and
that the upgrade path to kinetic works as expected:
root@jammy:~# apt-cache policy systemd-repart
systemd-repart:
Installed: 249.11-0ubuntu3.6
Candidate: 249.11-0ubuntu3.6
Version table:
*** 249.11-0ubuntu3.6 500
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/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:
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/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:
** Changed in: systemd (Ubuntu Focal)
Status: Triaged => Fix Committed
** Changed in: systemd (Ubuntu Focal)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https:/
> Eh? That isn't at all what the patch does...
Before the patch, the `getenv("TERM")` call would not happen; now it
does.
While fixing path_compare() may be a better long-term solution, I think
the existing patch is appropriate for this bug/SRU.
--
You received this bug notification because you
Er, I see the problem in my description now. It's been a while since I
looked at this patch. In any case, the patch is still appropriate.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpa
** Description changed:
[Impact]
This bug prevents users on Impish and newer from connecting to Focal
systemd containers using `machinectl shell`. This limits users ability
to manage containers spawned with systemd-nspawn.
[Test Plan]
On a Jammy host, do the following:
*
** Tags added: foundations-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1988819
Title:
When apt keeps back packages due to phased updates, it should say so
S
** 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
Public bug reported:
In Kinetic, TEST-36-NUMAPOLICY from upstream-2 fails very frequently on
ppc64el. See for example:
https://autopkgtest.ubuntu.com/results/autopkgtest-
kinetic/kinetic/ppc64el/s/systemd/20220908_195425_da51e@/log.gz, and the
full kinetic ppc64el history:
https://autopkgtest.ubun
I'm not sure I understand the problem you are experiencing. Can you
please expand on what you are trying to do, and what unexpected behavior
you are seeing?
Ideally, if you could provide steps to reproduce the problem, we can
better investigate the issue.
** Changed in: systemd (Ubuntu)
St
Onuh - are you running with -proposed enabled? This update hasn't been
released yet.
--
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 suppl
Onuh and David - Please share the output from the following commands:
$ apt-cache policy systemd
$ systemctl list-dependencies systemd-pstore.service
$ systemctl list-dependencies --reverse modprobe@mtdpstore.service
$ systemd-analyze unit-files systemd-pstore.service
--
You received this bug n
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 in
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: importan
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 daemo
** 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 (devi
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: sy
There is a pkgconfig file shipped with udev itself, which just contains
the definition of udev_dir. This is unrelated to the udev development
package (libudev-dev). For development purposes, you should be using
libudev, e.g. `pkg-config --libs libudev`.
The rest sounds related to your build system
rtance: Medium
Status: 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
** 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 subscr
** 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-pyt
** 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 be
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 logs,
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 not
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
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 b
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 d
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
*** This bug is a duplicate of bug 1967576 ***
https://bugs.launchpad.net/bugs/1967576
This was fixed in bug 1967576, so I am marking this a duplicate of that.
** This bug has been marked a duplicate of bug 1967576
systemd: autopkgtest: tests-in-lxd fails because of remaining snap .mount
This does not look like a systemd bug, so I am re-assigning to linux.
But, this sounds similar to your issue:
https://forums.developer.nvidia.com/t/nvidia-probe-of-00-0-failed-
with-error-1/199301, based on looking at your attached CurrentDmesg.txt.
** Package changed: systemd (Ubuntu) => li
: foundations-todo
** Changed in: ubiquity (Ubuntu Kinetic)
Assignee: Nick Rosbrook (enr0n) => (unassigned)
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Kinetic)
Status: New => Fix Released
** Changed in: ubiquity (
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 syst
** 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
** 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
properl
** 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 pa
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
** Changed
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 s
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 noti
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 seeded
** 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
Sta
** 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 x230
** 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, resol
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 received
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 coul
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 consis
** 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.
https://bugs.
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-
kinetic/kinetic/amd64/s/syst
** 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.
h
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 af
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.
https://bugs.
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
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 b
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 systemd-
** 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 sys
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
bina
-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: util-l
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.
https://bugs
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
** Ch
Murmel - What release of Ubuntu are you running? This has only been
fixed on Kinetic, not Jammy.
--
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 p
I think at the very least we would need to see journal output from that
time (at least until it crashes that is), and dmesg output from around
that time.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touc
This makes me think pid1 is dead, since the notification socket is
apparently down. Can you please try booting with these options appended
to the kernel command line?
systemd.log_level=debug systemd.log_target=console console=ttyS0,38400
console=tty1
Hopefully that will give us more information t
Sorry, I wrote my comment in a confusing way. No additional patch was
needed in Kinetic for this issue. However, the fix has not been released
for Jammy yet, but a patch has been provided that will be included in
the next systemd SRU.
--
You received this bug notification because you are a member
Upstream has encountered this issue on their CI as well:
https://github.com/systemd/systemd/issues/25091.
** Bug watch added: github.com/systemd/systemd/issues #25091
https://github.com/systemd/systemd/issues/25091
--
You received this bug notification because you are a member of Ubuntu
Touch
** Also affects: openssh (Ubuntu Kinetic)
Importance: Critical
Status: 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/1993478
Title:
package openssh-serv
** 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 mor
** Patch added: "openssh_9.0p1-1ubuntu8.debdiff"
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478/+attachment/5627076/+files/openssh_9.0p1-1ubuntu8.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to open
** Description changed:
+ [NOTE FOR SRU TEAM]
+
+ I would prefer that vorlon review the attached patch before the upload
+ is accepted. I will remove this note when that has happened.
+
[Impact]
Users with /etc/ssh/sshd_config's that contain ListenAddress entries
with the port specified
Looking at the upstream code, the --poweroff option is intentionally
ignored when reboot is invoked [1]. The man page should be fixed to
document this exception.
[1]
https://github.com/systemd/systemd/commit/a042efad57741e90ee78b69c57310858295bf3fc
** Changed in: systemd (Ubuntu)
Status: N
Fixed upstream: https://github.com/systemd/systemd/pull/25172.
--
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/1995048
Title:
reboot reboots system when --poweroff is passe
This patch has not been brought into the Ubuntu packaging yet, so the
status should remained "Triaged" for now.
** Changed in: systemd (Ubuntu)
Status: Fix Committed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
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 en
** 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 mor
** 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
** Ch
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 member
** 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
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 verif
** 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 remove
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 (/lib/syste
** 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
Title
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 remo
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 openssh-serve
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 affect
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: opti
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.
https://bugs
601 - 700 of 885 matches
Mail list logo
