Corrupt mouse pointer shades in Windows 7 guest

[marcnn]

Hi,

I copied my old Windows 7 .vdi drive, created a new VM using Virtualbox 5.1 on Arch. Upgraded the Guest Additions.

What I noticed: the cursor shade is broken. Instead of a gradual transparency change, the whole shade is black.

How can I fix it?
Thanks!

[socratis]

Do you have any screenshots so we can better understand what you're describing? See the "Upload attachment" at the bottom of the form.

Oh, and post the VBox.log. ZIPped.

[marcnn]

The photo is here, was too big: http://imgur.com/a/ZaJjH

[socratis]

VBoxTestGL 5.1.0_OSE r108711 linux.amd64 (Jul 14 2016 20:15:51) release log

It seems you're not using the "official" version from https://www.virtualbox.org/wiki/Downloads. Could you test with the one you download from there?

00:00:00.493336   VRamSize         <integer> = 0x0000000001500000 (22 020 096, 21 MB)

Your assigned virtual graphics RAM seems way too low. Try to bump it up to 64MB.

For future reference:
• Completely shut down the VM before grabbing the VBox.log and then ZIP it.
• Attach images locally. You can always crop them to make them smaller.

[marcnn]

I'm using the VirtualBox from the Arch Linux repos. There's no download for my distribution over there (Arch Linux). I have this in AUR, though: https://aur.archlinux.org/packages/virtualbox-bin/

I enabled 2D & 3D acceleration, bumped the video memory to ~180 MB. All persists

[socratis]

There's no download for my distribution over there (Arch Linux)

Download VirtualBox

• -> Download VirtualBox for Linux Hosts
  • -> All distributions (built on EL5 and therefore do not require recent system libraries) i386 | AMD64

Try that one. Be sure to change the appropriate .run file to +x.

[marcnn]

Is it possible to install this version without removing my existing OSE VirtualBox?

[socratis]

I don't really know. I don't run Arch. Why would you want to keep it? Souvenir? The word ... conflicts comes in mind. The general advice is not only to remove it but to purge the whole thing to Hades. Then install the official version. That's the only way we're going to be able to help you here. Otherwise you can always visit the Arch forums.

[marcnn]

This works correct with the non-open-source edition.

Now, is it possible to fix the open source version? I'm not very eager to run closed-source software on my computer.

[socratis]

Now, is it possible to fix the open source version? I'm not very eager to run closed-source software on my computer.

I don't think that you have it straight. You ARE running the open-source version. You are NOT running the Arch fork. That's the difference.

How to contribute: https://www.virtualbox.org/wiki/Contributor_information (read this one first)
Source code tree: https://www.virtualbox.org/browser

[michael]

Indeed, VirtualBox is divided into two components - the base package, which is available under the GPL, and the extension pack, which is closed source. The binary installer that you downloaded is simply our build of the open source part, whereas what you installed from the Arch repositories is Arch's build of the same code, possibly with a couple of patches which they applied. I personally suspect that the difference might be that our build also includes our own bundled build of Qt which is different to Arch's, but I also see from your log file that you were running the Arch build of VirtualBox 5.1.0, whereas you will have downloaded 5.1.8 from us. It may be that this is a bug which was fixed in between those versions.

[michael]

And generally, as long as the versions are not too different you can uninstall your current build of VirtualBox to replace it with a different one without affecting your virtual machines. That is how you were able to replace Arch's build with ours, but removing ours to reinstall Arch's one should work just as well. Removing a more recent version to reinstall an older one can potentially cause problems accessing your virtual machines (they can be fixed by fiddling with the XML configuration files, but you have to know what you are doing), but that should not be a problem going back from 5.1.8 to 5.1.0, which are both minor releases of the same major release. That said, there are other reasons that you would probably not want to downgrade. You should check whether Arch provides 5.1.8 instead, and if your bug is still present, please report it to the Arch maintainer. They can still contact us for help if necessary.

[socratis]

@michael
Since we ... "solved" this ( ), can you also take a look at a similar issue in OSX hosts (https://www.virtualbox.org/ticket/15610)? I kind of have a personal interest and I'm really sure I am running the official VirtualBox packages...

[michael]

Hello Socratis, I passed it on to the developer most likely to know, but he has quite a high workload I'm afraid.

[socratis]

Yep, that's what I thought, that's why I can't run my VMs correctly since 5.1b. Especially the OSX < 10.10 ones, I get dizzy . It's not just shadows, it's actually double cursors! With pics: viewtopic.php?f=15&t=78510

Thanks for the effort, I appreciate it...