abrt 1.1.1 detected a crash. architecture: i686 Attached file: backtrace cmdline: -:0 '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' comment: login via kdm with wrong password makes kdm crash when password is entered again component: kdebase-workspace executable: /usr/bin/kdm global_uuid: e18ff73f7a83e143332faa534b61db0b744bac8a kernel: 2.6.33.5-124.fc13.i686 package: kdm-4.4.4-1.fc13 rating: 3 reason: Process /usr/bin/kdm was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard) How to reproduce ----- 1. enter wrong password into kdm login window (empty is enough) 2. enter anything into pasword field again
Created attachment 424754 [details] File: backtrace
after commenting out this line auth sufficient pam_fprintd.so from /etc/pam.d/system-auth everything is ok
KDE Version 4.4.4 is now available. Please update to the this latest release and retest the application. Please advise if you are still having the same issue as documented. Any reports not updated within 30 days will be closed. Thanks from the Fedora KDE Team
Created attachment 425831 [details] new backtrace the bug is still here, backtrace is slightly different now it looks like the issue is out of the kdm, but I am not an expert commenting out pam_fprintd.so from /etc/pam.d/system-auth still works
*** Bug 612176 has been marked as a duplicate of this bug. ***
*** Bug 544701 has been marked as a duplicate of this bug. ***
*** Bug 548347 has been marked as a duplicate of this bug. ***
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. this wouldn't be too surprising if it was tested only with gdm. ========================== Re-assigning for feedback/comment from fprintd maintainer(s).
My tests after yum remove fprintd , couldn't reproduce the bug again, but just a few tests.
(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.
Could you please test with the newer libfprint and fprintd 0.2 releases? If you want the F13 packages, I'm afraid you'll have to wait a little, as the buildroot is broken, but the packages are available from http://koji.fedoraproject.org Updates have been filed for F-12 and F-14
Created attachment 439896 [details] backtrace unfortunately still the same behaviour with fprintd-debuginfo-0.2.0-1.fc13.i686 fprintd-pam-0.2.0-1.fc13.i686 fprintd-0.2.0-1.fc13.i686 libfprint-debuginfo-0.2.0-1.fc13.i686 libfprint-0.2.0-1.fc13.i686
OK, let's get this triaged properly -> pam_printd
*** Bug 635059 has been marked as a duplicate of this bug. ***
pam_fprint is obsolete, the new pam-fprintd module is in the fprintd-pam subpackage of fprintd.
*** Bug 506171 has been marked as a duplicate of this bug. ***
users reporting seeing this on f14 too. :( I guess we could consider omitting it from the kde spin considering it's known to cause problems.
ommited per http://git.fedorahosted.org/git/?p=spin-kickstarts.git;a=commitdiff;h=c5d32129f7789be52b7ff330cd5e8c75e3f5ffe8;hp=0fa07e73697cb5887dade22147b6ed8c0fb74ff1 until this is resolved. (And kde upstream noticing the backtraces involve crashes inside of pam, closed->downsream now too).
*** Bug 585799 has been marked as a duplicate of this bug. ***
fprintd-0.2.0-2.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/fprintd-0.2.0-2.fc14
Hey guys, someone came up to me during a conference and showed me a bug where the gnome-screensaver unlock dialog crashed. (there's no filed report about that as far as i can tell from searching). The bug ended up being an issue in pam_fprintd. On the surface, it looks like it may be same problem affecting this bug report. I'd appreciate if anyone affected could try the update and report back whether it solves this problem as well.
fprintd-0.2.0-2.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update fprintd'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/fprintd-0.2.0-2.fc14
With fprintd-0.2.0-1.fc14 kdm still crashes. But I can not reproduce reported crash in kdm with fprintd-0.2.0-2.fc14. It looks like the bug is gone. Thank you.
(In reply to comment #23) > With fprintd-0.2.0-1.fc14 kdm still crashes. But I can not reproduce reported > crash in kdm with fprintd-0.2.0-2.fc14. It looks like the bug is gone. Thank > you. Awesome. Thanks to Ray for fixing this up. Rex, any chance you can revert your patch and add the new fprintd to the spin (at least for F15).
Yes, thanks!
fprintd-0.2.0-2.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 655270 has been marked as a duplicate of this bug. ***