I am Manjaro user for many year. Running it on my older DELL Latitude E7470 without any problems with GNOME. I bought new notebook ThinkPad T14 Gen4 (Intel).
I installed latest Manjaro with GNOME and notice that in the moment I switch KVM switch to other computer my notebook suspends itself. This happens also when I use latest Fedora with GNOME.
I am not sure what can cause this. I have searched all over place and only indication I can find out is connection of this suspend and losing video output.
Would you have some suggestion what could cause this or what steps I can take to further investigate and find the cause?
Thank you
-r-
That means than KVM (Keyboard, Video, Mouse) switch will connect my mouse, keyboard and video from my notebook to other computer, in this case to my desktop.
-r-
Does the keyboard have keys for power, sleep, etc.? … if so, do you have another KB without these to try? I ask because I’ve had a similar (but in my case quite the opposite) issue where the KB would wake the machine immediately after entering suspend / hibernate.
Could be the KB itself is the issue, or possibly the KVM device.
What happens if you unplug the KB before switching?
The keyboard and KVM are also used with the other notebook (DELL) where it works well. But your note let me think about the differences. There is also docking station between ThinkPad notebook and KVM. For the DELL notebook it is true as well, but the docking stations are different.
Maybe this is caused by docking station ?
Why would you think that lid has something to do with this? There is no change in lid position during this action.
When the notebook is not docked than the lid switch is fully ignored (I like it that way) I like to control suspend on my notebook myself by the power button.
It could well be, but not having a docking station myself, can’t confirm or otherwise.
Note: I have my systems set to “Do Nothing” when closing the laptop lid. This might be worth a test. The screen should still turn off anyway, when the lid is closed, but retain its state.
ETA: was typing as you were, so if already set that way, ignore this message.
About the lid close actions: I wonder if the dock has some setting? Like, if KB disconnected (same as switching it to another input i.e.machine), it triggers the same sort of action as a lid close.
It was a shot in the dark at first, but there are also ones for docking as well.
Also from the man page:
Another HandleLidSwitch= defaults to “suspend”. HandleLidSwitchExternalPower= is completely ignored by default (for backwards compatibility) — an explicit value must be set before it will be used to determine behaviour. HandleLidSwitchDocked= defaults to “ignore”. If the system is inserted in a docking station, or if more than one display is connected, the action specified by HandleLidSwitchDocked= occurs; if the system is on external power the action (if any) specified by HandleLidSwitchExternalPower= occurs; otherwise the HandleLidSwitch= action occurs.
I’ve owned many Thinkpads, but ones I have now, do not come with a docking port. So I can’t test this directly. But there is the package extra/evtest. If the docking is handled by libinput events, it should come up here.
You can run sudo evtetst, and see if an event comes up related to docking. This only lets you monitor them though (or query). But I’m curious if it is here.
So before I was just suggesting to change those logind.conf properties to ignore, then try it.
For logging this, is set the log level to debug, to log as much as possible. So get everything to the point of when you are about to make the KVM switch, and type:
Thank you for suggestion to look more into the /etc/systemd/logind.conf. I have modified these two options and all seems to be working fine now.
It was also interesting to see more information in journactl.
Now I like to thank you all. Not sure how to make it visible in this forums system. Even do not know what should i mark as solution post as @Molski and @BG405 helped