b4j4 / indicator-kdeconnect

AppIndicator for KDE Connect
GNU Lesser General Public License v2.1
371 stars 38 forks source link

caja integration #151

Open brokoli-mate opened 5 years ago

brokoli-mate commented 5 years ago

Ubuntu mate 18.04. Caja does not have entry to send files. Adding script to scripts folders creates entry , but it does nothing. Also browse device does not work.

b4j4 commented 5 years ago

Have you try this one?

brokoli-mate commented 5 years ago

It is already present in the /usr/share/caja-python/extensions kde-connect-folder

but not visible in the caja preferences->extensions kde-connect-list

When i add it to scripts folder - action appears, and i get the "cross" , but nothing happens when i select file(s).

FrancescoCappio commented 5 years ago

Same problem in Arch Linux, I also have a stack Trace visible when starting Caja from Terminal:

Traceback (most recent call last):
  File "/usr/share/caja-python/extensions/kdeconnect-send-caja.py", line 9, in <module>
    gi.require_version('Caja', '3.0')
  File "/usr/lib/python2.7/site-packages/gi/__init__.py", line 121, in require_version
    (namespace, loaded_version))
ValueError: Namespace Caja is already loaded with version 2.0
kescherCode commented 4 years ago

I have found this while investigating this issue on Manjaro:

Using python version sys.version_info(major=2, minor=7, micro=17, releaselevel='final', serial=0)
File "/usr/share/caja-python/extensions/kdeconnect-send.py", line 28
    self.dbus = Gio.DBusProxy.new_for_bus_sync(
                                              ^
IndentationError: unindent does not match any outer indentation level

Fixing this indeed kinda wrongly indented element reveals:

Traceback (most recent call last):
  File "kdeconnect-send.py", line 9, in <module>
    gi.require_version('Caja', '3.0')
  File "/usr/lib/python2.7/site-packages/gi/__init__.py", line 133, in require_version
    (namespace, version))
ValueError: Namespace Caja not available for version 3.0
kescherCode commented 4 years ago

Changing the line mentioned in the second error to say "2.0" resolves the issue for me.