On Sat, 22 Dec 2012 15:29:22 -0800 Thomas Taylor wrote:

On Sat, 22 Dec 2012 13:06:45 -0500 Patrick Shanahan wrote:

...

For some *unknown* reason my screen now locks when the screen-saver in initiated and will not unlock but to a black/blank unresponsive screen. Checking the screen-saver settings, systemsettings, revealed the "screen-saver" is now a "screen locker" and the "simple locker" was selected, *not* be me. Previous setting was "screen-saver". wtf!

The only recovery I find is *rebooting*.

Unexceptable! One would think I was running a version of windoz.

And, the "Screen locker type: Simple locker" DOES NOT WORK for me.

Testing new versions is becoming VERY difficult to the point of wasted effort.

A dyed in the wool openSUSE user for years who is becoming disenchanted!

Similar behavior for me under 12.3-M2 and KDE. Every time I reset the screen locker to "screen saver" without password it gets automatically set back to "simple screen locker" with password.

If I can narrow it down a bit by looking at the logs I'll file a bug report.

Tom

Bug 312088 filed with KDE Tom -- “What we do for ourselves dies with us. What we do for others and the world remains and is immortal.” Albert Pine -- Tom Taylor - retired penguin AMD Phenom II x4 955 -- 4GB RAM -- 2x1.5TB sata2 openSUSE 12.2 x86_64 openSUSE 12.3-M2 x86_64 KDE 4.7.2, FF 7.0 KDE 4.9.90, FF 17.0.1 claws-mail 3.8.0 registered linux user 263467 linxt-At-comcast-DoT-net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Thomas Taylor [12-22-12 18:31]: [...]

Similar behavior for me under 12.3-M2 and KDE. Every time I reset the screen locker to "screen saver" without password it gets automatically set back to "simple screen locker" with password.

also kde, guess I neglected to say that. I had a large update today that didn't change the menu, systemsettings/display, but still requires passwd after screen saver is invoked. 4.9.95-1.2.x86_64

If I can narrow it down a bit by looking at the logs I'll file a bug report.

Need any info, holler. I usually wait until someone more closely involved comments or requests but I guess it wouldn't hurt. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Raymond Wooninck [12-23-12 03:44]:

On Saturday 22 December 2012 13:06:45 Patrick Shanahan wrote:

...

For some *unknown* reason my screen now locks when the screen-saver in initiated and will not unlock but to a black/blank unresponsive screen. Checking the screen-saver settings, systemsettings, revealed the "screen-saver" is now a "screen locker" and the "simple locker" was selected, *not* be me. Previous setting was "screen-saver". wtf! I assume here (also based on newer emails that we are talking here about the KDE Desktop.

Yes, I was remiss for omitting that :^(

With the upcoming 4.10, the original screenlocker was rewritten and made part of plasma itself. As you can find on the KDE announcement page:

http://www.kde.org/announcements/announce-4.10-rc1.php

The main change is that it is no longer a separate process and therefore can no longer be killed. This to increase the security.

The screen locker will kick in even when the setting is "Screen Saver". At this moment you will always require to enter a password. This was reported with https://bugs.kde.org/show_bug.cgi?id=310871.

With regards to the setting in the system-locker. Is this a fresh install or an update of an existing installation ?

...

And, the "Screen locker type: Simple locker" DOES NOT WORK for me.

The question is if this is a general issue with more users ?

unknown.

...

Testing new versions is becoming VERY difficult to the point of wasted effort.

You are aware that you are running Factory, right ? These things can happen and this is also one of the main reasons why we are asking users to test so that these issues can be resolved before the new openSUSE release is being released to the general public.

Frustration has taken over, sorry. Thanks for the explanation. I did not see the announcement here and don't subscribe to kde.org. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org