Problema con Nautilus sotto Debian

[usag]

Ciao a tutti,
come da titolo, ho un problema al lancio di Nautilus sotto Debian 6.0, fresca fresca di nuova installazione. Nella 5.0 che avevo fino a 3 giorni fa, questo problema non si poneva.
Praticamente quando da shell do il comando "Nautilus" (previa autenticazione root, ovviamente), accenna ad aprirsi la finestra di navigazione da utente root per un decimo di secondo, richiudendosi subito; nel terminale, mi viene una valanga di messaggi che vado a postare:

Codice: Seleziona tutto

nautilus

(nautilus:2917): EggSMClient-WARNING **: Failed to connect to the session manager: None of the authentication protocols specified are supported


(nautilus:2917): Eel-WARNING **: Errore 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: Recupero delle connessione alla sessione non riuscito: 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:2917): Eel-WARNING **: Errore 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: Recupero delle connessione alla sessione non riuscito: 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:2917): Eel-WARNING **: Errore 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: Recupero delle connessione alla sessione non riuscito: 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:2917): Eel-WARNING **: Errore 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: Recupero delle connessione alla sessione non riuscito: 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.)
Avviso di GConf: enumerazione delle coppie in "/apps/nautilus/preferences" non riuscita: 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: Recupero delle connessione alla sessione non riuscito: 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.)Avviso di GConf: enumerazione delle coppie in "/desktop/gnome/file_views" non riuscita: 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: Recupero delle connessione alla sessione non riuscito: 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.)Avviso di GConf: enumerazione delle coppie in "/desktop/gnome/background" non riuscita: 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: Recupero delle connessione alla sessione non riuscito: 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.)Avviso di GConf: enumerazione delle coppie in "/desktop/gnome/lockdown" non riuscita: 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: Recupero delle connessione alla sessione non riuscito: 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.)Avviso di GConf: enumerazione delle coppie in "/apps/nautilus/desktop" non riuscita: 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: Recupero delle connessione alla sessione non riuscito: 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.)Avviso di GConf: enumerazione delle coppie in "/apps/nautilus/icon_view" non riuscita: 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: Recupero delle connessione alla sessione non riuscito: 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.)Avviso di GConf: enumerazione delle coppie in "/apps/nautilus/desktop-metadata" non riuscita: 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: Recupero delle connessione alla sessione non riuscito: 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:2917): Eel-WARNING **: Errore 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: Recupero delle connessione alla sessione non riuscito: 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:2917): Eel-WARNING **: Errore 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: Recupero delle connessione alla sessione non riuscito: 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:2917): Eel-WARNING **: Errore 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: Recupero delle connessione alla sessione non riuscito: 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:2917): Eel-WARNING **: Errore 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: Recupero delle connessione alla sessione non riuscito: 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:2917): 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:2917): Unique-DBus-WARNING **: Unable to connect to the running instance, aborting.

(nautilus:2917): 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:2917): Unique-DBus-WARNING **: Unable to connect to the running instance, aborting.

Lo stesso identico problema me lo dava anche con Arch Linux, che risolsi agevolando il lancio di Nautilus "accompagnando" il comando con d-bus, ma qui non funziona. praticamente non riesco a navigare fra le cartelle in qualità di super utente, cosa che mi da molto fastidio, avendo la partizione "Dati" cifrata, oltre ad aver "costretto" (tramite la modifica del file /etc/fstab) il s.o. a montare e navigare fra i vari volumi ESCLUSIVAMENTE in modalità di super utente.
Il sistema operativo, come ripeto, è nuovo di pacca, dal momento che l'ho installato appena 2 giorni fa (prima avevo la 5.0).
Grazie ad ognuno di voi che voglia rispondermi .