![]() ![]() ![]() The KR412 repo does contain a newer version now (4.11.6 got released together with KDE 4.12.2, and will be released as update for 13.1 as well), but AFAIK there was absolutely no change regarding the screen locker.Īnd it should in fact work with 4.11.4 as well. The screen locker is part of kdebase4-workspace, and there is no 4.12 version of that. maybe I want wait a update for 4.11 version with disable suspend options The default 13.1 settings had it turned on, I just decided I did not want the screen locker activated.īug seems to date back to Dec 2013, which is before I upgraded,…? I sort of recall that the “Lock on resume from STR” did work when I first upgraded to 13.1 from 12.3. OK, reread thread and bug again and agree with wolfi. My experience with 4.12 has been good, but as always, others might have a different experience Switch to KDE 4.12 using the KDE Upstream Repos (Core and Extras) where the bug does not appear (for me).Stay with KDE 4.11 and turn OFF “Lock Screen on Resume”. ![]() So it would appear alakulihal has two options until the bug is fixed I moved to KDE 4.12 immediately on upgrade to 13.1(was running 12.3/4.12.0 prior) so apparently this bug was fixed in KDE 4.12 Rereading the bug a third time, it specifies the 4.11 branch. ![]() I put the system to sleep, then resume and all works as expected( I get the unlock dialog window and it works). But not recently with 13.1.Įxperiment: Since my recollection and experience does not match alakulihal’s, I turned “Lock Screen on Resume” back on on my HPDV7 Laptop. Oh, and he already wrote that he uses KDE 4.11.5.įYI, I have in the past had resume from STR fail with the wallpaper displayed, the mouse cursor active but desktop otherwise useless without a full restart of kdm. The screen locker uses the default desktop wallpaper as background image. He says he sees the “desktop wallpaper” and the mouse cursor. Sometimes proprietary video drivers are a problem - what video device and driver are you running?Īs a general statement, I have found that STR works well on several different hardware platforms running 13.1, but that is no guarantee it does without help(tweaks) on yours.Any past history with your hardware - sleep OK with other Linux or Windows?.Are you sleeping (STR) or hibernating (STD) your system? If STD, is your swap partition at least as large as your installed RAM?.You can also execute “dmesg” in a console window, look for suspend/resume diagnostic messages.Are pm-utilities installed? If so, have to reviewed /var/log/pm-suspend.log for suspend/resume errors messages?.To help you with a failure to resume after suspend, we will probably need at least the following info from you: In post 13 of the thread I summarize how I removed pm-utilities and verified that they were no longer needed. My problem was different than yours, but the forum discussion revealed that pm-utilities is on the way out and the kernel and Upower will take over suspend/resume management in the future. You might benefit from reviewing THIS THREAD I realize we my be operating in 2 or three languages here (with translation), the details here can be difficult to identify. However, what you are experiencing sounds to me like a failure to fully return from resume, after suspend. You do not get a “login” screen or dialog. If you get a screen locker, your password will unlock it. To be specific, When your system correctly returns from suspend, you get a Screen Locker or not, depending on your settings. I will use slightly different terminology here, because it sounds to me like you are not actually returning from suspend fully, and that your screen is “frozen” (my terminology), not “locked” which to me implies that the screen locker has been activated. Ok, so apparently the screen is locked, but there’s no password dialog? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |