MX 25 Beta 1 Feedback thread

[NakedRider]

Just a quick question - Has anyone tried installing nvidia-driver in MX 25? This went horrible in Debian Trixie. It's still a problem. I'm really hoping this doesn't make it downstream to MX 25.

I have installed with many problems
1) I can not login in Wayland only in X11 and I had to add some parameters to boot options
2) There are many problems appeared in the dmesg log file and I had to install the free nvdidia drivers to my system
here are is the system info

Code: Select all

System:
  Kernel: 6.12.48+deb13-amd64 arch: x86_64 bits: 64 compiler: gcc v: 14.2.0 clocksource: tsc
    avail: acpi_pm parameters: BOOT_IMAGE=/boot/vmlinuz-6.12.48+deb13-amd64 root=UUID=<filter> ro
    quiet splash nvidia-drm.modeset=1
  Desktop: KDE Plasma v: 6.3.6 tk: Qt v: N/A info: frameworks v: 6.13.0 wm: kwin_wayland vt: 1
    dm: SDDM Distro: MX-25_KDE_beta1_x64 Infinity September 21 2025 base: Debian GNU/Linux 13
    (trixie)
Machine:
  Type: Desktop System: Dell product: Precision 3680 v: N/A serial: <superuser required> Chassis:
    type: 3 serial: <superuser required>
  Mobo: Dell model: 0VTKY7 v: A00 serial: <superuser required> part-nu: 0C8C
    uuid: <superuser required> UEFI: Dell v: 1.13.1 date: 03/03/2025
CPU:
  Info: model: Intel Core i9-14900K bits: 64 type: MST AMCP arch: Raptor Lake gen: core 14
    level: v3 note: check built: 2022+ process: Intel 7 (10nm) family: 6 model-id: 0xB7 (183)
    stepping: 1 microcode: 0x12F
  Topology: cpus: 1x dies: 1 clusters: 12 cores: 24 threads: 32 mt: 8 tpc: 2 st: 16 smt: enabled
    cache: L1: 2.1 MiB desc: d-16x32 KiB, 8x48 KiB; i-8x32 KiB, 16x64 KiB L2: 32 MiB
    desc: 8x2 MiB, 4x4 MiB L3: 36 MiB desc: 1x36 MiB
  Speed (MHz): avg: 1071 min/max: 800/5700:6000:4400 scaling: driver: intel_pstate
    governor: powersave cores: 1: 1071 2: 1071 3: 1071 4: 1071 5: 1071 6: 1071 7: 1071 8: 1071
    9: 1071 10: 1071 11: 1071 12: 1071 13: 1071 14: 1071 15: 1071 16: 1071 17: 1071 18: 1071
    19: 1071 20: 1071 21: 1071 22: 1071 23: 1071 24: 1071 25: 1071 26: 1071 27: 1071 28: 1071
    29: 1071 30: 1071 31: 1071 32: 1071 bogomips: 203980
  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: indirect_target_selection 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; PBRSB-eIBRS: SW
    sequence; BHI: BHI_DIS_S
  Type: srbds status: Not affected
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: Intel Raptor Lake-S GT1 [UHD Graphics 770] vendor: Dell driver: i915 v: kernel
    alternate: xe arch: Xe process: Intel 10nm built: 2020-21 ports: active: none empty: DP-1, DP-2,
    DP-3, HDMI-A-1, HDMI-A-2, HDMI-A-3 bus-ID: 0000:00:02.0 chip-ID: 8086:a780 class-ID: 0380
  Device-2: NVIDIA AD107GL [RTX 2000 / 2000E Ada Generation] vendor: Dell driver: nouveau
    v: kernel non-free: 550-570.xx+ status: current (as of 2025-04) arch: Lovelace code: AD1xx
    process: TSMC n4 (5nm) built: 2022+ ports: active: DP-7 empty: DP-4,DP-5,DP-6
    bus-ID: 0000:01:00.0 chip-ID: 10de:28b0 class-ID: 0300
  Device-3: Microsoft LifeCam HD-3000 driver: snd-usb-audio,uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-7.3:6 chip-ID: 045e:0779 class-ID: 0102
  Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6 compositor: kwin_wayland
    driver: X: loaded: modesetting unloaded: fbdev,vesa dri: nouveau,iris gpu: nouveau display-ID: 0
  Monitor-1: DP-7 model: Dell P2725H serial: <filter> built: 2024 res: mode: 1920x1080 hz: 100
    scale: 125% (1.25) to: 1536x864 dpi: 82 gamma: 1.2 size: 598x336mm (23.54x13.23")
    diag: 686mm (27") ratio: 16:9 modes: max: 1920x1080 min: 720x400
  API: EGL v: 1.5 hw: drv: intel iris drv: nvidia nouveau platforms: device: 0 drv: nouveau
    device: 1 drv: iris device: 2 drv: swrast gbm: drv: nouveau surfaceless: drv: nouveau wayland:
    drv: nouveau x11: drv: nouveau
  API: OpenGL v: 4.6 compat-v: 4.3 vendor: mesa v: 25.0.7-2 glx-v: 1.4 direct-render: yes
    renderer: NV197 device-ID: 10de:28b0 memory: 15.6 GiB unified: no display-ID: :1.0
  Info: Tools: api: eglinfo,glxinfo de: kscreen-console,kscreen-doctor wl: wayland-info
    x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Alder Lake-S HD Audio vendor: Dell driver: snd_hda_intel v: kernel
    alternate: snd_soc_avs,snd_sof_pci_intel_tgl bus-ID: 0000:00:1f.3 chip-ID: 8086:7ad0
    class-ID: 0403
  Device-2: NVIDIA AD107 High Definition Audio vendor: Dell driver: snd_hda_intel v: kernel
    bus-ID: 0000:01:00.1 chip-ID: 10de:22be class-ID: 0403
  Device-3: Microsoft LifeCam HD-3000 driver: snd-usb-audio,uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-7.3:6 chip-ID: 045e:0779 class-ID: 0102
  API: ALSA v: k6.12.48+deb13-amd64 status: kernel-api tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.4.5 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-LM vendor: Dell driver: e1000e v: kernel port: N/A
    bus-ID: 0000:00:1f.6 chip-ID: 8086:1a1c class-ID: 0200
  IF: eth0 state: down mac: <filter>
  Device-2: TP-Link 802.11ac WLAN Adapter driver: rtl8852au type: USB rev: 2.0 speed: 480 Mb/s
    lanes: 1 mode: 2.0 bus-ID: 1-8:3 chip-ID: 2357:013f class-ID: 0000 serial: <filter>
  IF: wlan0 state: up mac: <filter>
  Info: services: NetworkManager, nfsd, systemd-networkd, wpa_supplicant
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID Controller Intel driver: vmd v: 0.6
    port: N/A bus-ID: 0000:00:0e.0 chip-ID: 8086:a77f rev: class-ID: 0104
Drives:
  Local Storage: total: 1.86 TiB used: 70.52 GiB (3.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: PC SN8000S WD 2048GB
    size: 1.86 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD
    serial: <filter> fw-rev: 63012101 temp: 32.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 1.86 TiB size: 1.83 TiB (98.37%) used: 70.52 GiB (3.8%) fs: ext4
    dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 8.7 MiB (3.5%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: file size: 11 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 72.0 C mobo: 53.0 C
  Fan Speeds (rpm): cpu: 832 case-1: 688 case-2: 705 case-3: 684
Repos:
  Packages: pm: dpkg pkgs: 3241 libs: 1741 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/brave-browser-release.list
    1: deb [arch=amd64 signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https://brave-browser-apt-release.s3.brave.com/ stable main
  Active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list
    1: deb [arch=amd64] http://dl.google.com/linux/earth/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/insync.list
    1: deb [signed-by=/etc/apt/trusted.gpg.d/insynchq.gpg] http://apt.insync.io/debian trixie non-free contrib
  Active apt repos in: /etc/apt/sources.list.d/debian.sources
    1: deb http://deb.debian.org/debian/ trixie main  contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security/ trixie-security main  contrib non-free non-free-firmware
    3: deb http://deb.debian.org/debian/ trixie-updates  main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.sources
    1: deb http://ftp.cc.uoc.gr/mirrors/linux/mx/mx/repo/ trixie main  non-free
    2: deb http://ftp.cc.uoc.gr/mirrors/linux/mx/mx/repo/ trixie ahs
Info:
  Memory: total: 128 GiB note: est. available: 125.49 GiB used: 6.09 GiB (4.8%)
  Processes: 509 Power: uptime: 2h 11m states: freeze,mem,disk suspend: s2idle wakeups: 0
    hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 50.14 GiB
    services: org_kde_powerdevil,upowerd Init: systemd v: 257 default: graphical tool: systemctl
  Compilers: gcc: 14.2.0 Client: shell wrapper v: 5.2.37-release inxi: 3.3.38
Boot Mode: UEFI

Yikes. I was hoping this problem wouldn't make it downstream.

[FullScale4Me]

Neither XFCE nor KDE 25 betas boot on a Lenovo T430 and a 10 year old HP Envy. Lenovo T480 and X260 boot fine from the same two USB flash drives (used Ventoy for both). The issue is that after I choose to boot in normal mode, it then goes to a black screen with a static underscore. Secure boot is off. I have 23.6 on the same flash drives and they boot fine everywhere.

There might be an issue with the type of partition aka Partition Style of MBR vs GPT (when preparing the Ventoy drive). Generally for newer PCs use GPT. MBR is the default.



More detail on Ventoy use Ventoy – How-To PDF, 433 Kb, illustrated. I am the author. Updated: 02 August 2025.

[kwg]

No matter which option I select for Double click action on the Advanced tab in Window Manager (and even after a reboot, which shouldn't be necessary in any case), double-clicking the title bar shades the window. For example, I select Maximize window for the Double click action, but double-clicking the title bar still shades the window, even though Double click action continues to show Maximize window after reboot.

A related problem: Double-clicking the title bar of a shaded window does not restore the window.

I do not experience these problems with MX Linux 23.6.

Edit: This problem occurs only when using the mx-ease window manager themes. I have re-posted to the mx-ease testing thread.

[Adrian]

No matter which option I select for Double click action on the Advanced tab in Window Manager (and even after a reboot, which shouldn't be necessary in any case), double-clicking the title bar shades the window. For example, I select Maximize window for the Double click action, but double-clicking the title bar still shades the window, even though Double click action continues to show Maximize window after reboot.

A related problem: Double-clicking the title bar of a shaded window does not restore the window.

I do not experience these problems with MX Linux 23.6.

QSI? What flavor you are talking about?

[m_pav]

Hi everyone,
upgrading from a mx23 to mx25beta1 preserving /home: the "second user" can't login till "chown -R" his home, that after upgrade belongs to "1001".
-- Clipped --
Veryfing the owner of the second user home I find "1001".

I don't see anything out of the ordinary here, just standard first Unix user account UID with Debian based systems. The first is always 1000, the second 1002, the third 1003 and so on.

! - - - - EDIT - - - - ! correcting my mistake above , the 2nd user is 1001, third 1002 and so on ! - - - - EDIT - - - - !

I would surmise your second user account was not in fact the second account created on the original installation and it may have been assigned a UID higher than 1001, hence your need to change it.

When saving /home on a multi-user system, it is important to identify each users UID as seen in the original installations /etc/passwd file, then make the accounts in the same order so as not to mess them up.

I have successfully performed multi-user upgrades or reinstalls with MX while re-using /home, and I provisioned them in the Live system before running the installer. Not a single one had a problem with UID values because I copied the lines from the original /etc/passwd to a text file and referenced it as i created each user in the Live system to ensure I provisioned each user in the order in which they were originally created.

I do not recommend folk do this live because the installer will lay down a demo account and skip the account creation process, but if you are a seasoned Linux user, this is a trivial thing to work through and our MX User app is capable of renaming the demo account post install, and again, only for seasoned an experienced users.

[Jerry3904]

The font sets (*.ttf) are inside, see previous post

Did you read this? It's not about being in the same folder it's about having them registered with fontconfig (not sure if accurate but that's what I got when I searched for the issue):

"Because Conky (with use_xft = true) only sees fonts that are registered with fontconfig. It won’t load a .ttf just because it’s in the same folder."

I did, quickly. Didn't totally understand it and I'm working outdoors this afternoon. Can you see how Conky Manager is doing it?

[Adrian]

The font sets (*.ttf) are inside, see previous post

Did you read this? It's not about being in the same folder it's about having them registered with fontconfig (not sure if accurate but that's what I got when I searched for the issue):

"Because Conky (with use_xft = true) only sees fonts that are registered with fontconfig. It won’t load a .ttf just because it’s in the same folder."

I did, quickly. Didn't totally understand it and I'm working outdoors this afternoon. Can you see how Conky Manager is doing it?

That's OK, I checked with dolphin_oracle, the files just need to be copied or linked to ~/.fonts (which is what conky-manager seems to be doing) so it should be an easy fix.

[kwg]

QSI? What flavor you are talking about?

I am testing MX-25_Xfce_beta1_x64 on a QEMU virtual machine, after latest MX updates:

Code: Select all

System:
  Kernel: 6.12.48+deb13-amd64 arch: x86_64 bits: 64 compiler: gcc v: 14.2.0 clocksource: kvm-clock
    avail: tsc,acpi_pm parameters: BOOT_IMAGE=/boot/vmlinuz-6.12.48+deb13-amd64 root=UUID=<filter>
    ro quiet splash
  Desktop: Xfce v: 4.20.1 tk: Gtk v: 3.24.48 wm: xfwm4 v: 4.20.0 with: xfce4-panel
    tools: xfce4-screensaver vt: 7 dm: LightDM v: 1.32.0 Distro: MX-25_Xfce_beta1_x64 Infinity
    September 21 2025 base: Debian GNU/Linux 13 (trixie)
Machine:
  Type: Kvm System: QEMU product: Standard PC (Q35 + ICH9, 2009) v: pc-q35-10.1
    serial: <superuser required> Chassis: type: 1 v: pc-q35-10.1 serial: <superuser required>
  Mobo: N/A model: N/A serial: N/A uuid: <superuser required> BIOS: SeaBIOS
    v: Arch Linux 1.17.0-1-1 date: 04/01/2014
CPU:
  Info: model: Intel Core i3-4160 bits: 64 type: SMP arch: Haswell gen: core 4 level: v3
    note: check built: 2013-15 process: Intel 22nm family: 6 model-id: 0x3C (60) stepping: 3
    microcode: 0x28
  Topology: cpus: 2x dies: 1 clusters: 1 cores: 1 smt: <unsupported> cache:
    L1: 2x 64 KiB (128 KiB) desc: d-1x32 KiB; i-1x32 KiB L2: 2x 4 MiB (8 MiB) desc: 1x4 MiB
    L3: 2x 16 MiB (32 MiB) desc: 1x16 MiB
  Speed (MHz): avg: 3592 min/max: N/A cores: 1: 3592 2: 3592 bogomips: 14366
  Flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: indirect_target_selection mitigation: Aligned branch/return thunks
  Type: itlb_multihit status: KVM: Split huge pages
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
  Type: mds mitigation: Clear CPU buffers; SMT Host state unknown
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  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: Retpolines; IBPB: conditional; IBRS_FW; STIBP: disabled; RSB
    filling; PBRSB-eIBRS: Not affected; BHI: Retpoline
  Type: srbds status: Unknown: Dependent on hypervisor status
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape status: Not affected
Graphics:
  Device-1: Red Hat Virtio 1.0 GPU driver: virtio-pci v: 1 ports: active: Virtual-1 empty: none
    bus-ID: 00:01.0 chip-ID: 1af4:1050 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.16 compositor: xfwm4 v: 4.20.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: swrast gpu: virtio-pci display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1200 s-dpi: 96 s-size: 509x318mm (20.04x12.52") s-diag: 600mm (23.63")
  Monitor-1: Virtual-1 model: QEMU Monitor built: 2014 res: mode: 1920x1200 hz: 60
    scale: 100% (1) dpi: 150 gamma: 1.2 size: 325x203mm (12.8x7.99") diag: 383mm (15.1") ratio: 16:10
    modes: max: 1280x800 min: 640x480
  API: EGL v: 1.5 platforms: device: 0 drv: kms_swrast device: 1 drv: swrast gbm: drv: kms_swrast
    surfaceless: drv: kms_swrast x11: drv: swrast inactive: wayland
  API: OpenGL v: 4.5 vendor: mesa v: 25.0.7-2 glx-v: 1.4 direct-render: yes renderer: llvmpipe
    (LLVM 19.1.7 256 bits) device-ID: ffffffff:ffffffff memory: 3.74 GiB unified: yes
  Info: Tools: api: eglinfo,glxinfo de: xfce4-display-settings x11: xdriinfo, xdpyinfo, xprop,
    xrandr
Audio:
  Device-1: Intel 82801I HD Audio vendor: Red Hat QEMU Virtual Machine driver: snd_hda_intel
    v: kernel bus-ID: 00:1b.0 chip-ID: 8086:293e class-ID: 0403
  API: ALSA v: k6.12.48+deb13-amd64 status: kernel-api tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.4.5 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: Red Hat Virtio 1.0 network driver: virtio-pci v: 1 pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: N/A bus-ID: 01:00.0 chip-ID: 1af4:1041 class-ID: 0200
  IF-ID-1: eth0 state: up speed: -1 duplex: unknown mac: <filter>
  Info: services: NetworkManager, nfsd, systemd-networkd, wpa_supplicant
Drives:
  Local Storage: total: 12 GiB used: 8.81 GiB (73.4%)
  ID-1: /dev/vda maj-min: 254:0 model: N/A size: 12 GiB block-size: physical: 512 B
    logical: 512 B speed: <unknown> tech: N/A serial: N/A scheme: MBR
  SMART Message: Unknown smartctl error. Unable to generate data.
Partition:
  ID-1: / raw-size: 12 GiB size: 11.71 GiB (97.58%) used: 8.81 GiB (75.3%) fs: ext4 dev: /dev/vda1
    maj-min: 254:1
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: file size: 768 MiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  Src: lm-sensors+/sys Message: No sensor data found using /sys/class/hwmon or lm-sensors.
Repos:
  Packages: pm: dpkg pkgs: 2211 libs: 1118 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.sources
    1: deb http://deb.debian.org/debian/ trixie main  contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security/ trixie-security main  contrib non-free non-free-firmware
    3: deb http://deb.debian.org/debian/ trixie-updates  main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.sources
    1: deb http://la.mxrepo.com/mx/repo/ trixie main  non-free
Info:
  Memory: total: 4 GiB available: 3.83 GiB used: 1.53 GiB (40.0%)
  Processes: 256 Power: uptime: 5m states: freeze,mem,disk suspend: s2idle wakeups: 0
    hibernate: shutdown avail: reboot,suspend,test_resume image: 1.48 GiB
    services: upowerd,xfce4-power-manager Init: systemd v: 257 default: graphical tool: systemctl
  Compilers: gcc: 14.2.0 Client: shell wrapper v: 5.2.37-release inxi: 3.3.38
Boot Mode: BIOS (legacy, CSM, MBR)

[dolphin_oracle]

Hi everyone,
upgrading from a mx23 to mx25beta1 preserving /home: the "second user" can't login till "chown -R" his home, that after upgrade belongs to "1001".
-- Clipped --
Veryfing the owner of the second user home I find "1001".

I don't see anything out of the ordinary here, just standard first Unix user account UID with Debian based systems. The first is always 1000, the second 1002, the third 1003 and so on.

I would surmise your second user account was not in fact the second account created on the original installation and it may have been assigned a UID higher than 1001, hence your need to change it.

When saving /home on a multi-user system, it is important to identify each users UID as seen in the original installations /etc/passwd file, then make the accounts in the same order so as not to mess them up.

I have successfully performed multi-user upgrades or reinstalls with MX while re-using /home, and I provisioned them in the Live system before running the installer. Not a single one had a problem with UID values because I copied the lines from the original /etc/passwd to a text file and referenced it as i created each user in the Live system to ensure I provisioned each user in the order in which they were originally created.

I do not recommend folk do this live because the installer will lay down a demo account and skip the account creation process, but if you are a seasoned Linux user, this is a trivial thing to work through and our MX User app is capable of renaming the demo account post install, and again, only for seasoned an experienced users.

fehlix reported this. said hardinfo2 installation was creating a user account when we build the isos, with the user being 1001. in effect, the hardinfo2 user "owned" that preexisitng home directory.

I don't like that behavior at all. if that cannot be adjusted, I will remove hardinfo2 from the default installations.

[Melber]

Using mx-ease-themes_25.09.02...

With the mx-ease theme, in galculator, without a value saved yet to memory...

• The text on the MR and M+ buttons is invisible (probably because the text and background have the same color) instead of being grayed out against a background of a different color.

• Unlike all the other galculator buttons, the MS, MR and M+ buttons do not display a border, even after a value has been saved to memory.

With the mx-ease-Dark theme, in galculator...

• While text on the MS, MR and M+ buttons is always visible, borders do not appear on these buttons, whether or not a value has been saved to memory.

@kwg thanks for the report, I'll look into it.