abrt 1.0.0 detected a crash. Comment: I don't know what caused this. Attached file: backtrace cmdline: -:0 component: kdebase-workspace executable: /usr/bin/kdm kernel: 2.6.31.6-166.fc12.i686 package: kdm-4.3.3-7.fc12.1 rating: 4 reason: Process was terminated by signal 11
Created attachment 378917 [details] File: backtrace
Are you trying to login with a fingerprint? Because it's pam_fprintd which is triggering the crash.
Hi Kevin, Nope. I do have a fingerprint reader on my laptop, but I am not using it. The last time I checked the hardware was not supported. kind regards, Egon
Thank you for taking the time to report this issue to us. This is an issue which is best addressed by the upstream developers. Please file a report at bugs.kde.org , and when done add the upstream report info to this report. We will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates. Thank you for the bug report. This bug has been triaged Steven M. Parrish KDE & Packagekit Triager Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I created the upstream bug report. See: https://bugs.kde.org/show_bug.cgi?id=220404 kind regards, Egon
Hi, Quote from the upstream bugreport: ========================== well, i'll just generously bounce back the ball. :P this looks like a pam_fprintd issue - judging by the backtrace it may be assuming the presence of a glib main loop, which is of course absent in kdm. this wouldn't be too surprising if it was tested only with gdm. ========================== kind regards, Egon
Yeah, while the KDM frontend probably actually does have a GLib event loop with the GLib event loop integration in Qt 4, the backend doesn't and that's where the PAM modules plug into. I guess we need to disable pam_fprintd in the KDM configuration and use the KDM fingerprint plugin that guy from Brno worked on.
*** This bug has been marked as a duplicate of bug 605156 ***