https://bugs.kde.org/show_bug.cgi?id=435971
Harald Sitter <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #6 from Harald Sitter <[email protected]> --- Huge caveat: this is entirely not fit for production. Technically one could do a poweroff update without any reboot. If packagekit-offline-update.service grew an additional rule Requires=dbus.service (in addition to dbus.target, which will on its own not prevent ordering problems) one can simply isolate into the update target instead of doing a poweroff. - pkcon update -d - sudo qdbus --system org.freedesktop.PackageKit /org/freedesktop/PackageKit org.freedesktop.PackageKit.Offline.Trigger power-off - sudo systemctl daemon-reload - sudo systemctl isolate system-update.target at this point the system should shut down all units that aren't part of the dependency tree of system-update.target and fire up packagekit-offline-update.service (which is part of that target) and packagekit-offline-update.service will then issue the final system power-off once its done. This is however also a fair amount less reliable because isolation doesn't necessarily ensure that everything else has been killed by the time the update starts. Working under the assumption that the update cannot make systemd or dbus fall over that shouldn't really matter though. Anyway, mostly posting this for academic purposes. -- You are receiving this mail because: You are watching all bug changes.
