23 Feb
2020
23 Feb
'20
09:02
David C. Rankin wrote:
Just guessing here, but it looks like a fsck'ed screensaver that is threaded using mprime to compute some of the graphics and kdelocker for the display and there is a race condition (likely a screwed up mutex) that has caused the whole scheme to explode.
mprime is independent, not related to kscreenlocker. I guess I can disable the locking, although I would prefer not to. Nobody has any suggestions about what to do ? (other than using xscreensaver instead). -- Per Jessen, Zürich (12.5°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org