Registered Member
|
Hmm, interesting.
Perhaps my issue is not the same as the issue that some of the people above are having, or did have. I'm using KDE connect to connect KDE PCs to one another and transfer files that way, but it coincides so well with the phone issues that it seemed to be the same thing. "Ping" works, shared clipboard works, but the file transfers never happen. Those are the only KDE Connect functions I use, so I do not know about the rest. Something has changed in the 20.04 base that makes things not want to work as they did before. I tried the kdeconnect-indicator thing to test KDE Connect with Mint 20 Cinnamon, and it didn't work there either. The logs give no clues that mean anything to me. |
Registered Member
|
I have KDECONNECT 1.4.0 on MX Linux KDE Plasma which is working great.
I also have KDECONNECT 1.4.0 on Linux Mint 20 with Cinnamon 4.6.7 with Linux Kernel 5.4.0.47 generic with Intel© Pentium© CPU G630 @ 2.70GHz × 2 Processor with 7.8 GiB Memory. I've tried to get help on the Linux Mint Forum but none of the suggestions have worked including using GSConnect nor using KDE Connect Control Center Applet (kdeccc@Severga). Thank you, Kip OS Linux Mint 20 Cinnamon 4.6.7 Linux Kernel 5.4.0-47-generic Processor Intel© Pentium© CPU G630 @ 2.70GHz × 2 Memory 7.8 GiB |
Registered Member
|
To use KDEConnect add firewall rules https://userbase.kde.org/KDEConnect#Troubleshooting
ufw If your firewall is ufw, you can open the necessary ports with: sudo ufw allow 1714:1764/udp sudo ufw allow 1714:1764/tcp sudo ufw reload OS Linux Mint 20 Cinnamon 4.6.7 Linux Kernel 5.4.0-47-generic Processor Intel© Pentium© CPU G630 @ 2.70GHz × 2 Memory 7.8 GiB |
Registered Member
|
Didn't work for me. I tried removing ufw, and that didn't work either. It doesn't work on Kubuntu 20.04 or Mint 20 (with kdeconnect-indicator) either. It does work fine on all of the most recent non-Ubuntu KDE distros I tried, including Manjaro, Fedora 32, and OpenSUSE Tumbleweed, and it also works fine on Ubuntu 18.04 derivatives. I wish Neon had not rebased! |
Registered Member
|
Mine fails on unstable but was ok on Neon user and Fedora 33 beta (with 5.19.5), see bug report:
https://bugs.kde.org/show_bug.cgi?id=426372
Neon Unstable, AMD RX570, Steam (skyrim for now), Vivaldi, btrfs (with apt-btrfs-snapshot), bug-reporter
|
Registered Member
|
My KDE Connect--version 1.4.0--does not find any devices
/usr/bin/kdeconnect-cli -l = 0 devices found the ufw status = inactive specifying hostnames or IPs on Android has no effect the Android Connect version is 1.14.2 is this possibly related to the Android platform (5.1.1) that is rather dated, can't be upgraded and/or is not supported?
KDE neon 5.20 - Plasma 5.20.5 - Frameworks 5.78 - Qt 5.15.2 - Kernel 5.4.0-65
|
Registered Member
|
Neon Unstable updated today and kdeconnect works now ie browsing device shows folders.
New version: kdeconnect-20.08.1+p20.04+git20200916.0255-0.amd64 I don't know when this will be released to other channels. Edit: it seems the error was in kio and this was fixed in version kio 5.74.1 see https://mail.kde.org/pipermail/release- ... 12012.html
Neon Unstable, AMD RX570, Steam (skyrim for now), Vivaldi, btrfs (with apt-btrfs-snapshot), bug-reporter
|
Registered Member
|
Same here, I have to use connect via IP-Adress. Running on most actual openSuSE TumbleWeed and Android 9 |
Registered users: Bing [Bot], claydoh, Google [Bot], markhm, rblackwell, sethaaaa, Sogou [Bot], Yahoo [Bot]