-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
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
Hi Mike, let me be more specific. There should be one kdesktop in total and one kdesktop_lock per display I think. The last part of the name is given by the DISPLAY variable, like :0.0 and :0.1. So :0.0 and :0.1 are not competing with each other, but rather with older :0.0 and :0.1.
Another possibility is that kdesktop_lock crashes: in this case kdesktop will respawn the process and once again you would see the delete stale thing.
Cheers Michele