Bug 220404

Summary: [abrt] crash detected in kdm-4.3.3-7.fc12.1
Product: [Unmaintained] kdm Reporter: E. Kastelijn <kde2>
Component: generalAssignee: kdm bugs tracker <kdm-bugs-null>
Status: RESOLVED DOWNSTREAM    
Severity: crash CC: kevin.kofler, rdieter
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Backtrace

Description E. Kastelijn 2009-12-28 15:28:07 UTC 
Version:           kdm-4.3.3-7.fc12.1 (using KDE 4.3.3)
Compiler:          gcc-4.4.2-7.fc12.i686  glibc-2.11-2.i686 
OS:                Linux
Installed from:    Fedora RPMs

abrt 1.0.0 detected a crash.

Comment: I don't know what caused this.
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  

See also:
https://bugzilla.redhat.com/show_bug.cgi?id=548347
Comment 1 E. Kastelijn 2009-12-28 15:31:23 UTC 
Created attachment 39406 [details]
Backtrace
Comment 2 Oswald Buddenhagen 2009-12-31 10:41:59 UTC 
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.

ps: for the future, please paste backtraces instead of attaching them.
Comment 3 E. Kastelijn 2009-12-31 12:16:17 UTC 
;)
Okay..
I added part of your comment to the RedHat bug.
Let's see where this goes..

Thanks for looking into it.

kind regards,

  Egon
Comment 4 Kevin Kofler 2010-08-17 16:32:06 UTC 
From the Red Hat Bugzilla:

--- Comment #10 from Bastien Nocera <bnocera at RH> 2010-08-17 10:24:53 EDT ---
(In reply to comment #8)
> Quote from the upstream bugreport:
> https://bugs.kde.org/show_bug.cgi?id=220404
> ==========================
> 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.

Whao. Somebody isn't looking at code... It uses its own main loop, which
happens to be a GLib one.

> this wouldn't be too surprising if it was tested only with gdm.

It was also tested with a number of non-glib apps, such as "login"...

> ==========================
> 
> Re-assigning for feedback/comment from fprintd maintainer(s).

I'll look at this.