Ticket #16242 (new defect)

Opened 4 years ago

Last modified 3 years ago

MacOS Sierra host, CentOS 7 guest, VBoxClient clipboard breaks when copying rich text in guest

Reported by: tkvb Owned by:
Component: clipboard Version: VirtualBox 5.1.10
Keywords: clipboard Cc:
Guest type: Linux Host type: Mac OS X


VirtualBox (on Mac host), version 5.1.10 r112026 (Qt5.6.2)

Host version Mac OS Sierra 10.12.1

All host patches up to date

CentOS 7 guest, version 7.2.1511

Guest additions installed and up to date, all guest OS patches up to date

Application running in guest: CLion 2016.3 Build #CL-163.7743.47, built on November 18, 2016 (

When copying text from CLion using Ctrl+C which seems to be copying rich text rather than plain text by default, the VBoxClient clipboard in the CentOS guest stops working. Nothing can be copied anymore between host and guest. If only plain text is copied, the clipboard works OK, but as soon as rich text is copied, the clipboard breaks completely.

The only way to fix it is to restart VBoxClient in the guest:

killall VBoxClient

I do not expect rich text copy/paste to work correctly, but it must not take down the entire clipboard functionality in the guest and require VBoxClient to be restarted.


clipboard.log Download (5.2 KB) - added by tkvb 4 years ago.

Change History

comment:1 Changed 4 years ago by michael

It would be interesting to know if enabling extended logging in VBoxClient<1> produces any additional information. And please attach a host log file (see ticket creation guidelines<2>).


comment:2 Changed 4 years ago by michael

You added a comment to ticket #15782. If that does seem to be the same issue after inspection we can close this ticket as a duplicate of course.

comment:3 Changed 4 years ago by michael

And if you are confident with building and debugging software, you might actually want to try building your own Additions<1> to investigate yourself. I am pointing this out since I am the person most likely to be able to solve this, but I have enough higher priority tasks that I am not likely to get to it in the near future. I should be able to find a small amount of time to help you debug it yourself though.


Changed 4 years ago by tkvb


comment:4 Changed 4 years ago by tkvb

Attached clipboard.log

comment:5 Changed 4 years ago by michael

As I said, you should 1) attach a host log file and 2) you might get further if you build a debug version of VBoxClient on the affected guest machine and run it inside GDB. The process seems to be faulting based on the guest log file you attached.

comment:6 Changed 4 years ago by philip

I do feel that this and Bug #15782 are the same, but FWIW feel the content of this report (as reported by tkvb) is more useful (I reported #15782).

comment:7 Changed 3 years ago by philip

This bug has been confirmed by many yet is listed here as a "new defect", how do we change that? It's certainly not new :)

comment:8 Changed 3 years ago by frank

Just ignore the "status new". It gets the same attention as other tickets.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use