SUMMARY STEPS TO REPRODUCE 1. Install the program 2. Launch Discord or Steam 3. Join a voice channel in Discord or Launch SteamVR OBSERVED RESULT Discord freezes, SteamVR encounters an error and doesn't work anymore. EXPECTED RESULT No crashes or freezes SOFTWARE/OS VERSIONS Windows: 10 (Latest update as of 06/14/2020) ADDITIONAL INFORMATION I am 100% sure it was this program since uninstalling it immediately fixed all my computers bugs. Somehow it is interfering a ton!
Same issue here, though not quite as extreme (I don't use SteamVR). The issue only happens with discord for me, and it isn't instant. After about 5-10 minutes being in a voice call, discord will crash. Definitely caused by kdeconnect, because uninstalling it fixes the issue. I'm on archlinux 5.7.5, using kdeconnect 1.4.0. I'd be happy to provide any other information needed to help resolve this bug.
Does disabling the 'Multimedia control receiver' plugin in the KDE Connect settings help?
I am unable to reproduce this issue. If you can help us reproduce this issue with the latest build from https://binary-factory.kde.org/job/kdeconnect-kde_Nightly_win64/ , I can try to fix it.
is this report still valid? I am unable to
is this report still valid? I'm unable to reproduce this bug at all.
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!
Somewhere between then and now the bug has been squashed since I cannot reproduce the issue anymore.