They offer different flash templates with latest features.
Login

Forgot password
Register
Back
Written by:
clem
Score: 13
votes: 13
Format: Article

 How to upgrade to Linux Mint 19


A. Introduction

This tutorial explains how to upgrade to Linux Mint 19.

B. General considerations

B1. Do you need to upgrade?

Linux Mint 17.x (17, 17.1, 17.2 and 17.3) will be supported until 2019.

Linux Mint 18.x (18, 18.1, 18.2 and 18.3) will be supported until 2021.

If your version of Linux Mint is still supported, and you are happy with your current system, then you don't need to upgrade.

B2. Did you try Linux Mint 19 on this computer?

Each new version of Linux Mint comes with a new kernel. This means that it handles hardware differently. For instance, you may find out that a graphic card or a wireless adapter which currently works fine for you under Linux Mint, isn't recognized by the newer version of Linux Mint you're planning to upgrade to. In some cases, this could mean that upgrading to this release is the wrong decision, maybe you're better off skipping that particular release? There's only one way to know: you need to try it.

Linux Mint comes as an ISO image which can be burnt to a DVD or a USB stick. Thanks to this, you can try the newer release on your computer and see if your hardware is recognized without installing and before upgrading.

B3. Did you create a system snapshot?

If anything breaks or if anything goes wrong during the upgrade, you can go back in time and revert all changes by restoring your latest system snapshot. Whatever happens, you're covered.

B4. Did you make backups?

Your personal data is the most valuable thing in your computer. If anything happens and you break your operating system, it's not a problem, it can be reinstalled or restored via a system snapshot. If you lose your data or you're unable to access it... that's a different story.

To be safe, make a full backup of your data on an external device (USB stick or DVD).

C. Requirements

To upgrade to Linux Mint 19 you need to satisfy the following requirements.

C1. Experience with APT and the command line

Upgrading to a newer package base is not trivial and it should not be performed by novice users.

You need to know how to type commands and read their output.

You also need to be experienced with APT.  During the upgrade you'll need to understand the output of APT commands. You'll need to understand if a package needs to be removed, if it blocks the upgrade, if it conflicts with another package etc etc.

C2. Linux Mint 18.3 Cinnamon, MATE or Xfce edition

The upgrade tool only upgrades Linux Mint 18.3 Cinnamon, MATE or Xfce edition.

If you are running Linux Mint 18, 18.1 or 18.2, you first need to upgrade to Linux Mint 18.3 using the Update Manager.

C2. Timeshift snapshot

To install timeshift, open a terminal and type:

apt install timeshift

Then launch "Menu -> Administration -> Timeshift".

Follow the wizard to select a destination for your snapshots.

In the toolbar, click on the "Create" button to make a manual snapshot of your operating system.

If anything goes wrong, you'll be able to restore your operating to this current state, either from within Linux Mint, or by launching Timeshift from a live Mint session (live DVD or live USB).

C2. LightDM

To know which display manager you are currently using, open a terminal and type:

cat /etc/X11/default-display-manager

If the result is "/usr/sbin/lightdm", you can skip this step.

If the result is "/usr/sbin/mdm", you need to switch display managers by installing lightdm and removing mdm. Open a terminal and type:

apt install lightdm lightdm-settings slick-greeter

When asked to choose a display manager between MDM and LightDM, choose LightDM.

Open a terminal and type:

apt remove --purge mdm mint-mdm-themes*

sudo dpkg-reconfigure lightdm

sudo reboot

D. How to upgrade

D1. Update your Linux Mint 18.3 system

Using the Update Manager, click on "Refresh" to refresh the APT cache and apply all updates.

D2. Give your terminal unlimited scrolling

Open a terminal.

Click on "Edit"->"Profile Preferences"->"Scrolling".

Check the "unlimited" option and click "OK".

D3. Install the upgrade tool

To install the upgrade tool, open a terminal and type:

apt install mintupgrade

D4. Check the upgrade

To simulate an upgrade, open a terminal and type:

mintupgrade check

