[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Problem Initializing device during login
From:       Oswald Buddenhagen <ossi () kde ! org>
Date:       2002-11-30 11:40:28
[Download RAW message or body]

On Sat, Nov 30, 2002 at 10:07:23AM -0000, siddharth sharma rajput wrote:
> I think you are not getting my problem.
>
would you bet? :)

> I have just added a single line of code in kgreeter.cpp .
> 
yes, i understood that.

>  FPMInitLibrary();
> 
> Now writing this line doesn't sends any message to backend.
> 
that's correct.

> I have just used this function. And when kdm reaches there, It aborts.
> 
that's why i said that you blew it. :)
this does not have anything to do with kdm. possibly with the kde
libraries. i think some requirement of the library is not met, so it
simply crashes.

> So is there not any possibility to just initialize the device in
> kgreeter.cpp
> 
it should be _possible_ there like anywhere else. that does not change
the fact, that this simply does not belong into this module (the
greeter).

> Actually how it brokes the architecture??
> 
it does not break anything, it just shows how broken kdm (and, btw, xdm)
already is. see the bug report i pointed you to.
the architecture should be just like pam works: the backend dictates the
frontend what do show and which input to obtain from the user. currently
the frontend simply obtains a username and a password and passes them to
the backend, what obviously won't work with anything but "classic"
login.
that having said, pam does not get everything right (tm), too, but it's
closer to what is needed. let's see, if i can hack something together
that is actually suitable for biometric authentication.

greetings

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
--
Chaos, panic, and disorder - my work here is done.
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]