Bug 486251 - KDEConnect spams MDNS query errors in log
Summary: KDEConnect spams MDNS query errors in log
Status: REPORTED
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (show other bugs)
Version: 24.02.2
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-28 14:17 UTC by Martin
Modified: 2024-04-28 14:38 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Seemingly one of the "Error sending MDNS query response" wireshark captures (7.57 KB, application/x-7z-compressed)
2024-04-28 14:38 UTC, Martin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin 2024-04-28 14:17:08 UTC
SUMMARY

This just seems to occur 3 times in the same moment every minute or less, sometimes multiple times in a minute when I started trying to reproduce it by clicking around in kdeconnect and avahi-discover:
  Apr 28 16:08:37 Luxuria kdeconnectd[11570]: 2024-04-28T16:08:37 kdeconnect.core: Error sending MDNS query response

If I click Refresh on the devices, I get 21~ errors like this at once, reproducable:
  Apr 28 16:11:07 Luxuria kdeconnectd[11570]: 2024-04-28T16:11:07 kdeconnect.core: Failed to send mDNS query: Cannot assign requested address

OBSERVED RESULT
Spam in logs with no idea why

EXPECTED RESULT
No spam at all, or at least with an explanation why they're occurring. Which address cannot be assigned? Which what query response exactly is erroring?

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.7-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor
Memory: 62.0 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 4090/PCIe/SSE2
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X670 AORUS ELITE AX
Comment 1 Martin 2024-04-28 14:38:32 UTC
Created attachment 168971 [details]
Seemingly one of the "Error sending MDNS query response" wireshark captures

Not sure which part of this errors out of it is supposed to have more back and forth, but it seems to be the thing behind one of the issues.

Capture is attached, short version:

14:17:08.631641324	192.168.1.156	224.0.0.251	MDNS	113	Standard query 0x0000 PTR _kdeconnect._udp.local, "QM" question PTR 15447d7f50b6f64d._kdeconnect._udp.local

14:17:08.631801298	fe80::61bc:2d94:7824:ea83	ff02::fb	MDNS	133	Standard query 0x0000 PTR _kdeconnect._udp.local, "QM" question PTR 15447d7f50b6f64d._kdeconnect._udp.local

14:17:08.631810124	192.168.1.10	224.0.0.251	MDNS	292	Standard query response 0x0000 PTR _b23e5f59_4ad3_4f23_a64c_db862d04ce0f_._kdeconnect._udp.local SRV 0 0 1716 Luxuria.local A 192.168.1.10 AAAA fdb9:9e13:d719:0:5aa:7f9a:caa4:dd53 TXT