Re: No puedo inicar nautilus como root debian 6
Si funciono, muchas gracias
2011/6/27, Isaac Abreu Rodríguez <caasi1024@gmail.com>:
> prueba con
>
> nazhir@debian:~$ gksu nautilus
>
>
> El 27/06/11 19:36, Nazhir Jesus Amaya Tejera escribió:
>> Saludos, al querer hacer unas modificaciones a unos archivos queria
>> acceder a nautilus como root, pero no pude, al fin de cuentas, hice
>> todo por terminal, pero sin embargo, aun no puedo acceder a nautilus
>> como root, al tratar de iniciar desde al terminal me general el
>> siguiente error, alguna idea??
>>
>>
>>
>> nazhir@debian:~$ su
>> Contraseña:
>> root@debian:/home/nazhir# nautilus
>>
>> (nautilus:4958): EggSMClient-WARNING **: Failed to connect to the
>> session manager: None of the authentication protocols specified are
>> supported
>>
>>
>> (nautilus:4958): Eel-WARNING **: Error de GConf:
>> Failed to contact configuration server; the most common cause is a
>> missing or misconfigured D-Bus session bus daemon. See
>> http://projects.gnome.org/gconf/ for information. (Details - 1: Falló
>> al obtener la conexión con la sesión: 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:4958): Eel-WARNING **: Error de GConf:
>> Failed to contact configuration server; the most common cause is a
>> missing or misconfigured D-Bus session bus daemon. See
>> http://projects.gnome.org/gconf/ for information. (Details - 1: Falló
>> al obtener la conexión con la sesión: 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:4958): Eel-WARNING **: Error de GConf:
>> Failed to contact configuration server; the most common cause is a
>> missing or misconfigured D-Bus session bus daemon. See
>> http://projects.gnome.org/gconf/ for information. (Details - 1: Falló
>> al obtener la conexión con la sesión: 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:4958): Eel-WARNING **: Error de GConf:
>> Failed to contact configuration server; the most common cause is a
>> missing or misconfigured D-Bus session bus daemon. See
>> http://projects.gnome.org/gconf/ for information. (Details - 1: Falló
>> al obtener la conexión con la sesión: 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.)
>> Aviso GConf: ha ocurrido un error al listar los pares en
>> «/apps/nautilus/preferences»: Failed to contact configuration server;
>> the most common cause is a missing or misconfigured D-Bus session bus
>> daemon. See http://projects.gnome.org/gconf/ for information. (Details
>> - 1: Falló al obtener la conexión con la sesión: 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.)Aviso GConf: ha
>> ocurrido un error al listar los pares en «/desktop/gnome/file_views»:
>> Failed to contact configuration server; the most common cause is a
>> missing or misconfigured D-Bus session bus daemon. See
>> http://projects.gnome.org/gconf/ for information. (Details - 1: Falló
>> al obtener la conexión con la sesión: 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.)Aviso GConf: ha
>> ocurrido un error al listar los pares en «/desktop/gnome/background»:
>> Failed to contact configuration server; the most common cause is a
>> missing or misconfigured D-Bus session bus daemon. See
>> http://projects.gnome.org/gconf/ for information. (Details - 1: Falló
>> al obtener la conexión con la sesión: 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.)Aviso GConf: ha
>> ocurrido un error al listar los pares en «/desktop/gnome/lockdown»:
>> Failed to contact configuration server; the most common cause is a
>> missing or misconfigured D-Bus session bus daemon. See
>> http://projects.gnome.org/gconf/ for information. (Details - 1: Falló
>> al obtener la conexión con la sesión: 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.)Aviso GConf: ha
>> ocurrido un error al listar los pares en «/apps/nautilus/desktop»:
>> Failed to contact configuration server; the most common cause is a
>> missing or misconfigured D-Bus session bus daemon. See
>> http://projects.gnome.org/gconf/ for information. (Details - 1: Falló
>> al obtener la conexión con la sesión: 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.)Aviso GConf: ha
>> ocurrido un error al listar los pares en «/apps/nautilus/icon_view»:
>> Failed to contact configuration server; the most common cause is a
>> missing or misconfigured D-Bus session bus daemon. See
>> http://projects.gnome.org/gconf/ for information. (Details - 1: Falló
>> al obtener la conexión con la sesión: 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.)Aviso GConf: ha
>> ocurrido un error al listar los pares en
>> «/apps/nautilus/desktop-metadata»: Failed to contact configuration
>> server; the most common cause is a missing or misconfigured D-Bus
>> session bus daemon. See http://projects.gnome.org/gconf/ for
>> information. (Details - 1: Falló al obtener la conexión con la
>> sesión: 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:4958): Eel-WARNING **: Error de GConf:
>> Failed to contact configuration server; the most common cause is a
>> missing or misconfigured D-Bus session bus daemon. See
>> http://projects.gnome.org/gconf/ for information. (Details - 1: Falló
>> al obtener la conexión con la sesión: 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:4958): Eel-WARNING **: Error de GConf:
>> Failed to contact configuration server; the most common cause is a
>> missing or misconfigured D-Bus session bus daemon. See
>> http://projects.gnome.org/gconf/ for information. (Details - 1: Falló
>> al obtener la conexión con la sesión: 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:4958): Eel-WARNING **: Error de GConf:
>> Failed to contact configuration server; the most common cause is a
>> missing or misconfigured D-Bus session bus daemon. See
>> http://projects.gnome.org/gconf/ for information. (Details - 1: Falló
>> al obtener la conexión con la sesión: 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:4958): Eel-WARNING **: Error de GConf:
>> Failed to contact configuration server; the most common cause is a
>> missing or misconfigured D-Bus session bus daemon. See
>> http://projects.gnome.org/gconf/ for information. (Details - 1: Falló
>> al obtener la conexión con la sesión: 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:4958): Unique-DBus-WARNING **: Unable to open a connection
>> to the session bus: 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:4958): Unique-DBus-WARNING **: Unable to connect to the
>> running instance, aborting.
>>
>> (nautilus:4958): Unique-DBus-WARNING **: Unable to open a connection
>> to the session bus: 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:4958): Unique-DBus-WARNING **: Unable to connect to the
>> running instance, aborting.
>> root@debian:/home/nazhir#
>>
>>
>
>
> --
> To UNSUBSCRIBE, email to debian-user-spanish-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
> Archive: [🔎] 4E08C662.3060207@gmail.com">http://lists.debian.org/[🔎] 4E08C662.3060207@gmail.com
>
>
Reply to: