Hi, > postinst has: > > if [ -n "$2" ]; then > systemctl daemon-reexec || true > systemctl try-restart systemd-logind.service || true > systemctl try-restart systemd-networkd.service || true > systemctl try-restart systemd-resolved.service || true > systemctl try-restart systemd-timesyncd.service || true > fi > > > Can you run those commands step-by-step and check if a specific restart > is able to trigger the issue? > Might be, that some KDE program doesn't cope with the restart of > systemd-logind and doesn't properly reconnect to the logind D-Bus service.
As you guessed: After the systemd-logind restart, suspend is broken. It was my understanding that D-Bus operates on a per-call basis and there is no such thing as a "connection" between a d-bus client and a service it's accessing (there's of course a "connection" between each peer and the bus daemon, but that's an implementation detail) - but that may just as well be wrong. Kind regards, Ralf _______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
