Bug 494980

Summary: Find devices button broken in kdeconnect-app
Product: [Applications] kdeconnect Reporter: contact
Component: commonAssignee: Albert Vaca Cintora <albertvaka>
Status: RESOLVED FIXED    
Severity: normal CC: andrew.g.r.holmes, kdebugs, kdedev
Priority: NOR    
Version First Reported In: 24.08.1   
Target Milestone: ---   
Platform: NixOS   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description contact 2024-10-18 09:16:02 UTC
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
Comment 1 Angus Mackenzie 2024-12-15 07:26:40 UTC
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
Comment 2 Angus Mackenzie 2024-12-17 08:30:31 UTC
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.
Comment 3 Angus Mackenzie 2025-03-05 08:49:50 UTC
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.
Comment 4 TraceyC 2025-04-17 21:44:10 UTC
(In reply to contact from comment #0)
> SUMMARY
> Find new devices button is inoperable right now.

Is this still happening on an up to date system?


> qrc:/qt/qml/org/kde/kdeconnect/app/FindDevicesPage.qml:13:1: QML
> FindDevicesPage: Created graphical object was not placed in the graphics
> scene.

This is an unrelated warning. I have that on my laptop where KDE Connect does see my other devices.
Comment 5 Bug Janitor Service 2025-05-02 03:47:30 UTC
๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Angus Mackenzie 2025-05-02 10:51:01 UTC
I'm not the original reporter, but I solved my problem with firewall rules to allow mdns etc. I think it could be closed.
Comment 7 TraceyC 2025-05-07 15:42:21 UTC
(In reply to Angus Mackenzie from comment #6)
> I'm not the original reporter, but I solved my problem with firewall rules
> to allow mdns etc. I think it could be closed.

Thanks for confirming. 

contact@betalars.de, are you still having problems with this?
Comment 8 contact 2025-05-08 16:34:05 UTC
I can't seem to find the "find devices" button right now but I can find an unpaired device. So I think this can be closed.