QSI on XFCE Slightly Off [Solved]

[asqwerth]

@asqwerth:

On my KDE and Fluxbox installs, the top of the QSI shows my Latest Snapshots:

For Fluxbox:
Snapshot created on: 20240216_1220
Distro: MX-23.2_x64 Libretto September 18 2023

For KDE:
Snapshot created on: 20240214_1402
Distro: MX-23.2_x64 Libretto October 13 2023

I have a much more recent Snapshot for Xfce. See my latest LUM.log for Xfce:
posting.php?mode=reply&t=79604#pr767830
That occured on: snapshot-20240212_1300

So, not sure why Xfce is not updating QSI for the latest Snapshot, whereas KDE & FLUX do.

Again, No Biggie, just curious...

Why should it "update QSI for the latest Snapshot", if that's not the snapshot you installed your distro from?

[dolphin_oracle]

Again likely the string. If a string doesn’t match one of ours we don’t touch the line. So that people can customize without having there customizations wiped out.

It’s just text.

[operadude]

@asqwerth:

Not to appear too nit-picky, but that seems to be exactly what KDE and Fluxbox are doing in their respective QSIs-- I am seeing at the top of their QSIs, the latest snapshot-- not the one that was used for the install. You can see on their respective QSIs (which I have already posted), that for KDE & Fluxbox, the Snapshots are from 2024-02-14 and 2024-02-16. I installed both of those Distros long before that, as you can also see in their QSIs (September and October, 2023).

Again, just wondering why Xfce is not showing the latest Snapshot from 2024-02-12; whereas, both KDE & Fluxbox do show the most recent Snapshots.

Maybe that's the way ("uh-huh, uh-huh, I like it") that Xfce rolls...

[operadude]

Again likely the string. If a string doesn’t match one of ours we don’t touch the line. So that people can customize without having there customizations wiped out.

It’s just text.

Thanks again, D.O.

Just Curious: Where does the Snapshot string (for inxi) reside?

[dolphin_oracle]

/etc/snapshot_created

the string is created by mx-snapshot. we don't touch that one at all during updates.

[operadude]

/etc/snapshot_created

the string is created by mx-snapshot. we don't touch that one at all during updates.

@dolphin_oracle

And to prove it, here's my latest QSI for Xfce:

Code: Select all

Snapshot created on: 20240212_1300
System:
  Kernel: 6.1.0-18-amd64 [6.1.76-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-18-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel, plank wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.2_x64 Libretto October 12  2023 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop System: Gigabyte product: H270-HD3 v: N/A serial: <superuser required>
  Mobo: Gigabyte model: H270-HD3-CF v: x.x serial: <superuser required> UEFI: American Megatrends
    v: F5 date: 04/24/2017
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse PID:0080 serial: N/A
    charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
  Info: model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake gen: core 7 level: v3
    note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 9
    microcode: 0xF4
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
    desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 800 min/max: 800/3900 scaling: driver: intel_pstate governor: powersave
    cores: 1: 800 2: 800 3: 800 4: 800 bogomips: 31199
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: IBRS, IBPB: conditional, STIBP: conditional, RSB filling,
    PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Oland PRO [Radeon R7 240/340 / Radeon 520] vendor: Micro-Star MSI driver: radeon
    v: kernel alternate: amdgpu arch: GCN-1 code: Southern Islands process: TSMC 28nm built: 2011-20
    pcie: gen: 3 speed: 8 GT/s lanes: 8 ports: active: HDMI-A-1 empty: DVI-D-1,VGA-1
    bus-ID: 01:00.0 chip-ID: 1002:6613 class-ID: 0300 temp: 37.0 C
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: radeon
    unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: radeon display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
  Monitor-1: HDMI-A-1 mapped: HDMI-0 model: Samsung built: 2007 res: 1920x1080 hz: 60 dpi: 305
    gamma: 1.2 size: 160x90mm (6.3x3.54") diag: 184mm (7.2") ratio: 16:9 modes: max: 1920x1080
    min: 640x480
  API: OpenGL v: 4.5 Mesa 22.3.6 renderer: OLAND ( LLVM 15.0.6 DRM 2.50 6.1.0-18-amd64)
    direct-render: Yes
Audio:
  Device-1: Intel 200 Series PCH HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel
    bus-ID: 00:1f.3 chip-ID: 8086:a2f0 class-ID: 0403
  Device-2: AMD Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series]
    vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 8
    bus-ID: 01:00.1 chip-ID: 1002:aab0 class-ID: 0403
  API: ALSA v: k6.1.0-18-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I219-V vendor: Gigabyte driver: e1000e v: kernel port: N/A
    bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Drives:
  Local Storage: total: 7.76 TiB used: 5.38 TiB (69.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 250GB size: 232.89 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 1B2QEXE7 temp: 27.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 model: SATA SSD size: 111.79 GiB block-size: physical: 512 B
    logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 61.3 scheme: GPT
  ID-3: /dev/sdb maj-min: 8:16 vendor: Kingston model: SA400S37120G size: 111.79 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 61K1 scheme: MBR
  ID-4: /dev/sdc maj-min: 8:32 vendor: Seagate model: ST3000DM001-1ER166 size: 2.73 TiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: CC25 scheme: GPT
  ID-5: /dev/sdd maj-min: 8:48 vendor: Toshiba model: DT01ACA050 size: 465.76 GiB block-size:
    physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: A750
    scheme: GPT
  ID-6: /dev/sde maj-min: 8:64 vendor: Western Digital model: WD5000AADS-00S9B0 size: 465.76 GiB
    block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> rev: 0A01
    scheme: GPT
  ID-7: /dev/sdf maj-min: 8:80 type: USB vendor: Seagate model: Expansion Desk size: 3.64 TiB
    block-size: physical: 4096 B logical: 4096 B type: N/A serial: <filter> rev: 0739 scheme: MBR
  ID-8: /dev/sdl maj-min: 8:176 type: USB model: Storage Device size: 7.42 GiB block-size:
    physical: 512 B logical: 512 B type: N/A serial: N/A rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  ID-9: /dev/sdm maj-min: 8:192 type: USB model: Storage Device size: 14.84 GiB block-size:
    physical: 512 B logical: 512 B type: N/A serial: N/A rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  ID-10: /dev/sdn maj-min: 8:208 type: USB model: Storage Device size: 3.69 GiB block-size:
    physical: 512 B logical: 512 B type: N/A serial: N/A rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  ID-11: /dev/sdo maj-min: 8:224 type: USB model: Mass Storage Device size: 7.4 GiB block-size:
    physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: / raw-size: 25 GiB size: 24.44 GiB (97.76%) used: 10.56 GiB (43.2%) fs: ext4
    dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 1.6 MiB (0.7%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 25 GiB size: 24.44 GiB (97.76%) used: 10.62 GiB (43.4%) fs: ext4
    dev: /dev/nvme0n1p3 maj-min: 259:3
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 32 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p10
    maj-min: 259:10
Sensors:
  System Temperatures: cpu: 35.0 C mobo: N/A gpu: radeon temp: 36.0 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2414 libs: 1253 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mxrepo.com/mx/repo/ bookworm main non-free
  Active apt repos in: /etc/apt/sources.list.d/skype-stable.list
    1: deb [arch=amd64] https://repo.skype.com/deb stable main
Info:
  Processes: 281 Uptime: 1h 46m wakeups: 3 Memory: 31.3 GiB used: 2.93 GiB (9.4%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

[asqwerth]

/etc/snapshot_created

the string is created by mx-snapshot. we don't touch that one at all during updates.

Then the question is, what is the intention behind displaying "Snapshot created...." in the QSI? I had always assumed it was so that the forum helpers knew that the system in question had been created by a snapshot rather than an official iso.

But if that is the case, displaying the date that the user last created a snapshot on that distro makes no sense.

[dolphin_oracle]

/etc/snapshot_created

the string is created by mx-snapshot. we don't touch that one at all during updates.

Then the question is, what is the intention behind displaying "Snapshot created...." in the QSI? I had always assumed it was so that the forum helpers knew that the system in question had been created by a snapshot rather than an official iso.

yes that's why its there.

[operadude]

@dolphin_oracle:

Really hope I'm not wasting folks' time, since this has been SO resolved for me by now....But...

I know that I did all of my installs (incl. KDE & Flux) with official ISOs, and NOT from Snapshots, even though for my KDE & Flux installs, it shows at the top of the QSI the latest snapshots from Feb., 2024.

I know I did all of my installs from the official MX ISOs, since I did them all on the same day, and setup my "rEFInd" to appropriately access them.

Anyway...I'm obviously procrastinating from my work!

So, maybe on KDE and Fluxbox, the "snapshot-created" is getting updated and imported to "inxi" ?

WARNING: There be Rabbit Holes in 'Dem Dar Hills'

[operadude]

Just a shout-out to:

@dolphin_oracle & @asqwerth

for their help with my issue, which I have marked "[SOLVED]"

Thanks, and moving on to whatever comes next.