This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Timeout set with AutoLoginDelay in kdmrc. Solved.

Tags: None
(comma "," separated)
User avatar
dwightpaige79
Registered Member
Posts
13
Karma
0
OS
AutoLogin immediately works. But when I set 'AutoLoginDelay=10' in
'kdmrc' upon reboot login screen shows selected autologin user and grey **** entry in password field but does not log in. And after 10 seconds password field is uneditable and no user can login. FWIW this is happening in openSuSE 11.2 and 11.3 Milestone 5, Fedora 12 & 13, and Mandriva 2010.0 and 2010.1 all X86_64. This behavior started with KDE 4.4.0 and persists in KDE 4.4.2. kdmrc is thus:

Code: Select all
...
NoPassEnable=true
# The users that do not need to provide a password to log in. NEVER list root!
# "*" means all non-root users. @<group> means all users in that group.
# Default is ""
NoPassUsers=<userx>
...
#NoPassAllUsers=true
# Enable automatic login. USE WITH EXTREME CARE!
# Default is false
AutoLoginEnable=true
# If true, auto-login after logout. If false, auto-login is performed only
# when a display session starts up.
# Default is false
AutoLoginAgain=true
# The delay in seconds before automatic login kicks in.
# Default is 0
AutoLoginDelay=10
# The user to log in automatically. NEVER specify root!
# Default is ""
AutoLoginUser=<userx>
# The password for the user to log in automatically. This is NOT required
# unless the user is logged into a NIS or Kerberos domain. If you use this
# option, you should "chmod 600 kdmrc" for obvious reasons.
# Default is ""
#AutoLoginPass=secret!
# Immediately lock the automatically started session. This works only with
# KDE sessions.
# Default is false
AutoLoginLocked=false
# See above
ClientLogFile=.xsession-errors
...


The following is from:

https://bugs.kde.org/show_bug.cgi?id=229475

Comment #8 From Jorge Manuel B S Vicetto 2010-03-29 04:34:02

AFAICS, there are two issues being reported here:

1. The timeout set with AutoLoginDelay in kdmrc is not respected - kdm just
sits waiting and never performs the login

2. kdm shows the specified user and default password display of "****" on
start, but the password field isn't selectable and thus it's not possible to
type the user's password and or press enter to force the login.

I can confirm both on Gentoo with kdm-4.4.1 with the following entries in
kdmrc:

AutoLoginEnable=true
AutoLoginAgain=true
AutoLoginDelay=5
AutoLoginUser=<user>


My questions are, knowing this is certainly how kdmrc used for work before KDE 4.4:

1. Is this still how kdmrc is supposed to work? It certainly is still listed as a commented out option in original kdmrc after fresh install of openSuSE, Fedora, and Mandriva.

2. Are other users experiencing this behavior?

3. If this is supposed to work how can I fix it? The bug report was filed on March 5, 2010 but hasn't been assigned.

Last edited by dwightpaige79 on Sun Sep 26, 2010 11:49 pm, edited 1 time in total.


Thanks,
Dwight Paige
User avatar
dwightpaige79
Registered Member
Posts
13
Karma
0
OS
I believe it would be accurate to say I've never filed a bug before and gotten no response from the organization with whom I filed the bug. It's been since, if I'm reading the date correctly, May 3, 2010. Or is it March 5, 2010? I must have done something wrong. Wish someone would tell me what I did wrong??? Feeling like an idiot is much easier to take if one has the opportunity to learn what one did wrong.


Thanks,
Dwight Paige
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
It is unlikely you did anything wrong. Many developers simply only have a small amount of time to deal with so many bug reports. Especially for more visible components, many bug reports are filed.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
User avatar
dwightpaige79
Registered Member
Posts
13
Karma
0
OS
This is scheduled to be fixed in KDE 4.5.2.

https://bugs.kde.org/show_bug.cgi?id=229475


Thanks,
Dwight Paige
User avatar
dwightpaige79
Registered Member
Posts
13
Karma
0
OS
In Mandriva Cooker we have:

KDE - Platform Version 4.5.68 (4.6 >= 20100912)

and this bug is indeed fixed there.

Again. Many thanks.


Thanks,
Dwight Paige


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], Sogou [Bot]