Then follow the instructions on the screen.

This command temporarily points your system to the Linux Mint 19 repositories and calculates the impact of an upgrade.

Note that this command doesn't affect your system. After the simulation is finished, your original repositories are restored.

The output shows you if the upgrade is possible, and if it is, which packages would be upgraded, installed, removed and kept back.

It is extremely important that you pay close attention to the output of this command.

If it shows packages which are preventing the upgrade, remove them (and take note of them so you can try to reinstall them after the upgrade).

Also note any important packages in the list of packages which would be removed, so you can reinstall them after the upgrade.

Keep using "mintupgrade check" and do not proceed to the next step, until you're happy with the output.

D5. Download the package upgrades

To download the packages necessary to upgrade to Linux Mint 19, type the following command:

mintupgrade download

Note that this command doesn't actually perform the upgrade itself, but just downloads the packages.

Note also that this command points your system to the Linux Mint 19 repositories (if you want to go back to Linux Mint 18.3 after using this command, you still can, with the command "mintupgrade restore-sources").

Use the "mintupgrade download" command until all the packages are successfully downloaded.

D6. Apply the upgrades

Note: This step is non-reversible. Once you perform it, the only way to go back is by restoring a system snapshot. Make sure you've made a snapshot before following this last step.

To apply the upgrades, type the following command:

mintupgrade upgrade

E. Workarounds

E1. Boot stuck at /dev/mapper/cryptswap1

If upon reboot, the computer fails to boot and the boot sequence seems stuck, type the left or right arrow to switch from the boot logo to the boot details.

If the boot is stuck trying to run the /dev/mapper/cryptswap1 job, then do the following:

  • Boot the computer with the Shift key pressed to force the Grub menu to show
  • Choose "Advanced Options" for the latest kernel entry
  • Choose "Recovery mode"
  • Once in the recovery menu, choose "fsck" and choose "yes".
  • Once fsck is done, press Enter to go back to the menu.
  • Choose "root" from the recovery menu and press "Enter" to start the root console.
  • Type "nano /etc/fstab" to edit the fstab file.
  • Find the line with "/dev/mapper/cryptswap1" and add a # sign in front of "/dev/mapper/cryptswap1"
  • Press "Ctrl+O" and then "Enter" to save the file
  • Press "Ctrl+X" to exit the nano editor
  • Type "reboot" to restart the computer

After a successful boot, the crypted swap might activate properly. You can try that by editing /etc/fstab again and reactivating the line for cyptswap (by removing the # sign in front of it).

F. Alternatives

If you cannot upgrade to Linux Mint 19, please perform a fresh installation.

Generic instructions on "fresh upgrades" are also available at https://community.linuxmint.com/tutorial/view/2

G. Notes

  • It is recommended to use the default Linux Mint mirror before upgrading, to make sure you're using the latest version of mintupgrade. You can check your version of mintupgrade with "apt version mintupgrade", and you can check what the latest version of mintupgrade is at https://github.com/linuxmint/mintupgrade/commits/master. You can also download it at http://packages.linuxmint.com/pool/main/m/mintupgrade/
  • The upgrade overwrites files in /etc/ with default configuration files. You can restore files indivually by the Timeshift snapshot you made prior to upgrading.

Tags: upgrade mint 19
Created: 4 months ago.
Last edited: 4 months ago.
Reviewed: 1 month ago.


Comments
2 days ago

lipiakter
Thanks a lot. Specially jancoffee and hamaryns for full proofing.  
1 month ago

jancoffee
I just upgraded from Linux mint 17->18->19 and it worked great but during the 18->19 upgrade I got this error after running the "mintupgrade upgrade"

I got repeating error message:

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.

My solution was to run the commands:
sudo dpkg --configure -a
sudo apt-get install -f

and then re-run the "mintupgrade upgrade" and it worked like a charm to upgrade to Mint 19 :-)

I hope this can help anyone,
thanks for a great community!
 
2 months ago

peppefava
I do suggest everyone to follow hamaryns instructions before upgrading. In fact I experienced some problems (repeated "dpkg: error processing package gconf2", as described by MRDK) when following this guide and solved it all with autoremove + autoclean + upgrade + reboot.
Hope the author may want to update the tutorial.

Besides this, I'm do experiencing important system slow down after upgrading, both at boot time and system running time. In fact, I've been looking for some driver updates, such as video and CPU microcode drivers. Video drivers already result to be set on the recommended (proprietary) driver, but no trace of the CPU microcode which may really make the difference.

That said, any suggestion to make my system faster and worth the upgrading?

Thanks,
Regards.

ASUS S510UN-BQ052T
Intel Core i7-8550U
 
3 months ago

hamaryns
Update on last post: I logged in via the terminal (Ctrr-Alt-F1) and did

sudo apt-get autoremove
sudo apt-get autoclean
sudo apt-get upgrade
sudo reboot

after which it works! (Unsure whether autoremove and autoclean made a difference.)

Woohoo!
 
3 months ago

hamaryns
Hi,

I’m afraid this didn’t work for me. I came from 17.3. The upgrade to 18 and then 18.3 worked smoothlessly, but then after changing the display manager and reboot, I had a blank screen. X no longer worked. I tried to do the rest of the upgrade from the command line (Ctrl-Alt-F1), but it ended in an error, a few hundred packages were not upgraded and still blank screen. So I’ burning a fresh ISO now...

Cheers, H.
 
3 months ago

www_MKRD_info
7. This upgrade breaks additional / custom keyboard layouts, and they have to be added back:
http://mkrd.info/computer-software-related-articles/linux-2/adding-russian-phonetic-yazhert-keyboard-to-linux.html
 
3 months ago

rewind
Another attempt here, last time I thought the libgl1 issue was caused by the installed padoka-ppa only. After the latest blog post, however it turned out it was an issue with the latest mesa update, related to the upgrade somehow, so I've attempted to upgrade again, but failed due to a similar reason:

```
+ Re-installing the meta-package for your edition of Linux Mint...
[sudo] password for tod:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
mint-meta-cinnamon : Depends: mint-meta-core but it is not going to be installed
Depends: cinnamon but it is not going to be installed
Depends: cinnamon-control-center but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
```

Which in my case seems to be indeed related again to a not fully uninstalled padoka-ppa.

READ BELOW ONLY IF YOU GET INTO THE SAME SITUATION, this might not fix any other issues, but could be useful to someone.

If someone else gets into the same situation, the steps up to the end of the upgrade in my case were:

apt install -f # then just select "no" to the option to remove cinnamon and select "yes" on the option to downgrade the libgl1 to the "bionic" version (down from the version in the "padoka-ppa"). It should be the only change required.

Looked at the mintupgrade script (which could be conveniently found in the timeshift backup snapshot ;) ) and to the end of the upgrade there are only the following changes:

sudo apt-get install mint-meta-core mint-meta-cinnamon mintsystem mint-meta-codecs # I'm using cinnamon, please update as necessary
sudo apt-get install rhythmbox libblockdev-crypto2
sudo apt-get purge vino banshee gnome-user-share
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
sudo /usr/share/ubuntu-system-adjustments/systemd/adjust-grub-title
diff ~/Upgrade-Backup/fstab /etc/fstab && cp -va ~/Upgrade-Backup/fstab /etc/fstab && echo "A package modified /etc/fstab during the upgrade. To ensure a successful boot, the upgrader restored your original /etc/fstab and saved the modified file in ~/Upgrade-Backup/fstab.upgraded." 1>&2

Also something bad happened with my fonts, only ubuntu fonts were left installed, so I've checked what were the differences between the regular Mint 19 install CD and the packages installed after the upgrade and it turned out that one of the ttf-* font packages were breaking the dependencies for some of the packages that were in the default Mint 19 install ISO. Try to remove all ttf-* font packages (they could be re-installed later) and install all font* packages from the default CD (this of course is from the diff between my installation and the Mint 19 CD):

apt-get install fonts-beng fonts-beng-extra fonts-deva fonts-droid-fallback fonts-deva-extra fonts-gubbi fonts-gujr fonts-gujr-extra fonts-guru fonts-guru-extra fonts-indic fonts-kalapi fonts-knda fonts-liberation2 fonts-lohit-beng-assamese fonts-lohit-beng-bengali fonts-lohit-deva fonts-lohit-gujr fonts-lohit-guru fonts-lohit-knda fonts-lohit-mlym fonts-lohit-orya fonts-lohit-taml fonts-lohit-taml-classical fonts-lohit-telu fonts-lmodern fonts-lyx fonts-mlym fonts-nakula fonts-navilu fonts-noto fonts-noto-cjk fonts-noto-color-emoji fonts-noto-mono fonts-noto-unhinted fonts-orya fonts-orya-extra fonts-pagul fonts-sahadeva fonts-samyak-deva fonts-samyak-gujr fonts-samyak-mlym fonts-samyak-taml fonts-sil-andika fonts-smc fonts-smc-anjalioldlipi fonts-smc-chilanka fonts-smc-dyuthi fonts-smc-karumbi fonts-smc-keraleeyam fonts-smc-manjari fonts-smc-meera fonts-smc-rachana fonts-smc-raghumalayalamsans fonts-smc-suruma fonts-smc-uroob fonts-symbola fonts-taml fonts-telu fonts-telu-extra libfont-afm-perl libfontconfig1-dev:amd64 libfontconfig1:i386 libfontenc-dev:amd64 libfreetype6-dev:amd64 libfreetype6:i386 libt1-5 libxfont-dev libxfont1-dev libxfont1:amd64 libxft-dev libxft2:i386 ttf-ancient-fonts-symbola ttf-bitstream-vera ttf-indic-fonts-core ttf-mscorefonts-installer ubuntu-restricted-extras x11-xfs-utils x11proto-fonts-dev x11proto-xf86bigfont-dev xfonts-mathml

Anyhow, to the others:

@www_MKRD_info - indeed, thought that the time to upgrade might be related to the OS drive and filesystem/options used. In my case however with a really fast NVMe and btrfs with lzo compression it still took a lot of time to finish the installation, and asked couple of times for a password. But this really is an improvement from the 24 hours I've seen with some of the Ubuntu upgrades ~10 years ago :)

@sqbeal - I guess a good idea to work around the timeshift enforced snapshot is to install and configure it under 18.3, directly on a partition/drive different than the OS one (if there is no space available there) or to directly use BTRFS snapshots if the OS filesystem is compatible (it might not be not working, though, see below).

On another note timeshift would sometimes complain that it needs a root(@) btrfs volume, even if one exists. Another user already reported this here - https://github.com/teejee2008/timeshift/issues/241, hopefully it will be fixed soon, the timeshift with btrfs subvolume snapshots is much more efficient in terms of space and takes significantly less time/resources compared to the rsync approach.

Good luck with the upgrade to all! :)
 
3 months ago

www_MKRD_info
6. sudo restart is an immediate and a forceful restart. Authors here and elsewhere should say "after you have saved any session data you want to save, and closed all user documents / browser windows etc, and when you are ready then type in sudo restart". I did not know this process does not even prompt me to save any open and edited files.  
3 months ago

www_MKRD_info
1. This process will take 4 hours or more, only do on a weekend if you don't want to lose sleep on a work evening / night.

2. I got repeating error message:

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.

then it said

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

And I guess repeated everything all over again, and it seems OK...

3. You will get a badly resized version of your desktop picture as your login picture, and this will have to be fixed.

4. TimeShift image should, of course, go to a different and separate (i.e. external backup HD) media!

5. I guess this is because how long it takes, but this process will ask for your su password about four times, so this process requires babysitting, or at least an occasional progress check.

www.MKRD.info
 
3 months ago

sgbeal
One major gripe: the installation of timeshift is forced on the user - the installation won't run without it. Then, ironcially, timeshift is what broke by install. It made a 16GB snapshot of my 13GB installation, filling up the 29GB root partition, which of course caused the remainder of the installation to fail.

