Titlebar incorrectly drawn with geforce 5/6/7, compiz and human-theme

[Maciej Podkomorzy]

When compiz and human-theme are being used, the titlebar of windows often go completely grey, or partially grey (see screenshots). Moving the cursor over the buttons in the top right of the window will trigger the issue on affected systems.

This affects all Geforce 5, 6 and 7 users with nvidia-glx-173 or -177. This issue appeared as a regression with 169.07, and has been fixed as of 180.06.

More information at http://www.nvnews.net/vbulletin/showthread.php?t=104822 and http://www.nvnews.net/vbulletin/showthread.php?t=123072 .

WORKAROUNDS:
Change the titlebar of the Human theme (eg. to clearlooks)
-or-
Disable Compiz
-or-
Use the 180.06 or greater Nvidia driver

SCREENSHOTS:
http://launchpadlibrarian.net/19116675/glitch.png
http://satfilm.net.pl/~gammaray/compiz_bug.png

NOTE:
Bug 186382 is an unrelated nvidia titlebar issue which looks like these:
http://launchpadlibrarian.net/12535841/eclipse-titlebars.png
http://launchpadlibrarian.net/11586392/gwd_drawing_problem.png

[Sebastien Bacher (seb128)]

 compiz (1:0.3.6-1ubuntu13) feisty; urgency=low
 .
   * 020-move-away-from-having-client-side-positioning-of-windows.patch:
     - Upstream patch : Move away from having client side positioning of windows.
       Window size must be server side so to be able to do atomic move-resize
       operations position must also be server-side. This means that
       serverX and serverY fields in CompWindow struct has higher priority
       than attrib.x and attrib.y. attrib.x and attrib.y is still the client
       side position and any code dealing with the visible position of a
       window should use these. Code that needs to be aware of any pending
       position changes should look at serverX and serverY.
   * 021-only-update-window-position-when-no-pending-position.patch:
     - Upstream patch : Only update window position when no pending position
       changes exists.
   * 022-libXrender-workaround-gradient-issue.patch:
     - Upstream patch : Check version of libXrender and workaround gradient
       issue if older than 0.9.3. (Close #99508)
   * 023-dont-force-a-resize-when-maximize.patch:
     - Upstream patch : Do not force a resize when maximize state changes.
   * 024-fix-a-few-initiate-functions.patch:
     - Upstream patch : Fix a few initiate functions that should steal events.
   * 026-enable-sync-request-protocol-for-override_redirect-windows.patch:
     - Upstream patch : Enable sync request protocol for override_redirect
       windows as 025-fix-sync-request-issue.patch likely fixed the issues seen
       previously.
   * 027-fix-windows-being-maximized-on-incorrect-output.patch:
     - Upstream patch : Fix issue with windows being maximized on incorrect
       output.
   * 028-make-sure-no-core-instance-of-window-is-painted-after-minimize.patch:
     - Upstream patch : Make sure no core instance of window is painted after
       minimize animation. (bnc 240960)
   * 029-add-demands-attention-state-when-focus-on-map-was-prevented.patch:
     - Upstream patch : Add demands attention state when focus on map was
       prevented.
   * 030-reset-rotation-correctly-when-we-receive-a-client-message.patch:
     - Upstream patch : Reset rotation correctly when we receive a client
       message that cause us to move the viewport.
   * 031-fix-active-window-tracking.patch:
     - Upstream patch : Fix active window tracking. We're always setting the
       active window property so there's no need to monitor that property.
   * 032-check-for-pending-maps-on-hide.patch:
     - Upstream patch : Check for pending maps when trying to hide a window.
   * 033-maximize-windows-if-too-big-for-desktop.patch:
     - Upstream patch : Enable the code in the placement plugin that maximize
       windows when they are too big for their work area.
   * 034-read-current-window-position-properly.patch:
     - Upstream patch : Read current window position properly.
   * 035-set-state-to-normal-when-window-is-mapped.patch:
     - Upstream patch : Make sure we set state to Normal again when window is
       mapped.
   * 036-use-findTopLevelWindowAtDisplay-when-receiving-FocusIn-events.patch:
     - Upstream...

[Maciej Podkomorzy (gammaray)]

Well, after the last compiz update the bug still seems to be there. In addidtion, I've noticed that after the update, when I maximize windows. sometimes their titlebar becomes inactive (the buttons don't work either). Attached a small screencast to show the aforementioned bugs.

[Janne Hyötylä (janne-hyotyla)]

> In addidtion, I've noticed that after the update, when I maximize windows. sometimes their titlebar becomes inactive (the buttons don't work either). Attached a small screencast > to show the aforementioned bugs.

I can confirm that with Feisty final, compiz activated, Radeon 9800 Pro with 'ati' driver (details at the bottom).
It does not seem to depend on any compiz setting.

When opening a window and then maximizing it, the title bar buttons do not work anymore.
After pressing Alt + leftclick in the window (activating the "move window" mode), the buttons work again.
When unmaximizing from this state, the title bar buttons stop working in the now unmaximized window until briefly activating the "move window" mode.

When a window is opened in the maximized state, same behaviour after unmaximizing once.

When the title bar is in the 'broken' state, right clicking on it displays the desktop popup menu, or if there is another window at that position, brings that window to the foreground. It's as if the title bar did not exist (see screenshot, note the context menu, I right clicked directly on the title bar, then waited for the delayed screenshot to be taken).

This happens to me almost every time, but not *every* time.

$uname -a:
Linux gondor 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux
$sudo lspci -vv:
03:00.0 VGA compatible controller: ATI Technologies Inc Radeon R350 [Radeon 9800 Pro] (prog-if 00 [VGA])
        Subsystem: ATI Technologies Inc Unknown device 0002
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (2000ns min), Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 22
        Region 0: Memory at d0000000 (32-bit, prefetchable) [size=128M]
        Region 1: I/O ports at d000 [size=256]
        Region 2: Memory at e6000000 (32-bit, non-prefetchable) [size=64K]
        [virtual] Expansion ROM at e5000000 [disabled] [size=128K]
        Capabilities: [58] AGP version 3.0
                Status: RQ=256 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3+ Rate=x4,x8
                Command: RQ=32 ArqSz=2 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x4
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

[Alexander Hungenberg (alexander-hungenberg-gmail)]

With all updates installed I can also confirm this bug.
The titlebar gets truncated after switching between a maximized and a non maximized Window 2 to 3 times. The way compiz truncates the title bar is always exactly the same, and when you drive with the mouse over it everything is alright.
System: Feisty 7.04 stable
Graphics Driver: nvidia / Geforce 2 MX 400

Attached is a screenshot of the problem

[Matthew McGowan (mmcg069)]

I have this problem as well.

Its really easy to reproduce, it happens roughly 1 in 5 times i hover over a minimise. expand or close button. But also on other occasions.

[Matthew McGowan (mmcg069)]

with regard to above comment. i have nvidia 9600, glx-nvidia-new driver packaged by ubuntu

[Jan de Mooij (jandemooij)]

I can confirm that this bug is not fixed yet. nVidia 6600GT, nvidia-glx-new driver, Ubuntu Gutsy.

Should we move this from Fix Released to Confirmed?

[Chris Coulson (chrisccoulson)]

This is still affecting users in Gutsy RC

[Chris Coulson (chrisccoulson)]

I can also confirm that this is not fixed in Gutsy RC - nvidia 7900GT 100.14.19 drivers. Screenshot attached.

[bwat47 (bwat47)]

Same here, Nvidia 7600GS, 100.14.19 driver, Gutsy RC

[Kalpik Nigam (kalpik)]

Yes, i get the same artifacts here. Nvidia FX5700 LE / 100.14.19.

[Matt Joiner (anacrolix)]

I get it too. Gutsy RC up to date. Nvidia 7600 GS. Exactly as per first screenshot above.

[Chris Coulson (chrisccoulson)]

I've nominated this for Gutsy as this seems to be a long standing issue affecting quite a few users. With Compiz enabled by default, this bug will not leave very good first impressions with potentially new Ubuntu users.

[James N (jnylen)]

Chalk up another user with this problem - I filed a bug not realizing this one already existed. My screenshot can be seen at http://www.auburn.edu/compiz-gtk.png

[James N (jnylen)]

Sorry, that URL should be http://www.auburn.edu/~nylenjc/compiz-gtk.png

[Fabio FZero (fabio-fzero)]

I can also confirm this bug on Gutsy final release version. My card is an on-board GeForce 6100 using the nvidia-glx-new drivers.

[Crispin Kirchner (kcrispin)]

I had this in Feisty and now in Gutsy. It's also when using beryl instead of compiz. I think it's rather a heliodor bug because when using emerald (in Feisty) the artefacts didn't appear. I'm using nvidia-glx-new now, it was the same with nvidia-glx under Feisty. All buttons still work, but sometimes it happens that the whole decoration turns grey. My artefacts look the same as the screenshots above. I don't think (but I'm not sure) that the error occured with windows that weren't maximized. The buttons in the decoration also all still work because when I hover the buttons, all artefacts in the decorations disappear.

[Amol Karmarkar (amol-karmarkar)]

I can also confirm this bug on Gutsy final release that I installed few days ago. My card is an NVIDIA GeForce 7300 and I am using the nvidia-glx-new drivers.

[Gaspard Leon (gaspard.leon)]

Confirmed with Ubuntu 7.10 gutsy i386 release

Video: NVidia Geforce FX 5900XT (nvidia-glx-new)

Randomly it appears the top half of the title bar is a white/gray gradient with part of the window icon poking through.

Not a critical bug but looks like it's been hanging around for a while, and looks a bit un-polished.

As described above, when the window is maximized, you just move your mouse over the minimize/maximize/close or window icon buttons then hover (don't always need to hover), randomly the corruption should appear.

[Stefan Rehm (stefan-rehm)]

Confirmed with Ubuntu 7.10 using a Geforce 7950 GT (nvidia-glx-new).
However the bug occurs only when using certain windows border themes like Human or Glossy. When using for example Glider or Mist everything works fine for me.
I also could not trigger the bug using various ATI cards (with xorg radeon drivers).

[Gaspard Leon (gaspard.leon)]

My fix: use emerald

[Benjamin Drung (bdrung)]

I can confirm this bug. I am using Ubuntu 7.10 (amd64) and I have a GeForce 7950 GT (nvidia-glx-new). I am using the Human theme.

Sometimes the title bar turns gray when switching the window, instead of getting brown.

uname -a
Linux deepthought 2.6.22-14-generic #1 SMP Sun Oct 14 21:45:15 GMT 2007 x86_64 GNU/Linux

[andmej (andmej)]

Any fix for this bug yet?

I'm also affected using Ubuntu Gutsy 7.10. My video card is an AGP nVidia GeForce 6600, using nVidia proprietary drivers.

[Michael Walter (mwalter)]

Happens for me, too (gutsy with latest updates).

[James N (jnylen)]

I've switched to using Emerald as my theme engine, mainly because of this bug.

[Gabriel M. (gabrielm)]

The problem persists in Gutsy final, with all updates as of today.
Nvidia 7800gs here.

[ಓಂಶಿವಪ್ರಕಾಶ್ (Omshivaprakash H L) (omshivaprakash)]

Even Emerald is not helping me. NVidia GeForce Go 7400 here

[Sam Townsend (stownsend42)]

I have this problem too on an nVidia GeForce 6100.

A temporary fix is to install XGL.

[ashish (13lackhat)]

yeah this bug bugs me too. i am using Ubuntu 7.10 x86_64 (64-bit). i have installed compiz and also i use nvidia proprietary drivers. my graphics card is GeForce 7300 Go. this happens to me using firefox generally. but interestingly yet i don't think this bug is restricted to title bar only. i' have attached a screen shot of an another problem (screen shot will make it clear). and this happens only to Firefox during maximization. also the latter bug isn't seen always (but most of the time it is).

PS: during viewing pdf in full screen using the default viewer shipped with ubuntu if i hover the mouse over leave full screen button the screen flickers* twice before displaying the description of the button.

*complete screen goes black for a millisecond

hope this helps. i don't think its limited to the title bar only. and neither is it related to i386 only.

[ashish (13lackhat)]

one more screen shots are attached. and is a permanent fix released??

[Rodney Halaquist (rhalaquist)]

Well I guess I am not the lonely sailor after all.
-nVidia GeForce 6150 LE
Ubuntu 7.10 (Gutsy)

I had far worse screen shots of some of the mess (got misplaced) I hope they are/will try to figure out a solution to this.
Yea, I know, there are other more important.... or why don't you fix it, etc..., Anyway good luck all and thanks for the ear!

[James N (jnylen)]

I advise everyone experiencing this bug to switch to Emerald for theme management, as it doesn't look like anyone will be fixing this bug any time soon.

Emerald has the potential to look and act a lot nicer, and it is infinitely more customizable than the Compiz GTK decorator, with a wide variety of options for transparency and color blending, shadows, order/type/position of titlebar buttons and other elements, window title colors and outlines, etc.

[Travis Watkins (amaranth)]

This is some weird interaction between gtk-window-decorator, libmetacity, and clearlooks themes. It only occurs when using Clearlooks or a theme based on it (like Human).

[Stefan Rehm (stefan-rehm)]

This seems to be fixed in version 0.6.3+git20071119-0ubuntu1~gutsy1 available in gutsy-backports.

[Stefan Rehm (stefan-rehm)]

Ups, 0.6.2 is the correct upstream version number.

[Jan Rathmann (kaiserclaudius)]

@Stefan
On my system the backported version did not fix this bug.

Kind regards,
Jan

[Benjamin Drung (bdrung)]

@Stefan
On my system the backportet version 0.6.2+git20071119-0ubuntu1~gutsy1 did not fix this bug.

[Stefan Rehm (stefan-rehm)]

Ok, this is indeed not fixed. But this time I had to hover over the title bar buttons for quite a long time to trigger it.

[Nanley Chery (nanoman)]

***Attention*** Potentially helpful material below:
For me, this only occurs on a maximized window. Whenever I move to an object on the title bar (icon,min,max,exit), on the fourth time, the title bar glitches as seen above. The glitch disappears when I take the mouse off the object.

[Nanley Chery (nanoman)]

Sorry, the picture is above. I'm using an NV17 Geforce 4 MX420 on Ubuntu 7.10.

[Travis Watkins (amaranth)]

Guys, please stop adding "me too" posts and examples of how you trigger this bug. We know exactly when and how it happens we just haven't gotten to it to figure out where in the code it happens yet.

[yochaigal (yochaigal)]

I have the exact same problem. It only happens when I maximize the window.
Using Gutsy with an Nvidia Geforce 6600.

[tomko222 (tomko222)]

I think that It only happens in nvidia cards because in my 2 computers with nvidia cards (geforce 7600GS and geforce 6200) it doesn' t work good and in laptop (card: intel GMA 900) it works good. I use ubuntu 7.10.

[tomko222 (tomko222)]

I think that the solution for this problem are new nvidia drivers.

[Uphaar Agrawalla (uphaar)]

Have the same problem, on nvidia geforce 7000M card (ubuntu gutsy with all updates, proprietary driver).

[Jan Rathmann (kaiserclaudius)]

I have currently worked around the bug by using the MurrineRounded metacity theme, it looks rather similar to the original one, blends in well with the other components of the Human theme and obviously isn't affected by this bug. For anyone who is interested, it can be downloaded here:

http://gnome-look.org/content/show.php/MurrineRounded?content=54088

Kind regards,
Jan

[Jean-Francois Saucier (jfsaucier)]

Just to add that I am also affected by this bug with Gutsy/Compiz and a Nvidia card.

The new Nvidia driver (169.07) didn't fix it for me but the MurrineRounded workaround work well.

[Spencer Paul French (spf)]

For people experiencing this bug and using the clearlooks metacity theme the latest version from gnome svn is fixed, this might also help root out the reason the ubuntu default theme does it.

[Michael (madmac)]

I have started using Emerald and this has problem has gone away. I am leaning towards it being something to do with GTK/pre-loaded themes and 7.10 not playing nice with each other. Maybe?

[Travis Watkins (amaranth)]

As I said about 20 comments up we have a general idea of what the problem is. I wish people would stop "me too"ing on this bug, it is well known and we don't need more people to confirm it or state their configuration. It happens with every video card, every driver, etc.

[Savvas Radevic (medigeek)]

mark it as high (cosmetic) importance then :)

[Jan Rathmann (kaiserclaudius)]

On my up to date Hardy installation I was not able to reproduce the problem anymore so far. Maybe the new Human theme did fix this (a few days ago I still saw the bug with the "old" Human theme.)? Anyway, great news :-)

Kind regards,
Jan

[robert114 (robertreems)]

The problem isn't solved here on my 64 box.
I'm running the latest updates of 1 march

Robert

[Jan Rathmann (kaiserclaudius)]

@Robert
Good that you mentioned this, I gave it a closer look now and found out that the bug is also suddenly gone on my Gutsy installation. Could it be possible that this issue depends on the exact model of the graphics board one is using? I recently replaced my Geforce 7600GS with a Geforce 8600GT and can't remember of other changes I might have done to my system.

Kind regards,
Jan

[sfan (sfan)]

Hi!

I asked about this bug in the #gnome irc channel. Before gnome 2.22 the bug was also in the clearlooks metacity theme. Some months ago it was fixed. I thought, maybe somebody oft the gnome-devs knows what is the problem. I got 1 interesting answer:

>> [18:07] <benzea> I think the gradient in the clearlooks metacity theme was changed to lines to speed things up a bit or something
>> [18:07] <benzea> that might work around the issue

[sfan (sfan)]

I got also an answer of Cimi, he said

>> [18:13] <Cimi> valentin, you just need to replace <tint> operations with <lines> and correct chades
>> [18:13] <Cimi> *Shader
>> [18:13] <Cimi> *shades

it's a workaround, the problem is here:

>> [18:16] <Cimi> it's compiz buggied, btw
>> [18:17] <Cimi> or nvidia drivers :|
>> [18:17] <benzea> or both ;-)

Maybe this informations can help you to fix the bug

[tomko222 (tomko222)]

i think that nvidia drivers because with ati and intel gma cards it work fine

[Travis Watkins (amaranth)]

Not according to other reporters. Some say they have the problem with ati and intel drivers.

[tomko222 (tomko222)]

This bug is in ubuntu 8.04 alpha6 too.

[Steven W. Johnson (swj)]

I can confirm this bug is in ubuntu 8.04 alpha 6 as well, when using human-murrine +human window border (default); however changing the window border to clearlooks and using human-murrine works fine.

[Joshua Martin (jsmartin)]

I have the issue with Ubuntu 8.04 alpha 6 with latest updates, nvidia-glx-new, and the default theme. This bug has existed since Feisty - the title bar displays inactive when maximized in some applications (almost always in Firefox). Requires you to click on the title bar a few times before it is displayed correctly.

[Vince N (libertyshadow)]

Confirmed for Hardy Alpha 6 with Nvidia's 169.12 binary driver on the GeForce Go 7300 GPU. This bug seems to be particularly effecting Eclipse (3.2.2)

[Savvas Radevic (medigeek)]

Still not fixed, mouse-over an active maximized window, specifically over the buttons "minimize", "maximize" and "close".
I don't see a reason why this should be marked as "fix released", I've changed it back to "Confirmed", unless a bug/package maintainer knows if it's "In Progress".

$ lspci | grep -i nvidia
01:00.0 VGA compatible controller: nVidia Corporation G70 [GeForce 7300 GT] (rev a1)
$ apt-cache policy compiz nvidia-glx-new
compiz:
  Installed: 1:0.7.2-0ubuntu1
  Candidate: 1:0.7.2-0ubuntu1
  Version table:
 *** 1:0.7.2-0ubuntu1 0
        500 http://uk.archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status
nvidia-glx-new:
  Installed: 169.12+2.6.24.10-12.30
  Candidate: 169.12+2.6.24.10-12.30
  Version table:
 *** 169.12+2.6.24.10-12.30 0
        500 http://uk.archive.ubuntu.com hardy/restricted Packages
        100 /var/lib/dpkg/status

[sam tygier (samtygier)]

I described an alternate way to trigger this (or maybe a separate similar issue) in Bug #174880

it happens when the title of a fullscreen window changes

"
to reproduce on stock compiz, with the visual effects set to normal in system -> preferences -> appearance
open firefox.
maximize the firefox window
open a number of tabs (middle click on the BBC news headlines rss bookmark)
then switch between the tabs with the mouse or with CTRL+ Page Up.

it is not specific to firefox, i can reproduce with gnome terminal. it seems to occur when the title of a window changes.
run
while :; do echo -ne "\033]0;`date`\007";sleep 1; done
(changes the tile to the date and time every second)
"

[xoco (arthur.ivanov)]

Yes, i get the same artifacts here.

[xoco (arthur.ivanov)]

ai@ai:~$ lspci | grep -i nvidia
01:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6800 GS] (rev a2)
ai@ai:~$ apt-cache policy compiz nvidia-glx-new
compiz:
  Установлен: 1:0.7.2-0ubuntu2
  Кандидат: 1:0.7.2-0ubuntu2
  Таблица версий:
 *** 1:0.7.2-0ubuntu2 0
        500 http://archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status
nvidia-glx-new:
  Установлен: 169.12+2.6.24.11-12.31
  Кандидат: 169.12+2.6.24.11-12.31
  Таблица версий:
 *** 169.12+2.6.24.11-12.31 0
        500 http://archive.ubuntu.com hardy/restricted Packages
        100 /var/lib/dpkg/status

[Lex Ross (lross)]

Got the same problem as reported by xoco on nVidia GeForce 7000M / nForce 610M chipset running Hardy 64-bit. Same versions of Compiz and nvidia-glx-new driver.

[Edward Clark (eeclark)]

I cannot reproduce on Dell D600 with ATI using FGLRX and Compiz.
Kernel is 2.6.24-12-generic

[Jan de Mooij (jandemooij)]

I can confirm the quotes from simpson-fan. When I commented out the <tint> lines for the three buttons in the top-right corner, it worked fine. So it would be nice if a theme expert could workaround the bug and redesign the buttons using lines, or copy them from another theme..

[Marco Scholl (traxanos)]

@Edward Clark
It only a Bug in combination with NVIDIA-Cards

[yaztromo (tromo)]

Marco it has been reported to affect all graphics chipsets, not just nvidia.

This has been mentioned several times already.

[Marco Scholl (traxanos)]

Oh sorry!

I can only confirm it for all my NVIDIA-Cards.
ATI and Intelcards work fine!

[Rossimo (ross-squires)]

Same problem here. Using Nvidia 7900 GS, if that matters.

[robert114 (robertreems)]

Jan de Mooij / simson-fan what exactly do I need to edit?

Is it the "/usr/share/themes/Human/metacity-1/metacity-theme-1.xml" file?
I've changed all the "<tint" with "<lines". I now have other buttons in the topright of a window. And the problem hasn't been solved, alltough it's a lot less obvious and it doesn't happen quite as much as before.
I'm not sure how to describe it.

Robert

[Jeremy (jeremy127)]

also getting this bug, running 64 bit hardy and nvidia 7900 GS

[Savvas Radevic (medigeek)]

At compiz devs / maintainers of the packages reported to be affected in this bug report:
You could calm down the crowd if there's a process in question, just to know someone's working on it, instead of jumping from party to party in the "assigned to" field.
I believe the main question is:
1) Can this be fixed? If not, then compiz shouldn't be supported, since users cannot see the most important part of a window, the subject / title in a titlebar, marking it as unusable from my point of view.
2) Is currently anyone doing anything about it?

Thanks

[Stéphane Maniaci (stephh)]

Still present on Hardy Beta. This has to be fixed before Hardy final release.

[brownknight (ramilclarin)]

I am running Hardy Beta x386 and I still have this issue with the title bar name becoming cut and unresponsive. Attached is screenshot.

[Greg Taylor (gtaylor)]

Still an issue on x86 with an ATI mobility card on a previously Canonical-issued Toshiba Tecra A4. This is a very glaring bug, it definitely needs attention. How about a status update at the very least?

[Savvas Radevic (medigeek)]

@ brownknight:
You don't suffer from this bug, your titlebar is not cut, it's hidden under gnome panel.
Hold the ALT key and your left mouse button to move your window a bit, then resize it properly.

[bwallum (rbw2)]

I have taken this bug to Gnome who insist it is a compiz bug.

QUOTE

http://bugzilla.gnome.org/show_bug.cgi?id=525298

------- Comment #4 from Thomas Thurman 2008-03-31 14:44 UTC -------
"None" is Ubuntu-speak for Metacity. "Normal" and "Extra" are Ubuntu-speak for
Compiz. Therefore this bug is NOTGNOME, but thanks for providing all that
information: I suggest you should take it to
https://bugs.launchpad.net/ubuntu/+source/compiz/+filebug where they'll be able
to make better use of it.

UNQUOTE

I am running:- Hardy 8.4 beta (2.6.24-12) AMD64, MSI K9N4 Ultra F, nForce 500 Ultra, Athlon 64 X2 4200+, nVidia GeForce 7300 GS. Driver is nvidia-glx-new. No problem with Visual Effects set to 'None'. Window bar breaks up and buttons whiteout on 'Normal' and 'Extra'.

If it means some intensive work between Compiz devs and Gnome devs then please, can we do it before the Hardy release.

It really needs fixing, it's as obvious as trying to drive a 4x4 with three wheels.

[DanielDeboer (scatterfingers-gmail)]

I upgraded to the 8.04 beta today and am suffering from this bug, but I did not suffer from it under 7.10 or any of the previous Ubuntu releases that I installed Compiz on. Changing the theme doesn't help, all my title bars including their icons and other decorations are either completely invisible or contain major artifacts (that appear to be bits of the background). I've disabled effects for now.

I'm using the lated restricted Nvidia drivers.

[billytalent (billytalent)]

I have a similar but different problem. Check out my title bar. It displays correctly, except the order of the close, minimize and maximize buttons are wrong !!

[Jan Rathmann (kaiserclaudius)]

@Suraj James
Regarding your problem it might help to have a look at the button order in the configuration of Metacity (at /apps/metacity/general/button_layout in gconf-editor). Compiz (with gtk-window-decorator) does also use these settings.

Kind regards,
Jan

[Nicklas Svanteson (nicklas-teknister)]

Still a problem in Hardy with latest updates as of today.

Will this be fixed before the Hardy release? As far as I remember it has also been a problem in Gutsy.
I sometime get a corrupted window border (half orange) as seen in earlier screeshots but most of the time I get a completely gray border as seen in attached screenshot.

[Nicklas Svanteson (nicklas-teknister)]

Forgot to mention....

As some have already pointed out the problem only appears when the window is maximized.

[Nicklas Svanteson (nicklas-teknister)]

Sorry for spamming... :(

If I change from Human window border to Clearlooks I don't experience the problem anymore.

[Stéphane Maniaci (stephh)]

Can confirm this too: this bug is related to the Human border theme. Switching to Clearlooks window borders fix the problem.

[billytalent (billytalent)]

Jan Rathmann,

 Your solution solves my problem. The order of the buttons are correct. However, the upgrade from 7.10 to 8.04 somehow made this change. Thanks for your help.

[deimon (deimon-gmail)]

"this bug is related to the Human border theme"
and UbuntuStudio theme :), and right, switching to not *buntu theme fix the problem.

[Savvas Radevic (medigeek)]

switching to clearlooks doesn't fix it here, but using the
clearlooksclassic window border, yes

[Savvas Radevic (medigeek)]

can this bug be added for the hugday on the 10th of april too? :\
https://wiki.ubuntu.com/UbuntuBugDay/20080410

[Dereck Wonnacott (dereck)]

package already marked as affected.

[Travis Watkins (amaranth)]

No, it says 'Status tracked in Hardy' so you completely closed the bug for human-theme. Reopening.

[James Schriver (dashua)]

For some strange reason this bug is not present in Hardy on my Dell XPS m1530 using nvidia-glx-new with an nVidia 8400 GS. However, it's still present on my workstation using an nVidia 7600 GS same driver.

[Juan C. Villa (juanqui)]

Same issue here. I've had it for as long as I can remember. Right now I have hardy with all available updates, an nVidia 7900GS, and nvidia-glx-new (+compiz).

[gabr10 (gabriobarbieri)]

I have the same problem with Hardy, with the human theme and compiz enabled.. Nvidia card with the latest nvidia-glx-new

[Phil Norbeck (ptn107)]

I can also confirm this on both my machines running [clean installed] Hardy beta daily 4-10-08, both with nvidia cards.

[cstadach (christian-stadach)]

I can also confirm this but.

Although up until todays update the "Extra Visual Effects" worked fine in my 8.04 installation.

I have a Thinkpad R60 with an intel gma 950 graphics card

[cstadach (christian-stadach)]

Actually I just did a clean reinstall of Hardy. Afterwards the "Extra Visual Effects" worked again

[tomko222 (tomko222)]

I think that the easiest way to solve this problem is using emerald.

[robert114 (robertreems)]

Well i installed XGL and i don't have the gliches anymore.

With emerald the problem is only less obvious.

Robert

[Max Littlemore (simon-leonard)]

I was just about to report the same bug when I stumbled across this.

I preformed an automated update today and went from having emerald working fine with no glitches to being lumped with metacity and title bars disappearing or not being displayed properly.

It's a bit annoying because I don't actually want metacity, but it got it replaced emerald anyway and it's still broken. Why is metacity still the default wm?

If there is any info I can provide that will help, please let me know.

[Bruno Santos (bsantos)]

Can you try do disable shade opacity like this:

gconftool-2 -s /apps/gwd/metacity_theme_shade_opacity -t bool FALSE

[Savvas Radevic (medigeek)]

Tried it, logged out and logged in, maximized a window and mouse-over a couple of times over the maximize,minimize and close buttons of the window, still happens

[Bruno Santos (bsantos)]

I've been following Hardy dev on a laptop with Intel graphics and it has been close to perfect (less the known 3d rendering issues to be fixed later), and thought of upgrading my desktop which has a nvidia card and had 7.10 working perfectly with compiz. I've also updated to latest nvidia drivers using envy and continue to get this weird issues with shadows and window borders using metacity themes.

If I change /apps/gwd/use_metacity_theme to FALSE the decorations seem OK, but the shadows don't show up.

[Bruno Santos (bsantos)]

OK, I unset the gconf keys for compiz and gwd and now the metacity decorations look OK, but on changing desktops the application windows render blurry until gaining focus... this must be related to something else. Window shadows still don't show.

[_oOMOo_ (hermann-blaxhall)]

Bruno I think the blurry windows was introduced with Compiz 0.7.4 release, it was for me and a couple of others - I reported a bug at https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/216705

Which key did you change for Compiz? I can only find the gwd key you mention.

[Bruno Santos (bsantos)]

I did a --recursive-unset for compiz and gwd, but I just confirmed that it was that key I referred previously that was FALSE, and made the decorations work with metacity themes. If I activate it, it breaks decorations again. :-(

As for blurry windows I found this: http://forum.compiz-fusion.org/showthread.php?p=54534 could the fix be backported to 0.7.4? Or will we need to get 0.7.5 from git?

[Michael Devenish (mdevenish)]

I'm getting the same issue with hardy beta, today's updates installed, nvidia-glx (GeForce 2 MX) - see screenshot. As mentioned above, it only seems to happen with windows maximised. I have visual effects set to normal. After updates of a week or so ago, I didn't notice the problem but it has started happening again. It doesn't occur all the time and I've noticed it mostly with firefox.

[Damian Barberon (damian01w)]

I'm getting the same issue with today's updates of gutsy, hardy, and fedora 8 on GeForce 7300GT and Clearlooks Gnome theme.

[Ahmad Amr (aamr)]

THIS BUG HAPPENS ONLY WITH THE UBUNTU HUMAN THEMES! I think that's the source of the bug, not compiz, change the theme to clear-looks for examples and everything will be just fine :)

[Jan de Mooij (jandemooij)]

Hi, I looked a bit further at the code and the theme, and this works for me:

In the theme file (/usr/share/themes/Human/metacity-1/metacity-theme-1.xml) on line 28 you have this line:
<distance name="left_width" value="0"/>"

If you change the 0 to a 1 it works fine for me, and it looks the same.

Can someone please confirm this?

[deimon (deimon-gmail)]

Jan de Mooij, thanks, its working for me. UbuntuStudio theme and Human theme.

[Kenneth Wimer (kwwii)]

If others who experience this bug can please test this and see if it also fixes the problem I can easily edit the xml file. As it is after final freeze I am hesitant to submit a new package without a couple of people verifying the results of this fix.

[jc1985 (jc1985)]

This has fixed the problem for me too (with Human theme). thanks!

[Roberto Cássio Jr. (rcsdnj)]

Anyone knows what is this setting supposed to do? I'd like to have some idea
about that, because, knowing this, side-effects of this modification could
be more predictable and we could do better testing.

[Benjamin Drung (bdrung)]

I can confirm that it also works for me (Human theme). Thanks to Jan de Mooij.

[yaztromo (tromo)]

After a bit of gpogling I found this http://ubuntuforums.org/showthread.php?t=74510
If you look at the bottom of the page there is some explanation there, maybe someone will understand what it means?

[Manolis Tzanidakis (mtzanidakis)]

On Wed, 2008-04-16 at 15:03 +0000, Jan de Mooij wrote:
> Hi, I looked a bit further at the code and the theme, and this works for
> me:
>
> In the theme file (/usr/share/themes/Human/metacity-1/metacity-theme-1.xml) on line 28 you have this line:
> <distance name="left_width" value="0"/>"
>
> If you change the 0 to a 1 it works fine for me, and it looks the same.
>
> Can someone please confirm this?
>

Works for me..

--
Manolis Tzanidakis
<email address hidden>
<email address hidden>

[Roberto Cássio Jr. (rcsdnj)]

Just my opinion: I don't believe this is a bug in the Human theme, since the windows manager probably is supposed to have the responsibility to draw things always in a consistent state, which doesn't seem to be the case (since the titlebar appears randomly corrupted). Even if human theme definition file was "broken" or anything like that, I'd expect all elements to be always drawn in the same way (even if it was the "wrong" way due to the bad configuration), or not drawn at all.

But I confirm this workaround changing the theme file's "left_width" setting works for me. I didn't understand very well what it does, but I'm not seeing any inconvenient while using it. So I guess this would be a suitable emergence fix for Hardy final, but the real bug itself should be probably fixed in Compiz (or something like that).

[Jan de Mooij (jandemooij)]

In decoration.c and gtk window decorator at some places different codepaths are taken if left_width == 0 && right_width == 0. Or if one of them or the sum is 0. I think you should look in that direction.

But including this fix/workaround in Hardy would be nice, as it's very annoying behavior for many people. For the theme redesign of 8.10 you should maybe base the theme on Clearlooks or a Murrine theme or anything else that doesn't need this...

[Darryl Grennan (darryl-grennan)]

The fix provided by Jan de Mooij worked perfectly.

[xoco (arthur.ivanov)]

The fix provided by Jan de Mooij worked perfectly.

[Troy James Sobotka (troy-sobotka)]

Roberto Cássio Jr. wrote:
Just my opinion: I don't believe this is a bug in the Human theme

This is 100% correct. There is no reason that setting a variable should cause unwanted behavior. This is a compiz bug as the same issue happens with a minimalist Mist window decoration layout. If both themes appear to work fine without compiz enabled, it seems a bit of a no-brainer that the bug lay inside of compiz.

[Darryl Grennan (darryl-grennan)]

Ok. I take that back. After applying the fix by Jan de Mooij, the corruption is gone. But now if I "Unmaximize" the window I get what would be best described as a "fluttering" effect with the titlebar. This never happened before. Can anyone else confirm that?

[Savvas Radevic (medigeek)]

Woohoo!! Works for me too, tested with firefox, terminal and some other apps.

> Ok. I take that back. After applying the fix by Jan de Mooij, the
> corruption is gone. But now if I "Unmaximize" the window I get what
> would be best described as a "fluttering" effect with the titlebar.
> This never happened before. Can anyone else confirm that?

No "fluttering" effects whatsoever.

P.S. Everyone hug Jan :)

[jc1985 (jc1985)]

I'm using Jan's fix since yesterday and everything is working perfectly, without any "fluttering effect"

[Jayson Rowe (jayson.rowe)]

On Thu, 17 Apr 2008, Jan de Mooij wrote:

> In decoration.c and gtk window decorator at some places different
> codepaths are taken if left_width == 0 && right_width == 0. Or if one of
> them or the sum is 0. I think you should look in that direction.
>
> But including this fix/workaround in Hardy would be nice, as it's very
> annoying behavior for many people. For the theme redesign of 8.10 you
> should maybe base the theme on Clearlooks or a Murrine theme or anything
> else that doesn't need this...
>
> --
> Window titlebar displayed not right with compiz enabled
> https://bugs.launchpad.net/bugs/99508
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
I just want to add that I'm using "Human Murrine" and I'm still having the
issue.
-jayson

[Jayson Rowe (jayson.rowe)]

On Thu, 17 Apr 2008, Jayson Rowe wrote:

>
>
> On Thu, 17 Apr 2008, Jan de Mooij wrote:
>
>> In decoration.c and gtk window decorator at some places different
>> codepaths are taken if left_width == 0 && right_width == 0. Or if one of
>> them or the sum is 0. I think you should look in that direction.
>>
>> But including this fix/workaround in Hardy would be nice, as it's very
>> annoying behavior for many people. For the theme redesign of 8.10 you
>> should maybe base the theme on Clearlooks or a Murrine theme or anything
>> else that doesn't need this...
>>
>> --
>> Window titlebar displayed not right with compiz enabled
>> https://bugs.launchpad.net/bugs/99508
>> You received this bug notification because you are a direct subscriber
>> of a duplicate bug.
>>
> I just want to add that I'm using "Human Murrine" and I'm still having the
> issue.

I have solved my issue by disabling compiz and enabling the new Metacity
Compositing feature. I'm satisfied.

-jayson

[Roberto Cássio Jr. (rcsdnj)]

This "fluttering" effect always happened to me here, with Compiz. When I put a window on certain positions, it starts moving quickly, as a flag under the wind. I didn't see any increase on the number of occurrences for this by using the Human theme workaround, though.

[dpr (dpr-aha)]

Hi, Jan's fix works for me too, although it just helps to avoid some problematic paths in the code.

[Kenneth Wimer (kwwii)]

Added the suggested work around changing 0 to 1, hope this helps

[Michael Devenish (mdevenish)]

Jan's fix works for me too (Human Theme, visual effects set to normal). I haven't noticed any "fluttering" effects.

[sam tygier (samtygier)]

i have always had the fluttering with wobble enabled. take an unmaximised window. move it so that the top of the window snaps to the bottom of the top panel, and that half the window is off the edge of the screen.

or put two windows side by side, with their tops differering by a few pixels. then move a third window to snap to the top of the higher of the first two.

[Savvas Radevic (medigeek)]

I think I know what you mean, the window suddenly jumps up and down
and you can't move it. That's a "snapping windows" or "wobbly windows"
problem, hence another bug, I had that before :)

[Jayson Rowe (jayson.rowe)]

On Thu, 17 Apr 2008, Savvas Radević wrote:

> I think I know what you mean, the window suddenly jumps up and down
> and you can't move it. That's a "snapping windows" or "wobbly windows"
> problem, hence another bug, I had that before :)
>
> --
> Window titlebar displayed not right with compiz enabled
> https://bugs.launchpad.net/bugs/99508
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

Call me crazy, but this just seems like WAY too many "bugs" for compiz to
be the default window manager (on supported hardware that is) in a LTS
release of Ubuntu. I might be off my rocker for thinking that, but oh
well.

With GNOME 2.22 there is an awesome compositing feature now compiled into
Metacity by default, and the results are similar to Ubuntu's compiz
implementation of "Standard Effects" - sure, the windows don't wobble, but
that's annoying after a while anyway (to many anyway, still - it's
personal preference).

PLUS, Metacity compositing runs on a lot more hardware than Compiz does -
it will run on Nvidia w/ just the "nv" driver enabled - it doesn't require
H/W acceloration at all.

Am I the only one thinking this way?!?!\

-jayson

[yaztromo (tromo)]

You're not crazy, compiz has many more window placement bugs than the ones mentioned here, like this one: https://bugs.launchpad.net/compiz/+bug/156055

That bug has prevented me from using compiz completely and it is only marked wishlist!

How do you enable the metacity compositing? I'd like to try that.

[Jayson Rowe (jayson.rowe)]

On Thu, 17 Apr 2008, yaztromo wrote:

> You're not crazy, compiz has many more window placement bugs than the
> ones mentioned here, like this one:
> https://bugs.launchpad.net/compiz/+bug/156055
>
> That bug has prevented me from using compiz completely and it is only
> marked wishlist!
>
> How do you enable the metacity compositing? I'd like to try that.
>
> --
> Window titlebar displayed not right with compiz enabled
> https://bugs.launchpad.net/bugs/99508
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
To enable the Metacity compositing in GNOME 2.22, simply run gconf-editor
and select Apps-> Metacity -> General and put a check in "Compositing
Manager"

A quicker way is from the CLi - to enable:

gconftool-2 -s '/apps/metacity/general/compositing_manager' --type bool
true

To Disable:

gconftool-2 -s '/apps/metacity/general/compositing_manager' --type bool
false

-jayson

[Launchpad Janitor (janitor)]

This bug was fixed in the package human-theme - 0.18

---------------
human-theme (0.18) hardy; urgency=low

  * Changing left_width value from 0 to 1 to fix bug (LP: #99508)

 -- Kenneth Wimer <email address hidden> Thu, 17 Apr 2008 13:56:43 +0200

[Jayson Rowe (jayson.rowe)]

On Fri, 18 Apr 2008, Launchpad Bug Tracker wrote:

> This bug was fixed in the package human-theme - 0.18
>
> ---------------
> human-theme (0.18) hardy; urgency=low
>
> * Changing left_width value from 0 to 1 to fix bug (LP: #99508)
>
> -- Kenneth Wimer <email address hidden> Thu, 17 Apr 2008 13:56:43 +0200
>
> ** Changed in: human-theme (Ubuntu Hardy)
> Status: Fix Committed => Fix Released
>

Yippee!

-jayson

[tomko222 (tomko222)]

human-theme looks good now but some other themes should be fixed too.

[Roberto Cássio Jr. (rcsdnj)]

Fixed in Compiz...? Isn't just an workaround done in Human theme? Shouldn't
be "fixed" in Human Theme only?

On Sun, Apr 20, 2008 at 9:40 AM, simpson-fan <
<email address hidden>> wrote:

> ** Changed in: compiz (Ubuntu Hardy)
> Status: Confirmed => Fix Released
>
> --
> Window titlebar displayed not right with compiz enabled
> https://bugs.launchpad.net/bugs/99508
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Travis Watkins (amaranth)]

Reopening compiz bug, this is not fixed in compiz.

[Hew (hew)]

I use the "Airplane" effect for minimise in compiz. I minimised firefox and saw the bug appear on the titlebar as the animation occured, which I could reproduce by maximising and minimising again. I moved the window to the next (empty) workspace and could not reproduce the bug, but moving it back it appeared again. My workspace had about 5 other windows open on it, so I closed a few preparing to take a screenshot, but now I can no longer reproduce the issue, even after filling my workspace with all sorts of windows.

It's clear that this issue still exists in compiz, and the value="1" fix is just a workaround. I suppose technically this is not fixed in human-theme, but then again this is a compiz issue in the first place.

[Tristan Schmelcher (tschmelcher)]

Hewus and other Hardy users:

If you still see title bar corruption but with reduced frequency, you may actually be seeing bug 186382, which is separate. (In particular, if you see any corruption on non-maximized windows, then that's bug 186382.)

[Juan Xavier (juanvicious)]

I started having a problem like this (Title Bar messes up when hovering the buttons) after upgrading my nvidia drivers to 173.14.05. It only happens themes using the "Human" window borders; I already have the fix committed here but it doesn't seem to help. Also tried Compiz 0.7.6 without any luck.

The bug was filed by another Compiz user here http://bugs.opencompositing.org/show_bug.cgi?id=985

[warmrobot (imfrolov)]

The same situation like Juan Xavier described, except one thing: the bug is not only in "Human" theme, but in Blue "Glossy" (not sure how it will be English name of this) theme too. However bug triggered not very often.

[mickeydz (dave-watchingred)]

Here is a fix. None of the above worked for me so I started to look into how to fix it from an nVidia perspective.

1. Go here and download this driver: http://www.nvidia.com/object/linux_display_ia32_100.14.19.html

2. Once downloaded, press Ctrl+Alt+F1 this will take you to a terminal. To get back out of it press Ctrl+Alt+F7.

3. Type in your login info.

4. Kill X by typing: sudo /etc/init.d/gdm stop

5. Now install by typing: sudo sh NVIDIA-Linux-x86-100.14.19-pkg1.run

6. Start X again by typing: sudo gdm

7. Enjoy a glitch free titlebar.

[tomko222 (tomko222)]

It works in my computers with nvidia geforce 7600GS and nvidia geforce 6200 card :)

[Wobbo (wobbo)]

This bug still exists in Ubuntu 8.04.1 all updates. Using nvidia geforce 7600GS, nvidia geforce 7800GS and nvidia geforce 6600GS on i386 systems.

[robert114 (robertreems)]

No solution found yet?

I'm using Emerald right now

[Hew (hew)]

This bug is back in Intrepid. Present in at least Human-Murrine, Human-Clearlooks, and NewHuman.

<distance name="left_width" value="1"/> in both Human and NewHuman versions of the xml file.

[K. Deniz Ogut (kdenizogut)]

My experience: 8.04, nvidia G0 7600. There was no such problem when "nvidia-glx-new" package was installed via "Hardware Drivers". For some reason (namely, screen flashing problem) I uninstalled "nvidia-glx-new" via "Hardware Drivers", installed Envy and let Envy to choose and install the driver by itself. Now everything else seems OK about the driver (no flashing yet) but now -for the first time- I have the title bar issue with all the three human theme variants. If to add: Compiz is not enabled on my machine as I know far; I mean, I didn't install or enable Compiz. I don't know exactly what driver Envy installed (some sort of "new" thing, I know) and what setup changes it performed so title bar problem showed up. I hope you'll find a solution because I want my human theme back; it means much more than cosmetics to me. Regards.

[Vikram Dhillon (dhillon-v10)]

Hey,
I have had some similar problem to this a little while ago. Okay first   of all I am not a computer geek, but i'll try my
best.  Your envy drivers might not be compatible with the theme you installed.  I prefer NVIDIA and about your screen flashing problem you need to decrease your screen refreshing rate it is usually set at 60 hertz you need to either decrease it or increase it, whichever one sovles your problem. After changing your refreshing rate try to apply your theme agian and reboot your system.  http://support.microsoft.com/kb/311403  it will tell you that the your refreshing rate needs to increase or decrease.
If the problem still continues please email me.  I'll be glad to help you. Hope that helps
Vikram

----- Original Message ----
From: K. Deniz Ogut <email address hidden>
To: <email address hidden>
Sent: Friday, August 15, 2008 6:50:00 PM
Subject: [Bug 99508] Re: Window titlebar displayed not right with compiz enabled

My experience: 8.04, nvidia G0 7600. There was no such problem when
"nvidia-glx-new" package was installed via "Hardware Drivers". For some
reason (namely, screen flashing problem) I uninstalled "nvidia-glx-new"
via "Hardware Drivers", installed Envy and let Envy to choose and
install the driver by itself. Now everything else seems OK about the
driver (no flashing yet) but now -for the first time- I have the title
bar issue with all the three human theme variants. If to add: Compiz is
not enabled on my machine as I know far; I mean, I didn't install or
enable Compiz. I don't know exactly what driver Envy installed (some
sort of "new" thing, I know) and what setup changes it performed so
title bar problem showed up. I hope you'll find a solution because I
want my human theme back; it means much more than cosmetics to me.
Regards.

--
Window titlebar displayed not right with compiz enabled
https://bugs.launchpad.net/bugs/99508
You received this bug notification because you are a member of Ubuntu
Artwork Team, which is subscribed to human-theme in ubuntu.

[Nick (nicky-nick-nickleton)]

I have this problem in 8.04 with an NVidia card using the drivers provided by Ubuntu.

My screenshot looks a little different to the other ones I've seen - rather than being cut off and grey, my titles go pink and transparent. It appears at random when I focus a window, and it can be fixed again by defocusing and focusing the window. The smaller window shows what the title bar ought to look like.

It seems most reproduceble when flicking to and from a maximised Eclipse window. Going between other windows doesn't seem to produce the effect. Flicking between Eclipse and Firefox will sometimes cause the Firefox title to go pink too. Simply having Eclipse running doesn't cause the effect.

[Hew (hew)]

Nick: Your issue is bug 186382

[Γουργιώτης Γιώργος (aka Gourgi) (gourgi)]

this bug still exist in intrepid
i use alpha 6 with nvidia-glx-177

here is my xorg.conf something else needed please tell me to provide it

[Laura Cowen (lauracowen)]

I've installed Intrepid alpha 6 with all the updates to date and when I enable compiz (Normal, Extra, or Custom option (when simple-ccsm is installed)), the window titles are not displayed at all.

I'm on a Samsung Q35 with Intel graphics - all non-proprietary drivers. This has always been a problem (I raised a bug about it a long time ago but I can't find it now - it's most likely one of the dupes of this bug). Is there any chance of fixing it for Intrepid?

[hal1984 (hal-1984)]

A workaround to this problem is custom the Human theme and change the titlebar by other one available, like the clearlooks.

[hal1984 (hal-1984)]

https://bugs.launchpad.net/ubuntu/+source/human-theme/+bug/276375

see this bug reported by me. Now that the border_left=1 isn't working for many people, and that have introduced a new bug, I think is should be restore to border_left=0.

[Terry Zhou (zhouxc)]

Hal's workaround really works!

>hal1984
>A workaround to this problem is custom the Human theme and change the titlebar by other one available, like the c>learlooks.

[Hew (hew)]

Yes, this issue only occurs when compiz is combined with the human-theme titlebar. Clearlooks (and others) work fine.

[Ricardo Pérez López (ricardo)]

Bug reported by me for Intrepid beta. Same issue, same symptoms and same workaround (change the titlebar to Clearlooks). I'll mark my bugreport (bug #277562) as duplicated.

[_oOMOo_ (hermann-blaxhall)]

Changing the titlebar doesn't work for me, not does using emerald. The window decoration comes and goes as it pleases.

If I hover the cursor over the button area the decoration returns. Using different themes alters the behaviour slightly, but the basic issue remains.

No problems evident when using Metacity, just Compiz. I'm using the Nvidia 177 beta driver but the problem has happened on my laptop since Gutsy, and all the Nvidia drivers + Compiz have exhibited the same behaviour.

[Hew (hew)]

This bug report is about the compiz/human titlebar issue which looks like these:
http://launchpadlibrarian.net/13469825/FirefoxTitleBar.png
http://launchpadlibrarian.net/13147434/Screenshot.png

Bug 186382 is an unrelated nvidia titlebar issue which looks like these:
http://launchpadlibrarian.net/12535841/eclipse-titlebars.png
http://launchpadlibrarian.net/11586392/gwd_drawing_problem.png

Changing the titlebar to something other than Human (eg. clearlooks) stops this issue, but does not stop the nvidia titlebar issue. While there is no need for extra confirmation since this report has already been triaged, if you have new information for the report, please include a screenshot of your problem. Thanks.

[Ricardo Pérez López (ricardo)]

If it's so obvious that Human theme is broken when using Compiz, why don't change the default Ubuntu theme (the titlebar, at least)? To ship a broken theme by default is not a very good decision, IMHO...

Later, when the Human theme were fixed, it could be included by default again.

[Hew (hew)]

This bug only occurs when using compiz, so metacity users do not have a problem. It is also possible that this is only happening to a subset of those using both human-theme and compiz, so the real scope of this bug is still unknown. Removing human-theme from Intrepid is not a reasonable solution as this is only a cosmetic issue (does not affect functionality) and has a workaround (using a different titlebar or using metacity). I believe there would be more of an outcry if users didn't have human-theme than if they have this current problem with compiz ;-)

I suspect the real bug is in compiz anyway, and human-theme is simply triggering it in a way that other themes don't. The earlier fix that was provided for Hardy was merely a workaround patch for this issue in compiz, so the developers probably already know where to look.

[Hew (hew)]

Is anyone experiencing this bug on non-nvidia hardware on Intrepid? If so, please include a screenshot. Thanks in advance.

[Ricardo Pérez López (ricardo)]

> It is also possible that this is only happening to a subset of those using both human-theme and compiz, so the real scope of this bug is still unknown.

The problem is that Ubuntu uses Human theme and Compiz by default (the latest only if he has a compatible hardware), so the scope of this bug could be considered high.

[Kenneth Wimer (kwwii)]

What is not clear is exactly which graphics chipsets this bug effects

[Ricardo Pérez López (ricardo)]

nVIDIA graphics card, at least (mine).

Besides that, this bug in Intrepid is obviously a regression, because Hardy doesn't have this problem. If Ubuntu developers applied in the past a fix/workaround for Hardy, I think they must re-apply it again for Intrepid, and do it before Intrepid release. Later, with lower time requirements, we could investigate further for the origin of the problem, and fix it forever (in that way, the bug will not be re-opened again for Jaunty, and so on...).

Thanks in advance.

[Erno Horvath (szerencsefia)]

Kenneth Wimer wrote:
> What is not clear is exactly which graphics chipsets this bug effects
>
nVIDIA definitelly.
--
Cheers, Erno Horvath [szerencsefia]
--
http://www.szerencsefia.webs.com

[Hew (hew)]

Ricardo: The workaround is still applied, you should read the previous comments to become familiar with the issue. The grey titlebar is what seems to be "new" with Intrepid, but it should be considered as this same bug for now since it has exactly the same behaviour as the stripey titlebar issue, and likely has the same root cause. There is no known fix for this other than the workarounds already mentioned.

Erno: There have been comments about this bug on ATI hardware earlier in this report, but we don't know if that is still the case with Intrepid, or if they were even commenting on the right bug. It's looking like it might be nvidia specific (but not all nvidia hardware), but it's too early to say "definitely".

[nyékhelyi gábor (n0gabor)]

It seems when changing titlebar from Human to e.g. Glossy, the titlebark works as expected.
(using latest Intrepid + nvidia)

[Ricardo Pérez López (ricardo)]

I don't know why it's so difficult to apply the same Hardy's "patch" in order to fix/workaround the problem in Intrepid. Not doing so will generate a regression. I have my Intrepid fully updated, but I can't select Human default theme with Compiz enabled because of this bug.

Any Compiz developer can explain why the bug is "fixed" in Hardy and why can't be fixed in Intrepid?

Thanks in advance.

[Kenneth Wimer (kwwii)]

I will reapply the hack to make this go away...I had removed it because I thought it was no longer a problem and it caused another bug

[Ricardo Pérez López (ricardo)]

Thank you very much, Kenneth. Obviously it isn't the best solution, but at least Intrepid will not show this ugly symptoms and we'll have six more months to get a better fix. Thanks again.

[Launchpad Janitor (janitor)]

This bug was fixed in the package human-theme - 0.28.2

---------------
human-theme (0.28.2) intrepid; urgency=low

  * Adding work-around for LP: #99508 again

 -- Kenneth Wimer <email address hidden> Thu, 16 Oct 2008 13:09:59 +0200

[_oOMOo_ (hermann-blaxhall)]

Seems to me that applying some ugly hack to the human theme that stops ONE of the issues for SOME of the people experiencing this bug is not the same as FIXING it.

[Ricardo Pérez López (ricardo)]

Kenneth, the latest update DOESN'T solve the problem. The title bar changes from brown to grey when you move the mouse over the top-right buttons in the title bar (minimize, maximize & close), rhythmically left and right, right and left.

$ dpkg -s human-theme | grep ^Version:
Version: 0.28.2

Please, can you check if the workaround has been actually applied? Thanks.

[Hew (hew)]

Reopening / triaging. The human-theme workaround has been applied, you can see from the diff. It doesn't fix the problem because the root cause lies in compiz or the nvidia drivers, and there is something new and unknown with Intrepid that is triggering it. Again, this is likely the same bug as Hardy since it is the same behaviour, but it is being triggered by something new. If you really can't stand the problem, you can replace the human-theme titlebar with something else such as clearlooks. This is unlikely to be fixed by Intrepid release.

[Ricardo Pérez López (ricardo)]

It's not about me. It's about the fact that many users will have a regression. I can change the titlebar style; that's not a problem for me. But many nVIDIA users (and there's a LOT of nNVIDIA users), both novice and experienced, many of them even Ubuntu newcomers, could feel a degraded experience and a sense of some-sort-of-unfinished work. I don't know how to fix this issue, but IMHO the Ubuntu artwork team could take a look and see if the default titlebar style of the Human theme could be changed slightly in order to not get the issue, at least as a temporary fix until a better solution will found in the following six months.

It's only my opinion.

[Hew (hew)]

Thanks for your comment and concern Ricardo. There are many Nvidia users who do not experience this issue, and the feeling I get is it's only a small fraction of users that get this problem. I spoke with mvo a while ago asking if this bug should be release critical for Intrepid, but this doesn't appear to be a high-impact bug and it has a simple workaround. I share your concern about the impact of this issue on new users with Intrepid, but I don't believe there are enough users experiencing this problem to warrant changing the human-theme titlebar for everyone (remember also that we are now in FinalFreeze).

Since there have only been reports of this issue on Nvidia hardware (ATI and Intel seem to be unaffected), I'm opening a task for nvidia-graphics-drivers-177 (experienced the problem with 177 and 173).

[Eric Donkersloot (ericd)]

Could this bug be affecting AGP based cards only ?

[Shane O'Connell (shaneoc)]

Hew: If this is only affecting a small fraction of users then I agree with you. But how do you know that there are many nvidia users who don't experience the problem?

[Kenneth Wimer (kwwii)]

Does the added one pixel still work around the problem? If not I will remove it again as the work around causes another bug.

[Hew (hew)]

Eric: I have a PCIe card and I am affected.

Shane: mvo said he didn't have the problem with an nvidia card, and although there are a reasonable number of subscribers, I would expect far more if, say, half of nvidia users had the problem. This is of course just a guess, and we can't know for sure without some sort of survey being conducted, or ideally, the actual problem being identified.

Kenneth: The one pixel workaround does not fix the problem. It's best to remove it if it's causing other problems. Thanks.

[MarcoBazzani (visik7)]

regression in intrepid same behaviour as on hardy before the fix

[MarcoBazzani (visik7)]

here the sshot

[Filipe Sousa (natros)]

I have two graphics cards, one nvidia 7300 and another nvidia 8800. The problem (eclipse-titlebars.png) only happens with 7300. If I set InitialPixmapPlacement=2 then I get the title bar effect in FirefoxTitleBar.png.

[Barry Shilliday (teppic74)]

This affects me. I never had a problem with any previous release, only in Intrepid. The graphics card is an nvidia 6600GT.

It is reproduced every time I move the mouse over the title bar.

Changing the window border style from Human to Clearlooks fixes the problem.

[Uphaar Agrawalla (uphaar)]

This bug has 28 duplicates, how can it be affecting a small number of people? I'm sure there are plenty of people who haven't commented here.

For me also the hardy workaround had fixed the problem, but it has reappeared now that I've upgraded to Intrepid.
An annoying thing about this is that if you are working with a changing title bar, like compose a new mail in evolution and start typing the subject - then it will exhibit the behaviour which is distracting.

[_oOMOo_ (hermann-blaxhall)]

"An annoying thing about this is that if you are working with a changing title bar, like compose a new mail in evolution and start typing the subject - then it will exhibit the behaviour which is distracting."

Exactly. In Thunderbird the email subject seems to overwrite the default titlebar text which sends it into a frenzy of blinking and vanishing. The other usual suspects are anything run under WINE and OpenOffice.

I wish this only affected the human theme for me, but it even messes up emerald. Every theme and window decorator I've used on this laptop (Nvidia 6100) with Compiz enabled displays this bug to a greater or lesser degree.

[billytalent (billytalent)]

How come this wasn't addressed over the last 6 months ? Does Kubuntu have this issue ? I'll just switch over to kubuntu if it doesn't. Kubuntu looks better anyway (Eye Candy)

[Hew (hew)]

Uphaar, _oOMOo_: You are experiencing bug 186382, not this bug.

Suraj: The real cause is still unknown, which is why this issue still exists. Workarounds have already been discussed (disable compiz or change the human-theme titlebar). I suppose switching to KDE is just an extreme way of implementing this workaround :P

Thanks for the reports on which cards this is happening. I'm using a 7600GT. Perhaps this is specific to Geforce 6 and 7 series? It's looking more and more like an nvidia driver issue.

[Hew (hew)]

Closing the Hardy SRU tasks since the fix was already provided by human-theme.

[_oOMOo_ (hermann-blaxhall)]

"Uphaar, _oOMOo_: You are experiencing bug 186382, not this bug."

Sadly, both.

[Uphaar Agrawalla (uphaar)]

Agreed. We are experiencing both the bugs.

[Leif Walsh (leif.walsh)]

I still see this on Intrepid with full updates. Also, this affects not only human-theme, but anything with a similarly-shaped window decoration (human-clearlooks, darkroom).

[Leif Walsh (leif.walsh)]

Agh, I should have given my system stats:

% cat /etc/X11/xorg.conf
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder63) Wed Oct 1 15:09:35 PDT 2008

Section "ServerLayout"
    Identifier "Layout0"
    Screen 0 "Screen0" 0 0
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "Module"
    Load "dbe"
    Load "extmod"
    Load "type1"
    Load "freetype"
    Load "glx"
EndSection

Section "InputDevice"

    # generated from default
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/psaux"
    Option "Emulate3Buttons" "no"
    Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier "Keyboard0"
    Driver "kbd"
EndSection

Section "Monitor"
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "Unknown"
    HorizSync 30.0 - 110.0
    VertRefresh 50.0 - 150.0
    Option "DPMS"
EndSection

Section "Device"
    Identifier "Device0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
EndSection

Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    Option "AddARGBGLXVisuals" "True"
    SubSection "Display"
        Depth 24
    EndSubSection
EndSection

% dpkg -l nvidia-glx-177 compiz human-theme metacity xorg linux-image-generic
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
ii compiz 1:0.7.8-0ubunt OpenGL window and compositing manager
ii human-theme 0.28.2 Human theme
ii linux-image-ge 2.6.27.7.10 Generic Linux kernel image
ii metacity 1:2.24.0-0ubun A lightweight GTK2 based Window Manager
ii nvidia-glx-177 177.80-0ubuntu NVIDIA binary Xorg driver
ii xorg 1:7.4~5ubuntu1 X.Org X Window System

[ian0mackenzie (ian0mackenzie)]

Dunno if it helps for me to say so and add one more affected, but I'm having this problem too... Using latest intrepid (beta) with all updates.
On an HP DV6000T Laptop:
Intel core 2 duo
geforce Go 7400 video card
1 GB DDR2

[Michael Hastrup Bendsen (michael-bendsen)]

having the same issue here on my HP DV9232EU

amd turion TL-52 CPU
Geforce GO 7600 256mb
2GB DDR2 Kingston pc5300

wondering about if its the nvidia 177.80 driver.

or if its just compiz-related

Kind regards Michael H

[Michael Hastrup Bendsen (michael-bendsen)]

just like to add, that im on ibex beta.
and gnome

[robert114 (robertreems)]

like Filipe Sousa wrote on 2008-10-17:
I tried InitialPixmapPlacement=2 and I noticed an improvement, but the problem did not go away, it looks like the glitches appear and get fixes itself very fast.

More info about InitialPixmapPlacement can be found here:
http://movingparts.net/2008/10/03/kde-42-trunk-now-rocking-on-my-thinkpad-t61/
It is defenetly not a solution but it might help improving ubuntu!

My system:
Ubuntu 8.04
Latest Nvidia driver (177.80 manually installed)
Geforce 7600 GT

I hope this info is helpfull

Robert

[robert114 (robertreems)]

Crap!!!
It didn't work!

I noticed an improved performance with: nvidia-settings -a InitialPixmapPlacement=2 -a GlyphCache=1 in Firefox and OpenOffice

Robert

[hads (hads)]

After upgrading to Intrepid I've stated seeing this issue (I haven't before). Using an Nvidia 7600GS.

[Dan Andreșan (danyer)]

hads, welcome to the club :(

[Hew (hew)]

Thanks to everyone who has commented on what card they are using. Reports so far are on Geforce 6 and 7 cards only. Can anyone not reproduce the bug on these cards (with -177 or other driver), or can anyone reproduce the bug on a card other than these? If so, please mention the card you have and the driver you are using.

A quick recap since this bug is giant and hard to follow:
Confirmed affected: 6600GT, 7300, GO 7400, GO 7600, 7600GT, 7600GS
Not-affected: 8800, AMD/ATI and Intel
Testing appreciated for: Geforce 6, 8 and 9 with -177, or any card with other drivers (-173, -96, etc)

Thanks again for your help. Triaging for n-g-d-177 since all reports indicate this is where the real bug lies, and there is a lot of relevant info for a dev to look at.

[tankdriver (stoneraider-deactivatedaccount)]

NVIDIA 9500 GT works. (just additional information)

[Martin Soto (soto255)]

I can reproduce it with an old Nvidia 5200 and the 173 driver. This card
isn't even supported by the 177. Unfortunately, I don't have access to
that machine right now, but I can provide the exact lspci output later.

[hal1984 (hal-1984)]

GeForce 6200 with the 173 and 177 drivers also has got the problem.

[Shane O'Connell (shaneoc)]

I see the bug with a Geforce 7900 GS and the 177 driver

[Exile71x (exile71x)]

Geforce 6150 go with the same problem

On Thu, Oct 23, 2008 at 5:52 AM, hal1984 <email address hidden> wrote:
> GeForce 6200 with the 173 and 177 drivers also has got the problem.
>
> --
> Window titlebar displayed not right with compiz enabled
> https://bugs.launchpad.net/bugs/99508
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "compiz" source package in Ubuntu: Triaged
> Status in "human-theme" source package in Ubuntu: Triaged
> Status in "nvidia-graphics-drivers-177" source package in Ubuntu: Triaged
> Status in compiz in Ubuntu Hardy: Invalid
> Status in human-theme in Ubuntu Hardy: Fix Released
> Status in nvidia-graphics-drivers-177 in Ubuntu Hardy: Invalid
>
> Bug description:
> Binary package hint: compiz
>
> When moving the cursor to the window buttons area, sometimes results in the titlebar display being corrupted. This happens with the top panel enabled and when the window is maximized (FIGURE: http://satfilm.net.pl/~gammaray/compiz_bug.png)
>
> The error appeared only with compiz enabled (running it on an nvidia gf6800xt, feisty fawn beta with all available updates)
>
> ProblemType: Bug
> Architecture: i386
> Date: Sat Mar 31 19:27:23 2007
> DistroRelease: Ubuntu 7.04
> Uname: Linux mainframe 2.6.20-13-lowlatency #2 SMP PREEMPT Sun Mar 25 00:23:53 UTC 2007 i686 GNU/Linux
>
> This seems to affect only Geforce 6 and 7 users (Intrepid).
>
> WORKAROUNDS:
> Change the titlebar of the Human theme (eg. to clearlooks)
> -or-
> Disable Compiz
>
> SCREENSHOTS:
> http://launchpadlibrarian.net/13469825/FirefoxTitleBar.png
> http://launchpadlibrarian.net/13147434/Screenshot.png
>
> NOTE:
> Bug 186382 is an unrelated nvidia titlebar issue which looks like these:
> http://launchpadlibrarian.net/12535841/eclipse-titlebars.png
> http://launchpadlibrarian.net/11586392/gwd_drawing_problem.png
>

[Dan Andreșan (danyer)]

If I understood Hew correctly, please post here ONLY IF
either:
1. You have a Geforce 6 or 7 and you *don't* see the bug.
or:
2. You have *another* card then Geforce 6 and 7 and you *see* the bug.

Otherwise you just add redundant information to the bug...

[Hew (hew)]

Thanks Dan. Yes, it's difficult to obtain good information here while keeping bug mail to a minimum on this large bug report.

It really looks like a problem with Geforce 5/6/7 cards only, when using 173 and 177. Thanks again to everyone that provided extra info. No more card info is needed, unless you have something new to report. The bug is triaged, so it's ready for a dev to look into the problem further.

[Ricardo Pérez López (ricardo)]

Why changed from Triaged to Confirmed?

[Chris Coulson (chrisccoulson)]

Ricardo, indeed. zhoufanking - There is no need to change the status to 'Confirmed' when it has already been 'Triaged'. Referring to https://wiki.ubuntu.com/Bugs/Status -

"A member of UbuntuBugControl believes that the report describes a genuine bug in enough detail that a developer could start working on a fix".

And why did you set the nvidia-graphics-drivers-177 task to Invalid? Generally, when changing a bugs status like this it is a good idea to leave a brief note explaining your actions, otherwise other people will have no idea why you did it. Re-opening nvidia-graphics-drivers task, which Hew had triaged 2 days earlier.

[jbg7474 (jbg7474)]

I also have this bug on an Nvidia Quadro NVS 110m video card. I believe this is equivalent to a GeForce 7300, but I'm not perfectly sure, so I thought I'd add the information. I saw this with both Nvidia drivers 173 and 177.

Additionally, just in case it hasn't been mentioned, I also saw this bug when using Metacity with compositing turned on, so it's not exclusive to Compiz.

[Dave Vree (hdave)]

I can confirm this bug on the latest version of Intrepid with the version 177 driver. I have an nVidia GeForce Go 7400.

My reason for posting is that I get this behavior with Human and the Human Clearlooks themes however.

[Dan Andreșan (danyer)]

@jbg7474: nice find! If other people having the bug can turn on the compositing in Metacity and turn off the Desktop effects and still reproduce it we can rule out compiz, and generaliase it to "compositing". AFAIK, you need to edit something in gconf to enable Metacity compositing. Could you add the info here, this will allow more people to test and confirm your findings.

@HDave, you get this with Human Clearlooks as they are based on Human. The community themes (Dust, NewWave, Kin) are based on Human too.

[jbg7474 (jbg7474)]

Here's a link on how to turn on Metacity compositing.
http://hehe2.net/linuxhowto/compositing-with-metacity-another-look/

I should note that it didn't do it right away for me in Metacity, but it did eventually do it.

[Rex de Jong (rex-de-jong)]

I think this bug is affecting me as well. Intrepid, 7600GT.

[rad_sci_guy (radsciguy)]

This bug affects me too. It was happening in hardy and now that i've switched to ibex it's still happening. I have an nVidia 7300 gt pci-express. Was working perfectly until the latest nVidia driver update and kernel update (don't know which caused the problem as the updated around the same time).

[thebigbluecan (thebigbluecan)]

8.10 RC.............. ME too. Nvidia 7800GS AGP with Compiz on... All windows... Firefox, Nautilus, Anything.

[Dan Andreșan (danyer)]

I know that all people here try to help but, please, read at least the last couple of comments before adding your "me too" comment.

The bug is in "triagged" status, which is higher than "confirmed". Until the bug is "confirmed" you can add "me too" comments, after that add info only if not provided already.

https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/99508/comments/212

So, to repeat:
Add new comments only if:
1. You have a Geforce 6 or 7 and you *don't* see the bug.
or:
2. You have *another* card then Geforce 6 and 7 and you *see* the bug.
or
3. if you have *new* information not included in the comments already posted (like the fact jbg7474 discovered that is dependent on compositing, not necessarily on compiz). For this last step, it requires that you read all the above comments (a pain, I know)

Thanks for helping.

[Adam Del Vecchio (tux.ice)]

Would it be possible to detect the card (from the gtkrc or another ace) and if 8.10 detects a geforce 5/6/7 it uses a different, compatable set of icons/ window drawing techniques?

-----Original Message-----
From: Dan Andresan <email address hidden>
Sent: October 28, 2008 5:56 AM
To: <email address hidden>
Subject: [Bug 99508] Re: Titlebar incorrectly drawn with geforce 5/6/7, compiz and human-theme

I know that all people here try to help but, please, read at least the
last couple of comments before adding your "me too" comment.

The bug is in "triagged" status, which is higher than "confirmed". Until
the bug is "confirmed" you can add "me too" comments, after that add
info only if not provided already.

https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/99508/comments/212

So, to repeat:
Add new comments only if:
1. You have a Geforce 6 or 7 and you *don't* see the bug.
or:
2. You have *another* card then Geforce 6 and 7 and you *see* the bug.
or
3. if you have *new* information not included in the comments already posted (like the fact jbg7474 discovered that is dependent on compositing, not necessarily on compiz). For this last step, it requires that you read all the above comments (a pain, I know)

Thanks for helping.

--
Titlebar incorrectly drawn with geforce 5/6/7, compiz and human-theme
https://bugs.launchpad.net/bugs/99508
You received this bug notification because you are a member of Ubuntu
Artwork Team, which is subscribed to human-theme in ubuntu.

[Ferenc Nagy (nxferenc)]

I have Geforce 6100, and I see the bug.
If I hibernate my pc, after wake up I don't see the bug.

[Øyvind Stegard (oyvindstegard)]

I can confirm this problem on a Nvidia GeForce Go 6600 card.

[garnettxd (garnettxd)]

I am giving a possible solution I just found.

Install Ubuntu Tweak, run it from Applications-Systme Tools-Ubuntu Tweak.
Click Desktop in the left panel and chose Window Settings in its sub-panel, then, on the right there are two slide bars, move the slider of the uper one, which stands for "Active window transparency level", to any where but 1.0, then hoover you mouse over the three in up right corner, see what.

I solved the problem in this way, but I don't know if this could work for you all. I'm using a Geforce FX5600 and driver 173.

If this also works for you, I suggest moving the second slider to 0.5 for that looks the best.

[garnettxd (garnettxd)]

I'm sorry, the problem still exist, just not that often.
I was too excited and can't wait to post.

[Datadog (pkutzner)]

This thread: http://www.nvnews.net/vbulletin/showthread.php?t=104822 explains that a regression was introduced after 169.04 into the official nVidia drivers. Essentially, all drivers 169.07 and newer have this problem.

Also, according to this thread: http://www.nvnews.net/vbulletin/showthread.php?t=120829#13
nVidia is aware of the issue, a patch that was a partial fix made it into the release of Intrepid. All "working" work-arounds mentioned in these threads have made it into the final release of Intrepid as well, so it appears.

I'm going to post my AOL! (me too!) comment here as well. Even with the fixes mentioned in these threads, I am still having window border rendering issues and am now unable to downgrade to working nvidia drivers as they're not compatible with the version of xorg shipping in Intrepid.

[billytalent (billytalent)]

This bug affects me too! I just did a fresh install of intrepid ibex. I have an Nvidia Geforce Go 7400 with nvidia 177 drivers installed. So..... compiz folks.. get off your ass and do something!

[xnv (xnvvnx)]

Likewise. Ubuntu 8.10 x86 with nVidia Corporation NV44 [GeForce 6200SE TurboCache (TM)] (rev a1) with 177 drivers and 'Normal' Visual Effects. Screenshot attached.

[Hew (hew)]

Datadog: Thanks for the useful links and info. It's good to see that the issue is known to Nvidia, and to get confirmation that this started with 169.07. I've tried the version from AaronP's PPA though, and it still doesn't fix the problem.

Suraj: The same comment could be made to you. Please be respectful and observe the code of conduct http://www.ubuntu.com/community/conduct/

Again, no more confirmation of this issue is needed (no "me too" comments). Please comment only if you have new information. Thanks.

[Rex de Jong (rex-de-jong)]

The workaround by garnettxd can also be mentioned as a workaround. Although it does not work perfectly for him, it does for me. No glitches at all anymore. Changed "Active window transparency level" to 0,71.

[Rex de Jong (rex-de-jong)]

Using 177 and Interpid BTW

[Dave Vree (hdave)]

The workaround suggested by garnettxd works fairly well for me. Not perfect, but is 80% better...still a great improvement. I get a decent improvement if I set the transparency to 99% even.

[Jos Seldenthuis (jsseldenthuis)]

BTW, another workaround for people who do wish to use the Human/Human-Clearlooks/DarkRoom theme is to simply change the window borders. Regular Clearlooks matches the Human windows borders pretty well and does not have this bug. It doesn't solve the issue of course, but it at least makes it possible to use the standard Ubuntu themes.

[Datadog (pkutzner)]

Jos: I've attempted changing my window borders (or completely changing my theme). It does seem to help a little bit (window border doesn't break while typing a subject in Thunderbird, for example). However, using "focus follows mouse", moving the cursor from one window to another to change focus causes window border corruption.

[Kido (greasedbolt)]

From a comment above, I'd like to point out that Dust isn't based on the Human theme, but the same bug appears using Dust window borders. See this one:

https://bugs.launchpad.net/dusttheme/+bug/273369

[robert114 (robertreems)]

The fix supplied by garnettxd works, thanx1!

with one exception, OpenOffice. I'm not sure weater the bug is the same, it might be an other bug because the disorientation is a little purple and transparent instead of grey. I haven't seen this with an other application.

[Dan Andreșan (danyer)]

robert114, you are right. The pink colors in titlebar is another bug.

[robert114 (robertreems)]

Is there any news on this?

I found this thread wich states the problem only occors with gecko-engine driven application:
http://www.linuxquestions.org/questions/debian-26/compiz-title-bar-weirdness-625532/

Robert

[Hew (hew)]

This has nothing to do with gecko, and everything to do with the proprietary nvidia driver. Please make sure you are talking about the same issue, that is, the grey titlebar bug. The pink titlebar bug is bug 186382. Other problems are other bugs.

I've increased the importance against nvidia-graphics-drivers-177 to medium as this seems to be where the problem lies, and it reflects the number of users impacted.

[mrtwister (mrtwister)]

Same bug here with nvidia quadro NVS 110 and Intrepid Ibex.

[Danny Baumann (dannybaumann)]

Datadog: The issue at hand is _not_ the issue solved by Aaron's patch. It is, however, the same issue as discussed here: http://www.nvnews.net/vbulletin/showthread.php?t=122043.
As one can see, Nvidia acknowleged the problem and is looking into it.

[Timothy Robertson (eltimablo)]

I found that doing nvidia-settings -a InitialPixmapPlacement=0 seemed to solve the problem, until I opened a new window, which caused compiz to crash altogether. I hope this helps somewhat.

[giorni (ricardogg)]

I can confirm this bug on intrepid - geforce go 7300

[Andrea Ratto (andrearatto)]

confirming with nvidia 177.82 (downloaded from nvidia website), geforce 7050, AMD Athlon 64 x2 BE 2350
Also version 169 did not compile...

[Dan Andreșan (danyer)]

giorni, this bug is already triagged, no need to confirm.
andrea, thanks for testing it with 177.82, this is new info.

[robert114 (robertreems)]

177.82 didn't fix it here either!

Nvidia geforce 7600 GT

Unfortunately the release notes are very small!

[Per Heldal (heldal)]

GeForce Go 7600:
 177.82 does not work
 180.06 works - see http://www.nvnews.net/vbulletin/showthread.php?t=123072

[robert114 (robertreems)]

Yes i can confirm it works!

Finally my two biggest problems with Nvidia are solved:
1. A lot of regression problems such as in this thread
2. My PC now suspend

[ArangeL (softwarej)]

Fixed with NVIDIA Driver 180.06!
DV6620es.

[Dan Andreșan (danyer)]

Great!

Could someone remind me the policy regarding the binary drivers in hardy-updates? Do we get version updates, or do we need to wait for Jaunty (or manually install)?

Thanks.

[Dave Vree (hdave)]

Confirmed fixed with nVidia 180.06 beta. It also got rid of my white boxes on AWN... I am SO HAPPY!!!!

Did the manual install via the instructions located here:

https://help.ubuntu.com/community/NvidiaManual

Was a piece of cake...

[Hew (hew)]

This is great news! Thanks Per Heldal for letting us know.

The new binary driver won't be issued as a SRU (a new beta driver is hardly a minimal update, especially due to its closed source nature), so I expect this fix to land in Jaunty. There may be the possibility of a backport for Hardy and Intrepid users, but we need to wait for the driver to appear in Jaunty first. Until then, Hardy and Intrepid users can either continue with the titlebar workarounds, or can do a manual install of the new driver. Remember that this is not recommended or supported by Ubuntu, and additionally, 180.06 is a beta driver.

I'm closing the compiz and human-theme tasks since we now know they are not part of the problem. Thanks again to everyone for their help with this bug, and thanks to Nvidia for the fix :-)

[Scott Wegner (swegner)]

Just want to point out that the new 180.06 driver is set to support a small subset of the NVidia cards which are experiencing this bug. In particular, "GeForce 6xxx and newer NVIDIA GPUs". Users with older cards (i.e. my GeForce FX Go) will need to stick with the 173.14 driver.

So, this beta driver isn't solving everyone's problems, but hopefully the NVidia people can backport whatever they fixed in 180.06 to their legacy drivers.

[Per Heldal (heldal)]

As previously described, 180.06 did sole this problem for me. It is however a beta so don't take that statement as a recommendation for general use. Stability seems somewhat questionable.

However, after 180.06 solved this particular problem for me, but didn't appear stable I decided to try 177.82 again and either drop compiz altogether or use the emerald decorator ... Big surprise, window frames now works with this version too. Stability still wasn't good though, so I opted for another downgrade - to 177.80 - and now the window borders look fine here too with /usr/bin/compiz-decorator.

I'm confused! Back where I started, running the software version that once didn't work, but now it does. The only possibility that I can think of is if there was something missing from the original 177.80 install that has been included with upgrades and not been removed again during downgrade.

[Thor K. H. (nitrolinken)]

Per: Did you do a complete removal of the 180.06 driver or just an overwrite?
Regardless, that seems like an interesting fact. I agree upon the theory that something wasn't removed/overwritten which does make the most sense.

[Malcolm Lalkaka (mlalkaka)]

I'm getting this bug on Intrepid Ibex, using a GeForce FX 5200, and driver version 173, provided by the ubuntu package.

[Timothy Robertson (eltimablo)]

Could it be something to do with nvidia's OpenGL libraries? because that's
all that i can think of that would remain after a reinstall of the driver.

On Sat, Nov 22, 2008 at 4:00 AM, Thor Marius K. Høgås <<email address hidden>
> wrote:

> Per: Did you do a complete removal of the 180.06 driver or just an
> overwrite?
> Regardless, that seems like an interesting fact. I agree upon the theory
> that something wasn't removed/overwritten which does make the most sense.
>
> --
> Titlebar incorrectly drawn with geforce 5/6/7, compiz and human-theme
> https://bugs.launchpad.net/bugs/99508
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "compiz" source package in Ubuntu: Invalid
> Status in "human-theme" source package in Ubuntu: Invalid
> Status in "nvidia-graphics-drivers-177" source package in Ubuntu: Triaged
> Status in compiz in Ubuntu Hardy: Invalid
> Status in human-theme in Ubuntu Hardy: Fix Released
> Status in nvidia-graphics-drivers-177 in Ubuntu Hardy: Invalid
>
> Bug description:
> When compiz and human-theme are being used, the titlebar of windows often
> go completely grey, or partially grey (see screenshots). Moving the cursor
> over the buttons in the top right of the window will trigger the issue on
> affected systems.
>
> This affects all Geforce 5, 6 and 7 users with nvidia-glx-173 or -177. This
> issue appeared as a regression with 169.07, and has been fixed as of 180.06.
>
> More information at
> http://www.nvnews.net/vbulletin/showthread.php?t=104822 and
> http://www.nvnews.net/vbulletin/showthread.php?t=123072 .
>
> WORKAROUNDS:
> Change the titlebar of the Human theme (eg. to clearlooks)
> -or-
> Disable Compiz
> -or-
> Use the 180.06 or greater Nvidia driver
>
> SCREENSHOTS:
> http://launchpadlibrarian.net/19116675/glitch.png
> http://satfilm.net.pl/~gammaray/compiz_bug.png<http://satfilm.net.pl/%7Egammaray/compiz_bug.png>
>
> NOTE:
> Bug 186382 is an unrelated nvidia titlebar issue which looks like these:
> http://launchpadlibrarian.net/12535841/eclipse-titlebars.png
> http://launchpadlibrarian.net/11586392/gwd_drawing_problem.png
>

[Carl-Eric Menzel (duesenklipper)]

I am also getting this on Intrepid with a GeForce 7900 GT/GTO, exactly as described and shown in the screenshots.

Interesting side note, not sure whether this is related to this or warrants a separate bug: I tried the 96 drivers offered by the restricted drivers managers. The titlebar problem was still there, but occured less frequently. But with the 96 driver none of the qt3-based applications that I tried (qt3-setting, but much more importantly Bibble Pro!) worked: They rendered no text. Everything was there, menu entries and all, but instead of text there was simply blank space. Compare http://support.bibblelabs.com/webboard/viewtopic.php?p=56196

[Akdo (menoft)]

Oh thanks GOD, I want report this bug but I 'm happy to see that's already done,
I have same problem since gutsy ...

ii compiz 1:0.7.6-0ubuntu2~ppa1 OpenGL window and compositing manager
ii compiz-core 1:0.7.6-0ubuntu2~ppa1 OpenGL window and compositing manager
ii compiz-fusion-plugins-extra 0.7.6-0ubuntu1~ppa1 Collection of extra plugins from OpenComposi
ii compiz-fusion-plugins-main 0.7.6-0ubuntu1~ppa1 Collection of plugins from OpenCompositing f
ii compiz-gnome 1:0.7.6-0ubuntu2~ppa1 OpenGL window and compositing manager - GNOM
ii compiz-plugins 1:0.7.6-0ubuntu2~ppa1 OpenGL window and compositing manager - plug
ii compizconfig-backend-gconf 0.7.4-0ubuntu1 Settings library for plugins - OpenCompositi
ii compizconfig-settings-manager 0.7.6-0ubuntu1~ppa1 Compiz configuration settings manager
ii libcompizconfig0 0.7.6-0ubuntu1~ppa1 Settings library for plugins - OpenCompositi
ii python-compizconfig 0.7.6-0ubuntu1~ppa1 Compiz configuration system bindings
ii stackswitch 0.0.1-0ubuntu3 compiz plugin implementing "stack switch"-me

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 8.04.1
Release: 8.04
Codename: hardy

Please see screenshot :

[Akdo (menoft)]

Operating System:Linux-x86
NVIDIA Driver Version:177.80

[Andi (nudeldieb)]

Hi,
is it correct that this issue will NOT be solved until the next official release 9.04??

[Hew (hew)]

It is too early to say since 180 is not yet in Jaunty. It won't / can't be included as an update (SRU), but there is a possibility it could be included as a backport.

[Hew (hew)]

nvidia-glx-180 is now in Jaunty, which fixes the problem. Due to the binary nature of nvidia drivers, a fix cannot be provided for -177, so I'm marking it as Won't Fix. Alberto Milone says that 180.08-0ubuntu1 will work on Intrepid, and is planned to be introduced to intrepid-backports.

[Tayroni Alves (tay-fisica)]

Any news about backporting nvidia-glx-180 on intrepid?

[Hew (hew)]

Bug 297543 is used for the 180 upgrade. It is currently In Progress for Intrepid.

[evgen (evgen-alice-dsl)]

i hope there will be a driver update after 177.80 for intrepid, there are broken tittle bars, appeared after updating from 8.04 to 8.10 today; using GeForce 6200... this issue was not present in ubuntu hardy!

wish you people happy new year!

[Christian González (droetker)]

Use the package from ps://launchpad.net/~thomas-creutz/+archive
It workes with my 6600 GT.

[Beto (es-beto)]

oh dear god, how do i get unsubscribed of this bug??, i receive tons of mails and i already found a fix....

[Bruno Santos (bsantos)]

On Sun, 2009-01-04 at 04:56 +0000, Beto wrote:
> oh dear god, how do i get unsubscribed of this bug??, i receive tons of
> mails and i already found a fix....

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

[Beto (es-beto)]

thank you very much I apologize for not being able to see the unsubscribe button I think I scrolled through it too fast to see it...i apologize also for my off-topic posts, it will never happen again.

The nvidia 180.06 driver should be made available in the updates, it fixes the problem and i haven't had any issues after updating (though i don't really know the procedure/testing/inclusion of updates etc)

[ski (skibrianski)]

Just wanted to note that 177.82 (just released in intrepid) doesn't do the trick for me on a Geforce Go 7300 / amd64 system. Has anyone checked the 180.x driver with this card?

ski@ganiodayo:~$ lspci | grep -i nvid
01:00.0 VGA compatible controller: nVidia Corporation G72M [Quadro NVS 110M/GeForce Go 7300] (rev a1)

ski@ganiodayo:~$ dpkg -l | grep nvidi
ii nvidia-173-modaliases 173.14.12-1-0ubuntu4 Modaliases for the NVIDIA binary X.Org drive
ii nvidia-177-kernel-source 177.82-0ubuntu0.1 NVIDIA binary kernel module source
ii nvidia-177-modaliases 177.82-0ubuntu0.1 Modaliases for the NVIDIA binary X.Org drive
ii nvidia-71-modaliases 71.86.04-0ubuntu10 Modaliases for the NVIDIA binary X.Org drive
ii nvidia-96-modaliases 96.43.09-0ubuntu1 Modaliases for the NVIDIA binary X.Org drive
ii nvidia-common 0.2.4 Find obsolete NVIDIA drivers
rc nvidia-glx-173 173.14.12-1-0ubuntu4 NVIDIA binary Xorg driver
ii nvidia-glx-177 177.82-0ubuntu0.1 NVIDIA binary Xorg driver
rc nvidia-glx-96 96.43.09-0ubuntu1 NVIDIA binary Xorg driver
ii nvidia-kernel-common 20051028+1+nmu2ubuntu2 NVIDIA binary kernel module common files
ii nvidia-settings 177.78-0ubuntu2.1 Tool of configuring the NVIDIA graphics driv

Thanks...

[ski (skibrianski)]

PS - The titlebar style workaround works for me tho. Cheers to whomever found that.

[ski (skibrianski)]

PPS - Actually the titlebar style workaround does NOT workaround for me, although it seems to decrease the bugs severity. Sorry for all the noise.

[Dave Vree (hdave)]

@ski -- As mentioned above, the 800.x driver work for me Geforce Go 7400. It'll probably work for you...why not try it out?

[Usufruct (benlong)]

I've been using every nVidia beta driver as they become available. For
me, the titlebar issue disappeared with the 180.06 beta driver, and
does not occur with the 180.17 driver. I recommend you install the
180.17 beta.

-Ben

ski wrote:
> Just wanted to note that 177.82 (just released in intrepid) doesn't do
> the trick for me on a Geforce Go 7300 / amd64 system. Has anyone checked
> the 180.x driver with this card?
>
> ski@ganiodayo:~$ lspci | grep -i nvid
> 01:00.0 VGA compatible controller: nVidia Corporation G72M [Quadro NVS 110M/GeForce Go 7300] (rev a1)
>
> ski@ganiodayo:~$ dpkg -l | grep nvidi
> ii nvidia-173-modaliases 173.14.12-1-0ubuntu4 Modaliases for the NVIDIA binary X.Org drive
> ii nvidia-177-kernel-source 177.82-0ubuntu0.1 NVIDIA binary kernel module source
> ii nvidia-177-modaliases 177.82-0ubuntu0.1 Modaliases for the NVIDIA binary X.Org drive
> ii nvidia-71-modaliases 71.86.04-0ubuntu10 Modaliases for the NVIDIA binary X.Org drive
> ii nvidia-96-modaliases 96.43.09-0ubuntu1 Modaliases for the NVIDIA binary X.Org drive
> ii nvidia-common 0.2.4 Find obsolete NVIDIA drivers
> rc nvidia-glx-173 173.14.12-1-0ubuntu4 NVIDIA binary Xorg driver
> ii nvidia-glx-177 177.82-0ubuntu0.1 NVIDIA binary Xorg driver
> rc nvidia-glx-96 96.43.09-0ubuntu1 NVIDIA binary Xorg driver
> ii nvidia-kernel-common 20051028+1+nmu2ubuntu2 NVIDIA binary kernel module common files
> ii nvidia-settings 177.78-0ubuntu2.1 Tool of configuring the NVIDIA graphics driv
>
> Thanks...
>
>

[evgen (evgen-alice-dsl)]

There is nvidia-glx-180 | 180.11-0ubuntu1~intrepid1 | intrepid-updates/restricted | amd64, i386 available, which fixes the issue with titlebars on GeForce 6200 (at least for me).

It's in intrepid-updates now, which is enabled by default.

[Ricardo Pérez López (ricardo)]

The nvidia-glx-180 package fixes the problem for me (nVidia Corporation G72 [GeForce 7300 LE]).

Great!

[jbg7474 (jbg7474)]

I'm sure it's user error, but I don't see nvidia-glx-180 in the repositories. There was an nvidia update today, but it was only to 177.82. Perhaps because I have a Quadro NVS 110M instead of an actual GeForce?

[Jamie Nadeau (james2432)]

You have to download the drivers yourself: http://nvnews.net/vbulletin/showthread.php?t=122606
1. Save it
2. chmod +x it (terminal)
3. Press ctrl+alt+f1
4. login
5. kill gdm (/etc/init.d/gdm stop) as root
6. run the .run ( ./NVIDIA......)
7. Say Yes to anything it asks you(especially if your are a noob)
8. Restart gdm (/etc/init.d/gdm start) as root
9.You may have to press ctrl+alt+F7 to get back

[jbg7474 (jbg7474)]

Thanks for the link and the instructions, but I'd rather wait until it's in the repositories. Someone above said it's in intrepid-updates, but I don't see it.

[Anand Thakur (athakur)]

I was able to install it from the repositories (Intrepid updates).

The "180" version is part of the package name so you need to explicitly
specify it.

This is what I did. I did this from a text console just to avoid any
possible interactions with the nvidia driver (hit CTRL-ALT-F1 to get to a
text window). Probably not necessary but can't hurt...

1. sudo /etc/init.d/gdm stop
2. sudo apt-get install nvidia-glx-180 nvidia-180-modaliases

The 2nd command will install the new driver and also uninstall the old 177
driver. I'm not sure if "nvidia-180-modaliases" is really necessary (it
doesn't automatically install if you leave it out) but the 177 version is
there so I figured I'd add that in too.

On Thu, Jan 8, 2009 at 11:50 AM, jbg7474 <email address hidden> wrote:

> Thanks for the link and the instructions, but I'd rather wait until it's
> in the repositories. Someone above said it's in intrepid-updates, but I
> don't see it.
>
> --
> Titlebar incorrectly drawn with geforce 5/6/7, compiz and human-theme
> https://bugs.launchpad.net/bugs/99508
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "compiz" source package in Ubuntu: Invalid
> Status in "human-theme" source package in Ubuntu: Invalid
> Status in "nvidia-graphics-drivers-177" source package in Ubuntu: Won't Fix
> Status in compiz in Ubuntu Hardy: Invalid
> Status in human-theme in Ubuntu Hardy: Fix Released
> Status in nvidia-graphics-drivers-177 in Ubuntu Hardy: Invalid
>
> Bug description:
> When compiz and human-theme are being used, the titlebar of windows often
> go completely grey, or partially grey (see screenshots). Moving the cursor
> over the buttons in the top right of the window will trigger the issue on
> affected systems.
>
> This affects all Geforce 5, 6 and 7 users with nvidia-glx-173 or -177. This
> issue appeared as a regression with 169.07, and has been fixed as of 180.06.
>
> More information at
> http://www.nvnews.net/vbulletin/showthread.php?t=104822 and
> http://www.nvnews.net/vbulletin/showthread.php?t=123072 .
>
> WORKAROUNDS:
> Change the titlebar of the Human theme (eg. to clearlooks)
> -or-
> Disable Compiz
> -or-
> Use the 180.06 or greater Nvidia driver
>
> SCREENSHOTS:
> http://launchpadlibrarian.net/19116675/glitch.png
> http://satfilm.net.pl/~gammaray/compiz_bug.png<http://satfilm.net.pl/%7Egammaray/compiz_bug.png>
>
> NOTE:
> Bug 186382 is an unrelated nvidia titlebar issue which looks like these:
> http://launchpadlibrarian.net/12535841/eclipse-titlebars.png
> http://launchpadlibrarian.net/11586392/gwd_drawing_problem.png
>

[Anand Thakur (athakur)]

I was able to install it from the repositories (Intrepid updates).

The "180" version is part of the package name so you need to explicitly specify it.

This is what I did. I did this from a text console just to avoid any possible interactions with the nvidia driver (hit CTRL-ALT-F1 to get to a text window). Probably not necessary but can't hurt...

1. sudo /etc/init.d/gdm stop
2. sudo apt-get install nvidia-glx-180 nvidia-180-modaliases

The 2nd command will install the new driver and also uninstall the old 177 driver. I'm not sure if "nvidia-180-modaliases" is really necessary (it doesn't automatically install if you leave it out) but the 177 version is there so I figured I'd add that in too.

[jbg7474 (jbg7474)]

Yep, that worked. Funny, it's not in Synaptic, even after installation. Lots of other nvidia-glx-XXX, but no 180.

[Giovanni Bajo (giovannibajo)]

I am not receiving it as an automatic update, nor I see it in synaptic. I even run "apt-get update". Any clue why it's not being pushed everywhere automatically?

[Hew (hew)]

nvidia-glx-180 is in intrepid-updates. This is not an automatic update, but a new package. If you wish to use -180 instead of -177, you will need to install the nvidia-glx-180 package.

[Ricardo Pérez López (ricardo)]

Unfortunately, the new nvidia-glx-180 driver reopens the bug #80890 which was closed with nvidia-glx-177 :(.

[Jeffrey Baker (jwbaker)]

Why is this marked fixed on Hardy? I just installed Hardy 8.04.2 x86 and I still see this exact corruption of the title bar with the default theme.

[Hew (hew)]

A workaround was provided in human-theme for Hardy. Please read the comments above which discuss this issue. Make sure you're not seeing bug 186382, or some other titlebar corruption bug.

[Jeffrey Baker (jwbaker)]

I hate to be a stick in the mud, but a workaround buried on Launchpad is not the same as "Fix Released". The workaround isn't even mentioned in the release notes.

[Hew (hew)]

By "workaround" I of course mean a patch was applied to the human-theme package. This occurred with human-theme 0.18, as you will be able to see if you read the above comments. This did fix the issue in Hardy, and many users, including myself, verified this.

If you are experiencing a titlebar issue on Hardy, it is not this bug.

[darkraven (jasminr)]

what workaround??? the only one i have been able to do is DISABLE COMPIZ.
its the only one that works.

this isn't a workaround. where is 180 drivers??? i have 177.

ubuntu doesn't have them available yet, and I'm on intrepid.

[_oOMOo_ (hermann-blaxhall)]

@darkraven

sudo apt-get install nvidia-glx-180

[Jeffrey Baker (jwbaker)]

Hew: On my completely up-to-date fresh install of 8.04.2/x86 with default settings, I see _exactly_ the same titlebar corruption that started this bug. I recommend reopening.

[Jamie Nadeau (james2432)]

@Jeffrey

You have to install the 180 nvidia drivers. Ubuntu team have fix the bug on their end, it's the 17x drivers that were the issue. This has been fixed with the 180 series drivers.

[nitto (nitto)]

I'm quite off-topic in this bug and I apologize in advance.
I'd like to know if anybody experienced any trouble with the new nvidia 180 drivers. They solved this bug but introduced a new bug for me (see Bug #330549).
My laptop is a HP pavilion dv6915nr.
If anybody has a similar laptop and switched to the new nvidia driver version can please contact me privately and tell how the new drivers behave?
Thanks

[Jeffrey Baker (jwbaker)]

@JamesxL

There is no nvidia 180 driver in Hardy.

[Usufruct (benlong)]

Jeffrey,

You can obtain the driver directly from nVidia's site and run the
installer as root from the command line (without xwindows running).

[Jamie Nadeau (james2432)]

I've previously stated on how to install the nvidia 180.x drivers here:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/99508/comments/288

[Jeffrey Baker (jwbaker)]

That's great JamesxL, but I've been using Linux for 14 years and I don't need advice on how to run shell archives. My point here is that the out-of-box experience for users of 8.04 "Long Term Support" is bad. Everybody who installs this thing on Nvidia graphics is going to get the same bad experience. The right thing to do would be to ship is with the Human window borders disabled, and the Clearlooks window borders enabled instead.

Telling people to install out-of-archive kernel modules from websites is not a good solution. Asking people to dig around on Launchpad looking for workarounds is not a good solution, either. 8.04 should work, out of the box, with the default settings as shipped. Right now that's not true. It doesn't matter if it's nvidia's fault.

[Jamie Nadeau (james2432)]

Well 9.04 already has them in the repo. I'd be surprised if they don't release them for LTS and 8.10 also.

[darkraven (jasminr)]

8.10 doesn't have it yet. at least on base install, which is were you see it most often.

Jackalope still shows partially as Ibex, so I never bothered with installing it[fully]. from what I can tell, it DOESn't find it either.

it is IN the repos and DOES install, but you have to dig for the answer. do us all the favor and put a note in the release for 8.10 and re-submit the ISO. shouldn't take but a few minutes to do. building the ISO I mean. compiling always takes a while.

:-)

