Per Jessen wrote:
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).
To disable the screenlocker, I went into System Settings->Display&Monitor->Compositor - where I see a message telling me that "openGL has crashed kwin in the past and has been disabled". I re-enabled and restarted - sure enough, kwin crashes on startup, a segfault. Any suggestions? I'm beginning to think I might go back to Leap, I just need a working system - that can be screenlocked without gobbling up a CPU :-) -- Per Jessen, Zürich (0.0°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org