I am building a new installation and must have messed up a step as gdm doesn't start from boot

If I manually execute
eselect rc restart xdm
I get

Sep 25 20:10:51 newlap gnome-keyring-daemon[2106]: couldn't create socket directory: No such file or directory
Sep 25 20:10:51 newlap gnome-keyring-daemon[2106]: couldn't bind to control socket: /root/.cache/keyring-dJpHuM/control: No such file or directory

which appears to be the problem and can also be found in /log/messages

I have installed xorg-x11, xdm and gnome and /var/log/Xorg.0.log looks
OK. The only complaints are failing to load vesa, modsetting, and
fbdev drivers. However, the intel driver loads fine.

/var/log/dmesg ends with entries saying that EXT4-fs mounted
filesystems. No gdm/xdm/X/keyring complaints.

What step did I miss?

thanks,
allan

You should edit this file: /etc/conf.d/xdm . Change the DISPLAYMANAGER="xdm" to DISPLAYMANAGER="gdm".Â*then:Â*sudo rc-update add xdm default .

2012/9/26 Allan Gottlieb <gottlieb@nyu.edu>

I am building a new installation and must have messed up a step as gdm doesn't start from boot



If I manually execute

Â* Â*eselect rc restart xdm

I get



Sep 25 20:10:51 newlap gnome-keyring-daemon[2106]: couldn't create socket directory: No such file or directory

Sep 25 20:10:51 newlap gnome-keyring-daemon[2106]: couldn't bind to control socket: /root/.cache/keyring-dJpHuM/control: No such file or directory



which appears to be the problem and can also be found in /log/messages



I have installed xorg-x11, xdm and gnome and /var/log/Xorg.0.log looks

OK. Â*The only complaints are failing to load vesa, modsetting, and

fbdev drivers. Â*However, the intel driver loads fine.



/var/log/dmesg ends with entries saying that EXT4-fs mounted

filesystems. Â*No gdm/xdm/X/keyring complaints.



What step did I miss?



thanks,

allan