![]() Registered Member ![]()
|
The login window will only appear after suspend, when I set the 'screen locker setting' -> 'start automatically after' to x minutes, and the 'energy saving' -> 'suspend session' to a smaller amount of minutes. E.g. suspend after 30 minutes, lock screen after 31 minutes. Seems to be interfering. When you set lock screen earlier than suspend, you get no login screen. I hope that somebody can replicate. If you need more info, please ask (with instructions if you'd be so kind - brand new on KDE). |
![]() Administrator ![]()
|
If someone else can reproduce this behaviour on another distribution, using the latest version of KDE (4.12), then please file a bug report at bugs.kde.org.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
Since the last changes I made, the problem doesn't seem to recur. But it's perhaps too early for a definite conclusion as it has always been intermittent.
|
![]() Registered Member ![]()
|
Hello all,
I have a similar issue and was wondering whether it's the same as this. For me, it doesn't matter whether the screen is locked after suspend, timeout, by user action, either with or without using a screensaver. I get a black screen with just the cursor visible and no login dialog. Kscreenlocker_greet is running though. The only way to get out of this is to Ctrl-Alt-Backspace out of the session, or to kill ksmserver from another terminal, which also ends the session. At this time, the X server process was hovering around 95% CPU usage and ksmserver 42%. I'm using KDE 4.12.2 on Fedora 20: 3.13.4-200.fc20.x86_64. Edit: Upon closer inspection, my issue arises from a recent switch to the QtCurve widget theme. After switching back to Oxygen or any of the other themes, I can see the locker dialog again. The issue is also relieved by adding kscreenlocker_greet to QtCurve's transparency exceptions. See also Bug #314663. |
![]() Registered Member ![]()
|
The problem did recur on resume when suspend is trigerred by timeout, even without QtCurce but oxygen. It never happens with 'systemctl suspend' . Just to mention.
|
![]() Registered Member ![]()
|
Please see here:
viewtopic.php?f=111&t=119867 |
Registered users: Bing [Bot], Google [Bot], Sogou [Bot], Yahoo [Bot]