i have pam stuff installed (for testing), but my system is USE=-pam. current kcheckpass ebuild doesn't properly respect this. # emerge -pv kcheckpass [ebuild R ] kde-base/kcheckpass-4.7.4 USE="(-aqua) -debug (-kdeenablefinal) -pam" 0 kB # emerge kcheckpass # scanelf -qN libpam.so.0 `qlist -e kcheckpass` libpam.so.0 /usr/lib64/kde4/libexec/kcheckpass
Created attachment 298463 [details] emerge --info
Created attachment 298465 [details] kcheckpass build.log
Yep, can confirm this even in 4.8.0. Why it's happening however is still a cmake mystery...
Created attachment 300109 [details, diff] kdebase-4.8.0-pam-optional.patch The problem is that FindPAM and UnixAuth are being read from the live system, ignoring the patched versions in the build directory. For some reason, the custom CMAKE_MODULE_PATH is not being respected for includes. Attached is an updated kdebase-4.0.2-pam-optional.patch that fixes this issue. This also fixes bug #398331. Based on kdebase-4.0.2-pam-optional.patch usage it initially looks as if kscreensaver is affected. However, I cannot find any evidence that kscreensaver actually links against PAM in any way.
Upstream is interested in a proper fix, please file a review request at git.reviewboard.kde.org
Added to reviewboard: https://git.reviewboard.kde.org/r/103818/
*** Bug 398331 has been marked as a duplicate of this bug. ***
Thanks all. Fixed in =kde-base/libkworkspace-4.7.4-r2 and =kde-base/libkworkspace-4.8.0-r1. The depending pam related packages kde-base/kdm and kde-base/kcheckpass have revision bumps also.