-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
I'm digging it right now, but a simple adding of the DISPLAY won't fix it for me because as for now there are actually 2 instances for each of two screens (4 in total, see the bug for details) are fighting over control. Having a squared-number-of-screen kdesktop_lock running all the time just looks messed up. Also they conflict with each other when locking a desktop from a «wrong screen».
As this bug results in kdesktop/kdesktop_lock eating CPU and going
unresponsive; might I humbly request that the fix is incorporated in the next possible/dev version.
I have not yet looked into the code in detail, but the kdesktop_lock is responsible for locking the screen. AFAICR from previous work on tdm+locking, kdesktop_lock use one file to determine the active lock process and eventually kill stale processes before doing his things. If we have multiple screens, we can not have multiple kdesktop_lock associated with each screen, for the simple reason that we can not have a screen locked and the other not locked. If we have multiple *different* user sessions, the lock files will live in different folders (again AFAICR) and they should not conflict. If we have multiple sessions from *the same* user, the different lock processes will conflict over the lock file and this will probably cause issues.
just my 2 cents, until I can find the time to look at this in more details.
Cheers Michele