https://bugs.kde.org/show_bug.cgi?id=506658
--- Comment #3 from [email protected] --- Yes, I thought about that. Obviously it should not crash. But fprintd works perfectly for me for all authentication, including the virtual consoles and all inside KDE. The only single occasion that it doesn't work is with kde screenlocker. It is expecting 80 bytes and got 8000, so I guess a fprintd bug fix would give an error and exit gracefully...? Anyway, I would report this also to fprintd. But I don't expect any answers though, since they are EXTREMELY slow adding new hardware even when patched versions for specific scanners have been circulating for a long time working perfectly. -- You are receiving this mail because: You are watching all bug changes.
