So it happened again, but on a different machine. After waking it up from hibernation the network-manager remained in the "asleep" state and logind reported that it is still in "PrepareForSleep" mode.
I am not sure, if restoring the pm-utils hook will resolve the actual issue.
So it happened again, but on a different machine. After waking it up from hibernation the network-manager remained in the "asleep" state and logind reported that it is still in "PrepareForSleep" mode.
I am not sure, if restoring the pm-utils hook will resolve the actual issue.