inxi / pinxi 2.9.00 beta testers!

[Jerry3904]

I got a clean output:

Code: Select all

$ pinxi -F
System:    Host: EB6930p Kernel: 4.14.0-3-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3 
           Distro: MX-17.a5_x64 Horizon October 22, 2017 
Machine:   Type: Laptop System: Hewlett-Packard product: HP EliteBook 6930p v: F.16 serial: N/A 
           Mobo: Hewlett-Packard model: 30DB v: KBC Version 87.2A serial: N/A BIOS: Hewlett-Packard 
           v: 68PCU Ver. F.16 date: 12/08/2009 
Battery:   BAT-0: charge: 35.8 Wh condition: 45.8/55.1 Wh (83%) 
CPU:       Topology: Dual Core model: Intel Core2 Duo T9550 type: MCP L2 cache: 6144 KB 
           Speed: 798 MHz min/max: 800/2667 MHz Core speeds: 1: 798 2: 798 
Graphics:  Card-1: Intel Mobile 4 Series Integrated Graphics Controller driver: i915 v: kernel 
           Display Server: x11 (X.Org 1.19.2) driver: modesetting unloaded: vesa,fbdev 
           resolution: 1440x900~60Hz 
           OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express version: 2.1 Mesa 13.0.6 direct render: Yes 
Audio:     Card-1: Intel 82801I (ICH9 Family) HD Audio Controller driver: snd_hda_intel 
           Sound Server: ALSA v: k4.14.0-3-amd64 
Network:   Card-1: Intel 82567LM Gigabit Network Connection driver: e1000e 
           IF: eth0 state: down mac: 00:23:7d:3f:3e:3a 
           Card-2: Intel Ultimate N WiFi Link 5300 driver: iwlwifi 
           IF: wlan0 state: up mac: 00:21:6a:81:8c:5a 
Drives:    HDD Total Size: 763.85 GB used: 10.57 GB (1.4%) 
           ID-1: /dev/sda model: TOSHIBA_MQ01ABD0 size: 465.76 GB 
           ID-2: /dev/sdb model: HITACHI_HTS54323 size: 298.09 GB 
Partition: ID-1: / size: 76.40 GB used: 10.57 GB (13.8%) fs: ext4 dev: /dev/sdb1 
Sensors:   System Temperatores: cpu: 33.0 C mobo: 31.3 C 
           Fan Speeds (in RPM): N/A 
Info:      Processes: 177 Uptime: 9 min Memory: 3.70 GB used: 676.3 MB (17.9%) Shell: bash 4.4.12 
           pinxi: 2.9.00-341-p 

See a typo: "Temperatores" for "Temperatures".

[h2-1]

yes, those are the types of bugs I'm looking for.

Those are all due to assumptions I'm making about data being present, which is present in all my test systems, which is why beta tests with test systems that are not mine are so valuable.

Just fyi, when you see those types of unitialized errors, you'll see them BEFORE the item that is wrong, not after. So those belong to the subsequent line.

If you feel inclined, run; pinxi --debug 21
which will run and then upload the debugger data to my server.

[h2-1]

Temperatures fixed, thanks for spotting that. Rewriting sensors was hard, and I dreaded it, and did it basically in one big session, so no surprise I made typos.

[richb]

........................
If you feel inclined, run; pinxi --debug 21
which will run and then upload the debugger data to my server.

Done.

[h2-1]

richb, 0342-p should fix those. That's the kind of thing I expect to see, uninitialized values in data that in all my test systems was initialized so I failed to do tests on valid for them.

kmathern, your bug is harder to figure out, that comes from the early pinxi tests to determine what it's running in, which run before the options, and thus before the logging starts, and before the updater runs.

Obviously again, I"m assuming a value is sent to that function, and in your case, it's not. I can figure that one out though just by logic I think.

[h2-1]

kmathern, a few questions and I think I can figure it out:

1. what is the shell you are running pinxi in? that is: echo $SHELL
2. what is the console client, like, xterm, gterm, etc.

That should do it, I think I know where the error came from.

I found the issue, I was sending the parameters in the wrong order in the case where the shell is not defined in my list of shell data. Since I never hit that case, I never discovered that bug.

Good bugs!!

Basically, I can fully resolve the issue for your shell with:

I have: bash/csh/dash/ksh/tcsh/zsh handled in theory, unless there is a bug in one of their data sets.

[richb]

Version 0342-p did fix it. Fast response!

[kmathern]

kmathern, a few questions and I think I can figure it out:

1. what is the shell you are running pinxi in? that is: echo $SHELL

Code: Select all

$ echo $SHELL
/bin/bash

2. what is the console client, like, xterm, gterm, etc.

xfce4-terminal (version 0.8.0)

[h2-1]

richb, I don't want to waste anyone's time, so if someone takes the time to test, I should at least take the time to figure out the issue asap.

kmathern, does the issue show when you run: pinxi -Fxxx

My first guess was not right, though there was a bug there anyway.

[richb]

Thank you for the opportunity to test. As you probably know we recommend that users asking for help use inxi and it is written into our Forum help documentation. It has been very useful to us in helping to solve users issues.