Instead of retyping UUIDs to withhold them from public divulging (@myswtest, who cannot be private messaged), use a more excluding filter selection. From inxi’s man page. :
-z, --filter
Adds security filters for IP addresses, serial numbers, MAC, location (-w), and user home directory name. Removes Host:. On by default for IRC clients.
--za, --filter-all
Shortcut to trigger -z, --zl, --zu, --zv. All the filters, that is.
--debug 22
Automatically uploads debugger data tar.gz file to ftp.smxi.org, then removes the debug data directory and the tar.gz file. See --ftp for uploading to alternate locations.
This amounts to a sort of bug report to submit in case you think inxi is doing something wrong, although inxi does have its own bug tracker. You can additionally add --debug-id <description> to suggest why you sent it, though mention to its author on his forum or at irc.oftc.net or his email would be welcome, and means to give you feedback or simply thanks. If your hardware is new, the submission may contain data valuable for inclusion in an upcoming inxi release.
Another: /etc/inxi.conf can be used to enable your favorite inxi options, and disable packaging options. Mine turns off colors.
Thank you for sharing this information. What type of damage can be done with bad actor seeing the UUID?
I will attempt to setup an inxi.conf file. The default appears to be blue fields with white text entries. I think having one complete color may be more difficult to review. Something besides blue would be welcome for change here.
I have been noticing (3 weeks approximately) that sometimes Display: Unspecified instead of Display: Waylandis shown when inxi -GSaz is passed. This just happened again.
Also, is it ok to continue to ask questions about inxi here?
If so then passing inxi -c 99then can change the color scheme.
An excerpt from the output below:
Simply type the number for the color scheme that looks best to your eyes for
your global settings and hit <ENTER>. NOTE: You can bring this option list up
by starting inxi with option: -c plus one of these numbers:
94 - console, not in desktop - Not Set
95 - terminal, desktop - Not Set
96 - irc, gui, desktop - Not Set
97 - irc, desktop, in terminal - Not Set
98 - irc, not in desktop - Not Set
99 - global - Set: 6
I am not understanding the differences meant between the following listed item areas: console VS terminal VS in terminal not in desktop VS desktop
G reports cannot be complete when not from from a GUI login, and may differ whether run by ordinary user or with superuser permission.
The right places for questions not already answered in the FAQ would be the comment #1-indicated IRC and forums. IIUC, feedback from Wayland users has been minimal, and since its author doesn’t use Wayland, Wayland reporting has been one of its shortcomings, and thus debug data submissions from its current version users is welcome.
I have no knowledge about its color settings beyond GLOBAL_COLOR_SCHEME=0 in /etc/inxi.conf to turn them off.
Leap users should not report problems, unless they have used the -U switch to upgrade, or have otherwise upgraded to the current version or installed manually from upstream, and keep current. 15.6 is currently 12 versions behind, 16.0, 3 behind. Inxi can be manually installed from upstream using these instructions. Both -I and --vs report current version.
Inxi is a perl script. Programmers are free to offer patches.
Looking a bit more deeply into this. On a machine here (Tumbleweed), there is no /etc/inxi.conf file. Passing inxi -c 99excerpt from bottom of the output is as follows: Your selection(s) will be stored here: /home/username/.config/inxi.conf
So where is the change to the inxi.conf storage location being implemented at in the OS development chain? This would be interesting for me to know, (so that other programs which exhibit subtle nuances) such as this. I can know where to look to correct the issue.
Maybe this is done in Open Build Service when source is compiled to binary?
You can also override, per user, with a user configuration file found in one of the following locations (inxi will store its config file using the following precedence):
if $XDG_CONFIG_HOME is not empty, it will go there, else if $HOME/.config/inxi.conf exists, it will go there, and as a last default, the legacy location is used), i.e.:
For too long to remember, /etc/ has been a place where an admin puts global configuration customization (for all users), likely since before Linus released his first kernel, in Xenix and Unix, while ~/.config/ has been a corresponding location for individual users.
@panorain it’s not a binary and there is no /etc/inxi.conf installed on purpose, /etc is for the system administrator and manually create if they so wish.
Hi, are you aware if there is a way to obtain the serial number on a Sceptre E225W-FW144G display monitor without physically inspecting the S/N tag on the back of the display monitor?
When I pass inxi -GSaz --vs --za I do see information displayed in the Monitor-1: category but no serial number.
Besides inclusion in inxi -Gxxx, inxi -Ga, & inxi --edid outputs, hwinfo --monitor works on at least some if not all of my displays. None are Sceptres.
Are there ROM or related updates for monitors?
In a situation such as this should the manufacturer be contacted perhaps?
Perhaps this is off topic due to discussing hwinfo results.
