Skip to content
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.

Sign up for GitHub

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

Jump to bottom

indicator kde-connect not working #38

Open
ghost opened this issue Feb 13, 2016 · 24 comments
Open

indicator kde-connect not working #38

ghost opened this issue Feb 13, 2016 · 24 comments

Comments

@ghost
Copy link

ghost commented Feb 13, 2016

ayush@ayush-VPCEB44EN:$ indicator-kdeconnect
ayush@ayush-VPCEB44EN:$

I am using Ubuntu 14.04 and indicator kdeconnect application just wont launch .
@spravo13
Copy link

I am having the same problem with debian testing

I recieve an alert with the message: "cannot connect to KDE Connect DBus service"

@diegonz
Copy link

diegonz commented Feb 29, 2016

Same behaviour on Ubuntu 15.10, pairing and receiving notifications on pc works great if done from kdeconnect-plasma.
Also indicator wizard runs good, but the icon(s) doesn´t show at all

@armc
Copy link

armc commented Mar 31, 2016

Is anyone working this issue??. It would be great to get a working package back in circulation.

@spravo13
Copy link

spravo13 commented Apr 1, 2016

I agree, I've been swamped so I haven't had a chance to look into the problem any further than before. Please update this thread if you find any additional information. Just got on Spring Break today (Wooo!!) so I will let you guy's know through this with what I find.

@armc
Copy link

armc commented Apr 1, 2016

Excellent. Good luck... but enjoy your spring break first and foremost!

@ghost
Copy link
Author

ghost commented Apr 1, 2016

Try this
open terminal try use this command "kcmshell4 kcm_kdeconnect"
and try to remove the device or unpair and then try it.

@armc
Copy link

armc commented Apr 3, 2016

I will try this when I get the chance... been packing for a trip. I'll post an update to my experience with the kcmshell4 kcm_kdeconnect and then unpair / repair. No time presently. Thank!!! :)

@Natsumi-sama
Copy link

I'm getting the error:
** 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/d2d4bb6f54282ffa' (signature '')

@ghost
Copy link
Author

ghost commented Apr 3, 2016

@cmcooper123 couldn't you be more specific . What command did you run ?

@aldomann
Copy link

aldomann commented Apr 3, 2016

@1595ayush I get the same message when launching indicator-kdeconnect from the Terminal, so it must be it. To be more specific, I get this:

** Message: KDEConnectManager.vala:32: KDE Connect daemon found
** Message: Device.vala:73: device : /modules/kdeconnect/devices/e1342f8007f52a77
** 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/e1342f8007f52a77' (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/e1342f8007f52a77' (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/e1342f8007f52a77' (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/e1342f8007f52a77' (signature '')

@ghost
Copy link
Author

ghost commented Apr 3, 2016

Well you can either use plasma(see 3rd comment by btsunami) or go to issue number #31 @aldomann

@Natsumi-sama
Copy link

@1595ayush indicator-kdeconnect, I tried removing ~/.config/kdeconnect and running "kcmshell5 kcm_kdeconnect" before after and during running indicator-kdeconnect

nicklan added a commit to nicklan/indicator-kdeconnect that referenced this issue Apr 6, 2016
@nicklan
isReachable/isPaired as properties, correct icon
2222e7c 
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 vikoadi#31 and (I think) vikoadi#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
@nicklan
isReachable/isPaired as properties, correct icon
0c129c0 
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 vikoadi#31 and (I think) vikoadi#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 nicklan mentioned this issue Apr 6, 2016
Open
rcristi pushed a commit to rcristi/indicator-kdeconnect that referenced this issue Apr 16, 2016
@nicklan @rcristi
isReachable/isPaired as properties, correct icon
37c2221 
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 vikoadi#31 and (I think) vikoadi#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.
@lutostag
Copy link

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.

@NiklasMerz
Copy link

I have the same problem after upgrading my Linux Mint 17.3 (Ubuntu 14.04) to Mint 18 (Ubuntu 16.04)

@edouard-lopez edouard-lopez mentioned this issue Aug 4, 2016
Closed
@pandacriss
Copy link

lutostag, i compile your version and it work. very thankful.

@Simon0Harms
Copy link

Same Problem here with Ubuntu Mate 16.04 64 Bit

@Simon0Harms
Copy link

@lutostag Your version don't work for me on Ubuntu Mate 16.04 64 Bit, too
** Message: KDEConnectManager.vala:29: retrying to find KDE Connect DBus service
** Message: KDEConnectManager.vala:29: retrying to find KDE Connect DBus service
** Message: KDEConnectManager.vala:29: retrying to find KDE Connect DBus service
** Message: KDEConnectManager.vala:29: retrying to find KDE Connect DBus service
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

@lupa18
Copy link

lupa18 commented Sep 5, 2016

Not working here. Ubuntu 16.04

@ghost
Copy link

ghost commented Nov 6, 2016 •
edited by ghost
Loading

I am also having same issue in Ubuntu 16.04 ! indicator popups do not work. Only the ping showed when i pinged from phone as soon as i installed everything on Ubuntu 16.04.
then i restarted the pc and none of the popup indicators work. the only notifications i get from my phone to my pc is from the kde-monitor.

Also the kde-monitor i cannot see a mirror of my phone so i cannot remote control. I only see battery and notifications, and when i close kde-monitor, and i re-open it, it doesnt open again until i kill the process manually, then i can re-open it.

kde-monitor has no menu or indicator taskbar settings to be able to minimize it in taskbar, or close in taskbar.

Please can someone try fix the indicator problems on ubuntu 16.04?

@ghost
Copy link

ghost commented Nov 6, 2016

i get this when i type:
kcmshell4 kcm_kdeconnect

Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kbuildsycoca4 running...
kbuildsycoca4(5514) KBuildSycoca::checkTimestamps: checking file timestamps
kbuildsycoca4(5514) KBuildSycoca::checkTimestamps: timestamps check ok
kbuildsycoca4(5514) kdemain: Emitting notifyDatabaseChanged ()
kcmshell(5483)/kdecore (services) KServiceFactory::findServiceByDesktopPath: "kcm_kdeconnect.desktop" not found
kcmshell(5483)/kdecore (services) KServiceFactory::findServiceByDesktopPath: "kcm_kcm_kdeconnect.desktop" not found
kcmshell(5483)/kdecore (services) KServiceFactory::findServiceByDesktopPath: "kcmkcm_kdeconnect.desktop" not found
Could not find module 'kcm_kdeconnect'. See kcmshell4 --list for the full list of modules.

@NeoMahler
Copy link

same as @Beast141

@Tehmal
Copy link

Tehmal commented Feb 12, 2017

reflesh

indicator-kdeconnect
** Message: KDEConnectManager.vala:29: retrying to find KDE Connect DBus service
** Message: KDEConnectManager.vala:29: retrying to find KDE Connect DBus service
** Message: KDEConnectManager.vala:29: retrying to find KDE Connect DBus service
** Message: KDEConnectManager.vala:29: retrying to find KDE Connect DBus service
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
Naruszenie ochrony pamięci (Core Dump)

@sollidsnake
Copy link

I tried kcmshell5 kcm_kdeconnect instead of kcmshell4 and it worked. Knowing this is there a way to run the indicator?

@Simon0Harms
Copy link

This one is working:
https://github.com/Bajoja/indicator-kdeconnect

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests