Bug 433781

Summary:	[Y2-GNOME-Control-Center] Every action in Yast2 pop up an error message (contacting gconf)
Product:	[openSUSE] openSUSE 11.1	Reporter:	Stephane Delcroix <sdelcroix>
Component:	GNOME	Assignee:	E-mail List <gnome-bugs>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	forgotten_h13THG8RK1, mmeeks
Version:	Beta 2
Target Milestone:	---
Hardware:	x86-64
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	y2loags

Description Stephane Delcroix 2008-10-09 08:56:48 UTC

Opening Yast2, and clicking on any button pop up a error dialog saying:

"An error occurred while loading or saving configuration information for y2controlcenter-gnome. Some of your configuration settings may not work properly."

Details >

"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: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
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: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
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: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
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: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
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: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)"

Comment 1 Michal Seben 2008-10-09 11:36:51 UTC

Please attach y2logs. If you are in doubt follow:

http://en.opensuse.org/Bugs/YaST

Thanks!

Comment 2 Christoph Thiel 2008-10-15 11:44:19 UTC

*ping*

Comment 3 Stephane Delcroix 2008-10-16 07:49:51 UTC

Created attachment 245881 [details]
y2loags

here it is, sorry for the dealy, I never received the NEEDINFO mail

Comment 4 Stefan Hundhammer 2008-10-16 09:40:13 UTC

YaST2-GNOME control center + Gtk UI -> GNOME maintainers

Comment 5 Forgotten User h13THG8RK1 2008-10-16 14:17:28 UTC

The following bug report is two fold, and one of them is the one you report,
which boils down to a gnomesu bug.

*** This bug has been marked as a duplicate of bug 416259 ***