QSI on XFCE Slightly Off [Solved]

[operadude]

It's a Miracle

Followed @dolphin_oracle's train of thought and edited "mx-version" (see previous posts). Today, I made an MX-Snapshot.

Lo, & Behold:

Now, on Xfce, today's Snapshot date appears, Auto-Magically, at the top of the Xfce QSI:

"Snapshot created on: 20240305_1311"

Quick Reminder: this was NOT happening for the longest time-- showing a very old snapshot date, even though numerous snapshots were taken after that old date. Check my previous posts. Anyway:

For completeness' sake, here's the whole QSI for my Xfce install, after today's Snapshot:

QSI_XFCE_Updated_Last_Miracle.txt

All I did was to make a snapshot, logout, login, and check the QSI.

So, thanks D.O.: not sure what made the change, but Xfce is behaving exactly the same as my KDE and Fluxbox installs-- whenever I make a Snapshot, that date automagically appears in the QSI.

And some people don't believe in Miracles

[asqwerth]

Although it now appears to behave like KDE and FB installs, the question is should it?

:-P

Doesn't seem helpful to display the latest snapshot made by the user, if the intention in QSI is to show the helpers that the system was made from a snapshot dated XXXX in the past.

[operadude]

Although it now appears to behave like KDE and FB installs, the question is should it?

:-P

Doesn't seem helpful to display the latest snapshot made by the user, if the intention in QSI is to show the helpers that the system was made from a snapshot dated XXXX in the past.

Again, @asqwerth, your logic is impeccable.

Just one thing...

And I have said this a number of times in my previous posts...

None of my systems (neither Xfce, KDE, nor Fluxbox) were made from Snapshots-- neither from the Snapshot date that appears in the latest QSI, nor from any earlier Snapshot.

All of my MX-23 systems were made from the official MX-ISO, taken from the official source, with verified checksums and signatures, back in 2023.

And yet, every time I do a new snapshot, the date of that new snapshot appears in the QSI.

This was happening automatically for KDE and Fluxbox, but not for Xfce; that's what my original post was about-- why wasn't this happening with Xfce. Again, not a deal breaker; just getting obsessive

Again, this is an extremely minor point, but I think there's a bit of a disconnect in the interpretation of the QSI. I'm on KDE right now, and here's my latest Snapshot info, and, system created info (from QSI). The file can be downloaded from one of my previous posts. Here's the info:

Snapshot created on: 20240214_1402

Distro: MX-23.2_x64 Libretto October 13 2023 [found under "System" heading]


My interpretation of this QSI information is that my (KDE) system was made on October 13, 2023 (found after "Distro"), which gels with my memory of making the actual system back in 2023 from the official release of the MX-ISO.

My KDE system was NOT made on 2024-02-14 @ 14:02

Rather, my KDE system was made back in 2023!

To put it even more strongly, from my post yesterday: posting.php?mode=reply&t=79604#pr768012, I made a Snapshot of my Xfce system (yesterday). I did NOT create my Xfce system yesterday. Rather, my Xfce system was created on: October 12, 2023; info taken from Xfce QSI: "Distro: MX-23.2_x64 Libretto October 12 2023".

If the helpers want to know when my system was made-- I would think, "Unless I'm Wrong..." (name that movie )-- that they should look (in QSI) at the date that occurs after the word "Distro", which is under the heading "System", which in this (KDE) instance, was: October 13, 2023.

Just sayin'...

Final Coda: After making a minor change to "mx-version", and updating "snapshot-created" (see previous posts), my Xfce install now also updates, automatically, the "Snapshot created" line in QSI.

Movin' On

[asqwerth]

If the helpers want to know when my system was made-- I would think, "Unless I'm Wrong..." (name that movie )-- that they should look (in QSI) at the date that occurs after the word "Distro", which is under the heading "System", which in this (KDE) instance, was: October 13, 2023.

I believe the date after 'Distro' is the date on which the iso was created, not when you installed it on your own system.

MX23.1 was officially announced on 15 Oct 2023 in the blog, but the announcement is made only after the iso file has been uploaded to all the download locations. Thus its creation date was 13 Oct 2023.

If a user creates a snapshot iso from their original system, the 'distro' date shown will still be the date of the iso from which the original system was installed.

[operadude]

/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.

Nutshell:

"...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."

All I'm sayin' is:

I did not create any of my MX systems from a Snapshot.

Despite what it says at the top of my QSI (for all 3 Distros).

I created them all from the MX official ISOs, from the official download source.

[richb]

I installed MX 23 KDE version from the original ISO. Since then I have made several snapshots. QSI shows the date of the original ISO not any snapshot. That is how it should be and how it is.

[operadude]

I installed MX 23 KDE version from the original ISO. Since then I have made several snapshots. QSI shows the date of the original ISO not any snapshot. That is how it should be and how it is.

