..at least that's what seems to be happening.
I have had
for a long time but after updating today the power key just powers off which is the default.
No error messages are shown in the logs, the only thing I see is
So it looks like elogind is actually still handling the power key, but just using the default value instead of what is in /etc/elogind/logind.conf

There's a bugfix release elogind-255.4-r1 that fixes stuff. This thread applies

I did see that -r1 release on github but the changes didn't seem to apply to my problem so I didn't build it. I just built it now though, and it doesn't fix the problem.
I downloaded and built 252.23-r1 from github and built that, and now my config works again - but after resume the network is broken.

From the 255.4 changelog 3 days ago:
I guess that is what caused the problem. So I need to figure out if it's a bug in elogind or do I just need to update my config
Although that is sleep.conf, but the setting is from logind.conf.
~~Maybe I just need to move it.....~~ Nope, moving the settings to sleep.conf just give a warning that the key is not recognized in the Sleep section.

It looks like logind.conf and logind.conf.d don't get parsed at all in version 255.4. Even if I put incorrect values in the files elogind doesn't complain. It only mentions the sleep.conf files.

I have found the difference between reading logind.conf and sleep.conf files. When reading logind.conf it prepends PKGSYSCONFDIR to the logind.conf file name which prevents it from finding it. Not sure if this is a problem with the slackbuild or a bug in the code.
I added
To the SlackBuild and then it reads the config OK.

I have opened an issue here: https://github.com/elogind/elogind/issues/279

4 members found this post helpful.

The patch to fix reading of logind.conf has been applied to elogind upstream now which fixes this issue

3 members found this post helpful.