Dual display shows no background or icons on second monitor

[twelve17]

Binary package hint: compiz-core

I am using gnome. I have a dual-head setup, using the nvidia TwinView feature to expand my X onto my two displays (one being 1680x1050 and the other 1280x1024).

When I enable the desktop effects, my desktop wallpaper and icons disappear. The desktop background turns black. The rest of the visual effects seem to work fine. If I switch the effects off, I see the original desktop wallpaper and icons again.

I am using a Nvidia GeForce 8400 video card, using the "nvidia-glx-new" package version 100.14.19+2.6.22.4-14.9. My compiz-core version is 1:0.6.0+git20071008-0ubuntu1.

See attachments for various logs and my x.org configuration file.

[twelve17 (spam-twelve17)]

I'm not sure if this will help, but I did find this interesting:

1. Turn off desktop effects (background wallpaper and icons appear)
2. Run gnome-terminal. Edit the current profile and give it a transparent background. Verify that you see the background.
3. Leave gnome-terminal running, then turn on desktop effects. gnome-terminal continues to show the background.
4. Move the gnome-terminal window around the desktop. gnome-terminal continues to show the "correct" background (i.e. the background portion that it shows changes to reflect what is really "behind" the window).

[twelve17 (spam-twelve17)]

I forgot to mention in my original post: I am not running emerald. Here is the list of the various related processes:

usr/bin/gtk-window-decorator --replace
/usr/bin/compiz.real --ignore-desktop-hints --replace --loose-binding --sm-client-id default0 ccp
/bin/sh /usr/bin/compiz --sm-client-id default0

Also, to rule out me breaking something by changing settings in the "Advanced Desktop Effects Settings" dialog, I tested creating a brand new user and enabling the desktop effects there. The issue still occurred.

[twelve17 (spam-twelve17)]

One thing that I noticed is that the nvidia driver thinks that my card has 512MB of RAM. According to the product box, the card *supports* 512MB, but only comes with 256MB installed. So I either got 256MB extra for free, or the driver is reporting the wrong value:

# nvidia-settings -q VideoRam

  Attribute 'VideoRam' (seadragon:0.0): 524288.
    'VideoRam' is an integer attribute.
    'VideoRam' is a read-only attribute.
    'VideoRam' can use the following target types: X Screen, GPU.

I will try overriding that value in my xorg.conf and try again.

[twelve17 (spam-twelve17)]

Just in case. :)

[twelve17 (spam-twelve17)]

Hmm, Xorg, seems to be ignoring my attempts to override the memory. If I'm reading the lspci output correctly, I does appear that the card only has 256MB:

01:00.0 0300: 10de:0422 (rev a1) (prog-if 00 [VGA])
        Subsystem: 1682:2310
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at de000000 (32-bit, non-prefetchable) [size=16M]
        Memory at c0000000 (64-bit, prefetchable) [size=256M]
        Memory at dc000000 (64-bit, non-prefetchable) [size=32M]
        I/O ports at dc80 [size=128]
        [virtual] Expansion ROM at dfe00000 [disabled] [size=128K]
        Capabilities: [60] Power Management version 2
        Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
        Capabilities: [78] Express Endpoint IRQ 0

I was attempting to override by putting this in the "Device" section:

 VideoRam 262144

However, the xorg.log still reported the original 512MB value. Sigh.

[twelve17 (spam-twelve17)]

Ok, so apparently the memory reported by Xorg may not be incorrect, according to <a href="http://www.nvnews.net/vbulletin/showthread.php?t=100228">this post</a>.

"The reported amount of 'Memory' includes local video memory and system memory available for use by the GPU, i.e. it reflects the overall amount of memory available to the GPU."

So I suppose it's back to the drawing board for me. I don't have any other leads. :(

[twelve17 (spam-twelve17)]

I ran a few more test cases to narrow things down. "Works" means I see the background wallpaper + icons. "Doesn't work" means I don't see those items.

1. (Original configuration) Dual Head: 1280x1024 and 1680x1050: doesn't work

2. Single head: 1280x1024: works

3. Dual head: both at 1280x1024: works

4. Dual head: 1024x768 and 1280x1024: doesn't work

Here are the relevant portions of my xorg.conf that I changed to run those tests (these are from my "Screen" section):

# test 1 - no worky
Option "MetaModes" "CRT: 1280x1024 +1680+0, DFP: 1680x1050 +0+0"

(For test 2, I simply commented out the TwinView and MetaMode lines.)

# test 3 - worky!
Option "MetaModes" "CRT: 1280x1024 +1280+0, DFP: 1280x1024 +0+0"

# test 4 - no worky
Option "MetaModes" "CRT: 1024x768 +1280+0, DFP: 1280x1024 +0+0"

Hope this helps. Also, if the bugfixer lives in Manhattan, beers are on me. :)

[jeffez (jeffez)]

Hi,

I have the same problem.
My config is :
- Nvidia Geforce MX440 128MB dualhead,
- Two monitors wich one with 1024 x 768 - 87Hz (my nvidia maximum is 2048 x 2048),
- Ubuntu 7.10 (plus kubuntu-desktop and xubuntu-desktop packages),
- Twinview configuration,
- nvidia-glx package.
- Emerald packages.

Some different things, same behavior.

[Cian Davis (davisc)]

I have the same problem: Gutsy, nvidia dual head, primary monitor 1680x1050, secondary 1280x1024, using nvidia-glx-new. However, yesterday when I woke the machine from a sleep and it showed the background correctly. It broke again when I had to reboot to install the new kernel. I will keep trying to replicate the conditions it did work.

[twelve17 (spam-twelve17)]

Cian,

If there is something I can do to help, let me know. I couldn't figure out a more useful way to debug this.

Cheers,

Alex

[Caroline Ford (secretlondon)]

new ->confirmed

As lots of people seem to have this issue.

[Leonox (leonox)]

I have the same problem, is there any solution? or how can i help?

[Tristan Schmelcher (tschmelcher)]

I have just started seeing this issue. I'm using a mostly Gutsy system but with the Hardy Kernel/Compiz/X/NVIDIA packages (and various dependencies). I have a Dell XPS M1710 laptop with an NVIDIA GeForce Go 7900 GS. Note that I am using separate X screens, NOT TwinView like the other reporters. Also, this didn't used to happen to me until today when I was fiddling around with compiz again, but I don't know what has changed that caused the problem ...

[Tristan Schmelcher (tschmelcher)]

Just a note: the problem mysteriously went away for me a couple days after my last comment. Don't know why. I am now running Hardy final and it is still working.

[Mike Spiz (spizm)]

This issue still persists in the latest version of Hardy for me, though the desktop now doesn't turn black.

[twelve17 (spam-twelve17)]

I've upgraded to Hardy as well and I am experiencing the slightly different behavior as spizm. When switching effects on, the desktop and icons remain on the screen, but they are frozen. If I try and drag an icon, it appears as if I'm unable to drag it. However, when I turn effects back off, the background refreshes and shows that the icon was actually dragged.

[Chris Schanck (chris-schanck)]

I have the same behavior as twelve17; with the latest hardy the icons are there, but if you move them or whatnot they are not redrawn. And when you change the background of the desktop, it doesn't update until you logout/login.

[Emerout (emeric-chardiny)]

I have the same behaviour as well : wallpaper cannot be changed until X session restart, icons on desktop cannot be moved, edited or refreshed.
I'm running Hardy, with desktop effects and twinview with nvidia-glx-new on two different monitors.

[[e-mail] (slump187)]

I also have the same prob as twelve17, enable desktop cube, back round go's black. wish there was a fix!

[nemiax (nemiax)]

I have a multimonitor configuration with nVidia Quadro140 (Dell Latitude D830) and have solved the problem setting the same vertical resolution for the monitor, using TwinView option.
This is just a workaround, I had to force the notebook panel to work @1024 while its real vertical resolution is 1050.

[larytet (larytet-48904418)]

I confirm the problem for single monitor, out of the box (almost - see below) installation in Ubuntu 8.10 - the Intrepid Ibex

The problem:
After i start screensaver Compiz wallpapers go all black. Even simple opening of a screen saver configuration window and choosing screen saver blanks the wallpapers.

I suspect that I know how I broke the system. I installed xscreensaver, but after some playing with it i removed it. Now I have the problem - original screen saver breaks compiz wallpapers.

[larytet (larytet-48904418)]

P.S. No NVDIA, i am not using proprietary drivers. I just ran Hardware Test and sent report to the launchpad.
$lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02)
$

[Vancouverite (sethgilchrist)]

I had a very similar problem in 8.10 (amd64) and now have the same similar thing in 9.04 (amd64).

For me the desktop just freezes when I start compiz. It doesn't go black, it just stays exactly the same: can't change the background, animations don't work, and file/folder icons don't update.

Of note: When I use the proprietary driver v180 my desktop completely locks up with compiz. The screen flashes and rendering becomes erratic. I have to hard-shutdown to recover and reconfigure the xserver in recovery mode to get back to work. Using the older v173 to run compiz leaves me with the stuck desktop - but at least it runs!

lshw returns the following about my video card:

    *-pci
          description: Host bridge
          product: 82Q963/Q965 Memory Controller Hub
          vendor: Intel Corporation
          physical id: 100
          bus info: pci@0000:00:00.0
          version: 02
          width: 32 bits
          clock: 33MHz
        *-pci:0
             description: PCI bridge
             product: 82Q963/Q965 PCI Express Root Port
             vendor: Intel Corporation
             physical id: 1
             bus info: pci@0000:00:01.0
             version: 02
             width: 32 bits
             clock: 33MHz
             capabilities: pci pm msi pciexpress bus_master cap_list
             configuration: driver=pcieport-driver
           *-display
                description: VGA compatible controller
                product: GeForce 8400 GS
                vendor: nVidia Corporation
                physical id: 0
                bus info: pci@0000:01:00.0
                version: a1
                width: 64 bits
                clock: 33MHz
                capabilities: pm msi pciexpress bus_master cap_list
                configuration: driver=nvidia latency=0 module=nvidia

Could the problem be related to the 64 bit system and vid card, with only a 32 bit pci bridge?

What else can I provide to help find a resolution to this problem?

Cheers.

[twelve17 (spam-twelve17)]

Vancouverite,

That seems to be what I and a few others experienced since Hardy. See my comment an the few that follow above:

https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/160226/comments/19

I wish there was more I could do to help debug this issue. It's been over a year since I originally submitted it. :(

[Vancouverite (sethgilchrist)]

Hi twelve17,
Thanks for the quick reply, I'm sorry to see that you are still monitoring this thread...

I forgot to mention that I have my monitors set up in dual head as well: 1) Samsung 1680x1050, 2) Dell 1280x1024, so it seems that my setup fits this profile well.

Hopefully more people will get on the bandwagon here.

[Anmar Oueja (anmar)]

Could this be related to this bug 732050

[jhfhlkjlj (fdsuufijjejejejej-deactivatedaccount)]

Is this bug still reproducible in modern versions of compi/ubuntu?

[Luchostein (luchostein)]

It is working fine in Precise.

[jhfhlkjlj (fdsuufijjejejejej-deactivatedaccount)]

I'm going to close this bug as the older versions are no longer supported. If this issue arises please log a new bug.

Thanks!