[Smack head!!!] Yep that inxi -c 95 color selector followed by a number (26) fixed the problem... and created a NEW inxi.conf file under /home/cat/.config/inxi.conf. . A review of the contents of the file show:h2-1 wrote: ↑2018/07/19 07:25:52the reason that that the only file that seems to do anything is /usr/bin/inxi is that is the program. It creates, under normal circumstances, and I stress normal as in always in correctly configured systems (with one exception, chromebooks, which have a messed up permissions situation, a user reported that issue to me a while ago but I can't change that), a configuration file if one is not there when you run the -c95 color selector for your gui terminal window colors, and it tells you the path, you have to open that file, read it, and if it did not get created after you set the colors, you have to check the permisssions on that directory, which is usually .config/ and figure out why you failed to be able to write to it, as in, creating and updating a new file.
Again, don't worry about what you believe inxi is doing, worry about the configuration file, and if it's getting created and updated, or not. If not, then worry about your system permissions, and why they are broken. Also, after you create the configuration color selection, run: updatedb as root then locate inxi.conf to find where it is, in case something weird is going on.
Note that when inxi starts, it determines the preferred path the config file shouild go to based on tests, and that path is what the color selector tool tells you is the path, so that's the file inxi is going to write to and read from.
Code: Select all
Probably a bad case of "Set it and forget it": One forgets how one did something a few years ago... until something goes wrong. Will pass this along to my buddy.
Thank you for all your help.