How do you enable auto login??

[trojan]

I'm new to XFCE 4 , and I was wondering how you enable autologin, it doesnt appear to have a login manager like KDE and Gnome.

[bigpaws]

http://forum.vectorlinux.com/index.php?topic=5956.0

Bigpaws

[trojan]

Theres nothin in the file that it said to edit

[stretchedthin]

I read through the link bigpaws suggested the relevant info seems to be this...


Make sure you use KDM as your login manager.
Edit the file /usr/share/config/kdm/kdmrc, change three lines:
AutoLoginEnable=true   
AutoLoginUser=   <-- insert user name
PreselectUser=    <-- insert user name

If you are not finding the appropriate file are you sure you are using the KDM window manager.

I can find it on my system and I have these two items loaded via GSlapt. kdm-small 3.5.5-i586-2vl58 and kdmtheme-Bela 1-noarch-2vl59

To be honest I never chose to switch to the KDM window manager it just seemed to happen when I loaded Amarok. 

Just to be sure I was not sending you on a wild goose chase I did it myself.

Using Super File Manager I followed the path above and opened kdmrc in mousepad.
I removed the # before the AutoLoginEnable=true
then I entered the two other lines below that one, inserting my own user name.
AutoLoginUser=   <-- insert user name
PreselectUser=    <-- insert user name
Then I saved.
Restarted my machine to see what would happen and, baddabing, it worked.

[trojan]

#AutoLoginEnable=true
#AutoLoginUser=colin
#PreselectUser=colin

is that correct should they have a # sign at the beginning?

[trojan]

ha ha ! thanks guys worked without the hash symbole great!

[The Headacher]

the '#' symbol is (in bash and other shells) used to start a comment. So, lines starting with # are often used as comments in configuration files as well. .

[caitlyn]

To be honest I never chose to switch to the KDM window manager it just seemed to happen when I loaded Amarok. 

KDM is a display manager, not a window manager.  It handles the GUI login process only.  It is installed by default on *every* Vector Linux installation.  To use something else you have to make a conscious decision to do so.  It has nothing to do with Amarok.

trojan:  It sounds like your problem is solved.  If so could you please add the word (SOLVED) to the subject title.  That makes life easier for those looking to offer technical support.  Thanks!

[wcs]

To use something else you have to make a conscious decision to do so.  It has nothing to do with Amarok.

True, but I see where trojan is coming from.
When you install amarok it pulls kdebase 3.5.9 and I've seen that leading to changes in kdm. I suppose some files in kdebase overwrite the "default" files.

(I don't remember if a fresh 5.9 install has kdebase or the kdm-small package, but either way, iirc upgrading to 3.5.9 overrides your previous kdm settings, and I think the kdmrc file even goes to a different directory altogether).

Of course, it's still kdm, but it might look different after you install kde packages for the first time.