I have found that the method of adding lines to different x11 configs was ineffective in my case. As an alternative, I created a bash script that applies my settings automatically at login. Simply enough, I just grabbed what I had changed from the saved xconf
file, which essentially gets us to the desired end. It isn't the most elegant method, but it works...
The file below is my settings for my monitors, you will need to put your own info over mine.
My personal solution was to add these lines directly to .bashrc
:
nvidia-settings --load-config-only
nvidia-settings --assign CurrentMetaMode="DVI-I-1: nvidia-auto-select +0+54, HDMI-0: nvidia-auto-select +1600+0 {viewportout=1792x1008+65+30}"
My original and valid answer was edited to suggest putting it in a separate file and instead of calling the file in .bashrc
. Both are valid. However, I wanted the answer to reflect both methods.
An example bash script:
# Save this to some script.sh
nvidia-settings --load-config-only
nvidia-settings --assign CurrentMetaMode="DVI-I-1: nvidia-auto-select +0+54, HDMI-0: nvidia-auto-select +1600+0 {viewportout=1792x1008+65+30}"
Next, edit .bashrc
or .bash_profile
(whichever you prefer) and add your script there so it runs automatically on login.
Lastly, make your script executable with chmod +x script.sh
Best Answer
Are you using KDE? I had this problem the other day, and
systemctl stop/disable packagekit
didn't help at all.Here's the prompt:
In this example, polkit.subject-pid is PID 2201, which is:
Which suggests that KDE might be doing something. On my system, KDE doesn't have package management settings in the system settings tool, but opening apper's settings menu I found this:
Setting this to Never took care of the problem for me.
Update:
systemctl mask packagekit
works as well. See for example http://0pointer.de/blog/projects/three-levels-of-off, which describes the difference between systemctl stop, disable, and mask. mask makes services completely unstartable until they areunmask
ed again.