A _forced_ backup, especially one written to the root partition, is a poor policy choice. Anyone running the upgrade without making a backup, or knowing how to recover, knows what the hell they're doing (or will know after the installation fails and they have to learn to recover it).
 
3 months ago

SeaMonkey82
If you have added the padoka ppa, you will want to purge prior to upgrading.

sudo apt-get install ppa-purge aptitude
sudo ppa-purge -d xenial ppa:paulo-miguel-dias/pkppa

Also, after upgrading, if you're using nvidia-396, you'll have to switch to the recommended driver (currently nvidia-driver-390) in Driver Manager.
 
3 months ago

sgbeal
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
emacs24-bin-common emacs24-common emacs24-common-non-dfsg


*Nooooooo!*

Oh, whew....

The following NEW packages will be installed:
...
emacs25 emacs25-bin-common emacs25-common


i almost panicked.


It does seem extremely odd that the "mindupgrade" command refuses to let you start it as root, but the first thing it does is ask for your su password.
 
3 months ago

sidux
it works's fine, GREAT JOB guys.
if updating two system whitout any problems :thumb:
 
3 months ago

petaramesh
Hello,

I confirm Ooberi's comment 2 weeks ago : I just used this procedure to upgrade my son's machine from Mint 18.3 to 19, and the upgrade went seemingly well, but broke grub, going into rescue mode at reboot with a message about bad grub binaries ELF signature.

Booting from a live distro stick, chrooting into the HD install and then reinstalling grub to sda from there fixed the issue, but a n00b would have been checkmated...

(Once grub is reinstalled, everything looks allright)

Kind regards.
 
4 months ago

biker95
I was not able to update Linux Mint 18.3 As well as previous users, got the libgl1 error. What destroyed my Cinnamon environment. Restored the system using the Timeshift program. But now some programs work with failures, their reinstallation does not help. When will libgl1 be released?  
4 months ago

RPeters52
Hello,

I just did a massive update on my old Chromebook running LM 19 as a result of "update". It had a problem with libwebkit2gtk-4.0.so.37 when starting gufw -- see previous comments. Now, gufw starts with no problems. So, never mind. One less item on your list.

I still see "Ubuntu 19" on the startup screen??

I would appreciate a link to a discussion or a comment on:
"It looks like 19.0 has moved from cron to a systemd timer.... setup. For example, my files in cron.weekly had their names changed -- fstrim became
fstrim.dpkg.bak. I suppose that means my fstrim is not being run or ????"

Thanks,
Ralph
 
4 months ago

maxfranco
another tip...
during installation i suggest to work only with wired network connection, disabling wireless networking, both on new installation and upgrade.
in new installation install proprietary driver first, then disable wireless networking and then proceed to install.
in upgrade pay attention that wireless is removed and restored in active state during upgrade process, also if you disabled it, so when it become active again disable it as soon as possible.
without this trick i obtained a partial installed new system , without cinnamon and i was not able to install a working system also installing cinnamon-meta package (only fallback was working).
 
4 months ago

rewind
Hello Clem,

Thank you for providing this tutorial, just tried to upgrade from 18.3 to 19 and it turned out that the timeshift step was really crucial :)

Similar to RPeter52 I've had cinnamon complaining that libgl1 is missing (ldd was indeed showing no libgl1), however an attempt to install the libgl1 package actually removed cinnamon and a bunch of other packages. I've restored to the last stable snapshot, because the system was in broken state at this point.

