Bug#602310: does not start as root (# nautilus )
Mansour Karami
karami.mansour at gmail.com
Wed Nov 3 16:51:14 UTC 2010
Package: nautilus
Version: 2.28.4-1
Severity: important
here is what happens when i want to run nautilus on my dell inspiron 1564 with debian squeeze :
root at debian:/home/mansour# nautilus
(nautilus:2788): EggSMClient-WARNING **: Failed to connect to the session manager: None of the authentication protocols specified are supported
(nautilus:2788): 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://projects.gnome.org/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:2788): 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://projects.gnome.org/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:2788): 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://projects.gnome.org/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:2788): 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://projects.gnome.org/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://projects.gnome.org/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 `/desktop/gnome/file_views': 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://projects.gnome.org/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 `/desktop/gnome/background': 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://projects.gnome.org/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 `/desktop/gnome/lockdown': 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://projects.gnome.org/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/desktop': 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://projects.gnome.org/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/icon_view': 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://projects.gnome.org/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/desktop-metadata': 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://projects.gnome.org/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:2788): 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://projects.gnome.org/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:2788): 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://projects.gnome.org/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:2788): 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://projects.gnome.org/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:2788): 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://projects.gnome.org/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:2788): 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:2788): Unique-DBus-WARNING **: Unable to connect to the running instance, aborting.
(nautilus:2788): 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:2788): Unique-DBus-WARNING **: Unable to connect to the running instance, aborting.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages nautilus depends on:
ii desktop-file-utils 0.15-2 Utilities for .desktop files
ii gvfs 1.4.3-1 userspace virtual filesystem - ser
ii libatk1.0-0 1.30.0-1 The ATK accessibility toolkit
ii libbeagle1 0.3.9-1 library for accessing beagle using
ii libc6 2.11.2-6 Embedded GNU C Library: Shared lib
ii libcairo2 1.8.8-2 The Cairo 2D vector graphics libra
ii libdbus-glib-1-2 0.84-1 simple interprocess messaging syst
ii libexempi3 2.1.1-1 library to parse XMP metadata (Lib
ii libexif12 0.6.19-1 library to parse EXIF files
ii libgail18 2.18.6-1 GNOME Accessibility Implementation
ii libgconf2-4 2.28.0-1 GNOME configuration database syste
ii libglib2.0-0 2.24.2-1 The GLib library of C routines
ii libglib2.0-data 2.22.4-1 Common files for GLib library
ii libgnome-desktop-2-11 2.28.2-1 Utility library for loading .deskt
ii libgtk2.0-0 2.18.6-1 The GTK+ graphical user interface
ii libice6 2:1.0.6-1 X11 Inter-Client Exchange library
ii libnautilus-extension1 2.28.4-1 libraries for nautilus components
ii libpango1.0-0 1.26.2-1 Layout and rendering of internatio
ii libselinux1 2.0.89-4 SELinux runtime shared libraries
ii libsm6 2:1.1.1-1 X11 Session Management library
ii libtrackerclient0 0.6.95-3 metadata database, indexer and sea
ii libunique-1.0-0 1.1.6-1 Library for writing single instanc
ii libx11-6 2:1.3.3-1 X11 client-side library
ii libxml2 2.7.6.dfsg-2+b1 GNOME XML library
ii libxrender1 1:0.9.5-1 X Rendering Extension client libra
ii nautilus-data 2.28.4-1 data files for nautilus
ii shared-mime-info 0.70-1 FreeDesktop.org shared MIME databa
Versions of packages nautilus recommends:
pn app-install-dat <none> (no description available)
ii brasero 2.28.3-2 CD/DVD burning application for GNO
ii consolekit 0.4.1-3 framework for defining and trackin
ii desktop-base 5.0.5 common files for the Debian Deskto
ii eject 2.1.5+deb1+cvs20081104-7 ejects CDs and operates CD-Changer
ii gvfs-backends 1.4.3-1 userspace virtual filesystem - bac
ii librsvg2-common 2.26.0-1 SAX-based renderer library for SVG
ii synaptic 0.63 Graphical package manager
Versions of packages nautilus suggests:
ii eog 2.28.2-1 Eye of GNOME graphics viewer progr
ii evince [pdf-viewer] 2.28.2-1 Document (postscript, pdf) viewer
ii totem 2.28.5-1 A simple media player for the GNOM
pn tracker <none> (no description available)
pn xdg-user-dirs <none> (no description available)
-- no debconf information
More information about the pkg-gnome-maintainers
mailing list