virtualbox.org

Hi there everyone,

latest vbox on Windows Vista 32bit
Mint Debian Guest with all updates and GA installed.
Shared clipboard is set to bidirectional in Guest Settings.

Found a thread on this topic that I can not share due to my untrustworthiness and checked and the following packages are at their latest version:

dkms
build-essential
linux-headers-486

Any thoughts on how I can get my clipboard shared both ways would be greatly appreciated

My log can be found at schwim net slash mint hyphen debian txt.

Very sorry, but you can thank the site's security measures for the ridiculous line above.

Please don't use phrases such as "latest vbox" - we have no way to know what you think the latest version is, so please be explicit.

In VirtualBox 4.1.22 and later the shared clipboard is disabled by default for security reasons, and must be enabled using the settings dialog, see <VM settings>|General|Advanced tab|Shared clipboard pulldown.

Hi there and thanks very much for your response.

Version is 4.1.22 r 80657.

As stated in initial post, shared clipboard is set to bidirectional under General/Advanced.

Issue persists in spite of this setting.

Thanks for your time!

Ok, so not the latest vbox (latest was VBox v4.2.0/1 at the time you posted - the .1 version only relevant to Mac hosts).

If the clipboard is enabled, and the VM has been shut down and restarted since that happened, and the correct GAs are installed - then it ought to work. What are you trying to copy via the clipboard? As far as I know only plain text can be passed.

I have had no luck decoding your obfuscated URL.
ps. even as a first time poster you could have included your log file as a (zipped) attachment.

Why is everyone so grumpy to people who are simply trying to get solutions? It's counter-productive to shoot the messenger. I have this problem as well on my MAC with WinXP or Ubuntu guests. Both have guest additions. This issue has been reported in this forum many times and for a long time. It would be really nice if this was put to bed.

VirtualBox 4.2.1

Aside from user or configuration errors there is actually little that can be achieved here. You should open a ticket at bugtracker

Grumpy? I see nothing from the the above conversation to justify what you got from it. A request for a precise problem description is not grumpiness: it ensures accurate advice is given and prevents time being wasted on all sides. But then we have time wasted on irrelevant side matters such as this. Ah well.