I guess this is caused by the non-default mesa installed from the padoka-ppa some time ago (I've actually forgotten about this). Perhaps I'd need to first clean this up a bit and restore to the expected version provided by default in 18.3 (I guess 16.04 LTS).

I'll use another drive tomorrow to play around with the upgrade without padoka-ppa drivers. Thought it would be best to leave a not here for other users before an attempt to upgrade.

Best,
T.
 
4 months ago

RPeters52
Hi,

I tried running gufw (Firewall) from the USB stick and it runs fine. On my upgrade it fails -- see previous comment.

I have used unix systems for a time (since the early 1990s) so I looked around for more info on the "missing library". It is not obvious to me what the problem is. The upgrade's info about the library (libwebkit2gtk-4.0.so.37) appears OK to me and nearly identical to that from the USB stick run.. See below! ANY bright ideas???

This is an old, slow machine, so I do not need it running anytime soon. BUT, it makes me hesitant to "upgrade" laptops that I use regularly.

Ralph
-------------------------------------------------------------------
Running on the USB stick
mint@mint:~$ ldconfig -p | grep libwebkit2
libwebkit2gtk-4.0.so.37 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37


mint@mint:~$ ls -las /usr/lib/x86_64-linux-gnu/libwebkit2gtk*
0 lrwxrwxrwx 1 root root 28 Apr 10 18:34 /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 -> libwebkit2gtk-4.0.so.37.28.1
41979 -rw-r--r-- 1 root root 42986008 Apr 10 18:34 /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.28.1
mint@mint:~$
--------------------------------------------------------------------
Running on the same PC using the upgrade:
ralph@ralphChrmBk ~ $ ldconfig -p | grep libwebkit2
libwebkit2gtk-4.0.so.37 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37

ralph@ralphChrmBk ~ $ ls -las /usr/lib/x86_64-linux-gnu/libwebkit2gtk*
0 lrwxrwxrwx 1 root root 28 Jun 14 10:58 /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 -> libwebkit2gtk-4.0.so.37.28.3
41984 -rw-r--r-- 1 root root 42986008 Jun 14 10:58 /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.28.3
 
4 months ago

RPeters52
When I try to start the Firewall (gufw), it fails

gufw

** (gufw.py:6361): WARNING **: 19:27:27.489: Failed to load shared library 'libwebkit2gtk-4.0.so.37' referenced by the typelib: libGL.so.1: cannot open shared object file: No such file or directory
/usr/share/gufw/gufw/gufw/view/gufw.py:117: Warning: cannot retrieve class for invalid (unclassed) type 'void'
self.web_content = WebKit2.WebView()
Traceback (most recent call last):
File "/usr/share/gufw/gufw/gufw.py", line 30, in
gufw = Gufw(controler.get_frontend())
File "/usr/share/gufw/gufw/gufw/view/gufw.py", line 79, in __init__
self._set_objects_name()
File "/usr/share/gufw/gufw/gufw/view/gufw.py", line 117, in _set_objects_name
self.web_content = WebKit2.WebView()
TypeError: could not get a reference to type class

BUT, it appears that the library
(from above: libwebkit2gtk-4.0.so.37' referenced by the typelib: libGL.so.1: cannot open shared object file: No such file or directory)
is actually there!!

ralph@ralphChrmBk ~ $ locate libwebkit2gtk
/usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 <<<<<<<<<<<<<<<<<<<<
/usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.28.3
/usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/injected-bundle/libwebkit2gtkinjectedbundle.so
/usr/share/doc/libwebkit2gtk-4.0-37
/usr/share/doc/libwebkit2gtk-4.0-37/NEWS.Debian.gz
/usr/share/doc/libwebkit2gtk-4.0-37/NEWS.gz
/usr/share/doc/libwebkit2gtk-4.0-37/changelog.Debian.gz
/usr/share/doc/libwebkit2gtk-4.0-37/copyright
/var/lib/dpkg/info/libwebkit2gtk-4.0-37:amd64.list
/var/lib/dpkg/info/libwebkit2gtk-4.0-37:amd64.md5sums
/var/lib/dpkg/info/libwebkit2gtk-4.0-37:amd64.shlibs
/var/lib/dpkg/info/libwebkit2gtk-4.0-37:amd64.symbols
/var/lib/dpkg/info/libwebkit2gtk-4.0-37:amd64.triggers
ralph@ralphChrmBk ~ $ ^C
ralph@ralphChrmBk ~ $

 
4 months ago

arun175
I Upgrade to 18.3 to 19, the start screen says Ubuntu 19 & thers is no Hibernate option....  
4 months ago

RPeters52
BTW, the start screen says "Ubuntu 19" ????  
4 months ago

RPeters52
I did the upgrade from 18.3 to 19.0 on an old chromebook (Acer c720) and things appear to work so far.

It looks like 19.0 has moved from cron to a systemd timer.... setup. For example, my files in cron.weekly had their names changed -- fstrim became fstrim.dpkg.bak. I suppose that means my fstrim is not being run or ????

Could you tell me where I can read about this change and what I should do in the future?
 
4 months ago

iscadar
I did the upgrade from LM 18.3. After the reboot it says that "Cinnamon just crashed. You are currently running in Fallback mode. Do you want to restart Cinnamon? Yes/No"
Choosing 'Yes' results in an error message repeat.

I changed the kernel i use and the message remains. Any suggestion?
 
4 months ago

Trapper333
I did this upgrade on a LM 18.3 box that was set up using full disk encryption with no vulnerable boot partition via Pepas' lmdescrypt v 0.986 script. It upgraded without a hitch and I experienced no adverse affects/problems regarding the encryption/lvm2 setup that already existed. Only hiccup I have found so far with this upgrade is that xed vanished after the upgrade and I had to apt install it.  
4 months ago

stefanoful
Hi Clem, congratulation for excelent work all team.
On fresh install with mint 18.3 on Virtualbox(cinnamon), executing the mintupgrade guide (conplete and whitout error's or package conflict), but at login start in fallback mode.
 
4 months ago

bartv
Update to my last comment for others that may experience this issue.

The answer at https://unix.stackexchange.com/questions/125832/no-hibernate-option-in-power-manager-on-mint-16-mate successfully re-enables the Hibernate option in the shutdown menu. Worked for both machines. I don't know if it is necessary, but I marked the new .pkla file as executable.

It seems strange that the live disk has the Hibernate option (it actually finds and mounts the swap partition), but the upgraded installation does not have it.

Cheers, Bart
 
4 months ago

bartv
Hi Clem,

Have just upgraded my desktop Dell T3500 also from mint 18.3 Cinnamon. Everything went smoothly, except that I now have no Hibernate option anymore in the shutdown menu (Suspend is there and works fine). The swap partition is active and is twice the size of RAM.

Just checked, and the laptop from my previous comment has also lost its Hibernate option. Its swap partition is also active and plenty large enough.

Any ideas?

Cheers, Bart
 
4 months ago

JOPETA
Thanks Clem. Just a typo, when numbering C subsections get stuck at C2. ;)  
4 months ago

bartv
Thanks for an excellent upgrade process.

Very smooth upgrade from 18.3 Cinnamon on a Dell Inspiron 7000 series 2 in 1 laptop. Only issue (trivial) so far was that the window title bar icons went back to default positions.

I would also suggest that you add an option to bypass the compulsory installation of Timeshift for the upgrade script. Some of us use other snapshot tools, such as Clonezilla.

Cheers, Bart.
 
4 months ago

Sivee
Upgraded from Mint 18.3 Cinnamon to Mint 19 Cinnamon OK.
One issue my icon for Evolution email disappeared from the panel, but the application was installed and it was updated from the older version that was in Mint 18.3 to version 3.28.1-2. Not sure if this is a bug but thought I should report it.

Also can't select the same title bar in settings that I had in Mint 18.3 is this by design?

Other than that it all went smoothly following this procedure.

Thanks for a great release Clem.

Siv
 
4 months ago

Ooberi
Hi, successfully upgraded Cinnamon Edition from 18.3 to 19. Everything went well. After reboot, I got a message: "error: no symbol table, press any key". After a key a successful boot occurred. I fixed this by official Ubuntu instructions of reinstalling grub: https://help.ubuntu.com/community/Grub2/Installing#Reinstalling_GRUB_2_from_a_Working_System
 

Other tutorials from clem