KDE

5412 readers

120 users here now

KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.

Plasma 6 Bugs

If you encounter a bug, proceed to https://bugs.kde.org/, check whether it has been reported.

If it hasn't, report it yourself.

PLEASE THINK CAREFULLY BEFORE POSTING HERE.

Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.

founded 1 year ago

MODERATORS

carlschwan@lemmy.kde.social

Bro666@lemmy.kde.social

herzenschein@pawb.social

Aniqakhokhar@lemmy.kde.social

KDE 6 fingerprint unlock (lemmy.world)

submitted 9 months ago* (last edited 5 months ago) by RegalPotoo@lemmy.world to c/kde@lemmy.kde.social

6 comments fedilink hide all child comments

The KDE 6 announcement says that

On prior versions you chose between either password or fingerprint authentication for the lockscreen. In Plasma 6, both are supported at the same time.

I've updated my Neon install, what do I need to do to enable this? I've set up a fingerprint through the user settings, but when the screen is locked I still have to use my password to unlock - there isn't a prompt, and touching the reader doesn't seem to do anything

Edit: follow up on an old post in case someone stumbles across it - I needed to install libpam-fprintd

you are viewing a single comment's thread
view the rest of the comments

[–] RegalPotoo@lemmy.world 2 points 9 months ago (1 children)

Empty password doesn't prompt for a fingerprint, and I thought that was the old hacky workaround for Plasma 5 that Plasma 6 was supposed to have fixed?

[–] Rustmilian@lemmy.world 2 points 9 months ago* (last edited 9 months ago) (1 children)

Even if it is, I'm unable to find any other solution. It's at least worth a shot.
Do be sure to report this bug in the meantime, it's likely related to pam &/or SDDM.

[–] RegalPotoo@lemmy.world 1 points 9 months ago

Will do if I can establish what the expected behaviour is supposed to be - from the one line on the website I'd expect a "login with fingerprint" button or something, but I might be wrong - so I know what I'm seeing is actually a bug and not me misinterpreting

Will see if I can track down the original PRs or something, see if there is screenshots or a proposed UI design