Some final notes on two X screen two TDE desktop screen flashing before I attempt to move on with life on a two monitor single xinerama X screen and single TDE desktop. Prior to the rapid fire stale lock file messages I can find none of the error texts from kdesktop/lock/main.cc in the .xsession-errors. This suggests to me that the desktop_lock processes are dying due to either (a) outside signals not properly blocked by broken signal masking, or (b) by return 12 (ENOMEM!?) or return 1 in response to a failed kill(0). Further diagnosis of this problem would be facilitated by emitting error messages before dropping out of main() with a return, and by expanding the stale lock file message with the pid of the reporter and the three elements of the lock file content. I tip my hat to Tim and the TDE developers who inherited a 3.5 codebase that frankly makes me lose sleep every time I attempt to comprehend it. --Mike --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-users-help@xxxxxxxxxxxxxxxxxxxxxxxxxx Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting