Strange GConf Error breaks GUI after update to karmic

Bug #444067 reported by iblue on 2009-10-05
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gconf (Ubuntu)
Low
Unassigned
Nominated for Karmic by skybon

Bug Description

Binary package hint: libgconf2-4

Hi,

After updating from 9.04 (jaunty) to 9.10 (karmic), the desktop is not usable anymore. I keep getting strange error messages. When trying to start gnome-terminal, firefox, or any applets in the taskbar, I get the following error message in the terminal or in some popup:

GConf 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://projects.gnome.org/gconf/ for information. (Details - 1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0)
GConf 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://projects.gnome.org/gconf/ for information. (Details - 1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0)
GConf 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://projects.gnome.org/gconf/ for information. (Details - 1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0)
GConf 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://projects.gnome.org/gconf/ for information. (Details - 1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0)
[...]

Solution:
iblue@raven:~$ sudo -s
Password:
root@raven:~# groups iblue
iblue : adm disk dialout cdrom plugdev lpadmin admin sambashare mythtv
root@raven:~# usermod -G admin,iblue iblue

And after rebooting everything works as usual.

I have no idea why this works.

You can reproduce this bug (at least on my machine) by creating a new user:
# useradd foobar
And setting a few groups:
# usermod -G adm disk dialout cdrom plugdev lpadmin admin sambashare mythtv -a foobar
Then log in via gdm and you get this strange error.

Sebastien Bacher (seb128) wrote :

Those errors usually indicate a dbus issue, do you have a session dbus bus running?

Changed in gconf (Ubuntu):
importance: Undecided → Low
iblue (iblue) wrote :

Sebastien, have you red the whole bug report? Just in case you have:

iblue@raven:~$ ps aux | grep dbus
103 1974 0.0 0.0 24284 1928 ? Ss Oct05 0:01 dbus-daemon --system --fork
gdm 5338 0.0 0.0 26156 780 ? S Oct05 0:00 /usr/bin/dbus-launch --exit-with-session
iblue 5595 0.0 0.0 36060 708 ? Ss Oct05 0:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session /usr/bin/seahorse-agent --execute gnome-session
iblue 5598 0.0 0.0 26156 772 ? S Oct05 0:00 /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session /usr/bin/seahorse-agent --execute gnome-session
iblue 5599 0.0 0.0 24244 1952 ? Ss Oct05 0:00 /bin/dbus-daemon --fork --print-pid 7 --print-address 9 --session
iblue 9028 0.0 0.0 7340 968 pts/0 S+ 00:25 0:00 grep --color=auto dbus

Sebastien Bacher (seb128) wrote :

why do you ask if I did read the bug? why would I comment on a bug without reading it? do you get those warnings when running those commands on a command line? does using dbus-launch command makes a difference?

iblue (iblue) wrote :
Download full text (3.5 KiB)

I am asking, because at the end of my bug report I have documented how to reproduce the bug. Have you tried to reproduce the bug on your system?

When running "those commands" (I think you mean "gnome-terminal", "firefox" or other applications) I get said "GConf Error". When running them (e.g. the gnome terminal) from the Application Menu, I get a popup which says: "An error occurred while loading or saving configuration information for gnome-terminal. Some of your configuration settings may not work properly". There is a button labeled "Details", when I click this button I get the error messages described above in a textarea in the popup dialog.

Trying the dbus-launch command does make no difference:

foobar@raven:~$ dbus-launch
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-zMmMdHqH08,guid=fd347750656658e
28506eafc4aca7907
DBUS_SESSION_BUS_PID=12191
foobar@raven:~$ gnome-terminal
Xlib: extension "RANDR" missing on display ":2.0".

** (gnome-terminal:12192): WARNING **: Can not stat /tmp/orbit-foobar-282828a8

GConf Error: Failed to contact configuration server; some possible causes are th
at you need to enable TCP/IP networking for ORBit, or you have stale NFS locks d
ue to a system crash. See http://projects.gnome.org/gconf/ for information. (Det
ails - 1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0)
GConf Error: Failed to contact configuration server; some possible causes are th
at you need to enable TCP/IP networking for ORBit, or you have stale NFS locks d
ue to a system crash. See http://projects.gnome.org/gconf/ for information. (Det
ails - 1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0)
GConf Error: Failed to contact configuration server; some possible causes are th
at you need to enable TCP/IP networking for ORBit, or you have stale NFS locks d
ue to a system crash. See http://projects.gnome.org/gconf/ for information. (Det
ails - 1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0)
GConf Error: Failed to contact configuration server; some possible causes are th
at you need to enable TCP/IP networking for ORBit, or you have stale NFS locks d
ue to a system crash. See http://projects.gnome.org/gconf/ for information. (Det
ails - 1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0)
GConf Error: Failed to contact configuration server; some possible causes are th
at you need to enable TCP/IP networking for ORBit, or you have stale NFS locks d
ue to a system crash. See http://projects.gnome.org/gconf/ for information. (Det
ails - 1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0)
GConf Error: Failed to contact configuration server; some possible causes are th
at you need to enable TCP/IP networking for ORBit, or you have stale NFS locks d
ue to a system crash. See http://projects.gnome.org/gconf/ for information. (Det
ails - 1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0)
GConf Error: Failed to contact configuration server; some possible causes are th
at you need to enable TCP/IP networking for ORBit, or you have stale NFS locks d
ue to a system crash. See http://projects.gnome.org/gconf/ for information. (Det
ails - 1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0)
GConf...

Read more...

Chris Coulson (chrisccoulson) wrote :

Just because you have a particular issue doesn't mean that everybody who tries your instructions are guaranteed to experience the same issue that you're having.

Your instructions don't work anyway - your use of usermod is syntactically incorrect, and your steps don't actually create a home folder for the new user, so the users account doesn't work anyway. If I tell useradd to create the home folder, then I have no such issues with the new user account

I also get this error - each time I run Firefox on my new Karmic install.

iblue (iblue) wrote :

Chris, you're right. The correct steps to reproduce the bug are:
# adduser foobar
# usermod -G adm,disk,dialout,cdrom,plugdev,lpadmin,admin,sambashare,mythtv -a foobar
Eventually you need to remove some of these groups on your system.

Michał, can you post the output you get when running "groups" in a terminal?

eris23 (jdkatz23) wrote :

I'm getting the same error after latest updates.

$ groups
mgol adm dialout cdrom plugdev lpadmin admin sambashare

But I don't know if it's relevant now as my problems disappeared (or at least it seems they did) after last bunch of updates.

I have the same problem as you do. The same error. This appears to be a breakage by some of the latest Karmic updates.

Changed in gconf (Ubuntu):
status: New → Confirmed
Andy Ruddock (andy-ruddock) wrote :

I have a similar error when running seamonkey & firefox over ssh, but I get

(Details 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-3sJfPhARd0: Connection refused)

where the socket name changes each time. Is this the same issue?

Andy Ruddock (andy-ruddock) wrote :

Answering myself - it seems that my issue is caused by incorrect permissions on files in ~/.dbus/session-bus

Changed in gconf (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers