Created attachment 109883 [details] wireshark network record of a refresh done on the phone Hi, as statet in the title, the devices don't seem to see each other. when doing a refresh to look for new devices I can see in wireshark that the devices talk to eachother (sometimes there is a ICMP packet that fails, but not always.) however neither phone, nor kcm module show any entry in their list. this is connecting a Motorolla phone, running lineageOS Android and KDEconnect App installed from Google AppStore on the phone (192.168.0.14) and gentoo linux on the laptop (192.168.0.12) I have been using Gentoo only for a few months now, and i am wondering whether there are any polkit related things to look out for? This problem has been before and after switching from 13 to 17 profile (dekstop/plasma) Same phone, same Network kdeconnect works nicely with Debian 8 based KDE Laptop what could be going on here?
possible duplicates: #373327 (almost no information) #359149 359149 suggest that it doesn't work, if the network interface has a link-local address (ipv6 beginning with fe80:). apparently[1] the link-local address is required when using ipv6 so I am trying to disable ipv6 for my WLAN. Only way i found so far is to globally disable ipv6 through uncommenting the appropriate line in /etc/modprobe.d/aliases.conf will reboot to see the change and report on the outcome
Did it improve to disable ipv6?
(In reply to Aleix Pol from comment #2) > Did it improve to disable ipv6? unfortunately no. needed to recompile kernel (and learn how to do that) because ipv6 was not compiled as a module and thus couldn't be deactivated through /etc/modprobe.d/aliases.com I am using: kdeconnect: 1.2 KDE Frameworks 5.40.0 Qt 5.7.1 (built against 5.7.1) The xcb windowing system any ideas how I could go about debugging this?
Not really, best would be if you could provide us a way to reproduce your issue.
I am on Fedora 27 and Android 8.1. In the last few updates it has become difficult to keep the devices connected. My setup hasn't changed except the system and the app updates. KDE Connect connects and disconnects on its own. I am also wondering how to debug this issue.
*** Bug 394646 has been marked as a duplicate of this bug. ***
*** Bug 419077 has been marked as a duplicate of this bug. ***
*** Bug 399855 has been marked as a duplicate of this bug. ***
*** Bug 420884 has been marked as a duplicate of this bug. ***
I’m on HardenedBSD 13-CURRENT and has the same bugs there below, > https://git-01.md.hardenedbsd.org/HardenedBSD/hardenedbsd-ports/issues/5#issuecomment-107 And Mr. dSP, how is your ‘‘pcapng’’ file looked like? Please take some screenshots for us to briefly and clearly explain how your bug is looked like on Gentoo > My system: HardenedBSD CURRENT > Plasma, KDE connect, KF5 are up to date > (but the same combo on Linux never suffers not to connect like this) > KDE connect on Android is up to date too > And both Android and laptop are connected to the same active wifi named ‘‘KK’’ > Laptop model: ASUS K43SJ > Android: Samsung J7-2015 with Android 7.1.1 based AOKP
Thanks for the report and investigation work dSP. As it's been a while since this report was submitted can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!