SUMMARY Find new devices button is inoperable right now. STEPS TO REPRODUCE 1. Go to terminal and use kdeconnect-app 2. click the "+ Find Devices" Button OBSERVED RESULT Window flashes briefly, then the terminal prints out: qrc:/qt/qml/org/kde/kdeconnect/app/FindDevicesPage.qml:13:1: QML FindDevicesPage: Created graphical object was not placed in the graphics scene. EXPECTED RESULT finding devices SOFTWARE/OS VERSIONS Operating System: NixOS 24.11 KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 Kernel Version: 6.11.1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840HS w/ Radeon 780M Graphics Memory: 27.2 GiB of RAM Graphics Processor: AMD Radeon 780M Manufacturer: Framework Product Name: Laptop 16 (AMD Ryzen 7040 Series) System Version: AG
This is happening for me too. Running Debian Sid on a recently installed Dell Latitude 5420 but with the data - and hence config files - copied from an older install. If I run kdeconnect I get to a blank Devices page and clicking on the find devices icon on the panel results in "qrc:/qt/qml/org/kde/kdeconnect/app/FindDevicesPage.qml:13:1: QML FindDevicesPage: Created graphical object was not placed in the graphics scene." being logged in the journald log. The file .config/kdeconnect/config contains only [General] name=cuthbert I renamed the kdeconnect config directory, removed and reinstalled but that doesn't seem to have regenerated a config directory though the hostname is still present on the settings page. Anything else I can try? KDE Connect: 24.08.3 Debian GNU/Linux trixie/sid (Wayland) KDE Frameworks: 6.8.0 Qt: Using 6.7.2 and built against 6.7.2 Build ABI: x86_64-little_endian-lp64 Kernel: linux 6.12.3-amd64
I note in the system log that there is an earlier failure to send an mdns query, as "cannot assign requested address" - possibly an interaction with avahi occupying the mdns port. No surprise that I'm not identifying any devices then, but it's not clear that the later failure to place a created graphical object is related.
To update, it appears that a system update at some point gifted me a firewall which blocked kdeconnect and mdns. Adding rules to allow connections on the relevant ports has solved the issue for me. I don't know if the original reporter has fixed his issues but I think this could be closed.