SUMMARY kdeconnect-cli does not return a list of notifications. STEPS TO REPRODUCE 1. run kdeconnect-cli -n "<device-name>" --list-notifications OBSERVED RESULT Nothing printed, no debug messages from kdeconnectd EXPECTED RESULT List of notifications printed. I can see there are notifications displayed in kdeconnect plasmoid. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Also installed kdeconnect-kde from source to ensure I'm testing the latest version
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
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)
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/62297192/qml-connections-implicitly-defined-onfoo-properties-in-connections-are-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?
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.
This bug seems to persist, also verified in a github issue[1] for a project with kdeconnect-cli as a dependency. [1]: https://github.com/carldotac/kdeconnect.el/issues/5#issuecomment-1774286027