Arch Linux

chx

Member

Registered: 2011-05-28

Posts: 101

ACPI events no longer work

I have a T420. When I close the lid , the system doesn't sleep. Manual sleeping systemctl suspend works. I checked /etc/systemd/logind.conf and it's comments only. I restarted systemd-logind. lid close/open events are in journalctl. acpid is not running, [ktpacpid] and [acpi_thermal_pm] do. Brightness keys don't work (they haven't for a while now) manually setting brightness in /sys/class/backlight/intel_backlight does work. When I grabbed acpi_listen , the keys showed up as ACPI events. Since I removed and stopped acpid. I have no idea why events don't fire anything in systemd.

Aug 23 13:50:54 veyron2 systemd[1]: Stopped Login Service.
Aug 23 13:50:54 veyron2 systemd[1]: Starting Login Service...
Aug 23 13:50:54 veyron2 systemd[1]: Started Login Service.
Aug 23 13:50:54 veyron2 systemd-logind[1388]: New seat seat0.
Aug 23 13:50:54 veyron2 systemd-logind[1388]: Watching system buttons on /dev/input/event7 (Power Button)
Aug 23 13:50:54 veyron2 systemd-logind[1388]: Watching system buttons on /dev/input/event15 (Video Bus)
Aug 23 13:50:54 veyron2 systemd-logind[1388]: Watching system buttons on /dev/input/event5 (Lid Switch)
Aug 23 13:50:54 veyron2 systemd-logind[1388]: Watching system buttons on /dev/input/event6 (Sleep Button)
Aug 23 13:50:54 veyron2 systemd-logind[1388]: Watching system buttons on /dev/input/event8 (ThinkPad Extra Buttons)
Aug 23 13:50:54 veyron2 systemd-logind[1388]: New session c6 of user chx.
Aug 23 13:50:54 veyron2 systemd-logind[1388]: New session c2 of user chx.
Aug 23 13:50:54 veyron2 systemd-logind[1388]: New session c8 of user chx.
Aug 23 13:50:54 veyron2 systemd-logind[1388]: New session c7 of user sddm.
Aug 23 13:51:17 veyron2 systemd-logind[1388]: Lid closed.
Aug 23 13:51:26 veyron2 systemd-logind[1388]: Lid opened.
Aug 23 13:57:51 veyron2 systemd-logind[1388]: Lid closed.
Aug 23 13:57:56 veyron2 systemd-logind[1388]: Lid opened.

Last edited by chx (2015-08-23 12:05:46)

Raynman

Member

Registered: 2011-10-22

Posts: 1,539

Re: ACPI events no longer work

What does systemd-inhibit show?

chx

Member

Registered: 2011-05-28

Posts: 101

Re: ACPI events no longer work

Enlightenment is listed but a) Enlightenment is also set to suspend on lid b) Brightness (which was broken in KF5 before I ditched it) c) #LidSwitchIgnoreInhibited=yes

Edit: this is I why I dislike modern Linux, there's magic happening somewhere and I have absolutely no clue as to where and to how to debug it. acpid was simple, there are events (which can be checked to fire), a script handling events and that's all

Last edited by chx (2015-08-23 14:19:58)

Raynman

Member

Registered: 2011-10-22

Posts: 1,539

Re: ACPI events no longer work

Well, then use acpid.

Or you could try closing the lid without Enlightenment running.

Last edited by Raynman (2015-08-23 14:45:03)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,729

Re: ACPI events no longer work

Did you check the optdepends for Enlightenment?

chx

Member

Registered: 2011-05-28

Posts: 101

Re: ACPI events no longer work

I really hate Linux on days like this. Absolutely nothing works.

I fixed backlight by removing acpi_backlight=vendor . I also removed acpi_osi=Linux but it didn't help suspend at all. I am sure one day suspend will begin working again or I will figure out why it doesn't. The whole situation reminds me when I tried to get a DisplayLink monitor working and people insisted on reading the wiki section which I wrote. (Because, LidSwitchIgnoreInhibited should ignore the inhibitors...)

Since I ditched KF5 plugging / unplugging a monitor doesn't crash the system (should I be happy about that?) but it also doesn't resize automatically. Sigh.

On reboot KDE apps and super duper annoyingly, Chrome, decides to use oversize fonts (but only in tab titles) and I need to run the KDE System Settings to set the same font size and then things work. Why? What gets set? Where? How? No answers. Open source hates documentation. I fight it in my own community but one grows tired of fightin', ya' know?

I am sure after spending a few days of configuring Enlightenment, fighting the stupidity of systemd (I am losing that fight, even when I switched the loglevel to debug, there's nothing between Aug 23 18:13:25 veyron2 systemd-logind[390]: Lid closed.
Aug 23 18:13:29 veyron2 systemd-logind[390]: Lid opened.) etc I will have a system which works somewhat as well as it did four years ago and I can pray this time the E17 developers not lose their marbles and begin to chase something new and break everything again.

Last edited by chx (2015-08-23 16:22:27)

Noob Saibot

Member

Registered: 2015-11-03

Posts: 12

Re: ACPI events no longer work

Were you able to eventually resolve this issue?