use gdb and figure out where in the code it is failing?

maybe try using a breakpoint at the function that calls that error message. If you step through the function you  si
could see where it fails.

Calvin Morrison
On 17 November 2011 21:17, Darrell Anderson <humanreadable@yahoo.com> wrote:
> On a whim I tried this really big
> hammer. I created a patch to strip from the kdebase code all
> references of consolekit.c and CONSOLE_KIT. Seemed like a
> reasonable idea.
>
> No luck. Still can't login with KDM.
>
> Would somebody please provide me a
> knee-bone-connected-to-the-thigh-bone explanation or simple
> flow chart how KDM runs through everything? I'm still
> leaning toward this being an authentication problem. Perhaps
> with some kind of flow chart I can try something.

Some progress.

I tried some different -debug options with kdm. I saw an error message "password verify failed." The only place the message is found is in kdm/backend/client.c.

Any ideas where to attack next?

Darrell


---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net
Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting