CentOS

inxi should not have pulled in impitool as a required program. It should have been a recommended optional program, since it's only relevant on the few systems out there that actually have ipmi. That's a packaging oversight, best handled by having the maintainer change ipmitool to a recommended or su...

Thank you for following up/through. We've all done the set it and forget it, lol, so I had to start suspecting that was the case. However, with this said, there was a bug in the inxi color setting logic, and that bug was a real bug, which was selecting non global value would fail to delete global, e...

the 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 report...

Just as an aside, I personally like the inxi colors, and they are the first things I usually set on a new system I'm testing on, so I use this color selector a lot, though I don't generally use the global option, which is how I missed that particular bug. By definition these are usually new systems ...

I just tested, removed /home/user2/.conf/pinxi.conf tested, it's gone, colors return to default. Run pinxi -c 95 as user2, select a color, it switches, writes it to a new config file, run pinxi again, and it's all fine, new colors. cat /home/user2/.config/pinxi.conf VIRT_TERM_COLOR_SCHEME=31 this pr...

Just to clarify, because I think there is some confusion, aside from the global/specific color scheme reset bug: 1. a global color scheme in /etc/inxi.conf will override all subsequent user configuration values, unless one of them is also global. 2. a specific color scheme in /etc/inxi.conf will ove...

Your case did expose an actual bug, as I noted, what was supposed to happen when you selected a color scheme that is not global, it was supposed to unset and remove the global color scheme, for the user config file in question. This was not happening, only global was removing all other color schemes...

$status{...} is just setting the print values for output. I'd forgotten about that, but in fact, it was already telling you/me that global was set, as it should have. But the meaning of that is not sufficiently clear, that is, if global color is set, then you must unset the colors completely, and, i...

Thanks for following up on this. When you set the colors, whether you do it manually by editing the inxi.conf file, or if you use the inxi -c 94-99 color editor, if that color is set for the user you are running inxi as, it will use those colors. After checking, I found that the feature that was sup...

As 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 th...