In gsettings, I can see environment information in “System” → “About”:
However, when using ssh (which is common when using GNOME Mobile on postmarketOS) or a TTY, this is unusable. For comparison, KDE Plasma Desktop (although not Mobile) provides kinfo, which returns the YAML that kcmshell6 kcm_about-distro otherwise would.
Does an equivalent, perhaps accessible via dbus-send, exist for GNOME Desktop and/or Mobile?
Just to note, but “GNOME Control Center” (or gnome-control-center) is not the same as gsettings.
The former is the application showing the settings, the other is a command line utility.
Anyways, AFAIK you can get this information on a distribution with SystemD with hostnamectl.
@CodedOre, hostnamectl status indeed returns some equivalents, like the CPE ID for the OS name (when set, like on Fedora, but not PMOS), but doesn’t return the available much less versus total) SDRAM quantity and GPU, etcetera, that the aforedepicted GUI does.
You can use neofetch. Or other fetch tools. Surprisingly enough they work perfectly.
@tragivictoria, a 3rd-party tool might indeed be best, although discussion of that at something like the aforecited Fedora thread would be better than here. Though, in the case of your specific recommendation, neofetch’s repository has been archived. [1]
You can grab updated neofetch from hyfetch repo
@tragivictoria, I tried that, but it just gives me a selection of colour palettes with some of the strangest accompanying terminology I’ve ever seen. I just want some YAML of the OS hardware, not whatever that is.
Since dnf5 provides $(command -v kinfo) returns kde-cli-tools, I tried installing that, but kinfo depends upon some KCMs.
Actually, neowofetch (from hyfetch) works. It still outputs a damnned colour palette and a useless ASCII logo, though. [1] It’s also not available on PMOS (Alpine Linux), so I still want a method that’s native to GNOME, if possible.
I meant that in repo you can grab just neofetch script. Thats what I use. Just give it executable permissions and in put it in PATH
Thanks, @tragivictoria. neowofetch appears to be near identical to it, [1] though, so I’d rather use that, since it’s maintained.
Thats the same script. You can check via the url
@tragivictoria, I don’t see anything there which demonstrates that. Do you mean that in source, it’s still called neofetch, but is renamed in CI?
RokeJulianLockhart@Beedell:/$ file $(command -v neowofetch)
/usr/bin/neowofetch: Bourne-Again shell script, Unicode text, UTF-8 text executable
I sent the repo of hyfetch earlier. They still maintain neofetch there, its just that when you use it via package they call it neowofetch to avoid conflict with original neofetch. You can read more in the README file.
Yeah, @tragivictoria, it’s actually in source:
I see no evidence that GNOME provides this.
Since we’ve spent so much time discussing tangential alternatives, I’ll solve that discussion by stating that I’ve since ascertained that fastfetch is the solution: [1]
It’s DE-agnostic,
fast (it’s C), and
provides what kinfo does.
Additionally, for me, it being available in PMOS matters:
fairphone-fp4:~$ fastfetch /\ user@fairphone-fp4 / \ ------------------ / \ OS: postmarketOS v25.06 aarch64 / \ Host: Fairphone 4 / \ Kernel: Linux 6.15.0 / \ Uptime: 2 hours, 9 mins \ \ Packages: 1141 (apk), 5 (flatpak) /\ \____ \ Shell: ash 1.37.0 / \____ \ \ Display (Built-in display): 1080x2340 @ 60 Hz (as 360x780) in 6" / / \ \ WM: Mutter (Wayland) / / \ ___\ Terminal: /dev/pts/1 / / \ / ____ CPU: sm7225 (8) @ 2.21 GHz / / \/ / \ GPU: Qualcomm Turnip Adreno (TM) 619 [Integrated] / / __________/ \ Memory: 1.00 GiB / 7.23 GiB (14%) / \ \ \ Swap: 0 B / 1.81 GiB (0%) / \ \ \ Disk (/): 8.92 GiB / 218.28 GiB (4%) - ext4 / / / \ Local IP (wlan0): 192.168.1.177/24 /___________/ /____________________\ Locale: C