Summary: | kde-plasma/plasma-workspace should depend on kde-base/kcheckpass | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Mihai Donțu <mihai.dontu> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | emerge --info |
Description
Mihai Donțu
2015-09-27 19:25:59 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? Interesting. I use kde-plasma/plasma-workspace 5.4.1 emerge --info please. Is there anything interesting in ~/.xsession-errors, and do you have /usr/lib*/libexec/kcheckpass? 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
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 and it works again immediately after reinstalling kde-base/kcheckpass? 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. :-| Thanks for your feedback. Since it's working again, I guess we can call this a heisenbug for now. |