minimizing a maximized window leaves artifacts on the screen.

[Bilal Shahid]

some times when we minimize the window black broad lines appear on the destop,,see the vedio that i have attached.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: unity 4.10.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
Architecture: i386
CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,resize,fade,unitymtgrabhandles,scale,session,unityshell]
Date: Sun Aug 28 16:40:38 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110817)
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: unity
UpgradeStatus: Upgraded to oneiric on 2011-08-26 (1 days ago)

[Omer Akram (om26er)]

these black lines hack been there since Natty but before unity 4.10 release they were just visible till the app fully hides, now they get stuck on the screen. the initial issue was bug 737125

[David Henningsson (diwic)]

For me this only happens with the Nvidia binary driver, not with nouveau.

[bwat47 (bwat47)]

This happens on my machine with intel ironlake graphics. It has happened since natty.

The same issue is present in 11.10 only worse for me, because if I minimized a maximized window like firefox, I not only get those lines but it also renders any windows that were open in the background inaccessible until I close the application that caused the lines.

[Rainer Rohde (rainer-rohde)]

For me this happens since Oneiric. See attached screenshot.

[ignasi (igp-oenus)]

Same here on my Thinkpad z61t with 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)

[Rainer Rohde (rainer-rohde)]

.... and every time it leaves artifacts on the screen, other open windows are unresponsive. I either have to kill the window I just minimize or alt-tab a view times in order to get the window to respond again (that doesn't always work).

[nuttzo33 (slucas1979)]

Surely this is going to be fixed by the release candidate? I have uploaded a video to youtube showing what rainer rohde said about the other windows being unresponsive.
http://www.youtube.com/watch?v=ssYVlg77rHI

[Rainer Rohde (rainer-rohde)]

Excellent video, Shayne! Looks all too familar.

In addition, more recently when killing the window that caused this behavior, the whole desktop refreshes as if compiz had crashed. However, I am not always able to manipulate the window causing this glitch (unable to right-click and select "quit"), and then the only way to get out of this mess is to restart lightdm from the console.

As Shayne has identified, this happens only when minimizing a window from its fully maximized state involving the global menu; if the window is open but not maximized, minimizing it does not have a negative effect.

[bwat47 (bwat47)]

I can confirm Shayne's video is exactly what I see on my machine with intel ironlake graphics. I can get around the unresponsiveness if I kill whatever program I minimized that caused it (usually firefox)

[Olli Kankare (o.k)]

This bug makes unity basically un-usable on a hp elitebook 2530p with intel 9-series integrated graphics (and I presume on almost all other computers with newer intel display-adapters).

Bug-status should be raised to critical.

[Rainer Rohde (rainer-rohde)]

nVidia 9600m GT on my end. And I agree, this should be critical as it affects the usability of the desktop to a great extent... It's frustrating as can be, especially with documents open and data lost when having to restart lightdm in order to get out of a unresponsive session.

[martincasc (martincasco)]

I agree with the problem, also agree that this bug should be critical.

For example, if we have Firefox maximized (full screen) and then we minimize it, we'll see the black lines on the screen, but if we focus on the application that have open in the background, this does not respond, the window does not move, doesn't do anything. The only solution is close the Firefox window (still with the example) or maximize it again, normalize it and then minimize it.

The error only occurs when we minimize a full screen windows.

Have an intel video (Core i3)

[bwat47 (bwat47)]

Agreed. This seems to happen on a variety of hardware (so far on this page we've seen ranging from intel with oss driver to nvidia with proprietary driver.)

This basically makes unity unusable for anyone effected unless you just don't maximized windows. Of course unity's entire design encourages maximizing windows so this is a huge problem. This is the kind of thing that really shouldn't be making it into final release. This has been happening to me since natty.

This is reproducible for me 100% of the time when I minimize a maximized firefox window.

Are there any relevant logs we can attach?

[nuttzo33 (slucas1979)]

I have an asus p8p67 pro board and an nvidia g210 card and i am running 64 bit version of ocelot.There is also another bug that i have found that happens when maximizing firefox from the unity launcher where there is a gap under the title bar and the window is unresponsive until you minimize and maximize again.Does anyone know where this bug is filed?

[nuttzo33 (slucas1979)]

Here is a screenshot of what i was talking about in the last post.See the gap under the titlebar and the maximize and minimize buttons don't highlight when hovering over them.

[nuttzo33 (slucas1979)]

Ok i found a report for this bug here https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/772612
At least there is a fix released for this bug.

[Hernando Torque (htorque)]

Are you still having this issue? On my Arrandale (Intel HD Graphics 2000) this is no longer happening (though I'm using Unity and Nux from trunk).

[David Henningsson (diwic)]

Yeah, seems fixed here too with today's Oneiric, on an NVidia!

[martincasc (martincasco)]

Confirmed under Intel graphic?

[Holger Knust (hknust)]

Confirmed for Intel HD 3000

[Andrea Azzarone (azzar1)]

I can no longer reproduce this bug (intel).

[nuttzo33 (slucas1979)]

I confirm that this bug has been squashed.

[Rainer Rohde (rainer-rohde)]

I can confirm this as well! Good going, guys! And thank you! :)