Screen transparency problem

[townk]

I did and the variable is not defined at all. Pretty weird so far!

[greguric]

Ok. Thank you for enabling the "Upload attachment" tab. Now I can show you my screenshots

[greguric]

One more thing. I have the Vbox installed on my laptop together with cairo-dock, and it works perfectly! It is a little bit confusing. The thing is, that on the laptop I'm not using cairo with GL.

[greguric]

OK. It is definitly cairo-dock!

Code: Select all

sudo apt-get --purge remove cairo-dock

I've restarted the machine, and Vbox is running like a charm

So - cairo-dock is mostly aesthetic thing, and Vbox is, for me, essential. There were no much doubt which one will hit the higway

[bsleys]

Just wanted to add that I have the same problem. However I don't have Cario installed.

Code: Select all

bsleys@bsleys-laptop:~$ sudo apt-get --purge remove cairo-dock
[sudo] password for bsleys: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package cairo-dock is not installed, so not removed

I also tried running vbox with

Code: Select all

env XLIB_SKIP_ARGB_VISUALS=1 VirtualBox

and it didn't help.

However if I diable Compiz all is good. So I don't think its Cario, witch requires compiz (I think), but something to do with vbox and compiz. This only started happening after ugrading to vbox 2.2.2.

[Sasquatch]

Some programs can set a colour to transparent. So, in Compiz you have that option too. It's called "Colour Opacity", which creates transparency by using a colour for it. Setting black for transparent, will make all black objects on your system become transparent. Disable that option.

[townk]

And where exactly is this color option to disable it?

[myxiplx]

Hmm.... I don't know if this is related, but I posted a bug today about VirtualBox disappearing since my upgrade to 2.2.2. It could be transparency related - the entire guest keeps going invisible for a short while, and then appearing again.

http://www.virtualbox.org/ticket/3898

[seqizz]

I ran more tests here and if I start VirtualBox with environment variable XLIB_SKIP_ARGB_VISUALS=1 and Cairo-Dock, VirtualBox works fine:

Code: Select all

env XLIB_SKIP_ARGB_VISUALS=1 VirtualBox

I put this on my launcher and it's working, but I still think that this is a workaround not a fix.

only that one works.. i've tried to create a rule about VirtualBox class windows on compiz settings manager, not worked. but that env workaround sh** works

virtualbox-bin-2.2.2 and nvidia-drivers-180.51 (gentoo ~x86 host, running xp)

[Upsurged]

I ran more tests here and if I start VirtualBox with environment variable XLIB_SKIP_ARGB_VISUALS=1 and Cairo-Dock, VirtualBox works fine:

Code: Select all

env XLIB_SKIP_ARGB_VISUALS=1 VirtualBox

I put this on my launcher and it's working, but I still think that this is a workaround not a fix.

After long time of looking for the solution, and staying back in 2.1.4, the above helped. Thanks.

[fusa]

I was able to disable the transparency in 2.1.4 in Jaunty while still using Compiz by:
Preferences > CompizConfig Settings Manager > Enable Windows Rules > No ARGB Visuals,
and add "class=VirtualBox" to the box.

[psidrum]

I had same problem, but i ran this command

env XLIB_SKIP_ARGB_VISUALS=1 VirtualBox

it worked for me.

[PioStremel]

I solved it disabling the "Software compositing" option in Visual System Configurations on Centos.
I don't know what library this option disable.

[socratis]

Did you honestly wake up a 9-year old thread? Do you know what 9 years in software development mean? For the love of bytes, they were talking about VirtualBox 2.1.4!!!

Locking this.