Firefox Error Message - Seems to have been caused by previous error-report crashing gconf

[TDJACR]

Binary package hint: firefox

Error message:

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)
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)
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)
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)
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)

Reproduce: Close Firefox, Open Firefox.

[TDJACR (thedjatclubrock)]

This was after an Upgrade to Karmic Beta

[Brent Dunnaway (bdunnaway)]

I, too, am getting these errors. Both in Karmic Beta, and I also got them in Alpha (Daily)

The best solution (temporary work-around) I can give you for the moment, is to

sudo killall gconfd-2

and then try to do whatever you were doing again. That will automatically open a fresh instance of gconfd-2. It seems to be some kind of problem with gconf2 and .authorization (sp?) files (my terrible memory... I hope I got that correct.)

I'm guessing it's a regression of some sort. I have found posts about this error dating back to 2004. I've only just started experiencing it with Karmic builds, however.

[John Vivirito (gnomefreak)]

Changed package to correct package

[Rahul Hada (hada-rahul)]

today i have faced the same problem but now its working fine..
Thank you Brent Dunnaway.

Cheers,
Rahul

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.