Hello,

On resuming from suspend in RAM, the login window is just missing. Typing blindly the password and validate fails. I have to restart KDM in a virtual terminal to get back the login window, very annoying.

Occured at least since KDE 4.11.6 on ARCH x86_64, now on 4.12.1.

A somehow similar reported bug : https://bugs.kde.org/show_bug.cgi?id=259601 , re-installing polkit does not help.

This happens when the host goes in suspend mode from KDE menu command. If it goes in suspend mode with 'systemctl suspend -i', the screen does not get locked on resume. Unfortunately, the primary user on that particular host won't suspend on a command line, nor with a keyboard shortcut that would run a script.

In the Power Savings module of systemsettings, there's an option to start a script after a defined delay, but nothing happens after that delay. And it's not clear whether this delay means user inactivity.

Any solution ? Or as a workaround, is there a way to prevent the screen to be locked on resume, when suspend is gone in from KDE menu or per Power Savings automatic mode?

Thanks.

"kcmshell4 screensaver", set "Screen locker type" to "Simple locker". Still an issue?

1. It was already set to 'Simple Locker'.

2. I changed it to 'Screen saver', then back to 'Simple Locker' and applied each time. Immediate resume does show the KDM login window. Have yet to see when it has been suspended overnight.

Thanks.

Still no luck, nothing prompts for the password on resume, screen is not black. Emptied KDE cache, reinstalled KDM... stiil the same.

Since the screen is apparently neither black nor unlocked - what do you see instead then?
Regular desktio, just you cannot use it?

I just see the wallpaper, not the desktop. The screen is still locked, it's just that there's no prompt to enter the password.

sounds more like you're either seeing the root window or a broken screenlocker.
There was a bug about a re-crashing greeter (iirc due to missing kdm parts)

You could move to VT1 (ctrl+alt+f1), login and run "ps ax > ps.v1", wait some seconds and then "ps ax > ps.v2" (this will write two files with running processes) and then check whether plasma-desktop and a greeter process is running and whether the greeter process changed its PID (ie restarted) between the two calls.

I'll do so next time it occurs and post the relevant results.

Hi,

The problem occured again. Here are the results of the above move :

11184 ? Sl 0:01 /usr/lib/kde4/libexec/kscreenlocker_greet
11184 ? Sl 0:01 /usr/lib/kde4/libexec/kscreenlocker_greet
11184 ? Sl 0:01 /usr/lib/kde4/libexec/kscreenlocker_greet


644 ? Sl 2:23 kdeinit4: plasma-desktop [kdeinit]
644 ? Sl 2:23 kdeinit4: plasma-desktop [kdeinit]
644 ? Sl 2:24 kdeinit4: plasma-desktop [kdeinit]

I waited 5 - 10 mins between each step. So it seems it's still the same processes running.

It's not a blocker issue, just annoying.

Thanks.

Is the wallpaper your custom one, or is it the default theme background?

Everything is default : Air theme, Elarun default wallpaper, Oxygen window decoration.

I see. To determine if the greeter background is being displayed properly, can you change your normal desktop background to something different? If Elarun is still displayed on the lock screen, even though no login window is displayed, then this narrows down the cause of the issues.

Changed the background to Horos. On an immediate suspend(via KDE Menu)/resume, the greeter wallpaper is Elarun and the password window is here. But this happened intermittently before this change. I'll report if the problem persists in the coming days.

I have the same issue. KDE Platform Version 4.11.5. OpenSuse 13.1.

Can you please provide the same diagnostic information? Does the lock window show as Horos or your normal desktop wallpaper? If your normal wallpaper is Horos, please change it for this check.