Hi Giys
Isnce I installed Dropbox every time I insert a usb device nautilus opens a bunch of identical windows. I think my records i 12 so far.
All wqith the error
DBus error org.gtk.Private.RemoteVolumeMonitor.Failed: An operation is already pending
I can not eject the device via dolphin or erase anything via dolphin
Solutions please!
Thanks!
Sounds like you have installed the nautilus side to dropbox in kde (which works for me) but for you not so much.
There is a kdropbox
Did you install using the Contrib repo?
BTW, you device can be ejected in Nautilus, that’s what is holding on to the device so kde can’t eject it?
Uhm, what does this mean? hehe!
I followed the instructions on this page
Dropbox without Gnome :: antrix.net
What do I do now?
How do I “disable” nautilus from being what appears to be the default file browser? And reactivate dolphin?
Thanks
I have to run right now.
I’ll come back to you when I have more time.
Basically you need to uninstall what you have done.
Delete the hidden folders: .dropbox and .dropbox-dist
Can you just confirm what version of openSUSE you are using
Thanks
I use 11.3 with KDE as supplied.
Once you have cleared up the previous attempt.
Please add these repos
You need to be in a terminal and su -
Use your mouse to copy and paste the following code
zypper ar -f http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_11.3 kde-extra
zypper ar -f http://download.opensuse.org/repositories/openSUSE:/11.3:/Contrib/standard contrib
zypper ref
(a) to accept
zypper in dropbox kdropbox
Once that is done. Open a normal user terminal and do this:
dropbox start -i
Thanks a lot! I did this and it worked great except that the problem is not solved!
I still get multiple instances of Nautilus. Stil can not delete or eject via dolphin and also I had the following errors in terminal
(nautilus:16773): 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:16773): Tracker-CRITICAL **: Could not connect to the D-Bus 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:16773): GVFS-RemoteVolumeMonitor-WARNING **: cannot connect to the session bus: org.freedesktop.DBus.Error.NoReply: 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.
as well as
** (nautilus:16773): CRITICAL **: nautilus_inhibit_power_manager: assertion `proxy != NULL' failed
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 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 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 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 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:16773): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
The errors were repeated quite a few times. I did not copy the whole error message output but i believe that there is at least one copy of each error.
thanks!
Are you using gnome at all. How would it be if we deleted the gnome settings to prevent this happening?
I dont use Gnome at all.
Tell me how to delete what and I will give it a go!
Thanks!
They should be in you home directory ~/.gnome folder.
I think you will need to delete:
.config
.gnome2
.local
If you view hidden files in your /home/yourusername
you should see them
I suggest you reboot after doing it.
Oh and make sure you don’t have nautilus-dropbox installed.
When I open yast etc and look at what is installed there is
dropbox
and
kdropbox
Should I uninstall dropbox, delete the mentioned directories again and reboot again?
Thanks
As far as I know, you need ‘dropbox and kdropbox’ just not the nautilus-dropbox.
*But as I said earlier, although I use kde, I also use Gnome and have only dropbox and nautilus-dropbox. Nautilus is not a problem for me in kde.
Caf4926, thanks. I tried it but it didnt work.
What if I just uninstall nautilus?
You could try but it may be tricky
Try checking this when you do
http://dl.dropbox.com/u/10573557/Software%20Management/remove_depend.png
Why tricky? Are some applications or processes “inherently” dependent of nautilus?
It’s a key part to Gnome, which you may have inadvertently installed more of than you realise.
Try as I suggest, you can always abort
Well I am going to give it a go. Recently I inserted 2 usb devices after each other and 28 windows opened spontaneously as well as 42 error messages. All the clicking is wearing out my mouse!
It worked
Thanks for your help Caf. They should make you something important here on the site! 
Now, how do you associate a specific program, Dolphin with the autorun? That is when you insert an usb dolphin opens it and not something else. Thats the way it was before.