How to make nvidia-settings sticky

[Husse]

This is edited 2007-07-15
This is a problem that has been around some time
You change nvidia-settings and after the next boot they are back to default.

Nvidia-settings actually keep your customization but must run for them to take effect.
This guide tells you how to achieve this automatically.
In no part of this guide should you be root - no sudo!
In your ~ folder is a file called .xinitrc
~ is an "alias" for /home/your_name
A dot (.) first in a file name indicates it's a hidden file so you must turn on "Show hidden files" to see it. If it does not exist - create it (text file).
Then add the following

Code: Select all

#!/usr/bin/env bash
/usr/bin/nvidia-settings --load-config-only &
exec gnome-session


For KDE use

Code: Select all

exec startkde

The exec command must be the last command.
Make the file executable

Code: Select all

chmod chmod +x ~/.xinitrc

or use the GUI - right click>Properties>Permissions>Make this file executable
For the xserver to use xinitrc you must create a symlink

Code: Select all

ln -s ~/.xinitrc ~/.xsession

This starts nvidia-settings when you start gnome.

This is all that's needed.
You will have your personal settings for color and more remaining session after session.

This is not about X server Display Configuration but the other settings you find in nvidia-settings
Do not save to xorg.conf from nvidia-settings as all the special settings you may have (Beryl, touchpad etc.) will be removed.
Use the applet for screen resolution in the menu instead

I have read that for some the solution above does not work, and missed the easy solution.
A workaround is to remove --load-config-only
Then nvidia-settings open when gnome starts.
To close nvidia-settings automatically create a hidden file with some name you like in ~. I used ~/.xxx
Add the following to the file:

Code: Select all

#!/usr/bin/env bash
killall /usr/bin/nvidia-settings

Got to the Sessions tab in the menu.
Add a new "Start program" and use the ~/.xxx as target.
nvidia-settings will now close shortly after you see the desktop.
This edit makes Scorp123's remarks below somewhat unnecessary, but they aim at the original posting and are justified.

[scorp123]

Why so complicated?? The "man" page is your friend:

Code: Select all

man nvidia-settings

There we can read interesting things like this:

-l, --load-config-only
Load the configuration file, send the values specified therein to the X server, and exit. This mode of operation is useful to place in your .xinitrc file, for example.

I suggest using that parameter above and taking a closer look at man pages before we freak away users with too complicated suggestions?

BTW, the man page mentions everything. So why do we need to reinvent the wheel when it's already there in the manual?

Code: Select all

3. Loading Settings Automatically
       The  NVIDIA X driver does not preserve values set with nvidia-settings between runs of the X server (or even between
       logging in and logging out of X, with xdm(1), gdm, or kdm ).  This is intentional, because different users may  have
       different  preferences,  thus  these  settings  are stored on a per-user basis in a configuration file stored in the
       user’s home directory.

       The configuration file is named ~/.nvidia-settings-rc.  You can specify a different configuration file name with the
       --config commandline option.

       After you have run nvidia-settings once and have generated a configuration file, you can then run:

            nvidia-settings --load-config-only

       at  any  time  in the future to upload these settings to the X server again.  For example, you might place the above
       command in your ~/.xinitrc file so that your settings are applied automatically when you log in to X.

       Your .xinitrc file, which controls what X applications should be started when you log into X (or startx), might look
       something like this:

            nvidia-settings --load-config-only &
            xterm &
            evilwm

       or:

            nvidia-settings --load-config-only &
            gnome-session

       If  you  do not already have an ~/.xinitrc file, then chances are that xinit(1) is using a system-wide xinitrc file.
       This system wide file is typically here:

            /etc/X11/xinit/xinitrc

       To use it, but also have nvidia-settings upload your settings, you could create an ~/.xinitrc with the contents:

            nvidia-settings --load-config-only &
            . /etc/X11/xinit/xinitrc
...

[nelamvr6]

That worked great! Thanks to both of you!

[Husse]

Why so complicated - published prematurely - and I realize now that I must have been really tired when I pushed the submit button....
Somewhere I read that you needed to start nvidia-settings and I did not check out the --load-config-only
Hopefully we did not freak away users with too complicated suggestions :)
This has been asked more than once and sadly I did not take time to investigate until now - it's simple.

