Hello, Just looked at screenshots from #1210077 . They show corruption on screen background and some window content.
The bug I originally experienced shows on-screen corruption of launcher only, as confirmed by original description of this bug : "The unity launcher is reliably corrupted ...". Since symptoms of the two bugs are different, the two bugs may or may not be actually from the same cause. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/915265 Title: [regression] Unity launcher on-screen corruption on resume from suspend with nVidia proprietary driver Status in OEM Priority Project: Fix Released Status in OEM Priority Project oneiric series: Won't Fix Status in OEM Priority Project precise series: Fix Released Status in Unity: Fix Released Status in Unity 6.0 series: Fix Released Status in Unity Distro Priority: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Oneiric: Won't Fix Status in “unity” source package in Precise: Fix Released Bug description: [Impact] This bug basically makes NVidia machines unusable after suspend. This is causing problems for users and OEMs that want to use 11.10 alike. [Development Fix] https://bazaar.launchpad.net/~unity-team/unity/trunk/revision/2205 [Test Case] . To reproduce: 1) Suspend 2) Resume 2a) login, if necessary. Note that the login screen (lightdm) displays properly 3) Notice the corrupted launcher 4) Mouse over the launcher; the launcher redraws and the corruption goes away [Regression Potential] Low. We have tested the fix in the development version that we're planning on releasing in April 26th and have found no problems. With the big diff, the regression potential might be a bit bigger for precise. == Original Report == The unity launcher is reliably corrupted upon resume from suspend with some (all?) NVidia hardware with the proprietary NVidia driver. All other visual elements seem to draw correctly, it's just the unity launcher that has this problem. The launcher looks fine after it redraws (for example, if you mouse over it). The problem is not reproducible on Intel or AMD graphics hardware, and I'm told (by Ted Gould) that it doesn't affect the nouveau driver. I have not tested the nouveau driver myself. This problem been reported several times in the comments of bug 676166, I'm filing this separate bug for clarity since 676166 is overloaded. To reproduce: 1) Suspend 2) Resume 2a) login, if necessary. Note that the login screen (lightdm) displays properly 3) Notice the corrupted launcher 4) Mouse over the launcher; the launcher redraws and the corruption goes away The problem affects 11.10, and is not fixed by upgrading to more recent unity, compiz, or nvidia drivers from oneiric-updates or even the most recent SRU candidates not yet in oneiric-proposed. Currently I have the following installed and the problem still exists: ii nvidia-common 1:0.2.35.1 Find obsolete NVIDIA drivers ii nvidia-current 280.13-0ubuntu6 NVIDIA binary Xorg driver, kernel module and VDPAU library ii nvidia-current-updates 285.05.09-0ubuntu0.1 NVIDIA binary Xorg driver, kernel module and VDPAU library ii nvidia-settings 280.13-0ubuntu2.1 Tool of configuring the NVIDIA graphics driver ii nvidia-settings-updates 285.05.09-0ubuntu0.1 Tool of configuring the NVIDIA graphics driver Unity SRU candidate (not yet in -proposed): ii unity 4.28.0-0ubuntu1~ppa1 Interface designed for efficiency of space and interaction. Compiz SRU candidate (not yet in -proposed): ii compiz 1:0.9.6+bzr20110929-0ubuntu6.1~oneiric1 OpenGL window and compositing manager ii compiz-core 1:0.9.6+bzr20110929-0ubuntu6.1~oneiric1 OpenGL window and compositing manager Hardware is a MacbookPro 3,1 w/ NVidia 8600M GT. I'm using the amd64 build of 11.10. lspci -vvnn output for graphics card: 01:00.0 VGA compatible controller [0300]: nVidia Corporation G84 [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Computer Inc. Device [106b:00a0] Physical Slot: 1 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 16 Region 0: Memory at d2000000 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at c0000000 (64-bit, prefetchable) [size=256M] Region 3: Memory at d0000000 (64-bit, non-prefetchable) [size=32M] Region 5: I/O ports at 5000 [size=128] [virtual] Expansion ROM at d3000000 [disabled] [size=128K] Capabilities: [60] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Capabilities: [78] Express (v1) Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 <4us ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 <512ns, L1 <4us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM L0s L1 Enabled; RCB 128 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb: Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01 Status: NegoPending- InProgress- Capabilities: [128 v1] Power Budgeting <?> Capabilities: [600 v1] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Kernel driver in use: nvidia Kernel modules: nvidia_current, nvidia_current_updates, nouveau, nvidiafb To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/915265/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp