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
On 15 November 2011 15:37, Darrell Anderson humanreadable@yahoo.com wrote:
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
Why not just use pam? My guess is that kdm uses pam to authenticate.
Calvin Morrison
Le Tue, 15 Nov 2011 15:39:20 -0500, Calvin Morrison mutantturkey@gmail.com a écrit :
On 15 November 2011 15:37, Darrell Anderson humanreadable@yahoo.com wrote:
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
Why not just use pam? My guess is that kdm uses pam to authenticate.
Because Slackware does not use PAM and the Slackware community won't accept anything that uses PAM (actually, for the last version Patrick Volderking put Google Chrome SlackBuild in extra/ with a PAM solibs package that installs in /opt/google/chrome to ensure PAM libraries are used only by Chrome for runtime…). Anyway I didn't see anything obvious in the diff between KDE 3.5.10's kdebase/kdm/backend and the Trinity one that would prevent non-PAM authentication from working. I'm attaching this diff (there is some part in ctrl.c I don't really understand, sockets and perms are not the parts of programming I know the best :)).
Calvin Morrison
-
/dev/ammo42 -
Calvin Morrison -
Darrell Anderson