On Friday 17 Mar 2017 08:56:18 Raffaele Belardi wrote: > Miroslav Rovis wrote: > > On 170316-21:35+0000, Peter Humphrey wrote: > >> I've just finished (well, you know) installing Gentoo on a new box and > >> given it an LXDE desktop. Every time I start the desktop, whether by > >> startx or via lxdm, I immediately get an error box saying "Could not > >> connect: No such file or directory." Does anyone here recognise this? > >> Google hasn't helped me. > >> > > Look up what you get in /var/log/messages at the time of the error.
Mar 17 09:11:10 webs lxdm-binary[1804]: PAM unable to dlopen(/lib64/security/pam_gnome_keyring.so): /lib64/security/pam_gnome_keyring.so: cannot open shared object file: No such file or directory Mar 17 09:11:10 webs lxdm-binary[1804]: PAM adding faulty module: /lib64/security/pam_gnome_keyring.so Mar 17 09:11:10 webs lxdm-binary[1804]: PAM unable to dlopen(/lib64/security/pam_selinux.so): /lib64/security/pam_selinux.so: cannot open shared object file: No such file or directory Mar 17 09:11:10 webs lxdm-binary[1804]: PAM adding faulty module: /lib64/security/pam_selinux.so Mar 17 09:11:10 webs lxdm-binary[1804]: pam_unix(lxdm:session): session opened for user prh by (uid=0) Mar 17 09:11:10 webs ck-launch-session[1860]: error connecting to ConsoleKit > Also .cache/lxsession/LXDE/run.log A lot of stuff from vala. No timestamps though - do I get a new run.log each time LXDE starts, or are new entries appended? I guess it's the former. > Does the desktop show up regularly besides showing the error message? I don't know, as I've never used LXDE before. The screen is plain black, which doesn't seem right. Thanks for the clues, gents. I'll go away and poke around a bit. Maybe run an emerge -e world. -- Regards Peter