First my QSI, and then final comments:

Code: Select all

Snapshot created on: 20240306_1101
System:
  Kernel: 6.1.0-10-amd64 [6.1.38-2] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-10-amd64 root=UUID=<filter> ro quiet splash
  Desktop: KDE Plasma v: 5.27.5 info: plank wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23.2_x64
    Libretto October 13 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: 3900 min/max: 800/3900 scaling: driver: intel_pstate governor: powersave
    cores: 1: 3900 2: 3900 3: 3900 4: 3900 bogomips: 31199
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  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_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: 35.0 C
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
    loaded: radeon unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: radeon display-ID: :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-10-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-10-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: 8.44 TiB used: 8 TiB (94.8%)
  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: 26.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: 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-6: /dev/sde maj-min: 8:64 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-7: /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-8: /dev/sdm maj-min: 8:192 type: USB model: Mass Storage Device size: 14.84 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?
  ID-9: /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-10: /dev/sdo maj-min: 8:224 type: USB model: Storage Device size: 7.4 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/sdp maj-min: 8:240 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-12: /dev/sdq maj-min: 65:0 type: USB vendor: Sabrent model: SABRENT size: 698.64 GiB
    block-size: physical: 4096 B logical: 512 B type: N/A serial: <filter> rev: 0104 scheme: MBR
Partition:
  ID-1: / raw-size: 25 GiB size: 24.44 GiB (97.76%) used: 10.87 GiB (44.5%) fs: ext4
    dev: /dev/nvme0n1p4 maj-min: 259:4
  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: 9.52 GiB (38.9%) fs: ext4
    dev: /dev/nvme0n1p5 maj-min: 259:5
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 32 GiB used: 9.4 MiB (0.0%) priority: -2
    dev: /dev/nvme0n1p10 maj-min: 259:10
Sensors:
  System Temperatures: cpu: 29.0 C mobo: N/A gpu: radeon temp: 35.0 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2677 libs: 1427 tools: apt,apt-get,aptitude,nala 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: 294 Uptime: 9h 6m wakeups: 6 Memory: 31.3 GiB used: 4.19 GiB (13.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

Final Comments:

I think the confusion is between what the top line of the QSI says:

"Snapshot created on: 20240306_1101"

and the later line, after "Distro":

"Distro: MX-23.2_x64 Libretto October 13 2023"


Again, all I'm saying is that I did not create my KDE system today (20240306_1101).

That seemed to be the implication from comments from previous posts in this thread:

"...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."

Like I said before:

Didn't create my system from a Snapshot; created it from an official ISO


Movin' On...

[MXRobo]

Movin' On... [/quote]

Not so fast my friend.

I have not been following this tread closely whatsover, but my older (MX-21.3 Xfce) QSIs is:
++EDIT I saved QSIs and created MX-Snapshots well after this date ( 20220812_1130)

Code: Select all

Snapshot created on: 20220812_1130
System:    Kernel: 6.7.4-1-liquorix-amd64 [6.7-8~mx21ahs] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: audit=0 intel_pstate=disable rcupdate.rcu_expedited=1 
           BOOT_IMAGE=/boot/vmlinuz-6.7.4-1-liquorix-amd64 root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.18.1 tk: Gtk 3.24.24 info: xfce4-panel, cairo-dock wm: xfwm 4.18.0 
           vt: 7 dm: LightDM 1.26.0 Distro: MX-21.3_ahs_x64 Wildflower November 22  2021 
           base: Debian GNU/Linux 11 (bullseye) 

And my just recently created QSI from minutes ago reads:

Code: Select all

Snapshot created on: 20240301_0104
System:    Kernel: 6.7.6-1-liquorix-amd64 [6.7-11~mx21ahs] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: audit=0 intel_pstate=disable rcupdate.rcu_expedited=1 
           BOOT_IMAGE=/boot/vmlinuz-6.7.6-1-liquorix-amd64 root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.18.1 tk: Gtk 3.24.24 info: xfce4-panel, cairo-dock wm: xfwm 4.18.0 
           vt: 7 dm: LightDM 1.26.0 Distro: MX-21.3_ahs_x64 Wildflower November 22  2021 
           base: Debian GNU/Linux 11 (bullseye) 

I do however have an MX-Snapshot named:
snapshot-20240301_0103.iso
and was created on 2024-03-01 01:23:36 per R-Click Properties → Created.

It conceivably took about 20 minutes for it to be created.

Cheers!

[operadude]

"And Now You Know........THE REST.......of the Story" -- Paul Harvey (R.I.P. )

Re:

"...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."

See:

viewtopic.php?p=768357#p768357 :

... it had nothing to do with install, other than adding information into the QSI that a snapshot was made.