Bug 420198 - Clipboard sync stopped work after 1.14 update
Summary: Clipboard sync stopped work after 1.14 update
Status: RESOLVED FIXED
Alias: None
Product: kdeconnect
Classification: Applications
Component: android-application (show other bugs)
Version: unspecified
Platform: Android Unspecified
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
: 410254 420218 (view as bug list)
Depends on:
Blocks:
 
Reported: 2020-04-17 12:57 UTC by lubimov.maxim+kde
Modified: 2020-06-04 18:36 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description lubimov.maxim+kde 2020-04-17 12:57:39 UTC 
SUMMARY
I have a device with Android 10 with installed Riru - Clipboard whitelist module for Magisk. Clipboard sync worked before update. After update I got notification "Plugin will be disabled" or something similar. Even with enabled plugin clipboard synchronization doesn't work. Please allow to enable plugin on Android 10 with warning that it might not work because there is workaround for Android restrictions.

STEPS TO REPRODUCE.
1. Install kdeconnect 1.14 on Android 10.
2. Install "Riru - Clipboard whitelist" module for Magisk and configure it.

OBSERVED RESULT
Clipboart sync should work.

EXPECTED RESULT
It doesn't.

SOFTWARE/OS VERSIONS
Linux: Arch Linux
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.2
Comment 1 Nicolas Fella 2020-04-18 09:55:23 UTC 
*** Bug 420218 has been marked as a duplicate of this bug. ***
Comment 2 Dashon 2020-04-18 10:18:12 UTC 
I'm also affected by this. I understand that users without access to root were probably constantly reporting bugs, but I agree with the author of this bug that the warning should be for non root users. This way others can continue to use work arounds for this problem.
Comment 3 lubimov.maxim+kde 2020-04-22 07:51:52 UTC 
Works for me in 1.14.2.
Comment 4 Simon Redman 2020-06-04 18:36:59 UTC 
*** Bug 410254 has been marked as a duplicate of this bug. ***