New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Indicator not showing up in Ubuntu 15.10 #31

Open
metalbrick opened this Issue Nov 28, 2015 · 20 comments

Comments

Projects
None yet
@metalbrick

metalbrick commented Nov 28, 2015

the KDE-Connect Worked perfectly, but there's no indicator in the panel, thus I can no longer use the features such like "Browse device" conveniently.

@Deus-Rex

This comment has been minimized.

Show comment
Hide comment
@Deus-Rex

Deus-Rex Nov 29, 2015

Having same problem.

If I try to start the indicator using terminal, I get the following:

** Message: KDEConnectManager.vala:32: KDE Connect daemon found ** Message: Device.vala:73: device : /modules/kdeconnect/devices/1b34fcf462e1729 ** Message: Device.vala:263: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method 'isReachable' in interface 'org.kde.kdeconnect.device' at object path '/modules/kdeconnect/devices/1b34fcf462e1729' (signature '') ** Message: Device.vala:263: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method 'isReachable' in interface 'org.kde.kdeconnect.device' at object path '/modules/kdeconnect/devices/1b34fcf462e1729' (signature '') ** Message: Device.vala:263: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method 'isReachable' in interface 'org.kde.kdeconnect.device' at object path '/modules/kdeconnect/devices/1b34fcf462e1729' (signature '') ** Message: Device.vala:263: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method 'isReachable' in interface 'org.kde.kdeconnect.device' at object path '/modules/kdeconnect/devices/1b34fcf462e1729' (signature '')

Deus-Rex commented Nov 29, 2015

Having same problem.

If I try to start the indicator using terminal, I get the following:

** Message: KDEConnectManager.vala:32: KDE Connect daemon found ** Message: Device.vala:73: device : /modules/kdeconnect/devices/1b34fcf462e1729 ** Message: Device.vala:263: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method 'isReachable' in interface 'org.kde.kdeconnect.device' at object path '/modules/kdeconnect/devices/1b34fcf462e1729' (signature '') ** Message: Device.vala:263: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method 'isReachable' in interface 'org.kde.kdeconnect.device' at object path '/modules/kdeconnect/devices/1b34fcf462e1729' (signature '') ** Message: Device.vala:263: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method 'isReachable' in interface 'org.kde.kdeconnect.device' at object path '/modules/kdeconnect/devices/1b34fcf462e1729' (signature '') ** Message: Device.vala:263: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method 'isReachable' in interface 'org.kde.kdeconnect.device' at object path '/modules/kdeconnect/devices/1b34fcf462e1729' (signature '')

@mank319

This comment has been minimized.

Show comment
Hide comment
@mank319

mank319 Dec 2, 2015

I'm getting the same list of error messages like @Deus-Rex when trying to start it on Arch.

mank319 commented Dec 2, 2015

I'm getting the same list of error messages like @Deus-Rex when trying to start it on Arch.

@kill1n

This comment has been minimized.

Show comment
Hide comment
@kill1n

kill1n Dec 3, 2015

Same problem here.

OS: Ubuntu 15.10 (unity)

KDE Connect works fine. Ping, notifications, remote mouse...

indicator-kdeconnect doen't show the tray icon. Sometimes show this window, other times don't show anything.

Terminal output:

user@ubuntu15.10:~$ indicator-kdeconnect
** Message: KDEConnectManager.vala:32: KDE Connect daemon found
** Message: Device.vala:73: device : /modules/kdeconnect/devices/403a4015353e5b12
** Message: Device.vala:263: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method 'isReachable' in interface 'org.kde.kdeconnect.device' at object path '/modules/kdeconnect/devices/403a4015353e5b12' (signature '')
** Message: Device.vala:263: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method 'isReachable' in interface 'org.kde.kdeconnect.device' at object path '/modules/kdeconnect/devices/403a4015353e5b12' (signature '')
** Message: Device.vala:263: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method 'isReachable' in interface 'org.kde.kdeconnect.device' at object path '/modules/kdeconnect/devices/403a4015353e5b12' (signature '')
** Message: Device.vala:263: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method 'isReachable' in interface 'org.kde.kdeconnect.device' at object path '/modules/kdeconnect/devices/403a4015353e5b12' (signature '')

seleccion_001

kill1n commented Dec 3, 2015

Same problem here.

OS: Ubuntu 15.10 (unity)

KDE Connect works fine. Ping, notifications, remote mouse...

