nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   nvidia-settings twin-view save additional settings bug (http://www.nvnews.net/vbulletin/showthread.php?t=204242)

NHOjar 04-10-13 04:44 AM

nvidia-settings twin-view save additional settings bug
 
nvidia-settings twin-view save additional settings bug.

OS: Fedora 18
Desktop: Gnome 3
rpm -qa | egrep -i "xorg|nvidia" | sort --> edited to reduce list length
akmod-nvidia-304.64-7.fc18.x86_64
kmod-nvidia-3.8.3-203.fc18.x86_64-304.64-7.fc18.3.x86_64
kmod-nvidia-3.8.4-202.fc18.x86_64-304.64-7.fc18.4.x86_64
kmod-nvidia-3.8.5-201.fc18.x86_64-304.64-7.fc18.5.x86_64
nvidia-settings-1.0-26.fc18.x86_64
nvidia-xconfig-1.0-25.fc18.x86_64
xorg-x11-apps-7.7-1.fc18.x86_64
xorg-x11-drv-evdev-2.7.3-5.fc18.x86_64
xorg-x11-drv-fbdev-0.4.3-3.fc18.x86_64
xorg-x11-drv-intel-2.21.5-1.fc18.x86_64
xorg-x11-drv-modesetting-0.6.0-1.fc18.x86_64
xorg-x11-drv-nouveau-1.0.6-1.fc18.x86_64
xorg-x11-drv-nvidia-304.64-5.fc18.x86_64
xorg-x11-drv-nvidia-libs-304.64-5.fc18.x86_64
xorg-x11-drv-qxl-0.0.22-5.20120718gitde6620788.fc18.x86_64
xorg-x11-drv-synaptics-1.6.3-1.fc18.x86_64
xorg-x11-drv-vesa-2.3.2-2.fc18.x86_64
xorg-x11-drv-vmmouse-13.0.0-1.fc18.x86_64
xorg-x11-drv-vmware-12.0.2-3.20120718gite5ac80d8f.fc18.x86_64
xorg-x11-fonts-truetype-1.0.2-1.fc18.noarch
xorg-x11-fonts-Type1-7.5-6.fc18.noarch
xorg-x11-font-utils-7.5-10.fc18.x86_64
xorg-x11-server-common-1.13.3-2.fc18.x86_64
xorg-x11-server-utils-7.5-16.fc18.x86_64
xorg-x11-server-Xorg-1.13.3-2.fc18.x86_64
xorg-x11-utils-7.5-7.fc18.x86_64
xorg-x11-xauth-1.0.7-2.fc18.x86_64
xorg-x11-xinit-1.3.2-7.fc18.x86_64
xorg-x11-xkb-utils-7.7-5.fc18.x86_64


I had a significant issue with my Nvidia Twin-view setting, for my laptop, that was bugging me for a long time: -
When ever I resumed from hibernation, at home, all my open windows and Gnome Panels would have been shifted to the external monitor. On checking the defaul monitor was switched to the external monitor
I have identified 2 issues with the nvidia-settings applet:-
1. It adds the wrong location info to the additional device settings
2. It adds duplicate modes, it un-necessarily extends the modes list by appending duplicate modes to the modes list until the maximum length is reached

The location of the main window, DFP is +0+0;
The require location of the CRT is +1920+0; and not +0+0;
- which I believe is the source of my problem.

My fix is to manually edit the modes, removing the offending location definitions.

Extract from offending xorg.conf:-
Option "metamodes" "DFP: nvidia-auto-select +0+0, CRT: nvidia-auto-select +1920+0;
CRT: 1680x1050_60 +0+0;
CRT: 1680x1050_75 +0+0;
CRT: 1680x1050_60_0 +0+0;
CRT: 1600x1000 +0+0;
CRT: 1600x1000_60 +0+0;
CRT: 1440x900 +0+0;
CRT: 1440x900_75 +0+0;
CRT: 1440x900_60 +0+0;
CRT: 1280x1024 +0+0;
CRT: 1280x1024_75 +0+0;
CRT: 1280x1024_72 +0+0;
CRT: 1280x1024_60 +0+0;
CRT: 1152x864 +0+0;
CRT: 1152x864_75 +0+0;
CRT: 1024x768 +0+0;
CRT: 1024x768_75 +0+0;
CRT: 1024x768_70 +0+0;
CRT: 1024x768_60 +0+0;
CRT: 800x600 +0+0;
CRT: 800x600_75 +0+0;
CRT: 800x600_72 +0+0;
CRT: 800x600_60 +0+0;
CRT: 640x480 +0+0;
CRT: 640x480_75 +0+0;
CRT: 640x480_72 +0+0;
CRT: 640x480_60 +0+0;
CRT: nvidia-auto-select +0+0;
CRT: nvidia-auto-select +0+0;
CRT: nvidia-auto-select +0+0;
CRT: nvidia-auto-select +0+0;
CRT: 1680x1050 +0+0;
CRT: 1680x1050_60 +0+0;
CRT: 1680x1050_75 +0+0;
CRT: 1680x1050_60_0 +0+0;
CRT: 1600x1000 +0+0;
CRT: 1600x1000_60 +0+0"


All times are GMT -5. The time now is 07:49 AM.

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