Impossible to unlock

Every keyboard input or mouse movement on the lock screen currently triggers "wrong username or password".

If you get stuck it's possible to unlock through a different TTY or by SSH through the following command: ck-unlock-session Session2, alternatively dbus-send --system --print-reply --dest="org.freedesktop.ConsoleKit" /org/freedesktop/ConsoleKit/Session2 org.freedesktop.ConsoleKit.Session.Unlock, where Session2 may have to be adjusted to according to your system.

changed the description

changed the description

added 1 deleted label

added 1 deleted label

added bug help labels

Hi @advesperascit, were you able to fix this with your recent commit? Or did that not do the trick? If not, do you think this breakage has something to do with KDE6?

Hi @Obarun, I just noticed that obarun's consolekit2 is a little behind up-upstream. Is that by necessity? BTW, looks like ConsoleKit2 is going to have a major release soon.

I wonder, @advesperascit, if building ConsoleKit2 against the latest release or git commit might have some effect on your problem? I've never run KDE on Obarun before, but I'm willing to try it out in a VM if that will help with testing things out. Best, nfg

Hi @nfg, no, this package is still broken. I've made no commit since making this issue, but the last commit fixed an issue with the screen turning black when locked (repeatedly and insistently) which was caused by me removing the qt5-tools dependency. Upgrading consolekit2 is worth a shot. I didn't see any similar issues reported in the official places, so I'd assume it's either a dependency/build problem with non-systemd systems or a bug only affecting such builds. Might be worth looking at FreeBSD to see if they have got it working? I've got a laptop with a dated install somewhere..

Don't feel forced to try solving this on my account. I can live without locking my screen, and if I need to lock it I can use the workaround to crawl in through the trunk of the metaphorical car!

@nfg, the last release of consolekit is 1.2.6 on their github site which is the release available on obextra repo. This means that the same package version for consolekit was used with the previous version of kscreenlocker as well as with the new version of kscreenlocker.

@advesperascit, do you have some logs to share?

Also, if some guys can test on their machine it could be great to see if this bugs affect all users.

@Obarun, it looked to me that the version in obextra is 1.2.4. Am I looking in the wrong place?

Yeah, you're right, i changed on my local folder but forgot to push the changes. I will update it

@advesperascit, Consolekit was updated to the lastest version.

Tested after full system upgrade and kscreenlocker rebuilt with newest ConsoleKit but unfortunately the problem persists. I run Obarun with Plasma on both my desktop and an old laptop, both systems are affected.

I can't find any relevant logs under /var/logs and ~/.local/share/sddm/xorg-session.log has nothing related.. Do you know where/how to find any other relevant logs? /usr/libexec/kscreenlocker_greet --testing does not yield any interesting output either.

assigned to @advesperascit

unassigned @advesperascit

The pam files were not put to install in the package section. I think this is resolved

closed