I’m suddenly having a weird issue with Fedora 43 on my FW 12. The power button turns off the computer now, instead of suspending it. Closing the laptop will still put it into suspend, but the power button shuts it down. If I restart the machine the power button behavior changes back to suspend. But before long, the behavior goes back to powering the unit off. Also, once the power button behavior changes, selecting “Suspend” from the power menu does nothing. I can click in the top right, open the power options, click “Suspend,” and nothing happens.
This behavior has persisted now across multiple updates and kernel versions. A re-start always fixes it for a short time.
Which Linux distro are you using? - Fedora 43 (GNOME)
(If rolling release, last date updated?) - Last updated, earlier today. But this issue has been going on for at least a couple weeks, maybe a month.
Which kernel are you using? - Currently, 6.19.12-200
Which BIOS version are you using? 3.07
Which Framework Laptop 12 model are you using? (13th Gen Intel® Core™) i5-1334u
I recently opened a bug for a tangential issue (different behavior, different FW laptop). What do the journal queries (see bug for example) look like in your case in the success vs failed case?
@dimitris I’m very much a Linux noob, even though I’ve been using it for a couple years, lol. This morning I was doing some googling and added a custom file to hopefully force the power key to be suspend. We’ll see if that worked, lol. For better or worse, I rebooted after my changes, so it’s working now. The journal looks pretty normal. It detects the power button was pressed and suspended. If/when it acts up again, I’ll check the journal again.
The delta in the journal between the “fresh boot” and “corrupted” behavior could be a good thread to pull (no pun intended) towards the root cause.
Also, while acknowledging that people can (and should) have strong opinions about this: As a Linux curmudgeon for more than two decades now, I can honestly say, give AI (at least Claude Opus, that’s what I use day to day) a whirl on this. It probably won’t get you to the root cause by itself, but it’ll definitely suggest good avenues to explore. It has also been, for me, somewhat liberal with explaining the why of these Linux bug exploration suggestions, which is in itself instructional. Don’t forget to ask it more “why” questions, and turn research mode on
I saw some folks (and AI) say that you shouldn’t modify the logind.conf file where it is (user/lib/systemd), but should instead make a directory called logind.conf.d in etc/systemd/, copy the file into that directory, and then modify that file.
I did that and changed the power key behavior to suspend in that config file.
I literally just followed instructions I found. I figured worst case scenario, all I had to do is delete the file I created if it didn’t work or messed something up.
If any of that was wrong or stupid or pointless, I’m open to being told so, lol.
Edit: Knock on wood, so far the power key is still working as suspend. It hasn’t even been quite 24 hours, but usually it would have reverted by now. But maybe that’s pure coincidence.
