Problem with Xorg on Gentoo

JamesIvings · 02-19-2009, 04:18 AM

Hello!
Am working on a Gentoo distro on my Desktop and am having a few problems with X.
Current configured with xorgconfig, think it should be alright. However when I startx, it boots up fine, displaying the horrible X terminals, but then locks up. The only think that has any effect is pressing SysRq-E to kill all processes, taking me back to the command line, displaying the following error:

Code:

xinit: Connection refused (errno 111): Cannot register with 
ConsoleKit: org.freedesktop.CkConnector.Error: Unable to open 
session: Failed to connect to socket /var/run/dbus/system_bus-
socket: Connection refused.

Have tried many different xorg.conf settings, doesn't seem to have any effect. I'm using xorg-x11 7.4.

Can anyone shed some light on this? I can provide the xorg.conf if neccessary..

Thanks.

Pearlseattle · 02-19-2009, 11:42 AM

Hello
Mmmhh, xorg-x11 7.4 is still marked as unstable for amd64 arch... . I'm using 7.2.

Anyway I doubt that xorg.conf has something to do with it, if the problem has something to do with dbus.

Do you have dbus installed and running (/etc/init.d/dbus start)? (don't know if this would solve the issue)

At the bottom of "/etc/rc.conf", which window manager are you using? kde, gnome, enlightenment, ...? (asking because of the "horrible X terminals")

Which GPU are you using and which drivers? nVidia, Intel, ATI, ... .

Perhaps posting as well /var/log/Xorg.0.log would help... .

JamesIvings · 02-20-2009, 08:56 AM

Thanks for your help, but I solved the problem

Something was wrong with x11-driver/xf86-input-evdev. I re-emerged it and everything worked perfectly

i92guboj · 02-20-2009, 08:59 AM

As a remark, every time you update xorg-server you *might* also need to update all the xf86-input-* and xf86-video-* drivers that you use. It's also recommended to use revdep-rebuild.

Probably your current problem could have been detected by taking a look to /var/log/Xorg.0.log, more then probably there was some error there telling you about the driver being compiled against a different version of the API. Just a note for future reference so you can find the problem easily the next time