| 1 |
You should edit this file: /etc/conf.d/xdm . Change the |
| 2 |
DISPLAYMANAGER="xdm" to DISPLAYMANAGER="gdm". |
| 3 |
then: |
| 4 |
sudo rc-update add xdm default . |
| 5 |
|
| 6 |
2012/9/26 Allan Gottlieb <gottlieb@×××.edu> |
| 7 |
|
| 8 |
> I am building a new installation and must have messed up a step as gdm |
| 9 |
> doesn't start from boot |
| 10 |
> |
| 11 |
> If I manually execute |
| 12 |
> eselect rc restart xdm |
| 13 |
> I get |
| 14 |
> |
| 15 |
> Sep 25 20:10:51 newlap gnome-keyring-daemon[2106]: couldn't create socket |
| 16 |
> directory: No such file or directory |
| 17 |
> Sep 25 20:10:51 newlap gnome-keyring-daemon[2106]: couldn't bind to |
| 18 |
> control socket: /root/.cache/keyring-dJpHuM/control: No such file or |
| 19 |
> directory |
| 20 |
> |
| 21 |
> which appears to be the problem and can also be found in /log/messages |
| 22 |
> |
| 23 |
> I have installed xorg-x11, xdm and gnome and /var/log/Xorg.0.log looks |
| 24 |
> OK. The only complaints are failing to load vesa, modsetting, and |
| 25 |
> fbdev drivers. However, the intel driver loads fine. |
| 26 |
> |
| 27 |
> /var/log/dmesg ends with entries saying that EXT4-fs mounted |
| 28 |
> filesystems. No gdm/xdm/X/keyring complaints. |
| 29 |
> |
| 30 |
> What step did I miss? |
| 31 |
> |
| 32 |
> thanks, |
| 33 |
> allan |
| 34 |
> |
| 35 |
> |
Archives