inxi, error "Use of uninitialized value $val2"

[psl]

Ubuntu 18.04
inxi 3.0.32-00 (2019-02-07)

Desciption:

"inxi -F" reports an error, when it runs from pure text console. Can be simulated with "ssh localhost", ssh localhost -C "inxi -F")

$ inxi -F
...
Sensors: System Temperatures: cpu: 34.2 C mobo: N/A
           Fan Speeds (RPM): N/A
Use of uninitialized value $val2 in string eq at /usr/bin/inxi line 5759.
Use of uninitialized value $val2 in split at /usr/bin/inxi line 5764.
Use of uninitialized value $val2 in concatenation (.) or string at /usr/bin/inxi line 5766.
Use of uninitialized value $val2 in concatenation (.) or string at /usr/bin/inxi line 5767.
Use of uninitialized value $val2 in concatenation (.) or string at /usr/bin/inxi line 5768.
           GPU: device: temp: N/A device: radeon temp: 40 C
Info: Processes: 218 Uptime: 4m Memory: 15.64 GiB used: 986.2 MiB (6.2%) Init: systemd
           runlevel: 5 Shell: bash inxi: 3.0.32

When it runs from terminal in X-Windows, there is no error:

$ inxi -F
...
Sensors: System Temperatures: cpu: 34.4 C mobo: N/A gpu: radeon temp: 42 C
           Fan Speeds (RPM): N/A
Info: Processes: 201 Uptime: 9m Memory: 15.64 GiB used: 1004.6 MiB (6.3%) Shell: bash
           inxi: 3.0.32

[Harald Hope (lontact)]

This version of inxi is obsolete, inxi is on version 3.2.02 right now.

Bugs like this are only meaningful if the poster downloads current inxi and reproduces them on current release. I believe the ssh -C bug was fixed quite a while ago.

[Harald Hope (lontact)]

Note that the option --tty also often takes care of these issues, that was added before 3.0.32, though I'm not positive about which bug this user has, but they can trivially verify by simply testing on current inxi, if it goes away, the bug was fixed long ago.

[Sean Davis (bluesabre)]

Is this still an issue with a recent supported release (focal, impish, jammy)?

[Harald Hope (lontact)]

Current inxi release is 3.3.13.

What is 'this' referring to? Never use the term 'this' when discussing technical issues, it does not narrow it down enough to convey meaning. Rather than ask if 'this is still an issue', why don't you test it and see?

The bug reported here is 50 to 100 releases of inxi ago. jammy has 3.3.13 as of now. An undefined data bug would have been fixed immediately once detected and reported.

I believe this issue was closed ages ago, and if not, it should have been. Did you possibly post in the wrong bug issue? If you have a new issue, then file it as such, but make sure you are talking about current inxi, from the github master branch, not a legacy unsupported version.

[psl (slansky)]

I still see the problem at system with Linux Mint 20.1.

$ inxi -V
inxi 3.0.38-00 (2020-03-14)
...

$ ssh localhost -C "inxi -F -c0"
user@localhost's password:
Use of uninitialized value $pid in concatenation (.) or string at /usr/bin/inxi line 5207.
Use of uninitialized value $konvi in substitution (s///) at /usr/bin/inxi line 5208.
System: Kernel: 5.4.0-90-generic x86_64 bits: 64 Console: N/A Distro: Linux Mint 20.1 Ulyssa
...

[Harald Hope (lontact)]

That version is about 100 releases old, it's not my fault linux mint refuses to ship a current inxi. File a bug report with linux mint where it might do some good, not here, the ubuntu version in Jammy is current, and hirsute and impish both have 3.3.0x inxi versions as well. Mint failing to update isn't an inxi bug, it's not an ubuntu bug, and its not a Debian bug, it's a Mint bug, so file the issue there, ask them to update inxi, god knows I've tried doing that enough times to finally give up on trying anymore, but maybe more voices will get them to stop shipping that antique inxi.

[Launchpad Janitor (janitor)]

[Expired for inxi (Ubuntu) because there has been no activity for 60 days.]