[SOLVED] Blue tinted Second Life window with Nvidia 304.30 driver

[CronoCloud]

So far Second Life is the only thing having issues with 304.30. I can't even take a screenshot of the issue because imagemagick and ffmpeg's x11grab don't capture it. Had to use my phone to show what happens:

http://www.youtube.com/watch?v=YBkoUQ9-_7E

CronoCloud

[DBelton]

Is Second Life by chance using Flash? If so, there is a bug in Flash with some video cards that causes it to have a blue tint.

Some versions of Flash, you could disable the hardware acceleration to work around it, but I think that's even broken in the newer versions.

Search here in the forum, there were several threads about blue tint in flash, and I believe some may have workarounds in them.

[CronoCloud]

Originally Posted by DBelton

Is Second Life by chance using Flash?

No. it's openGL

Search here in the forum, there were several threads about blue tint in flash, and I believe some may have workarounds in them.

Yes, one of the first things I did, thought I remembered seeing something, but those issues were all flash related, and turning off hardware acceleration fixed it....which I can't do with SL.

CronoCloud

[DBelton]

I looked around some, and can't seem to find anything about it, and nvidia's forums are still closed. Couldn't find anything in their faq or knowledge base, either.

[smr54]

The only other thing, which I think no longer worked in newer versions of flash, was to make a change in the shared object file so that it wasn't trying to use libvdpau.

cd /usr/lib/adobe-flashplugin/
sudo perl -pi.bak -e 's/libvdpau/lixvdpau/g' libflashplayer.so

Don't know if that's working now though.

Some other suggestions here, as well.

http://askubuntu.com/questions/11712...o-appears-blue

[Prescience500]

The problem isn't related to flash. I'm having the same problem. It's effecting every non KDE, qt, or gtk-based game. It only just started happening. It was working fine just the other day. Any fix you can recommend would be GREATLY appritiated by me, too.

---------- Post added at 09:09 PM ---------- Previous post was at 09:02 PM ----------

Btw, if I had to guess at a cause, I'd say that it's caused by how the video driver interacts with X.

[CronoCloud]

Originally Posted by Prescience500

I'm having the same problem. It's effecting every non KDE, qt, or gtk-based game. It only just started happening.

I didn't try any Linux native games, glxgears seemed fine, as did Star Trek Online under WINE. Let me check FreeDroid RPG...Ah! it affects that too!

But yes, this is NOT flash related.

CronoCloud

[bob]

Just to confirm; since the updates today, Sauerbraten and Quake3 Demo are also blue-shaded to the extreme (unplayable). Not a kernel issue since it's now affecting prior kernels as well.

Here's the updates involved:

hcp-libs-4.2.4-9.P1.fc17
selinux-policy-3.10.0-142.fc17
cryptsetup-libs-1.5.0-1.fc17
dhcp-common-4.2.4-9.P1.fc17
nvidia-xconfig-1.0-17.fc17
openconnect-4.06-1.fc17
kdelibs-common-4.8.4-8.fc17
nvidia-settings-1.0-19.fc17
xorg-x11-drv-nvidia-libs-304.30-1.fc17
akmod-nvidia-304.30-1.fc17
xorg-x11-drv-nvidia-304.30-1.fc17
xorg-x11-drv-nvidia-libs-304.30-1.fc17
kdelibs-4.8.4-8.fc17
cryptsetup-1.5.0-1.fc17
openconnect-lib-compat-4.06-1.fc17
dhclient-4.2.4-9.P1.fc17
selinux-policy-devel-3.10.0-142.fc17
selinux-policy-targeted-3.10.0-142.fc17
sed-4.2.1-10.fc17
xorg-x11-drv-intel-2.20.1-1.fc17
SDL_mixer-1.2.12-3.fc17
ibus-chewing-1.4.0-1.fc17
google-chrome-unstable-22.0.1221.1-149058
lftp-4.3.8-1.fc17
libcdio-0.83-5.fc17
kernel-devel-3.5.0-2.fc17
java-1.7.0-openjdk-1.7.0.5-2.2.1.fc17.9
kernel-headers-3.5.0-2.fc17
ModemManager-0.5.3.96-1.fc17
kernel-3.5.0-2.fc17
kmod-nvidia-3.4.6-2.fc17.x86_64-304.30-1.fc17

[Prescience500]

CronoCloud, do you use RPMFusion for your graphics driver? Also, has there been an update in either the video driver or X in the past few days? I forgot if they were updated on mine...

---------- Post added at 09:54 PM ---------- Previous post was at 09:53 PM ----------

Oh, look...someone answered one of my questions while I was typing, lol.

[bob]

BTW, downgrading nvidia-settings doesn't affect the problem.

Well, it's snooze time; maybe someone will have a solution in the next few hours. In any case, this'll have to wait until tomorrow for me.

[CronoCloud]

Originally Posted by Prescience500

CronoCloud, do you use RPMFusion for your graphics driver? Also, has there been an update in either the video driver or X in the past few days?

Yes I do use RPMfusion and it was today's update that did it.. in fact SL was running fine under 295.59. just this morning!

CronoCloud

[Prescience500]

So I guess someone should let the good people at RPMfusion know. I just checked and there isn't a bug yet for this in their bug tracker.

[DBelton]

It has been reported on rpmfusion

https://bugzilla.rpmfusion.org/show_bug.cgi?id=2434

Go and add your issues to the bug, possibly things will get done then.

Originally Posted by CronoCloud

No. it's openGL



Yes, one of the first things I did, thought I remembered seeing something, but those issues were all flash related, and turning off hardware acceleration fixed it....which I can't do with SL.

CronoCloud

Wrong it's SDL.

If you report it the nvidia devs will fix it.
Report it here.

