Bug 440202

i forgot to add, Firewall is NOT enabled

I have the same problem running kdeconnect in arch linux. I have been using kdeconnect o transfer files from my Pixel 4XL for a long time but a recent update has a regression and neither the phone sees the laptop, nor the laptop sees the phone.  The firewall is stopped so that is not an issue.  Running the cli version I get:
$ kdeconnect-cli -l
0 devices found
on the laptop.  If I try to add a new device from the phone by either name or ip address nothing connects. So this is a serious regression.

My plasma version is plasma-desktop 5.22.4-1

@MikeC

> a recent update has a regression

Do you know this for sure? Are you able to pull an older version from your package repos to test? As far as I am aware there hasn't been an Android version release in awhile so any regression would be limited to the desktop packages.

> My plasma version is plasma-desktop 5.22.4-1

Just as a point of interest, KDE Connect does not ship with Plasma.

@Carl Draper and @MikeC

Could both of you share your KDE Connect version? (kdeconnect-cli --version, or read it from your package repository information)

If you both wouldn't mind, could you share a bit about your network setup? What router brand do you use, etc.

I also have a four-way "blackout". My Android tablet, my Android phone, my Linux laptop, and my Windows desktop all can't see each other. I haven't updated the version on any of them in awhile. This makes me suspect that it is a networking issue (for me) and not a code issue. If I use my laptop as a hotspot and connect my other devices, they are able to see each other. Can you all try a different wifi network?

I have a Comcast XFi modem/router combo, which I know can receive updates over the air. I have a suspicion that might be what I'm seeing.

Yes I believe it is kdeconnect on my laptop running in the plasma desktop - my version is the latest on arch linux - kdeconnect 21.04.3-1 (that version was installed as an update on July 7 2021)

My network setup is a LAN with three different routers on the network all acting as access points, but I believe that the router is not the issue.  All other networking between multiple laptops, phones, tablets, and other devices all work without any issue on my lan, including the wired and wireless networking.

(In reply to Simon Redman from comment #4)
> @MikeC
> 
> > a recent update has a regression
> 
> Do you know this for sure? Are you able to pull an older version from your
> package repos to test? As far as I am aware there hasn't been an Android
> version release in awhile so any regression would be limited to the desktop
> packages.
> 
> > My plasma version is plasma-desktop 5.22.4-1
> 
> Just as a point of interest, KDE Connect does not ship with Plasma.
> 
> @Carl Draper and @MikeC
> 
> Could both of you share your KDE Connect version? (kdeconnect-cli --version,
> or read it from your package repository information)
> 
> If you both wouldn't mind, could you share a bit about your network setup?
> What router brand do you use, etc.
> 
> I also have a four-way "blackout". My Android tablet, my Android phone, my
> Linux laptop, and my Windows desktop all can't see each other. I haven't
> updated the version on any of them in awhile. This makes me suspect that it
> is a networking issue (for me) and not a code issue. If I use my laptop as a
> hotspot and connect my other devices, they are able to see each other. Can
> you all try a different wifi network?
> 
> I have a Comcast XFi modem/router combo, which I know can receive updates
> over the air. I have a suspicion that might be what I'm seeing.

My KDE Connect version:
kdeconnect-cli 21.04.3

It's not a network issue because it works fine on kubuntu on the machine sat next to my desktop, which is on the same ethernet.

The system journal on my laptop has multiple repeated lines with the same content:

Aug 07 12:43:30 lenovo1 kdeconnect-app[4768]: qrc:/kdeconnect/qml/PluginChecker.qml:20:47: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }


This looks related to an issue with QT5 - eg see https://stackoverflow.com/questions/622 … e-deprecat and on the laptop and my other systems I now have qt5-base 5.15.2+kde+r211-1 so I wonder if the kdeconnect code was not updated to include the change in qml connections in QT5?

The stack overflow link should have been

https://stackoverflow.com/questions/62297192/qml-connections-implicitly-defined-onfoo-properties-in-connections-are-deprecat

in my previous comment.

I created a new bug https://bugs.kde.org/show_bug.cgi?id=440688

I have found the solution to this issue in my case.  The problem was that the nftables firewall did not flush the  firewall rules when the nftables service was stopped.  A recent change to nft meant that previous behaviour that stopping the nftables service would flush the ruleset was changed, and it is now necessary to manually flush the ruleset after stopping the firewall.  Once the nft rules are flushed kdeconnect works perfectly. 

Additionally when I added the port range 1714-1764 to the nftables rules for udp and tcp, and restarted the nftables firewall kdeconnect continues to work perfectly with the firewall running.

In my case clearing the following directory solved the issue:
~/.config/kdeconnect