You are not logged in.

#1 2008-10-22 18:03:48

vootpig
Member
Registered: 2008-08-11
Posts: 14

Weird gconf error

Hey all,

Out of nowhere I started getting this strange error. When I boot up my computer, I log in to a normal user account and type "startx", but it just comes up with a black screen and the "X" cursor. After a while GNOME starts up, but gconf spits out this error:

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-8dnUYudZiT: Connection refused)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-8dnUYudZiT: Connection refused)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-i657JJcKyq: Connection refused)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-i657JJcKyq: Connection refused)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-DJBlEoHKYY: Connection refused)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-DJBlEoHKYY: Connection refused)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-EvUAerfUO4: Connection refused)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-EvUAerfUO4: Connection refused)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-thzElTtpFH: Connection refused)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-thzElTtpFH: Connection refused)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-WsH9f6DK9f: Connection refused)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-WsH9f6DK9f: Connection refused)

I'm not sure how to go about fixing this, after a couple Googles and a quick wiki check. Can anyone lend me a hand? Thanks

Offline

#2 2008-10-22 21:15:11

byte
Member
From: Düsseldorf (DE)
Registered: 2006-05-01
Posts: 2,046

Re: Weird gconf error

What's the output of:
a) cat ~/.xinitrc
b) ls -ld /tmp
c) ls /var/run/daemons
?

Last edited by byte (2008-10-22 21:16:09)


1000

Offline

#3 2008-10-22 21:54:19

vootpig
Member
Registered: 2008-08-11
Posts: 14

Re: Weird gconf error

cat ~/.xinitrc:

#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)
#

 exec gnome-session
# exec startkde
# exec startxfce4
# exec icewm
# exec openbox
# exec blackbox
# exec fluxbox
# exec ratpoison
# exec dwm
# ... or any other WM of your choosing ...

ls -ld /tmp:

drwxrwxrwt 7 root root 4096 2008-10-22 17:53 /tmp

ls /var/run/daemons:

alsa  crond  dbus  fam  hal  netfs  network  portmap  syslog-ng

Offline

#4 2008-10-22 22:00:11

byte
Member
From: Düsseldorf (DE)
Registered: 2006-05-01
Posts: 2,046

Re: Weird gconf error

Ok, looks alright.

Duh, I love it when even Google leads back to this very forum... see http://bbs.archlinux.org/viewtopic.php?id=56215


1000

Offline

#5 2008-10-22 22:13:50

vootpig
Member
Registered: 2008-08-11
Posts: 14

Re: Weird gconf error

I tried all the methods in that thread, and succeeded in upgrading gnome-settings-daemon, but it still hasn't fixed the problem. :\ any help?

Offline

#6 2008-10-22 23:42:20

test1000
Member
Registered: 2005-04-03
Posts: 834

Re: Weird gconf error

i had that issue.. i even reported a bug about it but supposedly it was just all my fault(doesn't seem that way though when reading the mailinglist and various forum posts now). I tried to fid my bugreports but they have been closed and are now deleted(or i can't find them) but i remember a bunch of problems and i atleast did pacman -S gnome dbus dbus-core metacity, deleted my ~/.gnome*, .config/gnomerelated and /tmp/* and perhaps made a symbolic link to a nonexisting dbus library. a thing that helped was to sartup X with just an xterm and launch gnome-session from there and watch the errors..


KISS = "It can scarcely be denied that the supreme goal of all theory is to make the irreducible basic elements as simple and as few as possible without having to surrender the adequate representation of a single datum of experience." - Albert Einstein

Offline

Board footer

Powered by FluxBB