Bug 153583 - Crash with Thinkpad T61
Summary: Crash with Thinkpad T61
Status: RESOLVED DUPLICATE of bug 116682
Alias: None
Product: kdm
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdm bugs tracker
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-06 21:14 UTC by Ben Boeckel
Modified: 2009-02-11 11:24 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ben Boeckel 2007-12-06 21:14:45 UTC
Version:            (using KDE KDE 3.5.8)
Installed from:    Fedora RPMs

When I try to logon to my machine, kdm crashes and I get dropped to a console. It happens around 95% of the time and I get no reason why it works then rather than the times it crashes.  It has output 3 different error messages and I can't determine the difference between them. Here are the corresponding dmesg outputs:

The first time it failed, I kept restarting X to try again:
e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
e1000: eth0: e1000_watchdog: 10/100 speed: disabling TSO
input: Virtual ThinkFinger Keyboard as /class/input/input12
usb 3-2: usbfs: process 2641 (kdm) did not claim interface 0 before use
kdm[2641]: segfault at 0000000041506480 rip 00000032d4a043bb rsp 00000000413fe190 error 6
input: Virtual ThinkFinger Keyboard as /class/input/input13
e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
e1000: eth0: e1000_watchdog: 10/100 speed: disabling TSO
input: Virtual ThinkFinger Keyboard as /class/input/input14
kdm[3127]: segfault at 000000000d696914 rip 00000032d4a04381 rsp 0000000041400d90 error 4
input: Virtual ThinkFinger Keyboard as /class/input/input15
eth0: no IPv6 routers present
e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
e1000: eth0: e1000_watchdog: 10/100 speed: disabling TSO
input: Virtual ThinkFinger Keyboard as /class/input/input16
kdm[4731]: segfault at 000000000d696914 rip 00000032d4a04381 rsp 0000000041400d90 error 4

Another error:
input: Virtual ThinkFinger Keyboard as /class/input/input14
usb 3-2: usbfs: process 2824 (kdm) did not claim interface 0 before use
kdm[2824]: segfault at 0000000041507c60 rip 00000032d4a043bb rsp 00000000413fe190 error 6
input: Virtual ThinkFinger Keyboard as /class/input/input15

Another:
input: Virtual ThinkFinger Keyboard as /class/input/input12
kdm[2691]: segfault at 000000370000010b rip 00000037af872bc9 rsp 00007fff21130310 error 6
input: Virtual ThinkFinger Keyboard as /class/input/input13
input: Virtual ThinkFinger Keyboard as /class/input/input14
input: Virtual ThinkFinger Keyboard as /class/input/input15

The ThinkFinger output may just be a coincidence in the last ones, but before that is the stuff from boot.

I am not sure what exactly causes the error, so I don't know how to reproduce it consistently on a machine other than this one.
Comment 1 Oswald Buddenhagen 2007-12-15 18:41:16 UTC
are you by any chance trying to use thinkfinger for authentication or is it "just running"?
Comment 2 Ben Boeckel 2007-12-16 07:43:28 UTC
Turning it off works. Thinkfinger is in my pam-auth file for authentication and it worked with gdm (why it was in there), but kdm does this. I imagine that it was "just running" when this happened. I have since uninstalled it and had no problems, so ThinkFinger integration with KDE does seem to be the problem.

--MathStuf
Comment 3 Oswald Buddenhagen 2007-12-16 08:51:42 UTC

*** This bug has been marked as a duplicate of 116682 ***
Comment 4 Yuriy Kozlov 2008-04-13 18:07:19 UTC
I disagree that this is a duplicate of 116682.  That one is requesting an UI for already working fingerprint authentication.  This one is reporting a crash.

This crash is also reported in Kubuntu's bug tracker:
https://bugs.launchpad.net/kdebase/+bug/216697
Comment 5 Christoph Lange 2009-02-11 11:24:41 UTC
(In reply to comment #4)
> I disagree that this is a duplicate of 116682.  That one is requesting an UI
> for already working fingerprint authentication.  This one is reporting a crash.
I agree with you and vote for unmarking this as a duplicate.