|
|
#1 | |
|
Registered User
Join Date: Apr 2007
Posts: 7
|
numbers in $HOME/.nvidia-settings-rc of a user account are stored with '.' ( dot ) as decimal point:
0/RedBrightness=0.000000 this results in an Error parsing configuration file ... '0/RedBrightness=0.000000' (Trailing garbage). in root's .nvidia-settings-rc they are stored with ',' (comma) as decimal point. the two accounts has the same locale settings LC_NUMERIC="de_DE.UTF-8" the files are generated in both cases with nvidia-settings. nividia driver 1.0-9755 open suse 10.2, x86-64 dual core i.b. |
|
|
|
|
|
|
#2 | |
|
NVIDIA Corporation
Join Date: Aug 2002
Posts: 3,740
|
|
|
|
|
|
|
|
#3 |
|
Registered User
Join Date: Apr 2007
Posts: 7
|
nice to be not allone with non working saved settings.
aspecialy in front of a big audience, when connecting a notebook to a beamer. at least i this situation i can speak about the reason to use a "locale C" for mission critical persistent data or why using non localized system functions. if this problem is known, why it is not solved? give me the source code, i solve it for you. best regards i.b. |
|
|
|
|
|
#4 | |
|
NVIDIA Corporation
Join Date: Aug 2002
Posts: 3,740
|
An updated binary was attached to the above thread; the `nvidia-settings` source code is available from ftp://download.nvidia.com/XFree86/nvidia-settings.
|
|
|
|
|
|
|
#5 |
|
Registered User
Join Date: Apr 2007
Posts: 7
|
thx, this is a nice solution.
but which of the tar's is the latest one? nvidia-settings-1.0.tar.gz is from 04.04.2007 but the contents from 2006-12-15. the version numbering has not the order as expected from file dates. i.b. |
|
|
|
![]() |
| Thread Tools | |
|
|