[SOLVED] KDE lockscreen cannot be unlocked?

gehzumteufel · 2015-04-30 06:34:25

@archqt: I think I found what you're referring to as the dependency. Did you upgrade your kernel? If you're on 4.x, you will need to downgrade that too. Along with the linux-headers and the nvidia stuff. All at the same time.

MatejLach · 2015-04-30 11:55:47

Works for me with nvidia 349.16-2.

gehzumteufel · 2015-05-01 15:22:40

That did not solve things for me when I tried it, but I will try again.

MatejLach · 2015-05-01 16:07:55

gehzumteufel wrote:

That did not solve things for me when I tried it, but I will try again.

That's interesting...I wonder if it's actually the same problem or a similar one we've been experiencing...

archqt · 2015-05-01 18:01:14

Thanks for everything but when i look at the output of journalctl i can see some error with lockscreen and i have this

mai 01 12:32:31 localhost kscreenlocker_greet[831]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:24: TypeError: Cannot read property 'userName' of null
mai 01 12:32:31 localhost kscreenlocker_greet[831]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreen.qml:167: TypeError: Cannot read property 'showPassword' of undefined
mai 01 12:32:31 localhost kscreenlocker_greet[831]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreen.qml:192: TypeError: Cannot read property 'ButtonLabel' of undefined

It looks more a problem of a program than one with a driver (at least for me)

It is reported here
https://bugs.kde.org/show_bug.cgi?id=344567

Last edited by archqt (2015-05-01 18:03:33)

tbleiker · 2015-05-04 17:55:01

Same problem as described above after updating system (nvidia 349.16-1, kernel 4.0.1, kde stuff 5.3). I am back on nvidia 346.59-1 and kernel 3.19.3 (everything fine here). I am not in a bug-hunting-mood right now

MatejLach · 2015-05-04 18:46:41

For me, nvidia 349.16-2 solved the problem, however seeing how many people still have this problem, maybe I should remove the [SOLVED] tag, so that may be more people will have a crack at this?

archqt · 2015-05-15 09:44:45

Hi,
it worked for me now with the update so i think the Solved can stay.
Sincerely

MatejLach · 2015-05-15 10:19:53

archqt wrote:

Hi,
it worked for me now with the update so i think the Solved can stay.
Sincerely

That's great!

tbleiker · 2015-05-22 18:32:51

Does still not work for me (all packages updated) sddm-greeter crashes on login: sddm-greeter PID: 493 Signal: Segmentation fault (11)

gehzumteufel · 2015-05-22 20:43:35

Same, but the KDE developer who would work on it refuses to investigate. It's pretty shitty. In my bug report, he even gave some stupid childish response, which really pissed me off.

aikidokatech · 2015-05-25 01:59:54

I just switched back to trying out Plasma on my box with an Nvidia card. I am experiencing the same issue. I have a GTX960 using nvidia beta 352.09-1, kernel 4.0.4 and plasma 5.3. For the time being I've switch off KDE as I do not have time to play with driver and kernel versions. Might try that in a few weeks.

luke_dirtwalker · 2015-06-01 21:05:28

aikidokatech wrote:

I just switched back to trying out Plasma on my box with an Nvidia card. I am experiencing the same issue. I have a GTX960 using nvidia beta 352.09-1, kernel 4.0.4 and plasma 5.3. For the time being I've switch off KDE as I do not have time to play with driver and kernel versions. Might try that in a few weeks.

Same here with 352.09-1 (non-beta), 4.0.4 kernel and plasma 5.3

EDIT: FIXED by updating intel microcode.

Last edited by luke_dirtwalker (2015-06-03 07:05:29)

tbleiker · 2015-06-08 16:29:46

SOLVED! Fixed it by updating intel microcode!

IMPORTANT: You have to make sure that the package intel-ucode is installed! If you have not, a check will tell you that the micorode is up-to-dat!

MatejLach · 2015-06-08 18:51:05

Great!
Updated the top post for visibility!

pixel8r · 2015-06-10 23:57:31

Unfortunately I'm stuck on 340xx due to having an older nvidia card (Quadro NVS 3100M / GT218, Dell Latitude E6510), so upgrading to 349.16-2 is not possible.
This issue is frustrating and happens every time. When I attempt to lock the screen it hangs (kwin_x11 and/or klockscreen_greet goes to 100% cpu), and then about 5 mins later the lockscreen finally shows up, after which everything continues normally. (Is it the same bug?)

It happens on 340.76 (the current latest 340xx driver) and I've also tried 340.65 and it happens with that version as well. It's possible that this bug has been present for ages but has only been triggered recently via changes in plasma 5.1 or 5.2 and later.

