On Sat, Mar 07, 2015 at 12:47:33AM +0100, Michael Biebl wrote:
Can you provide steps how this issue can be reproduced?
Actually, I just discovered a set of steps on how to reproduce this: Run kill -s ABRT 1 Run telinit u Suspend the machine (possibly multiple times)When the machine unsuspends, systemd will no longer be responding to service commands. Also, on a laptop, Network Manager will work, although the applet will indicate it's not connected.
In my case, I interrupted the telinit u with Ctrl-C (as I thought it had hung) and suspended the machine several hours later.
-- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
signature.asc
Description: Digital signature
_______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
