-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
Since installing RC2 I have twice experienced
"lockups" upon
unlocking the screen. I have never experienced these before.
Once "locked up" the mouse has no effect and there is almost
no keyboard effect. However numlock and capslock keys still
flip their indicator LEDs and ctrl-alt-Fn can be used to
switch to another console.
First time: as root I restarted tdm-trinity. I didn't notice
if there were any error messages. When Trinity restarted it
was on a new console - alt-F8 instead of alt-F7.
The second time: as root I stopped tdm-trinity. I noticed
error messages saying the stop had failed. I killed -9
kdesktop_lock, stopped tdm-trinity again, and started it.
This time Trinity started on the expected console.
I'd appreciate any suggestions of any additional steps I
should take to help diagnose the problem if it happens again.
--Mike
This was a regression that snuck into RC2; it was fixed shortly afterwards
and will not be a problem for R14 final. If you can, installing the
tdebase packages (specifically the kdesktop-trinity package) from the
nightly builds repository will resolve the issue.
Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iFYEARELAAYFAlSB0x8ACgkQLaxZSoRZrGENnADcDgSMKt6rFatqPiv6AeAa0Ht2
Yq7YumlEKCdwvQDfYjtdCImhyP+3QtE5wZo2v7dMjS7Z7N4Tla1YIg==
=d6Lw
-----END PGP SIGNATURE-----