indicator-kdeconnect doen't show the tray icon. Sometimes show this window, other times don't show anything.

Terminal output:

user@ubuntu15.10:~$ indicator-kdeconnect
** Message: KDEConnectManager.vala:32: KDE Connect daemon found
** Message: Device.vala:73: device : /modules/kdeconnect/devices/403a4015353e5b12
** Message: Device.vala:263: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method 'isReachable' in interface 'org.kde.kdeconnect.device' at object path '/modules/kdeconnect/devices/403a4015353e5b12' (signature '')
** Message: Device.vala:263: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method 'isReachable' in interface 'org.kde.kdeconnect.device' at object path '/modules/kdeconnect/devices/403a4015353e5b12' (signature '')
** Message: Device.vala:263: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method 'isReachable' in interface 'org.kde.kdeconnect.device' at object path '/modules/kdeconnect/devices/403a4015353e5b12' (signature '')
** Message: Device.vala:263: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method 'isReachable' in interface 'org.kde.kdeconnect.device' at object path '/modules/kdeconnect/devices/403a4015353e5b12' (signature '')

seleccion_001

@ProtoJazz

This comment has been minimized.

Show comment
Hide comment
@ProtoJazz

ProtoJazz Dec 5, 2015

Im having the same issue with a new arch install. No icon. Everything else works fine. I get messages, can even remote mouse. But no icon with Arch + XFCE 4

Any ideas?

ProtoJazz commented Dec 5, 2015

Im having the same issue with a new arch install. No icon. Everything else works fine. I get messages, can even remote mouse. But no icon with Arch + XFCE 4

Any ideas?

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Dec 6, 2015

Same problem here: OS: Ubuntu 15.10 (unity), no tray icon.

ghost commented Dec 6, 2015

Same problem here: OS: Ubuntu 15.10 (unity), no tray icon.

@FloEdelmann

This comment has been minimized.

Show comment
Hide comment
@FloEdelmann

FloEdelmann Dec 11, 2015

I know that I did have the same problem with the ownCloud desktop sync indicator until I changed the apt-repository and got the updated application from there. Maybe that helps finding the cause.

FloEdelmann commented Dec 11, 2015

I know that I did have the same problem with the ownCloud desktop sync indicator until I changed the apt-repository and got the updated application from there. Maybe that helps finding the cause.

@varlesh

This comment has been minimized.

Show comment
Hide comment
@varlesh

varlesh Dec 12, 2015

I build packages for Wily. Please use this repository:
https://launchpad.net/~varlesh-l/+archive/ubuntu/ubuntu-tools

  • Delete kdeconnect package and dependecies:
sudo apt-get purge kdeconnect
sudo apt-get autoremove
  • Add repository:
sudo add-apt-repository ppa:varlesh-l/ubuntu-tools
sudo apt-get update
  • Open Synaptic, search "kdeconnect" - Install kdeconnect & indicator-kdeconnect packages on Synaptic (select new version "kdeconnect_0.8.1wily2" on Menu-Package)
    Indicator not working because on official Wily repository used kde5-libs, but indicator working only kde4-libs.

varlesh commented Dec 12, 2015

I build packages for Wily. Please use this repository:
https://launchpad.net/~varlesh-l/+archive/ubuntu/ubuntu-tools

  • Delete kdeconnect package and dependecies:
sudo apt-get purge kdeconnect
sudo apt-get autoremove
  • Add repository:
sudo add-apt-repository ppa:varlesh-l/ubuntu-tools
sudo apt-get update
  • Open Synaptic, search "kdeconnect" - Install kdeconnect & indicator-kdeconnect packages on Synaptic (select new version "kdeconnect_0.8.1wily2" on Menu-Package)
    Indicator not working because on official Wily repository used kde5-libs, but indicator working only kde4-libs.
@kill1n

This comment has been minimized.

Show comment
Hide comment
@kill1n

kill1n Dec 19, 2015

Hi and thanks varlesh.

I'm using your instructions. Now i can see the indicator and seems work the most options. Only, when i click "browse the device", nautilus open a blank folder.

Other options like battery percentage, ping, mouse, notifications, etc.. seems work fine.

I never use kdeconnect previously. I forgot something?

seleccion_002

kill1n commented Dec 19, 2015

Hi and thanks varlesh.

