I have a desktop computer running Gentoo with KDE Connect 0.8 and two Android phones running KDE Connect 0.9g under Android 4.1 and 5.1. All three devices are paired with each other. Sometimes when all three devices are on the same network, I start getting very weird glitches with clipboard. Let's assume that I have been using a text editor for a while (so I have been using the clipboard a lot), I have selected some text and I've pressed Ctrl+C. Then I move the cursor elsewhere and I press Ctrl+V. The text that gets pasted isn't the same as the one that was copied, but rather something that I had copied before. Then I press Ctrl+V once again. Yet another different snippet is pasted. This way, I can obtain around 4 different pieces of text that I had copied to the clipboard, and they cycle as I press Ctrl+V repeatedly. As soon as I disconnect one of the devices from the network, the problem goes away (tested only with the Android 4.1 phone). Reproducible: Sometimes Steps to Reproduce: 1. Connect multiple devices with KDE Connect to the same network 2. Pair them with each other 3. Use the clipboard on one of the devices for a long time and wait for the glitch. Expected Results: The clipboard state should be in sync between the devices, and it definitely shouldn't have memory.
Thanks for the report Pastafarianist. I don't have two devices here to test this. Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I'm setting status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
I think it's not reproducible anymore, although I'm not sure what I exactly I meant by "all three devices are paired with each other" (i.e. are the two phones paired with each other? that would be somewhat weird). At the very least, I haven't seen anything similar to what I described. However, as far as I remember my recent experience, clipboard sync doesn't work at all (i.e. nothing is synced), but that would be a different bug report, which would also probably become irrelevant 4 years from now.