Bugzilla – Bug 433781
[Y2-GNOME-Control-Center] Every action in Yast2 pop up an error message (contacting gconf)
Last modified: 2008-10-16 14:17:28 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.)"
Please attach y2logs. If you are in doubt follow: http://en.opensuse.org/Bugs/YaST Thanks!
*ping*
Created attachment 245881 [details] y2loags here it is, sorry for the dealy, I never received the NEEDINFO mail
YaST2-GNOME control center + Gtk UI -> GNOME maintainers
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 ***