Difference between Tumbleweed version in GRUB versus /etc/os-release

Support Question:

Distribution: OpenSUSE Tumbleweed

Desktop Environment (DE): LXQt 2.3

Issue at Hand: I recently had to reinstall openSUSE Tumbleweed as I am inexperienced and flew a bit too close to the sun when playing around. On this install, I did a zypper dup today which bumped me up to the 20260122 version. However, I noticed this discrepancy.

In GRUB, the version is reported as the previous one, as indicated by YaST.

However, /etc/os-release reports the most updated version in the same session:

cat /etc/os-release 
─────┬───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
     β”‚ File: /etc/os-release
─────┼───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
   1 β”‚ NAME="openSUSE Tumbleweed"
   2 β”‚ # VERSION="20260122"
   3 β”‚ ID="opensuse-tumbleweed"
   4 β”‚ ID_LIKE="opensuse suse"
   5 β”‚ VERSION_ID="20260122"
   6 β”‚ PRETTY_NAME="openSUSE Tumbleweed"
   7 β”‚ ANSI_COLOR="0;32"
   8 β”‚ # CPE 2.3 format, boo#1217921
   9 β”‚ CPE_NAME="cpe:2.3:o:opensuse:tumbleweed:20260122:*:*:*:*:*:*:*"
  10 β”‚ #CPE 2.2 format
  11 β”‚ #CPE_NAME="cpe:/o:opensuse:tumbleweed:20260122"
  12 β”‚ BUG_REPORT_URL="https://bugzilla.opensuse.org"
  13 β”‚ SUPPORT_URL="https://bugs.opensuse.org"
  14 β”‚ HOME_URL="https://www.opensuse.org"
  15 β”‚ DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed"
  16 β”‚ LOGO="distributor-logo-Tumbleweed"                                                                                                                                    
─────┴───────

Is this something I should be concerned with? Does this even matter? The dist-upgrade seemed to have gone well as the system rebooted fine and I have not noticed anything out of the ordinary during use.

System information (in case it is relevant)

inxi -F
System:
  Host: jadams-Aspire-A315-23 Kernel: 6.18.6-1-default arch: x86_64 bits: 64
  Desktop: LXQt v: 2.3.2 Distro: openSUSE Tumbleweed 20260122
Machine:
  Type: Laptop System: Acer product: Aspire A315-23 v: V1.21
    serial: <superuser required>
  Mobo: DL model: Lotus_DA v: V1.21 serial: <superuser required>
    Firmware: UEFI vendor: Insyde v: 1.21 date: 09/08/2022
Battery:
  ID-1: BAT1 charge: 39.5 Wh (100%) condition: 39.5/41.8 Wh (94.6%)
CPU:
  Info: dual core model: AMD Athlon Silver 3050U with Radeon Graphics bits: 64
    type: MCP cache: L2: 1024 KiB
  Speed (MHz): avg: 1400 min/max: 1400/2300 cores: 1: 1400 2: 1400
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Picasso/Raven 2 [Radeon Vega
    Series / Radeon Mobile Series] driver: amdgpu v: kernel
  Device-2: Chicony VGA WebCam driver: uvcvideo type: USB
  Display: x11 server: X.org v: 1.21.1.21 driver: X: loaded: modesetting
    unloaded: vesa dri: radeonsi gpu: amdgpu resolution: 1: 1680x1050~60Hz
    2: 1920x1080~60Hz
  API: OpenGL v: 4.6 vendor: amd mesa v: 25.3.3 renderer: AMD Radeon
    Graphics (radeonsi raven2 ACO DRM 3.64 6.18.6-1-default)
  Info: Tools: api: glxinfo de: kscreen-doctor x11: xprop,xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP
    Audio driver: snd_hda_intel
  Device-2: Advanced Micro Devices [AMD] Audio Coprocessor
    driver: snd_pci_acp3x
  Device-3: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio
    driver: snd_hda_intel
  API: ALSA v: k6.18.6-1-default status: kernel-api
  Server-1: PipeWire v: 1.5.85 status: active
Network:
  Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
  IF: wlp2s0 state: up mac: 10:a5:1d:83:97:1c
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    driver: r8169
  IF: enp3s0 state: down mac: c0:18:50:a6:09:ea
