You are not logged in.
Using Arch on a Chromebook laptop. "sytemct suspend" works just fine when command launched from keyboard. However, sometimes when launched using acpi lid close event I open the lid to find that the system has resumed and battery power has drained. This happens inconsistently. This is what I have in my /etc/acpi/handler.sh file for a lid close event
xset -dpms
xset s 10
pkill dwb
sudo systemctl suspend
I am not sure what logs to check to try to diagnoze why this might be happening. Any ideas appreciated.
Philosophy is looking for a black cat in a dark room. Metaphysics is looking for a black cat in a dark room that isn't there. Religion is looking for a black cat in a dark room that isn't there and shouting "I found it!". Science is looking for a black cat in a dark room with a flashlight.
Offline
Who is the manufacturer? Samsung by any chance?
Offline
Yes, Samsung - why?
Philosophy is looking for a black cat in a dark room. Metaphysics is looking for a black cat in a dark room that isn't there. Religion is looking for a black cat in a dark room that isn't there and shouting "I found it!". Science is looking for a black cat in a dark room with a flashlight.
Offline
If the problem started upon upgrading to kernel 3.16.3 then you are possibly suffering from the same underlying issue as I've got here:
acpi says discharging; plugged in and charging
The kernel bug tracker can tell you more.
Offline
The problem has existed for the last few kernels so I don't think your suggestion is the problem. I will continue trying to find something in the systemd journal.
Philosophy is looking for a black cat in a dark room. Metaphysics is looking for a black cat in a dark room that isn't there. Religion is looking for a black cat in a dark room that isn't there and shouting "I found it!". Science is looking for a black cat in a dark room with a flashlight.
Offline