aboutsummaryrefslogtreecommitdiffstats
path: root/inxi.changelog
diff options
context:
space:
mode:
authorLibravatarUnit 193 <unit193@unit193.net>2022-04-09 01:09:44 -0400
committerLibravatarUnit 193 <unit193@unit193.net>2022-04-09 01:09:44 -0400
commitbbc572edbd9b44a1aa4c69425d57783bf5c3b0fc (patch)
tree43c2f8f0d13e27c6eac7740294b12aee4b045d01 /inxi.changelog
parentb3d3db76149121bb0937e7d06c5dbba68d8e1b6b (diff)
parentb9fb50643c0806c57385816761cca8170826c1bf (diff)
Update upstream source from tag 'upstream/3.3.15-1'
Update to upstream version '3.3.15-1' with Debian dir f399cc483433aaa6a5d5614379e6f7597a44161f
Diffstat (limited to 'inxi.changelog')
-rw-r--r--inxi.changelog142
1 files changed, 142 insertions, 0 deletions
diff --git a/inxi.changelog b/inxi.changelog
index 0dace8a..23acbdb 100644
--- a/inxi.changelog
+++ b/inxi.changelog
@@ -1,4 +1,146 @@
================================================================================
+Version: 3.3.15
+Patch: 00
+Date: 2022-04-08
+--------------------------------------------------------------------------------
+RELEASE NOTES:
+--------------------------------------------------------------------------------
+
+Bug fix, it's a bad edid data bug, rare, but when it trips, kills inxi execution
+dead right before -G/Graphics shows. Also some nice fixes and enhancements.
+
+--------------------------------------------------------------------------------
+KNOWN ISSUES:
+
+1. Possible case of Gnome Wayland failing to set any gnome environmental
+variables, making wayland detection not possible. This was in anonymous dataset
+inxi-proBook4540s dataset. Person never appeared in real life so can't follow up
+on it. This cascaded down to other failures in display detection, and desktop
+detection, though in theory much of the data needed was present. I expect
+similar issues may appear with kde wayland. This is/was probably a configuration
+or build error I believe, though not enough data yet.
+
+It appears that sudo start disabled the display environmental variable
+detections, which is unfortunate, and the fallback loginctl tests do not appear
+to work for unknown reasons. I've confirmed this on Fedora stock Gnome as well.
+
+--------------------------------------------------------------------------------
+BUGS:
+
+1. Forgot to test that return from get_display_manager is array ref, this
+impacts only a tiny handful of distros probably, TinyCore was one, but it is a
+fatal failure, so fixed it. Never trips in console, only on tiny linux where no
+dm is used at all. Tripped with Xvesa, seen other bug reports, but not enough
+data to know for sure.
+
+2. EDID errors and warnings had several bugs, errors a fatal critical bug which
+made execution stop. Had forgotten to pass the $edid hash reference to the error
+constructor. Also had used wrong hash key in output so would never have shown.
+
+--------------------------------------------------------------------------------
+FIXES:
+
+1. Corrected ram device indentation levels.
+
+2. Made memory width more clear with: width: data: total: which more
+accurately reflects the source data. Also in cases where no data or total
+values, only show width: N/A, not the data: total: sub items.
+
+3. Made edid errors/warnings output to numbered list of warnings/errors instead
+of using join() to made one long list. Much more consistent that way. This fixes
+issue #266 - thanks SheridanOAI for finding this bug.
+
+4. In --slots, -x wasn't loading the bus ID so it showed N/A, unnecessary data
+collection granularity, removed.
+
+5. For Display, if no X or gpu driver, show: driver: N/A. Showed driver: gpu:
+N/A before.
+
+6. For Display, remove filters for Xwayland tests, we always want to see
+xwayland data if it's installed. This was actually an error to not show it since
+display_server_data already had the correct tests to not redo Xorg data if found
+previously, which would be glxinfo based data. This is a partial fix also for
+Known Issue 1, at least we'll see Xwayland is present even if Wayland detections
+failed for unkonwn reasons.
+
+7. Added some ram value dmi filters, found some that had 'none' or 'unknown'.
+
+8. Show display protocol out of display!! Also handles most common root use
+cases as well, so in most cases, if the initial protocol detections failed, this
+will result in a decent attempt, though if root it is less reliable. sudo or
+regular user will be fine since looks for not tty/pts TTY type and username.
+
+This should also help narrow down Known Issue 1 failures, though there are more
+cases to be dealt with, but can only chip away since not enough data.
+
+9. Made info: item in slots more robust, and able to handle more diverse
+scenarios.
+
+10. Added alternate syntaxes for dmidecode permissions errors.
+
+--------------------------------------------------------------------------------
+ENHANCEMENTS:
+
+1. Added brzdm clogin mlogind xlogin display managers. Not verified. Version for
+brzdm is probably like slim since brzdm is a fork of slim.
+
+2. Added voltages to ram module report, that had been left out. Note that it's
+common for voltages to be either 'unknown' or not present at all. This is as
+close as inxi can get to handling issue #265 since there is no other source for
+the requested data type (show DDR3L, low voltage DDR3, which doesn't exist as a
+type in dmidecode).
+
+3. Added voltages to --slots report, --slots -xx. Only shows if present.
+
+4. Added for --slots -a for Linux, if detected, the PCI children of the bus ID
+of the slot. This is recursive, so supports as many levels as are present,
+though it would be rare for there to be more than one level of children.
+
+--------------------------------------------------------------------------------
+CHANGES:
+
+1. In -m ram report, moved ram type before size/speed/voltage, that makes more
+sense.
+
+2. Also in -m ram report, make type: the default value (was an -x options
+before), which contains the no module found messages etc, making the order:
+ Device-1: DIMM 0 type: no module installed
+ Device-2: DIMM 1 type: DDR4 size: 16 GiB speed: 2400 MT/s
+
+This puts all the speed/size/voltage data together, and stops putting the no
+module found message in speed, which never made any sense.
+
+2. In -m, changed width data to more clearly reflect the data source:
+ width (bits):
+ data: 64
+ total: 72
+
+--------------------------------------------------------------------------------
+DOCUMENTATION:
+
+1. Man page, added a TABLE OF CONTENTS section which lists all the primary
+sections. Can help since the man page has gotten so darned long and man doesn't
+as far as I know support clickable internal links, sadly.
+
+2. For -m, updated for revised output syntax and -x levels. Note that the help
+and man actually had the type: as default for -m, not -mx, but for some reason,
+the code had it wrong. Oops.
+
+3. For -m, fixed some legacy output syntax in the examples.
+
+--------------------------------------------------------------------------------
+CODE:
+
+1. Some refactors of slots, ram, as well as a bit more refactoring of edid stuff
+for graphics.
+
+2. Added $ENV{'DISPLAY'} to debugger data collector, no idea why that was left
+out.
+
+--------------------------------------------------------------------------------
+-- Harald Hope - Thu, 8 April 2022 22:46:26 -0700
+
+================================================================================
Version: 3.3.14
Patch: 00
Date: 2022-03-24