http://www.nvnews.net/vbulletin/forumdisplay.php?f=14


As rpmfusion nvidia packager perhaps I should have reported it, but as I'm not affected by this issue I wont bother.

---------- Post added at 07:09 AM ---------- Previous post was at 07:06 AM ----------

Originally Posted by Prescience500

So I guess someone should let the good people at RPMfusion know. I just checked and there isn't a bug yet for this in their bug tracker.

WTF are we (rpmfusion) supposed to do about it?, go and report it to nvidia instead.

http://www.nvnews.net/vbulletin/forumdisplay.php?f=14

---------- Post added at 08:07 AM ---------- Previous post was at 07:09 AM ----------

Originally Posted by DBelton

I looked around some, and can't seem to find anything about it, and nvidia's forums are still closed. Couldn't find anything in their faq or knowledge base, either.

They are open but still slow as "watching paint dry".
I forwarded the rpmfusion bugreport to

http://www.nvnews.net/vbulletin/show....php?p=2570719

[bob]

G'mornin' world!

Well, it looks like this is still a problem. Jumping to the bug report, I tried Leigh's listing of downgrades, but ran up against a kmod-common incompatibility:

yum downgrade nvidia-kmod-common akmod-nvidia kmod-nvidia nvidia-settings nvidia-xconfig xorg-x11-drv-nvidia xorg-x11-drv-nvidia-libs
Loaded plugins: fastestmirror, langpacks, presto, refresh-packagekit
Loading mirror speeds from cached hostfile
* fedora: mirror.hiwaay.net
* rpmfusion-free: mirror.hiwaay.net
* rpmfusion-free-updates: mirror.hiwaay.net
* rpmfusion-nonfree: mirror.hiwaay.net
* rpmfusion-nonfree-updates: mirror.hiwaay.net
* updates: ftp.linux.ncsu.edu
No Match for available package: 1:kmod-nvidia-295.53-1.fc17.1.x86_64
Resolving Dependencies
--> Running transaction check
---> Package akmod-nvidia.x86_64 1:295.59-1.fc17 will be a downgrade
--> Processing Dependency: nvidia-kmod-common >= 1:295.59 for package: 1:akmod-nvidia-295.59-1.fc17.x86_64
---> Package akmod-nvidia.x86_64 1:304.30-1.fc17 will be erased
---> Package nvidia-settings.x86_64 0:1.0-18.fc17 will be a downgrade
---> Package nvidia-settings.x86_64 0:1.0-19.fc17 will be erased
---> Package nvidia-xconfig.x86_64 0:1.0-16.fc17 will be a downgrade
---> Package nvidia-xconfig.x86_64 0:1.0-17.fc17 will be erased
---> Package xorg-x11-drv-nvidia.x86_64 1:295.53-1.fc17 will be a downgrade
---> Package xorg-x11-drv-nvidia.x86_64 1:304.30-1.fc17 will be erased
---> Package xorg-x11-drv-nvidia-libs.i686 1:295.53-1.fc17 will be a downgrade
---> Package xorg-x11-drv-nvidia-libs.x86_64 1:295.53-1.fc17 will be a downgrade
---> Package xorg-x11-drv-nvidia-libs.i686 1:304.30-1.fc17 will be erased
---> Package xorg-x11-drv-nvidia-libs.x86_64 1:304.30-1.fc17 will be erased
--> Finished Dependency Resolution
Error: Package: 1:akmod-nvidia-295.59-1.fc17.x86_64 (rpmfusion-nonfree-updates)
Requires: nvidia-kmod-common >= 1:295.59
Removing: 1:xorg-x11-drv-nvidia-304.30-1.fc17.x86_64 (@rpmfusion-nonfree-updates)
nvidia-kmod-common = 1:304.30
Downgraded By: 1:xorg-x11-drv-nvidia-295.53-1.fc17.x86_64 (rpmfusion-nonfree)
nvidia-kmod-common = 1:295.53
Error: Package: 1:kmod-nvidia-3.4.6-2.fc17.x86_64-304.30-1.fc17.x86_64 (installed)
Requires: nvidia-kmod-common >= 1:304.30
Removing: 1:xorg-x11-drv-nvidia-304.30-1.fc17.x86_64 (@rpmfusion-nonfree-updates)
nvidia-kmod-common = 1:304.30
Downgraded By: 1:xorg-x11-drv-nvidia-295.53-1.fc17.x86_64 (rpmfusion-nonfree)
nvidia-kmod-common = 1:295.53
Error: Package: 1:kmod-nvidia-3.4.5-2.fc17.x86_64-295.59-1.fc17.5.x86_64 (@rpmfusion-nonfree-updates)
Requires: nvidia-kmod-common >= 1:295.59
Removing: 1:xorg-x11-drv-nvidia-304.30-1.fc17.x86_64 (@rpmfusion-nonfree-updates)
nvidia-kmod-common = 1:304.30
Downgraded By: 1:xorg-x11-drv-nvidia-295.53-1.fc17.x86_64 (rpmfusion-nonfree)
nvidia-kmod-common = 1:295.53
Error: Package: 1:kmod-nvidia-3.5.0-2.fc17.x86_64-304.30-1.fc17.x86_64 (installed)
Requires: nvidia-kmod-common >= 1:304.30
Removing: 1:xorg-x11-drv-nvidia-304.30-1.fc17.x86_64 (@rpmfusion-nonfree-updates)
nvidia-kmod-common = 1:304.30
Downgraded By: 1:xorg-x11-drv-nvidia-295.53-1.fc17.x86_64 (rpmfusion-nonfree)
nvidia-kmod-common = 1:295.53
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

So, "you can't get there from here".

.