Diffstat (limited to 'inxi.changelog')
1 files changed, 181 insertions, 0 deletions
diff --git a/inxi.changelog b/inxi.changelog
index 89a8c18..eb5a208 100644
@@ -1,4 +1,185 @@
+New inxi, new man. Huge update, new line types, huge graphics upgrade, new
+switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
+Note that since this features a new primary line item (-j / --swap Swap:),
+the version number has been bumped to 3.1.0, making this a major version
+upgrade, the first since the new Perl inxi rewrite was launched, though of
+course 3.0.0 contained many new line items as well, but this is the first
+actually new line item since then.
+1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
+directory, the partitions would buggily duplicate in the output.
+2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
+because it was using the wrong Xorg log, it was only searcing in the original
+/var/log/Xorg.0.log file, not the newer alternative path locations.
+1. Both an enhancement and a fix, users reported Xorg log file location changes.
+Fix is that now inxi uses wildcard searches of all readable locations that can
+contain the log files, then collects a list of them, and uses the last modified
+one. This ensures that the best possible guess is made about which actual
+log file is current, which should lead to significantly more reliable Xorg
+driver reports overall.
+Note that this fix works for user level and root level, it will always use the
+most recent readable file no matter what. For root, that should translate to
+the most recent on an absolute level Xorg log file. This issue was caused by
+gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
+also, the location is often but not always now:
+~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
+root has to search for all user Xorg log files to find the most recent one.
+There were many red-herrings in this issue report, so it took some research to
+dig through those to the real data sources.
+2. Now that the compositor detection is out of early testing mode, enabled
+always on compositor detection for Wayland systems. Since the compositor
+is the Wayland display server, it makes sense to always show it if Wayland.
+Note that there is still no known way to actually reliably get Wayland data
+beyond simple environmental variables that let inxi detect Wayland is running
+the desktop. Lack of reliable logs or debugging tools across Wayland compositors
+makes this entire process about 10-50x more difficult than it should have been.
+3. In keeping with 2., also moved compositor: item to be right after server:
+4. Debian bug:
+requested that HTTP::Tiny be set to default always check SSL certificates.
+Now inxi does that, and --no-ssl flag disables this, which makes the Perl
+http downloader now work roughly the same as wget, curl, etc.
+5. Man page fixes, added pointer placeholders for out of alphabetical order
+options, so you can find anything by looking down the alpha sorted lists, like:
+--swap - See -j. Since inxi is running out of single letters that match new
+features, it's easier to point man readers to the right item without them
+having to already know it to find it. Also added --dbg [2-xx] pointer to
+github inxi-perl/docs/inxi-values.txt so people interested can learn how to
+trip the various per feature screen debuggers.
+1. updated ubuntu ids, added 'focal LTS'.
+2. USB Graphic devices added. This will add support for USB graphics adapters,
+an uncommon but existing category, often used in SOC boards, for example, but
+also on desktops, and things like USB webcams. Leaving these off was really
+just an oversight, the programming internally had the data, it just wasn't
+3. Support added for TV card type multimedia devices in Graphics. That was
+actually a long term oversight, I'd simply missed that in the device ID
+documentation, one of the multimedia device subtypes is Video device.
+4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
+technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
+Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
+but if xrandr is missing, the Screen information shows.
+Technically for -G, -Gxx, end users see very little difference except the per
+Screen / per Monitor resolutions are listed with a 1: type counter per item.
+Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
+out of the pieces of hardware that make up the Screen space. In many cases,
+1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
+New output items:
+Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
+Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
+Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
+s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
+s-diag: [diagonal of Xorg Screen size]
+Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
+hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
+from actual monitor resolution/size; size: [actual monitor size in mm (inch);
+diag: [actual diagonal size in mm (inch).
+4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
+section for -G.
+5. Big improvement in error messages and logging for Xorg driver detections,
+this logic is much more robust now, but after the main driver fix, also much less
+likely to ever be seen.
+6. Almost not visible to users, but major internal graphics refactor allows now
+for more modular treatment, and eventual Wayland data sourcing. Currently
+most Wayland data sourcing is in stub form, or only logically possible, but
+as it grows possible (if ever, since Wayland protocal appears to have totally
+neglected enforcing single location logging, and single tool debugging for
+the entire Wayland protocol of compositors, a massive oversight in my view).
+The -Ga refactors internally made this much more possible, and I integrated
+switches and tests, and fallbacks, and stubs in some locations, so it was
+clear where current Xorg specific logic is, and where future Wayland logic
+will fit in, sort of anyway.
+7. Debugger tools added for new features, or most of them.
+8. New primary line item: --swap / -j. This moves all swap data to a dedicated
+Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
+is used, all swap types, not only physical partition swaps, show. This should
+make some users happy.
+9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
+Intel cpu family ids in terms of cpu arch name tool.
+10. By request, added ability filter out all UUID or Partition Label
+strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
+--filter-uuid. Mostly useful in fringe cases, for example, replacing
+label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
+or in cases you want to show full -v8 output without showing UUID or Labels,
+11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
+dig in cases where dig is installed but failed due to maybe network firewall
+rules or something, and WAN IP detection fails. Normally you always want
+to use dig, it's faster, more reliable, and safer, than all the other regular
+downloader based methods, but we have seen server setups where for some reason
+those types of dig requests were blocked, thus disabling WAN IP detection.
+12. Added in WAN IP failure case, if dig was used, suggestion to try
+again with --no-dig, since most users are unlikely to learn about this issue,
+or the solution to it.
+13. Added single letter shortcut -J for --usb, maybe this will help people
+discover usb component of inxi, now you can request for instance: inxi -FJaz
+14. Added xonsh to supported shells, that had tripped a perl undefined value
+for start client bug since xonsh uses single word for version, xonsh/234
+so the default value, 2nd word, was undefined.
+15. More SSD and USB drive vendors from the endless fountain over at
+Linux Hardware Database (linuxliteos.com).
+1. Small change in how screen resolutions are output in -G non -a mode,
+now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
+This helps make it more readable. Note that in non -a mode, the increments
+are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
+Most users will only have one Screen systems, but more advanced setups may use
+the Xorg > 1 Screen, each screen able to run > 1 monitors.
+The counts in say, a 2 Screen system, with 3 monitors, would be:
+1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
+3: res3 [from screen 1, monitor 1.
+If xrandr is not installed, it would show:
+1: res1 [from screen 0] 2: res2 [from screen 1]
+-- Harald Hope - Wed, 22 Apr 2020 19:33:56 -0700