[nvidia 169.xx] gtk window decorator somtimes draws decoration ugly or not at all

"very fresh install" instead of "very install" of course ;-)

Thanks for your report. This is almost certainly an issue with the proprietary NVIDIA driver versions 169.07 and 169.09. I can reproduce it in Gutsy with those driver versions, but not others.

I'm seeing it too.

This is also reproducable while using an app such as thunderbird, where changing the window title often causes this issue.

Using Nvidia-glx-new in Hardy

Steps:
1) Open a window to write an email in thunderbird.
2) Change the subject of the email, the window title should change each time a change is made to the subject
3) At some point the window decoration will be corrupted around where the window title should be

I can also report one other case where the window can be drawn incorrectly.

Not every startup, but often the window border is redered wrong, wrong colours and wrong maximise/minimise/close buttons (size at least).

The issue can be fixed by swapping to metacity (metacity --replace &) then swapping back to comiz (compiz --replace &). Then borders are drawn correctly.

referring again to my previous attachment: this is what the border should look like, compiz rendering it correctly after swapping to metacity and then back to compiz's gtk-window-decorator.

referring again to my previous attachment: this is what the border should look like, compiz rendering it correctly after swapping to metacity and then back to compiz's gtk-window-decorator.

mmnz: that's a different issue and a bug in compiz.

I also see this behaviour frequently on Gutsy with the 169.12 NVIDIA drivers, and I've never seen it when running nvidia-glx-new (100.14.19)

See it also very often on Gutsy with the 169.12. On 2 pc's with GF7.

I reinstalled gutsy today and the error appears even with the 100.14.19 (the most recent gutsy nvidia-glx-new). Now, the bar doesn't get orange in firefox/thunderbird etc. but gets grey. (using Geforce 7600GS/AGP)

I also see it on Gutsy 32bit with 100.14.19, same as Peturrr. Using 7800GT 256MB PCI-E.

Peturr, Alex: that is apparently a separate bug. It is filed as bug 99508.

I confirm, just installed Hardy Beta and I have pink shadows while I have #000000 in the Compiz editor. Moreover, in the gconf-editor this value changes to #000000ff (see screenshot attached). Trying to modify any of these values does not fix the problem. I also filed a report on the bug #194851 which seems to be a duplicate of this one.
I am using the nvidia driver automatically downloaded by Hardy upon detection of my nvidia quadro graphic card.

The same problem here with Hardy Beta, Gutsy and Feisty. Here are two screenshots:

http://img237.imageshack.us/img237/2231/compiz1ut6.png

http://img247.imageshack.us/img247/4895/compiz2ow5.png

Cheers
Sascha

Is it possible that this is a Problem between compiz and the window decoration itself? With the Human Theme i get sometimes a very little flare into the title bar chancing a subject in a thunderbird message window but thats all. A Problem between compiz and some gtk-engines?

Cheers
Sascha

OK at the moment i have sent the last message i see the same Problems with the window decoration coming with the Human Theme.

Me too has the problem with the pink shadows around Windows when using Hardy Heron Beta. I hava a Sony Vaio with a nVidia GeForce 8600M GS Graphic Card. When i try to modify the shadow settings all the shadows completely disappear just to reappear after reboot.

I've got an nVidia 8600GT. I have the pink shadows, plus window decorations of inactive windows vanish or get fuzzy.

While the window is inactive, hovering over the title bar and moving the mouse cursor repeatedly into and out of the title bar area (without clicking) can make parts of the title bar reappear, usually in diagonal stripes or in scattered points... When the window regains focus, window decorations on that window get back to normal, although of course the window losing focus becomes inactive and its window decorations vanish in turn...

I hope this gets fixed before final Hardy ship...

I have this problem, too. I have only had experience with it when Emerald is enabled. Here is a thread I started on it: http://ubuntuforums.org/showthread.php?t=671279. When Emerald is not enabled, I get the problem that is described in this thread: http://ubuntuforums.org/showthread.php?t=606276

By the way, I have a 7900 GT/GTO.

I installed fusion-icon and switched the Window Manager over to Metacity and have not seen the problem yet.

Sascha:

I investigated the window decorator aspect of this fairly thoroughly. See duplicate bug 194933. There is some form of corruption for every window decorator (gtk-window-decorator and Emerald engines) and every GTK theme, though with different degrees of severity.

Tristan: OK hope this Problem will be fixed before the Hardy release.

Btw. yesterday i get a *nice* effect next to this problem:

http://img291.imageshack.us/img291/5176/compizzc6.png

Have a good day! :-)

Cheers
Sascha

Same errors on my machine.
Sascha: Even your last described error.

since ubuntu 7.04, 7.10, and even in latest 8.04/amd64
after activating compiz the window-decorations are often destroyed.
NVIDIA GPU GeForce 7300 GS (G72)

Same problem here. NV QUADRO + nvidia-glx-new.

Removing nvidia-glx-new and installing original drivers (with NVIDIA installer) things go OK (until next reboot..), so I guess the problem is "only" with Ubuntu packaging of nvidia new drivers...

Installing original drivers is not a work-around because after rebooting "desktop effect" will be disabled as ubuntu desktop WANTS nvidia-glx-new installed.
Trying to re-enable them triggers the installation of nvidia-glx-new

 ... so I must stick with it!

Pink shadows as well on Hardy Beta up-to-date, 32 bits version, nVidia 8600M GT, nVidia drivers 169.12 from the official Ubuntu repository.

