How to upgrade to Linux Mint 19

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

It is now possible to upgrade the Cinnamon, MATE and Xfce editions of Linux Mint 18.3 to version 19.

The upgrade instructions are available at:

Upgrade for a reason

“If it ain’t broke, don’t fix it”.

Linux Mint 17, 17.1, 17.2 and 17.3 are supported until 2019 and Linux Mint 18, 18.1, 18.2 and 18.3 are supported until 2021.

You might want to upgrade to Linux Mint 19 because some bug is fixed or because you want to get some of the new features. In any case, you should know why you’re upgrading.

As excited as we are about Linux Mint 19, upgrading blindly for the sake of running the latest version does not make much sense, especially if you’re already happy and everything is working perfectly.

Make sure to read the release notes and to know about the new features so you have all the information you need before deciding whether you want to upgrade.

Make sure also to try Linux Mint 19, in live mode, to know if it works well with your hardware.

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 make backups, to prepare system snapshots and to try Linux Mint 19 in live mode. 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:

  • You can post here in the comments section.
  • You can ask for help in the forums.
  • You can connect to the IRC (from within Linux Mint, launch Menu->Internet->Hexchat). If you’re new to IRC, please read this tutorial.


  1. Click on “Edit”->”Profile Preferences”->”Scrolling”.

    Check the “unlimited” option and click “OK”.

    There is no option for unlimited scrolling.There is a option of “Limit scrollback to”.

    On applying “apt install mintupgrade”, I got this

    apt install mintupgrade
    Reading package lists… Done
    Building dependency tree
    Reading state information… Done
    E: Unable to locate package mintupgrade

    Os: Linux mint 18.3.,64bit.

    1. Evowise CDN is my mirror.It is wicked fast in my area. Anyway ,how to switch to default respositories?
      Also,where is the option for unlimited scorolling.

      After installing the mintupgrade .deb 18.3.5, When I click upgrade check ,it is forcing me to have a backup,showing error in red colour cmd. I have only 500gb of a single hard disk,no storage.How to skip the compulsory backup.Why is the forced backup?

    2. After installing the mintupgrade .deb ,I opened cmd,applied “mintupgrade download”.It downloaded stuffs for 15 minutes.

      Then update manager shows mint updtae 5.02.20 something ,I installed it.

      Then boom,a lot of update is showing up in update manager.I have to download,install it or I should apply mintupgrade upgrade in cmd.

    3. @a: To switch to the default repositories, run Software Sources then, in the Official repositories tab, click on “Restore the default settings”.

    4. I too am getting this problem and I reset things to the default repositories and updated my caches and am still getting this error.

    5. please disregard my last comment, I found that the problem was actually that I never upgraded from 18.2 to 18.3 and didn’t realize it.

    6. I believe that ‘unlimited scrolling’ is not an option in xfce, GNOME terminal 3.18.3.

    1. Do I really need to remove the packages it showed to remove after applying mintupgrade check in cmd. I have 500 packages showing to remove.I need to remove it manually each by each.

    1. After 4 hours spent on upgrade process, the screen was suspended & lo all went wrong! The login manager wasn’t showing password field first. Somehow after few restart the desktop appeared but I couldn’t find the launcher, panel! Pressing super key gave no results!! I think I need fresh install

    1. It works on systems with docker installed. I use docker a lot personally. It might not work within docker though.

  2. I install LM19 in a VM yesterday and it’s blazing fast.
    I couldn’t find a way to share the desktop though.
    On the laptop I’m using right now with LM 18.3, I go to Desktop Sharing and enable it there but couldn’t find a similar setting in LM 19.

    Am I looking in the wrong place or do I need to install a separate VNC server?

  3. Why are we FORCED to use Timeshift and make system back-ups? How can I override this requirement?
    I don’t care if the upgrade fucks up my system, I’ll just zero the disk and do a clean install in case that happens.

    Please remember: It is my computer and it should be my choice and my choice alone whether I make a back-up or not. Please don’t force things on people.

    1. @osmcuser
      You know what’s funny? I actually used Timeshift because I didn’t know it could be avoided, but when that wonderful upgrade turned my completely clean new 18.3. into an unusable mess of UI bugs it wouldn’t even let me restore it. Just froze and smiled at me ….

  4. just upgraded it as a virtual box guest. seems ok, aside from 1 weird issue. it doesn’t auto mount the shared folder i have with win10 host. i clean installed 18.3 a few days ago and that worked just fine without any drama. upgraded to 19.0 and it’s acting up. if i install the guest addition, then the shared folder gets mounted and can be accessed just fine. but if i reboot the guest client, it disappears again until i reinstall guest addition. user is already in the vboxsf group.

    1. as far as i can tell, i’m using the oracle ones, from the vbox_GA_x5.2.14 iso
      i even upgraded from 5.2.12->5.2.14 to no avail.

    2. to be more clear.. when i say not mounted, if i go to the directory /media/sf_shared/ and open it, it’ll show an empty folder.. if i then do the insert guess addition iso and install, the directory will have contents…

    3. made a new vm with fresh 19 install. the mounted drive showed up just fine. not sure what went wrong during the upgrade..

  5. Hello, I really like Mint, but why is it still not possible to have an user freindly and easy upgrade path?
    If Linixmint aims to be real alternative to the mainstream OS it must be usable also for non coputer affine people.

  6. Using default Software Sources…
    apt install lightdm lightdm-settings slick-greeter
    Reading package lists… Done
    Building dependency tree
    Reading state information… Done
    E: Unable to locate package lightdm-settings
    E: Unable to locate package slick-greeter

  7. I just upgraded to Mint 19 and after reboot my computer does no longer accept my VALID password, so I cannot login! Also got a “kernel panic” when trying to boot another Linux distro (Manjaro) from another partition on my disk. Just terrible… I’ll guess I’ll have to use Timeshift to restore Mint 18.3, because clearly there is something wrong.

    1. Hi Luke,

      What doesn’t accept your password? Is that LightDM? did you try to log in via console? Did you switch from MDM to LightDM prior to upgrading?

      In regards to the other OS, it shouldn’t affect it at all. At most it would regenerate the Grub menu.

    2. Hi, i have the same problem, but i tested something and tried a wrong Password. LightDM complaints about the password as usual. If i try my valid Password LightDM do not complain but shows the Startpage with the Entry Form again and again. I switched to LightDM about 6 Month ago i think.

    3. manjaro doesn’t like other distro’s bootloaders… I usually install manjaro last and then lock the grub version in mint. Manjaro’s grub seems to boot other linux distros and windows just fine

  8. Hi!
    After a fresh install of LM 19 Cinnamon 64-bit I encountered a problem with my Acer Aspire laptop – I have disabled all close lid functions and when I close the lid instead of just turning the monitor off (like it as with LM 17 & 18) the OS now locks my computer as well and I have to enter password each time I open my laptop. I think that this is a bug, because previously this function worked flawlessly and now there is this annoying unlocking I have to do. Not a great deal, but still.
    Another more serious problem I also had with LM 18 (but not with LM 17) and it is still present at LM 19 – I cannot apply any changes to monitor settings. Whenever I click on “apply”, an error would pop up and tell me that something is missing. I can provide more details about my hardware specs and error message contents should there be anyone willing to look into these bugs.
    Other than that – thanks for the fresh distro. Although it is a shame to see that many options for window border decorations are now gone (I really liked Metabox) I guess LM developers are trying to steer away from old school looks. Not a fan of Mint-Y looks and default grayish colors, but at least I can still customize my desktop looks as I please with Mint-X and custom themes. I also noticed, that LM has dropped Brasero, which is fine by me. I preferred to use K3B anyway. Well if that is the case and LM is ditching some software only few might need, may I suggest to also remove the provided torrent software? This way You could trim down a few more bites and a user could choose his own software for his torrential needs (like qBittorrent) and not have the need to remove/disable an existing one.
    Also quite disappointed that the provided Driver manager did not provide proprietary AMD drivers. I have already submitted requests at Launchpad for LM 18 regarding AMD drivers with no results, so I will not waste my time and request the same thing for LM 19 too. And another thing, there is also no visible improvement for this bug: Then again, I have no faith that Launchpad bugs are being monitored by LM team on a regular and methodical base. Anyway, I got LM for free, I made some donations on my own accord and I am grateful for the thing I already use. It could be a lot better, but for now this will do just fine.

  9. If I upgrade LMC 18.3 to LMC 19, my printer Canon IP1800 will be still work? Because I didn’t seek such for last version of Cinnamon.

  10. Hi. Just upgraded to Mint 19 from Mint 18.3 on my Toshiba Satellite A200-27R. Have had no problems using 18.3. Boot time on Mint 19 i.e power up to being ready to use is currently taking a little over 8 mins. I have updated the kernels per the 2 updates. Any body else have this problem. Any solution ?

    1. Hi,

      Check if /etc/initramfs-tools/conf.d/resume contains a UUID which doesn’t exist (you can list your UUIDs with “blkid”). If it does, remove this file. This is known to cause boot delays.

      Other than that, don’t hesitate to use “systemd-analyze critical-chain” to troubleshoot your boot sequence.

    2. I can confirm it. it will simply hang before login screen, but when I press CTRL+ALT+F1 to drop to a console after a few seconds login screen will appear. I didn’t do anything. it just appear. Everything is fine before kernel update. I think is causing the problem, will try it again.

  11. Hi, after boot i cannot login, though i can login in the console. After entering password the screen went Black and im presented the login screen again. I forgot to switch to lightdm before Upgrade but now i have it
    cat /etc/X11/default-display-manager gives me lightdm.
    any chance to repair IT?

    1. Hi,

      You can check .xsession-errors for clues. If something is missing, misconfigured or broken, it’s likely to complain about it in there. The upgrader shouldn’t let you upgrade if you’re still using MDM.

    2. I had the same issue and managed to fix it. Try this:

      1) From login screen switch to the second console by pressing Ctrl+Alt+F2.
      2) Login as root.
      3) Uninstall a package ‘apt purge gnome-user-share’.
      4) Reboot and try to login again.

      That worked for me.

    3. I’m having the same issue over here. Any time I try to log in after booting, it just briefly goes to a black screen then asks me to log in again and repeats this forever. I’ve tried other kernels, fixing broken packages, fsck, gnome and as Vitality recommended ‘apt purge gnome-user-share’. None of these resolved the issue. What else can I look at? Going into recovery and a root terminal and typing ‘startx’ also has some issues, but I’m not sure that’s the correct way to get a gui these days.

    4. Actually ‘sudo apt purge gnome-user-share’ DID work for me as well. I originally tried it from a shell in recovery mode, but I don’t think that has write access by default or it doesn’t mount everything.
      Thanks Vitality!

    5. I have the same issue.

      The package “gnome-user-share” is not present. The file “.xsession-errors” says that an exception occured inside “mate-session” due to “libglib-2.0”.

    6. Hi Antonio,

      That’s a bit weird.. the upgrader is supposed to remove vino.. It doesn’t purge it though. We’ll try to reproduce the issue.

    7. This one hit me too, and I had lightdm installed. Returning to 18.3 for now …

  12. Hi Clem. Being a relative newcomer to Linux I am probably going to ask a silly question. How do you access
    /etc/initramfs-tools/conf.d/ ?

    1. It’s accessible by all, either via the file manager or via the command line (cd /etc/initramfs-tools/conf.d/; ls).

  13. My upgrade crashes out with this repeating error:

    dpkg: error processing package libglib2.0-0:amd64 (–configure):
    dependency problems – leaving triggers unprocessed
    dpkg: dependency problems prevent processing triggers for libglib2.0-0:amd64:
    libglib2.0-0:amd64 depends on libffi6 (>= 3.0.4); however:
    Package libffi6:amd64 is not configured yet.

    Please help!

    1. Hi,

      This happens to everybody. the upgrader shouldn’t crash though, it should detect this error and overcome it by calling sudo dpkg –configure -a and apt install -f and then retrying another 4 times. Do you see the upgrader fail on this 5 times? Can you paste the output of the upgrade on pastebin?

  14. Everything went like a charm!
    I upgraded my 18.3 following instructions step by step on my lenovo x240. Everything fine!

    Note: I had cinnamon broken as I was playing with MS QSV (Media Server Studio Essentials/DRM/etc.) last week. I decided to upgrade instead of make a fresh install as I have no free time right now, just to try, and it worked! (fixed it, is upgraded, and… and system works better!)
    Note2: Wireless. I have rtl8192ee (that is known to don’t have a good drivers on linux), works better than before althought is not perfect (but much better!, I don’t get disconnects now:).

    Thank you guys for your good and hard work!!!

  15. hello linux mint wanted to make an inquiry about the update in dvd live with fresh version of the system when doing the backup of the programs also saves the steam games and the previous installations in wine or simply discards it by installing only the program itself , thank you I await a response before proceeding to install 😎

    1. Hi Freddy, it depends what you back up and restore.. I would suggest to follow this upgrade path. First, you’re covered with Timeshift so you can always go back. Second, it keeps your installed apps and personal data, so your Steam collection and wine should remain intact. Be aware though that many people reported issues with wine in Ubuntu 18.04 and Mint 19 (which is based on it). You can always try I suppose and see if you can overcome these wine issues. Again, you can always go back to 18.3 post-upgrade by using Timeshift.

  16. Thanks for the reply, Clem. Sorry, perhaps error might be a better word than crash. This is what it displayed:

    Processing was halted because there were too many errors.
    E: Sub-process /usr/bin/dpkg returned an error code (1)

    + Error detected on try #1, running fallback commands…

    And now it’s seemingly carried on and completed the upgrade. Does this mean it will be OK to reboot, or will the
    libglib2.0-0:amd64 error cause a problem? Thanks.

    1. Hi,

      Yes, this happened to us during testing as well. It’s not really clear what makes apt trip over this but it’s harmless. APT just gets interrupted, mintupgrade cleans it up and retries again and then it goes smooth. Sometimes it trips more than once over other packages. The important thing is that all updates apply cleanly in the end. You can check that this is the case, post-upgrade with “apt dist-upgrade” and “apt install -f” but the upgrader does that for you so this should be fine.

    2. Seems I spoke too soon. Turns out it hadn’t actually finished the upgrade and now it really has crashed after looping around several times trying to fix an additional problem. The output is:

      Removing systemd-shim (9-1bzr4ubuntu1) …
      Removing ‘diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim’
      dpkg-divert: error: rename involves overwriting ‘/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service’ with
      different file ‘/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd’, not allowed
      dpkg: error processing package systemd-shim (–remove):
      subprocess installed post-removal script returned error exit status 2
      Errors were encountered while processing:
      E: Sub-process /usr/bin/dpkg returned an error code (1)

      + An issue was detected during the upgrade, running dist-upgrade in manual mode….
      Reading package lists… Done
      Building dependency tree
      Reading state information… Done
      You might want to run ‘apt-get -f install’ to correct these.
      The following packages have unmet dependencies.
      libxreaderview3 : Depends: libwebkit2gtk-3.0-25 (>= 2.0.2) but it is not installable
      systemd : Depends: libsystemd0 (= 229-4ubuntu21.2) but 237-3ubuntu10 is installed
      E: Unmet dependencies. Try using -f.

      !! ERROR: Failed to dist-upgrade some of the packages. Please review the error message, use APT to fix the situation and try again.
      !! Exiting.

      Any suggestions?

  17. What happened to me is interesting. After I upgraded to Mint 19; I tried to install the Obsidian desktop theme;
    and it gave me weird effects; first by booting into a command-line only interface; and then; upon reboot; delayed my time-to-login…with completely black screen and about a 7 minute delay. I fixed the problem with Timeshift; thereby immediately proving its value.

    1. Hi Jason,

      Timeshift is great. A desktop theme shouldn’t affect your login time though.. can you link us to the Obsidian theme you installed? Was that a package from the repository or a 3rd party?

  18. Installed Mint 19 yesterday and fought with it for over 6 hours. I kept getting broken package messages when trying to install Nvidia Graphics driver. Finally, it switched over to the Nvidia GPU but I still got the broken package message and when I reboot, the computer freezes on the mint logo during startup. I’ve tried reinstalling the 3 times but it’s always the same problem.

    So now I have a paperweight where my laptop used to to be.

    1. Hi Johnny,

      Please paste the error messages you’re getting. Try “sudo dpkg –configure -a”, “apt install -f”, “dkms status” and “inxi -Gxx”. The output of all these commands might help troubleshoot the issue.

  19. Hello, after upgrade from 18.3 to 19 I can’t seem to install gcc (or related dependencies) anymore, for example:

    $ sudo apt install liblsan0
    The following packages have unmet dependencies:
    liblsan0 : Depends: gcc-8-base (= 8-20180414-1ubuntu2) but 8.1.0-5ubuntu1~16.04 is to be installed
    E: Unable to correct problems, you have held broken packages.

    I tried changing apt sources but no success.

    1. Hi Henri,

      “apt policy gcc-8-base” and “inxi -r” might help understand the issue. The fact that you’re seeing 8.1.0-5ubuntu1~16.04 means you’re still pointing to 18.3/xenial or the upgrade didn’t succeed/complete and some of your packages aren’t up to date yet.

      … or worse you’re pointing at some Xenial PPA. Because gcc-8-base 8.1.0-5ubuntu1~16.04 isn’t in Xenial..

    2. Hello Clem, thank you for response. The installed version is probably a leftover package I had installed on 18.3 from ppa, I will try revert and retry (this time removing any ppa packages first). In case it’s helpful, see requested info below:

      $ apt policy gcc-8-base
      Installed: 8.1.0-5ubuntu1~16.04
      Candidate: 8.1.0-5ubuntu1~16.04
      Version table:
      *** 8.1.0-5ubuntu1~16.04 100
      100 /var/lib/dpkg/status
      8-20180414-1ubuntu2 500
      500 bionic/main amd64 Packages

      $ inxi -r
      Repos: Active apt sources in file: /etc/apt/sources.list.d/official-package-repositories.list
      deb tara main upstream import backport
      deb bionic main restricted universe multiverse
      deb bionic-updates main restricted universe multiverse
      deb bionic-backports main restricted universe multiverse
      deb bionic-security main restricted universe multiverse
      deb bionic partner

    3. Update: I was able to solve it by removing the ppa packages using dpkg and installing the corresponding bionic versions from .deb. Thank you again for help.

  20. hello more than a question a suggestion maybe for the future, they could make a program that allows the update of the versions of new systems since in part the process of creating a security backup disc before the update helps but for the people who have the system as main and used almost all the volume of your memory would be almost impossible to create a backup of your files and reaching 400 gigs or recommend installing the system in a small internal memory and the files in a large separate? 🤔

    1. No,You have to do this.

      apt remove ttf-mscorefonts-installer
      apt install libreoffice-sdbc-hsqldb sessioninstaller ttf-mscorefonts-installer
      sudo rm -f /etc/systemd/logind.conf
      apt install –reinstall -o Dpkg::Options::=”–force-confmiss” systemd
      sudo rm -f /etc/polkit-1/localauthority/50-local.d/com.ubuntu.enable-hibernate.pkla

    2. Yes, you just apply updates to the beta in the usual way. However there are a couple of additional steps to be taken. See “Upgrade instructions” in any of the recent “Linux Mint 19 Tara Released” blog posts.

  21. Hi Clem,

    Reboot after upgrade gets stuck at the LightDM login window. Each and every time I enter my valid username and valid password at the login window, the screen goes black. Then a few seconds later the login window reappears, with the username and password fields blank!

    I followed your instructions to use “Recovery mode” to edit the fstab file, but there was no line with “/dev/mapper/cryptswap1” to add a # in front of!

    Is it possible that Linux Mint 19 is not compatible with my Logitech K800 keyboard, and so doesn’t recognize certain keystrokes in my password? I haven’t had any hardware compatibility issues with Mint 18.x

    I used Timeshift to revert back to Mint 18.3, but would still like to try the upgrade to 19 again if you can help me resolve the login issue.


    1. Hi Tom,

      First, you’re not the only one. We’re see three people with similar issues. Second, this doesn’t look like a password problem, but a session one. Can you drop to console and check .xsession-errors after a failed attempt? It might give us a clue as to what’s going on.

    2. Exactly the same problem!…
      And exactly the same solution! Thanks Timeshift!
      Back to 18.3 and waiting for a more matured upgrade…
      Don’t know how to “drop to console and check .xsession-errors “…
      Couldn’t that be automated and reported back to you?
      I need my computer functional all the time for professional reasons and can’t spend hours upgrading and reverting…

    3. Just to add I noticed an error — no symbol table, press any key — before the login screen.
      Don’t know if this is related…

    4. Hi Clem,

      Before my second attempt at upgrading to Mint 19, I did “sudo apt purge gnome-user-share”, as Vitaly suggested. This time, after applying the upgrade and rebooting, I was able to login at the LightDm/slick-greeter window without a problem!

      Thanks, Vitaly!

      However, on a side note — I noticed that both times when I went through the upgrade process, it stopped several times for maybe 30 seconds each time, with this message on the screen:

      Unknown media type in type ‘all/allfiles’
      Unknown media type in type ‘all/allfiles’

      I’ve noticed this happens with Opera updates, too, and some others. How do I fix this issue, so as to avoid all those annoying delays?

      Also, during both upgrade attempts, the warning came up “System Program Problem Detected in Package libglib2.0-0”. What’s that all about? Thankfully, this did not stop the upgrade process.


    5. @Tom K: You don’t happen to have a file /usr/share/mime/packages/kde.xml do you? If so, try renaming it to a non-.xml name. Otherwise have a look through the contents of the files in /usr/share/mime/packages as the problem may be there.

    6. @Pete: Thanks very much for your suggestion. I do have kde.xml, as well as kde5.xml, opera-stable.xml, and a few other .xml files in /usr/share/mime/packages. How do I rename them, and what should I rename them to?

    7. @Tom K: Just rename your KDE xml files for the moment e.g. by adding .backup onto the end of the filename. You’ll need to do this as root. You may or may not have to logout or even reboot for this to take effect, but test it without doing so to start off with.

    8. @Pete: Thanks! I was able to rename, as root, those .xml files in /usr/share/mime/packages to .backup without a problem. I’ll find out if that avoids those “Unknown file type…” warnings/delays during updates when a few more become available to install (especially Opera).

    9. @Pete: Another Opera update became available today. When I installed it there was still a long delay at “Processing triggers for shared-mime-info…”, but no “Unknown media type…” messages showing below it this time. So, I’m still not sure why Opera updates, and some others, get hung up there. This same type of delay also happened several times when I was upgrading to Mint 19.

    10. @Tom K: It’s beyond my ken now I’m afraid. It looks like something legacy could be in there causing the delay. You could always try deleting and recreating the mime cache (search the internet for instructions). Alternatively, reinstalling shared-mime-info or even Opera might do the trick. As a last resort, a fresh install would certainly get rid of such legacy remnants. Perhaps it might be best for you to ask on the Mint Forums.

  22. Extremely novice user .

    Will it show in update manager automatically, after sometimes.? Or I have to do anything?

    1. If you boot, the ‘WELCOME’ screen should automatically appear, after you log in and do the password stuff… look for the Update Manager and then do your business.
      If you are already in Mint, go to Menu, and select. Look for the search box, and enter WELCOME and search, the welcome screen appears immediately…actually I only enter WE to save time, and this tool appears fast… select and do your thing…
      I am a new user having a fresh installation of LINUX Mint 19 Cinnamon…. I am a lesser extremely novice learner than you, having LINUX for only the last week or so

  23. I just upgraded to Mint Cinnamon 19 and on reboot the system won’t let me log in with my valid password: I am simply returned to the login screen. My password is apparently accepted as correct, since no error is produced while incorrect password entries are rejected. Any suggestions?

    1. Yes, after a failed session (your password is accepted but the login screen fails to start the session basically), drop to console with CTRL+ALT+F1, and look at errors with “more ~/.xsession-errors”. Paste any errors here. The cause of the issue is likely to appear there.

    2. Possibly related to the person above who solved their problem by removing gnome-user-share, the error I’m seeing is
      cinnamon-session[2845]: GLib-GIO-ERROR: t+0.01802s: Settings schema ‘org.gnome.desktop.file-sharing’ does not contain a key named ‘enabled’, aborting

  24. Awesome. Upgraded from 18.3 to 19. Very smooth and looks amazing. I’ll be sitting on this one for a while. Thanks Clem and team!

  25. hi trying to upgrade from 18.3 to 19 i get this E: There were unauthenticated packages and -y was used without –allow-unauthenticated.
    The repository ‘ tara Release’ is not signed.

    1. Hi John,

      You might have hit it just when we were adding packages into it and before it was signed again. Please try again.

    2. Thanks Clem, you were right, I tried it again and the install went perfectly. My old 2012 Macbook pro with 1tb 850evo ssd and 2tb 2.5 hdd is now lightning fast. I have one other question and that is to make it easier to map network drives and have every application be able to see it so you don’t have to navigate the gvfs folder. on windows you would type in run \\SERVERNAME\SHARE then you can right click on the share and map network drive and you can even tell it to reconnect at logon. on linux mint you either have to edit the fstab or use something like smb4k or gigolo to map the drives. would it be possible to look at integrating something similar in the next version of nemo. Even adding the feature to connect to server would be ideal. so users can type smb://SERVER/SHARE and when they click connect it asks for a username and password with an additional tick box to reconnect at logon. once again I would love to thank you and the team for your hard work as always.

  26. After the upgraded from 18.3 to 19, just 2 small problems for me.
    #1. not update ICEauthority file /home/ben/.ICEauthority
    #2. An new start takes about 1 to 1.5 min (? because problem #1 ?) in 18.3 with no problems starting up in 20-30 sec.
    For the rest my compliments

  27. Hi Clem,

    Yes, I had to switch from MDM to LightDM before upgrading, as I was told by “mintupgrade check”. After installing LightDM and rebooting, I continued the upgrade. When it was finished and I rebooted the computer, I got a new login screen. My user name was correct, but no matter how many times I entered my password, I always got thrown back to the login screen. When I login from a console, the computer seems to accept my password but then what do I do to enter the gui? Please help if you can.

    The grub menu was indeed completely regenerated. I have four partitions: one with Mint Cinnamon (my main OS), one with Mint KDE, one with Manjaro and one that used to have Mint Xfce, but is now empty. However the new grub menu still shows Mint Xfce and other entries are repeated twice.

    Selecting Manjaro from the grub menu gives me a a few lines with “kernel panic” and then stops. That is not a very big problem, I might just reinstall it later. As I said, Mint Cinnamon was my main OS so it’s unfortunate that this is giving me problems.

    Also, the new loading screen in Mint 19 (the one with the logo, right before the login screen) seems corrupted: it has a white background and the Mint logo has black circles beneath it.

    It’s a real mess I’m afraid, and unless there’s an easy solution, I think I’ll “timeshift” back to 18.3. I was hoping that Mint 19 would correct some old unsolvable problems that I have been having (like not being able to access the internet unless I first switch the network manager off and then back on again – very strange).

    Thanks for any help you may give.

    1. Hi Luke,

      The login screen should be the same before and after the upgrade. i.e. it should be slick-greeter (lightdm). If your password is accepted in console but not in the login screen, we’re looking at an issue in lightdm, possibly slick-greeter.. but this should have happened prior to upgrading, when you switched from MDM to LightDM. Could it be a keyboard layout issue? The login screen should show you the layout it’s using in the top-right corner of the screen.

    2. Just relating to two of your issues:

      . startx should, as far as I am aware, launch the GUI from a logged-in console.

      . A useful way of regenerating the grub menu, I’ve found, is to run sudo apt-get –reinstall install grub-pc

  28. hi sorry to bother again but thanks to loq told me I wanted to install linux mint 19 but the problem is that when I try to make the backup copy before the live installation of 19 with linux mint 18.3 the backup program
    It shows a lot of programs but there is a great majority that action should be done to not lose the data of the software or the installation of Linux 19 allows to install the system eliminating the previous one but keeping the programs, I would appreciate the answer as I bring more or about a year after installing linux mint 18.3 and I had no problem for that reason I do not remember how the alternatives were in the installation thanks 🤖

  29. Hi, I’m sorry to bother you again, but thanks to what he said he wanted to install linux mint 19, but the problem is that when I try to do the backup before the live installation of 19 with linux mint 18.3 with the copy program of security
    the program shows many programs but there is a large majority that needs to be done to avoid losing the software data or the installation of Linux 19 allows to install the system eliminating the previous one but keeping the programs, I would appreciate the answer as it took more or a year after installing Linux mint 18.3 and I did not have any problem for that reason, I do not remember how the alternatives were in the installation thanks 🤖 writing error so I uploaded it again I’m sorry

  30. I can’t even pass the mintupgrade check:

    W: Erro GPG: http : //packages. linuxmint. com tara Release: As seguintes assinaturas eram inválidas: BADSIG A6616109451BBBF2 Linux Mint Repository Signing Key
    E: The repository ‘http : //packages. linuxmint. com tara Release’ is not signed.
    N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
    N: See apt-secure(8) manpage for repository creation and user configuration details.

    !! ERROR: Failed to configure APT sources
    !! Exiting.


  31. Same here with the immediate return to lightdm after loggin in. .xerrors says:

    dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
    dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
    dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
    dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
    dbus-update-activation-environment: setting LC_MEASUREMENT=de_DE.UTF-8
    dbus-update-activation-environment: setting LC_PAPER=de_DE.UTF-8
    dbus-update-activation-environment: setting LC_MONETARY=de_DE.UTF-8
    dbus-update-activation-environment: setting LANG=de_DE.UTF-8
    dbus-update-activation-environment: setting GDM_LANG=de_DE
    dbus-update-activation-environment: setting DISPLAY=:0
    dbus-update-activation-environment: setting MANDATORY_PATH=/usr/share/gconf/cinnamon2d.mandatory.path
    dbus-update-activation-environment: setting LC_NAME=de_DE.UTF-8
    dbus-update-activation-environment: setting XDG_GREETER_DATA_DIR=/var/lib/lightdm-data/chennecke
    dbus-update-activation-environment: setting USER=chennecke
    dbus-update-activation-environment: setting DESKTOP_SESSION=cinnamon2d
    dbus-update-activation-environment: setting DEFAULTS_PATH=/usr/share/gconf/cinnamon2d.default.path
    dbus-update-activation-environment: setting PWD=/home/chennecke
    dbus-update-activation-environment: setting HOME=/home/chennecke
    dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
    dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
    dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/cinnamon2d:/usr/share/gnome:/home/chennecke/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share
    dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=cinnamon2d
    dbus-update-activation-environment: setting LC_ADDRESS=de_DE.UTF-8
    dbus-update-activation-environment: setting LC_NUMERIC=de_DE.UTF-8
    dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
    dbus-update-activation-environment: setting PAPERSIZE=a4
    dbus-update-activation-environment: setting SHELL=/bin/bash
    dbus-update-activation-environment: setting XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
    dbus-update-activation-environment: setting IM_CONFIG_PHASE=1
    dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
    dbus-update-activation-environment: setting SHLVL=1
    dbus-update-activation-environment: setting LANGUAGE=de_DE
    dbus-update-activation-environment: setting LC_TELEPHONE=de_DE.UTF-8
    dbus-update-activation-environment: setting GDMSESSION=cinnamon2d
    dbus-update-activation-environment: setting LOGNAME=chennecke
    dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-fGaxNxHuNb,guid=ce82ed975eb10cc16cd8f76f5b3cfe7f
    dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
    dbus-update-activation-environment: setting XAUTHORITY=/home/chennecke/.Xauthority
    dbus-update-activation-environment: setting XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
    dbus-update-activation-environment: setting XDG_CONFIG_DIRS=/etc/xdg/xdg-cinnamon2d:/etc/xdg
    dbus-update-activation-environment: setting PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
    dbus-update-activation-environment: setting LC_IDENTIFICATION=de_DE.UTF-8
    dbus-update-activation-environment: setting LC_TIME=de_DE.UTF-8
    dbus-update-activation-environment: setting _=/usr/bin/dbus-update-activation-environment
    dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
    cinnamon-session[1315]: GLib-GIO-ERROR: t+0,19708s: Settings schema ‘org.gnome.desktop.file-sharing’ does not contain a key named ‘enabled’

    1. dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1

      Same here 🙁

  32. Clem, I don’t think it’s a keyboard issue, because the top right of the login screen clearly shows “be” (Belgian azerty). I managed however to solve the login problem by following Vitaly’s suggestion to type “sudo apt purge gnome-user-share”. That seemed to work and I am now back in Cinnamon. However, the loading screen is still white and ugly.
    Also, the few unsolvable problems that I had in 18.3 seem to be still there in 19, so I have decided to reinstall the whole system from scratch. I know this will take a while, but Mint is worth it. Thanks for a great system.

  33. Managed to fix the earlier package problems but now I’m getting the dreaded failed session whenever I try to log in using LightDM, just like various other people.

    more ~/.xsession errors shows: cinnamon-session[1130]: GLib-GIO-ERROR: t+0.32835s: Settings schema ‘org.gnome.Vino’ does not contain a key named ‘enabled’

  34. I’ve used fresh install of 19 Cinnamon on my laptop and I love it! Was tempted to try upgrading to 19 on this Cinnamon 18.3 computer but.. I’ve got this one just as I like it and as Clem said “If it ain’t broke, don’t fix it”! Yes 19 is faster than 18.3, quite a bit especially Nemo if you have a massive amount of photos it loads the thumbnails in a fraction of the time! I always prefer to fresh install, so I’ll wait until I break this one (not broken Mint yet but guess it can be done!) or until it is no longer supported.
    Thanks to the team for Cinnamon, best DE out there for me. Also thanks for fixing Flatpak 🙂

  35. I had to carry out the same steps as detailed by Vitaly above, since I too was unable to login using my normal password and also had the dreaded ‘Login Screen Loop’.

    However, all good now and I must admit Mint 19 looks very nice!

  36. Hello there,

    Update done well. Thanks for the job \o/

    Just a fixed annoyance : nvidia-prime can’t switch off the discrete GPU.
    I did these :

    – Installed the latest kernel update available after Mint upgrade (4.15.0-24)

    – Installed nvidia-driver-390

    – Manually added the following lines in /etc/modprobe.d/blacklist-nvidia.conf :
    blacklist nvidia
    blacklist nvidia-drm
    blacklist nvidia-modeset
    alias nvidia off
    alias nvidia-drm off
    alias nvidia-modeset off

    – Reboot. And Voilà
    Bye bye the crazy fan 😉

  37. What is the point of dot number releases?

    If I install Cinnamon Mint 19.0 and then continuously update it over the next few years will this obviate the need to upgrade from 19.0 to 19.1, 19.2, and eventually to 19.3?

    In short, why do dot number releases exist if they do nothing that cannot be done by continually updating?


  38. Why do dot number releases exit? What do they do that cannot be done by simply continually updating a Mint 19.0 release?


    1. You might as well ask “Why do we have MONTHS, when each DAY is an ‘update’?”

      The 4th of July is not the same as the 4th of June (or August, or or or).

    2. Your premise is untrue: dot releases have different LinuxMint package bases on top of the same Ubuntu 1x.04 package base. In other words, updates of 18.1 bring bugfixes to the 18.1 packages and do not include the functionality introduced in 18.2 (and therefore the new bugs that new functionality always, necessarily brings along with it). To see this in action, check out and compare the package version numbers among the 18.*.

      This is different to Debian and Ubuntu dot releases, these are nothing more than a rebuild of the installer/live cd containing the most recent updates, as a convenience for new users not to download most of the distro twice (“pristine” release and updates).

      Ubuntu and Linux Mint dot release installers also default to a different kernel from the very same distro package base, but that’s something the user can also do manually in the “base” release if they want. Firefox and Thunderbird are another exception, they are always updated to the latest version on pretty much any distro, due to the nature of the problem they try to solve.

      So updating Mint 18.1 will never make it a 18.2, while e.g. updating ubuntu 14.04 will eventually turn it into the same thing as 14.04.4, because actually there is no 14.04.4 from apt’s point of view.

    3. Mark: Thanks very much for your most informative reply to my question regarding the respective roles of updates versus dot number releases. Best Regards.

  39. After upgrading to LM19 I can not longer open my separate LUKS encrypted HDD from Nemo. I receive the message “Error unlocking /dev/sdb1: The function ‘bd_crypto_luks_open_blob’ called but not implemented!”
    It is working fine in the terminal with “sudo cryptsetup luksClose /dev/sdb1 cr_crypto” but this is awkward. Any ideas?

    1. Hi Peter,

      Try to install libblockdev-crypto2 and reboot. Let us know if that helps, we might add this to the list of added packages so other people don’t experience this issue.

  40. We found the cause of the issue which prevents some people to log in Cinnamon after the upgrade. A left-over autostart file from gnome-user-share points to a configuration key which no longer exists.

    An update to cinnamon-session is on the way to fix this.

    In the meantime, you can work around the problem by purging gnome-user-share. Follow Vitaly’s steps at

  41. On two machines I upgraded both of them failed to boot after the upgrade because secure boot was turned on. I assume the keys have changed between 18.3 and 19.2. I had to turn secure boot off to get them to boot up.

    As it happened with two machines it might be worth adding a note in to disable secure boot before upgrading.

  42. Flawless upgrade after seeing it perform on VirtualBox with full encryption.

    Setting up Git on /etc is the way to go to detect modifications.

  43. A cosmetic glitch: I ran “mintupgrade check” from the console, prior to running timeshift, and it gave me an error message in red letters about not having run “timeshit” rather than “timeshift”. Let’s see, it appears that this is the actual error message:

    “”Please set up system snapshots. If anything goes wrong with the upgrade, snapshots will allow you to restore your operating system. Install and configure Timeshit, and create a snapshot before proceeding with the upgrade.”

    🙂 Anyway, I ran timeshift and am continuing with the upgrade. 🙂

    1. Uh oh, another cosmetic glitch: the word “superstition” is misspelled in this message:

      “Make sure you made backups, you tested Linux Mint 19 ‘Tara’ in live mode and you performed your favorite supertitious tricks before proceeding.”

      Apparently you guys need someone to edit your python scripts. 🙂 🙂

    2. OK, make that “superstitious” rather than “supertitious”. Geez, now I’m doing it.

      Anyway, the upgrade took a long time to apply, but otherwise went fine.

  44. Successfully made the trip from 18.3 to 19 on a Dell Latitude E6540. Followed the cook-book — the ““mintupgrade” tool did the work. All seems to be working just fine-n-dandy. 🙂

  45. Boot time is far, far longer on Mint 19 than it was on Mint 18.3 for me (Cinnamon edition).

    On 18.3 the system came right up, now after the Linux Mint Logo I’m looking at a black screen and waiting a good 2+ minutes – no idea what it is doing in the background. After 2-3 minutes I get the logon screen. I was using MDM before, now LightDM since it was required with the upgrade. Intel NUC i3 system using a SSD, nothing too complex.

    I saw Clem suggest the following command when somebody else complained about boot time, but I don’t know what the output means (if anything):

    mint@mint ~ $ systemd-analyze critical-chain
    The time after the unit is active or started is printed after the “@” character.
    The time the unit takes to start is printed after the “+” character. @32.356s
    └─ @32.356s
    └─cpufrequtils.service @32.317s +38ms
    └─loadcpufreq.service @32.225s +90ms
    └─ @32.215s
    └─media-download.mount @31.590s +623ms
    └─ @31.583s
    └─ @1.538s
    └─NetworkManager.service @1.105s +431ms
    └─dbus.service @1.068s
    └─ @1.004s
    └─ @1.002s
    └─uuidd.socket @1.002s
    └─ @993ms
    └─ @992ms
    └─dev-sda5.swap @979ms +13ms
    └─dev-sda5.device @978ms

    1. Thank you. Installing haveged fixed the slow boot for me too.
      Another issue was bad wine fonts, solved with sudo apt-get –reinstall install ttf-mscorefonts-installer
      Another issue is that my Caja bookmarks were deleted.

  46. Many thanks for great package Mint 19.
    Successfully upgraded from 18.3 in my HP Elitebook. Went without any problems and WINE seems to be fine also. I did have a problem in 18 with drier for the WIFI Modem but all good in 19.
    Thanks for excellent operating system
    Colin Schulz

  47. I am just in the middle of upgrading my Mint 18 cinnamon setup and an error message alarmed me.
    It said that grub could not be installed on dev/sbd. First it should be installed on /dev/sda1 and second, sbd is an NTFS disk so the grub embedding failed. If the upgraded 18.3 does not boot, not only do I have a backup, but I did a clean install of 19 as well.

    1. The OS was not bootable due to grub’s attempted install to the wrong disk. I would be intersted to see how many attempted upgrades on multi-hard drive systems succeed.
      I deleted both my Mint 18 installs and will use the clean installs of Mints 19 I did earlier this week.

  48. Nice job, upgrade went pretty much flawlessly thus far. A few network tweaks, but nothing major. Thanks!

  49. Upgraded 18.3 to 19 on my Sony Vaio VPCEB33FM, and everything works well. One thing- Gnome-Calendar didn’t install by default, so added it from Software Manager

    Anyway, great work, Mint Team! Thank you!

  50. Been using pdftk to split, reorder, and remerge PDF pages. Not present in LM19 repositories. What do you recommend for a relacement?

  51. So I’m also having the issue logging into cinnamon that others have mentioned. Sadly, all my tty sessions are showing a blank screen (I’m guessing this has something to do with proprietary nvidia drivers?) so I can’t get into the shell to fix my problem that way. I get back to LightDM when I hit ctrl-alt f7 but then I’m back at square one. Before I roll back with timeshift, anyone have any clever advice? And if I do roll back, has the cinnamon fix been pushed such that I should be ok if I try again?

    Oh, one more thing. When I got into 19 initially before rebooting, my PPAs hadn’t been restored and I had to run a mintupgrade check to restore them. I’m assuming this isn’t expected behavior. Something on my end or something that might need fixing? Thanks much.

  52. Hi,
    I upgraded without any trouble. But: certain programs stopped to work: SCUMM is looking for kyra.dat, can be fixed by manual install of the website dl. But the worst part is, that the playonlinux-install of MS-Office 2007 stopped to work and can’t be done anymore. If anybody knows a working solution: please post in the comments.

    1. Troubles with Microsoft Office programs come from Playonlinux and Wine issues. I recommend you delete previous installations of Playonlinux and Wine, reinstall both packages (including the i386 version of Wine and the packages that are installed from Winetricks) and try to install the programs using Playonlinux without the wizard (Install a non-listed program) in a 32-bit installation.
      Reported bugs in Playonlinux:

    1. Hi Candra,

      They’re saved in ~/Upgrade-Backup/APT/. You can read them from there and re-add them one by one. I suggest you use “Software Sources” -> PPA, to do this, as it checks whether a PPA supports Bionic or not before accepting to use it again.

  53. Good job as usual, Clem, but I noticed some issues yesterday, when I upgraded to LM19 from 18.3:

    – Nvidia GeForce G7 Series (nvidia-304) drivers did not work properly as on Linux MInt 18.3;
    – Flatpack has, in my opinion, a few bugs on LM19, as I cannot download the applications from it.

    Thus, hope these issues are solved as soon as possibile, but for the rest, I have no complaints.

    Best regards, Jonathan.

  54. Update from 18.3 to 19 MATE went without a catch, but when rebooted it wouldn’t boot into 4.15.0-24. Booted fine into 4.15.0-23 so I went with that and uninstalled 4.15.0-24. Guess I will have to avoid 4.15.0-24 on my machine for some reason.

  55. Upgrading from 18.3 to 19.0 – seems to work fine, but I wonder if nvidia is actually running (the system is much cooler than in 18.3) and I get x-server pop-up error a few seconds into login screen. It says something like xserver already running and proceed to stop it. What to do?

    Also – I wanted to make a clean/fresh install of 19, but the ‘safetybackup’ does not show any programs in the list for generating list of installed software. It would be too complicated to try and figure out what was installed after the install.

  56. Newbee question — I’d like to save my 18.3 installation and convert is to a virtual machine. Before I invest time in a crazy measure, can any of you tell me if I can do it using timeshift to back up the my current installation and then recover in a virtual machine running a fresh 18.3 install ?

    Yes, I have a practical reason to do this. I have, a digital signature software running flawlessly on my 18.3 machine. Nevertheless, I have not been able to make it run in Mint 19. Some java issue, I guess. So, I’d like to have that VM version (virtualbox) so I can resort to it when I need to sign some documents.

    Thank you for your time and input.

    1. I had problems with the Portuguese citizen card digital signature and solved by running in a terminal (and let the terminal open until all is done) — sudo /usr/lib/jvm/java-8-openjdk-amd64/bin/java -jar /usr/share/plugin-autenticacao-gov/plugin-autenticacao-gov.jar sj

    2. I’ve tried that, Tavares, but did not work. Not for the digital signature software.
      Nevertheless, the token is recognized by Firefox. No problem here. It is also
      recognized by Safenet applications. It seems only Java has some something different.
      Perhaps it requires a different configuration.

  57. Hello,

    I love Linux Mint and very excited with LM 19. I tried to install it yesterday and I just reverted to the 18.3 snapshot today (thank you so much Timeshift – a life saver!). Although I was able to log in once, it failed afterwards and stopped at the early system/command line login (like in the terminal), NOT at the LightDM login. Could not go past that stage, not even run LM 19 with my USB key.

    When I initially went through the installation steps, and tried to install the LightDM packages, it said lightdm was already installed and didn’t prompt me to choose between MDM and LightDM. I was still mdm, so I ran lightdm manually and switched to LightDM. However I did not purge the MDM files as instructed. When the installation was finished, I had a first failed attempt as it seemed to use the old login window but when I tried again it looked as it was fine. So I did my first timeshift, purged the MDM files, installed a new package with the Update Manager and switched to Auto Update. The Reboot/Restart command was not working any more (already before installation but I don’t know exactly at what time). Anyway booting the system was only getting me to the command line login. Any idea of what went wrong?


    PS. I have convinced a few PC users around me to switch to Linux Mint. They are not computer-literate and I view the auto update in LM 19 as a major improvement to their Linux Mint experience!

    1. One update: I saw a comment from another user about 4.15.0-24. I believe this is the package I installed from the Update Manager before it went wrong.

  58. My boot to Login screen time is 2min 54 seconds.
    Ouput of systemd-analyze critical-chain is as follows: @2min 45.394s
    └─ @2min 45.394s
    └─snapd.seeded.service @1min 31.972s +1min 13.420s
    └─snapd.service @1min 32.220s +1min 13.170s
    └─ @1.782s
    └─ @1.782s
    └─snapd.socket @1.778s +4ms
    └─ @1.777s
    └─systemd-timesyncd.service @1.622s +155ms
    └─systemd-tmpfiles-setup.service @1.597s +18ms
    └─ @1.593s
    └─run-snapd-ns-wekan.mnt.mount @32.736s
    └─run-snapd-ns.mount @32.381s
    └─ @1.575s

  59. It took more than 2 hours for my Lenovo G50 laptop to upgrade from 18.3 to 19 (Cinnamon, 64)

    There was this strange error (copy/paste from terminal):

    dpkg: error processing package gconf2 (–configure):
    dependency problems – leaving triggers unprocessed
    dpkg: dependency problems prevent processing triggers for gconf2:
    gconf2 depends on dbus-x11; however:
    Package dbus-x11 is not configured yet.

    dpkg: error processing package gconf2 (–configure):
    dependency problems – leaving triggers unprocessed
    dpkg: too many errors, stopping
    Errors were encountered while processing:
    Processing was halted because there were too many errors.
    E: Sub-process /usr/bin/dpkg returned an error code (1)

    + Error detected on try #1, running fallback commands…
    After these lines there was a prompt for sudo password, I typed it and the process continued. There was other 2 or 3 times when I need to type sudo password. But it seems, system was installed.

    Linux Mint 19 Cinnamon

    I notice, that my IDLE for Python3.5 was deleted, also TeXmaker didn’t work, so, I reinstall i

    1. That is, it’s a bug.

      The same happened to me (~2min), and to workaround it -as you mention- you only have generate entropy, for instance, moving the mouse/touchpad (lowered to ~15sec).

    2. Forgot, and if sb don’t won’t to move mouse (headless systems f.i.): apt-get install haveged

    1. Which unused system files? “Unused” in what way?

      Are you running short of space?

      Running ‘apt clean’ can often free up quite a bit of space.

  60. Upgrade to 19 went well with one issue.
    I’m using a Feitian ePass2003 crypto token to store RSA keys and certificates. I add that token to ssh-agent with ssh-add -s /usr/lib/, but this fails in 19 as opensc-tools is too old (0.17.0) and I couldn’t find a deb package with the new version (0.18.0). So I had to uninstall 0.17.0 and download the source for 0.18.0 and install that.
    After that I could use the token again.
    FYI if you use ePass2003.

  61. Upgraded today from Mint 18.3, without a single problem, everything went smoothly, great job Mint team!!

  62. Hi, i have a python dependency problem, and i haven’t any find to correct that:

    Lecture des listes de paquets… Fait
    Construction de l’arbre des dépendances
    Lecture des informations d’état… Fait
    Vous pouvez lancer « apt-get -f install » pour corriger ces problèmes.
    Les paquets suivants contiennent des dépendances non satisfaites :
    python : Pré-Dépend: python-minimal (= 2.7.12-1~16.04) mais 2.7.15~rc1-1 est installé
    Dépend: libpython-stdlib (= 2.7.12-1~16.04) mais 2.7.15~rc1-1 est installé
    python-dev : Dépend: python (= 2.7.15~rc1-1) mais 2.7.12-1~16.04 est installé
    Dépend: libpython-dev (= 2.7.15~rc1-1) mais 2.7.12-1~16.04 est installé
    E: Dépendances manquantes. Essayez d’utiliser l’option -f.

    !! ERROR: Failed to download packages for the upgrade.
    !! Exiting.

    Are you an idea?

    1. I reply to myself.

      Just change the line in /var/lib/dpkg/status for the python-minimal entry
      Status: install ok half-configured to Status: install ok installed.

      Dirty but it run 🙂

    2. You would probably be best posting your issue on the Mint Forums. However, personally, I would probably download the latest python and libpython-dev (2.7.15~rc1-1) packages directly from the Ubuntu repos ( and assuming that you’re running 64-bit) and manually install these. I would then check that you have no other python packages left that are still 2.7.12-1~16.04). If you are able, make a TimeShift snapshot before doing all this.

    3. @Fufu. Yes, very dirty. 🙂 I wouldn’t recommend that as a solution – you’re still going to have a half-configured package in reality. I have posted a solution but it has been held up for approval as it contains a couple of URLs. Hopefully they’ll release it shortly.

  63. As we know, during the upgrade GRUB is updated. I had previously installed Manjaro Linux, which installed its own GRUB in the MBR. My question is that upgrade to Linux Mint 19 can recognize the new Linux distribution installed in the meantime and register in its newly created GRUB menu?

    1. The Mint 19 installation procedure should recognise all the other distros installed on your machine and the generated GRUB menu should list these accordingly. Are you experiencing a problem?

    2. This is mean it that after upgrading process the Linux Mint installer will intelligently overwrite the GRUB which was created by Manjaro?

  64. Hello everyone.
    Even though my LM19 works almost flawlessly (Xfce perfectly, Cinnamon is a bit more hardware demanding, but nicely looking and way more usable than ever), I don’t understand why you are still losing your time and resources to produce 32 bit OSs. For example, the new Cinnamon DE requiers a pretty decent hardware to run smoothly, do you think someone has got such HW on an old 32 bit PC? Almost noone wants to use the newest operating system on a PC from 2008.

    Also, I think you should focus more on the LMDE. It’s not just an backup,but it’s actually a great combination of reliablesolid Debian, and user friendly Mint. I used it for a long time as a replacement for my LM 18.3, an I absolutely loved the LMDE. I would still be using it, if the LMDE 2 wasn’t so outdated. They have been some privacy concerns about Ubuntu in media recently. But what if Ubuntu users will switch to LM and other distributions in the near future, and the Ubuntu won’t be worth investing into anymore? Shouldn’t you reevaluate the importance of LMDE then? I know it’s not the biggest user base, but that’s mainly because it isn’t well known throughout the comunity. I hope the release of LMDE 3 will make a breakthrough, and more people will get interested in it. I can’t wait to beta-test it.

    Best wishes, P.

    1. 32bit not only goes to old HW
      you may install 32bit on every 64bit system too – that might be usable for some scenario


    2. to P. – I am just trying to get 18.3 to run like my 17.3 (both 32b) & having some problems- package manager says it downloads & installs some packages (eg lm-sensor) but then they are not found – and scrollkeeper seems to have disappeared, I eventually got psensor via an apt — suggested while in terminal (!) Some of my systems (about 2-of4) seem to have 64 bit processors (1 or 2 per system – no more) but I am a bit hesitant to go over to 64 bit Linux until I have time to try it on one sys & see how it handles older 32 bit apps, might be able to get newer hardware next year – hope 17.3 good well into 2019 ! Sometimes an old & well known /used piece of software is worth keeping an old system o be able to continue using – newer software unavailable or $ & unfamiliar (learning curve!) Some folk even think 3″ disks are of no current use – but they are. Don’t fix if not broke is good advice. I want to be able to use my sys to do work, not have to do work on my sys to be able to use… Enough old stuck-in-the-mud babble & thanks for your patience (hopefully some possible thoughtful amusement) I’m an old newbie started with CPM 8 bit (Z80) Kaypro which came with good software bundle – back in mid 1980s’ – and it worked…

    3. Hello Dave. Thanks for your reply!
      I think your transition to 64 bit should be probably fine. From what I’ve heard, problems and bugs are more common with 32 bit Mint, while the 64-bit is usually a bit more polished. On the other hand, I fully understand that upgrading can cause a ton of hassle sometimes. LM 17.3 was, and still is a solid bet for both older, and newer hardware alike. The 18.3 was my main choice for some time, than I switched to LMDE, but I switched back. I would especially recommend you the 64-bit Xfce version of 18.3 (or just stick with 17, it’s basically just as good user-wise and hardware friendlier), especially if your CPU isn’t that powerful for Cinnamon desktop, and you are going for high reliability, and minimum of troubleshooting.

      As older hardware goes, I was lucky enough to start my “computer journey” when 32-bit systems were a thing, and Windows XP was mainstream, so that saved me a lot of learning back than, because working with computers is just getting easier and easier since then. I’ve tried some really old machines (late 80s/early 90s), and man, those were not user-friendly at all, compared to more modern stuff 🙂 But on the other hand, my uncle is still running over 20 years old desktop PC as his backup computer, it has really poor hardware, and it was upgraded just once, when Win XP was released. And strangely enough I have to admit, that it is just as stable and reliable as I remember it to be 10 years ago. That is something you unfortunately can’t expect from most of modern software…

  65. I prefer Mint-X icons to Mint-Y icons. We are advised to use Mint-Y but what are the dangers of using Mint-X?

    1. I’m using Mint-X on Mint 19 and I’ve recently developed a bit of a rash on my left cheek. Other than that, I don’t think there should be any danger involved whatsoever. Mint-X is supported by Mint, it’s just not the default theme any more.

  66. Great ! Upgrade works. Linux Mint 19 Tara works smoothly on my Asus UX31A.

    Note : I had to remove a manually installed deb package (qwerty-fr.deb, a keyboard layout).
    Note 2 : mintupgrade upgrade failed the first time (cycle-dependency related on qwerty-fr.deb), I used Timeshift to restore. Worked nicely.

    Thanks a lot to the team for great work. Mint rocks !

  67. Upgraded today from 18.3 without a single problem, everything went smoothly and Mint 19 feels nice. Great job done Mint team!

  68. Installed drivers for wi-fi dongles on wired Internet computer

    All wi-fi dongle work fine until I get the Mint updates, then “POOF”, wi-fi is gone for good!

    If I do a clean install to a wiped SSD first, and get the Mint updates before installing the wi-fi drivers, I CAN SEE THE NETWORK WI-FI PASSWORDS BEFORE I ENTER MY PASSWORD!!!!!!


    I Found this bug or “feature” in network connections under my wi-fi SSID that was to auto connect from a previous install

    Somehow, Mint is getting the password from router after updates on a clean install on a freshly wiped SSD, but before the password is even entered

    Clean install WITHOUT UPDATES does not show this behavior
    The SSID still shows up under network connections/wi-fi/ but no password shows up after a clean install

  69. I followed all the steps.

    However, on the last step, after running for a while, “mintupgrade upgrade” crashed. My screen was completely blank, with just a cursor flashing in the top left corner. After giving it time, I shut down my computer by holding in the power button.

    My computer booted into a plain Xfce session (without any of my preferred settings). The boot screen was showing Ubuntu 19. And only one of my two monitors was displaying (at a lower screen resolution).

    I tried running “mintupgrade upgrade” again, and it told me to run “sudo dpkg configure -a” to correct the problem. Thereafter, I ran “mintupgrade upgrade” again. This time, it finished successfully.

    Although, my Xfce desktop had the Xfce menu (not the Whisker menu). And the xfce4-panel was at the top, with a docker at the bottom.

    Also, when I lock the screen now, the lightdm lock screen only displays on one monitor (with a lower screen resolution).

  70. Hi,

    Upgrade to LM19 was finally successful after I installed libblockdev-crypto2 and did a reboot. However, when comparing with my timeshift backup of LM18.3 I noted that access to my Synology diskstation DS213j has become extremely slow or non-responsive under LM19. It takes almost a minute to open a jpg with 2MB from the diskstation and data transfer is often interrupted so that the picture is not or not not completely shown.
    Therefore, I am currently back to LM18.3. Any idea how to resolve this performance issue?

  71. I was able to get to a fallback-cinnamon session once, after the update, ran updates in synaptic and now int only boots up to the point where the mousepointer spins on a black background. i am stuck.

  72. Linux Mint 19.0 Cinnamon bug report (I’ve installed the ISO):
    ‘System Settings’->’Backgrounds’->’Images’->’Linux Mint’|’Tara’ does not show any images.
    Only ‘Pictures’ shows the images in that folder.
    (BTW, I had to restore my system with Timeshift after last kernel update. I’m not sure if there’s any connection).

  73. Hi
    Im still running 17.3. I dont want to update but want a clean install. My question is the data. If I copy to external HDD will I run into any problems??

    1. Just a comment that, although it might sound paranoid, I would recommend backing up your documents, videos, music etc. to *two* separate external devices, just in case one of them decides to die or become corrupted while you’re upgrading you main system. Ok, it’s unlikely, but you never know.

      For Mint 19, I personally backed up all my data in this way (not the dot files in the home directory, only my personal documents and files), then installed Mint 19 from scratch and copied my files back over when the install was complete. It’s easy for me because I keep a document containing a list of all the software I install over and above what is installed in Mint by default, and a list of configuration changes I make to the software. So, if I do a fresh install, I just have to read through the instructions I have (bearing in mind that a new distro version might not support old software, that PPAs may need to updated etc.).

      I hope this helps in some way.

    2. to Graham
      Don’t know if this applies but I moves a HDD with mint from one sys box to another & the mint (including old logon password) survived & is usable in the ‘new’ box …

  74. As the Timeshift utility is a prerequisite of the upgrade to Mint 19, I installed it and manually tried to take a snapshot of my machine. Timeshift refused as there was less than 10G (actually about 5G) of disk space. The upgrade was successfull, but afterwards Timeshift automatically tried to take a snapshot and now “0 bytes available”. Timeshift can not be started manually – Message “Planned snapshot is running -Another instance of Timeshift is taking a snapshot – Please wait a few minutes and try again”. The original messages are in German, I translated them as well as possible. That was one hour ago. Why does Timeshift automatically take a snapshot despite there is not enough disk space, manually it refused to to so? How to solve the current situation? Stopping the Timeshift process(es)? Deleting the unfinished snapshot file ? Where?

    1. Open Timeshift and click on “Browse”. Delete the unfinished snapshot file.

    2. I said: “Timeshift can not be started manually.” So I tried to open Timeshift – but it does not work.

    3. Sorry, didn’t see that. Right-click on your file manager icon, click on “Open as Root”, paste the following location and press enter:




    4. As I have a few Linux Mint machines to update with disk space less than 10G, I disable recurring (daily) snapshots in Timeshift to not get into trouble after mintupgrade or use the touch command as Clem explained.

      On the first machine, where I got the error, I rebooted and then could run Timeshift and delete the snapshot, that was created automatically after mintupgrade.

  75. Installed Mint 19 (Cinnamon) yesterday.
    When I try to run a perl script I get the following error:

    ListUtil.c: loadable library and perl binaries are mismatched (got handshake key 0xdb00080, needed 0xde00080)

    Anyone have an idea how to get around this?

    perl -v comes back with:
    This is perl 5, version 26, subversion 1 (v5.26.1) built for x86_64-linux-gnu-thread-multi

    1. Pete,

      >Could your issue be related in that you have remnants from a previous Perl installation?

      Well, when I installed Mint 19, I reformatted / (root) to install 19 but kept /home (from Mint 18.3) as it was. I would have thought the reformatting of / (root) would have wiped out things like perl. But checking just now ~/perl5 exists so that predates Mint 19. I wonder if I delete ~/perl5 and re-install from the software manager (if I can) whether that will fix things up. Alternative is re-install Mint 19 by reformatting / (root) and /home during the re-install?

    2. Pete,

      I removed the ~/perl5 directory. The perl -v command still responded after that mysteriously enough. Tried one of my perl scripts, and it and others are running now. Don’t understand why this works, but it does.

    3. You could certainly try that (in case things go awry, either make a TimeShift snapshot before you do so or rename ~/perl5 rather than delete it). Personally, if I’m carrying out a fresh install which involves a major version change, I don’t keep my old home directory (although I do of course backup my non-dot files and directories to an external device and then restore them afterwards). Ok, so it involves more work in configuring my software once the basic install is finished, but I find it to be a more bug-free method.

    4. Pete,

      I’m beginning to think reinstalling 19 by reformatting / (root) and /home might be a very good idea. I’m seeing several bits of 18.3 debris in the All Applications Menu I can’t seem to get rid of. Who knows what else is lurking?

    5. Yup. May be a good idea. There are some who swear by keeping the home directory for fresh installs, but for major version changes, personally I’m not one of them. Remember to back up all of your data to a couple of external locations, the second location just in case the first one fails, before you fresh install. All the best!

  76. I’m experiencing a problem with the lack of display of an icon in the system panel for one application, CopyQ, in Mint 19 MATE using the Mint-X theme. I started out with Mint 19 Beta, and I’m fairly sure that the icon was visible recently. When I right click on the system panel where the icon should be, I can access its context menu, so it’s invisible but there. This only affects Mint-X, the icon being visible in Mint-Y. On searching for copyq icons in /usr/share/icons, I notice that there are some copyq svg’s in /usr/share/icons/Mint-Y/panel, but that /usr/share/icons/Mint-X/panel doesn’t exist at all, which seems unusual to me. Recreating /usr/share/icons/Mint-X/panel and its subdirectories to contain the relevant svg’s followed by a sudo pkill mate-panel has no effect.

    1. Now solved. For some reason Mint-X was using the copyq svg’s in /usr/share/icons/Mint-Y/panel for the copyq notification panel icon, despite using /usr/share/icons/Mint-X/apps for other applications. And, lo and behold, the icon it was using was entirely grey, the same shade of grey that Mint-X uses for the system panel, hence its “invisibility”. The solution was to copy the colourful /usr/share/icons/hicolor/scalable/apps/copyq.svg over /usr/share/icons/Mint-Y/panel/22/copyq-normal.svg (after backing up the original elsewhere just in case), refresh the icons with sudo update-icon-caches /usr/share/icons/*, then restart the system panel with sudo pkill mate-panel. Now working fine.

  77. I was running Mint 19 on my laptop and after za Bluetooth transmission error with my smartphone I got this issue
    At reboot a black screen with this message:” Could not update .ICEauthority file. Close the session.”
    I opened the virtual terminal TTY with Ctrl+Alt+F1, enter my login and my pass but did not know exactly how to close the session.
    I tried to change the file owner, to delete the file, then quit the TTY with Ctrl+Alt+F7 and reboot but without success.
    I tried another attempt: Boot on a USB stick and restore with Timeshift on a SD card but this did not help either.
    Finally I reinstalled Mint 19 from scratch. There is maybe a better way!

    1. Timeshift failed to fix this issue , because I think hidden files in home directory were not included in the settings

  78. When I try to change the login background image and reboot it will be shown for a very short time and after that gets overwritten by the ‘default’ one. Any ideas?

    1. I’m not experiencing this. Are you changing the background image through the Login Window section of the Control Centre? Also, are you using an image in the list that Mint provides in /usr/share/backgrounds or an image elsewhere on your system?

    2. Yes I’m trying to change it through the login window settings. The picture I try to use is located in /usr/share/backgrounds/linuxmint-nadia

    3. Are you using a multi-user setup? I’ve now replicated the problem but on a VM setup with three users, each of whom are using a different desktop environment. If I change the login window background for the two users who were created afterwards, the system instead changes the login window for the first user who was created. So, if I change the login window for those subsequent users and then logout, I experience what you did, with the newly selected background showing for a short moment before being replaced by the original one for that user. The login window background for the two subsequent users always matches their desktop background image. Is your situation similar in any way?

    4. Are you using a multi-user setup? I’ve now replicated the problem but on a VM setup with three users, each of whom are using a different desktop environment. If I change the login window background for the two users who were created afterwards, the system instead changes the login window for the first user who was created. So, if I change the login window for those subsequent users and then logout, I experience what you did, with the newly selected background showing for a short moment before being replaced by the original one for that user. The login window background for the two subsequent users always matches their desktop background image. Is your situation similar in any way?

    5. Ah, well there’s that theory out the window. 🙂 Hopefully someone else will be able to help.

  79. With the latest updates I can now log in again. However, cinnamon will crash immediately with:

    cinnamon: error while loading shared libraries: cannot open shared object file: No such file or directory

  80. For whose with the lightdm login problem ; to me it was a diskspace issue.

    Using CTRL + ALT + F2 console, df -h command showed me 0% space left.

    Removing files solved this.

  81. Cinnamon crash on my main computer. i5 and gtx 1080 :

    .xsession-errors :

    cinnamon: error while loading shared libraries: cannot open shared object file: No such file or directory
    Gtk-Message: 21:39:34.336: GtkDialog mapped without a transient parent. This is discouraged.
    cinnamon-session[3454]: WARNING: t+0,61641s: Failed to start app: Unable to start application: Failed to execute child process “/opt/minergate/minergate” (No such file or directory)
    Unable to open desktop file /usr/share/applications/caja-browser.desktop for panel launcher: No such file or directory
    Unable to open desktop file /usr/share/applications/mate-terminal.desktop for panel launcher: No such file or directory

    ERROR: libGL setup error : cannot open shared object file: No
    such file or directory

  82. Hi,
    I’ve tried updating 2 times.
    On both occasions the computer booted on a purple screen of Ubuntu, with the message:

    Ubuntu 19
    …. [9.308034] usb 4-10: device descriptor read / 64, error -110

    After that, the Mint login screen appeared but neither the keyboard nor the mouse work. So I had to revert with the Timeshift.

  83. Update on slow Boot to Login Screen time – screen stays blank until I touch the touchpad (on HP Folio 9470m), then within a few seconds the login screen appears. It seems to be independent of how long I wait before I touch the touchpad.

  84. Some remarks after the upgrade. The network and sound icon missed from the XFCE panel. The update manager icon is not in the notification area by default. Otherwise nice work, clean user interface, easy to use.

    1. Exactly the same result I got. I have a Dell Inspiron 5323. Ran LiveCD which confirmed everything was working as they did in 18.3 XFCE. Upgrade process completed without error.

  85. What an exercise in futility! Upgraded Dell XPS-13 from 18.3 to 19, following all instructions, and upon reboot, cinnamon desktop crashes/runs in fallback mode. Reinstalled cinnamon, tried numerous other fixes to no avail. On cold start, screen goes black until mouse is moved or touchpad is touched. Not even Windows 10 has this kind of problem! When can we expect fixes? Tried this on another similar laptop and had endless login loop until I was able to remove “vino” package.

  86. When installing the proprietary nvidia driver with the welcome screen, there is no longer any login possible, because it removes the package cinnamon-desktop-environment.

  87. When running cinnamon with the xserver-xorg-video-nouveau driver, cinnamon crashes and only is running in the backup-mode.

  88. Es posible instalar de 0 sobreescribir al 18.3?
    O debo hacerlo con estos pasos?
    Estoy experimentando con linux y hasta ahora es muy interesante

    1. Sí es posible. Yo lo probé antes con VirtualBox porque tengo el particionamiento cifrado y funcionó.

  89. I followed the instructions in the link in this blog post. However, things didn’t end well. Booting up, instead of the nice LM logo boot splash, I get text saying “Ubuntu 19” with a purple background and four orange dots underneath. LightDM login screen comes up just fine, but when I login, Cinnamon crashes and I’m left in fallback mode. In the mintupgrade check, there were quite a few packages that were to be removed that seemed odd (such as xed and xreader, as well as a bunch of libs), but nothing that seemed system-critical, and even after trying to reinstall as many of these as I could, I’m left with no splash and no cinnamon. I’m running on a fairly old computer (Toshiba Satellite C75D with an AMD A8 APU), but the Live disc seemed to run perfectly when I tried it. So I don’t think it’s an incompatibility issue. If I remember correctly, something similar to this happened the last time I tried this process moving from LM 17.3 to LM 18. I had to do a fresh reinstall then. I was hoping I wouldn’t have to now, either. Unless this can be figured out soon, I guess it’s back to my Timeshift backup of 18.3…

    1. Same here. Can’t get past the login screen. I’m using LightDM. Good thing I backed up first using timeshift. Now I’m restoring to 18.3. Hopefully the backup is just fine.

  90. I upgraded to LM19. Now I can not log in to Cinnamon. I can log into KDE Plasma. When I try Cinnamon my user name is listed in the new greeter. I enter my password then enter. It goes black and the new greeter is back.
    There are no error messages I can see. I am writing this on the KDE login. full graphical.
    I missed the steps to purge mdm and reconfigure lightdm. Did this after install on command line. I was not asked to choose lightdm.
    Then I got the new greeter.
    Googled the heck out it.

  91. Can confirm that Kernel can cause startup hang before login screen.
    After linuxmint logo disappear before login screen appear.
    Pressing CTRL+ALT+F1 to drop to console will make login screen appear again.
    Dropping to this problem disappears.
    Nothing suspicious showed up in .Xsession-errors or systemd-analyze

  92. I have the nearly same problem as Mike . I can login but Cinnamon crashes and goes into fallback mode and the system reports are empty. Any thoughts on my next step?

  93. Hi. I have a similar issue to Mike F. I can login but Cinnamon immediately crashes and goes into fallback mode. There is nothing in the system reports to give any clue why this is happening. I’m a linux novice by the way. Any thoughts on what my next step should be?

    1. Check “inxi -Gxx” to see if you have video acceleration. Check ~/.xsession-errors for clues about the issue.

    1. @Ely: Hi Ely! 🙂 Please explain in detail what kind of assistance you need. Perhaps someone here can help.

  94. I tried two times to upgrade from LM 18.3 to LM 19 om ny Lenovo Ideapad 320, which is dual bootted with Windows 10 (which I haven’t used, by the way). I followed the step-by-step instructions. The result in both cases was a message that Cinnamon had crashed and I was in the fallback mode. Fortunately, timeshift functioned excellently.
    I noticed that when I booted the system both times I raw a boot screen for “Ubuntu 19” before it tried to launch Cinnamon. Also, in the grub menu the only OS option was “Ubuntu 19: The system is back to LM 18.3 and is working. Any advice? There was no problem upgrading my tower system which is exclusively Mint or updating the beta on my HP Pavillion g6.

    1. On my fourth attempt (and after using timeshift to regress to the system as of 1 July) the upgrade was successful. I ignored the mesa update option which was the problem (see Clem’s post below). The whole upgrade option required 2.5 hours to complete, thought. Still, everythings appears to be working. Thank you.

  95. Trying to upgrade according to this guide f*d up my HP EliteBook 2560p compeletely to a point when there wasn’t a proper working system so I coundn’t even run Timeshift to revert to 18.3. There was no Menu or panel visible, just icons of the home dir and HDD. Had to do a clean 19 install. They tell us not to fix something that isn’t broken, but I just coudn’t resist. Luckily there weren’t anything of importance on the laptop, but now it just needs a lot of tweaking, installing and setting up…

    1. You can restore a Timeshift snapshot without a functional OS.

      – Boot the live USB/DVD
      – Launch Timeshift
      – It will scan your drives and find your snapshots
      – Restore straight from the live session

  96. The upgrade broke my nvidia video driver (cinnamon crash) and my sound daemon (no sound)… mint 19 works great on live usb still ! Hopefully Timeshift saved my Life… back to 18.3 until 2021. I will probably need a clean install to run mint19.

    1. No. According to a previous blog post, you have to first update to 18 then 18.3 through the Update Manager.

  97. Guys, why are you rushing with your system upgrades? LM 19 is due to so many bugs obviously released a little bit prematurely. Do yourself a favour and wait at least until version 19.1 is out and major bugs are fixed.

  98. I’ve upgraded 3 PC.
    Not any Timeshift 18.3 snapshot is still visible after upgrade and reboot.

    Is there something I’m missing here ?

    1. It could be. So, you have no /timeshift directory after the upgrade? Did the original TimeShift snapshots appear to be saved with no errors or warnings?

  99. I also experienced slower boot time after upgrade from 18.3 (10s) to 19 (over 1m!) on i7-6700 +GTX 1080+32GB 3000Mhz(15cl)+SSD. The kernel was in both cases the same – 4.15.0-24.
    For me, the solution was to remove the “quiet” parameter from “/etc/default/grub” config file.
    Now my boot time on Mint 19 went back to sweet 10s.

  100. Upgrade went off without a hitch. The only issue I have detected so far is when dragging a file with the middle mouse button in Nemo, it just copies and does not ask to move it.

  101. So… It appears my /etc/linuxmint/info is corrupt, which means mintupgrade guesses the wrong edition. How can I restore this file to its correct Cinnamon state? I only found out about the problem after the upgrade went horribly wrong… Thankfully the Timeshift snapshot worked like a charm.

    1. I would suggest that you find someone with a working 18.3 Cinnamon system to tell you the contents of their /etc/linuxmint/info file. Perhaps someone here will step up to the plate, or you can ask on the Mint Forums. Alternatively, you could try booting up a live 18.3 Cinnamon media and copying it from there if it exists.

    2. I found some info online and modified the file by hand. I also modified the mintupgrade script to print its results, so I can see this before it starts. I’m now trying again… *fingers crossed*.

    3. Still no luck. But again Timeshift comes to the rescue. 🙂

      The installation failed to install the libegl-vendor nvidia alternative and after that the system is broken.

      Like at least one other has written, my check step also wants to remove Cinnamon and other nice-to-have things, which looks strange. Anyway, I’ll backup the two home dirs and do a clean install instead.

  102. My update crashed midway of the upgrade (I think maybe network connection failed) and now I have a broken installation that sais it is ubuntu 19 on startup. My timeshift backup also magically dissapeared so I’m doing a clean install today. (I backed up all my data externally). I’m not sure if I’ll stay with Linux Mint but I’m I’ll keep using cinnamon. I’m thinking about installing manjaro with cinnamon since I need some more up to date packages for my college courses (and the aur looks great). Thanks for the past 4 years where I’ve been happy using Mint :).

  103. Same issues here… thank you for timeshift!!! saved my bacon.
    After upgrade from 18.3 Cinnamon – cinnamon crashes. remove/purge nvidia and install cinnamon and that is fixed, but a lot of menu items don’t work if used from the menu (fine from the terminal), installing nvidia-340 removes cinnamon…. uninstalling it removes xed, anything gl related like vlc, stellarium….

    1. I’m using nvidia 384.130-0ubuntu0.16.04.1 driver and on my first boot into LM19 after the upgrade a window popped up saying cinnamon has crashed with a prompt to reload cinnamon. Clicking to reload cinnamon closes the window and immediately opens another cinnamon crash window. Tried rebooting and had the same cinnamon crash. Rebooted and switched to Mate which allowed me to launch timeshift and drop back to 18.3, which recovered a perfectly working 18.3.

      I can’t wait to try LM19, but the upgrade didn’t work on my setup (Dell Precision 7510; Xeon E3-1505M v5; nVidia GM107GLM [Quadro M2000M]).

  104. Hi Clem,
    Me and at least one other user can’t get through the mintupdate check because of the following error:

    The following packages have unmet dependencies:
    libegl1 : Depends: libegl-mesa0 but it is not going to be installed or
    E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

    but we don’t have libegl1 installed. Ref. thread on

    Is this a bug in mintupgrade or in the mesa library?

    1. This was – in fact – the actual error I encountered when mintupgrade failed, in the issue I mention above. I tried installing libegl-vendor, which is a nvidia package at version 390, but 396 was already installed… That’s when I Timeshifted…

    2. I double checked: I do have libegl1-mesa installed (and even reinstalled it to no avail). Note that I don’t have an Nvidea graphics card, but an AMD Radeon RX570 instead, with AMDGPU-Pro driver.

      @Brian Ravnsgaard Riis: did you manage to upgrade now?

    3. @heinhuiz: In the hope that I might be able to help, could you please paste the output from the following command (paste everything below the equals signs):

      dpkg -l “*egl*”

    4. Hi Pete, thanks for trying to help! The output is:

      | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
      |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
      ||/ Name Version Architecture Description
      ii freeglut3:amd6 2.8.1-2 amd64 OpenGL Utility Toolkit
      un libegl1 (none) (none) (no description available)
      ii libegl1-mesa:a 18.0.5-0ubun amd64 free implementation of the EGL AP
      un libegl1-x11 (none) (none) (no description available)
      ii libgegl-0.3-0: 0.3.4-1ubunt amd64 Generic Graphics Library
      un libgegl-dev (none) (none) (no description available)
      un libqt5egldevic (none) (none) (no description available)
      un libwayland-egl (none) (none) (no description available)
      ii libwayland-egl 18.0.5-0ubun amd64 implementation of the Wayland EGL
      un xserver-xorg-v (none) (none) (no description available)

      *Note: I replaced the brackets around (none) because the blog software thinks it is HTML-code 🙂

    5. “(paste everything below the equals signs)”
      Sorry for being a bad reader 🙂

    6. @heinhuiz: Yup, that error message you received doesn’t appear to match the packages you have installed (as far as I can see – there is truncation in the output you posted, and the output in your original post doesn’t make sense to me when it says “but it is not going to be installed or libegl-vendor”). Unless something else you have installed depends on libegl. Have you checked to see if you have any improperly-installed packages?:

      dpkg -l | grep -v “^ii”

    7. @Pete, I did paste the full output of dpkg -l “*egl*”

      See for the output of the dpkg -l | grep -v “^ii” command.

      Note: atp-get check only returns:
      Reading package lists… Done
      Building dependency tree
      Reading state information… Done

    8. @heinhuz: By truncation of the output, I meant the truncation of columns. For example, the “ii libegl1-mesa:a 18.0.5-0ubun amd64 free implementation of the EGL AP” line is missing info from the output columns. If you expand your terminal to its maximum size and re-run the command, you’ll see what I mean. However, no need to repaste the info here.

      Thanks for the pastebin output. The “rc”‘s are nothing to worry about, they just mean that you’re removed a package but not purged it, so there are residual configuration files. You can purge these with (but confirm the list looks about right before continuing):

      apt purge $(dpkg -l | awk ‘/^rc/ {print $2}’)

      The “ri”‘s mean that the package is installed but is marked for removal. I’ve never seen that before to be honest. You might be best purging these after taking a note of what they are.

      Once you have got to the stage where the command in my previous post returns no packages at all, i.e. all packages are properly installed, we could look at other stuff if you want, although perhaps it might be best to take that to the Mint forums or Linux Questions (where I hang out).

    9. @Pete, I used:

      sudo apt purge $(dpkg -l | awk ‘$1==”rc” {print $2″=”$3}’)

      to purge the config data. The command you gave produced a long list of errors.

      The ri’s I purged manually. Now dpkg -l | grep -v “^ii” produces an empty list, but the initial problem still exists.

      Can we continue this discussion in ?
      I’m learning a lot today, thanks for that!

  105. i have done the upgrade to mint 19 it went smoothley, but a few problems still arised:
    – Virtualbox stopped working, tried to re-install but no luck
    – missing sound icon, couldn get that back
    -clementine not working on this version, but that is a clementime problem

    So for now I went back to my old trusty mint 18.3, because the above are for me show stoppers. Iĺl try later perhaps some bugs or issues are fixed

  106. Thank you Clem for your reply. I had work to do so I used timeshift to restore to prior to the upgrade. However, before I did, I manually started Driver Manager (It wouldn’t start from the menu) and it didn’t show Intel firmware as loaded. (I have a coffee lake processor) as it now does in Mint 18.3 with the new Kernal 4.15.0-24. Also I found and xsession-errors.old which had the the warnings below:
    It doesn’t seem to be a kernal problem so I was thinking of disabling Rainlendar and trying the upgrade again? Or is that not a good idea?

    Cjs-Message: JS LOG: About to start Cinnamon
    ** Message: nemo-desktop: session is cinnamon, establishing proxy
    St-Message: cogl npot texture sizes SUPPORTED
    Cjs-Message: JS LOG: Cinnamon started at Fri Jul 06 2018 01:26:50 GMT+0100 (IST)
    Cjs-Message: JS LOG: network applet: Cannot find connection for active (or connection cannot be read)
    openGL version 4.5 detected (GL3 Cogl Driver)
    MetaSyncRing disabled: couldn’t find required GL extensions, or the minimum safe openGL version was not met
    Cjs-Message: JS LOG: Invalid network device type, is 14
    Cjs-Message: JS LOG: network applet: Found connection for active
    mintUpdate: no process found
    Cinnamon warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x5000046 (rainlendar)
    Cinnamon warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x50000f1 (rainlendar)
    Cinnamon warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x500010e (rainlendar)
    Nemo-Share-Message: Called “net usershare info” but it failed: ‘net usershare’ returned error 255: mkdir failed on directory /var/run/samba/msg.lock: Permission denied
    net usershare: cannot open usershare directory /var/lib/samba/usershares. Error No such file or directory
    Please ask your system administrator to enable user sharing.

    cinnamon-session[1426]: WARNING: t+398.35736s: Playing logout sound ‘/usr/share/mint-artwork-cinnamon/sounds/logout.ogg’
    sys:1: Warning: /build/glib2.0-prJhLS/glib2.0-2.48.2/./gobject/gsignal.c:2635: instance ‘0x1b3f720’ has no handler with id ‘322’
    cinnamon-session[1426]: WARNING: t+398.48166s: Finished playing logout sound
    cinnamon-session[1426]: WARNING: t+398.48173s: Resuming logout sequence…
    cinnamon-session[1426]: GLib-GIO-CRITICAL: t+399.42683s: g_dbus_connection_call_sync_internal: assertion ‘G_IS_DBUS_CONNECTION (connection)’ failed
    cinnamon-session[1426]: WARNING: t+399.42694s: Requesting system restart…
    cinnamon-session[1426]: WARNING: t+399.42703s: Attempting to restart using systemd…

    (csd-xrandr:1623): GLib-GObject-WARNING **: g_object_notify: object class ‘UpClient’ has no property named ‘g-name-owner’

    (csd-power:1589): GLib-GObject-WARNING **: g_object_notify: object class ‘UpClient’ has no property named ‘g-name-owner’

  107. hello I wanted to ask you a question today I have received a lot of updates with the mintupdate update and some of them are from ubuntu 18.04 to install them in linuxmint18.3 what I would like to know if this is a step to update the new version through the administrator of updates, updated little by little in a more comfortable way to version 19 or only it is an update to the system of 18.3. before hands thanks for your answer 😶

    1. If you are running Mint 18.3 then you shouldn’t be receiving Ubuntu 18.04 updates as far as I am aware. Could you please paste the output from the command inxi -r here – that will show your software sources.

    1. I can’t remember what I did exactly, but I rebooted into mint 19 but I had the cinnamon crash loop mentioned below and buttons not working in the menu so I decided to use TimeShift to restore the pc. It rebooted and now all I get is a black screen. My docker web services are running so I’m guessing it’s an Nvidia driver issue?? I’m trying TimeShif again from a USB live session instead of it running in mint 19 like before. Can my system be saved? I really don’t want to format 🙁

  108. hello there is a problem with the new updates I get an error at the beginning it exits buntu 18.04 then it leaves the part to initiate normal session of cinamon but one places its key presses enter and says error cinamon can not begin to use the live cd of linuxmin19 for use timeshift because if I lose the whole system with the data solve it quickly before it affects someone else but without minimal knowledge would be a death of your secure system 😨

  109. Like many others are saying, I was forced to Timeshift back to 18.3. After what appeared to be an error free upgrade, the system booted into the desktop but immediately displayed a message saying Cinnamon had crashed and was in “fallback mode”. Also of note, I could not access System Settings on the menu and all the app and applet icons had disappeared off the taskbar.

    I have happily been using Mint since 17.1 and each version upgrade has completed flawlessly, until now. I will try upgrading to 19 again when all the issues have been identified and corrected. Please post a notice when it’s safe to do so. Thank you!

  110. they always recommend timeshift I thank them but they should also recommend having a cdlive in case this type of error occurs

  111. I tried to upgrad vom 18.3 to 19 but i fails. But i think its my own fault because i updated the cinnamon to beta before and now its broken. So i installed a fresh Cinnamon 19 and i have to say thank you for this fast and stable system. 🙂 its more better than the 18.3.

  112. tried to update with the steps given on the blog. countless errors, installation was interrupted. some things were deleted, anyway. couldn’t start timeshift gui, started in terminal, restored a snapshot. now back on 18.3 and i will stay some time here. maybe clean install will work. but i will not try it very soon. bummer!

  113. Thanks a lot Clem & Team!
    I followed the instructions to the letter and it went flawlessly without an itch.
    Took about 60 minutes to complete.

  114. I tried the upgrade, had some problems, but Timeshift perfectly restored. Will do a fresh install sometime

    1. time at “random: crng init done: … before and after “fix”

      syslog:Jul 6 10:00:34 lilnuxmint kernel: [ 151.526411] random: crng init done
      syslog:Jul 6 10:03:15 lilnuxmint kernel: [ 117.538253] random: crng init done
      syslog:Jul 6 10:05:55 lilnuxmint kernel: [ 122.316245] random: crng init done
      syslog:Jul 6 10:16:18 lilnuxmint kernel: [ 145.956289] random: crng init done
      syslog:Jul 6 10:23:12 lilnuxmint kernel: [ 153.842333] random: crng init done
      syslog:Jul 6 10:26:16 lilnuxmint kernel: [ 146.952452] random: crng init done

      syslog:Jul 6 10:36:39 lilnuxmint kernel: [ 9.660282] random: crng init done
      syslog:Jul 6 10:37:26 lilnuxmint kernel: [ 9.824501] random: crng init done
      syslog:Jul 6 10:39:52 lilnuxmint kernel: [ 9.703255] random: crng init done
      syslog:Jul 6 11:57:56 lilnuxmint kernel: [ 9.715895] random: crng init done

  115. Pete,
    Thanks! Followed your advice. Clean install with backup of data. No probs! 19 so much faster than 17.3!

  116. Hello,
    I followed the instructions migrating from Linux Mint 18.3 Sylvia 64-bit (MATE 1.18.0) to 19. Everything seems to look well, but some applications didn’t run after the final reboot. Several programs were removed during the upgrade process. (Yes I did the check before and I knew it before upgrading.)

    VirtualBox & Calibre didn’t start after re-installation in Mint 19 – my virtual machines and my library left untouched and save.
    I didn’t test more applications, because the two listed first are essential for my daily work.

    I could successfull timeshift back to mint 18.3 and hope a fresh mint 19 installation will not show the same problems as the upgraded version?! I like timeshift very much and use it together with backup2l.

    1. Taking Calibre, are you still having problems running that? If so, and you don’t mind losing any configuration you had in Mint 18.3, you could try renaming ~/.config/calibre to something else and then reinstalling Calibre with sudo apt-get –reinstall install calibre.

    2. Hi, I read your comment and I think I have the answer to your problem. Maybe it is broken packages with bleachtbit. Once this has been done, refresh your administrator of updates, possibly have a new version of mintupdate, then follow the normal check procedure, and then download the packages and go back to update. although if programs are erased since some do not work in the new version as for virtualbox I am updating without problems I hope you help my comment😶

    1. No that’s not right. That’s why there’s the check step, to identify this. Can you paste the entire output? It shouldn’t want to remove cinnamon.

    2. @Clem: thanks for your reply. I found that behavior on three different machines of mine. All wanted to remove cinnamon and other packages. Find the full output here:
      If you need more information let me know how I can be of help!

    3. Thanks, this is really good feedback. Something must have changed either in Xenial (maybe mesa) or in Bionic and it’s breaking the upgrade path. Removing metacity, mintsystem, cinnamon… that’s definitely not ok. A dependency on a crucial package must have been broken. We’ll probably pull the upgrade path for now until we can find what’s wrong and provide a solution for it.

    4. Same here.. Think this is the reason for cinnamon-crash after update my nuc5ppyh and x220.

  117. Upgrade from 18.2 over 18.3 to 19 worked fine. The only thing I’m missing is the terminal in the menu (first time I had to use gvim to start a shell). What is the easiest way to fix this?

  118. 18.2-to-18.3-to-19 went smoothly. Because 18.2-to-18.3 was quick, 5 hours for 18.3-to-19 was unexpected.
    My reason for upgrade was to get flatpak to install the Gimp 10, so coulda stopped the upgrade at 18.3. Glad I got 19. Great new stuff! Hoping Gimp 10 makes it into Mint repository soon.

    1. This is an upgrade to new Ubuntu base (16.04 -> 18.04), so it surely takes longer than upgrades between Mint 18.x versions.

  119. Hi there. I’m stuck here with a kernel panic not syncing NO APIC error. Keyboard disabled so that I can’t interfer with GRUB & by the way it seems not tu recignize my différent kernels (I assume m’y issue comes from the one that came out of the box with Tara)
    Thanks in advance for any help

  120. Thank you all for your superb work. I really appreciate all your efforts.Thank you.Thank you.
    I just upgraded from LM 18 Sylavia Cinnamon to LM 19 Tara Cinnamon by frugal install using unetbootin from Windows 10 Home. All went well. I have successful dual boot system. The only bug is bluetooth that is not working. It worked fine in LM 19 Live Cd mode. Please help.Thanks

  121. Try to update my machines. sadly 3 of 4 with problems.
    – lenovo x230 18.3 Cin -> no problem (just had to renew the ppa from kodi and kde-connect) -> stay on Mint19
    – lenovo x220 18.3 Cin -> after reboot, instant cinnamon-crash -> back to 18.3
    – intel nuc5ppyh 18.3 Cin -> after reboot, instant cinnamon-crash – > back to 18.3
    – synology VM 18.3 xfce -> after reboot, big mess on menu and desktop -> found a command to reset xfce -> all ok now -> stay on Min19

    btw: Live-ISO runs on all 4 machines without problem.

    maybe on nuc5ppyh and x220 i will try fresh install or just wait a bit and give updatepath a second chance.

  122. Have problem after update to 19 version, when updating i have problem with install mint-meta-cinnamon and after this i cant installed it, my log when i try:
    Reading package lists… Done
    Building dependency tree
    Reading state information… Done
    mint-meta-cinnamon is already the newest version (2018.06.08).
    You might want to run ‘apt –fix-broken install’ to correct these.
    The following packages have unmet dependencies:
    libegl1 : Depends: libegl-mesa0 but it is not going to be installed or
    E: Unmet dependencies. Try ‘apt –fix-broken install’ with no packages (or specify a solution).

  123. It looks nice, now that I did a clean install from USB. The attempt last night to upgrade 18.3 via the July 4th instructions didn’t work: the computer kept crashing out of the display manager. I was stuck in fallback-mode. Tried reverting to an earlier kernel, but that didn’t fix it.

    Timeshift was awesome, though, and I brought back 18.3 without a hitch. Love that!

    I could tell you more about my system if you want, but since the failed upgrade isn’t there any longer, I can’t test more about what went wrong. Oh, wait, except I do have a Timeshift version of that still saved too.

    I did upgrade my wife’s laptop with xfce and that worked fairly well. There are a couple of glitches and there were some warnings or even errors. But it is running well enough and she’s happy with it.


  124. Had issue with Cinnamon. Would immediately fail; offer to go into fallback mode. Turns out it can’t find its, even though I see it’s at /usr/lib/x86_64-linux-gnu, pointing to mesa. Looking in mesa, I see an with one line in it. Meaning, whatever it was that was supposed to append a line to /etc/ didn’t, and instead left the file there. If you fix that & run ldconfig -v, it clears up.

  125. Also, with timeshift: thanks for the ‘touch’ command. Personally I have a NAS, and would rather have backup tools that know how to ssh/rsync.

    1. I recently discovered “grsync” (included in both 18.3 and 19.0), installed it, RTFM, tried it, and I’m happy as a clam. Using grsync, I: back-up my desktop to a locally-attached (USB) drive; copy my home directory to my netbook, which I back-up to a removable 32G SDHC card.

    2. @Jonathan B. Horen
      check out LuckyBackup also. Different GUI that I find more friendly.

  126. Hi everyone,

    Ubuntu recently backported MESA 18.0.5-0ubuntu0~16.04.1 into Xenial (on top of which Mint 18.x is based). The problem with this is that its version is superior to the one in Ubuntu Bionic (on top of which Mint 19 is based).

    This creates issues in the APT dependency resolver during the upgrade, resulting in the removal of webkitgtk libraries, zenity, window managers (such as metacity and marco) and even DE components (cinnamon, mate, gnome).

    Post upgrade it also creates issues because the upgraded OS runs on a 18.04 base, but still has a 16.04 version of MESA. LibGL isn’t linked properly, software or even DE fail to load.

    Basically, the upgrade paths for Linux Mint 18.3 -> 19 and Ubuntu 16.04 -> 18.04 are currently broken by this update.

    We contacted the Ubuntu MESA maintainer and we’re hoping he’ll be able to fix the situation quickly.

    In the meantime, we updated mintupgrade to detect your version of MESA and to forbid the upgrade with MESA 18.0.5.

    To prevent people from upgrading to it, in 18.3 MESA is temporarily a level 5 update.

    We’re really sorry about this. We were getting a lot of successful feedback and all of a sudden it seemed upgrades failed for pretty much everybody. At least now we know why.

    If you’re able to restore a snapshot prior to the MESA upgrade, you’ll be able to upgrade to Mint 19 properly. We’ve postponed everything else for now (I know this won’t please people waiting on LMDE) and we’re fully focused on this upgrade path.

    Stay tuned.

    Note: If you already performed the upgrade to Mint 19, a good way to know if your upgrade was affected by this is to run xreader. If it’s missing, or it’s unable to launch because of a missing library, we recommend you use Timeshift to go back to 18.3. People who upgraded before the MESA update in xenial/mint18 are not affected by this. Everybody else is likely to be.

    1. Thanks Clem for the advice.
      We will stop upgrading, and we would appreciate your advice.

      Thank you & all the Mint team for a very good job and excellent OS! (I successfully upgraded one of my computers, and it rocks!!!)

    2. I ran xreader by typing that command in a terminal, and it worked. I upgraded between midnight on July 6 and the wee hours of July 7, from 18.3 to 19 on my HP Proliant Microserver using the instructions and mintupgrade available on July 6, and haven’t encountered any problems with any of my apps- VirtualBox, LibreOffice, etc.. I haven’t tested everything on my Mint 19 system yet. Another reason to ditch X Windows, XCB, Mesa, Qt and GTK3+ built on X, and go to pure Wayland.

    3. Yes, I do remember seeing a mesa update before I attempted the upgrade. Probably why it failed. Hopefully the Ubuntu folks will have this ironed out very soon, as it affects them as well. Keep us posted! Thanks!

    4. No response from Ubuntu yet, but it’s the week-end.
      18.0.5 showed up in bionic-proposed, so that looks good and we’re hopeful.

    5. I spent 5 hours following upgrade path without sleep & it failed. I did fresh install of Linux Mint 19 Cinnamon DE & downloaded all additional package, redo all settings etc with took less than 2 hours. I now ask people to wait till upgrade issue is fixed or go for fresh install. I think the upgrade is tedious process. When I had Ubuntu, upgrade from 14.04 LTS to 16.04 LTS was smooth & happened through update manager only. I feel LM should make it easy through update manager. Thanks for informing why upgrade failed & hope it’ll be fixed soon.

    6. I used aptitude to force downgrade to libegl1-mesa=11.2.0-1ubuntu2. That was the only other version visible to me in the repo. It took care of all the dependencies too. The upgrade suceeded after that.

    7. Scratch my last. The update said it completed successfully, but the xreader test failed. Looks like the GL bits did not make it in. *sigh*

  127. After updating from mint 18 cinnamon to mint 19 cinnamon my laptop has this bug, when i close the lid the monitor turns off (as it should) but when i open it back up the monitor won’t turn on so i would have to shutdown the laptop to make it turn on. Any help on this would be really appreciated

    1. Check in power/battery management if shut down or suspend when lid closed is ON. It may fix issue.

    2. i already check that but it works when i set it to suspend, the laptop suspends when closing the lid (turns off the screen) and when i open it wakes up (turns on the screen). The problem is when i set the option to do nothing when losing the lid, once i open lid back up the screen wont turn on

  128. Hello, same issue here with cinnamon, crashes and goes to fall back mode after upgrade from 18.3. Pretty standard desktop PC, Asus motherboard, Intel I3, 8Gb RAM. Weird Ubuntu 19 label while loading instead of the familiar Mint Logo. Hope it get fixed before I return to 18.3 via Timeshift (thanks God) for the second time – first one due to running out of space in my root partition during the upgrade. Dudes, this upgrade uses lots of disk space …

  129. Another oddity in 18.3 – I can’t seem to get it to find/install cowsay – seems to find & download but entering ‘cowsay’ in terminal results in hung terminal with cursor sitting on next line down & no prompt, ‘x’ to close terminal complains that something is running…

  130. After rebooting from 18.3 to 19 upgrade, my cinnamon crashed and it went to fallback mode. Anyone found any solution for that?

    1. I had this happen in a Mint upgrade because of the proprietary Radeon video driver. I had to manually uninstall and reinstall the video driver to fix it. Just a possibility.

  131. Hello All. I was running Mint 17.3 but wanted to try 19 so I downloaded the iso file and burned it to a DVD… I booted from the disc and all looked good so I went ahead and installed it. Works Great! There was a fan speed issue but I found a post about using i8k monitor for a dell inspiron laptop which is what I have. I experimented with the settings and now the Mint 19 fan runs as quiet as it does in win 10. I have a dual-boot setup and have started to use mint 19 as my primary OS. Good Job Developers!

  132. Another one in the login loop here. It started with an error on my side though, I did not purge MDM. Also slick-greeter did not get pulled automazically with installing lightdm. Fixed that, now I get a DM at least,though the loop. .xsession-errors tells me multiple times:
    #1 (mate-power-manager:1802): GLib-GObject-WARNING **: g_object_notify: object class ‘UpClient’ has no property named ‘g-name-owner’
    #2 Same message with ‘UpDevice’ instead of ‘UpClient’
    #3 (polkit-mate-authentication-agent-1:1792): polkit-mate-1-WARNING **: Error enumerating temporary authorizations: GDBus.Error:org.freedesktop.Policykit1.Error.Failed: Cannot determine the session the caller is in

    Any ideas? TY.

    1. So scatter brained -.- Ofc I tried the other suggested solutions. No vino nor gnome-user-share here, either.

    2. OK, found out by myself. Was totally unrelated to these error messages:
      ~/.Xauthority was owned by root suddenly. chown’ed back to myself and all works great again.

  133. So after updating to 19 from 18.3. I had a situation where 4.15.0-24 would not boot. So I booted in 4.15.0-23 and uninstalled 4.15.0-24 and 19 ran fine. Or so I thought. Turns out when I would wake my computer from sleep I would have no network and had to restart to get it back. I used timeshift and am back on 18.3 now. Anyone else have this problem?

  134. I got issue with login after switching to lightdm. But login using ‘Guest Session’ works. How can I check/reset user specific DM settings?

    Hi all,
    I went through the upgrade succesfully, but I cannot login to the system via GUI. It look like once the autentication has been performed some account configurations of old mdm crashes the session.
    I can only access to the system with CTRL+DEL+F1 terminal
    So I created a new user (user2) which instead successfully login via GUI (and infact I am writing this message)
    Maybe some file in my .config has to be deleted or removed. Any suggestion ?
    thanks in advance

  136. !! ERROR: MESA 18.0.5 currently breaks the upgrade between Ubuntu 16.04 and 18.04 and Linux Mint 18.3 and Linux Mint 19. Restore a snapshot taken before MESA was upgraded to 18.0.5, or wait for Ubuntu to fix this problem.
    !! Exiting.

    1. Should I wait now until there is a new update for Mesa? I have no snapshot point before.

    2. Probably….

      Or you could try to downgrade to the last working mesa (17.2.8-0ubuntu0~16.04.1).

      Sth like: apt-cache showpkg *mesa* , then
      apt-get install libegl-mesa0=17.2.8-0ubuntu0~16.04.1,

      Just a thought…

  137. when trying to install new python packages using pip(3), I get an error:

    ‘ ModuleNotFoundError: no module named ‘pip.internal”

    Tried reinstalling pip. Didn’t work.

    Any ideas?

    1. ah, solved it myself by using the following command:

      ‘pip3 install –user –upgrade pip’

  138. As per Clems advice at July 7, 2018 at 2:54 am, I have rolled back to 18.3 and await the new upgrade path.

    Clem – thanks for finding the route cause so quickly.

  139. Will be the upgrade from 18.03 to 19 available in update manager any time soon? Or it will be manual only?

  140. First attempt failed as I didn’t catch the “15 Go” requirement. I have 15 Go between / and /Home but in fact, the directory “/” has to have 15 Go. I did a Timeshift backup and it was useful to recover my “incomplete” installation. I enlarged to 20 Go and no problem with the update.
    On a fresh install keeping an existing user, I got a problem with .ICEauthority. I have to reinstall with a new user name (and then I copied the file from the old user home to the new one, not a big deal).

  141. I upgrade for performance increases, however little it may be! Much appreciated on hardware as old as mine!

  142. First, thanks to the Mint team for all you do.
    As I posted in the forum, I ran the upgrade on 3 systems. The 1st was downloaded on the 4th and run on the 5th without applying further updates and was successful. Unfortunately, I did the additional updates on the other 2 before upgrading, so they both went to fall back mode. I’m glad you’ve found the cause per the 2:54 am post.
    This is about Timeshift though. one of the pc’s I upgraded was a media pc and thus did not have enough free disk space to run Timeshift without using an external drive. Since this is just used as a media pc, it doesn’t have many additional software packages installed so it wasn’t worth the hassle. I backed up the docs and settings and will do a clean install. However, after upgrading it would not let me run Update Manager without setting up Timeshift (I used “sudo touch /etc/timeshift.json” from your earlier post). My concern is that less experienced users (who shouldn’t be upgrading, obviously) would not do updates after failing to set up Timeshift.
    Also, it would be useful to be able to exclude directories in Timeshift. That would allow me to use it in this media pc by using an external drive to do complete backups while using Timeshift for more frequent system backups.
    I know you all have higher priorities right now but wanted to comment. Again, thanks.

    1. Hi rjd,
      I can’t remember in 18.3 as I didn’t use it (own method, till now), but in mint 19 Timeshift does (let you include/exlude directories/files). Find next a timeshift.json snippet example from my mint:

      “exclude” : [
      “+ /included_dir/.**”,
      “+ /included_dir/**”,
      “exclude-apps” : [

      Hope that helps.

    2. Yes, you’re right Tabarnia, if you go into Settings>Filters you can select files/folders to include/exclude; 19 comes with the folders I would need to exclude already selected and 18 does exclude home folders (and /var/docker/*** – perhaps /var/lib/*** could be added to the config, as in 19, for the version in the 18 repo).
      At the time I posted this, I was trying to find answers as to why I had 2 upgrades fail after 1 was successful, so I didn’t have time to learn the ins & outs of a program I hadn’t used before.
      I believe my concerns are still valid however, as they could be an issue for many users. Having worked in IT support for businesses and schools, I try to first use new software as I think a less experienced user would. If you open Timeshift and just click on create, it just asks where to save. When I ran Update Manager after a clean install of 19, it nagged me to setup Timeshift and wouldn’t run until I let it open the wizard to set it up. You can click cancel and then do updates, but eventually you’ll give in (or just not open Update Manager). When I gave in and let it run the wizard, it just picked the first Linux formatted partition on the drive (which happened to be an Arch Linux root partition). When you open Timeshift and run the wizard from there, it does ask for the location as well as the schedule, but it would be good for newer users if it asked if they wanted to exclude/include here as well.
      I have installed Linux for several friends and family (as well as dozens of students and faculty) who had no experience with it. I also tried to enable users at work to do regular backups of their files (most didn’t, even though they only had to click 1 button) , so I see the value here, but know it needs to be easy to use.

  143. Linux Mint 19.0 Cinnamon bug report:
    After setting ‘System Settings’->’Language Settings’->’Input method’->’Fcitx’, for Korean language, then logout and login, Fcitx icon is presented in the system tray, but it’s invisible (which makes it hard to use the Fcitx Input Method). I’ve tried to change the color of the icon but it’s still invisible.

  144. I also have trouble logging in after the upgrade. I get a box with the message “Could not acquire name on session bus.

    Here is my .xsession-errors:
    dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
    dbus-update-activation-environment: setting DISPLAY=:0
    dbus-update-activation-environment: setting XAUTHORITY=/home/dwalton/.Xauthority
    dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
    dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
    dbus-update-activation-environment: setting LANG=en_US.UTF-8
    dbus-update-activation-environment: setting GDM_LANG=en_US
    dbus-update-activation-environment: setting DISPLAY=:0
    dbus-update-activation-environment: setting MANDATORY_PATH=/usr/share/gconf/cinnamon2d.mandatory.path
    dbus-update-activation-environment: setting S_COLORS=auto
    dbus-update-activation-environment: setting XDG_GREETER_DATA_DIR=/var/lib/lightdm-data/dwalton
    dbus-update-activation-environment: setting USER=dwalton
    dbus-update-activation-environment: setting DESKTOP_SESSION=cinnamon2d
    dbus-update-activation-environment: setting DEFAULTS_PATH=/usr/share/gconf/cinnamon2d.default.path
    dbus-update-activation-environment: setting PWD=/home/dwalton
    dbus-update-activation-environment: setting HOME=/home/dwalton
    dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
    dbus-update-activation-environment: setting LIBVIRT_DEFAULT_URI=qemu:///system
    dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
    dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/gnome:/usr/share/cinnamon2d:/home/dwalton/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop
    dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=cinnamon2d
    dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
    dbus-update-activation-environment: setting SHELL=/bin/bash
    dbus-update-activation-environment: setting XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
    dbus-update-activation-environment: setting IM_CONFIG_PHASE=1
    dbus-update-activation-environment: setting CHROME_REMOTE_DESKTOP_DEFAULT_DESKTOP_SIZES=1366×768
    dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
    dbus-update-activation-environment: setting SHLVL=1
    dbus-update-activation-environment: setting LANGUAGE=en_US
    dbus-update-activation-environment: setting GDMSESSION=cinnamon2d
    dbus-update-activation-environment: setting LOGNAME=dwalton
    dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
    dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
    dbus-update-activation-environment: setting XAUTHORITY=/home/dwalton/.Xauthority
    dbus-update-activation-environment: setting XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
    dbus-update-activation-environment: setting XDG_CONFIG_DIRS=/etc/xdg/xdg-cinnamon2d:/etc/xdg
    dbus-update-activation-environment: setting PATH=/home/dwalton/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
    dbus-update-activation-environment: setting _=/usr/bin/dbus-update-activation-environment
    cinnamon-session[5485]: WARNING: t+0.00470s: Failed to acquire org.gnome.SessionManager
    Gtk-Message: 14:18:09.663: GtkDialog mapped without a transient parent. This is discouraged.

  145. Hi Clem, thanks for the new Tara. As a theme developer I didn’t quite understand the constraints about metacity-3. My theme did not work anymore. Copying an arbitrary metacity-theme-3.xml into the metacity-1 folder solved the issue. It was verified but the original V1 theme was used. Talked to other theme developers – they didn’t know either, why it was working.
    My Question: Why are you constraining metacity to V3 ? Hardly any themes are out there. V3 seems to prevent any 3D graphics. Please do not go the way of Win 10 and Android. Flat design is not a solution (only because its faster?)

  146. Thanks. Just upgraded, and everything seemed to work smoothly. However, I did find after the upgrade that Virtualbox would no longer start. To make a long story short, it turns out the issue was that Virtualbox could not find I solved the problem by making a soft link to /usr/lib/x86_64-linux-gnu/mesa/ in /usr/lib/x86_64-linux-gnu/ using the command

    sudo ln -s /usr/lib/x86_64-linux-gnu/mesa/ /usr/lib/x86_64-linux-gnu/

    Has been working perfectly since this fix.

    1. Hi Timothy,

      That indicates you’re running the 16.04 version of MESA. You can go in Software Sources -> Maintenance and downgrade foreign packages… but really, you should go back to 18.3 and wait for the MESA issue to solve themselves before attempting the upgrade again.

    1. installing synaptic driver doesnt work. this tablet was working just fine on 18.3 cinnamon.
      ID 5543:3006 UC-Logic Technology Corp

  147. Dear mint support. I have noted unusual high cpu usage history with cinnamon desktop. RAM usage is ok. My machine is HP envy TS 15 Core i7 (8 Physical Cores) 8 GB RAM. All processors are recording over 20% usage. With Mate desktop the processors maximum usage is 1% (one or two processors are used)

    1. I checked my Mint 19 install with “MPSTAT” and it shows around %10 total usage with 90+% idle time, on average. Once I solved the fan speed issue it runs very well and I am happy with it. If anyone would like me to try out something that they are having a problem with then let me know…

  148. I got two hard disks , one SSD with win7 and another HDD with Ubuntu . Today when I delete my Ubuntu and install Mint , I had to make more 200MB for EFI .

  149. the update from linux mint 18.3 cinnamon sylvia to Tara was very good for me , except viber wich disappears from the disk.thanks you

  150. if you find a broken package after update is finished, just type this in terminal : sudo dpkg –force all –purge ‘name of the package” and it will repair the damage.thank you

    1. This isn’t necessarily true due to the dependencies which that package might have – it could leave a broken package system. If you’re not an experienced user then I would suggest that it would be best to post a request for help on the Mint Forums. If you’re an experienced user, you’ll know how to get your hands dirty with a broken package system anyway (it can get quite complex).

  151. On my laptop (XPS 15), I have to use the proprietary NVIDIA drivers; the open source ones freeze the system when starting X. The upgrade somehow messes with the driver, which crashed the system mid-upgrade and left LM in some inconsistent state. Therefore, do this upgrade from a virtual terminal without any X running! In case anyone else botched his system this way, this is how i fixed it:
    – Boot in recovery mode, open a root shell
    – Turn off automatic starting of X/LightDM on boot (boot into virtual terminal login):
    systemctl set-default
    – Reboot, do NOT select recovery mode in GRUB
    – Login in on virtual terminal
    – Fix corrupted package installation. This is not possible during recovery mode (see – i think booting without recovery mode in non-graphical environment is better than the solution presented there… especially since I did not have “screen” installed, and without X and network-manager installing it was too annoying to bother)
    sudo apt-get -f install
    sudo dpkg –configure -a
    – Resume the upgrade
    mintupgrade upgrade
    – Uninstall all nvidia stuff
    sudo apt-get remove *nvidia*
    – Reinstall the proprietary nvidia driver
    sudo apt-get install nvidia-drivers-390
    – Re-enable graphical boot with X:
    sudo systemctl set-default
    – Reboot

    Hope this helps someone!

  152. The upgrade went almost without problem.The only system problem was that I had to use kernel 4.13.0-43 because the new one somehow didn’t use the drivers for my wifi/bluetooth card (its a rtl8723de).

    The other issues are just esthetic, metabox theme was removed, i liked more the previous icons of the nemo sidebar and the sidebar now shows all of the bind mount points that were hidden before.

    Otherwise good job Mint team.

    1. Just a quick note that in a fresh install of Mint 19, I’m running the 4.15.0-24 kernel. It might be useful for you to try that out if it’s available in Update Manager (View->Linux kernels) so that you have the latest in a branch installed.

    2. Hi
      I kind of remember the Devs saying that on upgrades the upgrade of the kernel was left to us to do if we want it or not as to avoid disturbances in workflow. You get the new kernel only on clean install.

  153. Clem, you should advise people to delete some kernels before starting. Other than a notification that I was low on boot space everything went well. Thanks for a great OS.

  154. I upgraded as per the instructions and all went well but it did take a very long time, > 2 hours and I had already downloaded everything and run the check.
    Eventually, I got the prompt back and re-booted without incident.
    Following the steps on the welcome screen, I checked the drivers and opted to try the recommended manufacturer’s video driver instead of the installed xorg driver – big mistake!
    It took a while and then I rebooted as instructed and that was the end of the GUI. All I could do was open a terminal with Ctrl-Alt-F6 and log on.
    I tried to run the mintdriver utility but it refused to run. I couldn’t find any other way to roll back the video driver so I had to run timeshift and restore to the 18.3 restore point taken just before the upgrade.
    I will perform the upgrade again, without the driver change!
    I had previously tried booting with the live ISO and found no problems so I know that my old low-end system will work OK.
    What I found quite amazing was following the text output in Terminal during the upgrade just how complex a process it was and all achieved without any re-starts until right at the end. Processes just stopped, were upgraded and then re-started.
    This surpasses even my Mac’s upgrade process because all of my settings were preserved.
    Many congrats to the creators of the upgrade even though the recommended driver didn’t work for me.

  155. The Upgrade to Mint19 Mate worked fine.
    There are only 2 (rather small) problems:
    1. Cairo-dock is no longer to install du to a libglib problem and via the PPA: this doesn’t work for bionic.
    2. After a fresh Mint 19 Mate install oscam doesn’t work properly, although after an upgrade from Mint18.3 Mate oscam works fine.

  156. Hi,

    mintupgrade check reports a probleme with mesa :
    ERROR: MESA 18.0.5 currently breaks the upgrade between Ubuntu 16.04 and 18.04 and Linux Mint 18.3 and Linux Mint 19. Restore a snapshot taken before MESA was upgraded to 18.0.5, or wait for Ubuntu to fix this problem.

    Is there a way to remove mesa in order to upgrade ?

  157. Problem with the upgrade is that Timeshift is not in working condition. The program tries to backup it’s own data files until the partition is 100% full.

  158. My Pc. is Core i5, INTEL 650 3,2gHZ, RAM 4G, HARD DISK 500G, mint 18.3
    To know which display manager using, type:
    cat /etc/x11/default-display-manager
    result is:
    file no exist or directory
    what I do

    1. Make sure you use a capital X for the X11 folder. I made the same mistake initially 🙂

  159. Hi. Initial install of mint 19 didn’t go according to plan. Reverted back to 18.3 using Timeshift and am once again trying to upgrade. On running mint upgrade check receiving the following message:
    !! ERROR: MESA 18.0.5 currently breaks the upgrade between Ubuntu 16.04 and 18.04 and Linux Mint 18.3 and Linux Mint 19. Restore a snapshot taken before MESA was upgraded to 18.0.5, or wait for Ubuntu to fix this problem.
    !! Exiting.
    What is best action?

    1. Did you read through all the info about why Mesa is causing a problem? Just CTRL-F and search for mesa and you will get your answer.

    2. Read Clem’s comments and my bug report above.
      The upgrade path is currently broken.

  160. I recently aquire a 24″, 4K monitor but I just realise that on the maximum resolution everything looks very small.
    I tried to change the scale from Auto into double DPI but this results into huge butons, windows, text…
    Is thare any way to scale to 150%? In KDE Plasma it is possible, maybe you can get some inspiration from there.
    If there is no chance/workaround to get 150% scale I will have to leave Cinnamon until this feature will be implemented.
    (LM 19 Cinnamon x64, Nvidia GPU)

    1. I also have a 24″ 4K monitor which I use at half resolution (1920×1080) with Mint 18.3 using xfce.
      If you don’t have 1920×1080 in the settings list look up on the internet about articles showing how to add it. If your graphics card is capable of 4K on that monitor it is also capable of running at 1/2 resolution which should give you a very crisp “normal” resolution.
      Best size for 4K output is actually 40 to 43 inches.

    2. Thank you for the feedback, actualy the monitor it is 28″ (it was a typo)
      I know I can decrease the resolution but then whats the point in having a 4K monitor?
      After I changed the monitor Windows 10 was automaticaly select 4K resolution and a scale factor so that everything looks well proportioned.
      In KDE it is possible I manualy set 4K resolution and a 1,5% scale factor so that the content looks good.
      After some research on google I finded out that gnome/gtk++ in X11 can use only interger zoom factor, and a real number can be used only with Wayland.
      Since Cinnamon is based on gnome/gtk++ and not supporting yet wayland I think I have no change to achieve what I want, but I asked here with the hope that somebody can give my a smart workaround.
      If is not possible yet in Cinnamon, I have use KDE since is the only desktop (I know) that is offering this feature under X.
      In my view the display/graphic features/performance are very important and every distro whos trying to increase that userbase should make it a priority 1. But that it’s my view…

  161. MESA 18.0.5 was backported into Bionic today. The upgrade path between Xenial and Bionic is no longer broken.

    Mintupdate no longer blocks the MESA update and mintupgrade no longer blocks the upgrade with MESA 18.0.5.

    I’d like to thank everyone who’s been waiting for this this week-end, and the Ubuntu staff also. We didn’t get a response from them, but they got it fixed.

    1. Is there a way to fix a broken Tara upgraded install ?

      My timeshift 18.3 are not available…


    2. Hi Marc,

      Yes, well.. MESA 18.0.5 is in Bionic now, so you’ll get an update for it and that should fix itself. The other issue then is to reinstall whatever was removed during the upgrade.. zenity, metacity/marco, xed, xreader, cinnamon maybe?

    3. @marc b: It depends on how it is broken. If you have not done so already, I would recommend that you start a thread about the issue on the Mint Forums ( – they should be able to help you out with your specific situation.

    4. I still get “ERROR: MESA 18.0.5 currently breaks the upgrade between Ubuntu 16.04 and 18.04 and Linux Mint 18.3 and Linux Mint 19. Restore a snapshot taken before MESA was upgraded to 18.0.5, or wait for Ubuntu to fix this problem.”
      How can I upgrade from here?

    5. Finally it’s working.

      After a while, I applied updates (containing a mesa package) from my fallbacl cinnamon.

      After a reboot, everything is right. Nice !

      I’ll consider a full install sometime.

      Thanks to Clem and others !

  162. I currently have dual boot Win 10 and LM 18.3 KDE. I want to install LM 19, I do not want KDE anymore. I am looking for the easiest and safest way to install LM 19. Is it too soon? Has anyone done this yet? Do I proceed using the LM 19 install CD I created? What about the HDD partitions created with the 18.3 installation?

    1. Personally I would backup your data (documents, photos, music, videos etc.) to a couple of external devices (the second one just in case the first one fails). Then, booting up off the Mint 19 install media, test it live and, if it works fine on your machine, install Mint 19 using the partition(s) that you used for Mint 18.3 (it will overwrite this/these – ensure that you choose the right one(s)).

    1. It should be but, just in case, make a TimeShift snapshot before you do so. In the case that something goes wrong, you can revert back to the snapshot.

  163. HP6530b laptop,

    Unetbootin USB worked fine with the default settings as a” live disc”

    Fresh install to SSD. Applied all updates. Resized panel.

    BUG – Menu button and all default pinned applications do not respond to “left click”. They do respond to “Right click”. Shutdown using keyboard to open terminal

    BUG – will not restart properly, I do not see the grub menu I see the LM logo then a blank screen. Forced shutdown using power button, on restart get error “Could not update ICEauthority file /home/nigel/.ICEauthority” with a log out button, but no mouse pointer to click it with.

    Tried booting in 64 bit compatibility mode from unetbootin and got thousands of errors along the lines of [141.868173] hpet1: lost 5 rtc interrupts before I crashed out of it

    I am now stuck in this position. Luckily a test machine so can wipe and go back to 18.3

  164. Bug – when doing fresh install of LM19, Mint correctly set my location to London but tried to give me an English (US) keyboard. In 18,3 this correctly defaults to English (UK)

    1. That’s strange because when I installed it, it asked me for my language and keyboard choices before it got to asking me for my location. Did it not do that for you too? Is there a possibility that you could have accidentally skipped the keyboard page by pressing Next (or whatever) twice?

  165. When leaving Linux (reboot or shutdown) I get the warning that “at-spi-bus-launcher” is “. With the additional information “Not responding”. This happens with kernel 4.15.0-24 What do I need to do to resolve the problem?

    1. If you don’t use Assistive Technologies on your machine, then you can try disabling AT-SPI D-Bus Bus in your Startup Applications (see the Control Centre). You’ll need to restart to put it into effect.

    2. I don’t seem to have an entry for “AT-SPI D-Bus Bus” in my list of “Startup Applications”. I’m running Mint 19 Cinnamon 3.8.7 Could it be called something else ?

    3. My apologies. It’s listed in my Mint 19 MATE startup applications and I assumed it would be the same for Cinnamon. In fact there appear to be a quite a number of startup applications missing from the Cinnamon list – I’ve no idea why. The desktop file that is autostarted appears to be /etc/xdg/autostart/at-spi-dbus-bus.desktop – you could try moving this elsewhere (you’ll need to do this as root) and restarting. I would have suggested simply renaming it but some applications are fussy about files in their directories that have filenames that don’t conform to what they expect to find.

  166. Upgrade to 19 worked flawlessly today following resolution of the MESA issue. Thank you Clem and LM Team!!

  167. More irritating than anything else: when the system boots up, it puts up a little LinuxMint logo. Except, post-upgrade it now says (in text mode) “Ubuntu 19”. When you bring the system down, the (LM) logo appears. I guess the Plymouth install went weird, somehow

    1. Try the following:

      apt update

      apt install ubuntu-system-adjustments

      (make sure the above command installed at least v. 2018.07.09)

      sudo apt-get –reinstall install grub-common

  168. I am having a problem with timeshift. First, I created an image of a running Mint 18.3. So far, so good. Afterwards, I did a fresh install of Mint 18.3 in a virtual machine (Virtual Box). In the next step I ran timeshift in the virtual machine in order to recover the backup into the virtual machine.

    As far as I see it, it should work, but it did not. After running for a while rsync (started by timeshift) freezes. Timeshift itsel almost freezes (watching the cpu time used, it takes hour to move up a second.

    Then, after wating for about 24 hours (I’ve done this 3 times already) I tried to kill rsync. It did not work. An instance turned into DEFUNCT and the other instance did not respond to kill — even kill -9.

    Here is the command line (started by timeshift) that never ends:

    rsync -avir –force –delete –delete-after –log-file=/mnt/timeshift/backup/timeshift/snapshots/2018-07-09_13-09-38/rsync-log-restore –exclude-from=/mnt/timeshift/backup/timeshift/snapshots/2018-07-09_13-09-38/exclude-restore.list /mnt/timeshift/backup/timeshift/snapshots/2018-07-09_13-09-38/localhost/ /

    Any hints?

  169. I installed Linux Mint 19 Cinnamon and it crashed 2 days later. Over the last two weeks I have had to install a Linux Mint Distro for Linux Mint 19 about 7 times.

  170. Hello! Thanks a lot for all your work. I am running Linux Mint Cinnamon 18.3 and Linux Mint KDE 18.3 and I would like to upgrade to Linux Mint 19 hoping that newer versions of the packages will be available and I will be able to use the features that those bring, but I wonder if I will be able to upgrade my LM KDE or what will happen to it once it stops being supported.

  171. Clem, I am trying to install 19, but as soon as it asks for my wifi password the password block turns bright red and no matter what I do it refuses to allow me to enter the password.

  172. After install of Linux Mint 19, I have a problem with screen-tearing using default modesetting driver. In Mint 18.3 I was using Intel driver without a problem, the GPU is Intel HD Graphics 5500 (Broadwell GT2), Installing xserver-xorg-video-intel does not switch you to Intel driver anymore. What can be done?

  173. Couldn’t agree more with Clem’s comment, “If it ain’t broke, don’t fix it”. I have LM Cinnamon 18.3 on my HP Core i5 7th Gen laptop and it works beautifully. I have never had any issue whatsoever – it’s fast, seamless and clearly the best fit I’ve experienced. I won’t be upgrading until the support expires.

  174. I’ve upgraded mint 18.3 on a 32 bit Intel Atom D270 based netbook which has 1 GB of RAM. The upgrade completed after several hours of intensive hard disk drive activity, but mint 19 couldn’t start the basic Intel GPU.
    Timeshift started from a rescue flashdisk claimed to have restored 18.3 but it actually had not restored the graphics stuff, so 18.3 could only boot in low resolution text mode.
    I wiped out the whole thing and installed mint 19 from scratch. It took almost 3 hours to install and booted up properly, but it is very slow compared to 18.3.
    I saved the hard disk image and put back an 18.3 hdd backup to verify that it still worked as fast as in the past and I ran some trivial tests like start time for firefox, some large pdf documents, libreoffice spreadsheets, etc as well as some file copies that I timed with the time command.
    On this specific hardware mint 19 is far, far slower than 18.3. I compiled a table with actual speed figures if anyone is interested. The bottom line is that 18.3 is usable for basic tasks on this system whereas 19 is not. Who would wait 2 mn 40 seconds to get firefox ready to load a page and another 2 minutes to load for instance.
    I’m quite disappointed and worried that the same will happen when I upgrade my main desktop (which is a recent top notch 64 bit system). Generally speaking should there be any performance degradation with 19 vs 18.3, if so what’s typically the culprit?

  175. I am here as I was looking to install 19 as a solution to a few problems I was having with 18.04. Namely, I can no longer access Software Manager or Software and Updates through the settings menu. When trying to fix this I found my system had ‘become’ 18.03 for some reason. Is there any reason why my system would have updated itself from the installed 18.04 to 18.03, and does this have anything to do with the invisibility of the Software manager? Does the below error have anything to do with it …? Is upgrading to 19 my solution?

    E: Problem executing scripts APT::Update::Post-Invoke-Success ‘if /usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then appstreamcli refresh-cache > /dev/null; fi’
    E: Sub-process returned an error code

    Many thanks!

    1. I’m a bit confused by your comment due to the numbering. 18.3 is a version of Mint. 18.04 is a version of Ubuntu. They are different distros.

      Could you please paste the output from inxi -S

  176. Timeshift question – what happens when the designated device gets full? I think I had read somewhere this could bork a system. Is there an elegant mechanism to manage the device when its getting full and if so what does it look like? Thanks for insights. Looking to re-install from scratch and backups, assigning a separate 300MB partition for /timeshift.

    1. (If I haven’t misunderstood the question) you can delete the previous snapshots and create free space using the file manager – i.e. beginning from the oldest or choosing which ever you like – or if you don’t want to delete anything, you can move (cut, paste) some (i.e. all other than the last one) to an other place / partition, -so that it doesn’t have to be ext4 formatted just to be kept, can be ntfs and fat as well- If the device gets full in the middle of creating a snapshot, nothing bad will happen, it will just state this and stop creating that snapshot.. (like happened to me twice 🙂 )

    2. .. and I guess you meant GB when writing 300 MB .. (P.S. just when creating or re-installing, the snapshots’ place needs to be ext4 for convenience, and you can delete some of the snapshots using Timeshift itself, too)

    3. sorry, I just remembered the word more appropriate than “convenience” : “compatibility” 🙂

    4. Yes, if the partition your system is running on fills up, it would be “borked” until you freed some space. If this were to happen, you could unbork it by booting to a live session and deleting some files to free enough space to let it boot again. I don’t think you would do this with Timeshift however, even if you did use your system partition for storage (not best practice 😉 as it checks for available space.

    5. Yes, so the best is to assign another partition for backup; somewhere other than your running system, that’s why I had no problems though it became full..

  177. Hi. Just got back on system. Thanks to Gothic and bmillham for pointing out Messa issue was already Known event and ugrade path had been pulled resulting in message I was getting. Now see via Clem path has been restored so will give update another try.

  178. Hi Pete
    It is possible I could have accidentally skipped the keyboard page ; more likely I have just written down the wrong order as may well have mis remembered it. However, it did default to English (US) whereas 18.3 defaults to English (UK). Sorry for any confusion

    1. Thanks Nigel. I didn’t experience what you did, and I haven’t heard of others either. I guess that the Mint team will have a look if other reports of this emerge. In the meantime though, are you still configured to US English or have you changed it manually? Control Centre->Languages and Control Centre->Keyboard->Layouts should see you good. Let me know if you have any problems configuring either of these.

  179. Really disappointed that you discontinued the build-in upgrade tool in the Mint-Update GUI.
    It was one of the few aspects where Linux was more user-friendly then Microsoft. (Not only did it do upgrades in a time windows needed reformats, it actually even fixed a broken userinterface for me once! (around 15.1 I think).
    Not only is the year of the Linux desktop not coming nearer, it is actually going further away!

    I can understand not offering it immediately to make inexperienced users wait till a version is more mature, but it would be nice if an upgrade was offered at 19.1 or something.
    Never upgrading is not really an alternative for a desktop OS that expires every few years and who’s software updates are connected to the OS version – if I were still at Mint 13.1 I’d probably be stuck with Libreoffice 2 or something.

    1. It’s not discontinued. Upgrading from a point release to another is much more trivial and we do that from within the update manager. Here, you’re upgrading an entire package base as well.

    2. Dear Clem,

      Love you, man! But I noticed you still think the word “trivial” means the same thing in English as it does in French. In US English, at least, it usually means “of little significance or value”. I’m sure, instead of trivial, you meant to say, perhaps: “simple”, or “easy”, or “uncomplicated”? 🙂

    3. I used the GUI to update…
      While upgrading my old computer freezed. So i had to do a hard power off. After booting the update manager gui came up, told me about a little dpkg-voodoo and did all the rest. It worked for an hour or so and resulted in tara. Everything seems to be ok

    4. Hi Tom K.
      The word “trivial” expresses the very same ideas both in the french and english languages.
      Tom you seem to prefer limiting its meaning to “something of little value” but in fact its more common meaning in US english is actually “ordinary” or “commonplace” or still “simple”.
      Clem, your use of trivial in the context that you used is perfectly correct and you don’t have to be sorry or adjust your vocabulary.

    5. Oxford Living Dictionaries:
      Home>North American English> trivial
      Definition of trivial in US English:



      1 Of little value or importance.

      Synonyms: unimportant, insignificant, inconsequential, minor, of little account, of no account, of little consequence, of no consequence, of little importance, of no importance, not worth bothering about, not worth mentioning

      1.1 (of a person) concerned only with trifling or unimportant things.

      Synonyms: frivolous, superficial, shallow, unthinking, empty-headed, feather-brained, lightweight, foolish, silly

    6. Hi TrivialPursuit,

      I suggest that you use Merriam-Webster’s dictionaries as reference to look up US English words. You would find more complete description for the adjective “trivial” than in the link you cited.

      Please try this: “” and notice #2

      You might benefit from the following link too, as it elaborates on this word’s history – essentially for the benefit of young learners: “”

      To summarize for your own and Tom K.’s benefit though; although there is no denial that “trivial” may mean “Of little value or importance”, or “concerned only with trifling or unimportant things” depending on the context it is used in, one of its fundamental meanings (if not original) has always been and continue to be “ordinary”, “commonplace” and “simple”. By way of extension it also signifies “easy” or “easier”.

      If you remain unsure about your understanding of this trivial word (used in the sense of simple, not as a word of little value), I definitely urge you to look up in an unabridged paper edition (even Oxford’s) which will hopefully convince you to adopt and use the full scale of its meanings.


    7. English Language & Usage Stack Exchange:

      “In the minds of most people, dictionaries and usage guides are a cipher to some presumed existing canonical, regulated definition of what is correct in the English language. Of course, no such canonical definition exists — grammaticality of English is governed only by the bulk of actual usage.”

      “Most publishers of English dictionaries long ago abandoned any idea that they might set forth what is and is not correct in English…”

  180. I am trying the upgrade but am having issues with Timeshift.

    I have 3 hdd’s, 1 my main OS drive, another for music and movies, and a third blank 1tb drive formatted to EXT4
    I open Timeshift, and see all three drives. The main OS drive it says not enough room, my spare 1 drive with movies and music says not enough space <339.1GB. The blank 1TB EXT4 drive it says no linux partition.
    I tried to update without timeshift, as I have nothing to lose on the OS drive, but it won't let me do that without first making snapshots through Timeshift.

    Very frustrated by this. Can anyone help?

    Also 339.1 GB is an awful big snapshot, as most seem to be under 25 gb.

    1. Hi Gary,

      The upgrader only checks for the presence of the file /etc/timeshift.json. If you don’t care about possibly losing the OS, just create the file to trick it.

    2. Seems like this should be a switch for the mintupgrade command. If the machine is running in a VM, why would I use Timeshift over a VM snapshot? I shouldn’t have to “trick” a system upgrade.

  181. I have a problem in Mint 18.3 that may not be a Mint problem but a kernel problem. The last kernel I can use is 4.12.14-041214-genericx86_64. Trying to use kernel 4.13 and later causes a crash at boot time. I get a kernel panic message: not syncing IO_ACIP Timer doesn’t work. Booting from the LiveCD for 19.0 gives the same error, I think because it uses kernel 4.15, and it hangs with the same kernel panic. If i try booting the LiveCD in compatibility mode it boots up OK.

    I’m afraid if I install fro the LiveCD that it will fail to boot with the same error leaving me with no system. Tried to boot from the Ubuntu LiveCD for version 18.04 it also fails with the same kernel panic.

    Guess I’m just stuck with current version of Mint, which works just fine by the way. But something changed in kernel 4.13 and beyond on how it handles ACIP thay leaves me stuck here.

    Any suggestion on how to install with ‘noacip’ from the LiveCD?

    1. Sorry for the brain fart. Can’t spell either I guess. Just realized my error. The problem actually occurs with the “APIC” function.

  182. I waited a few days to let the traffic clear a bit and yesterday did an upgrade from 18.3 Cinnamon to 19.0.
    On a cellular hotspot. Took the modem a little while, but I got to marvel as all the downloads, then updates scrolled down the terminal screen. Wow!!! Haven’t tried everything, but what I have tried just works!
    Many many thanks.

  183. Updated a few days ago with no problems. My one disappointment is the disabling of hibernation, is this temporary or permanent?

  184. Tried the upgrade again last night. It worked beautifully! Things seem faster than before as well, which I’m very happy about. I do have the problem that DNS goes down occasionally after wake from suspend. When this happens, nothing can resolve any domain names unless I turn off networking then turn it back on. I think I had the same problem with 18, as well, but I forgot how to fix it. I think it had something to do with adding a command to the wake-up script that automatically turns networking off and on. But I don’t remember the exact command. I guess I’ll have to do some Googling.

  185. Very good OS.
    PPTP DOESNT WORK IN linux mint 19 Kernel 4.15.0-23-generic

    1. Hi Merowinger,

      We got a lot of negative feedback on VPN in Mint 19. We’re yet to know the cause of the issue though and its solution/workaround. It’s certainly upstream in Ubuntu 18.04 as well. We’ve nothing tangible to go by just yet, but we’re definitely aware there’s a problem.

    1. To get Tara running 🙂

      But, yeah, why would one want to do that indeed. I’ll wait for the fix.

  186. i’m stuck somewhere in cycle i dont know, when i use
    $ sudo mintupgrade check
    it ask me to remove libperl5.22 libwebkitgtk-3.0-common perl-modules-5.22
    >> when i remove them using it says following
    The following packages will be REMOVED:
    libperl5.22 libwebkitgtk-3.0-0 libwebkitgtk-3.0-common libyelp0
    mint-info-xfce mint-user-guide-xfce mintsystem mintupgrade perl
    perl-modules-5.22 yelp
    0 upgraded, 0 newly installed, 11 to remove and 0 not upgraded.
    After this operation, 80.6 MB disk space will be freed.
    >>after removing them i ran $ mintupgrade check
    bash: /usr/bin/mintupgrade: No such file or directory

    1. i solved last errort by combination of following commands
      >>> sudo apt-get update
      >>>sudo apt-get install -f
      >>> sudo rm -rf /var/lib/apt/lists/*
      >>> sudo apt-get update
      >>> sudo rm /var/lib/apt/lists/lock
      and restarting whole process after installing perl as $ apt install mintupgrade wont work without perl dependency.
      what should i do?
      but repeatedly stuck at

  187. Congrats on limiting Linux Mint to Cinnamon, MATE and XFCE. Now we can eliminate MATE and XFCE and put all of our focus on the best Linux version there is.

    Cinnamon is just so fantastic, and with Ubuntu MATE out there now, I would love to see you guys put 100% of your energy and time into Cinnamon.

    1. Well if Mint abandons the MATE edition in the future I will just have to move on.

  188. first thank mint team for the good OS .and I have a tiny problem that i am not sure it is a bug or not.After I fresh install mint19 cinamon I cannot connect to ENDIAN VPN with OPENVPN . I am so sure I setup connection same at I set in mint18.3 . in mint19 after I start connect it say openvpn service stop unexpected
    Any suggestion

  189. Hi, after upgrade from Linux Mint cinnamon 18.3 to 19.00 libreoffice dosent’t show small icons in drop down menus and dosen’t attach documents while trying to send them by email. Any solution for that?

  190. I have upgraded from 18.3 to 19 and running the system for a few days, all look good except one thing, the PAC (SSH session manager) won’t start and leaves a message in syslog: “Jul 11 18:43:11 localhost kernel: [31512.447052] pac[7388]: segfault at 38 ip 00007fcb0e5afac8 sp 00007fffccef9bf0 error 4 in[7fcb0e5a3000+27000]”

    I tried to follow instruction on and run `find /opt/pac/ -name “*” -exec rm {} +`, now PAC is able to start, however it is useless because trying to open any ssh connection put the application in halt

  191. Hi All.
    I’ve found problem after upgrade to (and verified on clear install of) Linux Mint 19 Mate edition with disk mounter for VirtualBox shared folder. Shared folder can be accessed and opened from the desktop, but pressing on disk mounter problem results into nothing. Other external sources like disk drive / usb flash mounted and shown in disk mounter icon without problems.
    (Linux Mint running as VirtualBox guest on Windows host, Virtualbox has the last version 5.1.4, guest extensions installed from Oracle).

  192. Hello, tried to update my Aspire–dual-boot(Win10/LM 18.3)-Laptopp last weekend. I had too switch from mdm to ligthdm and did it how you described it.
    But I stuck in boot (an unlimited job ran, don’t remember exactly). Thx to timeshift I returned.
    Is this part of the mesa-issue? Shall I do a clean install? What about grub? Is it infected? I still need the Windows.
    Anyway thank you for your great job!

  193. I had a nightmare with mintupgrade. Too many things either didn’t work or only “sort of” worked which made it not worthwhile firefighting every issue. Then Timeshift let me down, although I had done a backup immediately before – the system refused to finish booting. So back to basics with a clean install. Very pleased with 19.0 although there are still issues with Google Earth and some wine software no longer working. At least this gave me the opportunity to merge the mint installation with the $home directory in the same partition, which will save me the faff of regularly doing a purge-old-kernels!

    Pay heed to the “if it ain’t broke, don’t fix it” adage!

    1. Your system doesn’t need to boot to use Timeshift.
      If you have a Timeshift snapshot and your system doesn’t boot, boot a live session of Mint 19 from a DVD or USB. Start Timeshift and restore your snapshot from within the live session.

  194. After updating another Dell XPS-13 laptop from 18.3 to 19.1, the fixes to the update path appear to have worked – except for one minor thing. When the system boots up, it goes to a black screen and stays there until either the mouse or touchpad is used or a key is pressed on the keyboard. At that point, the login screen with the password box is presented. Why does the screen not show when the system fully boots?

    1. “Why does the screen not show when the system fully boots?”
      Maybe it’s related to kernel linux-4.15.0-24.26?
      If so, then try to revert back to kernel 4.15.0-23.

  195. Clem & Linux Mint Dev. Team – I am having so much fun with Mint Mate 19 Tara!! I tweaked everything to my specifications and it all is working for me. I love this OS! Thank you all so much for taking the time to read our feedback and then to fix those things you can. I also have been getting work done on my computer which allows me to make another donation to Mint. Bless you all from North Carolina US.

  196. Mint 19 is a fine new version. Beware that it may be premature to install it. I have installed it on two computers with some serious issues. Be sure whether you want EFI or MBR. If your motherboard supports EFI, there may be an automatic installation preference favoring EFI when MBR might be preferable (like a small SSD boot drive). Check your printer drivers after installation. I’ve lost functionality on HP and Canon printers because drivers haven’t been updated to run on Mint 19, so the printers install with Mint 18.3 drivers and dependencies. Some programs always readily available in prior Mint versions are not yet available in Mint 19, eg, pdftk. If you run into issues after updating to Mint 19, assume it’s the O/S, not your settings. A great reason to switch from KDE to XFCE is that the former no longer supports different wallpapers for each workspace, while XFCE has now supported that feature for some years. Besides, KDE has loaded its environment with useless functions that sap CPU cycles.

  197. I have issue with 5.1 sound after upgrading to Linux Mint 19 Cinnamon.
    Devices are detected correctly: but each time I try to change output profile for Maya U5 external usb card, then selected device changes to Speakers Built-in Audio and Analog Stereo Output.
    Syslog contains:
    kernel: [ 2038.800183] usb 1-1.4.1: cannot submit urb 0, error -28: not enough bandwidth.

    Any help with this issue? This sound card worked without any problems on Mint 18.3.

  198. Dear Linux mint team. Thanks for another fine update. I upgraded my Intel NUC from 18.3 to 19 with out any problems. I have been with you since Mint 13! I have 5 computers – and all of them is running Linux Mint! Thanks!

    1. Seems to be a thorough, fair, and balanced review, delivered with some humor. Clem, would you be willing to read it and give a response?

    2. Sadly everything said in that review is true. For me the worst issue is the fonts quality. Then the lack of contrast in text across the board. In this day and age it’s just incomprehensible.

      I am a very disappointed ex-LMDE-2 user of Tara and I am hoping that the upcoming LMDE-3 will be a much better release. Otherwise my Linux Mint saga will come to an end, as in my opinion Clem’s distro has hit the slippery slope like many other distros before his.

      Since I still have some hope, now that Tara is out of the door why the Mint team wouldn’t focus on urgent matters like fixing the graphical text subsystem of Tara.
      For instance the developers could look into matters like why basic kerning doesn’t work in any of the word processors under Mint.
      Or, how to ease the selection of black text on white background or vice-versa without worrying about gray on dark gray kind artistic non-sense that some juniors believe is the ticket to the distro hall of fame.

      Clem, thank you friend for all your efforts and I feel awful that I have to be critical of your baby here, but your distro has been losing steam on the front of essentials since the version 17.3.
      Can you believe that I still keep a 17.3 with an old version of openoffice to produce pro quality word-processing which can’t be done on 18.3 or Tara?

      Thanks and good day to you all.

  199. Hi Pete

    Thanks for your reply., much appreciated.
    I was able to change to the Uk layout with no problems, hopefully it was a one off. However, as stated in an earlier post, i cannot install mint 19 properly anyway as sometime after install the panel locked up (keyboard commands worked) and on reboot I got the error “Could not update ICEauthority file /home/nigel/.ICEauthority” with a log out button, but no mouse pointer to click it with.

    1. At the login screen, press Ctrl+Alt+F1 to get to the console.

      What are the results of ls -la .ICEauthority ?

      My working setup has: -rw——- 1 pete pete 17184 Jul 10 14:03 /home/pete/.ICEauthority

      If the file is owned by root, try taking ownership with sudo chown user:user .ICEauthority, replacing “user” both times with your username.

  200. Linux Mint 19.0 Xfce bug report:
    Using two windows of the file manager (Thunar), I use the mouse to copy directory of 2 GB from the hard disk to a USB stick, OR from a USB stick to the hard disk, then I Eject the USB stick and get the message: “Writing data to device – There is data that needs to be written to the device… Please do not remove the media…”
    But this message never disappears. And much later I may get a “Time out” message (i.e. still copying to device…).
    I’ve tested it with two different USB sticks. It works OK in Cinnamon 19, but NOT OK in Xfce 19.

  201. I am in complete agreement with Dedoimedo. Installed Tara on two drives, no problem, then upgraded, after reading, and disregarding Clem’s prescient warning, my main computer. WOW. disaster. If only I had read that review beforehand, I would not have wasted FOUR days (yes, I am a bit slow) trying to rectify my “mistakes”. Ooops, there were no mistakes. I kept desperately trying to change UFW, in order to get the print shares “safe”. Good luck with that.
    So, I had to regress, another day lost, now I am back to 18.3, and finding it very agreeable. As, per last decade, no trouble at all printing via Samba to winxp. No worry about whether or not ufw is installed correctly or not. NONE of that ridiculous “TIMESHIFT”. Whose big idea was that? Once the system crashes, and TARA did, THREE times, not only was the supposed backup unavailable, the entire computer was inoperable–retreat to BIOS. NEVER had that problem previously, with any other MINT edition. But,who would want to reconstitute the entire FLAWED operating system, after it crashes?
    The entire concept of TIMESHIFT is mistaken. I agree completely with the poster at the outset of this blog, who pointed out, the obvious, that one would naturally wish to reinstall a FRESH version of the OS, from scratch, having backed up important files, not by means of MINT, but onto a removable drive, daily. I further agree, with his indignant demand that an OS ought to be under user control, and I appreciate Clem’s response, indicating how we can disable TIMESHIFT. I am eagerly looking forward to LMDE, and hope it will not include TIMESHIFT, and if the pot of gold is really at the end of the rainbow, there in Eire, one hopes that LMDE will allow a user to print, via Samba, to M$, and crucially, that LMDE Cinnamon will support VIBER, something that Debian Cinnamon does not, but MINT 18.3 Cinnamon does.
    My main system is now running a different version of Linux, but, maybe one day, MINT cinnamon will return to its former position of dominance.
    Cheers, CAI ENG

    1. Wait wait wait here…

      – You can restore timeshift snapshots from the live session, it doesn’t matter if the OS boots or not.
      – You didn’t waste 4 days because you didn’t read a review, you started by disregarding our warnings and skipped on taking the steps necessary to go back.
      – I’ve no idea what the deal is with Samba (we certainly don’t maintain it by the way) and Gufw, but you care about this you can start by filing a bug report upstream, I assume this issue is also present in 18.04?
      – LMDE 3 ships with the latest mintinstall, so that includes Flatpak and Viber.

    2. @CAI ENG
      I can’t be sure, but suspect this samba printing issue may be because recent changes to Samba’s protocol affect browsing of network shares.

      On my LM19 test machine, Nemo wouldn’t browse network shares until I edited /etc/samba/smb.conf and added the line
      client max protocol = NT1
      in the [global] section
      – that forces samba to use the older samba protocol. Fixed it for me.

      That said, I am NOT planning to upgrade my 3 machines from LM18.3 any time soon – 18.3 is supported till 2021 after all. I didn’t see anything in LM19 that warranted an upgrade for me.

  202. Thanks, Clem, appreciate your time, in responding, so quickly. Well done. I wasted 4 days because for the past several years, I have effortlessly upgraded various MINT editions. Truly effortless. The result was invariably superior to the predecessor. Starting with 17, I was so pleased, that I replaced my prior main edition with MINT, until an update appeared on another distro, but, I continued to maintain half a dozen disks and flash drives on different systems, for the past three years. I have no experience with “18.04”, don’t know that edition. I have extensive use with, and love of, 18.3.
    “disregarding our warnings”, does not sound quite right. I read it. I appreciated the fact that you had warned us. I deliberately chose the path less taken…no offence to Robert Frost. I did not ignore your text. I used my past experience, and sought to hasten the switch from 18.3 with its obsolete version of Cinnamon, and the Intel cpu bugs uncorrected, to the new, much improved, much faster executing TARA. Just the name alone, suggests a need to get the horse hooked up to the wagon, and get the show on the road. Tara works for me, just fine, so long as I don’t try to print. So, I use it for a lot of other things.
    The error message that comes with MINT/UBUNTU, (and the same message, with Debian and ARCH/Manjaro) on attempting to setup the printer, conveys to the user, a problem with the “share settings in the firewall”. Hmm. Yup, tried everything except standing on my head. Disabled, reinstated, eliminated Gufw, and used only ufw with the bloody terminal commands, as if living once again back in New Jersey in 1968 at Bell Labs. Every time, with or without even a hint of firewall, or with the firewall in full bloom, but accepting all inputs, NOTHING worked. Nothing that I did, including three complete reinstallations, starting with dd if=/dev/zero, changed that error message. The error message insisted that SAMBA shares were not validated by the firewall, even if the firewall did not exist, according to the MINT “System Settings Menu”.
    No such error message with 18.3. Never even knew that ufw existed, until installing TARA. Never had any problem accessing my XP printer, until TARA.
    Very happy to read that LMDE will include a chance to install VIBER. That ‘s great. Even if I cannot print, I will definitely be using LMDE, and you can look for a check in the mail, upon my successful installation of VIBER.
    Cheerio, CAI ENG

    1. PPAs are 3rd party repositories. Only use a PPA if you trust its maintainer. It doesn’t matter how safe/secure/signed the communication and delivery of software is if you don’t know the person in charge of it. Just like you wouldn’t download a deb from a website you don’t trust, you wouldn’t install one from a PPA you don’t trust. Anyone can make a website to host malicious debs or make a malicious repository, just like anyone can create a PPA and serve debs with malicious code in it.

  203. I ran the LM 19 upgrade . My system is a dual Lenovo P27 monitor setup. One monitor is connected to an AMD Radeon RX 550 card via Displayport. The other monitor is connected to the same card via HDMI. The good news is that sound could now be configured on either monitor whereas it never worked under LM 18.3. The bad news is that the monitor connected via HDMI randomly turned black for two or three seconds. IT was not stable enough to stay on LM 19. I went to Timeshift and reverted back to the LM 18.3 release. I am hoping that as work continues on the AMDGPU driver this can get resolved. I am still happy with Linux Mint.

  204. Thank you Clem and Team for this beautiful release of Mint 19 Cinnamon.

    Maybe not the best (update)start 😉 ..but really no reason to be sad! Now all runs smooth and nice!
    Thank you so much for your love and passion for this project! Hope you will have a lot of this for many years ahead!


    ps: found out, with Mint19 i can finally disable smb1 on my synology! nice!

  205. I did the upgrade from 18.3 to 19 and it went well, upon reboot I could no longer access my windows server shares with either kernel 4.15.23 or.24. I reverted to 4.6.7 and made NO other changes and i had network connectivity. I also did a fresh install onto a formatted blank notebook and the same thing happened using 4.15.23. I installed 4.6.7 and again I had network connectivity. Each time I could not get into the network, I would get the message “failed to retrieve share list from server” Has anyone else experienced this??

    1. @John_F: I can’t be sure, but suspect this may be because recent changes to Samba’s protocol affect browsing of network shares.
      If you want to use the later kernel, try editing /etc/samba/smb.conf and add the line
      client max protocol = NT1
      in the [global] section
      – that will force samba to use the older protocol. Fixed it for me.

  206. After upgrade Startup Applications appears twice in the Menu. I suppose one of them is left over from 18.3. How do I remove the extra one?

    Also, I noticed that, unlike Update Manager, Software Updater doesn’t ask for a password before installing new updates. Is that safe? Is it a bug?

    1. Which desktop environment you are using? The exact method for modifying Mint Menu entries depends on that, but involves right clicking on the Menu button and selecting e.g. “Configure” or “Edit menu”.

      Also, what is the “Software Updater”? Do you mean the “Software Manager”?

    2. Hi Pete,

      Thanks very much for responding! I’m using the Cinnamon desktop. There’s no “Configure” or “Edit” option when I right-click on either of the two Startup Applications. But, there is an “Uninstall” option for each one.

      Now, it’s just a matter of deciding which one to uninstall!

      When I launch the two versions, the windows look a bit different, with different-sized buttons. And, with the FIRST VERSION of Startup Applications showing in Menu>Preferences, when I choose “Add to desktop”, right-click on the icon, and click on “Properties”, next to “Command:” it says “gnome-session-properties”. (Note: During upgrade to Mint 19, mintupgrade check showed “gnome-session-common gnome-startup-applications” as NEW PACKAGES to be installed — but didn’t show “gnome-session-properties” anywhere.)

      With the SECOND VERSION of Startup Applications showing in Menu>Preferences, clicking on its desktop icon, and selecting “Properties”, shows “Command: cinnamon-settings startup”. (Note: During upgrade to Mint 19, mintupgrade check showed “cinnamon-settings-daemon” TO BE UPGRADED — but didn’t show “cinnamon-settings startup” anywhere.)

      As for “Software Updater”… No, I didn’t mean “Software Manager”. “Software Updater” appeared recently (shortly before the upgrade), and appears to have essentially the same function as “Update Manager”. But, if you click on the “Software Updater” icon, a window immediately pops up, and immediately starts “Checking for updates…”. If it finds any, and you click on the “Install” button, it immediately starts installing all available updates — without asking for an Authentication Password!

    3. @Tom K: Thanks for the info. It appears that you have some superfluous remnants from the system from which you upgraded. When I suggested right-clicking and selecting Configure , it was to right-click on the Mint Menu button itself, not on any of the specific entries in the menu. Once you have selected Configure, click on the Menu tab in the window that opens, then on the “Open the menu editor” button. Find the application you want to remove from the menu, right-click on it and select Delete.

      I would suggest removing the gnome-session-properties entry – that application does not exist in a fresh install of Mint 19. There is probably no need to actually uninstall it.

      As for Software Updater, this also does not exist in a fresh install of Mint 19 and looks like it is another remnant of a non-standard previous Mint installation (i.e. it has been added in at some point in the past). My advice would be to not use it and to delete its entry from the Mint menu.

    4. @Pete: Thanks very much! I deleted the gnome-session-properties version of Startup Applications from the Menu, as you suggested. Why do you believe that “There is probably no need to actually uninstall it.”? Could uninstalling superfluous applications cause problems?

      I also deleted Software Updater from the menu. I’m assuming you believe there’s no need to uninstall it either?

      I guess these kinds of issues cropping up is one of the reasons many veteran Linux users generally advise a fresh install. But to me, as a new Linux user, using the upgrade method seemed so much easier.

      I’m disappointed, though, that mintupgrade didn’t automatically remove all the packages I no longer needed!

    5. @Tom K: You can try uninstalling the packages if you want. My view is just that, unless you’re absolutely sure about what you’re doing, and which packages you’re uninstalling, damage could be done by uninstalling the wrong packages. You may have something else installed, for example, which is dependent on the package you want to uninstall (which is maybe why it is there in the first place). We have many packages on our computers that we never use and that do us no harm being there. If however you definitely want those packages gone then you would probably be best to get more targeted help from the Mint forums.

      During the Mint upgrade process, Mint looks at the myriad of packages that are installed on the computer and checks to see if updated versions are in the new repos – if they are then it updates the relevant packages. If it didn’t do that, you would find that a lot of the supplementary programs that you had added to your system would all disappear with the upgrade and that wouldn’t please too many folk. At some point, you installed those programs on your 18.x system (or even earlier if you upgraded from 17.x). The upgrader does its job in updating the packages, that’s all.

      Personally, I upgrade in-situ from one point release to another, e.g. 18.2->18.3, but I do a data backup/fresh install/data restore for major version upgrades, e.g. 18.3->19. This allows me to do a “spring clean” every couple of years, giving me a good look at the software I have installed and how it is configured. In saying that, however, I keep a written record of all software that I have installed and how it is configured and that speeds up the process considerably when I’m reconfiguring my system after a fresh install.

    6. @Pete: Thanks so very much for explaining your view regarding uninstalling packages, how Mint upgrade functions, and your personal practice for installing upgrades. Sounds like good advice!

      You’ve been so very generous with your time, and with sharing your knowledge on this blog! And I, and I’m sure many others, appreciate it very much! 🙂

  207. Just tried 19 – fresh install, new disk. It feels snappy and smooth compared to 18.2 and I am looking forward to using it for real soon but there are a couple of things that for now will stop me.
    1) Tried to use Timeshift but while it seemed to go through the motions, the previous checkpoint wasn’t restored. No major issue since I had done very little since then so time to install fresh again. When I have time I will try to do some proper tests on this to see what is happening.
    2) Samba is still only version 2. Was really hoping for v3 so I could link to modern Windows machines again without dropping them back to SMB v1. Will try to find out what the plans are on this.
    I have another issue which I think is related to the machine not Mint 19. It insists on booting Mint 19 regardless of boot order selected in the BIOS set up.

    Thanks to the team for all the work. It’s generally looking good.

    1. Looking at the repos, the latest version of Samba is 4.7.6. It is listed as 2:4.7.6 but the 2 isn’t part of the upstream version number, it’s the packaged version “epoch” (an internet search will explain).

  208. I am using Brasero, K3b & Xfburn to try and burn some audio CDs, however all give an error of “cdrecord does not have permission to access that device. Many searches have not resulted in a successful outcome. Is this a problem in the transition to Linux Mint 19??

    1. Please see here for a potential solution:

      If this doesn’t work, searching the internet for “”cdrecord has no permission to open the device” (including the quotes) should provide other avenues to explore.

      Let me know how you get on, or if you need help with any of the solutions.

    2. Oops, there should have only been one double quote at the start of that search string. Sorry about that Donn. Please remove the superfluous one.

  209. I set up LINUX Mint 19 a few days ago…. I have never used LINUX before. But I happily report a big success.. I now have a stable desktop that simply works. I have dual booted, as some Windows programs are needed, but I am mainly using the LINUX O/S now. I am very impressed, it’s very easy to use … I am still converting (and learning) the Linux system, so I find that a little difficult… but I can see myself using only LINUX soon.

  210. Upgraded my desktop from 18.3 to 19. It is mostly working well for the most part. A couple upstream apps like Google Earth and Steam are crashing. Don’t know if that is anything that you guys would fix.

    The issue that is a Mint issue is that sometimes when I boot or reboot, the GUI login screen isn’t coming up- just a blank screen. If I hit ctrl+alt+bkspc it will come up though. Interestingly, I had Mint 19 Beta running (a clean install) on this computer on a secondary HD without this problem, including when I upgraded it from the Beta status.

    AMD Phenom 9950 Quad Core, 8 GB Ram, ASUS M3A78 Motherboard, NVIDIA GeForce 9600GT

    1. Thank you for your response, Pete! I had a very busy weekend, so this was the first chance I had to look at your advice.

      Steam- appears to be generally working now, except for one game- Medievel Total War II, which actually did work when I launched Steam in terminal. It crashes when Steam is not launched in terminal, though. Other games seem fine either way. Don’t know what that means! Is this a Mint issue, a Steam issue, or a MTW issue?

      Google Earth Pro- I installed the 7.1.8 amd64 version, and it seems to work. Would be nice if the newest one was working, but that may be a Google issue, don’t know.

      The login screen has come up fine the last several times, so I am hoping that means the issue is fixed!

      Thank you very much!

    2. That’s an unusual one, Doug. My first thought is that the command you are running on the command line to launch Steam may not be exactly the same as the one that is being run by means of the shortcut. There may be, for example, command line options in one but not the other. Depending on where the shortcut is, right-clicking on it and selecting Edit Properties or adding it to the Desktop then right-clicking on it and selecting Properties, or something similar, should show the exact command that is being executed.

  211. Hi Pete

    Thanks for your information, however I reinstalled 18.3 when i could not get 19 to work on reboot after install.

    If I try 19 again I will follow your suggestions

    Many thanks for your help, much appreciated
    Kind regards


  212. Can some one please clamtk says i have unix virus after fact i know i did everything correctly. Or can you please put instruction how to upgrade to clamtk 100.2 please. LinuxMint 19 is so great. We use it always just hard to to open dialogues with people.

    1. Can you please paste the exact clamtk virus alert message here. It may well be a false positive.

  213. took about two weeks using the new update of the system without any problem also install wine and it is functional but the icon does not appear in the menu details minimum as a bit of slowness in some games but in minimum amount and a lot of apt cache but they are things that will be fixed over time in terms of everything else perfect best connection by means of wifi does not have the disconnections that I had in 18.3 is the program kdenlive in almost all the most updated programs excellent system thanks 😶👍

    1. @freddy: re wine
      Below is a link to a PDF document that explains how to add the wine menu items in the Cinnamon edition. I can’t comment of mate or xfce.

      It also has a script that does the download, installation, and creation of menu items in one hit if you want to do that. Have a look at the code to ensure it does what you want, then copy and paste the script lines into a text file and make it executable & run it. The document tells you how to do that. Here is the link to the PDF on my MegaSync account:
      Install wine in Mint 19 Cinnamon

    2. @Tony W: Apart from the inherent dangers for inexperienced users running scripts provided by individuals on the internet, the script that you linked to adds the winehq *xenial* repository, not the *bionic* one, thus explicitly going against the advice of WINE themselves ( Users of Mint 19 should not be adding old xenial repositories to their systems. They should also, imo, not be running random scripts on the internet unless they are VERY SURE about what they do. Just my tuppence worth.

    3. @Pete – re wine.
      That advice on winehq’s page has recently been updated. At the time I wrote the script, the winehq page told mint users to use the xenial package because there wasn’t one available for bionic at the time. My document does warn that “you should read the code overleaf and make sure you are confident that it isn’t going to do damage to your system.”
      I concur that people shouldn’t blindly run scripts without understanding them; the script is heavily commented and not particularly hard to comprehend. For people needing to get wine going at the time, it seemed a useful contribution.

    4. Just revisiting wine in a fresh build of LM19 Cinnamon , I see that “wine-stable” is no longer in the list in Synaptic or Software Manager, and if you install the ‘wine’ meta-package it will now install the older version (1.6) of wine, complete with menu items.

    5. In view of the changes made most recently to LM19 Cinnamon, which now provides installation of wine 1.6, I have removed my previously-linked document with installer script since it is now not relevant.

    1. @Ngonidzashe Mangudya: I’m assuming you’re referring to Joe Collins’ YouTube video “Beginner’s Guide to Installing Linux Mint 19”?

      Joe seems to be very knowledgeable, and, although I didn’t use his video as an aide to upgrading to Mint 19, I have found many of the videos on his YouTube channel very helpful, interesting and informative!

  214. Thank you mint team! Upgrade went well. I only had to restore default cinnamon settings because some programs like nemo, update manager etc had menu bar wrong. It was squished and menu entries were all together with no spaces in between. But again typing in terminal “dconf reset -f /org/cinnamon/” fixed it all. Is there a button to do it in system settings?
    Another thing I wanted to mention. Thank you very much for all the work on x-apps like Xreader etc. Xreader is very good, lightweight, fast! For viewing perfect! I do have a request though. I have have to print documents in pdf regularly. 30-50 pages or even more at a time. Very often I have to scale them. For some reason my experience with printing using Xreader wasn’t good. Scaling doesn’t work as expected, neither aligning on a page (like centering etc). There is no option to print only odd or even pages. Of course I could just type page’s numbers but if there are 50 of them, it’s not fun! 🙂 And if I have to make a booklet I have to use another program, which is not that critical. I can live with that, but those other print options are important, I think. It would be so nice to see them improved in a future releases. Thank you so mush again for your work!

  215. Sorry! I found the option for printing only odd or even sheets! My bad! But scaling and aligning is not working right for some reason.

  216. Still struggling with upgrading my desktop. So far the upgrade script failed (miserably I might add). Timeshift failed to restore to 18.3, instead it left me with a system wreck. Thankfully I had a system drive image copy previously made, so I could go back in time 🙂

    I swapped the SSD with a blank one and installed Linux Mint 19 Xfce. I’ve tried to restore my 18.3 setup using aptik (another Tony George tool) with some success.

    I seem to have 2 issues for which help would be appreciated:

    – On my 18.3 system I used pamusb-tools and libpam-usb successfully. On 19 I was able to install it and create my token as well as my user.
    pamusb-check confirms that my user is recognized and configured for. But, when I try to open a utility that requires login, Mint still asks me for a password rather than using the token.

    – On 18.3 I used Canon inkjet and scanner drivers such as cnijfilter-common-64, cnijfilter-mx920series-64, scangearmp-common-64 and scangearmp-mx920series-64. I took them from ppa:inameiname/stable or ppa:michael-gruz/canon-trunk.
    These PPAs do not support Ubuntu 18 or Mint 19. So I tried manual install of the deb files as well as compilation from source. I couldn’t get them to work.
    I have another (older) Canon printer which uses a different set of device drivers. Same result. deb files which worked on Mint 18.3 do not work on 19. Basic Debian drivers do not work either. Source compilation fails with a million errors (not exaggerating). Any thoughts? Anyone can help?


  217. Thank-you guys! Job well done!

    I’m hoping we can get a Dash-like Launcher built into Cinnamon that will give us a way to search/index objects via screen overlay.

    That is the hope, at least.

    Again, many thanks!!!

  218. I have tried upgrade as instruction suggested but it did not work. I am seeing just blank/black screen. I did hear a sound when starting up. I have waited for at least 2 hours.
    I have created a USB drive for 19 and try to start it up..again blank/black screen with sound one time. did not start up waited a while.
    on both instance I can’t see anything on screen. I have AMD ATI graphics card with no driver installed using whatever comes with mint.
    use timeshift and get back to 18.3 ??

  219. I have a Lenovo W520 laptop, and after the upgrade, the backlight broke. The graphical indicator is popping up, but the hotkey (Fn+Home, Fn+End) is not doing anything. So I have to do `echo 800 > /sys/class/backlight/intel_backlight/brightness` every time my train enters a tunnel. Upgrading the kernel did not help. How `uname -a` returns `Linux w520 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux`. How can one fix this issue?

    1. The reason that vlc gets installed again in an upgrade is that it is part of the standard Mint 19 install, a dependency of mint-meta-codecs. It is, I imagine, much more manageable to provide everyone with the standard install, Mint-wise, and then allow them to play about with it afterwards if they so desire.

    1. Any uninstallation of vlc will only last until the next Mint version upgrade, as I outlined in my other post, so it won’t be permanent. I would also advise that you make a system snapshot with e.g. TimeShift so that you can roll back if you don’t like the results.

      In saying that, the following will do the trick: apt purge vlc

      If you want to see what will happen if you carry out the above command without actually doing it, you can run a simulation with: sudo apt-get -s purge vlc

      To anyone else reading, i would advise you not to uninstall vlc unless you really need to. Even if you want to install another media player, you can leave vlc installed and just not use it.

  220. Dear All in linuxmint,
    I followed Your instructions for upgrading (given the fact I am facing a problem with “service network-manager” with my Mint 18.3 Cinnamon 64 installation (dual-boot with Win10 PRO on DELL Inspiron 3737)) up to the point where I had – according to Your instructions – to turn to lightdm instead of running mdm: all run, to the point I pressed “enter” after running the replacement in Terminal…
    Now I cannot boot in to my system, even if grub seems to run smoothly!
    Please help, someone!

    1. …to be more specific, I pressed enter after writing “sudo reboot” in Terminal, as instructed !
      Then… well, I already told You!

  221. Couldn’t agree more:

    Awful. The default font color/contrast is appalling. It’s a weak gray on white background. The AA settings are reasonable, but the clarity just isn’t good enough. Ubuntu wins here big time. The issue of fonts remains one of the great embarrassments of the Linux space.” —

    I’ve had a hard time with this lack of contrast Tara brought in. Can anybody out there tell me how to chance this? For me it would suffice to have real black on real white.

  222. Today I updated all my computers (4 desktops & 2 laptops) from 18.3 to 19 (Mate), almost without any problem.
    Most of this computers are updated since LM 17.2 and everything is still ok.
    Thanks to the LM team, great work. I’ll donate again!

  223. Something very strange happened:
    Everything worked fine, but now, a few reboots later, inxi -S shows still
    System: Host: HP635 Kernel: 4.15.0-23-generic i686 bits: 32
    Desktop: MATE 1.20.1 Distro: Linux Mint 18.3 Sylvia

    and inxi -r
    Repos: Active apt sources in file: /etc/apt/sources.list.d/official-package-repositories.list
    deb tara main upstream import backport
    deb bionic main restricted universe multiverse
    deb bionic-updates main restricted universe multiverse
    deb bionic-backports main restricted universe multiverse
    deb bionic-security main restricted universe multiverse
    deb bionic partner

    mintupgrade shows only
    Paketlisten werden gelesen… Fertig
    Abhängigkeitsbaum wird aufgebaut.
    Statusinformationen werden eingelesen…. Fertig
    Paketaktualisierung (Upgrade) wird berechnet… Fertig
    Die folgenden Pakete sind zurückgehalten worden:
    0 aktualisiert, 0 neu installiert, 0 zu entfernen und 1 nicht aktualisiert

    Has anybody an idea how I can fix this? Or is reinstall the only possible solution?

  224. The upgrade seems to be a bit of a rush job… on shutdown, I get a red/purplish Ubuntu screen, the boot manager shows Ubuntu instead of Mint… and the installer doesn’t check for sufficient disk space. I seem to have upgraded to about 90 % ok, but now my root partition has 0 bytes left, and I can’t log in. Although I guess those could be two different issues.
    Oh well, I may need to re-install from scratch, I suppose.

  225. Fortunately, the upgrade program insisted on creating a snapshot… now I got my old 18.3 system back. Nice.

    1. Freed up some space and tried again. This time the upgrade went fine. Mint 19 works well for me, except for SMB. Hopefully it’ll be fixed soon.

  226. i’m using ryzen 5 2400g… i’m having problem boot in the linux mint 19… it show acpi error… how to solve this…

  227. the installed on my computer and my failed and the windows that I installed. the oldest editions did not do that. This is a big problem and I will have to abandon linux mint

  228. You could always run the latest in a VM as a test to see if it is worth upgrading to that version. I often do that before I make the change.

    1. As good and important and helpful as other users’ feedback can be, it’s nowhere near as “good and important and helpful” as testing on one’s own hardware. My preference is booting-from-and-running a new release from the LiveCD, but as MDC wrote, installing-in and running-from a VM is more fruitful, given the memory/storage constraints of doing so from the LiveCD.

      As with Iranian nuclear development, there’s no meaningful alternative to “inspect and verify”.

  229. Linux Mint 19 Cinnamon 64bits ISO from USB doesen’t recognize hard drive partitions so I can’t install it. When I try to install it form ISO USB It hangs on type of installation. I try using mintupgrade but I couldn’t — I want to upgrade from MinUpdate but it doesn’t appear the option

  230. If you are new to Linux then do not follow those “Top 10 things to do after you install… ” instructionals.

  231. Hi, since I upgraded to 19XFCE, I have regular issues with the graphics card (nvidia GEForce 7150) – in 50% of cases, I get a “blurred” screen, impossible to read. When it works and I run the “drivers manager” program, I do not have the possibility to chose the Nvidia drivers, like I did with 18.3
    I have 2 similar laptops (one with GEForce 6150, the other with 7150) and the problem is the same for both.

  232. RE: Software Sources>Maintenance>Remove foreign packages

    Since upgrading from Mint 18.3 to Mint 19, I’ve been getting this pop-up window 2 to 3 times a day “Sorry, Linux Mint 19 has experienced an internal error.” When I choose the option to send an error report, it says that it can’t send an error report because the package that caused the crash, or other type of error, is a foreign package.

    Today when I looked in Software Sources it listed 182 foreign packages! Of those 182, 29 show ubuntu 16.04 in the version number. I have a Timeshift Snapshot for Mint 18.3 created before I upgraded to Mint 19. Would those packages show up as “foreign packages” in Software Sources?

    If these “foreign packages” have nothing to do my pre-upgrade Timeshift Snapshot, is it safe to just remove all of them?

    1. Tom, 182 foreign packages doesn’t sound right (I only have 9, for example). Given the large number, perhaps it would be best to upload a list of these to e.g. Pastebin and raise an issue in the Mint forums ( that refers to that list. Also useful would be to include the output of inxi -r and apt check.

      To get a list of the foreign packages and their versions, installing apt-show-versions is useful. The following command line does the trick once it has been installed:

      apt-show-versions | grep “No available” | awk ‘{print $1, $2}’

    2. Oops, Pete! I forgot to click on “Reply” first, before posting! (Getting tired and sleepy, bedtime for me.) Please scroll down for my full reply…

  233. Pete, thanks for your prompt response, and for your advice!

    FYI: inxi -r output looks normal — 4 ubuntu sources and 1 canonical source – all bionic, and linuxmint tara. The only additional repositories — Google Chrome and Opera.

    apt check looks fine, too — no broken dependencies showing.

    apt-show-versions would not install from the terminal — shows error: “Unable to locate package…” And the package doesn’t show in Synaptic Package Manager, either. Oddly, it does show in Software Manager, but it’s description/reviews page, allowing install from there wouldn’t completely load. So, I’ll try again later.

    1. Something is definitely awry in that case since apt-show-versions is in Bionic’s universe repo. I assume that you’ve run apt update at some point (or some other program that has refreshed the indices).

      Definitely open a thread in the Mint forums. Additional output to include there, in addition to the output from the commands I’ve already provided, is dpkg –audit. If you paste a link to that thread here then I’ll head over and take part too.

    2. Hi Pete: Yes, I ran apt update several times the first 3 or 4 days after upgrading to Mint 19. Lately, though, I’ve mostly just refreshed Update Manager.

      But… I ran apt update just now again — and when I searched in Synaptic Package Manager this time for apt-show-versions it was there! Then I opened the Terminal and ran sudo apt install apt-show-versions and it installed without a problem!

      However, when I tried the command you suggested: apt-show-versions | grep “No available” | awk ‘{print $1, $2}’ I got this error:

      grep: available”: No such file or directory
      awk: cmd. line:1: ‘{print
      awk: cmd. line:1: ^ invalid char ‘�’ in expression

      Also, regarding “foreign packages” showing in Software Sources, today it lists 178. Then, when I looked in Synaptic Package Manager under Status>Installed (local or obsolete) — it listed the same 178 packages!

      So, I’m thinking now that a large part of the issue is that mintupgrade failed to clean up obsolete packages. For example: I noticed several gstreamer0.10 packages installed (not showing as supported) — and several other gstreamer packages with the same description installed (supported). They’re gstreamer1.0

      But, there are also headers for an extra kernel I have installed (just in case) in the “local or obsolete” list — e.g. linux-headers-4.13.0-45 latest version: 4.13.0-45.50~16.04.1 So, I guess Synaptic considers these as “obsolete” because, since the upgrade, there are no longer any sylvia repositories in Software Sources.

    3. P.S. Pete, the other command you suggested, dpkg –audit, didn’t show any output at all in the terminal.

    4. @Tom: When text is pasted on this site, the single and double quotes are both converted into “fancy” quotes, while a double dash (two dashes straight after each other) are converted into a long dash. You should try both the commands again but replacing those characters with the intended originals. For almost any command, entering man command, e.g. man dpkg, shows what the options are. For example, you’ll see that dpkg –audit has two consecutive dashes. This is one of the reasons that detailed support is better through the Linux Mint forums rather than on here, to be honest.

    5. Tom, sorry, I’ve just reread your comment and realise that you probably did use dpkg –audit correctly. No output means that all is good. My comment still applies to the other command though. I guess I shouldn’t try to reply to posts when I’m tired! 🙂 I look forward to you posting your problem on the Linux Forums.

    6. Hi Pete: I corrected the “fancy” quotes in the code you suggested I run to “regular” quotes. But the terminal rejected it again, still noting errors.

      In reading through man awk,, I noticed this: “pattern { action statements }”. So, I thought that there might need to be a *space* between the left curly bracket { and the first character in the statement in the code you suggested, and a space between the last character in the statement and the right curly bracket }

      So, I assumed that your code: apt-show-versions | grep “No available” | awk ‘{print $1, $2}’+, modified to apt-show-versions | grep “No available” | awk ‘{ print $1, $2 }’+ should work.

      But, when I tried it, the terminal complained about “awk: cmd. line:2: ^ unexpected newline or end of string”. So, I thought maybe the terminal didn’t like the + at the end of the string. So, I tried it without the +, and this time there were no errors noted, and I got an output!

      But, the output looks just like what’s showing in Software Sources>Maintenance>Remove foreign packages, and in Synaptic Package Manager>Status>Installed (local or obsolete). So, this command just yielded confirmation — but no new information.

      In case somehow getting the + at, or near, the end of the string to be accepted would give additional output, I tried several different variations — e.g., with a space }’ + and before the single quote }+’ and even inside the bracket $2, + }’ and probably a couple other variations I don’t remember right now, but none of them worked.

    7. Tom, I don’t know where the + came from, but it wasn’t from me. Putting that command aside, have you posted your problem on the Mint forums yet?

    8. Pete, how very strange! I copied and pasted the command from your post. So, it’s a mystery to me, too, where the + came from!! Maybe it was a typo on my part from being overtired at the time.

      But, the command as given, even without the +, wouldn’t work without the spaces I inserted after { and before }. I wasn’t imagining that, at least! 🙂 And, as a new Linux user, using the man file to find a way to tweak the command so it would run was a useful, confidence-building experience!

      I’m a bit puzzled, though, by the command output… What information did you expect the command you suggested would give that wasn’t already available in Software Sources>Maintenance>Remove foreign packages, and in Synaptic Package Manager>Status>Installed (local or obsolete)?

      As for the forum… No, I haven’t posted the “foreign” packages problem there. (A forum virgin, here!) I’m not a registered forum member, and, before posting anything, for a newbie, there is a substantial learning curve to first get thoroughly familiar with all of the proper procedures, the dozens of rules, guidelines, terms, policies, how to use a paste website, etc.

      And, anyway, I’ve already decided on my own solution: Creating a Timeshift snapshot, then carefully looking through all the “foreign” packages, and removing any that appear to be just duplicates of already installed newer packages.

      So, thank you, again, Pete, *so very much!* for your generosity and patience, for taking the time to share your knowledge, advice, and suggestions with me and so many others on this blog! You’re an outstanding example, in my opinion, of The Linux Way!! 🙂

    9. Hi Tom, the output from that command is essentially no different, as you rightly point out, but it is actual command line output which can then be properly cut and pasted, piped into another command etc. I just thought it might be useful to have the information in that format, particularly as the command is generic and doesn’t need e.g. Synaptic. You’ll just have to take my word for it that the original command I pasted worked fine on my system before I pasted it here and the quotes were “converted”, and that it works fine for me without the need for spaces within the curly brackets.

      Many thanks for your kind words. I just try to help out where I can because this isn’t really a support forum as such and therefore people’s queries for support aren’t generally given the same attention as they would be on the Mint Forums. I still recommend that you join the Forums – they’re a smart and helpful bunch on there. Don’t worry too much about etiquette – you’ll learn that as you go along.

    10. @Pete: Hi Pete! Don’t know if you’re still monitoring this blog… But, for the sake of clarity, and a mea culpa:

      I’ve discovered that the terminal command you suggested will work *with or without* a space inside each of the braces in the command, e.g., {print $1, $2}’ and { print $1, $2 }’

      Didn’t know the terminal could be so “flexible”! 🙂 I assumed exactitude and precision with commands was an inviolate rule!

      But the man awk I read through showed spaces inside of braces in each of the command examples I saw there!

      By the way: After many hours and much work I reduced the number of so-called “foreign packages” showing in Software Sources–> Maintenance post-upgrade from the original 182 to *10*.

      When I tried to remove the remaining 10, Maintenance refused removal of 9 of them, calling 7 of the 9 an “essential system package”. And the other 2 it said were dependencies of one or more of the “essential” packages. (It would have allowed removal of 1 of the 10 packages, but that would also remove xplayer.)

      Why packages that are “essential system packages” appear in Maintenance–> Remove foreign packages makes no sense at all to me!!

      So many confusing and seemingly contradictory things in Linux for a newbie!

  234. Thanks, Clem and TeamLM…I have to say that I was a bit trepidatious about upgrading…I know, I know, but I could always fallback with ‘Timeshift’.
    Faultless upgrade, having followed the advice given about reading, taking time and having a simulated upgrade to check.
    Minor niggle – I was hoping that my ‘Archer’ T9UH wireless adapter would be recognised – but apparently not; it was fine in kernel 4.13.43.
    All-in-all though, a good job very well done, Thanks again. DC.

  235. I have a SSD with LM19, Windows 10 and a NTFS partition, where i store data. Today i saw that it’s not possible to copy something from LM 19 to that NTFS partition or the other one with W10. Also it’s not possible to create a new folder or document. From that partitions to LM it works to copy something.
    I hope that this problem will be solved soon!
    Thank you!

    1. Concentrating on the separate NTFS partition to start off with (because not being able to access the Windows 10 partition may also be due to fast startup), what is your line in /etc/fstab to mount the partition? Also, which desktop environment are you using and how are you trying to copy the data?

      This works for accessing my shared NTFS partitions:

      UUID=xxxxxxxxxxxxxxxx /media/data ntfs rw,auto,users,exec,nls=utf8,umask=003,gid=1000,uid=1000 0 0

      assuming in this case that you have already created the /media/data directory.

    2. Pete
      I’m using only Cinnamon. I had always the same partitions and it was not a problem in the past for any other edition of LM. The last one was 18.3. Also beta 19 worked very well. About 2-3 weeks ago i had something to move on that partition and it was ok. Today Create new folder, Create new document, Organize by name and Paste are not activate and i can do nothing. This a very new and unexpected mistake and this is all i can tell you about. I haven’t had this problem in the last 20 years since i’m using a computer. To copy from that partition on other exterior HDDs, or on LM partition is not a problem because is working. So, the problem is with the interior SSD.

    3. @Tom K.
      check the ownership and read/write permissions on that shared partition first.

    4. Pete
      I put on SSD an older backup and i saw that everything works. I took the yesterday updates from the default servers and it’s ok. I don’t know what it was bun doesn’t matter!
      Thank you!

    5. @Peter E: I haven’t posted anything about issues with shared partitions. I’m assuming your suggestion was actually meant for dd.

  236. Hi again! Just wanted to clarify about printing with Xreader. After experimenting with different settings and printing into PDF printer, or just using Preview function it looks like “auto rotate and center” works right only if “Scale” is set to 100%. If it is less or more than 100% the page is moved off the center. This is a small but frustrating thing that makes you look for some other program which does the printing right.
    Again, Xreader is very light and fast and perfect for viewing pdfs! My hope is that in the future releases it will be just as awesome for printing as well!
    Thank you for all your hard work!

  237. Clem,
    The upgrade instructions you provided crashed my computer and I cannot access the my data, chiefly because I had encrypted the drive, I believe. Any advice on how to recover my files before I do a fresh install of Linux Mint 19?

  238. A big thank you to the folks who put Linux Mint 19 together. I am thoroughly enjoying the improvements, most of all the GUI speed-up, which is very, very pronounced. You have made my work life easily twice as enjoyable!

  239. The linux creators are a reason to live. It’s gotten to the point that It’s like a holiday to see what the new mint inventors have glued together for us. We probably would all agree, the intuitive and down to earth menus of mint make us all more productive (and going over to the mac and microsoft systems are always a total drag that leads to being distracted and bombarded with lost time).
    Vive La Mint!

    1. High praise of Clem and the Mint team — and well deserved!! 🙂

      Dear Clem and Team,

      I’d like to add my own *sincere appreciation!*, along with that of so many others, to all of you,
      for all the excellent work you do for all of us!! 🙂

      Love you guys!


  240. 18 July 2018 Many thanks again to Clem and team for an attractive and useful update. Especial thanks to Tony W, whose message directed to me, but of use, potentially to anyone who seeks to print via SAMBA, dated 14 July, led to my success printing, after so many days of frustration. Here is Tony’s message, excerpted:
    ” … recent changes to Samba’s protocol affect browsing of network shares…..
    edit… /etc/samba/smb.conf … added the line
    client max protocol = NT1
    in the [global] section ……… ”
    Many Thanks Tony W, fixed it for me, too.
    With regard to Tony’s reflection on advantages of upgrading or not, I would add that, in my experience, if one intends running MINT on a newer machine, (for me, Intel 8350k), only 19 works, 18.3 chokes, and yields an error message, runs incredibly slowly. That problem only exists, in my experience, on the newest Intel architecture. So, that could represent further motivation for some folks to upgrade.

  241. I noticed today on a fresh build of LM19 Cinnamon, with updates, that:
    (1) wine-stable is no longer available, the wine meta-package now installs wine 1.6 with suitable menu items
    (2) Network browsing with samba now works without having to fiddle with smb.conf
    I assume these are adjustments made in recent updates to overcome problems reported during beta testing.

  242. I downloaded linux mint 19 cinnamon and installation in my HP ENVY Ultrabook 4-1030. Now shutdown time is 4-5 minute. Please solve this issue.

    1. Ahmed, although there’s no error displayed, it may be related to “acpi”.. So just go to Bios and have a look to all menus and submenus if there’s an option as acpi (or something like Advanced Power … etc.). If there’s ; make it OFF or Disabled and save & exit …

      ( )

    2. … And this may be helpful: ..

      ( Shortly: If you see such a file or folder named resume under conf.d , for example I have no such problems and my conf.d folder is empty; no resume file )


      instead of the line
      RESUME = UUID = 1d55ee77-cf0….. (yours will be a different number)
      enter the line:
      RESUME = none

      (And also try to install the newest kernel using the update manager)

  243. do you have any linux mint distro that doesn’t use grub, grub is the source of all installation failures I ever had with linux mint, I think grub should be banned forever, grub is the worst piece of cancer that ever been created, all my head ache would disappear if linux mint didn’t use grub, the world would be a better place w/o grub.
    please, make a grub free linux mint distro,

    1. it’s mid 2018, why are you still clining onto textual boot loader grub when there’s graphical boot loaders like gag out there, it’s mid 2018 and nobody should be forced to use a text terminal, graphical user interfaces isn’t news, there’s gag graphical boot loader, just kick grub to the curb and use gag instead, i’m going to try gag and hopefully I can throw grub in the trash can where it belongs.

    2. Hello, I searched for the gag BL that you mentioned but could not find anything that mentions it… Can you provide a link? Thanks

    1. As far as I know, the libGL issue has been resolved and you should be fine to go through with the upgrade process. I would suggest that you make another TimeShift snapshot, go through the upgrade process again and, if you encounter any issues, ask for help on the Mint Forums (

  244. Linux Mint 19 Cinnamon/Xfce bug report:
    I restore ‘System Settings’->’Startup Applications’->’mintwelcome’ to ON (after it was reset to OFF), then restart the laptop, but the mint-welcome screen does not appear.

    1. The welcome screen has its own “don’t run me” flag. Launch it manually and tick “Show this dialog at startup”, at the bottom of the window.