[nelamvr6]

My setting stick now, thanks a lot!

[D-EJ915]

I noticed an easier way (this was on ubuntu but should work since it's just the x config file)...

anyway, just run nvidia-settings as root, you can then "save configuration to file" and it'll never ever change, lol.

[Husse]

@ D-EJ915 No!
That's not it - that's to get the part of nvidia settings you should not! use sticky. The sloution here does not affect the xorg.conf file

[vinoman]

This is edited 2007-07-15
This is a problem that has been around some time
You change nvidia-settings and after the next boot they are back to default.

Nvidia-settings actually keep your customization but must run for them to take effect.
This guide tells you how to achieve this automatically.
In no part of this guide should you be root - no sudo!
In your ~ folder is a file called .xinitrc
~ is an "alias" for /home/your_name
A dot (.) first in a file name indicates it's a hidden file so you must turn on "Show hidden files" to see it. If it does not exist - create it (text file).
Then add the following

Code: Select all

#!/usr/bin/env bash
/usr/bin/nvidia-settings --load-config-only &
exec gnome-session


For KDE use

Code: Select all

exec startkde

The exec command must be the last command.
Make the file executable

Code: Select all

chmod chmod +x ~/.xinitrc

or use the GUI - right click>Properties>Permissions>Make this file executable
For the xserver to use xinitrc you must create a symlink

Code: Select all

ln -s ~/.xinitrc ~/.xsession

This starts nvidia-settings when you start gnome.

This is all that's needed.
You will have your personal settings for color and more remaining session after session.

This is not about X server Display Configuration but the other settings you find in nvidia-settings
Do not save to xorg.conf from nvidia-settings as all the special settings you may have (Beryl, touchpad etc.) will be removed.
Use the applet for screen resolution in the menu instead

I have read that for some the solution above does not work, and missed the easy solution.
A workaround is to remove --load-config-only
Then nvidia-settings open when gnome starts.
To close nvidia-settings automatically create a hidden file with some name you like in ~. I used ~/.xxx
Add the following to the file:

Code: Select all

#!/usr/bin/env bash
killall /usr/bin/nvidia-settings

Got to the Sessions tab in the menu.
Add a new "Start program" and use the ~/.xxx as target.
nvidia-settings will now close shortly after you see the desktop.
This edit makes Scorp123's remarks below somewhat unnecessary, but they aim at the original posting and are justified.

I don't have an .xinitrc file or folder. This is very confusing. Can you simplify these instructions. I just want to set my resolution to 1440x900. It should be so difficult.

[Husse]

@ vinoman
Use the screen resolution tool for that - the nvidia settings are not aimed at resolution
If you read the beginning of the howto it says if youd don't have .xinitrc create it

[vinoman]

The screen resolution tool didn't let me change settings to 1440x900. That's why I did the nvidia-settings. It worked and now my screen is sharp and clear. None of the instructions made much sense to me. Nobody has been able to explain why doing it the way I did it is so bad.

What if I pull out the nvidia card and go with the on-board Intel video? Would it make a difference?

You should be able to set your resolution simply with the resolution tool no matter what video card you have.

[Husse]

You should be able to set your resolution simply with the resolution tool no matter what video card you have.

Agreed - this is a point where work has to be done - and is done

[vinoman]

Will it be offered on Celena?

[Husse]

Not in Celena - but perhaps in Daryna (4.0) There will be a lot of work on x in Gutsy and Daryna will be based on gutsy.
But I fear that for the really odd resolutions you may still have to add them in xorg.conf
You should know this is a problem on Windows too (don't know about Mac)

[lancest]

Desktop Intel 32. I got the Nvidia custom color settings to start at login but lose them after the power management kicks in.

[Stretch]

You should be able to set your resolution simply with the resolution tool no matter what video card you have.

Agreed - this is a point where work has to be done - and is done

Have you guys grandr ? It's in the repositories. It puts an applet in the panel and allows you to change resolutions on the fly.