PDA

View Full Version : Nautilus doesn't work after switching from KDE to GNOME!



sadaltager
20th January 2010, 12:59 AM
Hello.

I recently switched my desktop environment from KDE-4.3.4 to GNOME-2.28-2 and I did that by installing most of the gnome-packages and uninstalling pretty much all of the kde-ones. After reboot everything worked fine except the file browser that doesn't seem to care about my feelings. It launches and when I try to kill the process the status changes from sleeping to uninterruptible and then back to sleeping. The only way is to reboot but that isn't a solution.
Any thoughts everyone?

---------- Post added at 01:59 AM CST ---------- Previous post was at 01:22 AM CST ----------

When trying to launch nautilus via command-line I get the following output:

(nautilus:2314): Unique-DBus-WARNING **: Error while sending message: 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.

JEO
20th January 2010, 03:34 AM
You could check to see if dbus daemon is running properly, what is the output of the following command?

ps -ef |grep dbus

sadaltager
20th January 2010, 08:17 AM
[Mircea@fedora ~]$ ps -ef |grep dbus
dbus 906 1 0 09:09 ? 00:00:00 dbus-daemon --system
gdm 1481 1 0 09:10 ? 00:00:00 /usr/bin/dbus-launch --exit-with-session
Mircea 1604 1 0 09:10 ? 00:00:00 dbus-launch --sh-syntax --exit-with-session
Mircea 1605 1 0 09:10 ? 00:00:00 /bin/dbus-daemon --fork --print-pid 7 --print-address 9 --session
Mircea 2322 2282 0 09:12 pts/0 00:00:00 grep dbus
[Mircea@fedora ~]$

JEO
20th January 2010, 08:54 AM
dbus daemon looks fine. Not sure what is causing that error message.

Mordocai
20th January 2010, 11:06 PM
I would try reinstalling nautilus.

first yum reinstall nautilus, if that doesn't work you could always try doing it "manually" with yum erase nautilus; yum install nautilus.

That's my only idea...

sadaltager
21st January 2010, 12:27 AM
already done the reinstall with no effect. I will try the manual reinstall. thanks.

sadaltager
23rd January 2010, 12:02 AM
manual reinstall also had no effect.
I removed nautilus completely and rebooted.
After reinstalling I had the following error:

bash-4.0$ nautilus
Bazaar nautilus module initialized
Initializing nautilus-open-terminal extension
Initializing nautilus-search-tool extension
VST_PATH not set, defaulting to /home/Mircea/vst:/usr/local/lib/vst:/usr/lib/vst
sys:1: Warning: cannot register existing type `GstBaseVideoCodec'
sys:1: Warning: g_once_init_leave: assertion `initialization_value != 0' failed
sys:1: Warning: g_type_register_static: assertion `parent_type > 0' failed

(plugin-scanner:2629): GStreamer-CRITICAL **: gst_element_register: assertion `g_type_is_a (type, GST_TYPE_ELEMENT)' failed

more, I could kill the process via system monitor. after reboot, I was back at the beginning.
further more, running nautilus as root gave the following:

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


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

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

this is getting depressing.
...

Quasaur
10th February 2010, 05:16 PM
I'm having the same problem...

I have 2 userids on my laptop: one for normal ops and a 2nd for webdevelopment.

I hardly ever use the 2nd, but now I'm rebuilding mysite and need nautilus to work on it.

Nautilus works fine on my main account, but not at all on the 2nd...

...and get this: dolphin works fine!

Dies
10th February 2010, 06:45 PM
Make sure 'gnome-settings-daemon' is running.

And please post the output you get when starting or attempting to start nautilus from a terminal, otherwise there's not much to go on.

Quasaur
14th February 2010, 02:09 PM
Make sure 'gnome-settings-daemon' is running.

And please post the output you get when starting or attempting to start nautilus from a terminal, otherwise there's not much to go on.

Here's my output:


(nautilus:2488): Unique-DBus-WARNING **: Error while sending message: 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.


my logs have no other info.

old noob
15th February 2010, 04:37 AM
I ran into this problem on a centos system of mine. I never figured out what package I was missing but try to install all of the gnome packages under package kit that worked for me.

David Batson
15th February 2010, 01:03 PM
Why not use dolphin instead? That is the default file manager for KDE (at least in Mandriva 2010 KDE that's true).

http://dolphin.kde.org/features.html

EDIT: Oops. I got it backwards. I was thinking you went from Gnome > KDE, but in fact you went from KDE > Gnome.
I read on another forum that such DBus errors are often only fixed by a fresh install.

Quasaur
19th February 2010, 02:22 PM
I ran into this problem on a centos system of mine. I never figured out what package I was missing but try to install all of the gnome packages under package kit that worked for me.

Good idea...

...so I checked all available packages for:
*gnome*
*packagekit*
*dbus*
*gconf*

and installed them, removing the *-devel* packages.

The error for my 2nd account has now changed:


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


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

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

old noob
19th February 2010, 05:04 PM
Check your users and groups settings on the non-functioning account. See if adding that account to "wheel" helps.

Quasaur
26th February 2010, 03:50 PM
the problem was resolved by removing gstreamer-plugins-bad...dont know why it worked, though.

zmdmw52
26th February 2010, 04:18 PM
Hello.

I recently switched my desktop environment from KDE-4.3.4 to GNOME-2.28-2 and I did that by installing most of the gnome-packages and uninstalling pretty much all of the kde-ones.
You can try re-installing the KDE and GNOME libs. GNOME and KDE can both be there on the same Fedora install and you can choose b/w either at Login (from the 'Session' tab).
Also GNOME and KDE apps can be used in either session, provided the respective libraries are installed.