11 Jul
2019
11 Jul
'19
2:44 p.m.
-----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
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEjhl1z5vbYB3YbFTiKnW3yore1c8FAl0nS2MACgkQKnW3yore
1c8BBQ//eomE4ebwpftE3wLLdCQDV2fVFe6nsZje4klQD23kk/TyN9oQ6dt0WJcv
zivbU7Vv6qLdRcqFoaviT+cd6xG1+yPBvjgGq9kmy2HIJpx+OwmMyCMDyg55Uupb
icAeafDLwC8lzfWCx6PIJ+fkSPAHcvrm+0vRTNLkXpZfVBhRpIfmDzWGnIyNqrl9
HxqbRaXe3I7OtupYMk6VQTa6xnYNum+PxlL0dtSzpUyVmvdA86cnS58ZMwqj3qkd
yPlgdYJt3dOdcaLPdibnJHIfI2Lf3NlUx9gkzONGLvipssQPStg2sXwcpPkLFccd
TT6y3cSEAP2Lz0pcN6vRe/uSWDna4hThsM+2t5MaAPjvocLf7WOikieo5K4ADtRy
dR2tfE2P0PrKDSEeS9BpnFpNkkGVOcTT3ZlpZthlSAGpnXAoLQgTv7BKY8FDNIxG
IByNCs8Oi5uOBgS3t1+eW3bu16vJpFw52hO+JI+oiD6v1h2DDldJtO/wgi9c2ay/
yjFruaWBpoAY/SkrlpU2+Fp7wH+akUc92sHUuUrQ5xkrIRTAJYAPUlo2kYFaVvy+
Z5M+sVpxfYhHyJMVot3M1jIEyq2KZWZvJ/LTCfZfyyV16tAmlITX0S+zpXdNYfct
eD56NVVi5zagKuoSu0H11Fz5DJ0fW2PQqT/Qpeu+ntOP28gl5/g=
=W3cE
-----END PGP SIGNATURE-----