Page 1 of 3 123 LastLast
Results 1 to 10 of 21

Thread: Nautilus = mulitple windows on usb plug in on KDE after installing Dropbox

  1. #1
    Join Date
    Sep 2010
    Location
    Antananarivo, Madagascar
    Posts
    103

    Default Nautilus = mulitple windows on usb plug in on KDE after installing Dropbox

    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!

  2. #2
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    36,733
    Blog Entries
    20

    Default Re: Nautilus = mulitple windows on usb plug in on KDE after installing Dropbox

    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?
    Leap 15.1_KDE
    My Articles Was I any help? If yes: Click the star below

  3. #3
    Join Date
    Sep 2010
    Location
    Antananarivo, Madagascar
    Posts
    103

    Default Re: Nautilus = mulitple windows on usb plug in on KDE after installing Dropbox

    Quote Originally Posted by caf4926 View Post
    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

  4. #4
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    36,733
    Blog Entries
    20

    Default Re: Nautilus = mulitple windows on usb plug in on KDE after installing Dropbox

    Quote Originally Posted by ClrScr View Post
    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
    Leap 15.1_KDE
    My Articles Was I any help? If yes: Click the star below

  5. #5
    Join Date
    Sep 2010
    Location
    Antananarivo, Madagascar
    Posts
    103

    Default Re: Nautilus = mulitple windows on usb plug in on KDE after installing Dropbox

    Thanks

    I use 11.3 with KDE as supplied.

  6. #6
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    36,733
    Blog Entries
    20

    Default Re: Nautilus = mulitple windows on usb plug in on KDE after installing Dropbox

    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

    Code:
    zypper ar -f http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_11.3 kde-extra
    Code:
    zypper ar -f http://download.opensuse.org/repositories/openSUSE:/11.3:/Contrib/standard contrib
    Code:
    zypper ref
    (a) to accept

    Code:
    zypper in dropbox kdropbox
    Once that is done. Open a normal user terminal and do this:

    Code:
    dropbox start -i
    Leap 15.1_KDE
    My Articles Was I any help? If yes: Click the star below

  7. #7
    Join Date
    Sep 2010
    Location
    Antananarivo, Madagascar
    Posts
    103

    Default Re: Nautilus = mulitple windows on usb plug in on KDE after installing Dropbox

    Quote Originally Posted by caf4926 View Post
    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
    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
    Code:
    (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
    Code:
    ** (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!

  8. #8
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    36,733
    Blog Entries
    20

    Default Re: Nautilus = mulitple windows on usb plug in on KDE after installing Dropbox

    Are you using gnome at all. How would it be if we deleted the gnome settings to prevent this happening?
    Leap 15.1_KDE
    My Articles Was I any help? If yes: Click the star below

  9. #9
    Join Date
    Sep 2010
    Location
    Antananarivo, Madagascar
    Posts
    103

    Default Re: Nautilus = mulitple windows on usb plug in on KDE after installing Dropbox

    Quote Originally Posted by caf4926 View Post
    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!

  10. #10
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,761

    Default Re: Nautilus = mulitple windows on usb plug in on KDE after installing Dropbox

    They should be in you home directory ~/.gnome folder.

Page 1 of 3 123 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •