[nvidia] Windows appear blank white

[pablomme]

[ Impact ]

When switching focus from one window to another, the target window may become blank. See the attached screenshot, where I opened two gnome-terminals and clicked on their titlebars alternately - the issue was triggered after about 5-10 clicks. I've had this happen on other appications too, e.g. software-centre, empathy, etc.

HOW TO REPRODUCE:

[ Test Case ]

Verification requires an nVidia GPU with proprietary drivers. The problem can not reliably be reproduced at will, only after some time (depending on resident GPU memory and usage) and even then only randomly.

1. Minimize a window
2. Initiate Scale and deactivate it again (press Super+W to show all windows and then press it again to go back to normal)
3. Click the window icon on the launcher to maximize it again.
4. The window contents will be white, black, or transparent depending on the Ubuntu version

[ Regression Potential ]

It is unlikely this change has the potential to introduce new regressions.

[ Other Info ]

Fix was cherry-picked from the Ubuntu "Vivid Vervet" dev relase where it has been in use for some weeks without problem.

[pablomme (pablomme)]

Strangely now I'm having the same problem but the windows contents are transparent instead of solid grey.

[Omer Akram (om26er)]

Are you still facing this issue with latest unity and compiz in natty?

[pablomme (pablomme)]

Actually, no, this disappeared about 2 weeks ago.

[Sergey Glita (s-v-glita)]

it seems that I have the same problem
App window is frequently blanc after start, Maximise-minimise somуtimes helps me. Context menu in firefox is blanc too.

Natty updated from 10.10, Motherboard Asus M2NPV-VM with integrated video
uname -a
Linux assa 2.6.38-7-generic #39-Ubuntu SMP Fri Mar 25 19:38:02 UTC 2011 i686 athlon i386 GNU/Linux

[[e-mail] (anthonyjschulte)]

I have this exact bug as well. For me this constitutes a severe usability issue.

natty from maverick

hp dv9000, nvidia restricted graphics driver

[Sergey Glita (s-v-glita)]

Optional: this happens only in Unity, where the first window are less likely to remain empty than next windows. In Gnome's all good.

[Josh Leverette (coder543)]

Yeah.. this is really starting to irk me. It most consistently is happening with Firefox and Chrome.. sometimes no amount of tabbing will bring back the contents of either. Old nVidia Geforce 6150 LE graphics card. This has never happened in any other Ubuntu that i've seen.

[Hefeloce (hefeloce)]

Well, for me this happens wen I maximize windows, then they appear blank, but when I resize them they become normal (All windows become normal when they reach a certain size, this size seems to be the same for all the windows).
A fact is that when I open amarok and maximize or minimize it, a few seconds later it crashes, it doesn't happen when I keep it under a tiny window (so the window is not blank) Amarok then reports a seg fault error.
This makes me think that this problem happens when windows are minimized too even when we are not able to see it.
Last, for I reason I don't know this time firefox is working properly maximized.

I'm using 64 bit edition and I use an Nvidia card like the guy who posted this bug.

[Hefeloce (hefeloce)]

I found this, when using compiz config settings manager, and disabling Metacity Workarounds Plugin it stoped to happend, so is the problem with compiz and this plugin? except for Kde apps, they keep crashing all the time

[pablomme (pablomme)]

This problem has definitely stopped happening for me (the original reporter), so for devs to investigate I think it would be more useful if one of those currently affected reported a new bug and attached their apport-collected data.

[Josh Leverette (coder543)]

Where is this Metacity Workaround Plugin you speak of?

[[e-mail] (anthonyjschulte)]

How could we create a new bug and retain the descriptions listed here? would it make more sense to post our debug info to this thread?

also-- I discovered that even while using the classic gnome desktop, the problem still exists, though in a much diminished sense; now windows are displayed blank when maximized, and even then, at a low frequency.

[Josh Leverette (coder543)]

In my studies it has mainly to do with the obscene memory usage Unity is causing compared to previous versions of Ubuntu. 800MB idle! But yeah, who knows.

Sincerely,
Josh

On Apr 6, 2011, at 9:38 PM, "<email address hidden>" <email address hidden> wrote:

> How could we create a new bug and retain the descriptions listed here?
> would it make more sense to post our debug info to this thread?
>
> also-- I discovered that even while using the classic gnome desktop, the
> problem still exists, though in a much diminished sense; now windows are
> displayed blank when maximized, and even then, at a low frequency.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/729979
>
> Title:
> Windows sometimes become blank/transparent when changing focus to them
> in natty
>
> Status in “compiz” package in Ubuntu:
> Invalid
> Status in “unity” package in Ubuntu:
> Invalid
>
> Bug description:
> Binary package hint: compiz
>
> When switching focus from one window to another, the target window may
> become blank. See the attached screenshot, where I opened two gnome-
> terminals and clicked on their titlebars alternately - the issue was
> triggered after about 5-10 clicks. I've had this happen on other
> appications too, e.g. software-centre, empathy, etc.
>
> Doing shade+unshade, maximizing or clicking away from the problematic
> window usually makes the window contents come back. The window remains
> responsive to both keyboard and mouse (by the way, in the screenshot
> the mouse cursor was an I-beam before I pressed PrtScr).
>
> This is on up-to-date natty, installed from scratch using the daily
> image from the 1st of March.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 11.04
> Package: compiz 1:0.9.4-0ubuntu3
> ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
> Uname: Linux 2.6.38-5-generic x86_64
> NonfreeKernelModules: nvidia
> .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0'
> .proc.driver.nvidia.registry: Binary: ""
> .proc.driver.nvidia.version:
> NVRM version: NVIDIA UNIX x86_64 Kernel Module 270.29 Wed Feb 23 16:18:35 PST 2011
> GCC version: gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-3ubuntu3)
> Architecture: amd64
> CompizPlugins: [core,bailer,detection,composite,opengl,decor,imgsvg,resize,resizeinfo,mousepoll,wall,regex,animation,place,blur,compiztoolbox,text,session,grid,put,imgpng,imgjpeg,gnomecompat,commands,copytex,wobbly,annotate,move,vpswitch,workarounds,expo,ezoom,staticswitcher,fade,scale,scaleaddon,unityshell]
> CompositorRunning: compiz
> Date: Sun Mar 6 02:42:49 2011
> DistUpgraded: Log time: 2011-03-03 20:05:16.908415
> DistroCodename: natty
> DistroVariant: ubuntu
> DkmsStatus: nvidia-current, 270.29, 2.6.38-5-generic, x86_64: installed
> GraphicsCard:
> nVidia Corporation ION VGA [GeForce 9400M] [10de:0876] (rev b1) (prog-if 00 [VGA controller])
> Subsystem: ASUSTeK Computer Inc. Device [1043:8402]
> InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110301.1)
> InstallationMedia_: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20...

[[e-mail] (anthonyjschulte)]

correction, this bug is now fully present in the classic desktop.

Moreover, I have discovered a fairly consistent behavior: When multiple aplications are open, the bug can manifest itself as: the active window is blank (white in my case... title bar displays but nothing else.) while windows behind it will display content. If one of the unfocused windows is selected, it gains focus, and goes blank. The previously blank window, no longer focused, regains its content and is no longer blank.

Switching between applications, the ones gaining focus always going blank only to regain content after losing focus is quite infuriating.

To force an application to quit being blank, another application is opened, and applications are switched until the blanking behavior begins for the new application. (I use terminal as my dummy app...) Terminal is given focus, observed to be blank, and closed. The aplication which was behind the dummy application gains focus, and does not go blank. (this has been verified in classic desktop, not yet in unity)

[pablomme (pablomme)]

@anthonyjschulte: most of the info here you don't want to retain. My description and apport-collected info are irrelevant, and so is my screenshot. There are some pieces of information that might be useful (especially that everyone seems to be on an nvidia card), but that can be very easily written in a new report. Just run 'ubuntu-bug compiz' from the command line to file a new bug report, and try to get a screenshot of the problem happening to you. Then post a link here so that other people can follow over to the new report.

[[e-mail] (anthonyjschulte)]

https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/753144

Here is the bug

[Sam Spilsbury (smspillaz)]

More importantly, are people getting this bug without nvidia? Due to
the way that nvidia is linking libGL (eg without -fPIC) this means
that every new instance of every application is going to increase
memory usage, which might explain why pixmaps of windows can be blank
at some times (especially when maximized or at large sizes)

On Thu, Mar 31, 2011 at 8:49 PM, Omer Akram <email address hidden> wrote:
> Are you still facing this issue with latest unity and compiz in natty?
>
> ** Changed in: compiz (Ubuntu)
>       Status: New => Incomplete
>
> --
> You received this bug notification because you are a member of compiz
> packagers, which is subscribed to compiz in Ubuntu.
> https://bugs.launchpad.net/bugs/729979
>
> Title:
>  Windows sometimes become blank/transparent when changing focus to them
>  in natty
>
> _______________________________________________
> Mailing list: https://launchpad.net/~compiz
> Post to     : <email address hidden>
> Unsubscribe : https://launchpad.net/~compiz
> More help   : https://help.launchpad.net/ListHelp
>

--
Sam Spilsbury

[[e-mail] (anthonyjschulte)]

Yes- I observe that the larger the window, the more likely it is to be blank. When (enlarging) a window, the size can be increased up to a certain point at which the window goes blank.

[Sam Spilsbury (smspillaz)]

Its likely that you are running out of pixmap memory or the server is
having trouble allocating those pixmaps.

Out of curiousity, do you get any messages from compiz in a console
which say something like "failed to bind pixmap to texture" ?

On Thu, Apr 7, 2011 at 12:38 PM, <email address hidden>
<email address hidden> wrote:
> Yes- I observe that the larger the window, the more likely it is to be
> blank. When (enlarging) a window, the size can be increased up to a
> certain point at which the window goes blank.
>
> --
> You received this bug notification because you are a member of Unity
> Bugs, which is subscribed to unity in Ubuntu.
> https://bugs.launchpad.net/bugs/729979
>
> Title:
>  Windows sometimes become blank/transparent when changing focus to them
>  in natty
>
> Status in “compiz” package in Ubuntu:
>  Invalid
> Status in “unity” package in Ubuntu:
>  Invalid
>
> Bug description:
>  Binary package hint: compiz
>
>  When switching focus from one window to another, the target window may
>  become blank. See the attached screenshot, where I opened two gnome-
>  terminals and clicked on their titlebars alternately - the issue was
>  triggered after about 5-10 clicks. I've had this happen on other
>  appications too, e.g. software-centre, empathy, etc.
>
>  Doing shade+unshade, maximizing or clicking away from the problematic
>  window usually makes the window contents come back. The window remains
>  responsive to both keyboard and mouse (by the way, in the screenshot
>  the mouse cursor was an I-beam before I pressed PrtScr).
>
>  This is on up-to-date natty, installed from scratch using the daily
>  image from the 1st of March.
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 11.04
>  Package: compiz 1:0.9.4-0ubuntu3
>  ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
>  Uname: Linux 2.6.38-5-generic x86_64
>  NonfreeKernelModules: nvidia
>  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0'
>  .proc.driver.nvidia.registry: Binary: ""
>  .proc.driver.nvidia.version:
>   NVRM version: NVIDIA UNIX x86_64 Kernel Module  270.29  Wed Feb 23 16:18:35 PST 2011
>   GCC version:  gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-3ubuntu3)
>  Architecture: amd64
>  CompizPlugins: [core,bailer,detection,composite,opengl,decor,imgsvg,resize,resizeinfo,mousepoll,wall,regex,animation,place,blur,compiztoolbox,text,session,grid,put,imgpng,imgjpeg,gnomecompat,commands,copytex,wobbly,annotate,move,vpswitch,workarounds,expo,ezoom,staticswitcher,fade,scale,scaleaddon,unityshell]
>  CompositorRunning: compiz
>  Date: Sun Mar  6 02:42:49 2011
>  DistUpgraded: Log time: 2011-03-03 20:05:16.908415
>  DistroCodename: natty
>  DistroVariant: ubuntu
>  DkmsStatus: nvidia-current, 270.29, 2.6.38-5-generic, x86_64: installed
>  GraphicsCard:
>   nVidia Corporation ION VGA [GeForce 9400M] [10de:0876] (rev b1) (prog-if 00 [VGA controller])
>     Subsystem: ASUSTeK Computer Inc. Device [1043:8402]
>  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110301.1)
>  InstallationMedia_: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110301.1)
>  JockeyStatus: xorg:nvidia_current - NVIDIA accelerated graphic...

[[e-mail] (anthonyjschulte)]

...not sure how I would try this...

killall compiz, and somehow reopen from a terminal?

I will post my .xsession-errors to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/753144 tonight.

I am also having some other issues that may or may not be related... GDI pixbuf assertions failing If I recall (I am at work)

[Sam Spilsbury (smspillaz)]

unity --replace

On Thu, Apr 7, 2011 at 11:46 PM, <email address hidden>
<email address hidden> wrote:
> ...not sure how I would try this...
>
> killall compiz, and somehow reopen from a terminal?
>
> I will post my .xsession-errors to:
> https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/753144 tonight.
>
> I am also having some other issues that may or may not be related... GDI
> pixbuf assertions failing If I recall (I am at work)
>
> --
> You received this bug notification because you are a member of Unity
> Bugs, which is subscribed to unity in Ubuntu.
> https://bugs.launchpad.net/bugs/729979
>
> Title:
>  Windows sometimes become blank/transparent when changing focus to them
>  in natty
>
> Status in “compiz” package in Ubuntu:
>  Invalid
> Status in “unity” package in Ubuntu:
>  Invalid
>
> Bug description:
>  Binary package hint: compiz
>
>  When switching focus from one window to another, the target window may
>  become blank. See the attached screenshot, where I opened two gnome-
>  terminals and clicked on their titlebars alternately - the issue was
>  triggered after about 5-10 clicks. I've had this happen on other
>  appications too, e.g. software-centre, empathy, etc.
>
>  Doing shade+unshade, maximizing or clicking away from the problematic
>  window usually makes the window contents come back. The window remains
>  responsive to both keyboard and mouse (by the way, in the screenshot
>  the mouse cursor was an I-beam before I pressed PrtScr).
>
>  This is on up-to-date natty, installed from scratch using the daily
>  image from the 1st of March.
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 11.04
>  Package: compiz 1:0.9.4-0ubuntu3
>  ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
>  Uname: Linux 2.6.38-5-generic x86_64
>  NonfreeKernelModules: nvidia
>  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0'
>  .proc.driver.nvidia.registry: Binary: ""
>  .proc.driver.nvidia.version:
>   NVRM version: NVIDIA UNIX x86_64 Kernel Module  270.29  Wed Feb 23 16:18:35 PST 2011
>   GCC version:  gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-3ubuntu3)
>  Architecture: amd64
>  CompizPlugins: [core,bailer,detection,composite,opengl,decor,imgsvg,resize,resizeinfo,mousepoll,wall,regex,animation,place,blur,compiztoolbox,text,session,grid,put,imgpng,imgjpeg,gnomecompat,commands,copytex,wobbly,annotate,move,vpswitch,workarounds,expo,ezoom,staticswitcher,fade,scale,scaleaddon,unityshell]
>  CompositorRunning: compiz
>  Date: Sun Mar  6 02:42:49 2011
>  DistUpgraded: Log time: 2011-03-03 20:05:16.908415
>  DistroCodename: natty
>  DistroVariant: ubuntu
>  DkmsStatus: nvidia-current, 270.29, 2.6.38-5-generic, x86_64: installed
>  GraphicsCard:
>   nVidia Corporation ION VGA [GeForce 9400M] [10de:0876] (rev b1) (prog-if 00 [VGA controller])
>     Subsystem: ASUSTeK Computer Inc. Device [1043:8402]
>  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110301.1)
>  InstallationMedia_: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110301.1)
>  JockeyStatus: xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use)
>  Lsusb:
>   Bus 004 Device 001: ID 1d...

[[e-mail] (anthonyjschulte)]

tony@siddhartha:~$ sudo unity --replace
[sudo] password for tony:

(process:2060): GLib-WARNING **: In call to g_spawn_sync(), exit status of a child process was requested but SIGCHLD action was set to SIG_IGN and ECHILD was received by waitpid(), so exit status can't be returned. This is a bug in the program calling g_spawn_sync(); either don't request the exit status, or don't set the SIGCHLD action.
GConf Error: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Abnormal program termination spawning command line `dbus-launch --autolaunch=04c5cad7d29cd8e6cb65d5ca00000009 --binary-syntax --close-stderr': )
Backend : gconf
Integration : true
Profile : unity
Adding plugins
Initializing core options...done

(process:2060): GConf-WARNING **: Directory `/apps/compiz-1' was not being monitored by GConfClient 0x952f220
Initializing bailer options...done
Initializing detection options...done
Initializing composite options...done
Initializing opengl options...done
Initializing decor options...done
Initializing mousepoll options...done
Initializing vpswitch options...done
Initializing animation options...done
Initializing snap options...done
Initializing expo options...done
Initializing move options...done
Initializing place options...done
Initializing grid options...done
Initializing gnomecompat options...done
Initializing wall options...done
Initializing ezoom options...done
Initializing workarounds options...done
Initializing staticswitcher options...done
Initializing resize options...done
Initializing fade options...done
Initializing unitymtgrabhandles options...done
Initializing scale options...done
Initializing session options...done
** (<unknown>:2060): DEBUG: Unity accessibility initialization

** (<unknown>:2060): WARNING **: Unable to load GDesktopAppInfo for 'ubiquity-gtkui.desktop'

** (<unknown>:2060): WARNING **: Desktop file 'ubiquity-gtkui.desktop' Does not exist anywhere we can find it

(<unknown>:2060): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(<unknown>:2060): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(<unknown>:2060): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

Screen geometry changed:
  Monitor 0(primary)
   0x0x1440x900

Initializing unityshell options...done
** (<unknown>:2060): DEBUG: MaximizeIfBigEnough: Gnome-terminal window size doesn't fit
Changed: favorites
Changed: favorites
Changed: favorite-migration
** (<unknown>:2060): DEBUG: PlaceEntry: Files & Folders
** (<unknown>:2060): DEBUG: PlaceEntry: Applications
** (<unknown>:2060): DEBUG: PlaceEntry: Commands

(<unknown>:2060): libindicator-WARNING **: Shortcut Group does not have key 'TargetEnvironment' falling back to deprecated use of 'OnlyShowIn' and 'NotShowIn'.
** (<unknown>:2060): DEBUG: Acquired the name com.canonical.Unity.Launcher on the session bus

** (<unknown>:2060): DEBUG: Connected to proxy

(<unknown>:2060): dee-WARNING **: Transaction from com.canonical.Unity.File...

[pablomme (pablomme)]

You certainly don't want to run that with sudo.

[[e-mail] (anthonyjschulte)]

oops-- why is that? It gives root priv. to all processes in unity?

[pablomme (pablomme)]

It runs compiz with the unity profile as root, yes, but rather than being a security/permissions issue I would guess it simply wouldn't connect to the user's X session and Gnome services and crash due to that. Do it without sudo for useful output.

[[e-mail] (anthonyjschulte)]

tony@siddhartha:~$ unity --replace
Backend : gconf
Integration : true
Profile : unity
Adding plugins
Initializing core options...done
Initializing bailer options...done
Initializing detection options...done
Initializing composite options...done
Initializing opengl options...done
Initializing decor options...done
Initializing mousepoll options...done
Initializing vpswitch options...done
Initializing animation options...done
Initializing snap options...done
Initializing expo options...done
Initializing move options...done
Initializing place options...done
Initializing grid options...done
Initializing gnomecompat options...done
Initializing wall options...done
Initializing ezoom options...done
Initializing workarounds options...done
Initializing staticswitcher options...done
Initializing resize options...done
Initializing fade options...done
Initializing unitymtgrabhandles options...done
Initializing scale options...done
Initializing session options...done
** (<unknown>:1938): DEBUG: Unity accessibility initialization

Screen geometry changed:
  Monitor 0(primary)
   0x0x1440x900

Initializing unityshell options...done
** (<unknown>:1938): DEBUG: MaximizeIfBigEnough: Gnome-terminal window size doesn't fit
** (<unknown>:1938): DEBUG: PlaceEntry: Files & Folders
** (<unknown>:1938): DEBUG: PlaceEntry: Applications
** (<unknown>:1938): DEBUG: PlaceEntry: Commands

(<unknown>:1938): libindicator-WARNING **: Shortcut Group does not have key 'TargetEnvironment' falling back to deprecated use of 'OnlyShowIn' and 'NotShowIn'.
** (<unknown>:1938): DEBUG: Acquired the name com.canonical.Unity.Launcher on the session bus

** (<unknown>:1938): DEBUG: Connected to proxy
** (<unknown>:1938): DEBUG: Connected to proxy
** (<unknown>:1938): DEBUG: Connected to proxy

(<unknown>:1938): GLib-GIO-CRITICAL **: g_bus_own_name: assertion `g_dbus_is_name (name) && !g_dbus_is_unique_name (name)' failed

(<unknown>:1938): GLib-GIO-CRITICAL **: g_bus_watch_name: assertion `g_dbus_is_name (name)' failed

(<unknown>:1938): GLib-GIO-CRITICAL **: g_bus_own_name: assertion `g_dbus_is_name (name) && !g_dbus_is_unique_name (name)' failed

(<unknown>:1938): GLib-GIO-CRITICAL **: g_bus_watch_name: assertion `g_dbus_is_name (name)' failed

(<unknown>:1938): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion `object_path != NULL && g_variant_is_object_path (object_path)' failed

(<unknown>:1938): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion `object_path != NULL && g_variant_is_object_path (object_path)' failed
** (<unknown>:1938): DEBUG: IndicatorAdded: libapplication.so
** (<unknown>:1938): DEBUG: IndicatorAdded: libsoundmenu.so
** (<unknown>:1938): DEBUG: IndicatorAdded: libmessaging.so
** (<unknown>:1938): DEBUG: IndicatorAdded: libdatetime.so
** (<unknown>:1938): DEBUG: IndicatorAdded: libme.so
** (<unknown>:1938): DEBUG: IndicatorAdded: libsession.so
Setting Update "run_command_terminal_key"
Setting Update "force_glx_sync"
Setting Update "fullscreen_visual_bell"
Setting Update "launcher_hide_mode"
** (<unknown>:1938): DEBUG: Setting to primary screen rect: x=0 y=0 w=1440 h=900

[Sam Spilsbury (smspillaz)]

I need the output for when you actually start getting blank windows.
Screenshot would be nice.

On Fri, Apr 8, 2011 at 10:42 AM, <email address hidden>
<email address hidden> wrote:
> tony@siddhartha:~$ unity --replace
> Backend     : gconf
> Integration : true
> Profile     : unity
> Adding plugins
> Initializing core options...done
> Initializing bailer options...done
> Initializing detection options...done
> Initializing composite options...done
> Initializing opengl options...done
> Initializing decor options...done
> Initializing mousepoll options...done
> Initializing vpswitch options...done
> Initializing animation options...done
> Initializing snap options...done
> Initializing expo options...done
> Initializing move options...done
> Initializing place options...done
> Initializing grid options...done
> Initializing gnomecompat options...done
> Initializing wall options...done
> Initializing ezoom options...done
> Initializing workarounds options...done
> Initializing staticswitcher options...done
> Initializing resize options...done
> Initializing fade options...done
> Initializing unitymtgrabhandles options...done
> Initializing scale options...done
> Initializing session options...done
> ** (<unknown>:1938): DEBUG: Unity accessibility initialization
>
> Screen geometry changed:
>  Monitor 0(primary)
>   0x0x1440x900
>
> Initializing unityshell options...done
> ** (<unknown>:1938): DEBUG: MaximizeIfBigEnough: Gnome-terminal window size doesn't fit
> ** (<unknown>:1938): DEBUG: PlaceEntry: Files & Folders
> ** (<unknown>:1938): DEBUG: PlaceEntry: Applications
> ** (<unknown>:1938): DEBUG: PlaceEntry: Commands
>
> (<unknown>:1938): libindicator-WARNING **: Shortcut Group does not have key 'TargetEnvironment' falling back to deprecated use of 'OnlyShowIn' and 'NotShowIn'.
> ** (<unknown>:1938): DEBUG: Acquired the name com.canonical.Unity.Launcher on the session bus
>
> ** (<unknown>:1938): DEBUG: Connected to proxy
> ** (<unknown>:1938): DEBUG: Connected to proxy
> ** (<unknown>:1938): DEBUG: Connected to proxy
>
> (<unknown>:1938): GLib-GIO-CRITICAL **: g_bus_own_name: assertion
> `g_dbus_is_name (name) && !g_dbus_is_unique_name (name)' failed
>
> (<unknown>:1938): GLib-GIO-CRITICAL **: g_bus_watch_name: assertion
> `g_dbus_is_name (name)' failed
>
> (<unknown>:1938): GLib-GIO-CRITICAL **: g_bus_own_name: assertion
> `g_dbus_is_name (name) && !g_dbus_is_unique_name (name)' failed
>
> (<unknown>:1938): GLib-GIO-CRITICAL **: g_bus_watch_name: assertion
> `g_dbus_is_name (name)' failed
>
> (<unknown>:1938): GLib-GIO-CRITICAL **:
> g_dbus_connection_register_object: assertion `object_path != NULL &&
> g_variant_is_object_path (object_path)' failed
>
> (<unknown>:1938): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion `object_path != NULL && g_variant_is_object_path (object_path)' failed
> ** (<unknown>:1938): DEBUG: IndicatorAdded: libapplication.so
> ** (<unknown>:1938): DEBUG: IndicatorAdded: libsoundmenu.so
> ** (<unknown>:1938): DEBUG: IndicatorAdded: libmessaging.so
> ** (<unknown>:1938): DEBUG: IndicatorAdded: libdatetime.so
> ** (<unknown>:1938): DEBUG: IndicatorAdded: libme.so
> ** (<unknown>:1938): DEBU...

[[e-mail] (anthonyjschulte)]

All that info including screenshots is posted at https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/753144

I can repost here if necessary, but it was recommended that I file my own bug since OP says it stopped on his machine.

[Garrett (elite-installs)]

I belive my problem went away when i disabled the Focus Animation from CompizConfig -> Animations -> Focus Animation

> Date: Fri, 8 Apr 2011 06:06:37 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: Re: [Bug 729979] Re: Windows sometimes become blank/transparent when changing focus to them in natty
>
> I need the output for when you actually start getting blank windows.
> Screenshot would be nice.
>
> On Fri, Apr 8, 2011 at 10:42 AM, <email address hidden>
> <email address hidden> wrote:
> > tony@siddhartha:~$ unity --replace
> > Backend : gconf
> > Integration : true
> > Profile : unity
> > Adding plugins
> > Initializing core options...done
> > Initializing bailer options...done
> > Initializing detection options...done
> > Initializing composite options...done
> > Initializing opengl options...done
> > Initializing decor options...done
> > Initializing mousepoll options...done
> > Initializing vpswitch options...done
> > Initializing animation options...done
> > Initializing snap options...done
> > Initializing expo options...done
> > Initializing move options...done
> > Initializing place options...done
> > Initializing grid options...done
> > Initializing gnomecompat options...done
> > Initializing wall options...done
> > Initializing ezoom options...done
> > Initializing workarounds options...done
> > Initializing staticswitcher options...done
> > Initializing resize options...done
> > Initializing fade options...done
> > Initializing unitymtgrabhandles options...done
> > Initializing scale options...done
> > Initializing session options...done
> > ** (<unknown>:1938): DEBUG: Unity accessibility initialization
> >
> > Screen geometry changed:
> > Monitor 0(primary)
> > 0x0x1440x900
> >
> > Initializing unityshell options...done
> > ** (<unknown>:1938): DEBUG: MaximizeIfBigEnough: Gnome-terminal window size doesn't fit
> > ** (<unknown>:1938): DEBUG: PlaceEntry: Files & Folders
> > ** (<unknown>:1938): DEBUG: PlaceEntry: Applications
> > ** (<unknown>:1938): DEBUG: PlaceEntry: Commands
> >
> > (<unknown>:1938): libindicator-WARNING **: Shortcut Group does not have key 'TargetEnvironment' falling back to deprecated use of 'OnlyShowIn' and 'NotShowIn'.
> > ** (<unknown>:1938): DEBUG: Acquired the name com.canonical.Unity.Launcher on the session bus
> >
> > ** (<unknown>:1938): DEBUG: Connected to proxy
> > ** (<unknown>:1938): DEBUG: Connected to proxy
> > ** (<unknown>:1938): DEBUG: Connected to proxy
> >
> > (<unknown>:1938): GLib-GIO-CRITICAL **: g_bus_own_name: assertion
> > `g_dbus_is_name (name) && !g_dbus_is_unique_name (name)' failed
> >
> > (<unknown>:1938): GLib-GIO-CRITICAL **: g_bus_watch_name: assertion
> > `g_dbus_is_name (name)' failed
> >
> > (<unknown>:1938): GLib-GIO-CRITICAL **: g_bus_own_name: assertion
> > `g_dbus_is_name (name) && !g_dbus_is_unique_name (name)' failed
> >
> > (<unknown>:1938): GLib-GIO-CRITICAL **: g_bus_watch_name: assertion
> > `g_dbus_is_name (name)' failed
> >
> > (<unknown>:1938): GLib-GIO-CRITICAL **:
> > g_dbus_connection_register_object: assertion `object_path != NULL &&
> > g_variant_is_object_path (object_path)' failed
> >
> > (<unknown>:19...

[Josh Leverette (coder543)]

sadly mine persists. I can't exceed certain window dimensions.. i'll give it
time. Maybe that will help.

[FernanAguero (fernan-ciudad)]

This is also affecting me. Very, __very__ annoying. It happens both in unity and in ubuntu classic.

Box is a Dell Optiplex 740 (AMD), i386. I can provide further details if guided. Let me know what you want me to capture, send.

--
fernan

[FernanAguero (fernan-ciudad)]

Locking the screen (screensaver) would also get you a completely white screen. You can unlock it by typing your password blindly ...

[FernanAguero (fernan-ciudad)]

Just to clarify: It happens both in unity and in ubuntu classic when the nvidia driver is active (nvidia current)

[Daniel van Vugt (vanvugt)]

Fix committed into lp:compiz at revision 3223

[Daniel van Vugt (vanvugt)]

Sorry, that was premature.

Only white window bug 1002602 is definitely fixed. Not this one. Though I suspect we need to divide the duplicates of this bug into a couple of bugs. It's possible some of them might have been fixed with bug 1002602. However I still get white windows when restoring minimized windows using the Unity switcher for example.

[Sam Spilsbury (smspillaz)]

Hmm, that's strange. I put in a workaround for bug 729979 in http://bazaar.launchpad.net/~unity-team/unity/trunk/revision/2273 of unity. While it is a workaround, both didrocks and I tested it and it worked for both of us.

Daniel, do you have "keep previews of mimized windows" disabled? If so - we should remove the option, it is meant to be on by default, and the only reason I had it as an option was because it wasn't fully polished when it went in.

[Daniel van Vugt (vanvugt)]

"Keep previews of mimized windows" is disabled as it is for everyone in 12.04. If you think it should be enabled, then a proposal enabling it should be made.

I have now tested enabling it, with standard precise AND with this fix backported to precise. In all cases the white windows persist on restore (using Unity).

Note the white windows on restore only happen with Unity. Running the latest lp:compiz without Unity, there are no white window problems. I have not yet tested other combinations, so please don't ask.

[Sam Spilsbury (smspillaz)]

On Thu, 7 Jun 2012, Daniel van Vugt wrote:

> "Keep previews of mimized windows" is disabled as it is for everyone in
> 12.04. If you think it should be enabled, then a proposal enabling it
> should be made.
>
> I have now tested enabling it, with standard precise AND with this fix
> backported to precise. In all cases the white windows persist on restore
> (using Unity).
>

My Apologies, I meant "Show minimized windows in switcher" (Keep previews
of minimized windows in workarounds should in fact be removed to avoid the
confusion as we don't use it elsewhere in compiz). Looking at the XML file
says that its turned on by default.

The reason I asked is beacuse the hack basically has no effect if this
option is turned off. In any case, I'm pretty sure that part the the
original bug I fixed said that if you disabled keeping previews, this didn't
happen.

(I'd love to deliver a real fix, however I just don't know enough about
the driver to understand what its doing that's causing us to lose binding
here. According to the tfp documentation you only need to rebind whenever
the pixmap becomes invalid, and this is what we do. With
"show_minimized_windows" on - the windows nor their frames are not even
resized when they are (un)minimized. That being said, its entirely
possible that a separate opengl operation is triggering a driver bug
causing the pixmap binding to be lost)

> Note the white windows on restore only happen with Unity. Running the
> latest lp:compiz without Unity, there are no white window problems. I
> have not yet tested other combinations, so please don't ask.
>
> --
> You received this bug notification because you are a member of Compiz
> Maintainers, which is the registrant for Compiz Core.
> https://bugs.launchpad.net/bugs/729979
>
> Title:
> [nvidia] Windows appear blank white
>
> Status in Compiz:
> Triaged
> Status in Compiz Core:
> Triaged
> Status in “compiz” package in Ubuntu:
> Triaged
>
> Bug description:
> Binary package hint: compiz
>
> When switching focus from one window to another, the target window may
> become blank. See the attached screenshot, where I opened two gnome-
> terminals and clicked on their titlebars alternately - the issue was
> triggered after about 5-10 clicks. I've had this happen on other
> appications too, e.g. software-centre, empathy, etc.
>
> Doing shade+unshade, maximizing or clicking away from the problematic
> window usually makes the window contents come back. The window remains
> responsive to both keyboard and mouse (by the way, in the screenshot
> the mouse cursor was an I-beam before I pressed PrtScr).
>
> This is on up-to-date natty, installed from scratch using the daily
> image from the 1st of March.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 11.04
> Package: compiz 1:0.9.4-0ubuntu3
> ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
> Uname: Linux 2.6.38-5-generic x86_64
> NonfreeKernelModules: nvidia
> .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0'
> .proc.driver.nvidia.registry: Binary: ""
> .proc.driver.nvidia.version:
> NVRM version: NVIDIA UNIX x86_64 Kernel Module 270.29 Wed Feb ...

[Iestyn Guest (iguest)]

Hi there,

If it's any help, I've found that disabling "Animations" from the
Effects category in CCSM eliminates the white windows. That is to say,
that when maximizing previously minimized windows by using the window
switcher (drilling into multiple minimized windows of the same type) no
longer brings up a white window.

Re-enabling the top level "Animations" check box restores the broken
behavior.

Hope this helps.

Kind regards,

Iestyn

On 06/07/2012 04:14 AM, Sam Spilsbury wrote:
> On Thu, 7 Jun 2012, Daniel van Vugt wrote:
>
>> "Keep previews of mimized windows" is disabled as it is for everyone in
>> 12.04. If you think it should be enabled, then a proposal enabling it
>> should be made.
>>
>> I have now tested enabling it, with standard precise AND with this fix
>> backported to precise. In all cases the white windows persist on restore
>> (using Unity).
>>
> My Apologies, I meant "Show minimized windows in switcher" (Keep previews
> of minimized windows in workarounds should in fact be removed to avoid the
> confusion as we don't use it elsewhere in compiz). Looking at the XML file
> says that its turned on by default.
>
> The reason I asked is beacuse the hack basically has no effect if this
> option is turned off. In any case, I'm pretty sure that part the the
> original bug I fixed said that if you disabled keeping previews, this didn't
> happen.
>
> (I'd love to deliver a real fix, however I just don't know enough about
> the driver to understand what its doing that's causing us to lose binding
> here. According to the tfp documentation you only need to rebind whenever
> the pixmap becomes invalid, and this is what we do. With
> "show_minimized_windows" on - the windows nor their frames are not even
> resized when they are (un)minimized. That being said, its entirely
> possible that a separate opengl operation is triggering a driver bug
> causing the pixmap binding to be lost)
>
>> Note the white windows on restore only happen with Unity. Running the
>> latest lp:compiz without Unity, there are no white window problems. I
>> have not yet tested other combinations, so please don't ask.
>>
>> --
>> You received this bug notification because you are a member of Compiz
>> Maintainers, which is the registrant for Compiz Core.
>> https://bugs.launchpad.net/bugs/729979
>>
>> Title:
>> [nvidia] Windows appear blank white
>>
>> Status in Compiz:
>> Triaged
>> Status in Compiz Core:
>> Triaged
>> Status in “compiz” package in Ubuntu:
>> Triaged
>>
>> Bug description:
>> Binary package hint: compiz
>>
>> When switching focus from one window to another, the target window may
>> become blank. See the attached screenshot, where I opened two gnome-
>> terminals and clicked on their titlebars alternately - the issue was
>> triggered after about 5-10 clicks. I've had this happen on other
>> appications too, e.g. software-centre, empathy, etc.
>>
>> Doing shade+unshade, maximizing or clicking away from the problematic
>> window usually makes the window contents come back. The window remains
>> responsive to both keyboard and mouse (by the way, in the screenshot
>> the mouse cursor was an I-beam before I pressed...

[bear7 (bear7)]

To fix that issue you don't have to disable all the animations. What you need to do is go to Animations in CCSM, choose the "Focus Animation" tab and change the "Focus Effect" from "Dodge" or "Fade" or "Wave" TO "None" or "Not selected". That did the trick for me. All other animations are working well. Not happy with that resolution (i like the Dodge animation) but the blank windows were annoying me much more.

[Magnetizer (magnetizer)]

@lniedzwiecki:

I doubt that is true.

I still do encounter some blank windows on restoring and I never had the dodge animation set.

I will try disabling all animations as Iestyn suggests.

The problem is that the bug does not show very often anymore (which is fine, of course) but it makes it difficult to say whether the problem is really solved.

[Bruce Crowther (bwucie)]

Abandoning the nvidia driver for Nouveau was the simple answer for me. Definitely Nouveau is not the equal of the Nvidia driver, but it provides adequate display for me, and causes no problems.

[Daniel van Vugt (vanvugt)]

smspillaz:
"Show minimized windows in switcher" is enabled as per the default. And it works too. Minimized windows look right in the switcher. They're just white when restored.

[Daniel van Vugt (vanvugt)]

And concurring with Bruce - Yes the nouveau driver will avoid all white window bugs.

[Iestyn Guest (iguest)]

Thanks for the tip. Setting just the "Focus Effect" to "None" didn't
fix it for me - It did turn out to be part of a successful workaround
though. After systematically turning off all of the effects one-by-one
and re-enabling them one-by-one, I found that both the "Minimize Effect"
and the "Focus Effect" together need to be set to "None". Only then do
I get around the white window on maximize problem.

Thanks so much for the tip.

Kind regards,

Iestyn Guest

On 06/07/2012 05:50 PM, lniedzwiecki wrote:
> To fix that issue you don't have to disable all the animations. What you
> need to do is go to Animations in CCSM, choose the "Focus Animation" tab
> and change the "Focus Effect" from "Dodge" or "Fade" or "Wave" TO "None"
> or "Not selected". That did the trick for me. All other animations are
> working well. Not happy with that resolution (i like the Dodge
> animation) but the blank windows were annoying me much more.
>

[Serrano Pereira (serrano-pereira)]

In my case, setting just the "Focus Animation" to "None" does work. Even with a "Minimize Animation" set. Occasionally however, menu's still display all white (whilst remaining clickable). But this happens rarely.

[FuzzyQ (atomicfuzzyq)]

The problem with focus animation effect is already filed in bug #1010091.
Your subscription and any additional information that could help exterminate that bug would be very much appreciated.

Best regards.

[triplesqaurednine (triplesquarednine)]

Out of curiosity, is anyone whom is affected by this bug NOT using Ubuntu?

I ask because i can't produce this bug and I am an Nvidia user (302.11-beta) ... The only time i can produce white windows, is by messing with the shadow radius settings in the 'window decoration' plugin. Which i filed here;

https://bugs.launchpad.net/compiz/+bug/991662

Although, the bug from my report is actually worse, only because you have to kill compiz and restart it to be able to use your desktop - it can easily be avoided, so it has less impact on actual usage (as long as you don't mess with shadow radius settings). I believe this window whiting may be tied into the window decoration somehow (ie: if you use compiz without a window decoration you won't get white windows at all. (i tried this out, a month or so ago, when white windows were an issue for me).

I was at one point experiencing this (related/duplicate) bug;

https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/976189

but i ended up being able to avoid it by not using a window decoration for maximized windows;

!(state=maxvert & state=maxhorz)

Which also leads me to believe (although, i could be wrong) that may be this bug has something to do with window decorations, being as when i was experiencing bug 976189 undecorating maximized windows stopped them from appearing white.

I do still notice (at least with Firefox) that menu's when closing (animation, in my case 'fade') do show some white for a split second, but other than this i can't produce white windows of any kind.

NOTE: i do have a few nvidia driver (xorg) settings on my system, and am not sure if they would make a difference here or not;

     Option "RegistryDwords" "PerfLevelSrc=0x2222"
     Option "NoLogo" "1"
     Option "TripleBuffer" "1"
     Option "DamageEvents" "1"
     Option "PixmapCacheSize" "70000"
     Option "OnDemandVBlankInterrupts" "True"

the rest of my specs can be found on my LP page;

https://launchpad.net/~triplesquarednine

I've also attached my flat-file config for compiz ( i don't use gconf-backend )

cheerz

[Zsolt Lauter (lauterzsolti)]

I set Effects > Animations > Minimize animation to "None" in CCSM and now I don't have blank white windows.

[quequotion (quequotion)]

Nvidia has added a new option for the drivers, "Use Conformant Texture Clamping" in version 302.

As of 302.17:

"Added a checkbox to nvidia-settings to control the texture clamping attribute. When the box is checked, OpenGL textures are clamped according to the OpenGL specification. When it is unchecked, GL_CLAMP is remapped to GL_CLAMP_TO_EDGE for borderless 2D textures."

Could this affect the issue?

[Daniel van Vugt (vanvugt)]

No, clamping should not be related to this bug. But you're encouraged to try different driver versions :)

[triplesqaurednine (triplesquarednine)]

@quequotion

I have been using that 302.17 since the day it was released (with clamping on - im pretty sure that is the default, now).

in the one or two situations where i see a little white, it has no effect.

[Launchpad Janitor (janitor)]

This bug was fixed in the package compiz - 1:0.9.8+bzr3249-0ubuntu1

---------------
compiz (1:0.9.8+bzr3249-0ubuntu1) quantal-proposed; urgency=low

  * New upstream snapshot.
    - Fall back to a refresh rate that is more likely to look correct; 60Hz.
      (LP: #1009338)
    - Benchmark plugin should consume its key binding, and not pass the key to
      the underlying window. (LP: #1009320)
    - Avoid needless STL operations leading to expensive heap operations.
      (LP: #1006335)
    - Fix a typo that was causing (LP: #1002606)
      (widthIncBorders/heightIncBorders)
    - Check if the window is decorated before trying to change its event window
      states (which won't exist if not decorated) (LP: #1007754)
    - Use the XDamage extension more efficiently (the way it was designed to be
      used). This dramatically reduces CPU usage, reduces wakeups, and
      increases frame rates. It also solves at least one observed performance
      bug (LP: #1007299) and probably several more.
    - Avoid constructing and destructing lots of strings on every single event,
      which was wasting lots of CPU (LP: #1005569)
    - md LINGUAS doesn't exist, it's mnk (Mandinka in ISO 639-3)
    - Move grid plugin to google test and don't depend on the plugin for the
      test (LP: #1005009)
    - Don't read plugin.Initialized and test the value. (LP: #1004848)
    - libcompizconfig's install () commands were still using the old includedir
      and libdir variables rather than their libcompizconfig_* variants.
      (LP: #1005176)
    - Execute the cmake files separately to ensure that DESTDIR is respected.
      (LP: #1005177)
    - Don't set_target_properties on a target that might not exist
      (LP: #1005008)
    - Don't allow windows which we weren't even tracking as decoratable to
      become decorated if they try and change their hints. (LP: #963794)
    - Change the mouse pointer while dragging windows in expo. Just like the
      ubuntu branches do. (LP: #987647)
    - Fix uninitialized memory use (LP: #1004338)
    - Fix uninitialized variable (LP: #1004335)
    - Delay unbinding of pixmaps until then next rebind (LP: #729979)
      (LP: #1002602)
    - Don't drop plugins from the list to try and load before you've even tried
      to load them. Doing so makes missing plugins silently ignored instead of
      an error message (LP: #1002715). It also means valid plugins in more
      unusual, but real locations in LD_LIBRARY_PATH will never get loaded
      (LP: #1002721).
    - If running test cases under a real X server, we don't care if Xvfb is
      missing (LP: #994841)
    - Don't assume pkg_check_modules always sets _PREFIX (LP: #993608)
    - Don't clear selections in ~PrivateScreen because it causes a race between
      the existing and the new compiz instances, breaking --replace and
      non-replace behaviour. (LP: #988684) (LP: #989545)
    - Always paint with infiniteRegion as the clip region if the window is
      transformed and always use the supplied region if painting with offset or
      on transformed screen. (LP: #987639)
    - Add synchronization primitives to the decoration protocol so that there
      isn't a r...

[Daniel van Vugt (vanvugt)]

Ignore the above message. It's a script that finds and updates bugs and it found incorrect data.

[Teo (teo1978)]

Please consider changing the importance from HIGH to CRITICAL.

Example: I had Eclipse open but minimized, I closed it by right-clicking on its icon and the "confirm exit" dialog popped up, because there was some unsaved file open. However, the window was blank white so I couldn't click either "save", "don't save", "ok" or "cancel" or whatever (I don't even remember exactly what the available options are".

Even by clicking Eclipse icon again to reminimize and remaximize it, the dialog would always show up white.

I had no other option that kill the process to quit the program. This bug can have consequences as devastating as this.

[Teo (teo1978)]

critical or whatever the highest importance is

[Leo (leopoldo-pena)]

+1

This bug persists even after the last updates...It does disrupt the daily workflow....i get 20-30+ white windows in a regular morning of work (maximize/minimize open applications).

[Neil Rodgers (neilr1971)]

I noticed that while using the emerald window decorator this bug goes away completely for me. All animations, dodge effect minimizing etc. working and no white windows. As soon as I issue a the command $gtk-window-decorator --replace the white windows return instantly upon selecting another window. Something going on in the decorator maybe? Using Ubuntu 12.04 with nvidia 295.40 binary driver

[joncamfield (jon-camfield)]

This bug is really, really a problem in adoption for us NV users. Other, related bugs:

https://bugs.launchpad.net/compiz/+bug/1002602
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/753144

And yes, still a problem, a year later.

[Mudito (mudito-f)]

I've tried installing Emerald on Compiz and it got a little bit better:

Before:
   Any minimized window, when restored would come up blank

Now (with Emerald)
   If a window is maximized, when you minimize it and then restore (or
use alt-tab) it comes up blank
   If a window is not maximized, when you minimize it and then restore
(or alt-tab) it comes up OK.

IS ANYONE AT ALL LOOKING AT THIS BUG????? It looks like Compiz more than
NVidia to me... I unfortunately don't have the knowledge to help fixing
it. Alas!

On 10/08/12 13:02, joncamfield wrote:
> This bug is really, really a problem in adoption for us NV users.
> Other, related bugs:
>
> https://bugs.launchpad.net/compiz/+bug/1002602
> https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/753144
>
> And yes, still a problem, a year later.
>

[Ronnie (ronnie-10)]

compiling compiz from source (bzr branch lp:compiz) fixes the blank window focus animation problem. However the problem persists in version 1:0.9.8+bzr3249-0ubuntu2 which is the latest compiz found in quantal and in version 0.9.8-1+bzr3305-staging1-201208080203~quantal1_amd64.deb.

Any suggestions on why is that happening? the one i compiled says its compiz 0.9.8 while the ubuntu compiz ppa has the newer 0.9.8.1 version.

[Mudito (mudito-f)]

Found a solution, which is crappiest but... use the horrible Unity
switcher, I was using Compiz Ring switcher, changed back to Unity and
now the problem doesn't occur. I needed something with a app preview but
I guess I'll have to conform to the Unity stuff.

As a palliative I created a launcher on the dock for Scale, so I can
click and see all windows, check if the processes I'm running are over
yet or not, and then keep working. Not the best, but endurable.

[David Warren (earthquakefish)]

Maybe it's your form of English but this is ridden with spoiled. You found
a solution and it's crappiest at best while being "endurable". Just go and
conform... Just f* those who give u something. Sorry for being
insensitive to this.....

I can think of worse things... I can add I'm happy on Fedora 17.

On 18 August 2012 23:32, Mudito <email address hidden> wrote:

> Found a solution, which is crappiest but... use the horrible Unity
> switcher, I was using Compiz Ring switcher, changed back to Unity and
> now the problem doesn't occur. I needed something with a app preview but
> I guess I'll have to conform to the Unity stuff.
>
> As a palliative I created a launcher on the dock for Scale, so I can
> click and see all windows, check if the processes I'm running are over
> yet or not, and then keep working. Not the best, but endurable.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/729979
>
> Title:
> [nvidia] Windows appear blank white
>
> Status in Compiz:
> Triaged
> Status in Compiz Core:
> Triaged
> Status in “compiz” package in Ubuntu:
> Triaged
>
> Bug description:
> Binary package hint: compiz
>
> When switching focus from one window to another, the target window may
> become blank. See the attached screenshot, where I opened two gnome-
> terminals and clicked on their titlebars alternately - the issue was
> triggered after about 5-10 clicks. I've had this happen on other
> appications too, e.g. software-centre, empathy, etc.
>
> Doing shade+unshade, maximizing or clicking away from the problematic
> window usually makes the window contents come back. The window remains
> responsive to both keyboard and mouse (by the way, in the screenshot
> the mouse cursor was an I-beam before I pressed PrtScr).
>
> This is on up-to-date natty, installed from scratch using the daily
> image from the 1st of March.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 11.04
> Package: compiz 1:0.9.4-0ubuntu3
> ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
> Uname: Linux 2.6.38-5-generic x86_64
> NonfreeKernelModules: nvidia
> .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory:
> '/proc/driver/nvidia/gpus/0'
> .proc.driver.nvidia.registry: Binary: ""
> .proc.driver.nvidia.version:
> NVRM version: NVIDIA UNIX x86_64 Kernel Module 270.29 Wed Feb 23
> 16:18:35 PST 2011
> GCC version: gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-3ubuntu3)
> Architecture: amd64
> CompizPlugins:
> [core,bailer,detection,composite,opengl,decor,imgsvg,resize,resizeinfo,mousepoll,wall,regex,animation,place,blur,compiztoolbox,text,session,grid,put,imgpng,imgjpeg,gnomecompat,commands,copytex,wobbly,annotate,move,vpswitch,workarounds,expo,ezoom,staticswitcher,fade,scale,scaleaddon,unityshell]
> CompositorRunning: compiz
> Date: Sun Mar 6 02:42:49 2011
> DistUpgraded: Log time: 2011-03-03 20:05:16.908415
> DistroCodename: natty
> DistroVariant: ubuntu
> DkmsStatus: nvidia-current, 270.29, 2.6.38-5-generic, x86_64: installed
> GraphicsCard:
> nVidia Corporation ION VGA [GeForce 9400M] [10de:0876] (rev b1)
> ...

[Leo (leopoldo-pena)]

will this be backported to 12.04? This is a must fix IMO.

[Charlson C. Kim (charlson-c-kim)]

I have the same problem on my new system with Mint Linux 13 using Mate. I don't think it is a memory issue, i have plenty. When i check my .xsession-errors file is see this message that correlates with the blanking problem

 mate_bg_crossfade_start: assertion `fade->priv->fading_pixmap != NULL' failed

I have seen similar bug reports related to the bg_crossfade. Could this be the culprit?

[Charlson C. Kim (charlson-c-kim)]

with a little more digging I think it is this mate_bg_crossfade_start (in ubuntu the same function is gnome_bg_crossfade_start ) IS THE CULPRIT. There was a variable name change from "fading_pixmap" to "fading_surface" and i guess this did not propagate to some compiz related code. For someone in the know, looks like it should be an easy fix.

[dimovnike (dimovnike)]

fresh install of 12.04 64bit, after apt-get update/upgrade bug is still present. Here it is like this: when clicking a minimized window it may appear as blank-white. Minimizing it and restoring it back usually fixes it.

[Samuel Dowling (sjdowling)]

Also experiencing this on 12.04 64bit with a GeForce GTX 680. Based on comment #69 I took a stab at disabling the fading windows plugin but after a day or so of usage the problem occurred again. I'm disabling the animation plugin now and will see if the bug occurs again.

[Jay S (topdownjimmy)]

One place in which this is consistently reproduced for me is in the Update Manager -- the window starts minimized (I think) during its daily check for updates, and when I restore it, it's blank white.

Usually my remedy is to maximize then restore it, and the contents appear.

[Leonardo Herman (tentaculo)]

I can fully reproduce it with any window (Unity 5.14.0, Compiz 0.9.7.8 - default settings) following these steps:

1) Minimize any window
2) Super+W (to show Scale)
3) Super+W (to hide it)
4) Click on the application icon in Launcher or browse to it using Alt+Tab / Alt+|

Notes:
- Minimizing the blank window and using Scale reverses it.
- This issue does not happen when the app has 2 or more windows (which,again, triggers Scale)

I hope this helps (=

[Leonardo Herman (tentaculo)]

Small mistake, sorry for my english:

- Minimizing the blank window and using Scale REVERTS it.

[Leonardo Herman (tentaculo)]

NVIDIA 310M, nvidia-current (304.43) from ppa:ubuntu-x-swat/x-updates

[digio.space (digiospace)]

This bug has started again for me with the last update. I experienced it earlier this year, but was fixed for me up until the last update yesterday. Now I am getting randmom white windows (does not happen all of the time)

[debili (karatedebili)]

Same thing here, very frustrating :( I think developers should unite in resolving this kind of bugs before anything else, it makes the system unusable

[gianluca.pettinello (g-pet)]

Same here! Frustrating. This bug goes and comes back regularly at each update of nvidia or unity. Also shadow below panel goes and comes back with a click

[emptythevoid (emptythevoid)]

I've got two different machines, one with Ubuntu 12.04 32-bit, the other with 64-bit. Both using nvidia cards with current proprietary drivers (per the x-swat ppa) and this problem occurs.

[DJ (twk3)]

This might be the same as a problem I am having. I get a different colored screens depending on the application, transparent, black, etc, in ubuntu 12.10 with nvidia 304.51. I have only produced it when the application is maximized, and if I open it while it's closing animation is still running. Minimizing and maximizing again slowly fixes the problem. I can repo every time with all the applications I've tried.

[Rainer Rohde (rainer-rohde)]

I also experience a black screen now. I noticed this with Firefox.

Open a couple of Firefox windows > minimize them > ALT-Tab select any one of them > observe black screen.

This happens regardless whether the window is maximized or minimized. Workaround for now: if small window, maximize it. If maximized, resize it.

[bowser (bwbernard-wong1)]

Not fixed in Quantal, except that white windows now become black. Compiz 0.9.8.4 bzr3407

[Rainer Rohde (rainer-rohde)]

I also experienced this with other applications, not just Firefox...

[Rainer Rohde (rainer-rohde)]

Just as an example -- this happens when ALT-Tab'ing between the Virtual Box manager and the actual VM window... black screen. See screenshot attached.

[bowser (bwbernard-wong1)]

It happens to all programs actually.

[stagelll (gedefr)]

I have this very annoying bug since I've upgraded to 12.04 from 11.04.

I have a Nvidia GTX 460 m and i'm using Compiz 0.9.7.8.

To sump up what I've found :

1) to reproduce the bug. You have to :
a) minimize a window
b) use spread view (super + W) and go back to normal
c) maximize the window previously minimized

2) to workaround the bug
a) an instant fix is to change the size of the blank window, even slightly
b) there's two permanent fixes, both through Compiz Config Setting Manager.

α) The first one is, in CCSM, to go to "animations", and there to change "minimize animation"from "zoom" to "none" (and to make sure that focus animation is set to "none" or "N/A").

β) The second one is, in CCSM, to unclick Windows Decoration.

They are only workarounds, as they imply to make do without either animations when maximizing/minimizing windows or decoration on windows (which is quite useful...).

I'd like to suggest that it's quite about time to find a proper solution to a bug that's been around for nearly two years and three releases of Ubuntu, and that affects potentialy anyone with a Nvidia card (that's a lot of people) and that impairs a basic functionality of unity.

[Daniel van Vugt (vanvugt)]

All,

Please test Ubuntu 12.10 if you can. Some of the changes in Compiz 0.9.8 for Ubuntu 12.10 are designed to solve "white windows" bugs with Nvidia. Possibly not all, but it should be better.

[Clint Byrum (clint-fewbar)]

I have not seen the noted effect at all in 12.10, which I've been running since early alpha days. Running on a MacBookPro 5,1 which has an nvidia 9600 something.

[Matthias Niess (mniess)]

I tried this with 12.10 and the driver from nvidia-current-updates and this bug persists (with a black blank window now). I just followed the instructions to reproduce the bug and they work every single time. I can't see any instances where this has gotten better than it was in 12.04.

[triplesqaurednine (triplesquarednine)]

@ Matthias

You are totally correct. This bug still exists.

Clint may not be experiencing it, but 'vanilla-compiz' built yesterday, still exhibits this bug on my machine.

As a side note, switching workspaces and then switching back to the workspace where the black windows was originally, also fixes the window contents. (so resizing/maximizing it isn't the only way(s) to fix it).

It's interesting though, this bug has existed for a very long time and even with so many users affected, there seems to be no progress made on fixing it.... SO! in the hopes of maybe doing something about this ~ or at least getting the ball rolling, and maybe having someone from nvidia actually be aware of the problem, i have started a thread in the _new_ official nvidia forums.

The new nvidia forum (for linux) is found here;

https://devtalk.nvidia.com/default/topic/523298/linux/nvidia-driver-fails-to-draw-window-contents-properly-with-compiz-and-or-unity-white-or-black-window/

Could every single person following this bug report please head over there, sign up (for the nvidia forums) and add your voice to my thread over there, on this bug??? I have provided nVidia with a link to this bug report, so hopefully Plagman (or someone else from nvidia) will take some time to look into this (since it appears to be an nvidia bug) and hopefully fix it.

thanks :)

[triplesqaurednine (triplesquarednine)]

Sorry, i meant my bug report @ the new nvidia forum is there.

the main page for the new linux nvidia forum is here:

https://devtalk.nvidia.com/default/board/98/linux/

anyways, please do sign up and add your voice to my thread.

cheerz

[Alistair Buxton (a-j-buxton)]

I installed 12.10 today to test this. I'm using the nvidia-current driver, not nvidia-current-updates and I haven't seen any blank windows yet. Perhaps the two drivers behave differently?

[Niclas Kiefer (niclas-kiefer)]

I've read something about a new experimental driver for nvidia graphic cards here

http://blog.sudobits.com/2012/11/07/new-nvidia-driver-for-linux-gamers/

and followed the installation instruction. Since i installed the new experimental 310 driver. For an hour nowi have'nt seen any black or white windows. So maybe nvidia fixed it?

[stagelll (gedefr)]

Not for 12.04 at least. I've tried different drivers, and settled on 310.14, because it seems to increase the overall performance, but it has no effect on the bug.

By the way, the bug is mainly Nvidia related, but it looks like its a more profound issue. I've noticed this on my other laptop (with an intel HD graphics card, no Nvidia, 12.04 and compiz 9.7.8) : when I reproduce the steps to get the bug, I have noticed that the minimized windows appears to be white in spread view. It's not when I maximize it again (hence the bug is not there), but it is white in spread view. A lesser variant of the bug, so to speak.

I really wonder how such a bug can be around for so long.

[triplesqaurednine (triplesquarednine)]

@Niclus && @ Alistair

I am running the beta nvidia driver 310.14 - the bug still exists. In fact, i have run every nvidia driver leading upto the current beta, including all of the stable nvidia driver releases inbetween ~ they ALL exhibit the blank window problem, if you try to reproduce the problem.

I also doubt they fixed anything specific to compiz, because their changelogs (for the driver) say nothing of the sort (and they would, if they a bug related to it).

