Bug 501594 - File sending, Linux -> iPhone - error: no route to host
Summary: File sending, Linux -> iPhone - error: no route to host
Status: RESOLVED WORKSFORME
Alias: None
Product: kdeconnect
Classification: Applications
Component: ios-application (other bugs)
Version First Reported In: 0.5
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Lucas W.
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-03-16 16:31 UTC by Rafael Rossi
Modified: 2025-03-16 16:45 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rafael Rossi 2025-03-16 16:31:22 UTC
SUMMARY
Sending a file from Linux to iPhone fails on the iPhone app: <filename> No route to host.
Sending file from iPhone to Linux works ok.

STEPS TO REPRODUCE
1. Connect Linux and iPhone in KDE Connect
2. With KDE Connect app open in the phone, send a file from Linux to iPhone

OBSERVED RESULT
The transfer fails and the app shows the error message "No route to host". 
In Linux, the transfer window hangs at 0%.

EXPECTED RESULT
File transfered to the phone.

SOFTWARE/OS VERSIONS

iOS: 18.3.2 (Iphone 12 Mini)
Linux: Arch 6.13.5-arch1-1
KDE Plasma: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2

ADDITIONAL INFORMATION
The correction described [here](https://bugs.kde.org/show_bug.cgi?id=495307) did not work for me. KDE Connect app doesn't seem to response when "Restart Discovery" is pushed.

In Linux, `journalctl`:
mars 16 17:30:14 xps plasmashell[1302]: QQmlExpression: Expression file:///usr/share/plasma/plasmoids/org.kde.kdeconnect/contents/ui/DeviceDelegate.qml:460:17 depends on non-NOTIFYable properties:
mars 16 17:30:14 xps plasmashell[1302]:     RemoteCommandsDbusInterface::canAddCommand
mars 16 17:30:15 xps plasmashell[1302]: kpipewire_logging: PipeWire remote error:  -2 unknown resource 5 op:7
Comment 1 Rafael Rossi 2025-03-16 16:45:21 UTC
After several failed attempts, the app decided to work after I files this bug. Not sure what went wrong. But it is working now. Closing it