Upgrading from MX-21 to MX-23 and getting an error  [Solved]

Help for Current Versions of MX
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Forum rules
Post Reply
Message
Author
User avatar
oldejimmy
Posts: 4
Joined: Tue Apr 15, 2025 3:34 pm

Upgrading from MX-21 to MX-23 and getting an error  [Solved]

#1 Post by oldejimmy »

Upgrading from MX-21 to MX-23 and getting an error,

https://mxlinux.org/wiki/system/upgradi ... nstalling/

sudo apt install mx23-archive-keyring
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package mx23-archive-keyring

is there something doing wrong?

Code: Select all

Snapshot created on: 20250331_1552
System:    Kernel: 6.1.0-9mx-ahs-amd64 [6.1.27-1~mx21ahs+1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-9mx-ahs-amd64 root=UUID=<filter> ro quiet 
           splash init=/lib/systemd/systemd 
           Desktop: N/A wm: xfwm 4.18.0 vt: 7 dm: LightDM 1.26.0 
           Distro: MX-21.3_x64 Wildflower April 9  2022 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop System: Dell product: XPS 8930 v: 1.1.30 serial: <filter> Chassis: 
           type: 3 serial: <filter> 
           Mobo: Dell model: 0DF42J v: A00 serial: <filter> UEFI: Dell v: 1.1.30 date: 03/14/2023 
Battery:   Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M510 serial: <filter> 
           charge: 55% (should be ignored) rechargeable: yes status: Discharging 
CPU:       Info: 6-Core model: Intel Core i7-8700 bits: 64 type: MT MCP arch: Kaby Lake 
           note: check family: 6 model-id: 9E (158) stepping: A (10) microcode: FA cache: 
           L2: 12 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 76799 
           Speed: 900 MHz min/max: 800/4600 MHz Core speeds (MHz): 1: 900 2: 900 3: 900 4: 900 
           5: 900 6: 900 7: 900 8: 900 9: 900 10: 900 11: 900 12: 900 
           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 mitigation: TSX disabled 
Graphics:  Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] vendor: Dell driver: i915 v: kernel 
           bus-ID: 00:02.0 chip-ID: 8086:3e92 class-ID: 0380 
           Device-2: NVIDIA GP104 [GeForce GTX 1070] vendor: Dell driver: nvidia v: 470.256.02 
           bus-ID: 01:00.0 chip-ID: 10de:1b81 class-ID: 0300 
           Device-3: Logitech HD Pro Webcam C920 type: USB driver: snd-usb-audio,uvcvideo 
           bus-ID: 1-12:7 chip-ID: 046d:082d class-ID: 0102 serial: <filter> 
           Display: x11 server: X.Org 1.20.11 compositor: xfwm4 v: 4.18.0 driver: loaded: nvidia 
           display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x286mm (40.0x11.3") 
           s-diag: 1055mm (41.6") 
           Monitor-1: DP-3 res: 1920x1080 hz: 60 dpi: 82 size: 598x336mm (23.5x13.2") 
           diag: 686mm (27") 
           Monitor-2: DP-5 res: 1920x1080 hz: 60 dpi: 82 size: 598x336mm (23.5x13.2") 
           diag: 686mm (27") 
           OpenGL: renderer: NVIDIA GeForce GTX 1070/PCIe/SSE2 v: 4.6.0 NVIDIA 470.256.02 
           direct render: Yes 
Audio:     Device-1: Intel 200 Series PCH HD Audio vendor: Dell driver: snd_hda_intel v: kernel 
           bus-ID: 00:1f.3 chip-ID: 8086:a2f0 class-ID: 0403 
           Device-2: NVIDIA GP104 High Definition Audio vendor: Dell driver: snd_hda_intel 
           v: kernel bus-ID: 01:00.1 chip-ID: 10de:10f0 class-ID: 0403 
           Device-3: BEHRINGER UMC204HD 192k type: USB driver: snd-usb-audio bus-ID: 1-10:6 
           chip-ID: 1397:0508 class-ID: fe01 
           Device-4: Logitech HD Pro Webcam C920 type: USB driver: snd-usb-audio,uvcvideo 
           bus-ID: 1-12:7 chip-ID: 046d:082d class-ID: 0102 serial: <filter> 
           Sound Server-1: ALSA v: k6.1.0-9mx-ahs-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell 
           driver: ath10k_pci v: kernel port: e000 bus-ID: 03:00.0 chip-ID: 168c:0042 
           class-ID: 0280 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Qualcomm Atheros Killer E2400 Gigabit Ethernet vendor: Dell driver: alx 
           v: kernel port: d000 bus-ID: 04:00.0 chip-ID: 1969:e0a1 class-ID: 0200 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-8:5 
           chip-ID: 0cf3:e009 class-ID: e001 
           Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2 
           sub-v: 25a hci-v: 4.2 
           Info: acl-mtu: 1024:8 sco-mtu: 50:8 link-policy: rswitch hold sniff 
           link-mode: slave accept service-classes: rendering, capturing, audio 
Drives:    Local Storage: total: 7.97 TiB used: 371.24 GiB (4.6%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/nvme0n1 maj-min: 259:5 vendor: Samsung model: SSD 970 EVO Plus 500GB 
           size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 
           type: SSD serial: <filter> rev: 2B2QEXM7 temp: 41.9 C scheme: GPT 
           ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Toshiba model: KXG50ZNV256G NVMe 256GB 
           size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 
           type: SSD serial: <filter> rev: AADA4101 temp: 39.9 C scheme: GPT 
           ID-3: /dev/sda maj-min: 8:0 vendor: Seagate model: ST2000DM001-1ER164 size: 1.82 TiB 
           block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 
           serial: <filter> rev: CC27 scheme: GPT 
           ID-4: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST4000DM005-2DP166 size: 3.64 TiB 
           block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5980 
           serial: <filter> rev: 0001 scheme: GPT 
           ID-5: /dev/sdc maj-min: 8:32 vendor: Western Digital model: WD20EZRX-00DC0B0 
           size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: N/A 
           serial: <filter> rev: 0A80 scheme: GPT 
Partition: ID-1: / raw-size: 457.5 GiB size: 449.25 GiB (98.20%) used: 97.1 GiB (21.6%) fs: ext4 
           dev: /dev/nvme0n1p2 maj-min: 259:7 
           ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 275 KiB (0.1%) fs: vfat 
           dev: /dev/nvme0n1p1 maj-min: 259:6 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2 
           dev: /dev/nvme0n1p3 maj-min: 259:8 
Sensors:   System Temperatures: cpu: 47.0 C mobo: 27.8 C gpu: nvidia temp: 45 C 
           Fan Speeds (RPM): cpu: 1629 mobo: 679 gpu: nvidia fan: 29% 
Repos:     Packages: 2843 note: see --pkg apt: 2821 lib: 1436 flatpak: 22 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/boot-repair.list 
           1: deb [signed-by=/etc/apt/keyrings/boot-repair.gpg] https://ppa.launchpadcontent.net/yannubuntu/boot-repair/ubuntu noble main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian/ bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security/ bullseye-security main contrib non-free
           3: deb-src http://deb.debian.org/debian/ bullseye non-free contrib main
           4: deb http://deb.debian.org/debian/ bullseye-backports non-free contrib main
           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
           No active apt repos in: /etc/apt/sources.list.d/mx.list 
           Active apt repos in: /etc/apt/sources.list.d/nordvpn.list 
           1: deb https://repo.nordvpn.com//deb/nordvpn/debian/ stable main
           Active apt repos in: /etc/apt/sources.list.d/onlyoffice.list 
           1: deb https://download.onlyoffice.com/repo/debian squeeze main
           Active apt repos in: /etc/apt/sources.list.d/signal-xenial-added-by-mxpi.list 
           1: deb [arch=amd64] https://updates.signal.org/desktop/apt/ xenial main
           Active apt repos in: /etc/apt/sources.list.d/thorium.list 
           1: deb [arch=amd64 trusted=yes] https://dl.thorium.rocks/debian/ stable main
           Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
           1: deb [arch=amd64] https://repo.vivaldi.com/stable/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/yannubuntu-ubuntu-boot-repair-plucky.list 
           1: deb http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu plucky main
Info:      Processes: 307 Uptime: 7h 42m wakeups: 26 Memory: 62.64 GiB used: 3.61 GiB (5.8%) 
           Init: systemd v: 247 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: UEFI
Thank you for your time!
Top
User avatar
5th.attempt
Posts: 50
Joined: Tue Mar 18, 2025 7:02 pm

Re: Upgrading from MX-21 to MX-23 and getting an error

#2 Post by 5th.attempt »

Your Repos are Bullseye they should be Bookworm:

Try again updating your Repo Source.

OR its an older Information.

Code: Select all

Repos:     Packages: 2843 note: see --pkg apt: 2821 lib: 1436 flatpak: 22 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/boot-repair.list 
           1: deb [signed-by=/etc/apt/keyrings/boot-repair.gpg] https://ppa.launchpadcontent.net/yannubuntu/boot-repair/ubuntu noble main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian/ bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security/ bullseye-security main contrib non-free
           3: deb-src http://deb.debian.org/debian/ bullseye non-free contrib main
           4: deb http://deb.debian.org/debian/ bullseye-backports non-free contrib main
           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
           No active apt repos in: /etc/apt/sources.list.d/mx.list 
           Active apt repos in: /etc/apt/sources.list.d/nordvpn.list 
           1: deb https://repo.nordvpn.com//deb/nordvpn/debian/ stable main
           Active apt repos in: /etc/apt/sources.list.d/onlyoffice.list 
           1: deb https://download.onlyoffice.com/repo/debian squeeze main
           Active apt repos in: /etc/apt/sources.list.d/signal-xenial-added-by-mxpi.list 
           1: deb [arch=amd64] https://updates.signal.org/desktop/apt/ xenial main
           Active apt repos in: /etc/apt/sources.list.d/thorium.list 
           1: deb [arch=amd64 trusted=yes] https://dl.thorium.rocks/debian/ stable main
           Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
           1: deb [arch=amd64] https://repo.vivaldi.com/stable/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/yannubuntu-ubuntu-boot-repair-plucky.list 
           1: deb http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu plucky main
Top
User avatar
kmathern
Developer
Posts: 2589
Joined: Wed Jul 12, 2006 2:26 pm

Re: Upgrading from MX-21 to MX-23 and getting an error

#3 Post by kmathern »

Repos: Packages: 2843 note: see --pkg apt: 2821 lib: 1436 flatpak: 22
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/boot-repair.list
1: deb [signed-by=/etc/apt/keyrings/boot-repair.gpg] https://ppa.launchpadcontent.net/yannub ... air/ubuntu noble main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian/ bullseye main contrib non-free
2: deb http://security.debian.org/debian-security/ bullseye-security main contrib non-free
3: deb-src http://deb.debian.org/debian/ bullseye non-free contrib main
4: deb http://deb.debian.org/debian/ bullseye-backports non-free contrib main
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
No active apt repos in: /etc/apt/sources.list.d/mx.list
Active apt repos in: /etc/apt/sources.list.d/nordvpn.list ...
It looks like the mx repo(s) are disabled.
Top
juwido
Posts: 23
Joined: Thu Apr 25, 2024 12:55 pm

Re: Upgrading from MX-21 to MX-23 and getting an error

#4 Post by juwido »

You should read this: https://mxlinux.org/migration/
Top
User avatar
Eadwine Rose
Administrator
Posts: 15152
Joined: Wed Jul 12, 2006 2:10 am

Re: Upgrading from MX-21 to MX-23 and getting an error

#5 Post by Eadwine Rose »

You HAVE read this bit, I hope?

"This how-to is for the benefit of advanced users who are comfortable with the command line and willing to research and fix things if things go wrong, it’s not guaranteed to work and is not supported in any way by the dev team."
MX-23.6_x64 July 31 2023 * 6.1.0-38amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Top
User avatar
m_pav
Developer
Posts: 1857
Joined: Sun Aug 06, 2006 3:02 pm

Re: Upgrading from MX-21 to MX-23 and getting an error

#6 Post by m_pav »

It's best to reinstall and re-use home, but even therein you can run into a condition where re-using old configs will leave your Desktop theming looking like it's been hit with the ugly stick. This is most prevalent when user customisations have been added, but it can happen the the default theme too, therefore I recommend using the same login name, but choosing the option to let the installer rename your old account. Doing it this way, elements from the old can be moved into the new, with one specific piece of knowledge required - do not overwrite the standard folders with the old ones, move the data from the old folders to the new.
The standard folders are what you see when you first open the File Manager to your home after installing. I do not suggest overwriting any of the folders that contain your desktop and theming configs, these are best set up from scratch.

IIRC, the User Installed Packages was made available for MX21, so run that on your old system first, save the list and use that list to repopulate the new installation. You can do it either live prior to running the installer where you'll need lots of RAM and/or a swap partition available (automatically used if exists), or run it after you've logged into the new installation, either way you'll get the same result.
Mike P

Regd Linux User #472293
(Daily) Lenovo T560, i7-6600U, 16GB, 2.0TB SSD, MX_ahs
(ManCave) AMD Ryzen 5 5600G, 32G, 8TB mixed, MX_ahs
(Spare)2017 Macbook Air 7,2, 8GB, 256GB SSD, MX_ahs
Top
User avatar
oldejimmy
Posts: 4
Joined: Tue Apr 15, 2025 3:34 pm

Re: Upgrading from MX-21 to MX-23 and getting an error

#7 Post by oldejimmy »

Thank you for the help!
Top
Post Reply

Return to “MX Help”