Page MenuHomeSolus

Indicator KDE Connect
Closed, WontfixPublic

Tokens
"Love" token, awarded by devxpy."Love" token, awarded by Devil505."Mountain of Wealth" token, awarded by bandh."Like" token, awarded by Beer."Like" token, awarded by JGH1000."Like" token, awarded by Commander-Zal.
Assigned To
None
Authored By
joebonrichie, May 24 2017

Description

https://github.com/Bajoja/indicator-kdeconnect

Since Solus is now accepting and working on kde applications and plasma, kde connect functionality with a gui would be useful on other desktop environments. It should be noted I have this packaged locally (indicator, kdeconnect and a couple of python rundeps) and everything is working as it should on budgie, I haven't tested it on the mate or gnome stacks though.

I would estimate that quite a large number of users would be interested in this as it has been requested multiple times.

latest release: https://github.com/Bajoja/indicator-kdeconnect/archive/0.9.0.tar.gz

joebonrichie updated the task description. (Show Details)

The stance on this has not changed. I said clearly in the kdeconnect task that it needed some means to work with the current desktops and if it was able to, I would happily put it in myself (this release was forked from what was basically abandoned code).

I've heard inconsistent results of this working (sometimes but not others), but if it does work correctly and not buggy, then yeah, it goes in.

The software is working pretty consistently for me.

The features I haven't been able to get to work is the remote input control, which i assume is kde specific. As well as sending files from my phone to my desktop. As well as the browse device feature from the indicator.

pairing, pinging, find my phone, sending sms, notifications, remote media control and sending files from the pc to my phone is working well.

I'll try to get all the features working but I wonder how much is kde specific and how much is the fault of indicator itself.

leinad added a subscriber: leinad.May 28 2017, 10:34 AM

Remote input control and sending files from the device is now working. The browse device feature will be fixed in the next release.

sunnyflunk triaged this task as Normal priority.

Well it sounds like there's enough there to make it worthwhile. I mean, kdeconnect needs to be added regardless for the new plasma spin. My issue was that once it's found in the software center people will complain it doesn't work (and without this being updated as it has been recently, it really couldn't be used well on other desktops).

I haven't gotten remote input/control stuff to work even on plasma (but I don't know how or really have a need to use it kdeconnect)...So it can go in with the proviso being, it is what it is (the odd feature may not yet work) and you'll keep it updated so we get the new goodies :)

yaomtc added a subscriber: yaomtc.Jun 27 2017, 2:35 AM
lulzor added a subscriber: lulzor.Jun 27 2017, 9:04 PM
Beer added a subscriber: Beer.Dec 22 2017, 3:14 AM
Beer awarded a token.Dec 22 2017, 3:18 AM
yaomtc removed a subscriber: yaomtc.Feb 25 2018, 5:25 AM

This works for what I need it to do. Thanks for packaging this!

bandh added a subscriber: bandh.Feb 26 2018, 2:24 PM

This bajoja indicator works great. I compiled it from the github. I think the indicator bundled with kdeconnect ( found in the repos should be disabled ) and this should be in the repos( as I don't find it ).

bandh awarded a token.Feb 27 2018, 1:50 PM
bandh added a comment.Feb 27 2018, 1:58 PM

On further testing if 'Show device directories: ' in KDE Indicator Settings is checked the browse device function works only once ( pop up a nautilus window to '/run/user/1000/<id>/storage/emulated/0' and on second try it pop up a window to '/run/user/1000/<id>/storage/emulated/0/DCIM/Camera' ) and after that it fails to open new windows. If the option is unchecked and checked again in KDE Indicator Settings it works again . I will post this on github also as I'm not sure if it is solus related or not.

Only reason I haven't put this in is due to the buggy nature of the 'Browse Device' option. I also need to split up the kdeconnect package into kdeconnect-core and kdeconnect-indicator in anticipation of different kdeconnect frontend options.

bandh added a comment.Mar 2 2018, 1:59 PM

The split is a great ideea. Also you could add Bajoja kdeconnect-indicator at it is and maybe the "Browse Device" will be fixed upstream . I opened an issue at : https://github.com/Bajoja/indicator-kdeconnect/issues/114.

https://github.com/Bajoja/indicator-kdeconnect/issues/114

Resolved in a commit on May 15, though they haven't had a release since April so would need to be coming from source right now

If it's actually fully fixed this time I'll include it.

@joebonrichie any progress about the inclusion ?

DataDrake added a subscriber: DataDrake.

Closing due to lack of activity in over 30 days. Still eligible for inclusion.

DataDrake closed this task as Wontfix.Oct 20 2018, 4:03 PM
DataDrake changed the task status from Wontfix to Resolved.Thu, Nov 29, 8:06 PM
DataDrake removed a project: Needs Maintainer.

@joebonrichie please make sure you mark things when you decide to maintain them.

joebonrichie changed the task status from Resolved to Wontfix.Sat, Dec 1, 1:04 PM
joebonrichie added a project: Needs Maintainer.

This is a different piece of software different from kdeconnect meant for gnome based environments.