anyway, I again am hoping other people will make some noise over at the new nvidia forums. This is an nvidia bug which is probably why the compiz-devs haven't done anything about it and they probably don't want to have to implement some nvidia hack (even if they could, which i don't know) So we really need to make nvidia aware of the problem.

cheerz

[Alistair Buxton (a-j-buxton)]

It's not true to say this is entirely an nvidia bug. After all, this bug is a regression. It does not happen with any other compositing window manager, and it does not happen with compiz 0.8.

[Rainer Rohde (rainer-rohde)]

Yes indeed -- this bug is alive and kicking.

[Matthias Niess (mniess)]

Also nvidia-experimental-310 is not available for 12.10 (yet).

[stagelll (gedefr)]

@Matthias. You can get it through ppa:xorg-edgers/ppa or through Nvidia, by downloading a nvidia.run driver. (http://www.nvidia.co.uk/Download/Find.aspx?lang=en-uk) That's the way I did it for 12.04.

[bowser (bwbernard-wong1)]

The xorg-edgers driver doesn't fix the problem in 12.10. Like I said before, the white blank windows in 12.04 only change to black blank windows.

[Nice Testhouse (testhouse)]

Week 46 - Same issue observed with Firefox browser on Ubuntu 12.04 Precise Nvidia machine with ppa:unity-team/sru. After step 4, the focussed window (recently minimized) was blank just showing the top title bar.

Please note that any action like a click anywhere on the desktop will bring the window back to normal looking displaying its content.

Test Steps:
Open 2 windows, minize one of them and using alt+tab move to the minimized window.

TEST CASE ID CAN - Can-92 :: Version : 1 alttab/windows-tab-release-minimized

Test Steps:
1 Open an application with multiple windows (some of them should be minimized)
2 Press alt + tab until you highlight this application, hold alt
3 Continue tapping tab to highlight on a minimized window
4 Release alt

Expected result:
-> After a short delay, all windows for this application should be shown (even minimized ones) [2D: fail]
-> The selected window should be restored and focused

[Jan Eppo Jonker (j-e-jonker)]

Ubuntu 12.04 (32bit), Geforce 8800 GTS, NVidia 304.43, Compiz 0.9.7.8,

I am affected by this bug too. Some days ago I decided to give Ubuntu a try again.

I started with Ubuntu 12.10, but it was so unstable that I decided to try 12.04 instead. After installation the system complained vaguely about internal problems. I just ignored this, went ahead and installed the recommended NVIDIA drivers (nvidia-current, 295.40-0ubuntu1.1). This immediately resulted in a very slow system, that after a while became almost unresponsive. After some minutes it just crashed. So I almost gave up on Ubuntu.

However, logging into Ubuntu 2D (click the icon in the login window) resulted in quite normal behavior, so I decided to persist and try the other drivers (10 years ago I got quite used to the quirks of compiling and installing NVIDIA kernel modules). The nvidia-173 driver did not improve things, and neither did nvidia-173-updates. Next I installed nvidia-current-updates (304.43-0ubuntu0.1). Finally, this one looked OK.

So I went ahead. I installed compizconfig, activated the cube and wobbly windows. I missed the Dodge Windows behavior, so I installed the fix (https://help.ubuntu.com/community/Unity-ReplaceDodgeWindowsBehavior). So far so good. All was looking fine after some initial trouble, just like in the good old days.

However, all along I was sometimes looking at a blank or a black or an incompletely filled window. I was hoping the problem would disappear, once I had found the right combination of versions (graphics card, NVIDIA driver, Ubuntu). But no, this bug stays with me, and it bothers me to the point that I will surrender. I have better things to do ;) .

I read part of the above comments. My experience is a bit of a mix of them. I restrict myself now to my present configuration.

Window contents are sometimes blank, sometimes black, sometimes black with some parts visible. Sometimes a window will take a few tenths of a second before showing contents. I have the impression that it is black then for a short time. Sometimes a window will be black for a short time before going blank. The Firefox window that I am typing in just now was black a while ago. When moving the mouse cursor over the window, the search window got filled in when the cursor moved over it, and next this comment window got filled in when the mouse moved over it. The rest of the Firefox window remained black.

Just now I have a Firefox window and a Terminal window. Both have normal contents. When I click on the Terminal window, both windows go blank (white). Only their title bars and shadow stay visible. When I move the mouse pointer over the blank contents of the Firefox window nothing happens. When I click on the Firefox window, both windows get their content back.

Now for a little riddle. I again have these two windows. I can click on any of the two as often as I want in any order, nothing happens to the contents. How can that be?

Well, in the first situation, the two windows had overlap, and in the second situation they had NO overlap. Whenever I move a window partly over another window and click on that other window, both windows go blank. If I click again on that w...

[triplesqaurednine (triplesquarednine)]

@Jan

that is a very long-winded comment. You could have probably not mentioned half of that stuff and more accurately gotten to your point.

On the issue of black-windows - it IS the exact same bug - *not a different one*. On some people's machines it used to appear white (like at the time of reporting this bug), but later became black - yet exhibits the 'exact' same behavior as this bug. I don't use Ubuntu, but i believe 12.04 should exhibit white-windows, while 12.10 + newer nvidia driver exhibits black - but somebody in Ubuntu land would need to varify that because i use Archlinux and vanilla compiz (as opposed to Unity).

As a side note: I'm not feeling positive about this bug actually ever being fixed though. I heard SmSpillaz is no longer even working for Canonical (not that he is the only dev - but certainly a big contributor who is familiar with compiz' internals) and this bug report has had little to no progress in fixing it and has been open for a very long time (unfortunately).

i guess we'll see what happens.

[Alistair Buxton (a-j-buxton)]

@triplesqaurednine when you say "vanilla" compiz do you mean 0.8 from compiz-fusion.org or 0.9 from launchpad?

I have never even once seen the white/black windows happen with 0.8. Then again, you can't run Unity with 0.8, so maybe that is the reason.

[Alistair Buxton (a-j-buxton)]

(and i meant compiz.org)

[triplesqaurednine (triplesquarednine)]

@Alistair

development at compiz.org died quite a while ago... I don't think anyone is building the 0.9.x series from git at this point (and if i remember correctly, compiz 0.9.x is somewhat broken at git.compiz.org anyway.)

 - By vanilla i mean compiz built from the master branch, here @ lp:compiz. ie: 0.9.9 ~ No Unity.

Common sense would dictate that i also wouldn't be reporting / participating in any bug reports (here on launchpad) if I was using 0.8, being as it has nothing to do with current compiz development.

cheerz

[Jan Eppo Jonker (j-e-jonker)]

@triplesquarednine

I don't even now know I had a point. I was only trying to reproduce a bug. I usually find it difficult to remember what actions I take and what happens exactly. Remember this thread started with: 'When switching focus from one window to another, the target window may become blank.' This is not a solid basis upon which to reproduce the bug. Next it is stated 'the issue was triggered after about 5-10 clicks'. So I clicked 30 times, and nothing irregular happened. And yet, I got bitten by this bug in circumstances more or less like this imprecise description.

My main purpose was to reproduce this bug in a deterministic way. If I lost my audience halfway, I'm sorry.

I have Ubuntu 12.04, NOT 12.10 and yet I encounter black window contents regularly. You state 'it is the EXACT same bug'. Only I cannot reproduce it. The only thing I remember is, that it seems to happen with Firefox windows. But if I try to reproduce it (even after rebooting) I only get blank (white) contents.

So please tell me have to reliably (deterministically) get black window contents.

[stagelll (gedefr)]

@Jan

Look at comment #87

[triplesqaurednine (triplesquarednine)]

@alistair

I'd like to point out something that i have noticed in the last few days, that contradicts a previous statement of yours;

"It's not true to say this is entirely an nvidia bug. After all, this bug is a regression. It does not happen with any other compositing window manager, and it does not happen with compiz 0.8."

While you claim this isn't an nvidia bug, i think you are probably wrong. Likewise saying it doesn't happen in any other compositing window manager is also wrong. I am easily able to produce blank windows in Cinnamon if i play with the maximizing animations (i can produce black windows during transitions, but once the animation finishes - you do end up seeing the window contents - unlike compiz).

While it is true this is a regression in compiz and that 0.8 doesn't suffer from this problem - that doesn't by necessity mean that the bug purely compiz. it could just be that the old codebase hid the issue, or some other (similar) scenario. I do think this is at least in part a bug within the nvidia driver, that the OSS drivers do not have.

anyway, I''ve decided to drop compiz (after many years of usage). Cinnamon is getting to a place where it is a suitable replacement, replicates enough of compiz' plugins / features and seems less buggy (in the few days that i have been using it steadily, built from git).

cheerz

[Alistair Buxton (a-j-buxton)]

@triplesqaurednine

If that is the case then the black window bug (which I cannot reproduce) is different to the white window bug, as suggested by others.

[triplesqaurednine (triplesquarednine)]

@Alistair. Fine....

it is a different bug (that i can reproduce EVERY single time, following the EXACT same instructions in this bug report - and the bug appears to be the exact same, with the exception of the blank windows appearing black - although they used to appear white (for the longest time, like a year - and if they had continued to be white - you wouldn't be claiming it's a different bug at all... but oh no, Alistair can't reproduce it - so that is the end of story :\ ).

but i understand now, since you can't produce it - it is impossible for it to be the same bug in your mind...There couldn't be some other culprit making this slight difference, like different nvidia settings or a difference in hardware, etc...

anyway, it doesn't matter anymore.... i am unsubscribing since in my mind, Compiz is dead (or close to being dead) and has become more and more unstable, less feature rich and bugs don't get fixed unless they affect OSS drivers or Unity (neither of which i use).

plus, compiz can't even handle moving windows when using XBMC, nor (after all these years) can it draw windows in scale/expo without having badly aliased edges. it kills performance in some applications and isn't improving at the same rate as other compositingWMs, either. ...and like i said, I've switched to Cinnamon, now ~ which instantly fixed a myriad of problems that had been ongoing when using compiz.

[Alistair Buxton (a-j-buxton)]

Did I mention that the steps to reproduce and workaround in #87 never worked for me on any version? In fact there was never any consistent way to reproduce and never any workaround found for the bug I was experiencing, which has now been fixed. So we have different steps to reproduce, different workaround, different symptoms, and a different set of affected software. Yes, I'd say it's pretty clear cut that that's a different bug.

[Matthias Niess (mniess)]

@Alistair Buxton: I'm really confused reading your last comments. What exact version of compiz are you using and which versions of the nvidia binary drivers?

I am able to reproduce this with four different nvidia graphic adapters (two mobile and two desktops) on 12.04 AND 12.10. I didn't test *all* driver combinations. All computers use nvidia-current except for my main desktop where I use nvidia-experimental-310 (and where I have used all other combinations of drivers and OS).

I can reproduce the bug on every Ubuntu-machine (with nvidia graphics) since 12.04 using the steps mentioned above resulting in white and black windows respectively.

So for users encountering this, Ubuntu seems to be broken. Nvidia is one of the most popular graphic chipsets. This bug should be the one most worked on, I believe. I can't find a launchpad branch linked to this bug, though. So is anyone working on this? Do you (whoever you are) need help working on this bug? What needs to be done?

[Teo (teo1978)]

@mniess

> So for users encountering this, Ubuntu seems to be broken.
> Nvidia is one of the most popular graphic chipsets.
> This bug should be the one most worked on, I believe.

Agree, but the fourth most worked on, at least. There are at least three worst issues with NVidia which make Ubuntu totally broken:
- x.org crashes
- shifted/inverted colors (blue skin) in all hardware-decoded video playback
- can't see virtual terminals with ctrl+alt+F1,F2, etc

(unless some of these is the same issue)

[Alistair Buxton (a-j-buxton)]

@matthias it's simple:

in 11.04, 11.10, and 12.04, using release compiz versions and stable nvidia driver, i see white windows after some time. the steps listed on this bug DO NOT reproduce it for me. it happens at random after several days of uptime.

in 12.04 using compiz 0.8.8 and stable nvidia i do not see white windows.

in 12.04 and metacity based compositing i do not see white windows.

in 12.10 using the stable compiz release and the stable nvidia driver or the 310 experimental drivers i do not see white windows.

[Matthias Niess (mniess)]

It's not simple. 12.04 comes with compiz 0.9.7.6. So it is no wonder you can't reproduce the bug there. This bugreport is about the compiz versions that ship with Ubuntu and not stuff you compiled yourself. You should report those bugs in the launchpad for Compiz and not the launchpad for Ubuntu.

For 12.10: what do you mean with stable compiz release? I get a feeling you're (again) not talking about the compiz that comes with Ubuntu.

[Matthias Niess (mniess)]

@Alistair: Could you test a vanilla installation of Ubuntu with the nvidia binary drivers. Open two windows. Minimize one window. Press Super+w. Then click on the launcher-icon of the minimized window.

[Alistair Buxton (a-j-buxton)]

@matthias try reading what i actually wrote:

in 11.04, 11.10, and 12.04, using release compiz versions and stable nvidia driver, i see white windows after some time. the steps listed on this bug DO NOT reproduce it for me. it happens at random after several days of uptime.

[Alistair Buxton (a-j-buxton)]

I will try to make this as absolutely brain dead simple as I can. I have tested every version of Ubuntu from 11.04 until 12.10 with every version of Compiz from 0.8.8 up to and including the last version of Compiz released on each version and the results are as follows:

compiz 0.8.8, any nvidia driver, any ubuntu version: no bug

compiz 0.9.8.4, any nvidia driver, ubuntu 12.10: no bug

*any other possible combination*: white windows after two days uptime.

[Matthias Niess (mniess)]

@Alistair: I read all your comments. No reason to be impolite here. If what you wrote was clear enough, people wouldn't ask. You obviously use compiz versions that don't ship with the respective Ubuntu versions, so excuse me and the other commenters for asking details. I'm still not sure if you use the stock compiz on 12.10 (i.e. the one shipped with Ubuntu) or the current stable one from the compiz devs (with the same version) that might not have patches that the Ubuntu-version of Compiz has.

In any case: Either report a seperate bug or wait for this one to be fixed to see if yours is fixed, too. You might want to report it here: https://launchpad.net/compiz.

[triplesqaurednine (triplesquarednine)]

@Alistair

You are experiencing a different bug than the one in this report -> if you are not able to reliably reproduce the bug using the same steps that everyone else has ( including myself! and i can reproduce it every time! ).

 You should be opening a bug report of your own, since clearly all you are doing is making noise and causing a bit of confusion on this bug report ~ a bug which by your own admission you are unable to reproduce... You might want to list in your own report the distinction between yours and this report (that being that they both are causing blank windows, but you cannot actually reproduce *this bug* - as opposed to coming here and telling people who CAN produce it ~ they are experiencing a different bug).

it's pretty obvious now, by your last few posts that your comments don't belong here, since you can't actually reproduce this bug reliably.

anyway, thanks for posting as i forgot to unsubscribe from lp:compiz and all of my bug reports (yesterday).

good luck to all of you in Ubuntuland, using compiz/unity,,,

[Alistair Buxton (a-j-buxton)]

@matthias one last time then:

I have tested every version of compiz released in Ubuntu in the past 18 months.

I have tested packages released in -main, -updates, -proposed, preview PPAs, and source builds. I have spent well over 1000 hours testing different compiz packages. I have been testing for this bug since I noticed it two days after installing 11.04.

I can reproduce this bug in 11.04. I can reproduce it in 11.10 and 12.04. I cannot reproduce it in 12.10.

In my tests the nvidia driver version was irrelevent to the outcome.

Now a few things:

 - This bug is marked as affecting both Compiz and Compiz (Ubuntu). So the source version *and* the packaged version.
 - People post steps to reproduce all the time on the dupes and they are never the same twice.
 - I'm not the only one who can't reproduce on 12.10 and can't get the steps to reproduce to work.
 - It would be silly for me to open a new bug report now, when this bug has finally been fixed for me (and in the exact update when a developer said it should be, and asked for people to test, see #88)
 - Even if I did it would just get marked as a duplicate of this one.

[Rainer Rohde (rainer-rohde)]

I just stepped up from 12.10 to 13.04 in its current iteration -- and rest assured, the bug is still there. :) Black screen, of course.

At least they keep the most annoying bugs for years and years on a consistent basis. Bravo everyone involved.

[stagelll (gedefr)]

Just a quick remark about the Nvidia/non Nvidia bug issue. Smspillaz, before leaving the compiz project, has written a long post about dealing with proprietary graphic drivers (meaning NVIDIA).

He mentionned this bug in it. Here is what he wrote : " In addition to that, we’re fighting lots of strange quirks where texture binding is randomly failing."

http://smspillaz.wordpress.com/2012/06/08/on-the-future-of-graphics-drivers/

So the compiz guys are aware of the bug. And they consider it Nvidia related. But the main point of his post was to say he didn't like to write hack to solve that kind of problem.

Anyway, either they don't work hard enough on it, or it's just not solvable, they haven't found that hack. And one of the basic functionnalities of unity is not working properly on lots of computer, as Nvidia drivers are pervasive.

[Bruce Chadwick (dsp-2)]

Re: Comment #123

Matthias:

Forgive my ignorance. I have been installing Compiz using the Ubuntu Software Center link on the launch bar. Is that the version you mention as being the stock version that ships with Ubuntu? The reason I ask is that in 12.04 I have the cube but 3-D windows, Cube Deformation and Wallpaper are missing completely in Compiz. This has been the case for me on an older ASUS and a newer Dell. I tried 12.10 on the older ASUS and the cube was also missing in Compiz. For the heck of it I tried Ultimate Edition 3.4 and everything was there in the preinstalled Compiz. But I would like to stick with regular Ubuntu, either 12.04 or 12.10.

Thanks,
Bruce

[Matthias Niess (mniess)]

@Bruce: Please don't write anything here that is not related to the bug in question.

[Bruce Chadwick (dsp-2)]

Understood. My apologies.

Cheers

[Nice Testhouse (testhouse)]

Week 50 - Same issue observed on Ubuntu 12.04 Precise Nvidia machine with ppa:unity-team/sru. Minimized window restores blank.

After step 4, the focussed window (recently minimized) was blank just showing the top title bar.

Please note that any action like a click anywhere on the desktop will bring the window back to normal looking displaying its content.

Test Case ID Can-55 :: Version : 1 UNITY_ Nvidia white windows in spread

Test Steps:
 #. Ensure unity is running on a machine with a nvidia GPU using the nvidia driver
#. Open two windows of the same app
#. Minimize one
#. Click the launcher icon to activate the spread
#. Deactivate the spread, now close the active visible window
#. Click the launcher icon to view the minimized window --> Observe

[Rainer Rohde (rainer-rohde)]

This issue still persists (black screen) on Ubuntu 13.04, with NVIDIA driver 313.09.

[triplesqaurednine (triplesquarednine)]

I've actually stopped using compiz (because of this bug and othera), but after reading Sam's blog about the very recent improvements (like fixing window moving, performance improvements) i decided to try the latest code (rev3530 lp:compiz). this bug still persists and through a conversation in the phoronix forum, i made a quick screencast (youtube) to post;

http://www.youtube.com/watch?v=0FNMTbFlTj4

obviously, it has been pointed out that at least some users see this bug is 'black' not white (in recent times). Anyway, the bug is 100% predictable (since i repeat exposing it a few times, easily), but since it ruins my workflow (ie: an app sometimes may be minimized) and since i use the scale plugin with my stylus (wacom), compiz becomes unusable, unless/without disabling minimize/unminimize animations, with the exception of 'fade' - i think(?)...

@ alister : "I have tested packages released in -main, -updates, -proposed, preview PPAs, and source builds. I have spent well over 1000 hours testing different compiz packages. I have been testing for this bug since I noticed it two days after installing 11.04."

None of that matters (and sort of seems like a waste of time, imo), since the bug is in lp:compiz (and 0.9.7 branch before that, etc) which means it will be in ALL of those repos/packages... Maybe the fixes from comment #88 did help you, but THIS bug is still open aka: not fixed.

anyway, apparently bzr does do bisecting, so if one was willing to put a boat load of effort in, you _might_ be able to find the regression. I may look at it over the holidays, we will see but i have a feeling it would be hard to find, as compiz seems to have been a bit of a rocky road in it's development. (i have a feeling git bisect is a better tool, as well, over bzr's bisect)

[Esokrates (esokrarkose)]

To make the bug easier to see and understand, make the animation slower:
"dconf write /com/canonical/unity/minimize-slow-duration 3000"
(You can undo this easily with "dconf reset /com/canonical/unity/minimize-slow-duration")
Now the animation should be slow enough to be able to interrupt it (meaning you are able to press the minimize button, and can move the mouse pointer faster to the launcher symbol and press it than the animated window is going there).
You can alternatively reproduce the effects shown in the linked video by moving the mouse pointer to the launcher and try to click the application instantly after the animation was initiated by pressing Strg + Alt + KP0 (numpad 0 key). The main point is, the bug seems to be quite randomly with default settings (most of the time it does not work, however there are situations when it works).
I found out, that you can reproduce the bug for sure if you apply the dconf setting mentioned above (you could also apply higher values). The slower the animation is, the more likely it is, that the bug happens.
The behaviour is shown in the following video:
http://ubuntuone.com/5xMF480diMFbN5np9rERcP

Now the very important part:

You can see, that the minimize animation ALWAYS works, when it was interrupted before (and the window is black, or without any content). But you have to consider, you are not allowed to shade/unshade, resize or click away from the window! This means doing only minimizing and unminimizing behind one another of the same window (without doing anything that makes the missing window content disappear), it works every second time.
If an window is opened, there is no way, that the animation works the first time minimizing, except you maximize it! This means you can always get the animation working if you maximize it before you press the minimize button (you have to maximize again even if the application is already maximized).
So to conclude there are two ways of always getting the animation work.

I have found an equivalent way to reproducing the bug (which could be relevant):
http://ubuntuone.com/16WmSevvitMlG8XfkfYzfE

(Note: For single windows in the video the ESC button was used to leave the spread without selecting the window. )
If you minimize a non fullscreen window (after you have opened it), click the spread view, leave it without selecting the minimized window and unminimize it, it gets the same condition as interrupting a window minimize.
This behaviour is not true for windows, that minimized correctly before, so the bug does not work for windows maximized an then minimised (last example in the video).
The behaviour shown in the second video is a consequence of the bug shown in the first video, so if you can reproduce the second bug this is also a proof for having the first bug.

The window content is missing when this bug appears, but if the window content is black or completely missing, depends if the window is transparent, or not.

[Matthias Niess (mniess)]

I think it is safe to assume that the person this bug is assigned to won't fix it as he doesn't work on compiz any more. Compiz itself is a dead project. The only work on it are hacks to bend it to the will of Unity. What I'm saying: any non-developer investigating this bug is most probably wasting their time. As sad as it is.

[Sam Spilsbury (smspillaz)]

I still help maintain compiz. And there are plenty of others that do as well. It is not a "dead project".

Some bugs are just trickier than others. I've spent weeks at a time looking into this problem - it is not simple and I don't know the root cause.

[Sam Spilsbury (smspillaz)]

@Esokrates

I think the problem with windows appearing white is different than what you just described. The problem you've identified is definitely worth looking into though. I think its because unity clears the bounding shape of windows when they are minimized.

I've got some code somewhere to make it not do that, now that the relevant bug in compiz that made us to do that is no longer a problem.

Would you be willing to compile and install a custom branch of unity to test?

[Esokrates (esokrarkose)]

@Sam

I put the description here because of https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/995659/comments/2
Maybe what I have described is really another bug, because the description of Bug #729979 does not say anything to me, meaning I was never able to reproduce that bug by clicking on the titlebars of two (or more) windows alternately.
You said you could not reproduce it, so do I (at least until now). But my way to reproduce the blank windows mentioned in comment #135 does always works. Does it work on you setup too?
I just noticed that in comment #132 and #134 part of my problem was already mentioned and therefore confirmed.

Yes if you have the code, I am willing to test it out.

[Sam Spilsbury (smspillaz)]

To be honest, I think the original problem that bug 729979 presented would have been fixed at revision 3220 in lp:compiz , since I know the code that generates mipmaps during animations was fixed for NVIDIA drivers. The focus animations use mipmaps, and incorrect usage of mipmaps generally leads to white textures.

Invisible windows are something else. Which I'm looking into now.

[Sam Spilsbury (smspillaz)]

@Eskorates:

Could you test the following two branches (running at the same time):

lp:~compiz-team/compiz/compiz.fix_729979.1
lp:~smspillaz/unity/unity.fix_1091600

[nuttzo33 (slucas1979)]

I am using ringtail kernel 3.8 4rc 3 and i can't reproduce also with 310.14 nvidia proprietary driver

[Esokrates (esokrarkose)]

@Sam:

I tried to build both, but I could not compile unity : Cmake has a problem with zeitgeist. Is the version I have installed too new?
Output is attached below. I was trying to build it on Raring latest updates. Compiz was built sucessfully, but I cannot test it without building unity (as compiz is incompatible with the installed unity, I suppose this is meant to be so, if not please mention in a response.)

[Esokrates (esokrarkose)]

Excuse me, I attached the file in a wrong way. You can find it here:
http://ubuntuone.com/6hsVC0HWDdWT2ky9Sux0vE

[Esokrates (esokrarkose)]

Okay I compiled both, but I cannot load unityshell plugin: it reports me an segmentation fault and aborts. Both unity and compiz compiled successfully. I installed them both in my home directory and started compiz with

env DISPLAY=:0 LD_LIBRARY_PATH=./lib ./bin/compiz --replace core ccp composi te opengl decor snap imgpng compiztoolbox mousepoll move regex vpswitch anim ation resize grid wall expo place workarounds session fade ezoom scale unityshell

Unity was installed the following way:

http://askubuntu.com/questions/28470/how-do-i-build-unity-from-source/28472#28472

so I suppose it is working all the time with the installed compiz version, but not with my compiled compiz version. Even using old unity compiz fails to load unity (but wihtout a segmentation error).

[Matthias Niess (mniess)]

@Esokrates: check out the documentation on building packages. Using pbuilder should make this quite easy.

[Sam Spilsbury (smspillaz)]

@Esokrates:

Can you post the valgrind trace when it crashes?

sudo apt-get install valgrind

DISPLAY=:0 LD_LIBRARY_PATH=./lib .valgrind /bin/compiz --replace ccp

[Teo (teo1978)]

After upgrading tu Ubuntu 12.10 I don't observe blank white windows any more. Now they are black.
Not kidding.

[Esokrates (esokrarkose)]

@Sam, you can see the output of DISPLAY=:0 LD_LIBRARY_PATH=./lib valgrind ./bin/compiz --replace unityshell here:
http://ubuntuone.com/00Wd4umgSCxKuxswRIAEkN
(--replace ccp works, i only get the crash if i attempt to start unityshell).
I noticed that the minimize problem disappears when I disable unity plugin in compiz, so your approach might be right.
Sam, how would you build compiz and unity?
I compiled unity first using this instruction: http://askubuntu.com/questions/28470/how-do-i-build-unity-from-source/28472#28472
After that I compiled compiz using this instruction: https://answers.launchpad.net/compiz/+question/203490 (comment #1)
and started compiz.
I will try the pbuilder approach too when I have time.

[joncamfield (jon-camfield)]

So, this bug has been driving me absolutely nuts. For me, alt-tabbing (using the dodge animation) caused the blanked screens (only in nautilus, oddly enough). Disabling the animation plugin has, so far, "solved" the problem. Sad to lose a bit of eye candy, but the cost was absolutely worth it.

[Andi Hafner (a-hafner)]

Hi everyone.

Just another report of which configurations are working and which don't. But with these results, it seems for me to be an nvidia-driver issue, as the last two setups mainly differ in the OpenGL-driver (except in the cpu-architecture).

---------------------------------------------------------------------------------------------

Configuration #1:

Focus-Animation-Effect "Dodge" IS WORKING GREAT for me with the following setup:

OS-Version: Ubuntu 12.10
Kernel-Version: Linux 3.5.0-22-generic (i686)
(Virtual)Machine: VirtualBox 4.2.6 r82870
Desktop-Environment: Mate 1.4.2
Display-Server: X.Org Version 1.13.0
OpenGL-Driver: VMware Inc. Gallium 0.4 on llvmpipe 2.1 Mesa 9.0 with direct rendering
Compiz-Version: 0.9.8.6

---------------------------------------------------------------------------------------------

Configuration #2:

Focus-Animation-Effect "Dodge" IS ALSO WORKING GREAT for me with the following setup:

OS-Version: Ubuntu 12.04.1 LTS
Kernel-Version: 3.2.0-36-generic (i686)
(Virtual)Machine: VirtualBox 4.2.6 r82870
Desktop-Environment: Mate 1.4.2
Display-Server: X.Org Version 1.11.3
OpenGL-Driver: Humper 2.1 Chromium 1.9 with direct rendering
Compiz-Version: 0.9.7.12

---------------------------------------------------------------------------------------------

Configuration #3:

Focus-Animation-Effect "Dodge" DOESN'T WORK for me (producing white windows) with the following setup:

OS-Version: Ubuntu 12.04.1 LTS
Kernel-Version: 3.2.0-36-generic (x86_64)
Machine: ASUS-Rampage III with Intel Core i7-930 with NVIDIA GeForce GTX 260
Desktop-Environment: Mate 1.4.2
Display-Server: X.Org Version 1.11.3
OpenGL-Driver: NVIDIA 304.64 with direct rendering
Compiz-Version: 0.9.7.12

All other Compositing-Effects I've activated, and there are a lot of them ;-), are working great with both configurations, except the "Focus Animations".

---------------------------------------------------------------------------------------------

I've noticed, that the OpenGL-Driver in configuration #2 is running much fluently than that one of configuration #1 but both are working at least, in opposite of the nvidia-driver in configuration #3.

I wasn't looking for further, but are there any recent setups with the nvidia-driver which are working with the focus-animation-effects out there?

Any further ideas? This bug is really nagging me, although dodging windows are a gadget, but it's a nice one ;-)

[Andi Hafner (a-hafner)]

Hi there...

Finally I got a solution: I installed emerald-0.9.5 from source this morning and the blank white windows are gone, focus-animation "dodge" is working fine, awesome!

The further hard- & software-configuration is like described in my post #152 as "Configuration #3".

To compile emerald-0.9.5 for ubuntu 12.04.1 I followed the description at "http://handytutorial.com/install-emerald-in-ubuntu-12-04-12-10/".

The first attempt failed with make complaining missing dependencies. I found the fix at "https://bugs.launchpad.net/ubuntu/+source/emerald/+bug/968112" in post #7, there is a further environment-variable to set before: 'export "LIBS=-ldl -lm"'. Great thanks to user "MC Return"!

After that, the package built successfully (I used "checkinstall" instead of "make install" to get a installable package).

I'm very happy to have emerald back in 12.04 and that the blank white windows are gone ;-) Thank you all out there for your great work and wish you a nice weekend...

[Sam Spilsbury (smspillaz)]

@Escorates

Did you actually install compiz after building it? Did you also build nux/bamf etc? Tried using unity-jhbuild?

Generally a crash in the vtable func means an abi mismatch somewhere. Try running with --debug in order to see what symbols you are missing.

Apologies for the late response, I'm currently on holiday.

[Sam Spilsbury (smspillaz)]

@Esokrates

Can you run with --debug? Try also compiling and installing the latest
nux/bamf from source - crashes in the vtable funcs usually indicate an abi
mismatch.

[MC Return (mc-return)]

@a-hafner: Andi, I am happy that the instructions for installing Emerald worked for you as well, and I am happy to hear that your white windows are gone and that the dodge focus animation is working also 4 you... :)

I am trying to convince the Ubuntu packaging/motu guys to continue packaging Emerald for modern Ubuntu (12.04, 12.10, 13.04), unfortunately I did not succeed with this task yet... :(

So every user who wants Emerald to continue to live on their modern Ubuntu system currently has to do some unnecessary complicated actions to make that happen:
For those interested in trying Emerald without having to compile from source, LP-user brainpower also maintains a PPA with .deb packages of Emerald for Precise and Quantal:

https://launchpad.net/~brainpower/+archive/testing

Both versions work on Raring as well, so if you are on raring simply download the .deb files, here for example the AMD64 builds for Quantal (also working on Raring):

https://launchpad.net/~brainpower/+archive/testing/+build/3916940

P.S.: Credits for making Emerald compile again on 12.04+ go to brainpower as well, as he was the first to come up with a solution for fixing the compilation...

[Esokrates (esokrarkose)]

Sam, I am afraid I cannot build your unity branch anymore (on a fresh install of today's daily build) ... I do not know what is causing this error (I have tried everything: compiling and installing bamf and nux first etc.).
All build dependencies were fullfilled.
I suppose it is not necessary anymore to compile your compiz branch as it has already merged, am I right? (https://bugs.launchpad.net/compiz/+bug/1089811)

If I compile unity I get the following error:

[ 16%] Building CXX object unity-shared/CMakeFiles/unity-shared.dir/IconLoader.cpp.o
/home/user/unity.fix_1091600/unity-shared/IconLoader.cpp: In member function ‘void unity::IconLoader::Impl::IconLoaderTask::PushSchedulerJob()’:
/home/user/unity.fix_1091600/unity-shared/IconLoader.cpp:637:9: error: ‘void g_io_scheduler_push_job(GIOSchedulerJobFunc, gpointer, GDestroyNotify, gint, GCancellable*)’ is deprecated (declared at /usr/include/glib-2.0/gio/gioscheduler.h:36): Use '"GThreadPool or g_task_run_in_thread"' instead [-Werror=deprecated-declarations]
/home/user/unity.fix_1091600/unity-shared/IconLoader.cpp:637:93: error: ‘void g_io_scheduler_push_job(GIOSchedulerJobFunc, gpointer, GDestroyNotify, gint, GCancellable*)’ is deprecated (declared at /usr/include/glib-2.0/gio/gioscheduler.h:36): Use '"GThreadPool or g_task_run_in_thread"' instead [-Werror=deprecated-declarations]
/home/user/unity.fix_1091600/unity-shared/IconLoader.cpp: In static member function ‘static gboolean unity::IconLoader::Impl::IconLoaderTask::LoaderJobFunc(GIOSchedulerJob*, GCancellable*, gpointer)’:
/home/user/unity.fix_1091600/unity-shared/IconLoader.cpp:672:7: error: ‘void g_io_scheduler_job_send_to_mainloop_async(GIOSchedulerJob*, GSourceFunc, gpointer, GDestroyNotify)’ is deprecated (declared at /usr/include/glib-2.0/gio/gioscheduler.h:49): Use 'g_main_context_invoke' instead [-Werror=deprecated-declarations]
/home/user/unity.fix_1091600/unity-shared/IconLoader.cpp:672:86: error: ‘void g_io_scheduler_job_send_to_mainloop_async(GIOSchedulerJob*, GSourceFunc, gpointer, GDestroyNotify)’ is deprecated (declared at /usr/include/glib-2.0/gio/gioscheduler.h:49): Use 'g_main_context_invoke' instead [-Werror=deprecated-declarations]
cc1plus: all warnings being treated as errors
make[2]: *** [unity-shared/CMakeFiles/unity-shared.dir/IconLoader.cpp.o] Error 1
make[1]: *** [unity-shared/CMakeFiles/unity-shared.dir/all] Error 2
make: *** [all] Error 2

[Sam Spilsbury (smspillaz)]

Trunk probably only builds on raring these days. sorry.
On 04/02/2013 2:26 AM, "Esokrates" <email address hidden> wrote:

> Sam, I am afraid I cannot build your unity branch anymore (on a fresh
> install of today's daily build) ... I do not know what is causing this
> error (I have tried everything: compiling and installing bamf and nux first
> etc.).
> All build dependencies were fullfilled.
> I suppose it is not necessary anymore to compile your compiz branch as it
> has already merged, am I right? (
> https://bugs.launchpad.net/compiz/+bug/1089811)
>
>
> If I compile unity I get the following error:
>
> [ 16%] Building CXX object
> unity-shared/CMakeFiles/unity-shared.dir/IconLoader.cpp.o
> /home/user/unity.fix_1091600/unity-shared/IconLoader.cpp: In member
> function ‘void unity::IconLoader::Impl::IconLoaderTask::PushSchedulerJob()’:
> /home/user/unity.fix_1091600/unity-shared/IconLoader.cpp:637:9: error:
> ‘void g_io_scheduler_push_job(GIOSchedulerJobFunc, gpointer,
> GDestroyNotify, gint, GCancellable*)’ is deprecated (declared at
> /usr/include/glib-2.0/gio/gioscheduler.h:36): Use '"GThreadPool or
> g_task_run_in_thread"' instead [-Werror=deprecated-declarations]
> /home/user/unity.fix_1091600/unity-shared/IconLoader.cpp:637:93: error:
> ‘void g_io_scheduler_push_job(GIOSchedulerJobFunc, gpointer,
> GDestroyNotify, gint, GCancellable*)’ is deprecated (declared at
> /usr/include/glib-2.0/gio/gioscheduler.h:36): Use '"GThreadPool or
> g_task_run_in_thread"' instead [-Werror=deprecated-declarations]
> /home/user/unity.fix_1091600/unity-shared/IconLoader.cpp: In static member
> function ‘static gboolean
> unity::IconLoader::Impl::IconLoaderTask::LoaderJobFunc(GIOSchedulerJob*,
> GCancellable*, gpointer)’:
> /home/user/unity.fix_1091600/unity-shared/IconLoader.cpp:672:7: error:
> ‘void g_io_scheduler_job_send_to_mainloop_async(GIOSchedulerJob*,
> GSourceFunc, gpointer, GDestroyNotify)’ is deprecated (declared at
> /usr/include/glib-2.0/gio/gioscheduler.h:49): Use 'g_main_context_invoke'
> instead [-Werror=deprecated-declarations]
> /home/user/unity.fix_1091600/unity-shared/IconLoader.cpp:672:86: error:
> ‘void g_io_scheduler_job_send_to_mainloop_async(GIOSchedulerJob*,
> GSourceFunc, gpointer, GDestroyNotify)’ is deprecated (declared at
> /usr/include/glib-2.0/gio/gioscheduler.h:49): Use 'g_main_context_invoke'
> instead [-Werror=deprecated-declarations]
> cc1plus: all warnings being treated as errors
> make[2]: *** [unity-shared/CMakeFiles/unity-shared.dir/IconLoader.cpp.o]
> Error 1
> make[1]: *** [unity-shared/CMakeFiles/unity-shared.dir/all] Error 2
> make: *** [all] Error 2
>
> --
> You received this bug notification because you are a member of Compiz
> Maintainers, which is subscribed to Compiz.
> Matching subscriptions: Compiz Maintainers ubuntu compiz
> https://bugs.launchpad.net/bugs/729979
>
> Title:
> [nvidia] Windows appear blank white
>
> Status in Compiz:
> Triaged
> Status in Compiz Core:
> Triaged
> Status in “compiz” package in Ubuntu:
> Triaged
>
> Bug description:
> Binary package hint: compiz
>
> When switching focus from one window to another, the target window may
> become blank. See the attached screen...

[Esokrates (esokrarkose)]

I tried to build it on raring (as I said latest daily build, installed only for compiling this branch), but make gives me the mentioned error. I would really like to test this branch to finally test if this bug is gone, because now I have one week time to test.

[Sam Spilsbury (smspillaz)]

On Mon, Feb 4, 2013 at 4:44 PM, Esokrates <email address hidden> wrote:
> I tried to build it on raring (as I said latest daily build, installed
> only for compiling this branch), but make gives me the mentioned error.
> I would really like to test this branch to finally test if this bug is
> gone, because now I have one week time to test.

Ah, hmm, I'll try re-syncing with trunk, maybe those functions were
marked deprecated recently.

The compiz branch is definitely necessary, as the previous branch
merged in was a workaround for problems in unity that weren't there in
my branch of unity anymore.

Try it now.

It might be better to ping me on IRC if you're having trouble building
it, the high-latency of bug reports means I'm not able to deal with it
quickly. I'm 'smspillaz' on freenode.

>
> --
> You received this bug notification because you are a member of Compiz
> Maintainers, which is subscribed to Compiz.
> Matching subscriptions: Compiz Maintainers ubuntu compiz
> https://bugs.launchpad.net/bugs/729979
>
> Title:
> [nvidia] Windows appear blank white
>
> Status in Compiz:
> Triaged
> Status in Compiz Core:
> Triaged
> Status in “compiz” package in Ubuntu:
> Triaged
>
> Bug description:
> Binary package hint: compiz
>
> When switching focus from one window to another, the target window may
> become blank. See the attached screenshot, where I opened two gnome-
> terminals and clicked on their titlebars alternately - the issue was
> triggered after about 5-10 clicks. I've had this happen on other
> appications too, e.g. software-centre, empathy, etc.
>
> Doing shade+unshade, maximizing or clicking away from the problematic
> window usually makes the window contents come back. The window remains
> responsive to both keyboard and mouse (by the way, in the screenshot
> the mouse cursor was an I-beam before I pressed PrtScr).
>
> This is on up-to-date natty, installed from scratch using the daily
> image from the 1st of March.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 11.04
> Package: compiz 1:0.9.4-0ubuntu3
> ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
> Uname: Linux 2.6.38-5-generic x86_64
> NonfreeKernelModules: nvidia
> .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0'
> .proc.driver.nvidia.registry: Binary: ""
> .proc.driver.nvidia.version:
> NVRM version: NVIDIA UNIX x86_64 Kernel Module 270.29 Wed Feb 23 16:18:35 PST 2011
> GCC version: gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-3ubuntu3)
> Architecture: amd64
> CompizPlugins: [core,bailer,detection,composite,opengl,decor,imgsvg,resize,resizeinfo,mousepoll,wall,regex,animation,place,blur,compiztoolbox,text,session,grid,put,imgpng,imgjpeg,gnomecompat,commands,copytex,wobbly,annotate,move,vpswitch,workarounds,expo,ezoom,staticswitcher,fade,scale,scaleaddon,unityshell]
> CompositorRunning: compiz
> Date: Sun Mar 6 02:42:49 2011
> DistUpgraded: Log time: 2011-03-03 20:05:16.908415
> DistroCodename: natty
> DistroVariant: ubuntu
> DkmsStatus: nvidia-current, 270.29, 2.6.38-5-generic, x86_64: installed
> GraphicsCard:
> nVidia Corporation ION VGA [GeForce...

[Esokrates (esokrarkose)]

@Sam: As I wrote you per mail, your branches seem to fix the minimize issue.
Have not tested (as I could not) the spread one (see #135) though.

[Launchpad Janitor (janitor)]

This bug was fixed in the package compiz - 1:0.9.9~daily13.02.19-0ubuntu1

---------------
compiz (1:0.9.9~daily13.02.19-0ubuntu1) raring; urgency=low

  [ Sam Spilsbury ]
  * debian/patches/100_workaround_virtualbox_hang.patch
    - VirtualBox uses a shared-memory texture_from_pixmap_implementation
    which is not compatible with our server grab usage, so force
    a different bind method when running with virtualbox and binding
    an externally managed texture

  [ Brandon Schaefer ]
  * Unity rendered behind windows (LP: #906231)

  [ MC Return ]
  * unmaximize_window_key instead of unmaximize_or_minimize_window_key
    exposed in g-c-c (LP: #1115128)

  [ Sam Spilsbury ]
  * [needs-packaging] Please upload: esvn merged (LP: #112433)
  * [nvidia] Windows appear blank white (LP: #729979)
  * Threads not found on CI (LP: #1124133)
  * Unity rendered behind windows (LP: #906231)
  * Compiz hangs in glXBindTexImageEXT in VirtualBox (LP: #1127866)
  * 1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to
    wrong values (LP: #1063617)
  * Creating windows above just-destroyed windows causes newly created
    windows to receive invalid stack positions (LP: #1088399)

  [ Marco Trevisan (Treviño) ]
  * Calling setOptionForPlugin does not work for core options (LP:
    #1122228)

  [ Automatic PS uploader ]
  * Automatic snapshot from revision 3611
 -- Automatic PS uploader <email address hidden> Tue, 19 Feb 2013 08:46:08 +0000

[Matthias Niess (mniess)]

Will this be backported to quantal?

[John B. (jbuncher)]

Will this fix be backported to us Precise LTS users?

[fldc (fldc)]

I still have black window issues on raring all the time.

[bowser (bwbernard-wong1)]

Post #162 said "This bug was fixed in the package compiz - 1:0.9.9~daily13.02.19-0ubuntu1". But I am still getting black windows in Raring daily build. Comiz version is compiz - 1:0.9.9~daily13.03.20-0ubuntu1

What happens?

[bowser (bwbernard-wong1)]

Since a fix is supposed to have been released and there has not been activity on this thread for a while (orther than queries about the status of the bug and whether fix will be back ported which went unanswered) I think the bug might have been closed.

But I am still getting blank black windows on raring daily build (compiz 0.99~daily13.03.29 ) and this thread appear to be closed I have created a new bug report https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1162954

[Matthias Niess (mniess)]

I can still reproduce this bug on every version of Ubuntu available to me.

[Felipe Uribe (wfpaisa)]

Hello friends,
I'm not sure but I think the problem is with the metacity window decorator,
eh decorator disabled and minimized windows from keyboard commands and effects work perfectly.
In the following video I demonstrate, test conducted in Ubuntu 12.04, 12.10, 13.04

https://www.youtube.com/watch?v=5lpexQGuuPY

[Matthias Niess (mniess)]

@Felipe: You're doing it wrong. What you're showing in the video is not the way to reproduce the bug. You need to minimize a window, initiate scale and then maximize it again.

[Matthias Niess (mniess)]

I just tried it and it doesn in fact work. With window-decorations off I don't get the black window after restoring it.

[Mikhail M (mmedvede)]

Tried Felipe's workaround as well. Could not reproduce the bug. Compiz version 1:0.9.7.12-0ubun.

[bowser (bwbernard-wong1)]

@Felipe

I watched your video, no sure which DE you are using, but I have never had the black window problem if I use the mouse to choose application from the launcher. The bug is triggered only when I use the alt-tab launcher to choose among applications that are already in use, and with raring it only happens when more than one instances of the same applications are in use. e.g If Firefox (one instance), vlc (one instance) and two instances of evenice (2 pdf documents) are in use and all minimized. Using the alt-tab launcher to choose either Firefox or Vlc doesn't result in black windows, but focusing on either instance of evince will.

I have replaced the default window decorator with emerald but it doesn't make a difference.

The only thing that works for me is to disable "animation" from ccsm, but that result in abrupt motion when opening closing maximizing and minimizing windows.

[André Desgualdo Pereira (desgua)]

Because many people (including myself) still have this bug, at least the "status" of it should be changed to "Confirmed" instead of "Fix Released".

[André Desgualdo Pereira (desgua)]

Also here is a video to illustrate the problem: http://youtu.be/YURpSbEF-Ns [updated video]

[bowser (bwbernard-wong1)]

Hi Andre,

I can't reproduce your problem. Which version of Ubuntu and which DE do you use? In Raring, as I said, the blank windows only appear when trying to use alt-tab or shif switcher to choose an application where more than one instances are already in use (but minimized)

[Matthias Niess (mniess)]

I can reproduce the bug with the current compiz version in raring using a default Ubuntu install with nvidia drivers.

[André Desgualdo Pereira (desgua)]

Like I said in bug #1162954, I am using Ubuntu 12.04 in one laptop and 12.10 in another. Both have this problem. This happens as showed in video and also with Alt-Tab. Both are new installations of Ubuntu with Unity DE and the Nvidia binary (this doen't happens with the nouveau driver).
Best regards.

[bowser (bwbernard-wong1)]

Hmmm..

Just updated compiz and unity with Sam Spilsbury's ppa https://launchpad.net/~smspillaz/+archive/compiz-experimental?field.series_filter=raring

Now the blank black windows don't appear (for applications with multiple instances in use but minimized) with the alt tab switcher provided the applications don't open to full screen. So suppose I have multiple pdf minimized and I try to select one of them with alt-tab, if I focus on an instance which opens to full screen I still see the blank blackscreen. But if I choose an instance which opens to a smaller window then it is normal.

[hansvschoot (hansvschoot)]

I also suffered from this bug, but managed to solve it by manually fixing all the libGL.so symlinks in /usr/lib (and lib32) to point to the libGL.so in the nvidia-current subdirectory.
After this, I re-installed nvidia-current using: sudo apt-get install --reinstall nvidia-current
You can check your own libGL.so symlinks using: ls -l `find /usr | grep libGL.so`

[André Desgualdo Pereira (desgua)]

@hansvschoot This would have been a great idea, unfortunately I didn't
manage to get it to work with nvidia-313-updates.
In my machine the only link that didn't pointed to something in nvidia
diretory was /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 which I linked to
/usr/lib/nvidia-313-updates/libGL.so.1 Then I execute "apt-get install
--reinstall nvidia-313-updates" and reboot.
If you have another suggestion I would be glad to test.
Thank you nevertheless.

[hansvschoot (hansvschoot)]

@André: Sorry to hear it is not working for you. I now believe the origin of the bug was slightly different for my machine, probably because I've also had an AMD gpu in there, running both the AMD and NVIDIA closed drivers side by side (not an advisable setup by the way...).

[André Desgualdo Pereira (desgua)]

@hansvschoot Although it didn't work, I was happy for more than a day,
hopping this old bug could finally be fixed ;-)

[bowser (bwbernard-wong1)]

Use Nvidia 319.23 (xorg-edgers) with the Compiz experimental ppa in 13.04 (though I don't think this ppa is essential and sometimes it does break Unity, so I have stopped updating from it after a while) Here are how things stand on my system

I) If all windows are non minimized, then no black window switching either with alt-tab or the shift switcher.

2) if some windows are minimized but there is only one isntance for such applications (e.g no two instances of evince for two pdf documents), then no black windows switching with alt-tab

3) if the minized windows (may have more than one instances of the same applications) restore to non maximized windows than no black windows using the alt-tab switcher.

4) Always get black windows with shift switcher if some applications are minimized (regardless of how many instances are in use)

5) Get black windows with alt-tab for applications with more than one instances in use and minimized AND only for those instances that restore to maximized windows.

6) One way to avoid ALL black windows would be to enable the scale addon in ccsm and use a hot corner to pick windows (i.e using Unity like Gnome Shell) There is no black window under any scenario.

So, if I am switching Windows with the scale addon (like using gnome-shell) I am able to avoild black windows al together and even if I get a black window say in using alt-tab in scenario 5 moving the cursor to the hot corner to refocus the open black window would make it normal again.

Since it doesn't look like this bug will be fixed this is the best I can do. By using mostly the hot corner I have restored normal work flow pretty much and haven't seen any black window for quite some time.

[Joey Espinosa (therealjoelinux)]

Btw guys, I know the status is "Fix Released," but I've managed to completely "fix" this issue by unchecking CCSM -> Ubuntu Unity Plugin -> Switcher -> Show live previews of windows in the Switcher.

On top of fixing the black window issue I was having (which, in addition to the methods mentioned above, was also easily recreated by minimizing a window and then clicking that window immediately with the mouse to reverse the animation... reproduced 8 out of 10 times), it also fixed the window content going blank upon minimizing.

I saw a few other workarounds with other options, but specifically the "Show live previews of windows in the Switcher" option is what fixed the whole shebang for me.

[Matthias Niess (mniess)]

@Joey: Your workaround is the only thing that works for me. I really don't understand why this hasn't been fixed, yet. ;(

[Matthias Niess (mniess)]

Adding to that: "Show live previews" doesn't actually show live previews anyway.

[Matthias Niess (mniess)]

I updated the description with the workaround instructions on how to reproduce. According to the related branches the apparent fix was merged into Compiz 0.9.8. I have 0.9.9 (raring) and it is not actually fixed. Was the fix removed again from 0.9.8 or is this wrongly marked fix released?

[MC Return (mc-return)]

@mniess:

Could you please try the ppa:smspillaz/compiz-dev-raring to see if it fixes the issue for you ?

[Matthias Niess (mniess)]

That ppa wants to remove unity. Not a good idea, I guess.

The following packages will be REMOVED:
  lightdm-remote-session-uccsconfigure ubuntu-desktop unity
The following packages will be upgraded:
  compiz compiz-core compiz-gnome compiz-plugins-default libcompizconfig0
  libdecoration0 libunity-core-6.0-5 unity-common unity-services

[Matthias Niess (mniess)]

Sorry, some packages were already upgraded. Here's the full list of packages after adding the PPA and running dist-upgrade:

The following packages will be REMOVED:
  lightdm-remote-session-uccsconfigure ubuntu-desktop unity
The following packages will be upgraded:
  compiz compiz-core compiz-gnome compiz-plugins-default
  compizconfig-settings-manager libcompizconfig0 libdecoration0
  libunity-core-6.0-5 python-compizconfig unity-common unity-services
11 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.

[Mateusz Stachowski (stachowski-mateusz)]

The PPA mentioned in comment #190 doesn't try to remove Unity anymore and is functional for Raring. I installed the updated packages from this PPA but unfortunately it didn't reslove the bug.

I've noticed that the blank windows are only a problem for windowed programs. If I minimize maximized program and follow the procedure to reproduce the bug I don't get blank white window. If I do the same for windowed program it results in blank white window.

[Evandro P. Alves (evandro-pa)]

I'm not experiencing this bug on my NVIDIA 8800 GT running 13.04 x86_64 (clean install)

[Vadim Peretokin (vperetokin)]

I'm having this issue on 12.04 LTS using 304.88 drivers. It hasn't always happened until a few weeks ago.

[Felipe Uribe (wfpaisa)]

Hello, the best solution so far has been to match the shade of the windows.
Inactive Active shadow = shadow.

https://dl.dropboxusercontent.com/u/18116331/Selecci%C3%B3n_004.png

no longer turn black when minimizing windows in 98% of cases, being in full screen some windows still looks black to minimize.

tested on nvidia 525M, ubuntu 12.13,
tested on nvidia GeForce 7300, ubuntu 12.13,

[Teo (teo1978)]

Ubuntu 13.04 on a different computer; now I'm using noveau (or whatever it's called what comes by default with Ubuntu) instead of proprietary Nvidia drivers.
Problem still there, but windows are now TRANSPARENT instead of black.

It's not just switching windows, it's WHATEVER RANDOM WINDOW that is opened and given focus, including even popups (e.g. confirmation or error popups) and submenus.

Examples:
- in Gedit you hit Ctrl+H, and the Search and Replace window that pops up, at random times is transparent.
- in Google Chrome you click on the menu button on the top-right corner: the submenu at random times is transparent
- in Nautilus, you right-click on the background of a folder; the context menu is fine but when you choose a submenu item, the submenu comes up transparent (but it works if you know where to click blindly)

All of these happen at random times, but when they start happening with a given application, they will usually keep happening systematically untill you close and relaunch that application.

So how do I get the supposed fix that is supposed to have been released?!?!?!?

[Sam Spilsbury (smspillaz)]

(I am no longer working on compiz, hence the unassign)

[vsespb (vsespb)]

What is the workaround for 12.04 LTS ?

There is no "Show live previews of windows in the Switcher".
and
"Show minimized windows in switcher" does not help.

[Frank Bicknell (fbicknel)]

Is this related?

Steps to reproduce:

0. Alt-F2
1. Run 'unity --replace &'
3. All windows that were previously minimized are now 'empty' when restored.
4. Minimize and restore the window to see the contents again.

Super-W puts on an interesting display (and loses track of minimized windows) after 'unity --replace'. Minimize/restore will bring them back to Super-W, however.

Side note: Need 'unity --replace' often due to confounded compiz sucking down all the system memory sometimes. (I think that's related to xscreensaver, but have yet to prove it definitively.)

[Matthias Niess (mniess)]

Can we please re-open this bug? There is no released fix that ever worked for me. I'm on 14.04 development, fresh install and I still experience this bug following the original steps to reproduce:

- minimize window
- show scale (super+w)
- hide scale (super+w)
- click on window in launcher

-> black empty window.

[Rainer Rohde (rainer-rohde)]

I support the notion of Matthias Niess above. I experience the same, and with the recent 14.04 updates, it happens a lot more often!

[C de-Avillez (hggdh2)]

I cannot see any reason for this bug being set fix released. Reverting to Triaged.

[C de-Avillez (hggdh2)]

sorry, the precise task was set on the wrong bug

[Ryan Tandy (rtandy)]

I've been through and reproduced this bug on every release since Precise, using exactly Matthias' test case from comment #202. All my tests were on 64-bit installs, totally up-to-date, with newly-created home directories.

I have not yet personally seen this happen with nouveau, only the proprietary nvidia driver.

02:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2)

Precise (nvidia-331, lts-saucy stack): restored window is white
Quantal (nvidia-304): restored window is transparent
Raring (nvidia-310): restored window is transparent
Saucy (nvidia-319): restored window is black
Trusty (nvidia-331): restored window is black

[Xavier (xavier.h)]

I'm on 14.04 with Nvidia prime. This bug happen when i swith on nvidia card, and disapear when i swith on the intel graphic card.
I think the bug begin when i installed compiz setting manager.

[Xavier (xavier.h)]

And everything work fine if i disable window minimize animation with unity tweak tool.

[vsespb (vsespb)]

> sorry, the precise task was set on the wrong bug
Why it's invalid for precise?, happening in Precies very often. Very annoying!

[pst007x (turone)]

Ubuntu 13.1064bit & Ubuntu 14.04 64bit disable Animations in CCSM seems to stop this problem..

[Silviu C. (silviucc)]

Still happens in 14.04 beta and the work-a-round is to disable animations in CCSM. It also happens on 12.04, why was it marked as "Invalid"?!

[Silviu C. (silviucc)]

I've changed the status to "Confirmed" for 12.04 as it's still affected by the bug

[Matthias Niess (mniess)]

I don't know how to do it but can someone also retarget this to trusty?

[assassini (assassini)]

This also seems to happen sometimes when waking up from suspend.

[vsespb (vsespb)]

Ubuntu 12.04, Unity 3d, nvidia
Disable "Animations" plugin in CCSM seems is a working workaround.

[misteraph (laporte-raphael)]

Same here. Ubuntu 14.04 64bits, Nvidia 331.38.

Disable plugins did the trick, but I'm waiting for a real fix.

[Christopher Townsend (townsend)]

Hey All,

Looking through some of the bug history, it seems this is specific to Nvidia and the proprietary driver. I'm thinking this is really a duplicate of bug #269904.

In that bug, there is a patch provided by Nvidia that hopefully fixes that issue. At this time, we cannot get that patch into Compiz proper due to some silly licensing issue, but I have made a PPA that has the fix incorporated. This PPA has packages for Precise, Trusty, and Utopic. If anyone would like to test this out and report your results, please add https://launchpad.net/~townsend/+archive/compiz-nvidia-refresh-test and give it a try.

I'm hoping that if we can get enough feedback that say this fixes the issue for many users, we can use that as leverage to get *something* done about getting the patch merged into Compiz.

Thanks!

[vsespb (vsespb)]

There is a comment that problem persists with noveau https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/729979/comments/197

[Ryan Tandy (rtandy)]

Hi Christopher,

I tried your PPA on Precise and Trusty, and this bug (minimize, scale, restore → blank window) still occurs.

As far as bug 269904 I need to touch base with my users who are affected by it... will post an update there when I can.

Thanks for trying to move that forward, greatly appreciated.

[Rainer Rohde (rainer-rohde)]

Yes, this issue still persists, even after using the compiz build from the PPA on 14.04 LTS. See screenshot attached.

[Rainer Rohde (rainer-rohde)]

Not sure where the screeenshot went, but here is it via Dropbox:

https://www.dropbox.com/s/u2pfl9uhrj3suh3/Screenshot%20from%202014-06-05%2011%3A30%3A02.png

[Christopher Townsend (townsend)]

Ok, well, it was worth a try. Thanks for those who tested and provided feedback.

[Alexander (aheihachi)]

Ubuntu 14.04 LTS - GTX 750 Ti, 331.89 drivers - black window when using Super + W and opening minimized window. Is it going to be fixed?

[stagelll (gedefr)]

Same here: Ubuntu 14.04.1 LTS - NVIDIA GeForce GTX 460M, using 331.38 drivers. The only change from 12.04 is that windows are now black -they used to be white.

The very least would be to assign someone to work on this bug. There's no chance that it will be fixed if no one works on it...

[vsespb (vsespb)]

In comment 215 I wrote that there is a workaround (Disable "Animations" ), but no, problem reappear.

[China Rulezzz (chinarulezzz)]

Hi Cris, unfortunately bug still persists (black screen when click minimize/restore on some applications, ccsm as example).

Ubuntu 14.04.1, GeForce GT 610.

driver packages:

nvidia-331-updates 331.38-0ubuntu7.1
nvidia-libopencl1-331-updates 331.38-0ubuntu7.1
nvidia-opencl-icd-331-updates 331.38-0ubuntu7.1
nvidia-prime 0.6.2

[Launchpad Janitor (janitor)]

This bug was fixed in the package compiz - 1:0.9.12.1+15.04.20150303-0ubuntu1

---------------
compiz (1:0.9.12.1+15.04.20150303-0ubuntu1) vivid; urgency=medium

  [ Andrea Azzarone ]
  * Do not cache textures in animation.cpp. (LP: #729979, #1072206)

  [ Martin Wimpress ]
  * tweak MATE profile INI
 -- CI Train Bot <email address hidden> Tue, 03 Mar 2015 18:31:02 +0000

[Adam Conrad (adconrad)]

Hello pablomme, or anyone else affected,

Accepted compiz into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/compiz/1:0.9.11.3+14.04.20150313-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Matthias Niess (mniess)]

@adconrad, is this in utopic-proposed, too? Judging by your link it doesn't look like it. The problem still exists in utopic (without proposed enabled).

[Matthias Niess (mniess)]

@adconrad, sorry for spamming. Just saw this fix is not in utopic-proposed. I've got no trusty on affected machines, sorry.

[Ryan Tandy (rtandy)]

Hi,

On a machine with a GeForce 6150SE iGPU and nvidia-304 304.125-0ubuntu0.0.1, opened a terminal and followed the steps in the test case with it:

1. Minimize a window
2. Initiate Scale and deactivate it again (press Super+W to show all windows and then press it again to go back to normal)
3. Click the window icon on the launcher to maximize it again.
4. The window contents will be white, black, or transparent depending on the Ubuntu version

With compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 (trusty-updates): restored window is transparent.

With compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 (trusty-proposed): restored window is drawn correctly.

Works for me, thanks!

[Matthias Niess (mniess)]

So any chance this fix will also make it into newer versions of Ubuntu?

[Christopher Townsend (townsend)]

This fix is already in Vivid, but not in Utopic.

[Launchpad Janitor (janitor)]

This bug was fixed in the package compiz - 1:0.9.11.3+14.04.20150313-0ubuntu1

---------------
compiz (1:0.9.11.3+14.04.20150313-0ubuntu1) trusty; urgency=medium

  [ Andrea Azzarone ]
  * removed texture caching from animations (LP: #729979, #1072206)

  [ Chris Townsend ]
  * Add a blacklist of Nvidia integrated GPU's affected by the Nvidia
    X11 Sync patch. (LP: #1424013)
 -- CI Train Bot <email address hidden> Fri, 13 Mar 2015 17:25:30 +0000

[Chris J Arges (arges)]

The verification of the Stable Release Update for compiz has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Steve Langasek (vorlon)]

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release