I can't make comments about the regressions, however I tested the
systemd (245.4-4ubuntu3.18) package in a focal container and confirm
that solves this bug (connecting from a jammy host).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
The selective version of the fix works for me, even if I'm not using xubuntu (I
use the Cinnamon desktop).
Thanks to Sebastien!
--
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/bu
Sorry, the host was running Ubuntu jammy with systemd 249.9-0ubuntu2.
--
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 immediat
>From the last comments in:
https://github.com/systemd/systemd/issues/22234
the problem is due to an incompatibility of the new versions of systemd with
older ones.
In fact the container was running ubuntu focal, with systemd_245.4-4ubuntu3.15,
and the host was running ubuntu focal with systemd
These are the messages reported by journalctl inside the container:
Jan 29 12:27:53 ns-xxx systemd[153]: Assertion 'a' failed at
src/basic/path-util.c:486, function path_compare(). Aborting.
Jan 29 12:27:53 ns-xxx systemd[1]: container-shell@2.service: Succeeded.
-- Subject: Unit succeeded
-- Def
Sorry, the patch in:
https://github.com/systemd/systemd/commit/e8cf09b2a2ad0d48e5493050d54251d5f512d9b6
is already applied in systemd 249.9-0ubuntu2, so that is not the
solution.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Public bug reported:
The command "machinectl shell" does not work in systemd 249.9-0ubuntu2:
$ sudo machinectl shell ns-xxx
Connected to machine ns-xxx. Press ^] three times within 1s to exit session.
Connection to machine ns-xxx terminated.
The issue seems to be described here:
https://forum.m
I confirm that after installing printer-driver-cups-pdf 3.0.1-13 from
impish/proposed the cups-pdf-printer is working properly.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/19
8 matches
Mail list logo