Hummmmm. Just for FUN I went over to jaguar my "test bed" on which I just installed inxi-3.0.14-1.el7.noarch the other day and ranh2-1 wrote: ↑2018/07/18 17:42:35As I suspected, you do have a corrupted inxi.conf file.
All the values you posted where the config item value is ='' are corrupted, those should never have been there in the first place.
Each of those config item rows should be one of the two:
1. commented out with #
2. deleted
My main concern is that CentOS or Redhat created this corruption for some unknown reason, and that this is the standard content of the packaged config files, which you can easily check by deleting all the config files, then uninstalling the package, then reinstalling it, then checking the config files again.
If the problem persists, this is a bug with the packaging of inxi, and should be reported to the appropriate packager.
While I've updated the checks to look for such errors in the config, that won't help users who are running pre inxi 3.0.19 versions, which hasn't been released yet, and probably won't be released for a few weeks since I've just released a small herd of inxis over the past weeks, but I may have to do one more to make sure this issue is corrected so that downstream can update.
It's always hard as a programmer to visualize the entire set of things that can be done wrong, and this error simply was not in the set of things I'd considered as a possible mistake end users or packagers would make, nor has it ever shown up previous to now, but that's why I now and then check online inxi reports, to see if any unknown and to me unreported issues are arising.
Note that as far as I can tell, the Fedora packaged inxi version does not have this issue, and I assume that's where the EPEL or other 3.0.14 etc versions are coming from, so I have to suspect a CentOS or Redhat specific config, though why that would exist is beyond me.
Code: Select all
locate inxi.conf
BTW just for fun I restored the old backup files and deleted out the " marked lines and left ONLY the line that said "DEFAULT_COLOR_SCHEME=28" to see if I could set the COLOR.... Nope that did not work. I went back to jaguar and tried to set the default color there too... Nope that did not work either. the ONLY apparent way -- at least that I could find so far -- is to set color at the same time you set the other options (?) such as i, S,C,s,w. Something changed between the two versions. If you know some way to set the default color scheme please let me know. I'll try to hack around and see if I can stumble across the solution, though without a .conf file that is recognizable that may be a tall order. Probably easier to set color as an option and be done with it.