This bug was fixed in the package systemd - 243-2ubuntu1
---
systemd (243-2ubuntu1) focal; urgency=medium
* Merge to Ubuntu from experimental
* Refresh patches:
- Dropped changes:
* Cherrypick ask-password: prevent buffer overrow when reading from
keyring.
@panfaust I believe this should be fixed now upstream by
https://github.com/systemd/systemd/pull/13656
can you verify that is correct? And we shouldn't need anything in Eoan
since it's going to be based on 242, which doesn't have commit
97afc0351a96e0daa83964df33937967c75c644f that introduces
** Changed in: systemd
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/1845314
Title:
udisks2 fails to install in a container with
** Changed in: systemd
Status: Unknown => 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/1845314
Title:
udisks2 fails to install in a container with systemd
On thinking about this, it does seem the behavior change of udevadm will
be highly disruptive to existing callers of udevadm trigger, so I opened
upstream bug to try to address it without needing all callers to ignore
its return code.
** Bug watch added: github.com/systemd/systemd/issues #13652
** Tags added: id-5d6fba2cac409d12ddb60a25
--
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/1845314
Title:
udisks2 fails to install in a container with systemd 243
Status
Hey BTW, I suspect this 'error' is due to upstream commit
97afc0351a96e0daa83964df33937967c75c644f which changed udevadm's
behavior; previously it silently ignored errors writing to
/sys/devices/*/uevent files, but now it logs error and returns error
code. So this is likely not *actually* a new
Oh, and a better fix would be not calling udevadm when 'systemd-detect-
virt --private-users' is true. It's a bit annoying that every udevadm
caller would need to know that, however.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
And yeah, ignoring the udevadm return value with ||: could be one way to
avoid the error.
--
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/1845314
Title:
udisks2 fails to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
3. How we could fix it?
Well, given the data I posted above, my *guess* is that we could safely
ignore the udevadm non-zero exit status in the udisks2 postinst script
with something like this:
if [ "$1" = "configure" ]; then
# we ship udev rules, so trigger an update
udevadm trigger
2. Why this is happening?
First of all, the udisks2 installation fails because the postinst script
fails. Inspecting the postinst script of udisks2, we can see these
lines:
if [ "$1" = "configure" ]; then
# we ship udev rules, so trigger an update
udevadm trigger --subsystem-match=block
Hi, I'm the santa_ above, so, to explain the full picture I'm going to
write 3 separate messages below trying to answer these 3 questions:
1. How to reproduce the issue?
2. Why this is happening?
3. How we could fix it?
--
You received this bug notification because you are a member of Ubuntu
1. How to reproduce the issue?
Very easy, you just have to create an eoan LXD container, add the ppa with
systemd 243:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3801/+packages
and then just do "apt dist-upgrade" to upgrate to systemd 243 and "apt
install udisks2", the udisks2
14 matches
Mail list logo
