trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: November 2011

Slackware 13.1 Binary Packages

From: Darrell Anderson <humanreadable@...>
Date: Tue, 15 Nov 2011 12:37:55 -0800 (PST)
My packages for Slackware 13.1 are ready --- except for one major bug: KDM.

I can't login using the Trinity KDM. At least one other Slackware/Trinity user has confirmed this behavior.

I am uncomfortable uploading packages when I know KDM is broken. Yes, Slackware users can use the KDE 4 KDM, which is part of the stock Slackware, but that is...icky. :(

I know everybody is busy but if I can get help with a patch then I would feel much better. If the patch succeeds then I'll submit the bug report to ensure SVN/GIT gets updated.

I'm fairly certain the problem is authentication. When I login all I see is a "Login failed" message.

Slackware does not use PAM.

Slackware supports PolicyKit but using that layer is not required by users. Indeed, the KDE 4 KDM, which is part of the stock Slackware, is not built or dependent upon PolicyKit. I can login with the KDE 4 KDM just fine.

As a note, I built KDE 3.5.10 for Slackware 13.1 and KDM there works fine.

I built kdebase 3.5.13 with the WITH_PAM=OFF option. No change. Allowing root logins through KDM fails too, so the problem is unlikely to be file permissions.

I also have tried enabling and disabling SAK. No change.

Thanks!

Darrell