Bug 561660 – kde-plasma/plasma-workspace should depend on kde-base/kcheckpass

• Status: RESOLVED INVALID
• Product: Gentoo Linux

[Description Mihai Donțu 2015-09-27 19:25:59 UTC]

I removed kde-base/kcheckpass thinking is was left behind by the old kde4 and also because nobody required it, but I soon came to realize that I can no longer unlock my screen.

Reproducible: Always

Steps to Reproduce:
1. emerge -C kde-base/kcheckpass
2. lock your screen (CTRL+Alt+l)
3. try to unlock
Actual Results:  
Screen unlocking fails


Expected Results:  
Should unlock the screen

[Comment 1 Andreas Sturmlechner 2015-09-27 19:35:40 UTC]

I do not have kde-base/kcheckpass installed and can unlock perfectly fine. Would seem strange for a plasma-5 package to depend on old kde4-stuff anyway.

Is this really about kde-plasma/plasma-workspace or is this in fact still kde-base/plasma-workspace you are working with?

[Comment 2 Mihai Donțu 2015-09-27 20:21:04 UTC]

Interesting. I use kde-plasma/plasma-workspace 5.4.1

[Comment 3 Michael Palimaka (kensington) 2015-09-28 11:34:16 UTC]

emerge --info please. Is there anything interesting in ~/.xsession-errors, and do you have /usr/lib*/libexec/kcheckpass?

[Comment 4 Mihai Donțu 2015-09-28 12:47:39 UTC]

Created attachment 413198 [details]
emerge --info

I have attached the output of 'emerge --info'.

$ file /usr/lib*/libexec/kcheckpass
/usr/lib64/libexec/kcheckpass: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, stripped
/usr/lib/libexec/kcheckpass:   ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, stripped

[Comment 5 Mihai Donțu 2015-09-28 12:51:59 UTC]

Nothing that appears to be connected to this issue appears in '.xsession-errors'. When I lock-unlock all I see is:

lock called
Lock window Id:  25165837
CreateNotify: 25165837
CreateNotify: 69206018
CreateNotify: 69206020
CreateNotify: 69206024
CreateNotify: 69206026
Skipped method "moduleDeleted" : Pointers are not supported: KDEDModule*
kcm_keyboard: Fetched layout groups from X server:      layouts: ("ro", "us")   variants: ("", "")
kcm_keyboard: Fetched layout groups from X server:      layouts: ("ro", "us")   variants: ("", "")
CreateNotify: 69206027
MapNotify: 69206027
MapNotify: 25165837
CreateNotify: 69206031
CreateNotify: 52498002
UnmapNotify: 39845933
Unknown toplevel for MapNotify
UnmapNotify: 31467669
UnmapNotify: 69206027
UnmapNotify: 69206027
CreateNotify: 69206033
QXcbConnection: XCB error: 3 (BadWindow), sequence: 45133, resource id: 69206033, major code: 18 (ChangeProperty), minor code: 0
Grab Released
QXcbConnection: XCB error: 3 (BadWindow), sequence: 45153, resource id: 25165837, major code: 2 (ChangeWindowAttributes), minor code: 0

[Comment 6 Michael Palimaka (kensington) 2015-09-29 17:57:52 UTC]

and it works again immediately after reinstalling kde-base/kcheckpass?

[Comment 7 Mihai Donțu 2015-09-30 00:55:47 UTC]

Yes.

I decided to take a look at the sources and see what's going on. I saw that kde-plasma/plasma-workspace already installs a kcheckpass, just in a different directory:

$ equery b kcheckpass
kde-base/kcheckpass-4.11.22 (/usr/lib64/kde4/libexec/kcheckpass)
kde-plasma/plasma-workspace-5.4.1 (/usr/lib64/libexec/kcheckpass)

I removed kde-base/kcheckpass and re-emerged kde-plasma/plasma-workspace (just in case). Lock/unlock. Seems to work fine now.

I don't know what happened before. :-|

[Comment 8 Michael Palimaka (kensington) 2015-10-08 14:22:56 UTC]

Thanks for your feedback. Since it's working again, I guess we can call this a heisenbug for now.