[systemd-devel] Antw: [EXT] Re: systemd killing processes on monitor wakeup?

[Ulrich Windl]

>>> Raman Gupta <rocketraman at gmail.com> schrieb am 29.01.2022 um 04:28 in Nachricht
<CADF5XCzXw-pGyoWUer1Ma0v-u-6+u+es9p_GrEvAF6FY9WykLw at mail.gmail.com>:
>> 
>> Try to set the systemd user instance's log level to 'debug'; I'm guessing
>> it's not that systemd kills processes directly but that something triggers
>> a 'systemctl stop' of the session .scope that they were in.
> 
> 
> Here are the logs at debug level with some annotations inline:
> 
> *<wake up at 21:57:30>*
> 
> Jan 28 21:57:34 edison plasmashell[3114743]: KCrash: Application
> 'plasmashell' crashing...
> Jan 28 21:57:34 edison plasmashell[3114743]: KCrash: Attempting to start
> /usr/libexec/drkonqi

[...]

This may not answer your question at all, but I think the real culprit is modern technology like display port, that allows the OS to detect when a monitor connects or disconnects.
I had real trouble with Windows 10 after using a new monitor and a KVM-switch: Every time I switched the KVM between two computers, Windows reset the graphics resolution to some "standard" (like 800x600), also moving all the windows on the desktop to the upper left corner. Besides that KVM switching is slower than ever. Back in the times of PS/2 and analog VGA connector I could switch twice within a second without a problem.

So for your problem I guess the application cannot really handle the monitor hotplug event.

Regards,
Ulrich