Timeline for Pairing KDE Connect with phone on i3wm
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 30, 2019 at 18:41 | history | edited | fra-san | CC BY-SA 4.0 |
Small edit to fix rendering of a code block that would have been broken by next edit after the introduction of code fences: https://meta.stackexchange.com/a/322000/410681
|
| Oct 20, 2018 at 14:02 | vote | accept | rajudev | ||
| Oct 20, 2018 at 14:01 | comment | added | user316808 | Cool, appended to the answer | |
| Oct 20, 2018 at 14:01 | history | edited | user316808 | CC BY-SA 4.0 |
added 293 characters in body
|
| Oct 20, 2018 at 13:54 | comment | added | rajudev | If you will add this comment briefly as an answer I'll accept that as an answer. This precisely helped me solve the issue. Or else I'll have to write an answer for my own question | |
| Oct 20, 2018 at 13:39 | comment | added | user316808 | Oh okay. Well dunst doesn't support interactive notifications, so open up the KDE Connect Indicator and launch the settings from the indicator and when you try to pair you can accept from the configure dialog. Here | |
| Oct 20, 2018 at 13:30 | comment | added | rajudev |
I tried following your instructions. In my case the location was /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd . Although this did not solve my issue. This seems a step to start kdeconnect daemon. In my case the daemon was already running.
|
|
| Oct 20, 2018 at 13:10 | review | First posts | |||
| Oct 20, 2018 at 13:18 | |||||
| Oct 20, 2018 at 13:09 | history | answered | user316808 | CC BY-SA 4.0 |