I've tried the nouveau driver and that does not hang on lockscreen, but has other issues of its own relating to display corruption. I enabled automatic fan control and also tried reclocking to use the highest clock speed but that didn't fix the corruption issues.

So again I'm trying the nvidia driver, going back to even earlier versions.

Does anyone know if this bug has been raised on the nvidia end? Is there a link? Hopefully they'll provide a fix for 340xx.

Last edited by pixel8r (2015-06-10 23:58:30)

aikidokatech · 2015-06-20 00:33:33

Great news! I decided to do all my updates and try the microcode install. After hours of fighting with the results of the upgrade I got to give it a try. Now I can finally unlock Plasma!

garak · 2015-07-15 20:05:37

Problem persists on my clean install for nvidia 352.21-2 even though I have the Intel microcode installed.

Journalctl still shows me:

 systemd-coredump[4871]: Process 4859 (kscreenlocker_g) of user 1000 dumped core.

Interestingly, there are a few other programs that also dump core in a similar manner:

systemd-coredump[789]: Process 780 (systemsettings5) of user 1000 dumped core.
systemd-coredump[794]: Process 790 (nvidia-settings) of user 1000 dumped core.
systemd-coredump[607]: Process 499 (ksplashqml) of user 1000 dumped core.

I've also had Truecrypt dump core on the gui-dialog for sudo.

Graphics card is a GeForce GTX 750 Ti. I have not downgraded to 346.59 and would like to avoid doing so if possible.

Just as pixel8r asked: Are there bug reports in existence with kde or NVIDIA?

MatejLach · 2015-07-15 20:24:55

Sorry to hear that!
There definitely was/is a bug report for KDE, only I can't find the link now :-(
Not sure about NVidia.

It may be a good idea to get a bug report into the KDE bugzilla if you can't find an active one.
Worst thing that can happen is that it'll be made a duplicate.
Same for NVidia.

Last edited by MatejLach (2015-07-15 20:28:56)

garak · 2015-07-16 20:48:40

Thanks for your reply.

Assuming that I'm at this point not the only person who still has this problem, I want to share some further things I've found out:

I've just updated to Kernel 4.1.2-2-ARCH and Nvidia drivers 352.21-4, but the problem persists, unchangedly.

Upon further inspection of journalctl I found the following types of errors interspersed with everything else:

 
Jul 17 00:21:36 central kwin_x11[641]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 17774, resource id: 37749994, major code: 18 (ChangeProperty), minor code: 0
Jul 17 00:21:36 central kwin_x11[641]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 17776, resource id: 37749994, major code: 3 (GetWindowAttributes), minor code: 0
Jul 17 00:21:36 central kwin_x11[641]: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 17777, resource id: 37749994, major code: 14 (GetGeometry), minor code: 0
Jul 17 00:21:36 central kwin_x11[641]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 17780, resource id: 37749994, major code: 3 (GetWindowAttributes), minor code: 0
Jul 17 00:21:36 central kwin_x11[641]: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 17781, resource id: 37749994, major code: 14 (GetGeometry), minor code: 0

Now, googling a bit for those types of errors, I've found a few forum threads for another issue with current NVIDIA drivers and kde/plasma5 (bear with me, this is indeed relevant). Herein, the screen becomes filled with triangles and memory garbage upon switching back from a tty or changing resolution. It is so far unclear if this affects only dual-head setups or if there are deterministic conditions (it is non-deterministic for me and I'm running dual-head).

As you've probably already guessed, I've noticed that my machine unfortunately also suffers from this glitch.

https://bbs.archlinux.org/viewtopic.php?id=197567
https://bbs.archlinux.org/viewtopic.php?id=184439&p=33

Now, this gives one piece of valuable information: The underlying cause of the lockscreen-issue for me (and presumably others for whom installing the Intel microcode package did nothing) is probably also the cause of other display issues in Kde/plasma5 Nvidia setups that are popping up here and there.

Since I'm not sure how to proceed further, I'll try my luck with nouveau for now. If anybody has suggestions, I'm all ears.

garak · 2015-07-16 21:45:11

Fixed

Is cursing allowed on here? Because I'm an f-ing idiot.

Turns out that it is not sufficient to install the intel microcode packages but you also have to modify your bootloader so that the microcode is actually used.

For future reference, as a grub user, after installing intel-ucode, run

grub-mkconfig -o /boot/grub/grub.cfg

and

mkinitcpio -p linux

Only then will the microcode actually be used.

MatejLach · 2015-07-17 09:50:23

Glad to hear that you were able to solve it.

pixel8r · 2015-09-17 04:28:07

pixel8r wrote:

Unfortunately I'm stuck on 340xx due to having an older nvidia card (Quadro NVS 3100M / GT218, Dell Latitude E6510), so upgrading to 349.16-2 is not possible. <snip>

After running with the nouveau driver for months due to this issue, I decided to try the nvidia-340xx driver again. Unfortunately the lockscreen hang was still there.

However, I decided to try some other things as well. I created a new user and logged into KDE under that user, so it would create a fresh KDE config, and there was no lockscreen issue.

So then I moved most of my KDE config from ~/.config/ into a backup location and logged in again under my regular user, and the lockscreen hang is gone! Of course it then took me all morning to reconfigure my settings etc but I'm happy to have found a solution that worked.

I don't know exactly which part of the kde config was to blame. If in doubt, move your .config directory to another location and copy back anything you can't recreate from scratch. I only moved things that were kde-related, and that worked.

ponyitomi · 2021-09-03 20:30:01

I have the same issue. After the screen is locked, I am unable to login, however selecting switch user, and starting a new session, lets me in.

I think it is a bug, which is already solved but none of the arch updates seem to solve my problem (or contain?) this fix.

https://bugs.kde.org/show_bug.cgi?id=380491

This is the solution:
https://phabricator.kde.org/D6091

I also have some permission elevation problem that might be linked to it, that is if I start partitionmanager, kde requires admininstrative privileges, and with a sudo or root pw I get an authentication error.

V1del · 2021-09-04 10:14:46

It is "extremely" unlikely that you still have the same issue as was discussed 6 years ago and additionally unlikely that a fix from 4 years ago didn't yet get released.

Likely your setup is broken, create a new thread, include details of your system and user setup, and post a

sudo journalctl -b

in [ code ] [ /code ] tags without the spaces. And also by which means you are logging in and starting plasma.

Closing this old thread.

Last edited by V1del (2021-09-04 10:16:05)

Arch Linux

#26 2015-04-30 06:34:25

Re: [SOLVED] KDE lockscreen cannot be unlocked?

#27 2015-04-30 11:55:47

Re: [SOLVED] KDE lockscreen cannot be unlocked?

#28 2015-05-01 15:22:40

Re: [SOLVED] KDE lockscreen cannot be unlocked?

#29 2015-05-01 16:07:55

Re: [SOLVED] KDE lockscreen cannot be unlocked?

#30 2015-05-01 18:01:14

Re: [SOLVED] KDE lockscreen cannot be unlocked?

#31 2015-05-04 17:55:01

Re: [SOLVED] KDE lockscreen cannot be unlocked?

#32 2015-05-04 18:46:41

Re: [SOLVED] KDE lockscreen cannot be unlocked?

#33 2015-05-15 09:44:45

Re: [SOLVED] KDE lockscreen cannot be unlocked?

#34 2015-05-15 10:19:53

Re: [SOLVED] KDE lockscreen cannot be unlocked?

#35 2015-05-22 18:32:51

Re: [SOLVED] KDE lockscreen cannot be unlocked?

#36 2015-05-22 20:43:35

Re: [SOLVED] KDE lockscreen cannot be unlocked?

#37 2015-05-25 01:59:54

Re: [SOLVED] KDE lockscreen cannot be unlocked?

#38 2015-06-01 21:05:28

Re: [SOLVED] KDE lockscreen cannot be unlocked?

#39 2015-06-08 16:29:46

Re: [SOLVED] KDE lockscreen cannot be unlocked?

#40 2015-06-08 18:51:05

Re: [SOLVED] KDE lockscreen cannot be unlocked?

#41 2015-06-10 23:57:31

Re: [SOLVED] KDE lockscreen cannot be unlocked?

#42 2015-06-20 00:33:33

Re: [SOLVED] KDE lockscreen cannot be unlocked?

#43 2015-07-15 20:05:37

Re: [SOLVED] KDE lockscreen cannot be unlocked?

#44 2015-07-15 20:24:55

Re: [SOLVED] KDE lockscreen cannot be unlocked?

#45 2015-07-16 20:48:40

Re: [SOLVED] KDE lockscreen cannot be unlocked?

#46 2015-07-16 21:45:11

Re: [SOLVED] KDE lockscreen cannot be unlocked?

#47 2015-07-17 09:50:23

Re: [SOLVED] KDE lockscreen cannot be unlocked?

#48 2015-09-17 04:28:07

Re: [SOLVED] KDE lockscreen cannot be unlocked?

#49 2021-09-03 20:30:01

Re: [SOLVED] KDE lockscreen cannot be unlocked?

#50 2021-09-04 10:14:46

Re: [SOLVED] KDE lockscreen cannot be unlocked?

Board footer