With max performance change in XServer the problem is gone too…
There is no way to save the settings so what is the point of changing them? It keeps telling the path is write protected.
Huh? I can save it without problems.
Btw. nvidia response to this bug last week ago and we may will see a finally fix for it soon… if we have luck in the next driver update.
Edit:
Which file you try to overwrite?
I dont see how that would help me. It is the same with Kubuntu, When I try to save the xserver-settings I get the message “unable to open x config file /etc/X11/xorg.conf for writing”. Maybe because there is no such file at this path?
If it is indeed the driver then I wonder why I have no flickering on Kubuntu.
As far i remember… 3years ago with my first steps in Manjaro i was running into the same issue and i open xserver with sudo… to save the file (overwrite) because of missing adminrights…
Someone told me later that its not a good idea (atleast normaly) for GUI Applications…
So i dont know if this is the recommend solution for your issue now, but i think this was helping me in the past.
You only have this flickering in Manjaro? And you using the same driver in Kubuntu?
I am not so good with console thus I dont know howto start the x-server console via sudo.
sudo nvidia x-server settings didnt open it 
Tbh. I am just always updating to the latest driver. No clue which one is running on Kub but it just updated recently. But I remember I had that flickering for a while on Kub too until it went away. Until it disappeared on Kub II kinda blamed the firmwareupdate of the monitor because I thought the flickering started with that.
without the - ?
try
sudo nvidia x server settings
sry i dont want to start it when i dont have to… because its resets my colour profile when i open xserver without a reason xD
on Kub is running 525.125.06, but the previous versions caused no flickering as well. Afair it started somewhere in March or April and ended like a week later on Kub. But on Manj it never stopped 
Ye with the “-” I typed it like it was named, I should check the package name I guess.
sudo nvidia x server settings gives “command not found”
no wonder… 525 was running fine with Manjaro too, the bug was introduced with 5.30 release.
Odd considering I have been having that flickering since early this year.
I did not expect Kub to be so far behind, but it seems to be a good thing in this case because that flickering really irritates me.
I created this Topic on 31 March:
So your nvidia Kubunto driver was pretty long not refreshed… good for you… but it was easy to fix it with a grub command… that its no longer working since 1 month
my bad it was:
sudo nvidia-settings
Thats the odd thing. I get nv-drivers like weekly with the auto-update. But since they are soo far behind maybe they rolled back because of the flickering?
I have to admit that I do not pay attention to the version even when I see that there is an update.
sudo nvidia-settings worked thanks but saving the settings still prompted the same error message.
Im actually think so.
Maybe try to save this file in your home folder somewhere or even better create a new file that you dont have to overwrite it?
It was 3years ago… i really not 100% sure how i fixed that
1 Like
There is nothing to overwrite. Like I said before, there is no such file in the path suggested by x-server settings.
I thought settings files had to be at the suggested path to work thats why I never tried to save it elsewhere.
The icing on the cake is, when I try to save it in my documents folder it asks for the pw and then again prompts the same error message… This is disconcerting.
I found this old video guide again 
Im actually dont have this 20-nvidia.conf saved that he recommend, but maybe it helps.
Im just happy that it works for me, so i dont want to mess around to much with my system.
If this guide dont help, i will look deeper in my system.
1 Like
No matter what name, what destination I keep getting the same error. Sudo or not sudo makes no difference either.
I also tried creating the file first but then it just adds the word “parse” to the error.
Those are the days when I really hate Linux.
Really strange, i cant remember i run this heavily into issues as i was new to Manjaro and was fighting the nvidia xserver
Are you using KDE too, maybe there is a differend issue because you have xfce?
There are other options also, like merge and preview… did you try them out yet?
I also recommend to create a timeshift backup befor you run in other problems when messing around… just in case.
Edit:
Wait a second… you only change Powermizer right?
Or do you change something else? So you only have to click on the Quit button.
There is no file save request for me… only when i do changes with my Monitor:
Where is also a button called Save to X Configuration file, where you run into this problems right? You don’t have to save your settings with that button for Powermizer.
1 Like
KDE
Preview said it created the config file. Since I dont know where or it’s name I wouldnt know if it did. Certainly not using the name the app suggests.
Merge is greyed out.
I am activating “Force full composition pipeline”
Quit saves it just for this session. I wish it wouldnt be disabled after every restart. It is pretty retarded.
I just see you had created your own topic 3 hours before, not sure it was a good idea to talk about all this problems in this topic here… maybe we should swap there… Anyways…
So your actual problem is not this changes got instant rejected, your actually main issue right now it is not loading again after a system restart… right?
1 Like
Yes.
Since the flickering is a driver bug my “flickering thread” is obsolete I guess. I forgot to delete it (if that is even possible) yesterday evening.
Trying to change/save/reload the settings via bash files might be nice but I’ve never used one of those and ofc failed But I answered there anyways