I'm using your instructions. Now i can see the indicator and seems work the most options. Only, when i click "browse the device", nautilus open a blank folder.

Other options like battery percentage, ping, mouse, notifications, etc.. seems work fine.

I never use kdeconnect previously. I forgot something?

seleccion_002

@khartahk

This comment has been minimized.

Show comment
Hide comment
@khartahk

khartahk Feb 6, 2016

I'm also not seeing the icon on gnome shell 3.18 on arch. When I installed systemsettings package for KDE I could pair the device and message notifications work, I can send files from the phone but not to it. I can control the mouse, keyboard on the computer. The only thing missing is browse the phone and send to phone from nemo and the indicator icon. I tried to install the nautilus-kdeconnect python script but it's not working with nemo. Any direction on what to do next will be appreciated.

khartahk commented Feb 6, 2016

I'm also not seeing the icon on gnome shell 3.18 on arch. When I installed systemsettings package for KDE I could pair the device and message notifications work, I can send files from the phone but not to it. I can control the mouse, keyboard on the computer. The only thing missing is browse the phone and send to phone from nemo and the indicator icon. I tried to install the nautilus-kdeconnect python script but it's not working with nemo. Any direction on what to do next will be appreciated.

@watermelonjuice

This comment has been minimized.

Show comment
Hide comment
@watermelonjuice

watermelonjuice Apr 3, 2016

Any update on this?

watermelonjuice commented Apr 3, 2016

Any update on this?

nicklan added a commit to nicklan/indicator-kdeconnect that referenced this issue Apr 6, 2016

