https://bugs.kde.org/show_bug.cgi?id=493505
Bug ID: 493505
Summary: Unhandled exception causing crash after multicast leak
changes in GrapheneOS
Classification: Applications
Product: kdeconnect
Version: unspecified
Platform: Android
OS: Android 14.x
Status: REPORTED
Severity: normal
Priority: NOR
Component: android-application
Assignee: albertv...@gmail.com
Reporter: matchboxbananasyne...@proton.me
CC: andrew.g.r.hol...@gmail.com
Target Milestone: ---
SUMMARY
KDE Connect not properly handling exception.
GrapheneOS is currently working on resolving various upstream Android leaks
with multicast. As part of that work, KDE Connect start crashing for people.
The changes have been reverted for the time being as we work to resolve app
compatibility issues, however the error below can be sorted by gracefully
handling the exception.
"java.lang.RuntimeException: Unable to create service
org.kde.kdeconnect.BackgroundService: java.lang.RuntimeException:
java.net.SocketException: setsockopt failed: EPERM (Operation not permitted)"
My understanding from the information that has been relayed to me, this is
where the issue lies:
https://invent.kde.org/network/kdeconnect-android/-/blob/master/src/org/kde/kdeconnect/Backends/LanBackend/LanLinkProvider.java?ref_type=heads#L302
STEPS TO REPRODUCE
To reproduce the issue, you would likely need to be on a version of GrapheneOS
with the changes that have since been reverted, but we still believe that
handling the exception above gracefully is important.
OBSERVED RESULT
The app crashes.
EXPECTED RESULT
The app should handle the exception and not crash.
--
You are receiving this mail because:
You are watching all bug changes.
