Brian,
When I tried to replicate your issue just now (Firefox and Waterfox) it
worked perfectly. The only thing I found was that from M$ Word on the
remote, with right-click / copy it wouldn't copy/paste, however ctrl-c /
paste did.
I've not alot to contribute but FYI I have found the _direct_ copy/paste
to be a bit flaky from time to time. In that instance I've used the
Guacamole sidebar ctrl-alt-shift; it might be worth seeing if your
clipboard data is available from there? If it is then it would suggest
the issue is Guacamole <-> Browser, if not then Guacamole <-> target is
perhaps where to look.
Particularly if the former then maybe you could try a different browser
to see if the issue continues, I'd probably try it anyway as I think
this would tend to narrow the field of possible contributory factors.
Otherwise if I notice any issues in the future I'll try the ctrl-c 3x
and will update if that works and/or I find a solution.
Otherwise
On 7/05/2020 2:29 a.m., brian dodds wrote:
Hello everyone, I was wondering if anyone might have any ideas about
this situation. Currently I have this setup:
Ubuntu 18.04 client running Firefox 72.0.1 connecting to Guacamole
1.1.0 docker container, serving out an RDP connection to a container
running Mate on Ubuntu 18.04 through xrdp 0.9.5-2
Copy-paste works fine most of the time, with ctrl-c copying something
inside the target container and having it immediately available on the
client system clipboard to paste. Then something happens to alter this
behavior that I've been unable to identify, and it stops working. But
in troubleshooting the problem I discovered that it still works if I
hit ctrl-c 3 times. If I hit ctrl-c once, the copied text is available
inside the Mate desktop environment but not outside guacamole. Ctrl-c
twice, same situation. Ctrl-c 3 times, and now it's available back in
the Ubuntu client! This is pretty repeatable in my production
environment, but in my development environment I still haven't gotten
this failure state to happen in the first place.
Anyhow, any thoughts on what to check or how to debug this issue? The
usual process of restarting services and clearing caches/cookies
doesn't seem to fix this situation, either, at least nothing I've been
able to do with regularity.
Many thanks,
Brian
