On Sun, 28 Jun 2015 19:08:35 +0200 Sven Arvidsson <s...@whiz.se> wrote:
> On Thu, 2015-06-25 at 23:41 -0400, Celejar wrote: > > Hi, > > > > Running wheezy. I've been suspending to ram (hibernate-ram --force) > > my > > ThinkPad T61 for several years with no problems. Recently, I > > installed > > acpi-support to enable suspending via lid closure (by enabling > > LID_SLEEP=true in /etc/default/acpi-support). I still tend to enter > > the > > hibernate command manually, by habit, followed by lid closure. When I > > subsequently open the lid, the machine wakes up (as it always has > > done, > > even before installing acpi-support) - and then goes back to sleep > > several seconds later (which it never did before). > > > > It seems pretty clear that somehow, the lid closure is triggering a > > second hibernation, which takes place after the machine wakes up from > > the first (even though the closure occurs after the machine has > > already > > gone to sleep). This is certainly not the desired behavior - is this > > is > > bug? Should I file against acpi-support? > > > > Celejar > > Do you get the right behaviour if you use "systemctl suspend" (or > hibernate) instead? If so, maybe acpi-support should be changed to use > that first for systemd setups. This is an old Wheezy system, without systemd. Celejar -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150628160052.0cac26d3a93b784e0d0b5...@gmail.com
