vamdolly wrote:Question as im still new to this is there a way to revert back to default encase this has a worse effect for me, as i have tearing on my lenovo thinkpad t430 after updates were installed from clean install.
Let me answer this by way of posing a question.
Why is the behavior of your computer (relating to the screen tearing issue) different now than it was before you followed my directions?
To answer this question "correctly", let's look at how the OS works in this particular situation.
The first step I gave you was to create a new file (into which subsequent directions had you add content). At no point did I give you an instruction to modify, in some way, an existing settings file, even including a modification for it to go looking for
the file I actually did
have you create.
By logic and plain reason alone, what should this suggest to you? It should suggest that there must be some central, system-level function which says, "look into this particular folder, see what files are there, and if any of them have settings relevant to detected hardware, then use those settings instead of (or in addition to) the default settings".
Sorry, I know that's a long-winded way of explaining it, but basically, that's what's going on.
The file you created has Intel Graphics chipset-specific settings. If you had specified some other make-believe hardware, then nothing would have happened because said hardware was never discovered on boot (because, of course, it doesn't exist.)
If you were to delete the file, it would stop using those settings.
... there is an alternative option for you.
It is the convention of settings files such as the one my directions have you create, that if you begin a line with the "#" character, it is treated as a comment, and not as any sort of executable instruction. Therefore, you can simply re-edit the file and add # characters to the beginning of each line, save the file, and restart the computer. At that point, the file will be read, but everything in it will be a comment, and therefore ignored.
This is sometimes referred to as "commenting out" a line, and it has the added benefit that, if you were to eventually find the problem you were having was something else
, instead of having to reconstruct the file (and hoping you could find these instructions again) you could merely de-comment the lines, save the file, reboot, and voila! everything would be back the way it was again.
Peoples of the universe, please attend carefully: the message which follows is vital to the future of you all.
Presently rocking Linux Mint 19.1 Cinnamon.
Remember to mark your fixed problem [SOLVED].