nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   [BUG] Resolution changes while running gnome-shell can lead to display corruption (http://www.nvnews.net/vbulletin/showthread.php?t=161376)

rapsure 04-09-11 11:53 AM

[BUG] Resolution changes while running gnome-shell can lead to display corruption
 
1 Attachment(s)
When running games that change the resolution at load time for intro graphics I will often experience display corruption in either the game or when I exit corruption on the desktop of gnome-shell. By simply changing the program to run in a windowed mode I've been able to avoid Xid's and display corruption. The worst game for causing corruption and Xid's is d2x-xl which can be obtained at http://www.descent2.de/ although it doesn't include the descent art and can be difficult to install. Another way to trigger display corruption is to run gnome-shell --replace when mutter is running. The bug is much worse with the 260.19.44. Unloading the driver and reloading does not always clear the screen corruption. Sometimes the result will be static across the desktop too.

Please fix this bug as it affects general usability of the desktop. I'm currently using the 270.30 driver.

rapsure 04-11-11 11:55 PM

Re: [BUG] Resolution changes while running gnome-shell can lead to display corruption
 
nvidia seems to have fixed more bugs than what is listed because now gnome-shell is fast with the animations, and I don't get the Xid's when loading d2x-xl.

rapsure 05-10-11 02:45 AM

Re: [BUG] Resolution changes while running gnome-shell can lead to display corruption
 
I have to respond to my own bug because after further testing this bug isn't entirely resolved. Dynamic twinview and switching to one of those resolutions doesn't work. Also resolution changes for 32-bit apps in the 64-bit environment doesn't always work either and lead to display corruption as well.

Nvidia please QA your driver against gnome 3 with gnome-shell and mutter. I shouldn't have to be careful on my actions because I know that there are three easy tasks I can do that will crash the driver along with the entire system that I perform quite often.

I have a script that I use to setup dynamic twinview the way that I like so that I can watch movies on the tv, and use the computer monitor for general work.

The following is the contents of the script.

./nv-control-dpy --set-associated-dpys 0x00030000
./nv-control-dpy --assign-twinview-xinerama-info-order DFP-0,CRT-1
./nv-control-dpy --add-metamode "DFP-0: NULL, DFP-1: nvidia-auto-select"
./nv-control-dpy --add-metamode "DFP-0: NULL, DFP-1: 1024x768"
./nv-control-dpy --add-metamode "DFP-0: NULL, DFP-1: 800x600"
./nv-control-dpy --add-metamode "DFP-0: NULL, DFP-1: 640x480"
./nv-control-dpy --add-metamode "DFP-0: NULL, DFP-1: 512x384"
./nv-control-dpy --add-metamode "DFP-0: NULL, DFP-1: 320x240"
./nv-control-dpy --add-metamode "DFP-0: 1024x768+0+0, DFP-1: 1024x768+1024+0"
./nv-control-dpy --add-metamode "DFP-0: 1600x1200+0+0, DFP-1: 1360x768+1600+0"


All times are GMT -5. The time now is 04:19 AM.

Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.