Qeustion about update cycle [Solved]

[Noax]

Hello,

I am now finished to migrate my household from windows to MX Linux and it seems like all is stable, more or less. A few problems persists (cant change wallpaper directory for screensaver etc.) But we can ignore that.

Long story short: I had quite the work cut out for me for these last weeks so I now stumbled, late I know, upon the release cycle for Debian Stable. So LTS should go on until 2028 so am I "safe" until then? Or "should" I completely reinstall the new "MX 25" in june 25 with Debian 13? Did I even understand that correctly?

Whats for example with updates for "Proton/Wine" on Steam? Do I need to go with Debian 13 for newest updates? Or with an office PC which uses mostly Libre Office, Firefox, Videoplayers and an printer? Do I need the newest Debian version or can I get security updates also through the LTS channel?

Quite frankly: I am tired. I just want my PCs to function and to update the least times possible.

So for function, stability and security reasons: "should" I go with the newest Debian or should I wait an year so it isnt "cutting edge" anymore or can I simply skip one Debian version?

Thank you in advance for your answers. Have a nice day.

EDIT. Here is one of my QSI...:

Code: Select all

Snapshot created on: 20250318_1840
System:
  Kernel: 6.12.17-1-liquorix-amd64 [6.12-22~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable amd_pstate=disable BOOT_IMAGE=/boot/vmlinuz-6.12.17-1-liquorix-amd64
    root=UUID=<filter> ro nomodeset splash quiet
  Desktop: Xfce v: 4.20.0 tk: Gtk v: 3.24.38 info: xfce4-panel wm: xfwm v: 4.20.0 vt: 7
    dm: LightDM v: 1.32.0 Distro: MX-23.6_x64 Libretto March 18  2025 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop System: Gigabyte product: Z690 AORUS PRO v: -CF serial: <superuser required>
  Mobo: Gigabyte model: Z690 AORUS PRO serial: <superuser required> UEFI: American Megatrends
    LLC. v: F8e date: 03/14/2022
CPU:
  Info: model: 12th Gen Intel Core i7-12700K bits: 64 type: MST AMCP arch: Alder Lake gen: core 12
    level: v3 note: check built: 2021+ process: Intel 7 (10nm ESF) family: 6 model-id: 0x97 (151)
    stepping: 2 microcode: 0x38
  Topology: cpus: 1x cores: 12 mt: 8 tpc: 2 st: 4 threads: 20 smt: enabled cache: L1: 1024 KiB
    desc: d-4x32 KiB, 8x48 KiB; i-8x32 KiB, 4x64 KiB L2: 12 MiB desc: 8x1.2 MiB, 1x2 MiB L3: 25 MiB
    desc: 1x25 MiB
  Speed (MHz): avg: 1588 high: 3601 min/max: 800/3601 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 2447 2: 3540 3: 1270 4: 800 5: 1585 6: 2200
    7: 800 8: 800 9: 800 10: 800 11: 924 12: 800 13: 3601 14: 800 15: 900 16: 1600 17: 1200
    18: 3601 19: 2400 20: 900 bogomips: 144383
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  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 mitigation: Clear Register File
  Type: retbleed status: Not affected
  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: Enhanced / Automatic IBRS; IBPB: conditional; RSB filling;
    PBRSB-eIBRS: SW sequence; BHI: BHI_DIS_S
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel AlderLake-S GT1 vendor: Gigabyte driver: N/A alternate: i915, xe bus-ID: 00:02.0
    chip-ID: 8086:4680 class-ID: 0300
  Device-2: NVIDIA GA104 [GeForce RTX 3070 Lite Hash Rate] vendor: Micro-Star MSI driver: nvidia
    v: 535.216.03 non-free: 530.xx+ status: current (as of 2023-03) arch: Ampere code: GAxxx
    process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.0
    chip-ID: 10de:2488 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: xfwm v: 4.20.0
    driver: X: loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa alternate: nv gpu: nvidia
    display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1017x572mm (40.04x22.52")
    s-diag: 1167mm (45.94")
  Monitor-1: DP-0 res: 3840x2160 hz: 60 dpi: 157 size: 621x341mm (24.45x13.43")
    diag: 708mm (27.89") modes: N/A
  API: OpenGL v: 4.6.0 NVIDIA 535.216.03 renderer: NVIDIA GeForce RTX 3070/PCIe/SSE2
    direct-render: Yes
Audio:
  Device-1: Intel Alder Lake-S HD Audio vendor: Gigabyte driver: snd_hda_intel bus-ID: 1-12.2:8
    v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_tgl chip-ID: 1532:0504 class-ID: 0300
    bus-ID: 00:1f.3 chip-ID: 8086:7ad0 class-ID: 0403
  Device-2: NVIDIA GA104 High Definition Audio vendor: Micro-Star MSI driver: snd_hda_intel
    v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:228b class-ID: 0403
  Device-3: Razer USA Kraken 7.1 Chroma type: USB driver: hid-generic,snd-usb-audio,usbhid
  Device-4: Giga-Byte USB Audio type: USB driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-4:2
    chip-ID: 0414:a012 class-ID: 0300
  API: ALSA v: k6.12.17-1-liquorix-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 I225-V vendor: Gigabyte driver: igc v: kernel pcie: gen: 2 speed: 5 GT/s
    lanes: 1 port: N/A bus-ID: 03:00.0 chip-ID: 8086:15f3 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel modules: wl pcie: gen: 2 speed: 5 GT/s
    lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlan0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-14:9 chip-ID: 8087:0029
    class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
    sub-v: 2184 hci-v: 5.2 rev: 2184
  Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: peripheral accept
    service-classes: rendering, capturing, object transfer, audio, telephony
Drives:
  Local Storage: total: 3.64 TiB used: 2.11 TiB (58.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:1 vendor: Samsung model: SSD 980 PRO 1TB size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 5B2QGXA7 temp: 27.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 1TB size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 5B2QGXA7 temp: 27.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Seagate model: ST2000DM008-2UB102 size: 1.82 TiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: 0001 scheme: GPT
Partition:
  ID-1: / raw-size: 279.38 GiB size: 273.93 GiB (98.05%) used: 24.19 GiB (8.8%) fs: ext4
    dev: /dev/nvme1n1p2 maj-min: 259:4
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
    dev: /dev/nvme1n1p1 maj-min: 259:3
  ID-3: /home raw-size: 651.88 GiB size: 640.58 GiB (98.27%) used: 66.89 GiB (10.4%) fs: ext4
    dev: /dev/nvme1n1p3 maj-min: 259:5
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 6 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 24.5 C mobo: N/A gpu: nvidia temp: 29 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Repos:
  Packages: 2617 pm: dpkg pkgs: 2602 libs: 1417 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 15
  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://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bookworm main non-free
    2: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bookworm ahs
Info:
  Processes: 420 Uptime: 1m wakeups: 1 Memory: 31.13 GiB used: 2.09 GiB (6.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

[j2mcgreg]

We are going to need your computer’s complete profile before we can proceed, so you need to post the output from the QSI utility. The Quick System Info (QSI) utility is located in MX Tools and its output is automatically formatted for use here in the forum. Run the QSI utility, click “Copy for Forum” at the bottom and then just paste it here in your thread.
Forum Rules

[Noax]

So I edited my QSI in. As you can guess out of my first sentences of my topic its just an qeustion about update cycle so I didnt think we need an QSI for an qeustion thats not specifically pc oriented is.
And I am not "so new" here anymore and posted my QSI like an dear little boy in almost all of my other topics.
But rules are rules... *sigh* Sorry for my rant but in my workplace I too have more coworkers who want to work "like the book" but dont even want to consider to think about an case where its more efficient to not work "like the book"...

[uncle mark]

The simple answer is that it's up to you. You'll get all the updates, security or otherwise, as long as MX-23 is supported. Additionally, you'll be able to get application updates thanks to our outstanding devs who work hard at providing updated programs for the Debian/MX base, even if they aren't provided from upstream.

Bottom line -- if it was me, I'd take the time to get fully familiar and comfortable with MX and if/when the time comes you think you need to upgrade to a later version, the Community will be here to help. Keep in mind that I'm an "it ain't broke so it don't need fixin'" type and feel no need to be running the latest and greatest. I'm still running MX-19 and am perfectly happy with it. JMO. YMMV.

[Stevo]

MX 25 won't be coming out immediately after Debian 13. It takes no little time for us to rebuild all our extra, non-Debian packages, and then to test and fix any problems with our ISOs. We don't have any bots or AI to help us with that.

[Noax]

Thanks for your answer uncle mark.

So I am too the type of guy where I dont see the need to fix something when its still functioning. Glad you answered on it.

When you say you use still MX-19 do you surf in the internet with it? Is it still "safe and stable" for you? Whats with working with libre office and/or looking Videos through Firefox or with an mp4, MPEG or Wave file? All stable and functioning? Do you still get security updates for it? Do I even need security updates with Linux... hehe so many questions...

[DukeComposed]

Long story short: I had quite the work cut out for me for these last weeks so I now stumbled, late I know, upon the release cycle for Debian Stable. So LTS should go on until 2028 so am I "safe" until then? Or "should" I completely reinstall the new "MX 25" in june 25 with Debian 13? Did I even understand that correctly?

I don't know what you do or don't understand. You "should" review the docs, starting with https://mxlinux.org/release-cycle/ and the timeline of support given on https://mxlinux.org/previous-releases/ . The MX team is currently working on the next version on top of the forthcoming release of Debian Trixie this June-ish. MX-25 will then be released sometime after that, date TBD.

And, before you ask, there's a migration page and in-place upgrades are not recommended or supported. https://mxlinux.org/migration/

If you have to put MX on something right now, committing to MX-23 is fine since it will keep getting updates for a while. Personally, I'm trying to hold off on reinstalling anything until MX-25 and this has the general result of making me feel itchy. I have an old MX-21 system I use that's working just fine. It will likely get updated later this year and plans have already begun for what that process will entail.

[Noax]

Thank you too for your answer Stevo,

Yes I thought about that too although just briefly but yes it is amazing what you guys are doing for the Linux community to provide us 0815 PC users with an simple and stable OS is not an easy task. And it requires time and effort to do all the work so I understand it that after an Debian release it will take time for an new MX release.

So another few qeustions: do I need to do something when I want to use the LTS Support until june 2028? Change repo or something? Do I get "only" security updates after june 2026? Or also stability/function related updates through LTS?

And sorry for all these qeustions... I only want to more "know" how all of these "updates" functioning.

Thank you too DukeComposed for your answer.

I already red all the 3 links and I just want to further ask here to generally clarify the function of for example "LTS" and updates in general. One further qeustion in that regard: when an new Debian stable is released do all the software developers for example Firefox or steam (proton/wine) stop their work for software development on Debian 12 and only concentrate on Debian 13 or would software function also on Debian 12 when it functions on Debian 13 (like windows xp games still functioning on windows 10)?

[MXRobo]

I don't think it's recommended to use an outdated distro (MX-19) for the internet.

A few relevant links, the first one Ninja'd by Duke:
https://mxlinux.org/previous-releases/
https://wiki.debian.org/LTS
viewtopic.php?p=661709#p661709 Older, question relevancy
viewtopic.php?p=781524#p781524 In a pinch, maybe.

Some people like to wait until the first point release becomes available, e.g. 25.1.

Cheers!

[FullScale4Me]

I already red all the 3 links and I just want to further ask here to generally clarify the function of for example "LTS" and updates in general. One further qeustion in that regard: when an new Debian stable is released do all the software developers for example Firefox or steam (proton/wine) stop their work for software development on Debian 12 and only concentrate on Debian 13 or would software function also on Debian 12 when it functions on Debian 13 (like windows xp games still functioning on windows 10)?

The LTS comes from Debian itself. IIRC the MX support position is current version and one major version back. At this time that's MX 23 and all releases of MX 21. MX 19 is best effort as no bug fix/feature extension work plan is underway @MX Linux. Security updates would come from Debian only.

More official verbiage on LTS from Debian https://wiki.debian.org/DebianReleases

Check into the MX app User Installed Packages for capturing your apps and installing them on the new installation. It does have some limits:

• Flatpacks - not covered

• Apimage - not covered

• SNAPS - not covered

• Anything 'installed' via copying, ie, not through 'apt install <program_name>' or a process that spawns it.

Additionally, set up Timeshift on the machine you intend to migrate, and most importantly, TEST IT ONCE, TEST IT AGAIN! <1>

If you have an old but capable PC that can host the same disks as your main PC, it could be a 'rehearsal stage' for your migration. A second purpose is to test your Timeshift restores. Not the same physical disks, just similarly sized stand-ins of a kind.

1) I was an enterprise email admin during the Enron era. Quite a few people lost their jobs due to backup failures (of key subpoenaed execs' mailbox content).