On 07/17/2015 03:30 PM, Gerald B. Cox wrote:
>
> On Mon, Jul 6, 2015 at 5:24 PM, Gerald B. Cox <gbcox(a)bzb.us
<mailto:gbcox@bzb.us>> wrote:
>
> I'll let you know what upstream says...
>
>
> Here is the reply, sorry for the delay in posting... unfortunately, don't think
it is going to help you much, but thought I'd post it anyway...
>
> "I remember that quite some time ago I had similar problems when setting or
getting clipboard content too often. So maybe there is some other app that misbehaves.
This can easily happen if there are more clipboard managers and they try to synchronize
clipboard and X11 selection (they're fighting to change the clipboard)."
>
>
>
>
> _______________________________________________
> kde mailing list
> kde(a)lists.fedoraproject.org
>
https://admin.fedoraproject.org/mailman/listinfo/kde
> New to KDE4? - get help from
http://userbase.kde.org
>
Well, since my last reply. I installed Fedora 22, Then reinstalled Fedora 21 two days
later. KDE5 is not ready for prime time.
Now I have a brand new Fedora workstation, with all new home directory, so nothing is
left of the previous KDE installation.
At first, the clipboard worked. That made it all worth the pain. But alas, it
didn't stay that way. The clipboard on this new installation is now just as messed up
as when I first started this thread.
I believe that you must be right that some other app is messing things up. But I have NO
idea how to go about discovering what that might be.
Does anybody know where to find docs on the clipboard and it operation details? I
don't even know what kind of action in plasma that hooks the clipboard.
Note that this issue is in no way related to "too often". It it fails to copy
even tow ot three hours after the last time I tried. Even the first time I try to copy
something when I first start my workday.
Emmett
_______________________________________________
kde mailing list
kde(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/kde
New to KDE4? - get help from
http://userbase.kde.org
That last suggestion about interference from another app, was the clue I needed.
Turn's out it was Tiger vnc's vncviewer. I seem to have fixed it by adding
-SendPrimary=0 to all vncviewer calls. I will probably also add the parameter to each
server's start up parameters as well.
Note that I usually have at least tree remote desktops open at many one time. I will file
a bug report on tiger vnc as soon as I am sure this resolves the issue.
Emmett