isReachable/isPaired as properties, correct icon
This change switches is_reachable and is_paired to fetch the properties
instead of trying to call a method.  (not sure if/when this changed in
the dbus interface, but that's how they are presented for me)

This fixes issue #31 and (I think) #38

This also switches the icon code to use the statusIconName as that seems
to have the correct value.  Also, in DeviceIndicator, no longer append
"-symbolic" as (at least on my system) the icons don't seem to have
that in their names.

nicklan added a commit to nicklan/indicator-kdeconnect that referenced this issue Apr 6, 2016

isReachable/isPaired as properties, correct icon
This change switches is_reachable and is_paired to fetch the properties
instead of trying to call a method.  (not sure if/when this changed in
the dbus interface, but that's how they are presented for me)

This fixes issue #31 and (I think) #38

This also switches the icon code to use the statusIconName as that seems
to have the correct value.  Also, in DeviceIndicator, no longer append
"-symbolic" as (at least on my system) the icons don't seem to have
that in their names.

rcristi added a commit to rcristi/indicator-kdeconnect that referenced this issue Apr 16, 2016

isReachable/isPaired as properties, correct icon
This change switches is_reachable and is_paired to fetch the properties
instead of trying to call a method.  (not sure if/when this changed in
the dbus interface, but that's how they are presented for me)

This fixes issue #31 and (I think) #38

This also switches the icon code to use the statusIconName as that seems
to have the correct value.  Also, in DeviceIndicator, no longer append
"-symbolic" as (at least on my system) the icons don't seem to have
that in their names.
@sergioad

This comment has been minimized.

Show comment
Hide comment
@sergioad

sergioad May 6, 2016

Hello @varlesh I am also having issues with KDE connect, I am in Xubuntu 16.04 and kDE connect indicator does not appears, if you have any solution or you know a workarround for this please let me know, greetings from Mexico 😄

PS: I recommend you to upgrade it to work with Qt5 😄

sergioad commented May 6, 2016

Hello @varlesh I am also having issues with KDE connect, I am in Xubuntu 16.04 and kDE connect indicator does not appears, if you have any solution or you know a workarround for this please let me know, greetings from Mexico 😄

PS: I recommend you to upgrade it to work with Qt5 😄

@tristan-k

This comment has been minimized.

Show comment
Hide comment

tristan-k commented May 12, 2016

@tristan-k

This comment has been minimized.

Show comment
Hide comment
@tristan-k

tristan-k May 12, 2016

I have to correct myself here. @rcristi fork solves the problem. Here are the steps to compile on Xubuntu 16.04:

sudo apt-get install gtk+-3.0-dev libappindicator3-dev valac
git clone https://github.com/rcristi/indicator-kdeconnect
cd indicator-kdeconnect
mkdir build
cd build
cmake .. -DCMAKE_INSTALL_PREFIX=/usr
make
sudo make install

Here's a binary I built with checkinstall

indicator-kdeconnect_20160512-1_amd64.zip

tristan-k commented May 12, 2016

I have to correct myself here. @rcristi fork solves the problem. Here are the steps to compile on Xubuntu 16.04:

sudo apt-get install gtk+-3.0-dev libappindicator3-dev valac
git clone https://github.com/rcristi/indicator-kdeconnect
cd indicator-kdeconnect
mkdir build
cd build
cmake .. -DCMAKE_INSTALL_PREFIX=/usr
make
sudo make install

Here's a binary I built with checkinstall

indicator-kdeconnect_20160512-1_amd64.zip

@sergioad

This comment has been minimized.

Show comment
Hide comment
@sergioad

sergioad May 12, 2016

As @vikoadi said before this is bgecause of Qt5 @tristan-k (or at east this is what I think) anyway I will try it soon with the fork you said 😄

sergioad commented May 12, 2016

As @vikoadi said before this is bgecause of Qt5 @tristan-k (or at east this is what I think) anyway I will try it soon with the fork you said 😄

@lutostag

This comment has been minimized.

Show comment
Hide comment
@lutostag

lutostag Jun 10, 2016

With a new build from https://github.com/rcristi/indicator-kdeconnect I got it working for me. I was running into the same issue.
PPA here: https://launchpad.net/~lutostag/+archive/ubuntu/indicator-kdeconnect-test

(couldn't get it to build for precise with the versioned dependencies). Not sure if they are necessary of not.

Still can't get remote file browsing to work though.

lutostag commented Jun 10, 2016

With a new build from https://github.com/rcristi/indicator-kdeconnect I got it working for me. I was running into the same issue.
PPA here: https://launchpad.net/~lutostag/+archive/ubuntu/indicator-kdeconnect-test

(couldn't get it to build for precise with the versioned dependencies). Not sure if they are necessary of not.

Still can't get remote file browsing to work though.

@bam80

This comment has been minimized.

Show comment
Hide comment
@bam80

bam80 Jul 19, 2016

@lutostag , still can't get indicator visible in Ubuntu 15.10 even with your PPA.
indicator-kdeconnect prints nothing wile running from terminal

bam80 commented Jul 19, 2016

@lutostag , still can't get indicator visible in Ubuntu 15.10 even with your PPA.
indicator-kdeconnect prints nothing wile running from terminal

@lutostag

This comment has been minimized.

Show comment
Hide comment
@lutostag

lutostag Jul 24, 2016

@bam80 yeah unfortunately it is still a bit finicky. The only way I get it to work currently is to run:
kcmshell5 kcm_kdeconnect # make sure it it connected to your device, then only after that...
indicator-kdeconnect #works for me and shows up in the systemtray.

lutostag commented Jul 24, 2016

@bam80 yeah unfortunately it is still a bit finicky. The only way I get it to work currently is to run:
kcmshell5 kcm_kdeconnect # make sure it it connected to your device, then only after that...
indicator-kdeconnect #works for me and shows up in the systemtray.

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Oct 10, 2016

@vikoadi @bam80 using @tristan-k 's .deb and running @lutostag 's commands as a startup script, i have managed to reliably get the indicator to appear in ubuntu 16.04, only if my screen is turned on

kdeConnect.txt

ghost commented Oct 10, 2016

@vikoadi @bam80 using @tristan-k 's .deb and running @lutostag 's commands as a startup script, i have managed to reliably get the indicator to appear in ubuntu 16.04, only if my screen is turned on

kdeConnect.txt

@markcross

This comment has been minimized.

Show comment
Hide comment
@markcross

markcross Jan 7, 2017

LXLE 16.04.1 got indicator-kdeconnect working of sorts with this, but no nice icon in the applet-indicators thingy at the top of LXLE

https://github.com/rcristi/indicator-kdeconnect
PPA here: https://launchpad.net/~lutostag/+archive/ubuntu/indicator-kdeconnect-test

markcross commented Jan 7, 2017

LXLE 16.04.1 got indicator-kdeconnect working of sorts with this, but no nice icon in the applet-indicators thingy at the top of LXLE

https://github.com/rcristi/indicator-kdeconnect
PPA here: https://launchpad.net/~lutostag/+archive/ubuntu/indicator-kdeconnect-test

@varlesh

This comment has been minimized.

Show comment
Hide comment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment