Page 1 of 1
Snapshot date is wrong in QSI
Posted: Fri Jun 07, 2024 10:55 am
by Eadwine Rose
Yesterday I had made a snapshot of the system, today I used that snapshot to install on a new harddrive.
All went well, only had a few updates that I knew about as they had appeared after making the snapshot of the old drive, and all was right in the world.
For kicks I thought of running QSI, and in there it said: Snapshot created on: 20230826_1058
HUH?
The kernel I have in use was DEFINITELY not there on that date, and had the snapshot indeed been that old, I should have gotten A LOT more updates than those 4 I had between taking the snapshot and the install just now.
The snapshot folder doesn't even hold a snapshot that old (oldest one there is from Feb this year).
This usb stick has held snapshots before, but I always set live USB maker to GPT, and to use that entire thing, no multiples on there at all.
I figured I'd report it in.
Code: Select all
Snapshot created on: 20230826_1058
System:
Kernel: 6.1.0-21-amd64 [6.1.90-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-21-amd64 root=UUID=<filter> ro quiet
Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
dm: LightDM v: 1.26.0 Distro: MX-23.3_x64 Libretto July 31 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Desktop Mobo: ASUSTeK model: TUF B450-PLUS GAMING v: Rev X.0x serial: <superuser required>
UEFI: American Megatrends v: 1607 date: 06/17/2019
Battery:
Device-1: hidpp_battery_0 model: Logitech MX Ergo Multi-Device Trackball serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
Info: model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+ gen: 2 level: v3 note: check
built: 2018-21 process: GF 12nm family: 0x17 (23) model-id: 8 stepping: 2 microcode: 0x800820D
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 768 KiB
desc: d-8x32 KiB; i-8x64 KiB L2: 4 MiB desc: 8x512 KiB L3: 16 MiB desc: 2x8 MiB
Speed (MHz): avg: 1539 high: 1550 min/max: 1550/3200 boost: enabled scaling:
driver: acpi-cpufreq governor: ondemand cores: 1: 1547 2: 1550 3: 1550 4: 1547 5: 1550 6: 1550
7: 1550 8: 1546 9: 1547 10: 1550 11: 1403 12: 1550 13: 1546 14: 1550 15: 1547 16: 1547
bogomips: 102209
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: untrained return thunk; SMT vulnerable
Type: spec_rstack_overflow mitigation: safe RET
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: Retpolines; IBPB: conditional; STIBP: disabled; RSB filling;
PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Conexant Systems CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb
vendor: Hauppauge works driver: cx23885 v: 0.0.4 pcie: gen: 1 speed: 2.5 GT/s lanes: 1
bus-ID: 07:00.0 chip-ID: 14f1:8880 class-ID: 0400
Device-2: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: ASUSTeK driver: nvidia v: 525.147.05
non-free: 530.xx+ status: current (as of 2023-03) arch: Pascal code: GP10x process: TSMC 16nm
built: 2016-21 pcie: gen: 2 speed: 5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s
bus-ID: 08:00.0 chip-ID: 10de:1c82 class-ID: 0300
Device-3: Logitech QuickCam E 3500 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-7:3
chip-ID: 046d:09a4 class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: nvidia
gpu: cx23885,nvidia display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x286mm (40.00x11.26")
s-diag: 1055mm (41.55")
Monitor-1: DVI-D-0 pos: right res: 1920x1080 hz: 60 dpi: 102 size: 477x268mm (18.78x10.55")
diag: 547mm (21.54") modes: N/A
Monitor-2: HDMI-0 pos: primary,left res: 1920x1080 hz: 60 dpi: 92
size: 531x299mm (20.91x11.77") diag: 609mm (23.99") modes: N/A
API: OpenGL v: 4.6.0 NVIDIA 525.147.05 renderer: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
direct-render: Yes
Audio:
Device-1: Conexant Systems CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb
vendor: Hauppauge works driver: cx23885 bus-ID: 1-7:3 v: 0.0.4 chip-ID: 046d:09a4 pcie:
class-ID: 0102 gen: 1 speed: 2.5 GT/s serial: <filter> lanes: 1 bus-ID: 07:00.0
chip-ID: 14f1:8880 class-ID: 0400
Device-2: NVIDIA GP107GL High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 08:00.1 chip-ID: 10de:0fb9 class-ID: 0403
Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 3
speed: 8 GT/s lanes: 16 bus-ID: 0a:00.3 chip-ID: 1022:1457 class-ID: 0403
Device-4: Logitech QuickCam E 3500 type: USB driver: snd-usb-audio,uvcvideo
API: ALSA v: k6.1.0-21-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: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK PRIME B450M-A
driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 03:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Ralink MT7601U Wireless Adapter type: USB driver: mt7601u bus-ID: 1-1:2
chip-ID: 148f:7601 class-ID: 0000 serial: <filter>
IF: wlan0 state: down mac: <filter>
Bluetooth:
Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB driver: btusb v: 0.8
bus-ID: 1-8:4 chip-ID: 0a12:0001 class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0
sub-v: 22bb hci-v: 4.0 rev: 22bb
Info: acl-mtu: 310:10 sco-mtu: 64:8 link-policy: rswitch hold sniff park
link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
telephony
Drives:
Local Storage: total: 1.36 TiB used: 154.28 GiB (11.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q
temp: 30.0 C scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 870 EVO 500GB size: 465.76 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q
temp: 30.0 C scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 3B6Q
temp: 31.0 C scheme: GPT
ID-4: /dev/sdd maj-min: 8:48 vendor: Samsung model: SSD 870 EVO 500GB size: 465.76 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q
temp: 31.0 C scheme: GPT
Partition:
ID-1: / raw-size: 78.12 GiB size: 76.35 GiB (97.73%) used: 15.68 GiB (20.5%) fs: ext4
dev: /dev/sdd2 maj-min: 8:50
ID-2: /boot/efi raw-size: 523 MiB size: 521.9 MiB (99.80%) used: 288 KiB (0.1%) fs: vfat
dev: /dev/sdd1 maj-min: 8:49
ID-3: /home raw-size: 379.31 GiB size: 372.29 GiB (98.15%) used: 9.3 GiB (2.5%) fs: ext4
dev: /dev/sdd4 maj-min: 8:52
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 7.81 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdd3
maj-min: 8:51
Sensors:
System Temperatures: cpu: 40.6 C mobo: 30.0 C gpu: nvidia temp: 38 C
Fan Speeds (RPM): cpu: 754 fan-2: 757 fan-3: 0 fan-4: 729 fan-6: 0 gpu: nvidia fan: 25%
Power: 12v: N/A 5v: N/A 3.3v: 3.36 vbat: 3.27
Repos:
Packages: pm: dpkg pkgs: 2583 libs: 1362 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/google-chrome.list
1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/megasync.list
1: deb [signed-by=/usr/share/keyrings/meganz-archive-keyring.gpg] https://mega.nz/linux/repo/Debian_12/ ./
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://nl.mxrepo.com/mx/repo/ bookworm main non-free
Active apt repos in: /etc/apt/sources.list.d/slack.list
1: deb https://packagecloud.io/slacktechnologies/slack/debian/ jessie main
Active apt repos in: /etc/apt/sources.list.d/spotify.list
1: deb http://repository.spotify.com/ stable non-free
Info:
Processes: 373 Uptime: 32m wakeups: 4 Memory: 31.28 GiB used: 4.6 GiB (14.7%) 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
Re: Snapshot date is wrong in QSI
Posted: Fri Jun 07, 2024 11:30 am
by Adrian
Thanks, I will check.
Re: Snapshot date is wrong in QSI
Posted: Fri Jun 07, 2024 11:32 am
by CharlesV
D_O's post on this a while back... I do not know if it still applies though.
viewtopic.php?p=768357#p768357
edit: Mine has never matched the 'last snapshot' either btw. After the post there, I kind of gave up on matching the dates ;-/
Re: Snapshot date is wrong in QSI
Posted: Fri Jun 07, 2024 11:34 am
by Eadwine Rose
Ah ok.
Well.. it's not bugging me anything, my install works
Re: Snapshot date is wrong in QSI
Posted: Fri Jun 07, 2024 11:48 am
by siamhie
CharlesV wrote: Fri Jun 07, 2024 11:32 am
D_O's post on this a while back... I do not know if it still applies though.
viewtopic.php?p=768357#p768357
edit: Mine has never matched the 'last snapshot' either btw. After the post there, I kind of gave up on matching the dates ;-/
The snapshot_created file gets updated on my system.
Here I made a snapshot at 08:37am June 7th 2024
Code: Select all
cat /etc/snapshot_created
20240607_0837
Then I made a second one 4 minutes later
Code: Select all
cat /etc/snapshot_created
20240607_0841
Re: Snapshot date is wrong in QSI
Posted: Fri Jun 07, 2024 11:52 am
by Eadwine Rose
Silly question.. well not silly.. but that file.. can the date be edited so it reflects the right one, and will that then be loaded into the QSI?
At least makes more sense than using a reaaaally old snapshot. Seemingly
Re: Snapshot date is wrong in QSI
Posted: Fri Jun 07, 2024 11:58 am
by CharlesV
siamhie wrote: Fri Jun 07, 2024 11:48 am
CharlesV wrote: Fri Jun 07, 2024 11:32 am
D_O's post on this a while back... I do not know if it still applies though.
viewtopic.php?p=768357#p768357
edit: Mine has never matched the 'last snapshot' either btw. After the post there, I kind of gave up on matching the dates ;-/
The snapshot_created file gets updated on my system.
Here I made a snapshot at 08:37am June 7th 2024
Code: Select all
cat /etc/snapshot_created
20240607_0837
Then I made a second one 4 minutes later
Code: Select all
cat /etc/snapshot_created
20240607_0841
Yeah.. no.
My primary rig:
snapshot: 20240519_1647
QSI says: 20240519_1648
Second rig:
snapshot: 20240519_1629
QSI says: 20240519_1636
and two others I have checked are also like this - off.
Re: Snapshot date is wrong in QSI
Posted: Fri Jun 07, 2024 12:01 pm
by CharlesV
Eadwine Rose wrote: Fri Jun 07, 2024 11:52 am
Silly question.. well not silly.. but that file.. can the date be edited so it reflects the right one, and will that then be loaded into the QSI?
At least makes more sense than using a reaaaally old snapshot. Seemingly
I just edited mine, matched it with the actual snapshot date and will do a snapshot not that they both match, and see what happens :-)
Re: Snapshot date is wrong in QSI [Solved]
Posted: Fri Jun 07, 2024 12:03 pm
by siamhie
Eadwine Rose wrote: Fri Jun 07, 2024 11:52 am
Silly question.. well not silly.. but that file.. can the date be edited so it reflects the right one, and will that then be loaded into the QSI?
Apparently you can.
Code: Select all
Snapshot created on: This-is-NOT-Eadwine's-snapshot
System:
Kernel: 6.6.15-amd64 [6.6.15-2~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.6.15-amd64 root=UUID=<filter> ro
init=/lib/systemd/systemd
Desktop: Fluxbox v: 1.3.7 vt: 7 dm: LightDM v: 1.26.0 Distro: MX-23.3_fluxbox_x64 Libretto May
19 2024 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Desktop Mobo: Micro-Star model: B550-A PRO (MS-7C56) v: 2.0 serial: <superuser required>
UEFI: American Megatrends LLC. v: A.F0 date: 10/11/2023
CPU:
Info: model: AMD Ryzen 9 5950X bits: 64 type: MT MCP arch: Zen 3+ gen: 4 level: v3 note: check
built: 2022 process: TSMC n6 (7nm) family: 0x19 (25) model-id: 0x21 (33) stepping: 2
microcode: 0xA20120E
Topology: cpus: 1x cores: 16 tpc: 2 threads: 32 smt: enabled cache: L1: 1024 KiB desc: d-16x32
KiB; i-16x32 KiB L2: 8 MiB desc: 16x512 KiB L3: 64 MiB desc: 2x32 MiB
Speed (MHz): avg: 2410 high: 3400 min/max: 2200/5083 boost: enabled scaling:
driver: acpi-cpufreq governor: schedutil cores: 1: 2880 2: 2200 3: 2200 4: 2200 5: 2200 6: 2200
7: 2200 8: 2200 9: 2200 10: 2200 11: 2200 12: 2200 13: 2200 14: 2200 15: 3400 16: 3400 17: 2200
18: 2200 19: 2200 20: 2200 21: 2200 22: 2200 23: 3400 24: 2857 25: 2200 26: 2200 27: 2200
28: 2200 29: 2800 30: 2200 31: 2200 32: 3400 bogomips: 217596
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: retbleed status: Not affected
Type: spec_rstack_overflow mitigation: Safe RET
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: Retpolines, IBPB: conditional, IBRS_FW, STIBP: always-on, RSB
filling, PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT] vendor: Tul / PowerColor
driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie:
gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-3 empty: DP-1,DP-2,HDMI-A-1 bus-ID: 2d:00.0
chip-ID: 1002:73df class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: Compton v: 1 driver: X: loaded: amdgpu
unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.65x15.00") s-diag: 777mm (30.58")
Monitor-1: DP-3 mapped: DisplayPort-2 model: HP X27q serial: <filter> built: 2021
res: 2560x1440 hz: 165 dpi: 109 gamma: 1.2 size: 597x336mm (23.5x13.23") diag: 685mm (27")
ratio: 16:9 modes: max: 2560x1440 min: 720x400
API: OpenGL v: 4.6 Mesa 23.1.2-1~mx23ahs renderer: AMD Radeon RX 6700 XT (navi22 LLVM 15.0.6
DRM 3.54 6.6.15-amd64) direct-render: Yes
Audio:
Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie: gen: 4
speed: 16 GT/s lanes: 16 bus-ID: 2d:00.1 chip-ID: 1002:ab28 class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 2f:00.4 chip-ID: 1022:1487 class-ID: 0403
API: ALSA v: k6.6.15-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 Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2725 class-ID: 0280
IF: wlan0 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI
driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 2a:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: down mac: <filter>
Bluetooth:
Device-1: Intel AX210 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-2.3:4 chip-ID: 8087:0032
class-ID: e001
Report: rfkill ID: hci0 rfk-id: 1 state: down bt-service: N/A rfk-block: hardware: no
software: no address: see --recommends
Drives:
Local Storage: total: 8.64 TiB used: 899.23 GiB (10.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:3 vendor: Western Digital model: WDS500G1X0E-00AFY0
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
serial: <filter> rev: 613000WD temp: 37.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Western Digital model: WDS500G3XHC-00SJG0
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD
serial: <filter> rev: 102000WD temp: 33.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 EVO 500GB size: 465.76 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 1B6Q
scheme: GPT
ID-4: /dev/sdb maj-min: 8:16 vendor: SanDisk model: ST8000DM004-2CX188 size: 7.28 TiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5425 serial: <filter>
rev: 0001 scheme: GPT
Partition:
ID-1: / raw-size: 465 GiB size: 456.63 GiB (98.20%) used: 9.67 GiB (2.1%) fs: ext4
dev: /dev/nvme0n1p2 maj-min: 259:5
ID-2: /boot/efi raw-size: 128 MiB size: 127.7 MiB (99.79%) used: 18.4 MiB (14.4%) fs: vfat
dev: /dev/nvme0n1p1 maj-min: 259:4
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 64 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda2
maj-min: 8:2
Sensors:
System Temperatures: cpu: 38.9 C mobo: N/A gpu: amdgpu temp: 47.0 C mem: 48.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 762
Repos:
Packages: pm: dpkg pkgs: 1966 libs: 995 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/librewolf.list
1: deb [arch=amd64] http://deb.librewolf.net bookworm main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://la.mxrepo.com/mx/repo/ bookworm main non-free
2: deb http://la.mxrepo.com/mx/repo/ bookworm ahs
Active apt repos in: /etc/apt/sources.list.d/nordvpn.list
1: deb https://repo.nordvpn.com/deb/nordvpn/debian stable main
Info:
Processes: 490 Uptime: 32m wakeups: 0 Memory: 31.27 GiB used: 2.38 GiB (7.6%) Init: systemd
v: 252 target: graphical (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
Re: Snapshot date is wrong in QSI
Posted: Fri Jun 07, 2024 12:04 pm
by Eadwine Rose
Ah cool. Does it show correctly now in the QSI window now that it has been edited to reflect the propers?
Re: Snapshot date is wrong in QSI
Posted: Fri Jun 07, 2024 12:05 pm
by Eadwine Rose
siamhie wrote: Fri Jun 07, 2024 12:03 pm
Eadwine Rose wrote: Fri Jun 07, 2024 11:52 am
Silly question.. well not silly.. but that file.. can the date be edited so it reflects the right one, and will that then be loaded into the QSI?
Apparently you can.
Code: Select all
Snapshot created on: This-is-NOT-Eadwine's-snapshot
Re: Snapshot date is wrong in QSI
Posted: Fri Jun 07, 2024 12:08 pm
by CharlesV
Eadwine Rose wrote: Fri Jun 07, 2024 12:04 pm
Ah cool. Does it show correctly now in the QSI window now that it has been edited to reflect the propers?
Yes it shows correctly.
AND... I just made a snapshot and now both are in sync again... either an update to snapshot fixed this ?
It is NOW showing the correct date... interesting.
Re: Snapshot date is wrong in QSI
Posted: Fri Jun 07, 2024 12:09 pm
by siamhie
Eadwine Rose wrote: Fri Jun 07, 2024 12:04 pm
Ah cool. Does it show correctly now in the QSI window now that it has been edited to reflect the propers?
Yes it does (for me).
Code: Select all
╔═[siamhie@flux23]═[09:05/07-06-24]═════════════════════════════════════════[~]
╚═> cat /etc/snapshot_created
This-is-NOT-Eadwine's-snapshot
╔═[siamhie@flux23]═[09:05/07-06-24]═════════════════════════════════════════[~]
╚═> cat /etc/snapshot_created
20240607_0906
╔═[siamhie@flux23]═[09:08/07-06-24]═════════════════════════════════════════[~]
╚═>
Re: Snapshot date is wrong in QSI
Posted: Fri Jun 07, 2024 12:10 pm
by Eadwine Rose
The editing shows the truth now. Here is the truth, the whole truth, and nothing but the truth
Code: Select all
Snapshot created on: 20240606_2135
System:
Kernel: 6.1.0-21-amd64 [6.1.90-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-21-amd64 root=UUID=<filter> ro quiet
Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
dm: LightDM v: 1.26.0 Distro: MX-23.3_x64 Libretto July 31 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Desktop Mobo: ASUSTeK model: TUF B450-PLUS GAMING v: Rev X.0x serial: <superuser required>
UEFI: American Megatrends v: 1607 date: 06/17/2019
Battery:
Device-1: hidpp_battery_0 model: Logitech MX Ergo Multi-Device Trackball serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
Info: model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+ gen: 2 level: v3 note: check
built: 2018-21 process: GF 12nm family: 0x17 (23) model-id: 8 stepping: 2 microcode: 0x800820D
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 768 KiB
desc: d-8x32 KiB; i-8x64 KiB L2: 4 MiB desc: 8x512 KiB L3: 16 MiB desc: 2x8 MiB
Speed (MHz): avg: 1548 high: 1583 min/max: 1550/3200 boost: enabled scaling:
driver: acpi-cpufreq governor: ondemand cores: 1: 1547 2: 1546 3: 1546 4: 1547 5: 1550 6: 1550
7: 1583 8: 1547 9: 1546 10: 1546 11: 1546 12: 1519 13: 1550 14: 1550 15: 1550 16: 1550
bogomips: 102209
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: untrained return thunk; SMT vulnerable
Type: spec_rstack_overflow mitigation: safe RET
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: Retpolines; IBPB: conditional; STIBP: disabled; RSB filling;
PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Conexant Systems CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb
vendor: Hauppauge works driver: cx23885 v: 0.0.4 pcie: gen: 1 speed: 2.5 GT/s lanes: 1
bus-ID: 07:00.0 chip-ID: 14f1:8880 class-ID: 0400
Device-2: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: ASUSTeK driver: nvidia v: 525.147.05
non-free: 530.xx+ status: current (as of 2023-03) arch: Pascal code: GP10x process: TSMC 16nm
built: 2016-21 pcie: gen: 2 speed: 5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s
bus-ID: 08:00.0 chip-ID: 10de:1c82 class-ID: 0300
Device-3: Logitech QuickCam E 3500 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-7:3
chip-ID: 046d:09a4 class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: nvidia
gpu: cx23885,nvidia display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x286mm (40.00x11.26")
s-diag: 1055mm (41.55")
Monitor-1: DVI-D-0 pos: right res: 1920x1080 hz: 60 dpi: 102 size: 477x268mm (18.78x10.55")
diag: 547mm (21.54") modes: N/A
Monitor-2: HDMI-0 pos: primary,left res: 1920x1080 hz: 60 dpi: 92
size: 531x299mm (20.91x11.77") diag: 609mm (23.99") modes: N/A
API: OpenGL v: 4.6.0 NVIDIA 525.147.05 renderer: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
direct-render: Yes
Audio:
Device-1: Conexant Systems CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb
vendor: Hauppauge works driver: cx23885 v: 0.0.4 bus-ID: 1-7:3 pcie: chip-ID: 046d:09a4 gen: 1
class-ID: 0102 serial: <filter> speed: 2.5 GT/s lanes: 1 bus-ID: 07:00.0 chip-ID: 14f1:8880
class-ID: 0400
Device-2: NVIDIA GP107GL High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 08:00.1 chip-ID: 10de:0fb9 class-ID: 0403
Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 3
speed: 8 GT/s lanes: 16 bus-ID: 0a:00.3 chip-ID: 1022:1457 class-ID: 0403
Device-4: Logitech QuickCam E 3500 type: USB driver: snd-usb-audio,uvcvideo
API: ALSA v: k6.1.0-21-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: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK PRIME B450M-A
driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 03:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Ralink MT7601U Wireless Adapter type: USB driver: mt7601u bus-ID: 1-1:2
chip-ID: 148f:7601 class-ID: 0000 serial: <filter>
IF: wlan0 state: down mac: <filter>
Bluetooth:
Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB driver: btusb v: 0.8
bus-ID: 1-8:4 chip-ID: 0a12:0001 class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0
sub-v: 22bb hci-v: 4.0 rev: 22bb
Info: acl-mtu: 310:10 sco-mtu: 64:8 link-policy: rswitch hold sniff park
link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
telephony
Drives:
Local Storage: total: 1.36 TiB used: 254.51 GiB (18.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q
temp: 31.0 C scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 870 EVO 500GB size: 465.76 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q
temp: 31.0 C scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 3B6Q
temp: 31.0 C scheme: GPT
ID-4: /dev/sdd maj-min: 8:48 vendor: Samsung model: SSD 870 EVO 500GB size: 465.76 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q
temp: 32.0 C scheme: GPT
Partition:
ID-1: / raw-size: 78.12 GiB size: 76.35 GiB (97.73%) used: 15.71 GiB (20.6%) fs: ext4
dev: /dev/sdd2 maj-min: 8:50
ID-2: /boot/efi raw-size: 523 MiB size: 521.9 MiB (99.80%) used: 288 KiB (0.1%) fs: vfat
dev: /dev/sdd1 maj-min: 8:49
ID-3: /home raw-size: 379.31 GiB size: 372.29 GiB (98.15%) used: 9.31 GiB (2.5%) fs: ext4
dev: /dev/sdd4 maj-min: 8:52
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 7.81 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdd3
maj-min: 8:51
Sensors:
System Temperatures: cpu: 44.9 C mobo: 30.0 C gpu: nvidia temp: 35 C
Fan Speeds (RPM): cpu: 675 fan-2: 734 fan-3: 0 fan-4: 707 fan-6: 0 gpu: nvidia fan: 25%
Power: 12v: N/A 5v: N/A 3.3v: 3.36 vbat: 3.27
Repos:
Packages: pm: dpkg pkgs: 2583 libs: 1362 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/google-chrome.list
1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/megasync.list
1: deb [signed-by=/usr/share/keyrings/meganz-archive-keyring.gpg] https://mega.nz/linux/repo/Debian_12/ ./
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://nl.mxrepo.com/mx/repo/ bookworm main non-free
Active apt repos in: /etc/apt/sources.list.d/slack.list
1: deb https://packagecloud.io/slacktechnologies/slack/debian/ jessie main
Active apt repos in: /etc/apt/sources.list.d/spotify.list
1: deb http://repository.spotify.com/ stable non-free
Info:
Processes: 395 Uptime: 2h 1m wakeups: 4 Memory: 31.28 GiB used: 6.55 GiB (20.9%) 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
Re: Snapshot date is wrong in QSI
Posted: Fri Jun 07, 2024 12:14 pm
by siamhie
CharlesV wrote: Fri Jun 07, 2024 12:08 pm
Eadwine Rose wrote: Fri Jun 07, 2024 12:04 pm
Ah cool. Does it show correctly now in the QSI window now that it has been edited to reflect the propers?
Yes it shows correctly.
AND... I just made a snapshot and now both are in sync again... either an update to snapshot fixed this ?
It is NOW showing the correct date... interesting.
+1
MX Snapshot was updated on 06/06/24
Code: Select all
╔═[siamhie@flux23]═[09:12/07-06-24]═════════════════════════════════════════[~]
╚═> nala history
ID Command Date and Time Altered Requested-By
1 upgrade c… 2024-05-26 08:53:05 PDT 46 siamhie (1000)
2 upgrade l… 2024-05-29 07:53:26 PDT 2 siamhie (1000)
3 upgrade l… 2024-05-29 20:38:56 PDT 4 siamhie (1000)
4 upgrade l… 2024-05-31 15:52:47 PDT 1 siamhie (1000)
5 upgrade g… 2024-06-01 08:22:05 PDT 5 siamhie (1000)
6 upgrade l… 2024-06-02 07:19:00 PDT 3 siamhie (1000)
7 upgrade q… 2024-06-02 16:46:55 PDT 1 siamhie (1000)
8 upgrade l… 2024-06-04 07:11:22 PDT 2 siamhie (1000)
9 upgrade l… 2024-06-06 08:14:52 PDT 3 siamhie (1000)
10 upgrade m… 2024-06-06 17:02:53 PDT 1 siamhie (1000)
11 upgrade l… 2024-06-07 07:43:36 PDT 3 siamhie (1000)
╔═[siamhie@flux23]═[09:12/07-06-24]═════════════════════════════════════════[~]
╚═> nala history info 10
===============================================================================
Upgraded
===============================================================================
Package: Old Version: New Version: Size:
mx-snapshot 24.5 24.6 310 KB
===============================================================================
Summary
===============================================================================
Upgraded 1 Packages
Re: Snapshot date is wrong in QSI
Posted: Fri Jun 07, 2024 12:15 pm
by CharlesV
Re: Snapshot date is wrong in QSI
Posted: Fri Jun 07, 2024 12:16 pm
by siamhie
Eadwine Rose wrote: Fri Jun 07, 2024 12:10 pm
The editing shows the truth now. Here is the truth, the whole truth, and nothing but the truth
Code: Select all
Snapshot created on: 20240606_2135
Re: Snapshot date is wrong in QSI
Posted: Fri Jun 07, 2024 12:22 pm
by CharlesV
siamhie wrote: Fri Jun 07, 2024 12:14 pm
MX Snapshot was updated on 06/06/24
Interestingly .. I am on 24.5 on all of my rigs.
( update notice just popped up for the 24.6 version.)
Re: Snapshot date is wrong in QSI
Posted: Fri Jun 07, 2024 12:24 pm
by Eadwine Rose
I just marked it solved, because I solved it using the edit of that file.
Of course it should update on its own, that old date showing up just looks silly. *chuckles*
Re: Snapshot date is wrong in QSI
Posted: Fri Jun 07, 2024 12:29 pm
by siamhie
CharlesV wrote: Fri Jun 07, 2024 12:22 pm
siamhie wrote: Fri Jun 07, 2024 12:14 pm
MX Snapshot was updated on 06/06/24
Interestingly .. I am on 24.5 on all of my rigs.
( update notice just popped up for the 24.6 version.)
@CharlesV I manually check for updates every morning with nala.
Just part of my morning routine when I turn on the computer.
Re: Snapshot date is wrong in QSI
Posted: Fri Jun 07, 2024 12:38 pm
by Eadwine Rose
Same here, avid updater. I was a bit bummed about the 4 updates between the snapshot and the install, but to create a new snapshot and all for just that.. nah.
Re: Snapshot date is wrong in QSI
Posted: Fri Jun 07, 2024 1:05 pm
by Adrian
There was a bug that I fixed in February... probably you took the snapshot before that fix.
mx-snapshot (24.02.01) mx; urgency=medium
* Fix: write actual snapshot date/time creation to /etc/snapshot_created
-- Adrian <
adrian@mxlinux.org> Mon, 12 Feb 2024 11:58:40 -0500
Re: Snapshot date is wrong in QSI
Posted: Fri Jun 07, 2024 1:08 pm
by Eadwine Rose
I took the snapshot yesterday.
