Ah, thanks! This finally revealed something interesting. So pretty much
everything is shut down already, but the last step triggers an
assertion:
Dec 01 17:23:49 test systemd[1600]: systemd-poweroff.service: Executing:
/bin/systemctl --force poweroff
Dec 01 17:23:49 test systemd[1]: [1;31mAssertion 'sd_id128_randomize(&id) >=
0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting.[0m
Dec 01 17:23:50 test systemd[1]: [1;31mCaught <ABRT>, dumped core as pid
1612.[0m
Dec 01 17:23:50 test systemd[1]: [1;31mFreezing execution.[0m
** Changed in: systemd (Ubuntu)
Status: Incomplete => New
** Summary changed:
- [systemd] SIGPWR doesn't always lead to shutdown
+ Shutdown failure: Assertion 'sd_id128_randomize(&id) >= 0' failed at
../src/core/dbus.c:657, function bus_on_connection(). Aborting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519499
Title:
Shutdown failure: Assertion 'sd_id128_randomize(&id) >= 0' failed at
../src/core/dbus.c:657, function bus_on_connection(). Aborting.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1519499/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
