[Error] Starting Nautilus as root.

Questions about applications and software
Forum rules
Before you post please read this

[Error] Starting Nautilus as root.

Postby BlaXun on Wed Feb 18, 2009 10:22 am

Hiya everybody.

Yesterday I installed Mint on my new Acer Aspire One.

Now I ran into a small Problem:

Whenevr I use the console as root and then try to start nautilus as root I get teh following error message:

Code: Select all
(nautilus:6064): GnomeUI-WARNING **: While connecting to session manager:
None of the authentication protocols specified are supported.

(nautilus:6064): Eel-WARNING **: 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://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.)

(nautilus:6064): Eel-WARNING **: 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://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.)

(nautilus:6064): Eel-WARNING **: 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://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.)
GConf warning: failure listing pairs in `/apps/nautilus/preferences': 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.)
(nautilus:6064): Eel-WARNING **: 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://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.)

(nautilus:6064): Eel-WARNING **: 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://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.)

(nautilus:6064): Eel-WARNING **: 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://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.)

(nautilus:6064): Eel-WARNING **: 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://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.)


Yeah...this looks pretty messy...but I didnt change anything on the system...so I wonder why I get this.

Maybe somebody else experienced this Problem too?

I'd be glad to get some help here =)

Best regards
BlaXun
BlaXun
 

Linux Mint is funded by ads and donations.
 

Re: [Error] Starting Nautilus as root.

Postby Husse on Thu Feb 19, 2009 7:53 am

Whenevr I use the console as root and then try to start nautilus as root

You have to explain what you do....
Image
Don't fix it if it ain't broken, don't break it if you can't fix it
Husse
Level 21
Level 21
 
Posts: 19703
Joined: Sun Feb 11, 2007 7:22 am
Location: Near Borås Sweden

Re: [Error] Starting Nautilus as root.

Postby schnebg on Thu Mar 05, 2009 12:13 pm

See the link at http://bbs.archlinux.org/viewtopic.php?id=56215

I encountered this issue in Debian when I had a mixed configuration of Gnome packages (some 2.22, other 2.24).

In Debian, I used synaptic to select "sid" as my preferred distro and reinstalled the policykit and policykit-gnome packages.
schnebg
Level 1
Level 1
 
Posts: 1
Joined: Thu Mar 05, 2009 11:59 am


Return to Software & Applications

Who is online

Users browsing this forum: No registered users and 11 guests