Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#22830 - nvidia-settings won't honor settings

Attached to Project: Community Packages
Opened by Anthony Clark (anthonyclark) - Wednesday, 09 February 2011, 19:24 GMT
Last edited by Ionut Biru (wonder) - Thursday, 10 February 2011, 16:56 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
XVideo settings in nvidia-settings are not honored. Configuring desired settings in either the GUI or the .nvidia-settings.rc under the catagory "X Server XVideo Settings" will not be effected when invoking the loading of the settings with 'nvidia-settings --load-config-only". The values get written to the config file, but are never actually applied.

This ultimately effects "Tearing" in X windows. Note that OpenGL settings such as VBlank will be honored as expected.

Additional info:
* Nvidia Proprietary driver 260.19.36-2
* Xorg and .nvidia-settings.rc are attached.


Steps to reproduce:
1: Install Arch
2: pacman -S nvidia nvidia-utils
3: configure via 'nvidia-settings'
4: add 'nvidia-settings -l &' to ~/.xinitrc
5: Change brightness and/or other settings, specifically Sync to VBlank
   xorg.conf (1.5 KiB)
This task depends upon

Closed by  Ionut Biru (wonder)
Thursday, 10 February 2011, 16:56 GMT
Reason for closing:  Not a bug
Comment by Anthony Clark (anthonyclark) - Wednesday, 09 February 2011, 19:25 GMT
Nvidia settings for the above
   nvidia-settings.rc (1.3 KiB)
Comment by Anthony Clark (anthonyclark) - Thursday, 10 February 2011, 03:44 GMT
Sorry for this. I realized XVideo == "videos playing in X" .. not all X windows like I originally thought. So this BUG would be considered mistakingly reported. Sorry everyone.

Loading...