which includes all this and USB and Repos sections.
If your mouse/touchpad is broken, then doing it with a keyboard only may be a bit tricky for a newbie, because you have the Shift+Tab to get to the Copy button:
Super (aka the Windows key),
arrow down to System Information,
Enter,
Shift+Tab 4 times,
Enter.
While CLI is superior in many ways, sometimes even for newbies, I’ve found that for them GUIs are usually much easier and safer. I recently struggled to get someone to type spaces in the correct places in a terminal, over the phone.
Not that I particularly want to get involved—I do also like inxi—but you can launch Info Center (kinfocenter) from krunner, the application menu, or under About this System in System Settings to get a good amount of this information and more.
Info Center is good, but getting the information into a forum post isn’t easy. With inxi, it’s just copy and paste. Just one simple example where the terminal is better.
One simple command vs:
Go to your start menu
Search for program name
Click on it
Scroll down about half way
Click the <Button>
Enter <Some text>
Click the <Button>
Click the <Button> in the popup
And if that’s done in Gnome, does it help a KDE user, Xfce, Mate? I think not. And that’s if the gui handles the problem at all.
Of course, the command comes with an explanation of what it does.
Trolls, who like to corrupt people’s data, exist. A GUI procedure is almost always safer.
Tell me how to gather this information from the GUI. Plasma for preference please.
>>> inxi -exzz ±[●][master] System: Kernel: 7.2.8-200.fc44.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 16.2.1 Desktop: KDE Plasma v: 6.7.5 Distro: Fedora Linux 44 (KDE Plasma Desktop Edition) Machine: Type: Desktop System: Intel Client Systems product: NUC8i7BEH v: J72992-303 serial: <superuser required> Mobo: Intel model: NUC8BEB v: J72688-303 serial: <superuser required> Firmware: UEFI vendor: Intel v: BECFL357.86A.0056.2018.1128.1717 date: 11/28/2018 Battery: Device-1: hidpp_battery_1 model: Logitech Wireless Mouse MX Master 2S charge: 100% (should be ignored) status: discharging CPU: Info: quad core model: Intel Core i7-8559U bits: 64 type: MT MCP arch: Coffee Lake rev: A cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB Speed (MHz): avg: 1132 min/max: 400/2700 cores: 1: 1132 2: 1132 3: 1132 4: 1132 5: 1132 6: 1132 7: 1132 8: 1132 bogomips: 43198 Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel CoffeeLake-U GT3e [Iris Plus Graphics 655] driver: i915 v: kernel arch: Gen-9.5 bus-ID: 00:02.0 Display: wayland server: Xwayland v: 24.1.13 compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting gpu: i915 resolution: 1: 2560x1440~60Hz 2: 2560x1440~60Hz API: EGL v: 1.5 drivers: iris,swrast platforms: active: gbm,wayland,x11,surfaceless,device inactive: N/A API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 26.0.3 glx-v: 1.4 direct-render: yes renderer: Mesa Intel Iris Plus Graphics 655 (CFL GT3) API: Vulkan v: 1.4.341 drivers: intel,llvmpipe surfaces: N/A devices: 2 Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdriinfo, xdpyinfo, xprop, xrandr Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 API: ALSA v: k7.2.8-200.fc44.x86_64 status: kernel-api Server-1: PipeWire v: 1.6.9 status: active Network: Device-1: Intel Cannon Point-LP CNVi [Wireless-AC] driver: iwlwifi v: kernel bus-ID: 00:14.3 IF: wlp0s20f3 state: down mac: <filter> Device-2: Intel Ethernet I219-V driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter> Bluetooth: Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) driver: btusb v: 0.8 type: USB bus-ID: 1-10:3 Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.1 lmp-v: 10 Drives: Local Storage: total: 2.81 TiB used: 920.76 GiB (32.0%) ID-1: /dev/sda vendor: A-Data model: SU800NS38 size: 119.24 GiB ID-2: /dev/sdb vendor: Toshiba model: Q300 size: 894.25 GiB ID-3: /dev/sdc vendor: Samsung model: ST2000LM003 HN-M201RAD size: 1.82 TiB type: USB Partition: ID-1: / size: 116.66 GiB used: 18.42 GiB (15.8%) fs: btrfs dev: /dev/sda3 ID-2: /boot size: 1.9 GiB used: 442.1 MiB (22.7%) fs: ext4 dev: /dev/sda2 ID-3: /boot/efi size: 598.8 MiB used: 20.1 MiB (3.4%) fs: vfat dev: /dev/sda1 ID-4: /home size: 893.82 GiB used: 246.53 GiB (27.6%) fs: xfs dev: /dev/sdb1 Swap: ID-1: swap-1 type: zram size: 8 GiB used: 827.8 MiB (10.1%) dev: /dev/zram0 Sensors: System Temperatures: cpu: 43.0 C pch: 49.0 C mobo: N/A Fan Speeds (rpm): N/A Info: Memory: total: 32 GiB available: 31.2 GiB used: 9.3 GiB (29.8%) Processes: 357 Uptime: 1d 3h 26m Init: systemd Packages: 7 note: see --rpm Compilers: clang: 22.1.8 gcc: 16.2.1 Shell: Zsh v: 5.9 inxi: 3.3.41I don’t use Plasma, but in Mint Xfce, you click:
which includes all this and USB and Repos sections.
If your mouse/touchpad is broken, then doing it with a keyboard only may be a bit tricky for a newbie, because you have the Shift+Tab to get to the Copy button:
While CLI is superior in many ways, sometimes even for newbies, I’ve found that for them GUIs are usually much easier and safer. I recently struggled to get someone to type spaces in the correct places in a terminal, over the phone.
Not that I particularly want to get involved—I do also like
inxi—but you can launch Info Center (kinfocenter) fromkrunner, the application menu, or under About this System in System Settings to get a good amount of this information and more.Info Center is good, but getting the information into a forum post isn’t easy. With inxi, it’s just copy and paste. Just one simple example where the terminal is better.
deleted by creator
I don’t know, it isn’t that hard for me to help others with UI. 🤷