-
Notifications
You must be signed in to change notification settings - Fork 30
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
Fix DBUS interface for recent KDE Connect versions #56
Comments
Sorry for breaking this. "isTrusted" is called "isPaired" now. |
Yeah, I have the DBUS side sorted, just need to plumb it through the NativeHost interface to the UI, and have ended up down a rabbit hole of extension manifest v3, serviceworkers and general refactoring. |
Hey @pdf, what's the status on this? I too see my devices in Firefox, but also the red exclamation mark and can't send, unfortunately. |
Sorry for the delay, IRL stuff has had me out of town and time-poor the last couple of weeks. |
Thanks for the update! It's great seeing you still working on this. Thank you for all your work! |
Subscribing to this issue, waiting for fix. |
until (if) this gets fixed, one can use the external application addon, which lets you chose an external binary with arguments and custom icon. |
I don't know if external links are ok here... but in worst case it gets deleted: Steps to make this work:
Now you should have a new icon in your extensions button menu. Once you click this it opens a page with the link for the native application. Download this, extract it, run ./install.sh Multiple DevicesYou don't get a menu with all your devices. For each device you need to add a separate "Application". Fill in the same details and just change the ID in arguments to match your other devices. Also change the title of the Application. If this seems cumbersome to you, don't call kdeconnect-cli directly, but use your own custom script, which lists all devices using dmenu/rofi/etc and then sends the url to it. Here is a custom script that uses rofi. the only argument this script needs is
Using this approach has another advantage: You can actually see if the device is available. calling kdeconnect-cli directly you will never know if the device was ready to receive data. |
Ok, added Instructions to make this work. |
@carnager Got it all setup, thanks. One important thing to note is that the install script provided by the extension creates folders to put the native messaging hosts in even though the corresponding browser isn't installed. |
Someone please maintain this repo. |
Looks like KDE Connect have removed the old
*Trusted
properties/signals, and now uses*PairState
need to update the DBUS interfaces and UI logic to use the new properties if they exist.The text was updated successfully, but these errors were encountered: