severity 747749 wishlist thanks Hi,
Am Mon, 12 May 2014 07:24:05 +0200 schrieb Martin Pitt <mp...@debian.org>: > Julian Wollrath [2014-05-11 16:17 +0200]: > > I switched from sysvinit to systemd and now, if I close the lid, my > > machine suddenly suspends. For me this means, that the data of my > > current session is lost, since there are some problems with suspend > > with my machine. > > > > This is unspected behaviour, that at least I would not expect from > > just changing the init system, since the init system should not > > have to do anything with events like closing the lid. > > It's not immediately connected to the init system, but that's logind. > You'll get the same if you use systemd-shim and sysvinit or upstart. > > I strongly advise to keep the current behaviour as a default. > [...] > It also mirrors what acpi-support does: It handles the power button to > shut down the machine (like logind) and on *some* models handles the > lid switch (but that's not very reliable). Logind's lid switch > handling uses the current kernel mechanisms which are fairly good. > > I claim that the number of users which expect their laptop to sleep > when they close the lid greatly outnumbers the number of users for > which sleep isn't working. that may be but nevertheless, I thought, that I just installed an init system and suddenly things like that happend. So maybe there should be a heads up in the package description or the README.Debian containing something along the lines: This package not only includes the systemd init replacement but also logind, a daemon for managing user logins and seats, which among other things also takes care of handling suspend and hibernation. > > I was able to restore the old behaviour (doing nothing) by editing > > the HandleLidSwitch entry in /etc/systemd/logind.conf > > Right, that would be the place to change it if you don't want this > behaviour outside of desktop sessions. The better fix would of course > be to fix sleep on your machine -- what's going wrong there? The screen stays black and not even the magic sysrq keys work but since I am not using the standard Debian kernel and do not have time to bisect it at the moment, it is not a problem we can solve here. > > Therefore, please consider changing the default to doing nothing > > when doing this actions, so that others do not get this unexpected > > behaviour and experience data loss like I did. > > Pretty much all OSes send the computer to sleep when you close the > lid, I think that should count as "expected behaviour" these days. I have no clue about other OSes, so maybe it just was unexpected for me. Cheers, Julian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
