upgrade to KDE 3.2 broke autologin in SUSE 9
Hi, I upgraded my KDE 3.1.5 installation on Suse 9 to KDE 3.2 with (almost) no pain. I have to say that KDE 3.2 is very stable and feature rich! My only issue is that the autologin option that I enabled for my wife is not working anymore. When KDE starts up we get a message saying that the authentication failed. Then when I manually login (on the same account), everything works fine... I thought that it might be something related to a saved setting (either in the .kde directory or somewhere else, but the issue is still in place if I enable autologin for another user)... what could be the reason? Can someone explain me what is exactly happening when you enable autologin (i.e. what is written, where) so that I can modify it in order to ensure the proper work of autologin thanks a lot & regards, Timur __________________________________ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html
Timur a écrit :
Hi,
I upgraded my KDE 3.1.5 installation on Suse 9 to KDE 3.2 with (almost) no pain. I have to say that KDE 3.2 is very stable and feature rich!
My only issue is that the autologin option that I enabled for my wife is not working anymore. When KDE starts up we get a message saying that the authentication failed. Then when I manually login (on the same account), everything works fine...
I thought that it might be something related to a saved setting (either in the .kde directory or somewhere else, but the issue is still in place if I enable autologin for another user)... what could be the reason? Can someone explain me what is exactly happening when you enable autologin (i.e. what is written, where) so that I can modify it in order to ensure the proper work of autologin
thanks a lot & regards, Timur
Strange but... true. The same thing happened by me when I updated from SuSE 8.2 to 9.0. I don't know how to recover the password-less mode. Robert
On Saturday 07 February 2004 11:28 am, Timur wrote:
My only issue is that the autologin option that I enabled for my wife is not working anymore. When KDE starts up we get a message saying that the authentication failed. Then when I manually login (on the same account), everything works fine...
That's an acknowledged bug, and one I've encountered too. Apparently it resulted from some miscommunication between the KDE people and the pam people. But there's a fix: 1. As root, look in the directory /etc/pam.d for files named "kde", "xdm", or "kdm". 2. Assuming you find the file "kde", do the following: cd /etc/pam.d (echo "auth sufficient pam_permit.so"; cat kde) > kde-np If instead you find "xdm" or "kdm", replace "kde" by one of those in two places in the second line above. For more details, go to: http://bugs.kde.org/show_bug.cgi?id=68331 I've been leaning on others here so often for help that I'm always grateful for the opportunity to help someone else. Thanks! Paul Abrahams
Op zaterdag 7 februari 2004 18:53, schreef Paul W. Abrahams:
If instead you find "xdm" or "kdm", replace "kde" by one of those in two places in the second line above.
For more details, go to:
http://bugs.kde.org/show_bug.cgi?id=68331
I've been leaning on others here so often for help that I'm always grateful for the opportunity to help someone else. Thanks!
Works very good indeed, thanks! -- Richard Bos Without a home the journey is endless
--- "Paul W. Abrahams"
On Saturday 07 February 2004 11:28 am, Timur wrote:
That's an acknowledged bug, and one I've encountered too. Apparently it resulted from some miscommunication between the KDE people and the pam people. But there's a fix:
...
For more details, go to:
Thank you very much Paul, I'll test it tonight (now I don't have that PC with me). Regards, Timur __________________________________ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html
--- "Paul W. Abrahams"
cd /etc/pam.d (echo "auth sufficient pam_permit.so"; cat kde) > kde-np
If instead you find "xdm" or "kdm", replace "kde" by one of those in two places in the second line above.
Paul, I tried your suggestion, but unluckly it didn't work... I'm one of those who had only the xdm file. Following your suggestion I did: (echo "auth sufficient pam_permit.so"; cat xdm) > kde-np But unluckly it didn't work: after the reboot I still had the authentication failed message. Is there anything specific that I have to do after I created the kde-np in the /etc/pam.d in order to tell pam to make use of it? (for example modifying the pam.conf file or changing the password for that specific user, etc.) Timur __________________________________ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html
Selon Timur
--- "Paul W. Abrahams"
wrote: cd /etc/pam.d (echo "auth sufficient pam_permit.so"; cat kde) > kde-np
If instead you find "xdm" or "kdm", replace "kde" by one of those in two places in the second line above.
Paul, I tried your suggestion, but unluckly it didn't work...
I'm one of those who had only the xdm file. Following your suggestion I did:
(echo "auth sufficient pam_permit.so"; cat xdm) > kde-np
But unluckly it didn't work: after the reboot I still had the authentication failed message.
I did so with the same conclusion. Later I wrote the added line at the very beginning of the "xdm" config file. Suddenly it became possible for ALL users to login without password ... even root. I quickly disabled ! Robert
On Tuesday 10 February 2004 8:04 am, Robert Cabane wrote:
Selon Timur
:
I'm one of those who had only the xdm file. Following your suggestion I did:
(echo "auth sufficient pam_permit.so"; cat xdm) > kde-np
But unluckly it didn't work: after the reboot I still had the authentication failed message.
I did so with the same conclusion. Later I wrote the added line at the very beginning of the "xdm" config file. Suddenly it became possible for ALL users to login without password ... even root. I quickly disabled !
I just tried that myself, and root still needed a password. You may have done something slightly different than what I did -- perhaps modifying the xdm file rather than creating the xdm-np file. As I said to Selon, though, I'm no expert on this stuff. All I did was to take material from a bug report and reformulate it as an easy-to-follow recipe (which Selon didn't precisely follow). Paul Abrahams
--- "Paul W. Abrahams"
On Tuesday 10 February 2004 8:04 am, you wrote:
I just tried that myself, and root still needed a password. You may have done something slightly different than what I did -- perhaps modifying the xdm file rather than creating the xdm-np file. As I said to Selon, though, I'm no expert on this stuff. All I did was to take material from a bug report and reformulate it as an easy-to-follow recipe (which Selon didn't precisely follow).
Paul, it worked fine for me by renaming kde-np to xdm-np as you were suggesting. thanks again, Timur
Paul Abrahams
-- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e
__________________________________ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html
On Tuesday 10 February 2004 5:43 am, Timur wrote:
--- "Paul W. Abrahams"
wrote: cd /etc/pam.d (echo "auth sufficient pam_permit.so"; cat kde) > kde-np
If instead you find "xdm" or "kdm", replace "kde" by one of those in two places in the second line above.
Paul, I tried your suggestion, but unluckly it didn't work...
I'm one of those who had only the xdm file. Following your suggestion I did:
(echo "auth sufficient pam_permit.so"; cat xdm) > kde-np
But unluckly it didn't work: after the reboot I still had the authentication failed message.
The problem, I think, is that you needed to replace "kde" by "xdm" in two places, not just one. The correct command would be: (echo "auth sufficient pam_permit.so"; cat xdm) > xdm-np Alternatively (and probably better), since you've created the correct file under the wrong name: mv kdm-np xdm-np I don't claim to understand what lies behind all this, however. Paul
On Saturday 07 February 2004 11:28 am, Timur wrote:
Hi,
I upgraded my KDE 3.1.5 installation on Suse 9 to KDE 3.2 with (almost) no pain. I have to say that KDE 3.2 is very stable and feature rich!
My only issue is that the autologin option that I enabled for my wife is not working anymore. When KDE starts up we get a message saying that the authentication failed. Then when I manually login (on the same account), everything works fine...
I thought that it might be something related to a saved setting (either in the .kde directory or somewhere else, but the issue is still in place if I enable autologin for another user)... what could be the reason? Can someone explain me what is exactly happening when you enable autologin (i.e. what is written, where) so that I can modify it in order to ensure the proper work of autologin
thanks a lot & regards, Timur -------============ Timur,
Did you go back into kcontrol center and reset the autologin? I believe it comes disabled under KDE 3.2 now. If you have in fact checked that, then my suspicions are that it was part of kdebase3-SuSE stuff that had to be removed for 3.2 to install and won't work until SuSE sends us a new version to work with KDE 3.2! Lee -- --- KMail v1.6 --- SuSE Linux Pro v9.0 --- Registered Linux User #225206 On any other day, that might seem strange...
participants (5)
-
BandiPat
-
Paul W. Abrahams
-
Richard Bos
-
Robert Cabane
-
Timur