-----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 -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEjhl1z5vbYB3YbFTiKnW3yore1c8FAlxc4hgACgkQKnW3yore 1c/rQQ/+KkPtTo//HpkfR/yOXjf6boZS3CRx75tPjgtghinITQjXd63CCIIBT0Lx 5IcsWbf+wrINxkcYSzGeHB4uCHEod+VO8wn0Szea46fmzcjRTEI46I6GaG8reECe vKG/TP0LuhEsqvxGVLP/71R9wezNR+5tWQl30UdBGdLoV1ezUkQwJBIVyRfc/YiN P0FgLmtzYFYDPyxvUGwse3q0KqmrrqQqV5C6/4E5y6oZ3kzu6PLlVpfuTvAKk2h7 bC0WGOpk9S7w/ZVWAt5a3sJAFNdbxUlKQ6UGT1ZJvUEHaWy3Cnh3W8r4LP0FaKjF u8pfnPhj+Ek9V1Dcy3nyPyjKsn/nRVKxCHoxFI41QzB/5ruKE89uklzF/R87XieA jlKcABWI3C1FUlyPHiIeFEsjNpvPNfYAuL0asRU2KFZfgyrja9BoxPJnQXdfgRae yrXujJjrT5VwiR22/MYouxShTXdGmYD+4etJ1/2zOKYAXpQBcJD0TVgyoWIrXFqS +uRT/qKvMejtvaMwVpnrhEuV2XaOQcmf7r8fXXmwhcAtnv8PAXJa31N9pOSLVnM+ Q4C73RVf2Xce7x777ZMknwdDYMKFLG1AO6IvzVMh44NUx0YAV5wISrV0MFBpcVEo prvCUxwVBFH8JcdfV8l026xfjrrCwIZKGU18FAw3CahbdzSF9VU= =RgLK -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-devel-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-devel-help@xxxxxxxxxxxxxxxxxxxxxxxxxx Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
