Bug 548347

Summary: [abrt] crash detected in kdm-4.3.3-7.fc12.1
Product: [Fedora] Fedora Reporter: Egon Kastelijn <redhat2>
Component: kdebase-workspaceAssignee: Than Ngo <than>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: fedora, fedora, jreznik, kevin, lorenzo, ltinkl, rdieter, smparrish, than
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:52bf502f293bb2a983ba2acf054bb7e8d043cea2
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-07 14:22:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Egon Kastelijn 2009-12-17 07:37:52 UTC 
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
Comment 1 Egon Kastelijn 2009-12-17 07:37:56 UTC 
Created attachment 378917 [details]
File: backtrace
Comment 2 Kevin Kofler 2009-12-17 07:59:44 UTC 
Are you trying to login with a fingerprint? Because it's pam_fprintd which is triggering the crash.
Comment 3 Egon Kastelijn 2009-12-17 20:41:18 UTC 
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
Comment 4 Steven M. Parrish 2009-12-22 15:08:53 UTC 
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
Comment 5 Egon Kastelijn 2009-12-28 14:34:37 UTC 
I created the upstream bug report.

See: https://bugs.kde.org/show_bug.cgi?id=220404 

kind regards,

  Egon
Comment 6 Egon Kastelijn 2009-12-31 11:14:49 UTC 
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
Comment 7 Kevin Kofler 2010-01-02 04:05:42 UTC 
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.
Comment 8 Rex Dieter 2010-07-07 14:22:34 UTC 

*** This bug has been marked as a duplicate of bug 605156 ***