Ticket #6947 (new defect)

Opened 7 years ago

Last modified 20 months ago

VBoxSharedClipBoardClass blocks when copying from host. (XP guest, CentOS host)

Reported by: afante Owned by:
Priority: critical Component: clipboard
Version: VirtualBox 3.2.4 Keywords:
Cc: Guest type: Windows
Host type: Linux


Since several versions ago, I have been experiencing clipboard blocking problems.

When copying contents (most of the cases, they are formatted texts), VBoxSharedClipBoardClass blocks, or locks up, so that the application in the guest stops responding.

I recently found that killing the virtual box service in the guest machine will return control back to the guest application, but the clipboard sharing between guest and host will be lost. Restarting the virtual box service on the guest does not help regain the sharing.

The problem happens at some time, I still cannot reproduce it at will.

Change History

comment:1 Changed 7 years ago by michael

You might take a look at and later to see if it looks like you are experiencing the same issue.

comment:2 Changed 6 years ago by daveu8282

I've experienced the VBoxSharedClipBoardClass hang in an XP guest (OpenSUSE 11.1 Linux host) but stopping the VBox Guest Additions service didn't release the hung app. The problem persisted after I shut down and rebooted the VM. Rebuilding the kernel modules (/etc/init.d/vboxdrv setup) didn't help. What did restore desired host-to-guest clipboard behavior was reinstalling the guest's VBox Guest Additions.


comment:3 Changed 6 years ago by redtech

This might be unrelated since my problem was in the other direction (Windos host, Linux Guest), but maybe it will help.

I was using Ubuntu as the guest and the clipboard would stop working until I added my login to the "disk" group.

comment:4 Changed 20 months ago by jedie

I have also problems, that clipboard stops working after some time...

Also: Windos host, Linux Guest with virtualbox v4.3.28

The linux user was not in "disk" group. (But why should this been needed?!?) However, i put the user into "disk" group and test if this will fix the problem...

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