Bluetooth:
  Device-1: Intel Wireless-AC 3168 Bluetooth driver: btusb type: USB
  Report: rfkill ID: hci0 rfk-id: 2 state: down bt-service: not found
    rfk-block: hardware: no software: no address: see --recommends
Drives:
  Local Storage: total: 2.05 TiB used: 289.38 GiB (13.8%)
  ID-1: /dev/nvme0n1 vendor: SK Hynix model: HFM256GD3JX016N
    size: 238.47 GiB
  ID-2: /dev/sda model: One Touch w/PW size: 1.82 TiB type: USB
Partition:
  ID-1: / size: 235.47 GiB used: 44.36 GiB (18.8%) fs: btrfs
    dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 1022 MiB used: 80.6 MiB (7.9%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-3: /home size: 235.47 GiB used: 44.36 GiB (18.8%) fs: btrfs
    dev: /dev/nvme0n1p2
  ID-4: /opt size: 235.47 GiB used: 44.36 GiB (18.8%) fs: btrfs
    dev: /dev/nvme0n1p2
  ID-5: /var size: 235.47 GiB used: 44.36 GiB (18.8%) fs: btrfs
    dev: /dev/nvme0n1p2
Swap:
  ID-1: swap-1 type: partition size: 2 GiB used: 0 KiB (0.0%)
    dev: /dev/nvme0n1p3
Sensors:
  System Temperatures: cpu: 47.9 C mobo: N/A gpu: amdgpu temp: 47.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 6 GiB available: 5.73 GiB used: 1.93 GiB (33.7%)
  Processes: 270 Uptime: 0h 49m Shell: Bash inxi: 3.3.40

Avenues of Research in an attempt to solve the problem include:

  • General internet searching with keywords of the issue through any forums available
  • Reviewing other forum posts in this forum.
  • Unfortunately, nothing came up that I could find that was relevant to what I am facing.

Any help would be appreciated. Let me know if there is anything needed further to help diagnose this.

Thanks, Jaymo

1 Like

20260123 has been released too. You might do another dup to see if it changes, but I wouldn’t be concerned about what YaST shows as a boot section label unless something is obviously not working right, and you’re booted to the latest kernel 6.18.6.

Snapshot 20260122 (and 20260123) did not include anything related to the kernel or the bootloader, so that the bootloader config was not rebuilt and you are seeing a label for snapshot 20260121 that included the 6.18.6 kernel that triggered a menu config rebuild.

This makes sense, thank you for the responses.

I did a zypper dup just now and my system got upgraded to 20260123.

cat /etc/os-release 
─────┬───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
     β”‚ File: /etc/os-release
─────┼───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
   1 β”‚ NAME="openSUSE Tumbleweed"
   2 β”‚ # VERSION="20260123"
   3 β”‚ ID="opensuse-tumbleweed"
   4 β”‚ ID_LIKE="opensuse suse"
   5 β”‚ VERSION_ID="20260123"
   6 β”‚ PRETTY_NAME="openSUSE Tumbleweed"
   7 β”‚ ANSI_COLOR="0;32"
   8 β”‚ # CPE 2.3 format, boo#1217921
   9 β”‚ CPE_NAME="cpe:2.3:o:opensuse:tumbleweed:20260123:*:*:*:*:*:*:*"
  10 β”‚ #CPE 2.2 format
  11 β”‚ #CPE_NAME="cpe:/o:opensuse:tumbleweed:20260123"
  12 β”‚ BUG_REPORT_URL="https://bugzilla.opensuse.org"
  13 β”‚ SUPPORT_URL="https://bugs.opensuse.org"
  14 β”‚ HOME_URL="https://www.opensuse.org"
  15 β”‚ DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed"
  16 β”‚ LOGO="distributor-logo-Tumbleweed"                                                                                                                                    
─────┴───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

I am also on Linux version 6.18.6.

uname -sr
Linux 6.18.6-1-default

However, the label on GRUB still shows 20260121.

@mrmazda Thank you for letting me know it is nothing to be concerned about. My system has been behaving normally, as far as I can tell.

@OrsoBruno This makes sense and thank you for this information.

I will mark this thread as solved.

Thanks for your help,

Jaymo

I just wanted to post back to this thread that today, I did a zypper dup and got upgraded to 20260126 Tumbleweed.

This also updated the boot entry to also read 20260126.

All is good now. Thanks again!

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.