On Thu July 11 2019 06:29:23 Michele Calgaro via trinity-users wrote: > if there are two kdesktop processes running, each will run a kdesktop_lock > process and the two processes will use the same lock file on the disk. The > "delete stale file" logs that you see are consistent with that. You need to > try to understand why two kdesktop processes are started together. Hi Michele, Agreed there should not be two kdesktops. However .xsession-errors shows them using different lock files: [2019/07/11 05:09:30.488] [tdecore] Deleting stale lockfile /tmp/tde-mgb/kdesktop_lock_lockfile.:0.0 [2019/07/11 05:09:30.489] [tdecore] Deleting stale lockfile /tmp/tde-mgb/kdesktop_lock_lockfile.:0.1 And yet they both decide these lockfiles are stale a couple dozen times per second. Not sure why the lockfiles refer to :0.0 and :0.1 when the two displays should be :0 (TDE) and :1 (not TDE). When I disable the second display TDE works fine with a single :0 lock file as expected. --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