[Jussi Lind (jussi-lind)]

Jeffrey Baker wrote:
> That's great JamesxL, but I've been using Linux for 14 years and I don't
> need advice on how to run shell archives. My point here is that the
> out-of-box experience for users of 8.04 "Long Term Support" is bad.
> Everybody who installs this thing on Nvidia graphics is going to get the
> same bad experience. The right thing to do would be to ship is with the
> Human window borders disabled, and the Clearlooks window borders enabled
> instead.
>
>
I totally agree. And that would be a relatively easy fix.
Btw, I'd like to know the cause of that bug. It's just sounds crazy that
only a certain _theme_ (not e.g. a 3d-accelerated application) works
incorrectly with nVidia drivers. :)

[Jamie Nadeau (james2432)]

@darkraven

I've installed JJ(9.04) from dailybuild(~5days ago) and it(180.x) does show up in the hardware drivers, then again it might be because I have a x295

[Matt Joiner (anacrolix)]

I couldn't agree more. While Hardy is very stable now, it took a point
release, and a lot of bugs exist purely because packages aren't being
upgraded quickly enough.

On Sat, Feb 21, 2009 at 7:02 AM, Jeffrey Baker <email address hidden> wrote:

> That's great JamesxL, but I've been using Linux for 14 years and I don't
> need advice on how to run shell archives. My point here is that the
> out-of-box experience for users of 8.04 "Long Term Support" is bad.
> Everybody who installs this thing on Nvidia graphics is going to get the
> same bad experience. The right thing to do would be to ship is with the
> Human window borders disabled, and the Clearlooks window borders enabled
> instead.
>
> Telling people to install out-of-archive kernel modules from websites is
> not a good solution. Asking people to dig around on Launchpad looking
> for workarounds is not a good solution, either. 8.04 should work, out
> of the box, with the default settings as shipped. Right now that's not
> true. It doesn't matter if it's nvidia's fault.
>
> --
> Titlebar incorrectly drawn with geforce 5/6/7, compiz and human-theme
> https://bugs.launchpad.net/bugs/99508
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Hew (hew)]

This bug is already very large, and the problem has been fixed for most people. It's possible that your Hardy issue is not the same as this bug, since nobody else has reported seeing it anymore. If you open a new bug for your issue, it would be much appreciated.

Please understand that the nature of proprietary binary drivers does not allow us to simply apply a patch to the driver. The real solution to this bug is to use >=180, or <169. This is already possible in Hardy by using the nvidia-glx package, however as mentioned already, a workaround patch was applied to human-theme to stop Compiz triggering the issue.

Please read https://wiki.ubuntu.com/StableReleaseUpdates to understand that we only fix high-impact bugs in the stable releases with small, unobtrusive patches. This bug is a cosmetic issue that has workarounds and is no longer widely reported on Hardy.

180 is present in Intrepid and Jaunty.

[Matt Joiner (anacrolix)]

LinkedIn
------------

Bug,

I'd like to add you to my professional network on LinkedIn.

- Matthew Joiner

Confirm that you know Matthew Joiner
https://www.linkedin.com/e/isd/856848887/jay-G-ta/

Every day, millions of professionals like Matthew Joiner use LinkedIn to connect with colleagues, find experts, and explore opportunities.

------
(c) 2009, LinkedIn Corporation