Library and components for secure lock screen architecture
https://www.kde.org
Library and components for secure lock screen architecture.
- Devel package for openSUSE:Factory
-
3
derived packages
- Links to openSUSE:Factory / kscreenlocker6
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout KDE:Frameworks/kscreenlocker6 && cd $_ - Create Badge
Refresh
Source Files (show merged sources derived from linked package)
| Filename | Size | Changed |
|---|---|---|
| _link | 0000000124 124 Bytes | |
| kde | 0000000222 222 Bytes | |
| kde-fingerprint | 0000000515 515 Bytes | |
| kde-smartcard | 0000000545 545 Bytes | |
| kscreenlocker-6.5.0.tar.xz | 0000186764 182 KB | |
| kscreenlocker-6.5.0.tar.xz.sig | 0000000488 488 Bytes | |
| kscreenlocker6.changes | 0000018134 17.7 KB | |
| kscreenlocker6.spec | 0000005157 5.04 KB | |
| plasma.keyring | 0000040445 39.5 KB |
Comments 2
Please consider making /etc/pam.d/kde-fingerprint and /etc/pam.d/kde-smartcard into separate packages, making them optional dependencies requiring fprintd-pam and pam_pkcs11 respectively. These only make sense if you have required PAM modules installed. Without those modules, we're getting authentication errors while unlocking user session despite password-auth was successful, which creates confusion
Whatever your issue may be, it's totally unrelated. Unlocking works fine even without these packages.
Obviously, if you authenticate with fingerprint or pkcs #11 module, you should have the mandatory packages installed.
fprintd-pam requires fprintd already and should already be installed if a device matching on the modules mentioned in https://build.opensuse.org/projects/hardware/packages/fprintd/files/fprintd.spec?expand=1 is present (lines 62-239)