How to upgrade to Linux Mint 22

If you’ve been waiting for this I’d like to thank you for your patience.

It is now possible to upgrade Linux Mint 21.3 to version 22.

Warning! We are anticipating very high server load and slow download/connection speeds. We recommend to follow this guide to switch to Fastly prior to performing this upgrade: Switch to Fastly to avoid slow upgrades and connection issues.

The upgrade instructions are available at: https://linuxmint-user-guide.readthedocs.io/en/latest/upgrade-to-mint-22.html

Take your time

Read all the instructions and take the time to understand them, ask for help if you’re stuck.

The instructions will ask you to be up to date and to prepare system snapshots. Don’t rush into upgrading and do not take shortcuts.

Don’t panic

If you’re stuck or wondering about something don’t hesitate to ask for help:

Notes

131 comments

  1. I’d like to set “fastly” on LMDE 6.

    My sources list file is :
    deb http://linux-mint.froonix.org faye main upstream import backport

    deb https://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    deb https://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
    deb http://security.debian.org/ bookworm-security main contrib non-free non-free-firmware

    deb https://deb.debian.org/debian bookworm-backports main contrib non-free non-free-firmware

    Which line to edit and replace?
    Can someone reply with an example? thanks.

  2. Is there anyway that an upgrade can be done from the ISO image? I have three PCs, constantly downloading the same files over a slow connection is frustrating. Upgrading online but with a DVD or USB drive connected containing the new system as the file source would be great.

  3. Thanks for the information.
    My upgrade is in an endless loop with the following errors:

    Building module:
    Cleaning build area…
    unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1 ‘make’ -j12 NV_EXCLUDE_BUILD_MODULES=” KERNEL_UNAME=6.8.0-39-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/6.8.0-39-generic/build LD=/usr/bin/ld.bfd CONFIG_X86_KERNEL_IBT= modules………………..(bad exit status: 2)
    Error! Bad return status for module build on kernel: 6.8.0-39-generic (x86_64)
    Consult /var/lib/dkms/nvidia/545.29.06/build/make.log for more information.
    dkms autoinstall on 6.8.0-39-generic/x86_64 succeeded for openrazer-driver
    dkms autoinstall on 6.8.0-39-generic/x86_64 failed for nvidia(10)
    Error! One or more modules failed to install during autoinstall.
    Refer to previous errors for more information.
    * dkms: autoinstall for kernel 6.8.0-39-generic
    …fail!
    run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
    dpkg: error processing package linux-headers-6.8.0-39-generic (–configure):
    installed linux-headers-6.8.0-39-generic package post-installation script subprocess returned error exit status 11
    Setting up linux-headers-6.8.0-38-generic (6.8.0-38.38) …
    /etc/kernel/header_postinst.d/dkms:
    * dkms: running auto installation service for kernel 6.8.0-38-generic
    Sign command: /usr/bin/kmodsign
    Signing key: /var/lib/shim-signed/mok/MOK.priv
    Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

    1. The solution was
      * stop the upgrade
      * remove the nvidia dkms package
      * run mintupgrade again
      * install the nvidia drivers with the driver manager again
      * reboot

      Now it works like a charm

    2. Thanks UWE
      Your solution worked, the nvidia driver was the problem, unfortunately there doesn’t seem to be an nvidia driver available that will work with my system. My PC would not boot with the one provided by the Driver Manager, it looks like I am stuck with the open source driver for now. I was using the nvidia-dkms-390 driver but that appears to have been dropped.
      All the best
      Pete

  4. Thank you, Mint Team! I just did the update and Wilma runs fine!

    I just had one small “issue”: During the upgrade, I needed to decide if I want to keep one configuration file, overwrite it or.. there where to more options. This message only showed up in the terminal, but not mintupgrade UI. So, keep an eye on the terminal.

  5. No boot loader after update
    After the upgrade from LM 21.3 to LM 22 the boot loader doesn’t appear. The boot process is waiting some seconds but nothing happens.
    I use a multiboot system with Win10 and LM 21.3. LM 21.3 was the main system.
    Any idea for a solution?
    erwn16

    1. My upgrade went through trouble free with everything working normally, with a similar multiboot. I do however now get a warning on starting any system of:
      EFI STUB: warning failed to measure data for event 1: 0x8000..0B
      after a few seconds everything proceeds normally.
      If I switch the main boot to one of the other systems (debian), and boot any system,
      the message does not appear.
      I don’t know what it means, or if it is related, but avoiding it could get your LM22 booting.
      This is on an ASUS B660M with NVIDIA 750ti graphics, in case that is related.

    2. I believe the default is a silent/hidden grub boot menu. Unfortunately in my case the update process also installed grub to the MBR over-writing my multi-boot setup. Had to copy the main grub.cfg menu entry from my primary partition into /etc/grub.d/40_custom and run ‘update-grub’ so I could get back into the primary OS and fix things. First time an update did that.

  6. Tried upgrading but after restart I got only a black screen after the bios screen. I could boot to recovery mode but only the wayland session was working there with low resolution. I’m using RX5700 XT.

    1. I was able to do a rollback with timeshift, but any clues what could be going wrong here? I think it’s somehow related to the AMD graphic drivers.

  7. Upgrade went through without a problem but it took a good long while on a fast connection and a desktop computer with 6 individual CPUs–not that I mind at all. By the way, I never leave and update/upgrade unattended. Unattended updates/upgrades and lead to madness. Well, maybe not madness but certainly much annoyance. 😉

    1. Please excuse the typos in my comment. I’m old you know and can see out of only one eye. Perhaps I should change my name from Kirk M to “The One Eyed Mint User”?

  8. Thank you clem and team! Over all it was a good upgrade. Matrix web app is showing up on fresh install but not after upgrading from 21.3. Appreciate if something can be done regarding this. Great job by the team!

  9. Great job! Thank you.

    Clem, can you write instructions for upgraders to install apps that do not exist which exist in fresh install.

    For instance, how do I install matrix? I couldn’t find.

    1. sudo apt install mintchat && cp /etc/skel/.local/share/applications/webapp*.desktop ~/.local/share/applications

  10. On my test computer upgrade from 21.3 to 22 (mate) appears to be completely successful except that it killed Virtualbox because it was the wrong version. Win 10 is not essential on that computer but I will try to get it going again from a .ova file after installing the correct version of Virtualbox. I may decide to go for a fresh install on my main computer since I already have it started on it’s own nvme drive. Windows will be essential there because of my tax software

  11. erwn16
    Dear Linux Mint Team,
    Many thanks for this extensive upgrade!
    The dissemination of this upgrade on a Sunday demonstrates your high level of service orientation. Exemplary!
    Best regards,
    erwn16

  12. The grub disappeared after the upgrade. Had to bring it back with a live usb and Boot Repair followed by update-grub.

  13. LMDE6 goes into fallback mode when I click on synaptic package manager. A box pops up saying cinnamon is running in fallback mode. Is there a fix for this? I am running LMDE6 32 bit. LMDE5 did not have this problem.

  14. Upgrade of 21.3 MATE went smoothly but with bad UX. You may want to consider overhauling the upgrade application’s behaviour. Just starting the snapshot application while keeping the process indicator running in mintupgrade doesn’t tell the user what to do. Also, please make it clear to the user that packages are just removed because there are newer versions.

  15. I can’t wait to check this new release!
    However, I tried the upgrade from 21.3 and noticed the screwed text, terminal window etc., and did not worry too much; but then the upgrade just did not complete. After 5 hours with the wheel spinning and almost zero network, CPU and disk activity I decided to timeshift the system back to 21.3 .
    I will try again in the next weeks, maybe it’s better to have the dust settle a bit.

  16. Hello.
    Upgrade went flawlessly but LM22 retained the screen stuttering of the clean install. It did not calm down and was even happening more often and faster the more time went on. Since nobody else seems to be having trouble with this that this is something specific to my machine, probably due to the repaired mother board.
    So I timeshifted back to LM21.3. “Sighh…”
    Regards

    1. Aahhhh…
      LM21.3-edge works as advertised. OK. This will do for a while.
      Regards

  17. The upgrade crashed (locked keyboard and mouse, had to use the power switch) after this message:

    apt_listdifferences : skipping differences for src:cdrkit – differences already set

    So, why did I have apt_listdifferences installed? Damned if I can remember why. I rebooted without problems, uninstalled apt_listdifferences, started Update Manager, and let that run for an hour or so. Everything is happy now, except that Timeshift still thinks I’m running 21.3 when it takes snapshots (but who cares?)

    1. Hmm. inxi -Sz also says I’m still running 21.3 Virginia.

      Just in case this could cause a potential problem elsewhere, what configuration setting do I need to edit to fix that?

  18. Problem here – after installing Wilma with the Upgrade Tool the first Boot went fine, asking me to install the nvidia driver (nouveaux driver was loaded). But after trying to configure it there appeared an error message that there is an issue with the nvidia driver. So the nouveaux driver was still checked and loaded.
    After rebooting the system tried to load the nvidia driver, without success.
    My question is: what is the exact command to load the nouveaux driver over the terminal, after choosing the compatibility mode?

    1. Hi Ovari,

      That would be part of mint-mirrors and handled by mintsources. We wouldn’t switch your mirrors automatically on your behalf. That being said, we might actually switch packages.linuxmint.com to make use of Fastly directly. We’re also planning networking upgrades to multiply bandwidth output speeds by 10 on our own servers. We’ll have more news on this soon, we’re still testing/finalizing a few things before moving forward with it.

  19. Just upgraded via the upgrade tool from 21.3 to 22 (no dual-boot) on Dell XPS Laptop. I get no logo on boot-up and a long series of messages before the login window appears. Aside from that, Thunderbird produces a second icon when started from the pinned taskbar icon, although no other apps do so. Any suggestions on how to correct these?

    1. Turns out that running update-grub fixed the startup issue. Thunderbird was fixed by removing “Thunderbird Mail” (system version) and installing “Thunderbird” (flatpak version). I did have to copy my account files from my user account .thunderbird folder into .var/app/.org/mozilla.Thunderbird to retain all my mail and settings.

  20. On this laptop all went fine BUT now the update manager does not work.
    Clem – What can I do?
    It hangs on “Generating cache, one moment”.
    I waited 30 minutes and then did a force quit
    Can I uninstall and reinstall?
    Or what?
    Please help!

    1. I uninstalled mintinstall and then installed it.
      Now software manager works.
      So that’s good.
      But why the problem happened remains a mystery!

    2. I had the same problem with mintinstall. Have you uninstalled Flatpak? That was the problem with me.
      Regards
      Helmut

  21. Clem, team, awesome job! Its faster , connectivity speed on the mirrors are crushing it, and it installed in 10 minutes from a cheap thumb drive. I’m loving the new improvements. Backing it up on Tshift as we speak. Matrix looks cool. I’m gonna have a good time with this one.
    Only issue I’ve had so far is with pipewire. No icon in the start menu. When I run it from the terminal, bunch of error messages in red. But I’ve seen some feedback from some beta testers and have no doubt whatsoever that it’ll fulfill my needs.
    After installation, fast and simplistic as ever, I took my time getting Mint customized. This brings me to an idea for a future version of Mint. I have been customizing Mint since as far back as when I first used it, about 17/18. I have a list of instructions I just feed into the cli to make this process a lot simpler, more efficient, but it’s still pretty cumbersome to use a combination of timeshift and manual backups to aid in this process.
    I came up with an idea for a package I call MintMigrator. Basically, it would ask you what settings you want to save, allowing for additional files and folders, and then running a reinstall script from another partition or external drive after upgrading. Problem is, I’m no coder. You won’t be seeing me craft this idea on git anytime soon. But if that’s something you and the team would consider, I’d share my script(s) to aid you 🙂

    1. Dave, you have a great idea there — one that’s already been made into a product you can buy for $25 (from the dev who also created Timeshift). Search for Aptik and you’ll be excited! 🙂

  22. Gtimer is missing in repo. It is not any alternative (it is not system monitor, it is more user monitor of human activity). It would be good create new app from side of team linux mint.

  23. -Try to update->finish process with something like ‘can’t install cinnamon-meta.. ‘
    -Reboot->black screen
    Reboot +F8 (for seeking any error) = black screen
    Live version+Boor tepair= change boot loader txt options but black screen again
    Timefhift->back to 21.3 (save my life)

  24. Worked beautifully! Just another reboot needed before bluetooth worked for some reason, but otherwise smooth sailing with Fastly servers. Many thanks!

  25. I upgraded from 21.3 to 22 on a Asrock Z370 extreme. I had to reinstall smplayer, virtualbox and qt5ct and rename fstab.upgraded to fstab. Everything works and seems faster.
    Thank you so much.

  26. LMDE6 goes into fallback mode when I click on synaptic package manager. A box pops up saying cinnamon is running in fallback mode. Is there a fix for this? I am running LMDE6 32 bit. LMDE5 did not have this problem. I will keep re-posting this until I get an answer from Clem. There is no reason not to answer a simple question.

    1. Well hopefully Clem ignores you! You seem pig ignorant!
      This page is specific to people upgrading to Linux Mint 22,
      not LMDE 6 which was released months ago.
      If you have an issue with LMDE 6, post it in Matrix or in the forums.
      Also, before you post, you could at least run “inxi -G ” in terminal,
      and add the output to your message.
      When you have a problem with your GPU and want people to help you solve it,
      it helps when people know what GPU you’re using.

    2. @Jackie

      Yeah unfortunately LMDE 6 has still some bugs. It also crashes often with Steam or Games (also Firefox) and they also didnt fix the notification window bug about internet connection every time you start LMDE 6. But i think its better to report these bugs on github where the whole Dev Team can read it instead of this blog here.

      @gerry:

      You dont have to be so unfriendly and toxic. Thats why many people say parts of Linux Community are toxic. please take out your uncontrolled rage elsewhere and not on any mint users. thanks

    3. every person should go through 3 things mentally before speaking or writing:

      1. is it true?
      2. is it necessary?
      3. is it friendly?

      this applies to all people.

      greetings

  27. It took a while to upgrade because there was errors with dkms and nvidia / evdi. But I finally succeeded! Thanks Mint for this upgrade!

    But I see there are still a few visual glitches. I’m on Mate and I prefer light colored themes. With Mint-Y, the taskbar background at the bottom becomes black. Is it a bug?

    Personally, I prefer the icons of Mint-X. But for Mint X and Mint-Y, the icons in the toolbars of LibreOffice are barely visible. The background is light gray and the icon is white. Is that also a bug?

    1. I use Mate and prefer Mint X themes and actually use Mint X themes from Mint Mate 20.3. On one computer, I did the upgrade from 21.3 to 22 and the Libreoffice tool bars are perfectly readable with nice black text, just like in Mint 21.3. On my main computer, installed Mint 22 Mate from scratch on it’s own hard drive. On that computer Libreoffice tool bars are horrible with text being white on grey. Same theme as on the computer that had the upgrade, same version for Libreoffice Writer on both – 24.2.4.2 (X86_64). What the heck?

    2. The only thing I have found that makes the toolbars usable in Libreoffice is to use a dark theme and I hate the dark themes. On a Mint 22 install from scratch on a DIFFERENT computer the Libreoffice tool bars are just fine. All computers concerned are Ryzen based and have exactly the same video board.

    3. Within LibreOffice, have you tried other themes (from LO, not Mint?)
      In LO, launch Writer, and in the menu choose Tools Options View and Choose an icon theme.
      I use Colibre (NOT Automatic Colibre), and it siuts my needs.
      Also there is a small icon just after the theme name that reads “Add more icon themes”, where you can click to install other themes and see what suits you.
      Hope this helps

    4. OK – did a little digging and tried this: Select Tools, then select View. The Icon Theme will showed as Coliber SVG Dark. Change to Coliber SVG. At least for me, this has solved the problem with the toolbars!

  28. The upgrade seemed to go pretty smoothly but I saw it kind of going round in circles sometimes, e.g. telling me that it was searching for bootloader images. On a positive note, the horror I felt seeing all those libs disappear were largely unfounded – most things seem to work. Grub did actually install on my first (Win10/sda) drive and populated itself with my other systems.
    A couple of queries I have when starting X-Plane-12:
    I get: libva error: vaGetDriverNames() failed with unknown libva error – any ideas?
    Next I get : jack server is not running or cannot be started
    JackShmReadWritePtr::~JackShmReadWritePtr – Init not done for -1, skipping unlock – why not it is there?
    Lastly I get :ALSA lib pcm_oss.c:397:(_snd_pcm_oss_open) Cannot open device /dev/dsp – sure enough, there is no /dev/dsp. Strange. I looked in timeshift and there is no /dev/dsp there either and yet I have never seen this error. Obviously, the sound is not working now, where it was before but my spearers are working.
    I haven’t had much chance to test anything else yet apart from Firefox

  29. Oops.. for the first Time since 2015 it looks like my old Lady don’t like the Upgrade fully.
    Upgrade runs well, but now i get this Message if i Boot:
    “workqueue: output_poll_execute hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND”
    Then the old Lady need some seconds (60secons i think), then it boots up and all runs fine.
    Looks like its something in the Kernel(?):
    https://askubuntu.com/questions/1499938/kubuntu-22-04-wifi-freeze-after-hwe-kernel-upgrade-to-6-5-was-fine-on-6-2

    Not a dealbreaker for me, maybe with a next Kernel this will be gone.

    My old Lady is an HP EliteBook 8560w, Intel Core i7-2760QM, AMD Radeon FirePro M5950.

    Cheers
    Roland

  30. Sorry guys, all I can say is thank heaven for Timeshift!
    As above, I booted once and it seemed to work OK, apart from the issues with X-Plane-12. I tried to reboot and see if anything would fix itself but instead just got the grub > screen. I had similar problems upgrading from 19.x to 20.0 and had to revert. In the end, I did a clean install of 20 on another drive and then moved all my stuff over to there. That took some time but it worked.
    The upgrade from 20 to 21 went fine but sadly, this one did not! I will do the same thing here, a fresh install on a new, clean drive and see how it goes. I love Mint and have been a user for 10 years or so and would be reluctant to change.

    1. I should add, thank heaven for rEFInd – these little ‘snags’ would be a nightmare without it!

  31. Hi Clem!
    First, thanks for Linux Mint v. 22. It works very smooth and fast.
    It’s a problem though. After two updates of Linux Mint from version 21.3 to 22 on 2 different computers, the Linux Mint logo did not appear on boot. Instead, system service startups were appearing.
    Initially I tried with just the “sudo update-grub” command, but it didn’t work. Then I thought to disable the command line “GRUB_TIMEOUT_STYLE=hidden” in the grub file and then updating grub, again it didn’t work.
    What did I do in the end? I ran the following commands:
    – “sudo update-alternatives –config default.plymouth” (and I also typed “0” – the automatic default value);
    – “sudo update-initramfs -u”;
    and rebooted the system.
    Worked. Now the Linux Mint logo appears. I believe that during the update it does not execute one of the 2 commands above.

    1. I’m coming back. On the second reset, the problem returns. The Linux Mint logo does not appear.
      I’ve also noticed that when scrolling through service startups, they don’t change their character resolution.
      Somewhere there is a bug when loading the system that the Linux Mint logo does not appear and the character resolution does not change if it still appears as the system is loading.

    2. I found that the Linux Mint logo/splash only appears when I choose option 2 – manual from the “sudo update-alternatives –config default.plymouth” command. If I choose option 0 – default, automatic, the logo no longer appears.
      ( Selecție Rută Prioritate Stare
      ————————————————————
      0 /usr/share/plymouth/themes/mint-logo/mint-logo.plymouth 200 mod automat
      1 /usr/share/plymouth/themes/bgrt/bgrt.plymouth 110 mod manual
      * 2 /usr/share/plymouth/themes/mint-logo/mint-logo.plymouth 200 mod manual
      )
      It’s a bug.
      Please Clem or the Linux Mint team fix this issue.
      Thank you.

    3. In fact, the logo sometimes appears, sometimes it doesn’t.
      I specify that all services when starting Linux Mint (Cinnamon) load correctly.
      Strange that when shutting down or restarting the system, the logo appears.
      It’s frustrating. There is a bug somewhere.

  32. Apparently there is some problem with this version when using an AMD gpu. Only a black screen on first boot after the upgrade. Can you please look into this.

  33. I did 4 Upgrades and experienced an issue I haven’t yet resolved only on the last one.

    The last computer is in a state where I have to to a safe boot and then resume to be able to sign in and use the desktop. If I do a normal boot I have no display on the console but the system seems to be otherwise working. I can ssh to is and all server functions are working.

    This computer has a NVIDIA GeForce GTX 1660 Ti Graphics card and is a Dell XPS 8940 Desktop. It has a 10th Generation Intel Core i7-10700 with 8 cores (16 treads), 16 MB Cache, 16 GB DDR4 3200MHz RAM a 512 GB SSD and a 1 TB HD. It is a dual boot machine with the original W10 Home OS as a secondary boot option.

    I have a 4 port KVM switch between the computer and monitor and a Display Port to VGA converter as part of the connection to the KVM switch.

    I have the upgrade log but haven’t seen an issue reported that I recognized as a related problem. This is the second Linux Mint upgrade for this computer.

    Any suggestions on what to look at to resolve this?

    1. I should have said after the upgrade I get a black screen after the grub boot menu if I don’t select the alternate boot to safe mode. As I am looking through other comments I see many mentions of a black screen after a reboot.

    2. O.K. Driver Manager fixed this for me. It recommended nvidia-driver-535 instead of nvidia-driver-470 and after the switch I no longer get a black screen from a normal (non safe mode) boot.

      Maybe I was too quick to comment but then again maybe my comment will help someone else.

      I really do like the Linux Mint mintupgrade process. I like all the detail scrolling past and in the log that I can mostly ignore if the upgrade goes well.

    3. I am looking at my comments and hating the typos. I commented followed by another 10 minutes later. In less than an hour I commented that I had found the fix I had asked for suggestions about myself.

      I am not sure if I followed the “Take your time” guidance in the upgrade instructions. I did 4 machines in quick succession with the first two taking less than 90 minutes each. When I had not resolved a new issue in maybe six hours after I started doing the Linux Mint 22 Upgrades on the fourth and final machine I asked for help. I have been a Linux Mint user for years now and have seen many comments about the Driver Manager resolving issues and know it it part of the Welcome screen in the First Steps section. Right after I asked for help I went there and sure enough I was able to resolve my problem. It was after my second comment where I first mentioned the black screen I had seen in other comments that I though about drivers and the fact that I have an NVIDIA gpu that sometimes needs extra attention with Linux. I did another comment saying I found an answer and reported what I did. I guess the problem with the “Take your time” guidance is that I want to finish and an unfinished task seems like it should be addressed.

      I had already tested the Beta and the Ubuntu 24.04 Noble Numbat LTS release and was prepared for most of the changes affecting me. Maybe this is why I asked for help after only an hour or two of my time looking for the answer.

      So I have now completed a major upgrade of the Operating System within the time of what for many is a normal eight hour workday on four machines. I encountered a few things requiring the install of software and addressing version changes of software. I commented mostly because I had done an evaluation and decided I did not need to undo the upgrade and could live with the unresolved issues for a while because the system was functional. I guess I was hoping someone would help me by tomorrow. Now I guess I hope my comments will help someone tomorrow or the next day. All is well and I can go to sleep (later than many because I am a night-owl and in the Alaska time zone).

  34. Upgraded from 19.3 to 20.0 – 20.3 – 21.0 – 21.3 – 22.0
    Had some 3rdparty packages that I was unable to upgrade. (old raid no longer supported. the reason I’ve postponed the upgrade).
    I then stopped the mintupgrade and removed the repos and packages and it worked fine.
    Found that if you do not stop mintupgrade you will be asked for the same packages all the way. probably stored in memory. Would like to have a remove package button along with the retry.
    But all in all a great experience. I also use RedHat and Ubuntu where I’ve always done clean installs.

  35. Software Manager was looping on startup, with Loading Cache message.

    apt install gir1.2-flatpak-1.0

    seems to have fixed it.

    My system has been through many upgrades, without a fresh install. This was upgrade from 21.3.

  36. I have a problem similar to that reported by LAMurakami. I successfully upgraded a laptop and a desktop with no problems. However, my main computer booted to a black screen after the upgrade. I was able to gain access using recovery mode and then resuming boot, but my display, a 27 inch 2k Dell monitor had a resolution of 800X600. In settings, the display showed as unknown and I was unable to change the resolution. I tried enabling fractional scaling, which helped a bit; but I still was unable to change any other settings, including dropping from 100% to 75%. I was able to Timeshift back to 21.3. I’m now debating whether to try the upgrade again and see if Driver Manager helps or just do a clean install. It’s a Ryzen system with an Asrock motherboard, so I’m doubtful it will help. I am puzzled why Mint 22 didn’t recognize my monitor, as 21.3 gives me no problems. I have a Ryzen 7 7800X with a Radeon 6400 GPU. The other desktop is also Ryzen, a 5600 with a Radeon 550 GPU; which is giving me no problems at all. Odd.

    1. I tried again, with the same results. Interestingly, it seems that I have no driver, if that makes sens. I opened a terminal and ran inxi -G, getting the following.
      Device-1: AMD Navi 24 [Radeon RX 6400/6500 XT/6500M] driver: N/A
      Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X:
      loaded: modesetting,radeon,vesa unloaded: fbdev dri: swrast gpu: N/A
      resolution: 800×600~60Hz
      API: EGL v: 1.5 drivers: kms_swrast,swrast
      platforms: gbm,x11,surfaceless,device
      API: OpenGL v: 4.5 vendor: mesa v: 24.0.9-0ubuntu0.1 renderer: llvmpipe
      (LLVM 17.0.6 256 bits)
      The GPU is a Raseon 6400, which shows as device 1, yet further on it says GPU N/A and the driver is N/A. The driver should be showing as AMDGPU, if I’m not mistaken. Does anyone know if I should try modifying grub for nomodeset?

  37. Hello
    My laptop with LMDE6 had cinnamon upgraded to 6.2.x this morning but so far the other laptop running on LM21.3-edge has not. How long will be the delay?
    Regards

  38. Have upgraded 4 machines successfully. The improvements to the upgrade tool much appreciated, much better than the tool for the upgrade from 20.3 to 21. Only issue is that Skype was removed (so now having to use an unverified flatpak 🙂 ) and it uninstalled softmaker office too. Other than that all went very smoothly. My impressions are that the machines now seem “snappier” in response and suspend/resume a little faster too
    A big thank you to Clem and the team for all their hard work.

  39. Success! As I wrote above, the upgrade didn’t work for me, unfortunately.
    I have lots of ‘stuff’ installed and built from source which is going to take a very long time to migrate. Other programs are no problem, just re-download and install again.
    I installed from scratch on a fresh disk and everything seems to be working well. X-Plane-12 runs fine now too. I only mention X-Plane as it is the most demanding application that I have on my computer and if it won’t run, as after the upgrade, then it’s no good to me
    Hopefully, everything else will work without major problems as well.
    Thanks to the team for all your hard work.

  40. You forgot (?) updating mint-upgrade-info…again…so people don’t get notified about it through mintreport…did you really forget it? What’s up?`:)

  41. After installing Mint 22 Mate I noticed that the aspect ratios of the panes in the workspace switcher were the wrong way round – they were much narrower than on previous Mint versions. I use the switcher a lot to drag windows from one workspace to another and this change makes it harder to do. Fortunately I found a workaround to fix the problem, but I hope it can be properly fixed in a future update.

  42. Another update:
    Not good news for me. As above, I did a fresh install of Mint 22 on a new disk. The installation went smoothly and it booted right up. All the built-in apps seemed to wotk OK as did Qt when I installed it. Code installation was straightforward and worked but I noticed some slight delays now and then. I tried to install nodejs and npm and ran into problems and the computer actually crashed. Not a gentle crash with a screenful of messages but a real hard crash, a black screen with some text flashed up and then immediate shutdown. Not a graceful shutdown, just bang and off. It did boot again and seemed pretty normal but would hang and become unresponsive sometimes with just the spinning beachball, or whatever you want to call it.
    It obviously isn’t going to work for me as is so I will pass on this one for now. Maybe I’ll try again with 22.1.
    On a similar note, I also have a very cheap but fairly new Chinese mini-computer with a Celeron and 8gb. I have installed Mint 22 on there with no problems. I haven’t loaded it up with applications yet but I will start adding the ones I use and see how it copes.
    My main system is Xeon E5 6c/12p @ 3.7ghz, 48GB ECC ram Nvidia 3060 and this is the first time I have seen problems like this.

    1. I’ve been having a few random crashes too.
      I think the current 6.8 kernel is buggy.
      We’ll have to wait for kernel updates to fix whatever the issues are.
      Other than that, Mint 22 is fine, no issues.
      One thing to pay attention to is file system errors.
      Today my system became read-only all of a sudden, so I could not execute anything (even reboot).
      I edited /etc/fstab and removed “errors=remount-ro” and also added the “fsck.mode=force fsck.repair=yes” to GRUB CMDLINE parameters to force a file system repair at every boot.
      It seems to be helping.
      (No there is nothing wrong with my drives, they are in good condition)

  43. It seems that some have boot problems, black or garbled screen. Some may be caused “phantom unknown display problem” from Ubuntu 22.04 with Nvidia drivers. My computer is AMD Ryzen 5 5600G, GTX 1660 Ti, nvidia-driver-535 and sometimes the login screen is partly black/garbled, no login field. But the login field is somewhere and active! If I just type the password, I succeed to login. The screen remains partly black/garbled. I can logout with ctrl+alt+del keys, without a mouse, and the normal login screen with desktop background appears. Now I can login in a perfectly normal manner.

  44. Weird thing: My wife’s computer was at Mint 20.3. Since it’s coming up to its end of life in less than a year, I offered to upgrade it for her (she uses Linux Mint, but has very little tech experience, so I do all the system maintenance on it). Following the upgrade instructions, I upgraded to LM 21 and rebooted. Everything booted normally and seemed fine. I upgraded that to LM 21.3. Everything’s fine. I did the upgrade to LM 22. It booted fine, and everything seemed to work. Then I shut it down. When we turned it back on, it gave showed the BIOS logo, then grub. We selected Linux Mint 22 Cinnamon, but then the screen turned completely black for a really long time. I couldn’t access anything on it, so I did a hard shutoff with the power button. I turned it back on and went to the “recovery mode” option in grub, selected “resume”, and everything worked fine. So next reboot, I removed the “quiet splash” option from the main boot line in grub. It booted just fine. Next reboot, I removed just “quiet”. It didn’t boot. Finally, I removed just “splash” from the line, and it booted fine. So it seems something is wrong with the splash screen on this system. I can’t seem to find any reports of this happening to anyone else, so I’m not sure where to check. So for now, I’ve just edited the default grub file to leave out the “splash”. It boots fast enough that it’s not the end of the world. It’s just an odd thing I thought I’d share of my experience doing this upgrade. Maybe it’ll help someone.

    1. Something similar happens to me too. (https://blog.linuxmint.com/?p=4732#div-comment-424470, including subcomments.) Both after upgrading and using the Linux Mint v. 22 Live ISO, while logging in it does not appear the Linux Mint logo, showing instead the scrolling of how system services are loading.
      I know it’s a bug, but I see that no one from the Linux Mint technical team reads the comments here at all except for the first 2 days after the release of the update of Linux Mint ver. 22.
      Maybe we’ll be lucky if someone from the Linux Mint team reads what the world is writing here. We hope so.

    2. I also had a long lasting black screen after restarting. It appeared that a few entries in fstab were changed to rubbish UUID’s and the system was trying and retrying to mount them. After correcting that the problem was no longer there.

    3. I wrote something wrong before. I rewrite.
      Something similar happens to me too. (https://blog.linuxmint.com/?p=4732#div-comment-424470, including sub-comments.) Both after upgrading and using ISO Linux Mint v. 22 Live, while booting the system logo does not appear Linux Mint, showing instead the scrolling as it loads system services.
      I know it’s a bug, but I see that no one from the Linux Mint technical team reads the comments here at all except for the first 2 days after the release of the update of Linux Mint ver. 22.
      Maybe we’ll be lucky if someone from the Linux Mint team reads what the world is writing here. We hope so.

    4. Hi Mike F

      Had exactly the same experience today, installed the new kernel, shutdown and rebooted to black screen, if I rebooted via recovery mode and resume it worked but the screen model was not detected and it ran at max resolution! Also I did not get my startup sound! I normally just put the machine to sleep so this was the first shutdown in several days. Reverted to the previous kernel and the problem persisted. I then removed the word splash as you suggested and it starts perfectly! Thank you!!!! You have REALLY helped, I am very grateful!! Ryzen 5900x and radeon GX6600 if it helps

    5. Mike:

      You could file a bug report. I _think_ that the right place for this particular bug report would be the following (though I won’t give the exact URL because I fear that so doing would fall foul of the spam filter): github / linuxmint / linuxmint / issues. That is: on github, within the ‘linuxmint’ repository (_sic_!) of Linux Mint.

  45. BUG after installing necessary dependencies as well as in mint 21.3 l2tp VPN does not work says server (error: could not load VPN connection editor)

  46. Bonjour, après être passé à la version de Linux Mint 22 xfce, DaVinci Resolve 18.6 ne fonctionne plus.
    Lorsque je lance DaVinci_Resolve_18.6.6_Linux.run, j’obtiens le message : “Missing or outdated system packages detected. Please install the following missing packages:
    libapr1 libaprutil1 libasound2 libglib2.0-0”.
    Malheureusement, les librairies demandées ne sont plus dans la version 22, alors qu’elles étaient dans le version 21.3.
    Comment résoudre ce problème ?

    1. à Constant :
      Peut-être essayer d’installer manuellement ces fichiers si tu les trouves en .deb quelque part ?
      à voir….

    2. Merci à Paul, mais j’ai déjà essayé toutes ces manipulations et sans succès.
      Il me semble que les paquets n’existent plus dans les dépôts pour le noyau 6.8 de linux Mint 22.
      Faut-il revenir à linux mint 21.3 et son noyau 5 ?
      A suivre ..

    3. Je reviens sur la mise à jour vers Linux Mint 22 : c’est une horreur !
      Non seulement il est impossible de charger les paquets pour DaVinci Resole, mais en plus lorsque j’installe les pilotes nvidia pour ma carte graphique, le redémarrage est impossible (écran noir).
      Je ne sais pas ce qui a été fait avec ce noyau 6.8, mais rien n’a été pensé convenablement.
      Je suis donc revenu à Linx Mint 21.3 xfce et comme par miracle, tout fonctionne comme avant.
      Messieurs et Mesdames les développeurs, pensez à bien tout vérifier avant de lancer une nouvelle version.
      Salutations.

    4. Ce n’est donc peut-être pas un problème avec Linux Mint mais avec DaVinci Resolve qui utilise des paquets obsolètes. Il faudrait d’abord écrire à cet éditeur de logiciel.

  47. I submitted a bug report here – it wasn’t published?! Is there a reason for that? I find it very irritating that I have to experience something like this with you.

  48. I have a Lenovo from 2007 and a second hard drive with Windows xp. After upgrading from 21.3, I could access the XP files through Mint File Manager as usual, but the XP hard drive would not boot up and I never got a grub menu. After using Timeshift to revert to 21.3, everything was back to normal.

    1. After upgrading to Mint 22 and that issue occurs, once on your desktop on Mint 22 like usual, open terminal and do… ‘sudo update-grub’ ; that will probably find the XP HDD and add it to grub menu. now if you want the Grub menu to show on boot (for like 10 seconds) that can be tweaked to…

      sudo xed /etc/default/grub

      then make the following section look like…

      GRUB_TIMEOUT_STYLE=menu
      GRUB_TIMEOUT=10

      after adjusting that save the file and then re-run ‘sudo update-grub’. now when you reboot it ‘should’ show the grub menu like usual.

      p.s. I got a old computer from 2006 (ASUS A8N32-SLI Deluxe motherboard (which I bought back in March 2006, but it’s basically high end 2005 motherboard tech)) and I think mine reacted similarly but I fixed it. basically Mint boots from a 120GB SSD and Win7 boots from 80GB IDE HDD. after I upgraded my grub menu that I used to select between Mint/Win7 was gone but I got it back.

  49. The trial run phase of the upgrade has a screen that lists kept packages, added packages and removed packages. It says press OK if happy with the removed packages or Check Again. Most of the packages don’t mean anything to me but there is one I want to keep. How do I move it to the kept list? Or is the only option to pres OK, even if not happy with the list of removed packages, and what does Check Again achieve if nothing can be changed? There is no relevent option in the hamburger menu to add to a list of kept packages.

  50. Just wanted to say thanks. It’s really a pleasure to use Linux Mint.
    Usually I used to clean install the new system. But this time I was lazy and curious.
    So I tried the upgrade tool and was pleasantly surprised. No flaws, no hiccups, nothing.
    It just worked as unagitatedly reliable as the whole system.
    Once again, thanks for that. Please continue like that, we keep supporting you.

  51. To ThaCrip: Thanks a bunch! I had tried the sudo update-grub which usually always works, but I had to try your idea of editing the grub menu. I never did an edit of the menu before. Now I can boot my XP hard drive and get Mint 22 also. Great!

  52. I missed this update came out until now. I’m happy to say the update went very smooth. And I do like the way updates have gotten easier and more reliable as we’ve progressed, so big thanks for that! It took quite a while, but the lack of hiccups along the way made it well worth it.

  53. I miss two packages gir1.2-gconf-2.0 and libgconf-2-4 for software installation of touchpad-indicator and Bluemail. These deb-packages are missing or are there alternative packages in Mint 22?

    1. I myself do not know the answer to your question, but I can advise as follows. If you do not get a (proper) answer here, then try the Linux Mint ‘matrix’ app thing (which, er, does not get put into the menu if one arrives at Mint 22 via an upgrade) or via the Linux Mint forum or, if needs must, via a bug report on github.

  54. > Warning! We are anticipating very high server load and slow download/connection speeds.

    Are you able to advise when the server load and download/connection speeds have be returned to normal? Thank you

  55. Can t install LM 22 because LM 21.3 has this problem:
    Preparing to unpack …/python3_3.10.6-1~22.04.1_amd64.deb …
    running python pre-rtupdate hooks for python3.10…
    Unpacking python3 (3.10.6-1~22.04.1) over (3.10.6-1~22.04) …
    Setting up python3 (3.10.6-1~22.04.1) …
    running python rtupdate hooks for python3.10…
    E: py3compile:272: Requested versions are not installed
    error running python rtupdate hook xviewer-plugins
    dpkg: error processing package python3 (–configure):
    installed python3 package post-installation script subprocess returned error exit status 4
    Errors were encountered while processing:
    python3
    E: Sub-process /usr/bin/dpkg returned an error code (1)
    A package failed to install. Trying to recover:
    Setting up python3 (3.10.6-1~22.04.1) …
    running python rtupdate hooks for python3.10…
    E: py3compile:272: Requested versions are not installed
    error running python rtupdate hook xviewer-plugins
    dpkg: error processing package python3 (–configure):
    installed python3 package post-installation script subprocess returned error exit status 4
    Processing triggers for man-db (2.10.2-1) …
    Errors were encountered while processing:
    python3

  56. The trial run phase of the upgrade has a screen that lists kept packages, added packages and removed packages. It says press OK if happy with the removed packages or Check Again. Most of the packages don’t mean anything to me but there is one I want to keep. How do I move it to the kept list? Or is the only option to pres OK, even if not happy with the list of removed packages, and what does Check Again achieve if nothing can be changed? There is no relevent option in the hamburger menu to add to a list of kept packages.

  57. Just black screen while/after booting after the upgrade. Only the receovery mode works. Timeshifted back to previous version after attempted fixes with new mesa version didn’t help. GPU: AMD 6900 XT

    1. My screen is working again after removing “splash” from the grub config / boot options. Seems like a problem with the splash screen.

  58. Just one problem… Why doesn’t Wilma support AMD ATI Radeon HD 7560D?

    I found the official AMD drivers and dependencies – so they do exist but apparently cannot be installed in Mint manually. Moreover, as of Wilma, I no longer have any 3-D rendering and 80 percent of my Steam library can no longer be used on Linux Mint now. And the FLICKER!

  59. Lenovo Legion laptop
    Graphics:
    Device-1: AMD Navi 23 [Radeon RX 6650 XT / 6700S 6800S] driver: amdgpu
    v: kernel
    Device-2: AMD Rembrandt [Radeon 680M] driver: amdgpu v: kernel
    Device-3: Chicony Integrated Camera driver: uvcvideo type: USB
    Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X:
    loaded: amdgpu unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi
    gpu: amdgpu resolution: 1920×1200~165Hz
    API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast
    platforms: gbm,x11,surfaceless,device
    API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: PPA renderer: AMD
    Radeon 680M (radeonsi rembrandt LLVM 17.0.6 DRM 3.57 6.8.0-41-generic)
    API: Vulkan v: 1.3.290 drivers: N/A surfaces: xcb,xlib
    Black screen on boot. Autologin not working. Fractional scaling not working. Going to disable splash and retest. Seems to be a configuration/driver bug somewhere.

Leave a Reply

Your email address will not be published. Required fields are marked *