On Tue, May 06, 2014 at 07:02:56PM +0200, Andreas Cadhalpun wrote: > Control: reassign -1 libpam-systemd 204-5 > Control: forcemerge 729576 -1 > > Hi, > > this is yet another duplicate of #729576, see also #726763. > > The problem is solved by libpam-systemd now having a dependency on > 'systemd-sysv | systemd-shim'.
I've switched laptops since reporting that bug, and once the TC had ruled on systemd switched to using that instead of sysvinit. So I can't test the situation that was broken back in December any more (i.e. that the suspend key stopped working, but the menu option worked). I can say that both the suspend key and the menu option are working fine on my current machines, however both are running with systemd as init. J. -- How does it work? I don't know but it does! This .sig brought to you by the letter K and the number 8 Product of the Republic of HuggieTag _______________________________________________ Pkg-systemd-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
