Lidswitch stopped doing anything (certainly stopped locking as desired), and unsure why: no dmesg output for lid-close

Help
1

I’m not sure if closing my laptop (lidswitch close) is suspending, but certainly when I open the lid, I find the screen unlocked. Question: any obvious steps to debug that lid-switch hardware events are even coming through to one’s laptop?

  • The hardware I have is: framework 13 inch 1st-gen laptop (the “11th gen intel”)
  • The nixos config I have is: this folder (symlink to this is followed; whole thing’s copy/pasted as a tree of content up into /etc/nixos/...)

debugging steps I’ve tried…

  1. checking my systemd settings…

I currently have uncommented this unrelated line (“unrelated” because it should only apply to being docked) just to be sure:

services.logind.lidSwitchDocked = "lock"

and according to docs, suspend should be default for lidSwitch but I’ve explicitly set that too, just to be sure.

  1. fwupdmgr update already says I’m on the latest firmware

  2. get a baseline: it used to work with this exact same hardware, but I recently upgraded my SSD, so reinstalled nixos from scratch. Then I merged my old configs with my new calamari-generated configs. It could be I messed up something int he process of reinstalling, but thought I’d ask here before continuing to dig.
    - made sure I followed the couple manual setps for channels for nixos-hardware
    - made sure to reboot
    - next: I guess I can try to find logs to indicated lidswitch is even being detected? I assume dmesg should show lidswitch happens, but maybe not (maybe logs normally only output for suspend/etc.-- systemd’s actions when it is handling lidswitch with a suspend?)

2

Hello
The lidswitch event and sleep is not in dmesg. It is logged in journalctl.
To see when the lid close event is triggerd use this command:

journalctl | grep "Lid closed"

Then just pick a time when the lid got closed and type something like this:

journalctl | grep "Jan 12 08:39"