I can confirm that this is a packaging issue. Uninstalling nvidia-glx-new and installing the drivers with the NVIDIA installer and option "--no-kernel-module" fixes the pink shadows. I do not experience the ugly titlebar bug, so I can`t say anything about that. However using the NVIDIA installer also solves bug #184440.

I confirm that I have been able to fix the "pink shadows" issue with the following sequence of actions today:

- update kernel to 2.6.24-14
- uninstall nvidia-glx-new (sudo apt-get remove nvidia-glx-new)
- install NVIDIA installer 169.12 WITH kernel modules (tried first without modules, it does not work)

after this, shadows are now black and consistent.

I think the kernel update was the key, becase I had tried before with the NVIDIA installer with no success.

Thanx marcelo for your hint: That works for me too.
Running Hardy Heron Beta i did as you described and now the shadows are black again and i can configure them via compiz settings. Before they always disappeared after changing one single parameter. So this is definitely an nvidia driver issue.

Greetings Uwe

I can confirm that using nvidia-installer fixed at least the shadows. Can anyone figure out what makes our package fail? I'm trying to do it myself, but an extra pair of hands/eyes won't hurt. I did notice that we didn't have libcuda, but that isn't relevant :) It must be something in the kernel module build (since the libraries are identical)..

Hey guys! Priority of this bug is set to LOW!!! How can It be?
Installing original driver is not a fix anymore for me: it doesn't work.
Also the title should be: decorators ALWAYS paints glitches.

Yesterday i install ubunut 8.04 Beta on a PC with nvidia nforce chipset, AM2 Socket, a AMD Athlon 64 X2 Dual Core Processor 3800+ and a GeForce 8400GS with 256 MB. After the installation it was a hard work to get the xserver run without a black screen. After this and when the nvidia-drivers are running i get with activated compiz ping shadows too. Btw. Ubuntu means my graphic card is a GeForce 6150SE nForce 430 with 512 MB.

Cheers
Sascha

PS. The picture in the attachment shows the ping shadow on a white desktop background.

I removed the nvidia-glx-new package, then downloaded the newly released (beta) driver from nvidia.com (released april 10th). After running the installation script, I now have black shadows, and they are consistent :)
yay :)

Unfortunately, this driver is not yet marked as stable, but it fixes the issue for me. Based on this, I suggest that it is either a driver issue related to the driver version in ubuntus repo, or something related to the specific ubuntu package of this driver. However, I never got around to test running the nvidia installer with the latest stable driver, so ...

What beta version? 169.09 and 169.12 are both fine for me.

This issue is not only an Ubuntu one, as it also happens on Arch (http://bbs.archlinux.org/viewtopic.php?id=41869) and I solved the problem almost the same way I did with Ubuntu.

This one:
http://www.nvidia.com/object/linux_display_ia32_173.08.html

How do I install the nvidia display driver please? I currently have

NVIDIA-Linux-x86-173.08-pkg1.run

sitting on my desktop.

Please keep support questions to the forums and support tracker.

A fresh install of the Hardy Heron release candidate with all updates shows pink shadows for me with appearance set to normal.

My video card is an 8800gt and I'm using the restricted driver.

Same here. Fresh installation of Ubuntu 8.04 RC, nvidia driver package (nvidia-glx-new)

Have a look at the screenshot.

I can confirm this bug:
Fresh Hardy, 2.6.24-16-generic,
GeForce 8500 GT (rev a1)
Nivida 173.08 (beta)
compiz 1:0.7.4-0ubuntu5
In case I go to the compiz-setting manager and I select a new theme. after going back to the old theme the shadow dissapears.

Hi,

today I switched to official nvidia drivers 173.08 (because of random X freezes). After logging into gnome, I get the errors described here. My guess is the human-theme. I have chosen that one and then customized it to use the clearlooks window borders. So it looks like the human theme. No more flickering.

So is the human-theme broken (at least for nvidia users)?

Nope, this bug is down to the NVIDIA driver. Bug 99508 (which is another issue, affecting only maximized windows) has a workaround which involves modifying a value in the Metacity theme.

I experienced with new nvidia drivers, that when running nvidia-settings you shouldn't set it to a value beyond "Performance".
(nvidia-settings > OpenGL settings > Image settings) Or try "Quality". Maybe this could help out with the wrong shadow colors.

For me since some updates, xserver crashes completely with compiz.

I have a 32 bit Hardy installation on a GF8800GT. No shadows for me.

Same problem here. Hardy final and Nvidia NVS140. Either pink shadow or no shadow at all (at the beginning of the dev cycle, i though it was a feature of the new theme :)

8600 GT on Hardy here aswell. No Shadows too. I'd be really happy if someone could put the newest Nvidia-Driver to the Repository. :/
As the fixing is not really hard but a lot of People are affected, this really should be fixed soon. I wouldn't want to recommend Hardy to someone transferring from Windows to Ubuntu. It's just very bad Publicity if Ubuntu is borked right from the first view.
Low Importance doesn't really meet the significance of this Bug.

Who says fixing this is not hard? It has nothing to do with the version of the driver, it is something our packaging is doing to the driver that makes it malfunction. Updating to the latest (beta) driver wouldn't make any difference, the key thing is you installed it yourself.

Just a me-too on the not seeing any shadows at all - not even pink ones. 64-bit hardy, 8600GT. Gotta wonder why this bug, which was reported in January, wasn't fixed before release, especially when compiz is the default when drivers support it now and nvidia cards are (afaik) the only cards that can do a composited desktop with xv and GL compositing working correctly...

+1. If this is a packaging issue, it really should be fixed.

I also have pink artifacts in the bottom right corner of my screen - I don't know if this is related. See attachment.

Oh, on, the artifacts of the last post were my fault. I had tried to temporarily disable the shadows, but put the x- and y- offset sliders fully negative instead of zero. The pink artifacts appearing above and to the left of windows were in fact shadows.

the fix provided in
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/194851/comments/37
works fine for me

For me No shadows at all!! (Ubuntu Hardy, 64 bit version, nvidia 8600gt)

@Yofel
How did you exactly do? and what was your problem?pink shadows or no shadows at all??

I can confirm that redirecting that sym link does fix the shadows. Whether it's a real fix or not I don't know. Interesting enough it also fixes bug #212648

Confirming!!! :D

https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/194851/comments/37
works fine for me too.

Hardy 64bit, Nvidia GeForce 8500 GT, shadows are black and back (had no shadow previously).

Can we expect official fix soon?

@neubauten84:
i redirected the link like explained in the other post.
And I had broken window decorations and pink shadows.

Works here too! :-) Hardy 32bit, Nvidia GeForce 8400GS. Shadows are black :-)

Cheers
Sascha

Perhaps this fixes it?

"sudo ln -sf /usr/lib/nvidia/libwfb.so.xserver-xorg-core /usr/lib/xorg/modules/libwfb.so"

If you are using nvidia 173.08, you can download a fixed libnvidia-wfb.so.173.08 from

http://people.freedesktop.org/~aplattner/wfb/Linux-x86/libnvidia-wfb.so.173.08

and replace /usr/lib/xorg/modules/libnvidia-wfb.so.173.08 with this version.

lrwxrwxrwx 1 root root 23 2008-04-22 10:29 libnvidia-wfb.so.1 -> libnvidia-wfb.so.173.08*
-rwxr-xr-x 1 root root 270552 2008-04-26 20:09 libnvidia-wfb.so.173.08*

lrwxrwxrwx 1 root root 18 2008-04-26 20:24 libwfb.so -> libnvidia-wfb.so.1*
-rw-r--r-- 1 root root 197363 2008-04-15 19:41 libwfb.so-dist

That works for me.

[quote]Perhaps this fixes it?

"sudo ln -sf /usr/lib/nvidia/libwfb.so.xserver-xorg-core /usr/lib/xorg/modules/libwfb.so"[/quote]
Yeeeeeeeeesss!!!It work ro meeeeeee!!!
Great!

I never had broken shadows, just title bar corruption, and it seems that the symlink fix has NOT made that go away. I just now saw corruption in the title bar of Eclipse.

Be aware that my fix is only a workaround because the libnvidia-wfb.so shipped with nvidia-glx-* have to work in the following version, so if anything is done by nvidia to fix their libnvidia-wfb.so the bug will certainly reappear by a next nvidia-glx-* apt update.

Hi,

I'm not sure what this means, but I had the same problem (pink shadows with an 8600M GT) and it was solved simply once I installed the package xserver-xgl (which wasn't installed).

sudo apt-get install xserver-xgl

Thanks Cedric,

"sudo apt-get install xserver-xgl" worked flawlessly for me.

Downgrading to Nvidia driver release 169.04 fixed this problem for me. I was not experiencing this problem under Gutsy, but only started experiencing it under Hardy. I'm pretty confident that it's an Nvidia driver issue if downgrading from 169.12 (Ubuntu's version) to 169.04 (Nvidia's version) fixed the problem.

As I mentioned previously, even if this workaround seems to work, we have to keep in minds that it's only a workaround, so turning the version of the wfb module is a bad thing and may probably affect others functionalities and making bugs appears... so, personally I think that if the punk shadows don't disturb you other way, keep your punk shadows and wait a new release of nvidia-glx-** that embed a fixed version of libnvidia-fwb.so...

Datadog: As Travis has already pointed out above - this is a packaging issue with the Ubuntu drivers. Therefore, it isn't downgrading from 169.12 to 169.04 which has fixed it for you. It is fixed because you've installed the version direct from NVIDIA as opposed to an Ubuntu packaged version. It would also probably work if you installed 169.12 direct from NVIDIA.

The 'fix' detailed at https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/194851/comments/37 works for me also. Don't know if there are any unwanted side-effects of doing this yet, though... It does highlight that the way libwfb.so is redirected by nvidia-glx is a bit irritating, there's no way of diverting that file without forcibly overwriting files, at least not that I could figure out. If multiple packages can provide this file, shouldn't it be handled by update-alternatives?

I can confirm pink shadows. I have nvidia-glx-new installed, which was handled by 8.04 automatically (which I just recently installed as a fresh install). Before this I was running 7.10 using drivers direct from nvidia using the nvidia installer. Expectedly for my 7.10 install the shadows were working correctly.

My card is a 8600 GT.

Fix confirmed to work on my Vostro 1400.

Will the package be updated?

Sorry, my full question is: will an eventual official fix for this package break the system of people who already did the fix manually?

Is this really a problem with Compiz or Nvidia drivers? I switched my window decorator from metacity to emerald and that seems to fixed this issue. Here is a link to an optimization bug with Metacity which may or may not be part of the problem: http://bugzilla.gnome.org/show_bug.cgi?id=478886

@alphamerk: That's a completely different issue - That issue is metacity drawing window borders incorrectly; in this bug, metacity isn't even running. There is a fix in comment #37 that seems to work for all users, which indicates this is a driver error, or a driver packaging error. An updated nvidia driver is likely to fix this issue, as would altering the packaging.

And just to add, this is shadows drawing incorrectly, not window borders - I'm pretty sure that compiz doesn't rely on any metacity/libwnck code to draw shadows...

Actually, my bad, I see the original bug report was about window borders, but the shadow bug has been set as a duplicate of this... Probably two unrelated bugs, you may well be right for the other one... Good luck on getting anyone to agree to file this as two separate bugs though :) (and apologies for not checking my facts thoroughly enough) - will stop comment spam now.

@Chris Lord: I would agree that the link I posted is not related, however I do not agree that "metacity isn't even running" (as you are not the submitter of the bug). Compiz-decorator by default uses metacity unless you explicitly tell it otherwise. If you are effected by the 'pink title bar' or otherwise distorted title bars while running Compiz (ie advanced effects) then I am willing to bet emerald will fix this issue in the interim until updated packages are released.

Well, gtk-window-decorator is running, metacity certainly isn't... That's even in the bug title - but perhaps gtk-window-decorator relies on libmetacity to draw decorations. Either way, digressing, sorry for my earlier unnecessary spam again (and this spam too :))

Nevermind, I am an idiot, gtk-window-decorator is the default, not metacity.

Chris Coulson: The fix mentioned here (changing the libwfb.so link) didn't work for me. I still was experiencing the same disappearing (or other wonky-ness) window-borders after changing that link with the restricted drivers. I had read in some other places that some people have experienced this problem since 169.04 and that that version was the last known "good" version that nobody experienced this problem with. I believe I read this on the Compiz / Compiz Fusion forums. It's been a known issue with them for a while and it affects distros other than Ubuntu. IIRC the Compiz team points the finger at Nvidia on this one.

But, it is odd that it worked fine in Gutsy (using the restricted drivers) then it ceased to work in Hardy, even after this "fix".

I can confirm this fix didn't work for me either, just like Datadog recently said.

I'm using Ubuntu Hardy "final" for AMD64, a Nvidia 6600 board, with Nvidia drivers from the Ubuntu repository. Moreover, I changed the window decoration to Emerald, and I'm still experiencing the same "wonky-ness" or 0% opacity (full transparency), so I think the responsible could be the Nvidia drivers.

Installing xserver-xgl package fully fixes the shadows bug.
Additionally, glxgears shows twice better performance, boosting fps from 7k up to 14k. CPU usage goes down as well, making the whole UI work noticeably faster.

My PC: Asus G1S (8600M GT) + Hardy (8.04) final.

One for all: installing xserver-xgl package IS NOT A FIX. Because it DOES NOT USE nvidia-glx-new. For example : try to run nvidia-settings after installing xserver-xgl.

Or am I missing something ?

That is correct, xserver-xgl uses the Mesa OpenGL drivers, and doesn't use
your nvidia drivers. Again, this seems to point in the direction that
NVidia's drivers are at fault for this problem.

On Mon, May 5, 2008 at 9:58 AM, Vittorio Ballestra <
<email address hidden>> wrote:

> One for all: installing xserver-xgl package IS NOT A FIX. Because it
> DOES NOT USE nvidia-glx-new. For example : try to run nvidia-settings
> after installing xserver-xgl.
>
> Or am I missing something ?
>
> --
> [nvidia 169.xx] gtk window decorator somtimes draws decoration ugly or not
> at all
> https://bugs.launchpad.net/bugs/186382
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Preston

No you don't miss something :-)
You are right, installing xserver-xgl is NOT a FIX.

My problem was that I had no shadows. (hardy 64-bit, Geforce 8600 GT)
I installed the official driver manually and my shadows were back, so it is a problem of the ubuntu package, I think.

I would NOT recommend people to install xserver-xgl!!!

best wishes
Achim

I installed "xserver-xgl" and now I get twice performance in "glxgears", why is this?

Though, it doesnt use the keyboard layout I had before...

XGL is an X Server project implementation (like Xorg,XFree86) and actually, there are two Xgl forks : XglX and Xegl... when whe do "sudo apt-get install xserver-xgl" : we install XglX that still relies on Xorg ... (and so still use X nvidia module)... XglX catch all 2D and 3D operations of the X protocol to a glitz wrapper that use OpenGL (and 3D hardware acceleration) for 2D and 3D rendering too(contrary to Xorg that event if nvidia driver are installed, it uses 2D Hardware Acceleration for 2D Drawing and 3D Hard. acc for 3D drawing, but today, via openGL, we can use 3D Hard.Acc even for 2D drawing that is more efficient)...
To speak basically the concept of XGL is good and bring better performances, but XglX is only a draft, the "true XGL" will be Xegl that will have no more dependency with Xorg....
All that to say :
1/ using "Xgl is not a bad thing"
2/ Xgl continue to use the embedded nvidia GL library (and the famous libwfb.so), but the container (The X server implementation) that load the wfb module is slightly different and that's why everything goes well with shadows under XGL. (to convince, you can scan your Xorg.0.log and you will see that's the nvidia libwfb.so is still loaded)...

For the keyboard layout try to add in Xorg.conf (at the "input device" section):
Option "XkbLayout" "fr" (change "fr" to other thing if you're not french)

I Think that's the pink shadow problem comes from the fact that the libwfb.so has been compiled for a bad version of Xorg (7.199) instead of the 7.3, only (seeing your Xorg.0.log never lie..).

Confirming that https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/194851/comments/37 solution works. Hope that a patch will be packaged soon.

I think the solution is really really simple. Just remove diversion from libwfb from the package and everything should just work. I'd make the patch myself if it were useful but I'm not the package maintainer.

check bug 212648, the fix is on it's way to hardy-proposed.

Accepted into hardy-proposed, please test and give feedback here.

I've just installed nvidia-glx-new 169.12+2.6.24.12-17.35 and linux-restricted-modules-2.6.24-17-generic 2.6.24.12-17.35, and I still see pink shadows. Do these packages contain the proposed fix?

Brendan Cully [2008-05-07 16:02 -0000]:
> I've just installed nvidia-glx-new 169.12+2.6.24.12-17.35 and linux-
> restricted-modules-2.6.24-17-generic 2.6.24.12-17.35, and I still see
> pink shadows. Do these packages contain the proposed fix?

No, you need -17.36. It should become available soon.

Confirming that the driver from Hardy Proposed fixed the problem. Shadows are back to the normal black and the incorrect drawing of the gtk-window-decorator on unfocused windows does not happen anymore.

GeForce 8400M GS

:~$ apt-cache policy nvidia-glx-new
nvidia-glx-new:
  Installed: 169.12+2.6.24.12-17.36
  Candidate: 169.12+2.6.24.12-17.36
  Version table:
 *** 169.12+2.6.24.12-17.36 0
        500 http://us.archive.ubuntu.com hardy-proposed/restricted Packages
        100 /var/lib/dpkg/status
     169.12+2.6.24.12-16.34 0
        500 http://us.archive.ubuntu.com hardy/restricted Packages

Works very well here, Hardy, 8600 GS, 64-bit. Thanks! (Feels faster too)

I have a 8600GT and have installed nvidia-glx-new 169.12+2.6.24.12-17.36 and linux-restricted-modules-2.6.24-17-generic 2.6.24.12-17.36. I also have:

  -rw-r--r-- 1 root root 270552 2008-04-26 11:53 libnvidia-wfb.so.173.08
  lrwxrwxrwx 1 root root 23 2008-05-10 15:06 libnvidia-wfb.so.1 -> libnvidia-wfb.so.173.08
  lrwxrwxrwx 1 root root 23 2008-05-10 14:57 libwfb.so -> libnvidia-wfb.so.173.08

But I still get those pink/yellow borders and corrupted window decorations. Any ideas?

markb: You have the libwfb.so link, which breaks the shadows etc. You've installed the beta driver by hand?

I installed the packages from hardy-proposed using aptitude but because I had set up the libwfb.so link manually I don't think the packages corrected it? Anyhow, I set them by hand as above. Note that I have no /usr/lib/nvidia/libwfb* files at all (I did not touch anything in that dir), so surely I need to create/link libwfb.so somewhere? You mean just delete that file/link and all will be ok?

that's not enough, since you've done things by hand. After removing the link you need to reinstall xserver-xorg-core to get the real libwfb.so from that package.

Yes, in the time I was waiting for your 2nd reply I worked that out for myself. The problem is fixed now. Many thanks for your help.

Just a "me too", to subscribe to this bug. I've this problem too on two amd64 machines. For whatever reason on one machine the problem is much worse on my desktop (GeForce 8600 GT) than my laptop (which has a G72M [Quadro NVS 110M/GeForce Go 7300]) but is annoying on both.

I tried using the following command:

"sudo ln -sf /usr/lib/nvidia/libwfb.so.xserver-xorg-core /usr/lib/xorg/modules/libwfb.so"

and it did not work.

I then tried a sudo apt-get install xserver-xorg-core

and it gave me this:

xserver-xorg-core is already the newest version.

can someone guide me through this process? this bug is very annoying. thanks!

You need to logout and back in after the "sudo ln" command for it to take effect.

Guys, I think something must be done here to make the availability of a fix in hardy-proposed more evident. As you can see by the posts immediately above, people are still trying to do the manual symlink fix or even trying to install XGL instead of downloading the package and giving feedback.

The fix in Hardy Proposed will filter down to Updates when it's tested
enough. :)

Can somebody make step by step explanation for a newbee:

I did that ln command and it fixed my 'no shadows at all issue'. I don't have hardy proposed enabled. It is enough to enable it or I must delete link first? Thanks, I do want to test this :)

I recommend deleting the link first, confirm that the problem returns, and only then download the fixed package. That way you can be sure that what fixed the issue was the new package version and not something you did manually.

Ok, I removed new symlink and returned old one from my backup so now I have windows without any shadows again.

I do have envyng installed. Do I need to remove it first or this patch works for for hardy with or without envyng? I am not sure about this but would like to perform a correct test. Thanks.

Dusan: can you post the result of this command (please put it on pastebin so that it doesn't take up too much space)?
sudo aptitude search nvidia

Sure, no problem.

Dusan: envyng (at least the one in the stable repository) installs Ubuntu's default restricted modules therefore, in order to the test the new driver you can follow these steps:

1) enable the -proposed repository and upgrade the restricted modules

2) Type:
sudo apt-get remove nvidia-glx-new

sudo apt-get install --reinstall xserver-xorg-core

3) install the new driver from -proposed:
sudo apt-get install nvidia-glx-new

The fix in hardy-proposed works for me, thanks.

Alberto, I followed your instructions but nothing happened, still without shadows. Please see attachment, I hope it will help.

Thanks.

how do I remove the link that I created before so I can try downloading the proposed-package?

Tom, does "sudo rm /usr/lib/xorg/modules/libwfb.so" work? If I remember correctly (but I'm not sure if I do), there was no /usr/lib/xorg/modules/libwfb.so before you created the link, so it should be safe to simply rm it.

Thanks Sympy. That worked. However when I followed the instructions to re-download the drivers, etc. from the propsed repositories, it did not seem to work. I'm still getting the annoying pink clear titlebars. Any suggestions?

hmmm I just noticed when I hit ESC at Grub there's now 2 different kernel versions...why would this be? Basically what I did was install updates after I enabled the proposed repositories

yeah on second look, I have both of these installed:

linux-image-2.6.24-17-generic
linux-image-2.6.24-16-generic

should I uninstall one?

Looking at my backup, THERE WAS previous libwfb.so symbolic link pointing to 'libnvidia-wfb.so.169.12'. I am not sure if this can be simply deleted.

I removed new symbolic link, restored old one, followed Alberto's advices but I still don't have no shadows at all.

I am working on 64bit Hardy and kernel is still -16 on 64 bit. Is this related to why new fix does not work here?

Tom, try booting in both kernels and see if the problem is fixed in one of them. Since the nvidia module is compiled for a specific kernel, it's expect that the problem will NOT be fixed on one of them.

Sympy, you're right! It *seems* to be fixed in linux-image-2.6.24-16-generic. I was loading the newly-installed "linux-image-2.6.24-17-generic" (i'm assuming this was installed with the proposed updates). what's the safest way to remove this?

also, should I keep updating proposed updates in the Update Manager?

thanks!

ugh...I spoke too soon...it's still happening. scratch my last post

It's recommended to install from hardy-proposed only the updates you want to test.

Tom, try to restore the original libwfb.so like Dusan mentioned, I think I gave you a wrong advice up there due to my old and poor memory.

how can I restore?

According to what Dusan said, it originally pointed to libnvidia-wfb.so.169.12.

I'd guess this is the /usr/lib/xorg/modules/libnvidia-wfb.so.169.12 provided in the nvidia-glx-new package.

okay I did this to restore:

thomass@linux-thomass:/usr/lib/xorg/modules$ sudo cp libnvidia-wfb.so.169.12 libwfb.so

was that the correct way to go about it?

also, I still dont' know what to do about having 2 kernel's now...should I uninstall one from Synaptic?

thanks for all the help thus far

Tom: please follow the instructions:

1) Uninstall the nvidia driver

2) Remove the wrong wfb.so:
sudo rm /usr/lib/xorg/modules/libwfb.so

3) Reinstall xserver-xorg-core (so as to restore the original libwfb.so):
sudo apt-get install --reinstall xserver-xorg-core

4) Install the nvidia driver from -proposed

l-r-m-envy moved to hardy-updates and intrepid, see bug 221304.

The package in -proposed fixed the problem for me, too. Thanks!

I have installed the proposed nvidia-glx-new package because my Thunderbird gave corrupted titles/window decorations when typing in the subject area when writing a new email, however, the new driver did not resolve this issue. I have no problems with shadows, never had these problems (I understand that this thread is about both shadows and window decorations).

I have not removed any libwfb.so links/files but as far as I understand this is only a fix for the shadows bug?

linux-restricted-modules 2.6.24-17.36 copied to hardy-updates.

I'm still experiencing broken window borders with this update. I have never
experienced the pink (or missing) drop-shadows, but I have experienced (and
still continue to experience) the incorrectly drawn window-borders. I still
maintain that the pink/missing shadows and the incorrectly drawn window
borders are two separate bugs, and the latter of the two is still not fixed.

On Mon, May 26, 2008 at 4:18 AM, Martin Pitt <email address hidden> wrote:

> linux-restricted-modules 2.6.24-17.36 copied to hardy-updates.
>
> ** Changed in: linux-restricted-modules-2.6.24 (Ubuntu Hardy)
> Status: Fix Committed => Fix Released
>
> --
> [nvidia 169.xx] gtk window decorator somtimes draws decoration ugly or not
> at all
> https://bugs.launchpad.net/bugs/186382
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Preston

Just a follow-up. Installing the 'xserver-xgl' package solved the window
border problem for me. I don't see this as a 'solution' to the issue, as
this issue didn't present itself when I was running Gutsy and I was not
running xserver-xgl before today. However, this 'solution' has presented
another problem. Running glxgears now crashes X for me, with the following
error in /var/log/messages:

May 27 11:25:19 usagi kernel: [ 254.600717] Xgl[7547]: segfault at 00000cf8
eip b7a97b0a esp bf8ed700 error 4

On Tue, May 27, 2008 at 10:47 AM, Preston Kutzner <email address hidden>
wrote:

> I'm still experiencing broken window borders with this update. I have
> never experienced the pink (or missing) drop-shadows, but I have experienced
> (and still continue to experience) the incorrectly drawn window-borders. I
> still maintain that the pink/missing shadows and the incorrectly drawn
> window borders are two separate bugs, and the latter of the two is still not
> fixed.
>
>
> On Mon, May 26, 2008 at 4:18 AM, Martin Pitt <email address hidden>
> wrote:
>
>> linux-restricted-modules 2.6.24-17.36 copied to hardy-updates.
>>
>> ** Changed in: linux-restricted-modules-2.6.24 (Ubuntu Hardy)
>> Status: Fix Committed => Fix Released
>>
>> --
>> [nvidia 169.xx] gtk window decorator somtimes draws decoration ugly or not
>> at all
>> https://bugs.launchpad.net/bugs/186382
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>
>
>
> --
> Preston

--
Preston

I've unduped the bug with broken window borders, see bug 191783.

This is still happening to me and it's getting VERY annoying. Is there an official fix yet? Can someone please help me?

Why is this marked fixed in hardy? I just upgraded from gutsy and I'm seeing this error now in hardy (I didn't see it in gutsy)

I've tried both versions of "libwfb.so" that I have in /usr/lib/xorg/modules and both still exhibit the pink window titles:

$ ll lib*wfb*
libnvidia-wfb.so.1 -> libnvidia-wfb.so.169.12
libnvidia-wfb.so.169.12
libshadowfb.so
libwfb.so -> libnvidia-wfb.so.1
libwfb.so.orig

--> Doesn't work

$ ll lib*wfb*
libnvidia-wfb.so.1 -> libnvidia-wfb.so.169.12
libnvidia-wfb.so.169.12
libwfb.so -> libwfb.so.orig
libwfb.so.orig

--> Still doesn't work

I am using nvidia-glx-new with a GeForce 7300 GS

$ sudo dpkg -l | grep nvidia
rc nvidia-glx 1:96.43.05+2.6.24.13-19.42 NVIDIA binary XFree86 4.x/X.Org driver
ii nvidia-glx-new 169.12+2.6.24.13-19.42 NVIDIA binary XFree86 4.x/X.Org 'new' driver
ii nvidia-kernel-common 20051028+1ubuntu8 NVIDIA binary kernel module common files
ii nvidia-settings 1.0+20080304-0ubuntu1.1 Tool of configuring the NVIDIA graphics driv

Since this bug seems to have been addressed, what exactly do I need to do to get the pink titlebars to go away?

Just installed the new NVIDIA 173.14.09 driver and I'm *still* seeting this problem.

Tried using both the X.org libwfb.so and libnvidia-wfb.so.173.14.09 -- same problem with both.

Behavior is very frequent. Screenshots attached. Any suggestions as to what I can do to fix this or workaround the bug?

I can confirm this bug for Hardy 8.04.1with nVidia 7600 and nvidia-glx-new.
I have not seen this problem before I got latest automatic updates on 8.04.1.
Never had this problem with 8.04.

sirianni:
1) uninstall the driver from the NVIDIA installer (i.e. stop the Xserver and sh name_of_the_installer --uninstall)
2) remove nvidia-glx-new
3) enable hardy-updates, universe and multiverse repositories, refresh the list of packages and type:
sudo apt-get install envyng-gtk
4) finally launch EnvyNG from Applications/System tools EnvyNG and install the NVIDIA driver from there.

Let me know how it goes.

rhersel:
can you post the output of this command?
ls -l /usr/lib/xorg/modules/*wfb*

Alberto - thanks for your reply.

I assume that EnvyNG will install a version of the NVIDIA driver > 169.04 ?

I don't think the newer NVIDIA drivers fix the issue I'm seeing. In fact, the only way I got the garbled/pink window borders to go away was to *downgrade* to NVIDIA driver 169.04. Please see the comments in bug 191783 and confirm that you still think that using EnvyNG to install the NVIDIA driver will fix my problem. Thanks.

Two comments:

- First, this is not ubuntu (or even linux) specific. I have the exact same problem when I boot opensolaris 2008.05 / snv_86 (which uses nvidia driver version 173.14.09) on my machine that has a Quadro NVS 110M/GeForce Go 7300.
- Second, there was a similar, but much more persistent and severe problem with other cards (in my case a GeForce 8600 GT), which involved the decorations not being there at all (except on one window, IIRC). Upgrading to the latest hardy updates *does* fix this particular problem, but not the corrupted title bar issue.

Hi Alberto

here is the output:

ralf@ralf-laptop:~$ ls -l /usr/lib/xorg/modules/*wfb*
lrwxrwxrwx 1 root root 23 2008-07-04
18:44 /usr/lib/xorg/modules/libnvidia-wfb.so.1 ->
libnvidia-wfb.so.169.12
-rw-r--r-- 1 root root 275292 2008-06-27
02:30 /usr/lib/xorg/modules/libnvidia-wfb.so.169.12
-rw-r--r-- 1 root root 25941 2008-06-13
03:22 /usr/lib/xorg/modules/libshadowfb.so
-rw-r--r-- 1 root root 197363 2008-06-13
03:22 /usr/lib/xorg/modules/libwfb.so

Regards
Ralf

Am Mittwoch, den 09.07.2008, 08:55 +0000 schrieb Alberto Milone:
> sirianni:
> 1) uninstall the driver from the NVIDIA installer (i.e. stop the Xserver and sh name_of_the_installer --uninstall)
> 2) remove nvidia-glx-new
> 3) enable hardy-updates, universe and multiverse repositories, refresh the list of packages and type:
> sudo apt-get install envyng-gtk
> 4) finally launch EnvyNG from Applications/System tools EnvyNG and install the NVIDIA driver from there.
>
> Let me know how it goes.
>
> rhersel:
> can you post the output of this command?
> ls -l /usr/lib/xorg/modules/*wfb*
>

sirianni,ski: there are 2 separate issues. Yours must be a bug of driver. I can only suggest you to report the problem on NVIDIA's forums:
http://www.nvnews.net/vbulletin/forumdisplay.php?f=14

rhersel:
can you try what I suggested in comment 139? If it doesn't solve the problem, then see what I suggested to sirianni and ski.

Same problem on 8.04.1 64-bit
default SW configuration, compiz enabled.

nvidia-glx-new, Nvidia Go 7600

(This bug is older than 6 Month! Why not fixed yet?)

Because nVidia doesn't care. Please get Intel or ATI hardware next time. :)

I can confirm this bug also. Most of the time it happens on OpenOffice.org application and Eclipse.
Using Nvidia GeForce 6600 AGP with modified bios.
Picture attached.

Skwo -

The screenshot you've uploaded is the nvidia corruption bug, not the "no decoration bug" and we're still waiting on nvidia for a fix to that.

The easiest workaround is to use a window list in your gnome panel, and click the window twice to minimize and un-minimize the window, which has solved the problem for me every time.

Another thing I've noticed is that if you change your desktop color, you get different artifacts in the titlebar, which may or may not make things more usable. I only mention that because it looks like you have a dark brown artifact which makes the buttons very hard to see. My blue background with yellow highlights gives me very visible minimize, maximize, and close buttons, so that's another thing to try if you absolutely hate the idea of having a window list in your panel. Good luck!

PS - I like your nick! :-)

Hi,

I'm currently on Intrepid i386 w/the 177.70 drivers, and I also experience this issue while using compiz. The only way I have been able to eliminate the problem was to:

a) Add the following to the "Device" section of your xorg.conf:

Option "BackingStore" "false"

b) Set the initial pixmap placement (IPP) to the following:

nvidia-settings -a InitialPixmapPlacement=2

With this configuration, the window decoration never corrupts; unfortunately, text input boxes seem to sporadically corrupt (it's happening as I type this very instant).

If I set IPP to 1, 3 or 4, the window decoration corrupts, but the text box never exhibits corruption.

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

here is a photo of the bug

I can confirm that in Intrepid too.
kernel 2.6.27-4 nvidia drivers 177.76, compiz 0.7.7+git20080807

And again i can confirm that in intrepid too.
kernel 2.6.27-7-generic nvidia drivers 177.80, compiz 1:0.7.8-0ubuntu4.
Its more ugly than in hardy!!!

Marking confirmed; this has not been fixed in Intrepid and I've seen it on two machines now.

Gourgi's screenshot in comment #150 shows the problem.

On my machine with an up-to-date intrepid, this occurs reliably when OpenOffice is running. Usually only affects the OpenOffice window decorations. Also occurs some of the time when running Eclipse.

Seems to be triggered by hovering over the window maximize/minimize buttons, or by clicking on something in an application window. Also, once one window starts being affected, it's only a matter of time until other windows start getting corrupt decorations as well.

I believe the 'corrupt' titlebars and 'missing' titlebars are manifestations of the same issue. In the case of 'missing' titlebars - they are just 100% transparent, not actually 'gone'. I've seen both, and it's a toss-up as to how the corruption will appear.

This only seems to be an issue when Compiz is running.

Also, could someone verify that this bug is classified properly? Which package should this be assigned to?

Gabriel Bauman: this is definitely nvidia drivers bug, see nvnews.net forums to get more info

http://www.nvnews.net/vbulletin/showthread.php?t=122043
http://www.nvnews.net/vbulletin/showthread.php?t=118408

And here is most significant comment:
http://www.nvnews.net/vbulletin/showthread.php?p=1817816#post1817816

actually this bug and bug #226833 are duplicates

Anyone tracking this may find this interesting:

 o http://lists.freedesktop.org/archives/xorg/2008-August/038022.html

From that post:

==
 a. Compiz registers for damage events.
 b. Some X client sends a rendering request.
 c. The X server sends Compiz a damage event.
 d. Compiz processes the request and sends commands to the HW.
 e. HW processes Compiz's commands using stale bits.
 f. X driver processes the rendering request.
 g. HW processes X's commands, causing the damage that Compiz thinks it's already processed.
==

So there's the technical description, and it looks like this is being actively worked on by the xorg folks and nVidia on internal bug number 470239 (thanks Dmitriy).

Conn,

The Option "BackingStore" "false" works for me
Unfortunately I get a lot of other corruption like the grey titlebar. But this defenately solved the purple corruption.

Robert

I can confirm this for Intrepid, too. Besides bug #99508 affects me too, but . Intrepid Ibex, nvidia quadro NVS 110. Both driver versions 177 and 173.
Both bugs combined are really looking awful.

I suspect the bug only exists when using large x-y shadow offsets. Try zeroing them at the decoration plugin in compizconfig-settings-manager. Check the screenshot and try setting the same values on yours.

That solved the problem in my PC. Good luck

macabro22, unfortunately this doesn't solve it for me.

I think this bug is fixed for me. There have been some driver updates in intrepid-proposed. Activate the proposed updates repository, and see what happens!

mrtwister, I activated intrepid-proposed in Synaptic, reloaded, but didn't get any updates in the Update Manager?

macabro22, zeroing the x-y shadow offset of the decoration plugin in compizconfig-settings-manager does not help for me either.

it's not fixed is a known bug of this nvidia driver series will be fixed in
the next release

Next release of what? I hope you mean the nvidia driver. :-)

On Fri, Nov 7, 2008 at 8:07 AM, nexus <email address hidden> wrote:

> Next release of what? I hope you mean the nvidia driver. :-)
>
> obviously
>

It hasn't been fixed here!

I've had Compiz en Human-theme updates. But these didn't fix it.

This is what my update manager did:

"nvidia-173-modaliases (173.14.12-1-0ubuntu4) to 173.14.12-1-0ubuntu5
nvidia-177-kernel-source (177.80-0ubuntu2) to 177.80-0ubuntu3
nvidia-177-modaliases (177.80-0ubuntu2) to 177.80-0ubuntu3
nvidia-96-modaliases (96.43.05-0ubuntu10) to 96.43.09-0ubuntu1
nvidia-glx-177 (177.80-0ubuntu2) to 177.80-0ubuntu3
linux-headers-2.6.27-7 (2.6.27-7.15) to 2.6.27-7.16
linux-headers-2.6.27-7-generic (2.6.27-7.15) to 2.6.27-7.16
linux-image-2.6.27-7-generic (2.6.27-7.15) to 2.6.27-7.16"

sorry man but... who cares of your update mangaer ? 177.80 has the bug

mrtwister, I've had the same updates without intrepid-proposed enable, so I think you enabling it and getting new updates was probably a coincidence!

MarcoBazzani,
Check http://www.ubuntu.com/community/conduct ...
And would you have a link that shows that this is a known bug of the nvidia driver series will be fixed in
the next release? Thanks!

Kenden, probably this was a coincidence. I read about this pre-release driver update in intrepid-proposed in a german ubuntu-forum, but my last update has already been two days ago.
Nevertheless, the problem seems to be solved for me.

Bug: Ubuntu 8.10 Intrepid Ibex - NVIDIA Driver Version: 177.80

Upgrading from 177.80-0ubuntu2 to 177.80-0ubuntu3 did not solve the bug.

I noticed that it occurs more frequently with dark themes, for eg. Newave from community-themes package.

I have the same problem with my nvidia geforce go 7400. I know another person, who has the same problem too, but I don't know exactly witch graphicard. I have the problem since 8.10. Under 8.04 oder 7.10 I've never seen it.
I've activated the version 177.

does this bug also issues rendering in avant-window-navigator?
I have also randomly the issues like described above in thunderbird.
Yesterday I installed awn in intrepid and registered also random vertical lines above icons when using launcher-applet only (imo no dep. issue)

vertical lines in awn were results of missing deps but if the frame border issues appear also rendering of icon effect "3d spotlight turn" looks disturbed.

Looks like it's been fixed in 180.06

"Fixed a regression that could result in window decoration corruption when running Compiz using Geforce 6 and 7 series GPUs."

http://www.nvnews.net/vbulletin/showthread.php?t=123072

FWIW, running restricted manager (system -> administration -> hardware drivers) and selecting nvidia driver version 96 (the oldest avail. version) fixes the problem for me in intrepid. It might have made something else slower, but I can't tell what after a few days.

ski@ganiodayo:~$ dpkg -l | grep -i nvidia-glx
rc nvidia-glx-173 173.14.12-1-0ubuntu4 NVIDIA binary Xorg driver
rc nvidia-glx-177 177.80-0ubuntu2 NVIDIA binary Xorg driver
ii nvidia-glx-96 96.43.09-0ubuntu1 NVIDIA binary Xorg driver

I've got a nVidia Corporation G72M [Quadro NVS 110M/GeForce Go 7300] (rev a1) on amd64 here.

I'm psyched to see the mainline release fix this bug in 180.06 tho. More here:
http://www.phoronix.com/scan.php?page=article&item=nvidia_180_vdpau&num=1

PS - Installing the old driver has also fixed a problem I've had quite sporatically and inexplicably on wikipedia image pages. As well as scrolling in VirtualBox's main screen when I have more than 7 VMs. Will be interested to see if 180.06 fixes this too. Out of curiosity, have others who've seen the titlebar corruption seen either of these problems as well?

i'm using the 180.06 since yesterday and this bug didn't appear.
So i guess it is really fixed.

the 180.08 fixed the bug.

but, waiting for it to appear in the repositories :)

waiting for a package from alberto :)

I'm using the 173 version on a GeForce 5 FX - the 180 does not apply to this card, right?

folks you can wait but i don't see the reason why.
With DKMS (installed by default) there is no need to reinstall the nvidia drivers after an kernel upgrade.

and how can I upgrade to 180.08 with dkms
could you give us a little guide
cheers

On Fri, Nov 21, 2008 at 12:27 PM, robert114 <email address hidden> wrote:

> wait but i don't see the reason why.
> With DKMS (installed by default) there is no need to reinstall the nvidia
> drivers after an kernel upgrade.
>

um, what has that to do with DKMS? Waiting means - until a new nvidia driver version is going to be put into the repositories.
DKMS just - like you said - takes care of recompiling drivers after a KERNEL upgrade.
No kernel upgrades are subject of discussion here.
And no nvidia driver REINSTALL, but a NEW nvidia driver has to be installed.
I guess you misunderstood ;-)

as far as i know i didn't had to reinstall the NVIDIA diver after a kernel upgrade. So I thought that was due to the DKMS. But right now i'm confused.
I don't think Ubuntu will release the latest driver in the repos. You can wait for envy tough.

Marco you can find a manual here:
http://us.download.nvidia.com/XFree86/Linux-x86/177.82/README/chapter-04.html

to sum it up:
- This bug has NOTHING to do with DKMS and kernel upgrades.
- Ubuntu can NOT backport the fix to hardy/intrepid because the nvidia driver is not open source.
- AFAIK Ubuntu won't provide the version 180 driver in "Intrepid proposed" due to Ubuntu's policy

so we have this options:

1. wait until Jaunty
or
2. get an inofficial package from somewhere, or directly install it from nvidia.
Everything clear?

I *believe* that the point being made about DKMS is that you should now be
able to install the driver directly from nVidia if you want to use it (and
you don't have to wait for the repos to be updated, if they ever are in this
case). This was not a good idea in past versions of Ubuntu because any
kernel updates would break the self-installed nVidia driver and you'd boot
into low-graphics mode. This is frustrating when the kernel gets upgraded
every couple of weeks. Since DKMS has been implemented by default in
Intrepid, this is no longer a problem. When Ubuntu updates its kernel, it
should no longer break you system (it recompiles the custom nVidia kernel
modules whenever the kernel gets updated). So you're able to install the
new driver directly from nVidia without worrying about future kernel updates
breaking your system.

@christian
uh ?
- other version of nvidia drivers were backported into hardy at least with envy (hardy has 169 drivers and 173 are available with envy, so why not do the same with 180.08 in intrepid?
- isn't it diehard to not backport a driver that fix a main issue ? I can understand from software version that implements new feature but for bug fixing should be reccomended or not ? I know that this is a binary driver and ubuntu cannot support because is closed source etc... but as SABDFL said some time ago propretary drivers allow us to use open source software at best (unfortunately).

Yes, in know.
Envy is not official ubuntu - I never said It were not possible. You can for sure backport any version into edgy if you want.

But AFAIK _Ubuntu_ won't DO it, by policy.
They don't even take new bugfix versions of e.g. Samba: loo at http://www.samba.org -
Samba maintainance version 3.0.32
Ubuntu hardy: 3.0.28a-1ubuntu4.4
Ubuntu hardy-updates: 3.0.28a-1ubuntu4.7

They implement bug fixes, yes, but they don't include newer versions. Thats policy.

So what I meant: Sure you can have them available with envy - but that has nothing wo do with Ubuntu updates or bug fixes. Envy is unofficial, unsupported. Envy says, that you have to uninstall envy if you want to dist-upgrade Ubuntu to a newer version.
Know what I mean?

And that's the bad thing in prop drivers like nvidia - Ubuntu can't see what caused the bug, and fix it in Intrepid (173/177) - because, as I understand their policy, they DON'T take newer versions to an existing release. Ubuntu has no rolling release. The driver version will stay at 173/177.
Please correct me if I am wrong.

180.xx will first be packaged for Jaunty before we look at the possibility of a backport, there doesn't need to be a lot of discussion about this. Please keep comments relevant to the window decorator bug.

On Sat, Nov 22, 2008 at 5:30 PM, Hew McLachlan <email address hidden>wrote:

> 180.xx will first be packaged for Jaunty before we look at the
> possibility of a backport, there doesn't need to be a lot of discussion
> about this. Please keep comments relevant to the window decorator bug.

I think that the bug is unsolvable with the current driver version so should
be marked ad "Impossible to fix" if no other version will be backported.
cheers :)

i'm using 173 version with compiz enabled. sometimes it manages to hide the window title behind the launch bar. did you see this too?

Seems no hope of fixing this issue in short term.

My experience, 169.04 from Nvidia is the best one for Hardy.
Hardy's own driver or 177 will get titlebar or compiz problem. I just tried the 180.06, which cannot support my dual monitors with separated screens (different resolutions).

BTW, I have to use '--indirect-rendering' to avoid memory leak of compiz.

set same state here too

This bug was fixed in the package nvidia-graphics-drivers-173 - 173.14.16-0ubuntu1

---------------
nvidia-graphics-drivers-173 (173.14.16-0ubuntu1) jaunty; urgency=low

  * New upstream release. Supports the new X.org ABI (LP: #308410)
    * Fixed a problem that caused nvidia-installer to remove Compiz's libglx.so.
    * Added "nvidia-uninstall" as a shortcut for "nvidia-installer --uninstall".
    * Fixed a bug that caused corrupt window decorations in Compiz (LP: #186382).
    * Fixed corruption in KDE 4 when OpenOffice is launched.
    * Fixed a problem that prevented X from starting on 2.6.29-rc1 with an error
      like the following:
      X:6500 map pfn expected mapping type write-combining for d0000000-d0500000,
      got uncached-minus
    * Added the ability to run distribution provided pre- and post- installation
      hooks to 'nvidia-installer'; please see the 'nvidia-installer' manual page for details.
  * Drop debian.binary/patches/NVIDIA_173.14.12_2.6.27.patch
  * debian/nvidia-glx-173.preinst:
    - Correct typo in the removal of diversions of /usr/lib/xorg/modules/extensions/libglx.so
  * debian/nvidia-glx-173.postrm.in
    - Do not remove libGL.so (LP: #309116)
  * debian/nvidia-glx-173-dev.preinst.in:
    - Add diversion on /usr/lib/libGL.so since (the postrm tries to remove it already)
  * debian/nvidia-glx-173-dev.postrm:
    - replace legacy-173xx with 173

 -- Alberto Milone (tseliot) <email address hidden> Thu, 29 Jan 2009 13:23:57 +0100

I have similar problems as being reported here. Running Ubuntu 8.10 (freshly installed just a few days ago) and have nVidia 177 driver activated. I have attached a screenshot to show the problem.

Is this being dealt with under a different bug report of will it continue to be dealt with here?

Thanks.

gsxruk, I had the same issue with the 177 driver in Intrepid.
I have installed the driver nvidia-glx-180 (now available as a package in synaptic), and I'm happy to say the issue seems to be gone.

Thanks, installed that and everything seems normal.

I'll see how things go.

This appears to be working for me too! *Hoorraay!*

Yup, fixes my issues with the KDE4 taskbar strobing in time with the OpenOffice cursor too. Also not noticed corrupt icons in the system tray either.

Vik :v)

[This is an automated message]

In Jaunty (9.04), we are dropping the nvidia-graphics-drivers-177 package, which
is now superseded by then nvidia-graphics-drivers-180 package.

  http://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180

To transition your bug into the new package, we need your help. Please do the following:

 a. Verify the bug occurs in Jaunty with the -180 driver
     (ISOs: http://cdimage.ubuntu.com/releases/jaunty/)
 b. If you haven't already, please include in the bug:
     * Your /var/log/Xorg.0.log
     * Your /etc/X11/xorg.conf
     * The output of `lspci -vvnn`
     * Steps to reproduce the issue
 c. Under Affects, click the down arrow to the left of 'nvidia-graphics-drivers-177'
 d. Edit the Package to change 'nvidia-graphics-drivers-177' to 'nvidia-graphics-drivers-180'
 e. Click Save Changes

Thank you!

[We'll expire the remaining -177 bugs in a month or so.]

nvidia-glx-180 fixes the visual glitches I was having with openoffice, metacity, and gnome-do. I have no further visual trouble.

[This is an automated message]

In Jaunty (9.04) we have dropped the nvidia-graphics-driver-177 package, as
it is superseded by nvidia-graphics-drivers-180.

Because of this, we are closing this bug as expired.

You are encouraged to file your -nvidia bug reports against the
nvidia-graphics-drivers-180 package. Please be aware that because this
is a proprietary graphics driver, the amount of bug support we can
provide at the distro level is very limited.

Not going to be updated for intrepid.