ThinkPad X1 Carbon Gen 12 Boots into Standby When Lid is Closed (Fedora 41 KDE)

Ask Fedora
, , , , , , , ,
1

I’m experiencing an annoying issue with my ThinkPad X1 Carbon Gen 12 running Fedora 41 KDE.

Problem:

  • The laptop is always used with the lid closed, as it is connected to a Thunderbolt 4 docking station:

    image
    image584×584 43 KB

  • Every time I turn on the laptop, Fedora boots directly into standby mode.

  • To wake it up, I have to open the lid manually, which is inconvenient.

I have double-checked the Power Management settings in KDE, ensuring that the laptop is configured not to enter standby when the lid is closed, so I’m not sure why the laptop goes in standby:

image
image786×318 33.8 KB

The docking station firmware and Fedora are both updated to the latest version.
Except for this small issue, the docking station works perfectly.

Has anyone encountered this issue before? Could this be related to firmware, BIOS settings, or something specific to Fedora 41 KDE?

4

When booting, not KDE Plasma but SDDM (the login manager) starts up

That has its own options for power settings etc, as it is a separate thing.

ChatGPT instead suggests editing the systemd logind config (modified):

run0 mkdir -p /etc/systemd/logind.conf.d

run0 cat > /etc/systemd/logind.conf.d/ignore-lid-switch.conf <<EOF
[Login]
HandleLidSwitch=ignore
#HandleLidSwitchExternalPower=ignore
#HandleLidSwitchDocked=ignore
EOF

Setting 2 and 3 may be optional so I commented them out.

1 Like
6

It seems you’re right, I am no longer noticing the issue after applying the following configuration:

$ cat /etc/systemd/logind.conf.d/ignore-lid-switch.conf 

[Login]
HandleLidSwitch=ignore
HandleLidSwitchExternalPower=ignore

I’m not sure if this should be a considered a bug or not, I found multiple open issues on GitHub:

1 Like
7

Not sure about policies here but adding such a config with disabled lines would be a possible workaround. In the end, the KDE systemsettings would need to have a toggle for that.

Maybe ask for that, linking to this issue?

They could add it in the power settings.

Bugs.kde.org