Upgrade from Mint 17.1 to Mint 19 in-place (experiment)

Chat about anything related to Linux Mint
Forum rules
Do not post support questions here. Before you post read the forum rules. Topics in this forum are automatically closed 6 months after creation.
User avatar
karlchen
Level 23
Level 23
Posts: 18173
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: Upgrade from Mint 17.1 to Mint 19 in-place (experiment)

Post by karlchen »

catweazel wrote: Fri Sep 28, 2018 7:55 amHave you had any complaints yet about cruelty to guinea-pigs?
So far no complaints. After all the guinea-pig is still alive. :)
Who would have suspected so 12 days ago? :wink:
Image
The people of Alderaan have been bravely fighting back the clone warriors sent out by the unscrupulous Sith Lord Palpatine for 762 days now.
Lifeline
DAMIEN1307

Re: Upgrade from Mint 17.1 to Mint 19 in-place (experiment)

Post by DAMIEN1307 »

hi karlchen...i have been following this for the 12 days...WOW...best argument ever that i have ever heard in support of new, clean install...lol...DAMIEN
User avatar
karlchen
Level 23
Level 23
Posts: 18173
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: Upgrade from Mint 17.1 to Mint 19 in-place (experiment)

Post by karlchen »

Hi, DAMIEN1307.

In case a user today, Sept. 28th, 2018, uses Mint 17.1 still and wants to upgrade to Mint 19 now, then yes, by all means, the most efficient approach and the most trouble-free approach will be:
+ backup your data (you do so regularly anyway, don't you)
+ install Linux Mint 19 from scratch
+ restore your data
+ fine-tune the system to your liking
This will give you a clean system, no remainders left behind from previous incarnations.

Yet, this was not the point of the experiment. The question rather was: can a Mint 17.1 system be upgraded in-place to Mint 19, using the official in-place upgrade paths without breaking it inbetween?

A user may start using Mint 17.1 way back in 2014, a fresh installation. He upgrades in-place to Mint 17.3 after some months, when Mint 17.3 becomes available.
Again some months later, in the middle of 2016, Mint 18 becomes available. Again this user upgrades in-place to Mint 18.
When Mint 18.3 becomes available, the same game: that user upgrades Mint 18 to Mint 18.3.
And finally in 2018, he upgrades to Mint 19.
This upgrade scenario would have taken more than 4 years, not just 12 days.
There are quite a few users around, who are pretty loathe to do fresh installations. Such a user might take this route.

The question is: can Mint 17.1, which has been upgraded in-place to Mint 19 in several stages, be a stable usable system in the end?
At the moment, the only thing I can tell is that this Mint 19 can be booted and used. I have not started investigating which issues may have been left behind.

About the 12 days: I could have reduced the number of days needed for the 4 upgrade stages substantially:
+ if I had had the time to spend whole days on the experiment, but there is the job also and a few other things which consume time
+ if I had not wanted to make sure after each upgrade that the resulting system were as clean as possible

Anyway, now that the system is on Mint 19, we will see into which problems I will run.

Best regards,
Karl
Image
The people of Alderaan have been bravely fighting back the clone warriors sent out by the unscrupulous Sith Lord Palpatine for 762 days now.
Lifeline
DAMIEN1307

Re: Upgrade from Mint 17.1 to Mint 19 in-place (experiment)

Post by DAMIEN1307 »

hi karlchen...yes i totally got it, why you were doing this...lol...in another posting by someone else sometime ago, the poster was trying to do via remote via teamviewer on his parents computer, the same thing that you just did...i could only say to him was, "really!!! your doing what!!!, via teamviewer???...you got to be kidding me"...lol...i totally get the exercise you went through and know you could have cut in time what you accomplished, and yes, i know that its possible but WOW...talking about the average user taking the "long way around the barn" to make it happen...lol...DAMIEN
User avatar
jimallyn
Level 19
Level 19
Posts: 9075
Joined: Thu Jun 05, 2014 7:34 pm
Location: Wenatchee, WA USA

Re: Upgrade from Mint 17.1 to Mint 19 in-place (experiment)

Post by jimallyn »

Nicely done and well documented, Karlchen. I am about to upgrade my Mint 17.3 Cinnamon to Mint 19 XFCE, by way of a fresh install on a new (and bigger!) hard drive. But once that is done, well, I will have that 17.3 install on the old hard drive to play with.
“If the government were coming for your TVs and cars, then you'd be upset. But, as it is, they're only coming for your sons.” - Daniel Berrigan
User avatar
karlchen
Level 23
Level 23
Posts: 18173
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: Upgrade from Mint 17.1 to Mint 19 in-place (experiment)

Post by karlchen »

Step 4: Upgrade my Mint 18.3 to Mint 19.0 in-place using MintUpgrade 18.3.11
  • MintUpgrade to Mint 19 Aftercare and Troubleshooting
    1. Eye candy: From Mint-Y to Mint-X
    2. Readability: System fonts on (None)
    3. Cleaning up obsolete software packages && More left behind software packages
    4. Re-adding PPA's removed by mintupgrade
    5. cgmanager left-over
    6. Uninstalling obsolete kernel series 4.4.0-xx
    7. HP Colour Laserjet & Scanner no longer fully functional
    • Eye candy: From Mint-Y to Mint-X
      I admit that this time, when Mint 19 Cinnamon had started up for the first time, I wasted some time on fixing the "eye candy" a bit. :oops:
      I am not a fan of flat, minimally structured, "modern" icons. Therefore the Mint-Y icons are not for me. Sorry, guys. Beauty lies in the eye of the beholder.
      So here is what has been modified via System Settings => Themes.

      Image
      (Sorry for the German screenshot, but prefixing "LC_ALL=C" to the command did not want to switch "Themes" to English)

      The 3 changes, illustrated in the screenshot do not only bring back the well-known icons, but also paint the application window title bars in the same dark colour as the bottom panel. Perfect match for my taste.
      .
    • Readability: System fonts on (None)
      The fonts in Cinnamon looked a bit weird. Not really blurry. But not fully clear, either. And the characters took more horizontal space than before the upgrade.
      Turned out this little visual glitches were a direct consequence of coming to Mint 19 all the way from Mint 17.1.
      On Mint 17.1, I had set all the system fonts to some variants of "DejaVu". From Mint 18.3 to Mint 19, the "DejaVu" fonts have been re-arranged, and my favourite system font is no longer named "DejaVu Sans".
      As a consequence, the system displayed all fonts, except 1, as "None" size 9 or "None" size 10, and used some "Sans" font.
      Solved the issue by selecting new favourite fonts via System Settings => Fonts. Issue resolved. - Hope there is not too much "Ubuntu" in my solution. :wink:

      Image
      (Sorry for the German screenshot, but prefixing "LC_ALL=C" to the command did not want to switch "Fonts" to English)
      .
    • Cleaning up obsolete software packages
      136 software packages were flagged as obsolete, no longer needed. They were removed by executing the command sudo apt-get autoremove

      Code: Select all

      Start-Date: 2018-09-28  20:26:06
      Commandline: apt-get autoremove
      Requested-By: karl
      Remove: 
      libpcre16-3:i386 (2:8.39-9)
      libgnutlsxx28:i386 (3.5.18-1ubuntu1)
      libmozjs-24-0v5:i386 (24.2.0-3ubuntu2.1)
      libisccfg140:i386 (1:9.10.3.dfsg.P4-8ubuntu1.11)
      libmsi0:i386 (0.97-1)
      libkadm5clnt-mit9:i386 (1.13.2+dfsg-5ubuntu2)
      libxapian-1.3-5:i386 (1.3.4-0ubuntu6)
      libtasn1-doc:i386 (4.13-2)
      gnupg-agent:i386 (2.2.4-1ubuntu1.1)
      libprotobuf-lite9v5:i386 (2.6.1-1.3)
      libgrilo-0.2-1:i386 (0.2.15-1)
      liblnk-utils:i386 (20171101-1)
      libsuitesparseconfig4.4.6:i386 (1:4.4.6-1)
      ruby2.3:i386 (2.3.1-2~16.04.10)
      libvncclient1:i386 (0.9.11+dfsg-1ubuntu1)
      libboost-filesystem1.58.0:i386 (1.58.0+dfsg-5ubuntu3.1)
      rename:i386 (0.20-7)
      libopencv-imgproc2.4v5:i386 (2.4.9.1+dfsg-1.5ubuntu1.1)
      libopencv-objdetect2.4v5:i386 (2.4.9.1+dfsg-1.5ubuntu1.1)
      libaprutil1:i386 (1.6.1-2)
      unixodbc:i386 (2.3.4-1.1ubuntu3)
      libavfilter-ffmpeg5:i386 (7:2.8.15-0ubuntu0.16.04.1)
      libraw15:i386 (0.17.1-1ubuntu0.3)
      liblouis9:i386 (2.6.4-2ubuntu0.3)
      mint-user-guide-cinnamon:i386 (18)
      libcapnp-0.5.3:i386 (0.5.3-2ubuntu1.1)
      libcapnp-0.6.1:i386 (0.6.1-1ubuntu1)
      libprotoc9v5:i386 (2.6.1-1.3)
      libasprintf0v5:i386 (0.19.8.1-6)
      libopencv-video2.4v5:i386 (2.4.9.1+dfsg-1.5ubuntu1.1)
      libumfpack5.7.1:i386 (1:4.4.6-1)
      libboost-date-time1.58.0:i386 (1.58.0+dfsg-5ubuntu3.1)
      libdleyna-connector-dbus-1.0-1:i386 (0.2.0-1)
      libcamd2.4.1:i386 (1:4.4.6-1)
      liblnk1:i386 (20171101-1)
      libccolamd2.9.1:i386 (1:4.4.6-1)
      libaprutil1-dbd-sqlite3:i386 (1.6.1-2)
      fonts-horai-umefont:i386 (670-2)
      libpython3.5:i386 (3.5.2-2ubuntu0~16.04.4)
      libboost-system1.58.0:i386 (1.58.0+dfsg-5ubuntu3.1)
      python3.5:i386 (3.5.2-2ubuntu0~16.04.4)
      libgmp-dev:i386 (2:6.1.2+dfsg-2)
      ruby-json:i386 (2.1.0+dfsg-2)
      mint-backgrounds-sarah:i386 (1.1)
      python3.5-minimal:i386 (3.5.2-2ubuntu0~16.04.4)
      fonts-unfonts-core:i386 (1:1.0.2-080608-14)
      libapache2-mod-dnssd:i386 (0.6-3.2)
      msitools:i386 (0.97-1)
      libmircore1:i386 (0.31.1-0ubuntu1)
      libgsf-1-114:i386 (1.14.41-2)
      python3.5-dev:i386 (3.5.2-2ubuntu0~16.04.4)
      libgmpxx4ldbl:i386 (2:6.1.2+dfsg-2)
      libprocps4:i386 (2:3.3.10-4ubuntu2.4)
      libopencv-flann2.4v5:i386 (2.4.9.1+dfsg-1.5ubuntu1.1)
      libopencv-contrib2.4v5:i386 (2.4.9.1+dfsg-1.5ubuntu1.1)
      libwebpdemux1:i386 (0.4.4-1)
      libopencv-highgui2.4v5:i386 (2.4.9.1+dfsg-1.5ubuntu1.1)
      python-ndg-httpsclient:i386 (0.4.4-1)
      libcolamd2.9.1:i386 (1:4.4.6-1)
      exe-thumbnailer:i386 (0.10.0-2)
      libical1a:i386 (1.0.1-0ubuntu2)
      libapr1:i386 (1.6.3-2)
      libopencv-photo2.4v5:i386 (2.4.9.1+dfsg-1.5ubuntu1.1)
      gist:i386 (4.6.1-1)
      nettle-dev:i386 (3.4-1)
      libaprutil1-ldap:i386 (1.6.1-2)
      libstdc++-5-dev:i386 (5.5.0-12ubuntu1)
      libgnome-desktop-3-12:i386 (3.18.2-1ubuntu1)
      libapparmor-perl:i386 (2.12-4ubuntu5)
      libmozjs-38-0:i386 (38.8.0~repack1-0ubuntu4)
      libebook-1.2-16:i386 (3.18.5-1ubuntu1.1)
      libmirprotobuf3:i386 (0.31.1-0ubuntu1)
      libass5:i386 (0.13.1-1)
      libpostproc-ffmpeg53:i386 (7:2.8.15-0ubuntu0.16.04.1)
      g++-5:i386 (5.5.0-12ubuntu1)
      libruby2.3:i386 (2.3.1-2~16.04.10)
      libblas-common:i386 (3.6.0-2ubuntu2)
      liblouisutdml6:i386 (2.5.0-3)
      libmirclient9:i386 (0.31.1-0ubuntu1)
      libquvi-scripts:i386 (0.4.21-2)
      libgsf-1-common:i386 (1.14.41-2)
      libamd2.4.1:i386 (1:4.4.6-1)
      python-ecdsa:i386 (0.13-2)
      dleyna-server:i386 (0.4.0-1.1)
      liblwres141:i386 (1:9.10.3.dfsg.P4-8ubuntu1.11)
      libp11-kit-dev:i386 (0.23.9-2)
      wine1.6-i386:i386 (1:1.8.4ubuntu1)
      libjpeg9:i386 (1:9b-2)
      gnome-exe-thumbnailer:i386 (0.10.0-2)
      libopencv-calib3d2.4v5:i386 (2.4.9.1+dfsg-1.5ubuntu1.1)
      libpython3.5-dev:i386 (3.5.2-2ubuntu0~16.04.4)
      libnma-common:i386 (1.2.6-0ubuntu0.16.04.4)
      libopencv-legacy2.4v5:i386 (2.4.9.1+dfsg-1.5ubuntu1.1)
      wine-gecko2.21:i386 (2.21-0ubuntu1)
      libwebrtc-audio-processing-0:i386 (0.1-3ubuntu1~gcc5.1)
      libdleyna-core-1.0-3:i386 (0.4.0-1)
      libtasn1-6-dev:i386 (4.13-2)
      libsodium18:i386 (1.0.8-5)
      libswscale-ffmpeg3:i386 (7:2.8.15-0ubuntu0.16.04.1)
      libdns162:i386 (1:9.10.3.dfsg.P4-8ubuntu1.11)
      libavresample-ffmpeg2:i386 (7:2.8.15-0ubuntu0.16.04.1)
      libxtables11:i386 (1.6.0-2ubuntu3)
      libopencv-core2.4v5:i386 (2.4.9.1+dfsg-1.5ubuntu1.1)
      libglew1.13:i386 (1.13.0-2)
      libbfio1:i386 (20170123-4)
      libdata-alias-perl:i386 (1.21-1)
      libbabeltrace-ctf1:i386 (1.5.5-1)
      libgupnp-dlna-2.0-3:i386 (0.10.5-3)
      apache2-bin:i386 (2.4.29-1ubuntu4.3)
      liblivemedia50:i386 (2016.02.09-1)
      libopencv-ml2.4v5:i386 (2.4.9.1+dfsg-1.5ubuntu1.1)
      wine-mono0.0.8:i386 (0.0.8-0ubuntu1)
      mint-backgrounds-sylvia:i386 (1.2)
      libavformat-ffmpeg56:i386 (7:2.8.15-0ubuntu0.16.04.1)
      libva-drm1:i386 (1.7.0-1ubuntu0.1)
      libpython3.5-stdlib:i386 (3.5.2-2ubuntu0~16.04.4)
      liborcus-0.10-0v5:i386 (0.9.2-4ubuntu2)
      libbind9-140:i386 (1:9.10.3.dfsg.P4-8ubuntu1.11)
      libboost-iostreams1.58.0:i386 (1.58.0+dfsg-5ubuntu3.1)
      libcamel-1.2-54:i386 (3.18.5-1ubuntu1.1)
      libopencv-features2d2.4v5:i386 (2.4.9.1+dfsg-1.5ubuntu1.1)
      python-setproctitle:i386 (1.1.10-1build2)
      libpython3.5-minimal:i386 (3.5.2-2ubuntu0~16.04.4)
      libpoppler58:i386 (0.41.0-0ubuntu1.8)
      libprotobuf9v5:i386 (2.6.1-1.3)
      libgupnp-av-1.0-2:i386 (0.12.10-1)
      libxapian22v5:i386 (1.2.22-2)
      libedataserver-1.2-21:i386 (3.18.5-1ubuntu1.1)
      libllvm3.6v5:i386 (1:3.6.2-3ubuntu2)
      libquvi7:i386 (0.4.1-3)
      libmircommon7:i386 (0.31.1-0ubuntu1)
      cgmanager:i386 (0.39-2ubuntu5)
      libidn11-dev:i386 (1.33-2.1ubuntu1)
      python3-pyasn1:i386 (0.4.2-3)
      libpanel-applet0:i386 (1:3.18.3-0ubuntu0.1)
      libcholmod3.0.6:i386 (1:4.4.6-1)
      End-Date: 2018-09-28  20:28:27
      
    • Re-adding PPA's removed by mintupgrade
      mintupgrade had removed 2 PPAs from the software sources: ppa:unit193/inxi, ppa:ubuntu-mozilla-security/ppa. They have been added back.

      Code: Select all

      sudo add-apt-repository ppa:unit193/inxi
      sudo add-apt-repository ppa:ubuntu-mozilla-security/ppa
      The software list has been refreshed.
      .
    • First software updates
      As expected Update Manager displayed some upgradable software packages, after the PPA's had been re-added and the software list refreshed. They have been installed.

      Code: Select all

      Commit Log for Fri Sep 28 19:55:05 2018
      
      The following packages have been upgraded:
      inxi (3.0.24-1-1~16.04) to 3.0.24-1-1~18.04
      thunderbird (1:60.0+build4-0ubuntu0.16.04.2) to 1:60.0+build4-0ubuntu0.18.04.4
      thunderbird-gnome-support (1:60.0+build4-0ubuntu0.16.04.2) to 1:60.0+build4-0ubuntu0.18.04.4
      thunderbird-locale-de (1:60.0+build4-0ubuntu0.16.04.2) to 1:60.0+build4-0ubuntu0.18.04.4
      thunderbird-locale-en (1:60.0+build4-0ubuntu0.16.04.2) to 1:60.0+build4-0ubuntu0.18.04.4
      thunderbird-locale-en-us (1:60.0+build4-0ubuntu0.16.04.2) to 1:60.0+build4-0ubuntu0.18.04.4
      
    • (more items to follow down below)
    --(the end for this week, no time to play around much during the next days)--
Last edited by karlchen on Sun Oct 14, 2018 12:01 pm, edited 1 time in total.
Image
The people of Alderaan have been bravely fighting back the clone warriors sent out by the unscrupulous Sith Lord Palpatine for 762 days now.
Lifeline
User avatar
Pjotr
Level 23
Level 23
Posts: 19883
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland) 🇳🇱
Contact:

Re: Upgrade from Mint 17.1 to Mint 19 in-place (experiment)

Post by Pjotr »

An experiment done and documented in the best German tradition of thoroughness (Gründlichkeit). Deutsche Wertarbeit! :)
Tip: 10 things to do after installing Linux Mint 21.3 Virginia
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.
User avatar
karlchen
Level 23
Level 23
Posts: 18173
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: Upgrade from Mint 17.1 to Mint 19 in-place (experiment)

Post by karlchen »

<The "Happy End" misunderstanding>

We all have watched one or two or more romantic movies like e.g. "Harry & Sally". They all follow the same pattern. After overcoming a lot of ups and downs and misunderstandings and obstacles, at the end of the movie, the two lovers celebrate their wedding; and this is the "Happy End".

Yet, we all know that the wedding is the "Happy End" by no means. Rather it is the start of a new chapter in life. This chapter may not be half as romantic in the long run. And it is not guaranteed to have another "Happy End" at some point in time. Very likely this is the reason, why romantic movies end where they end and do not tell what happens afterwards.

In a similar way, a lot of users will be glad and relieved that this thread about "Upgrading from Mint 17.1 to Mint 19 in-place" seemed to have reached its "Happy End" after two long weeks, when Mint 19 booted successfully after the in-place upgrade from 18.3 to 19.

Sorry to disappoint you, folks, but this was not the "Happy End". In the same way as smaller and bigger issues had to be fixed after each of the first 3 in-place upgrades, this aftercare work cannot be skipped after the final in-place upgrade either.
The previous post MintUpgrade to Mint 19 Aftercare and Troubleshooting already made this clear.

The aftercare work had only been interrupted for 2 weeks, because we had spent some days on the island of Tenerife. During our vacation, I did not have access to my desktop machines.

From now on there will be a few more posts reporting on issues resulting from the in-place upgrade to Mint 19 and on how they have been resolved. Hopefully I will not come across too many of them. At some point in time, this thread will simply fade away into oblivion, hopefully because all issues have been identified and resolved.

Summary:
Successfully rebooting the freshly upgraded Mint 19 was not the "Happy End". The story will go on for a short while. But definitely, it will not be like "The Walking Dead", which has just reached its 8th series in Germany, and no-one knows how many more series will follow. This thread will have an end. Promised.


</The "Happy End" misunderstanding>
Image
The people of Alderaan have been bravely fighting back the clone warriors sent out by the unscrupulous Sith Lord Palpatine for 762 days now.
Lifeline
User avatar
karlchen
Level 23
Level 23
Posts: 18173
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: Upgrade from Mint 17.1 to Mint 19 in-place (experiment)

Post by karlchen »

Step 4: Upgrade my Mint 18.3 to Mint 19.0 in-place using MintUpgrade 18.3.11
  • MintUpgrade to Mint 19 Aftercare and Troubleshooting (continued)
    • cgmanager left-over
      Stumbled across this thread, [Solved] cgmanager fails to start.
      Service cgmanager should no longer be present on Mint 19. Left over from Mint 18.x.

      Checked the status of service.cgmanager. Result:

      Code: Select all

      $ systemctl status cgmanager.service 
      ● cgmanager.service
         Loaded: masked (/dev/null; bad)
         Active: inactive (dead)
      Checked still installed cgmanager components:

      Code: Select all

      $ dpkg --list cgmanager libcgmanager* upstart
      +++-===========================-==================-==================-===========================================================
      rc  cgmanager                   0.39-2ubuntu5      i386               Central cgroup manager daemon
      ii  libcgmanager0:i386          0.39-2ubuntu5      i386               Central cgroup manager daemon (client library)
      ii  upstart                     1.13.2-0ubuntu21.1 i386               event-based init daemon - essential binaries
      Applied the solution from the linked thread.

      Code: Select all

      sudo systemctl stop cgmanager.service
      sudo systemctl disable cgmanager.service
      sudo apt-get purge upstart libcgmanager0 cgmanager
      sudo reboot
      Note: Terminated the first invocation of "apt-get purge" by replying "n(o)". Then used "apt-cache policy <package>" in order to check each package which "apt-get purge" wanted to delete. Each package did not have a repo attached any longer, i.e. really left behind by Mint 18.3.
      So invoked sudo apt-get purge upstart libcgmanager0 cgmanager a second time. This time agreed to remove the suggested packages.

      Code: Select all

      $ sudo apt-get purge upstart libcgmanager0 cgmanager
      Reading package lists... Done
      Building dependency tree       
      Reading state information... Done
      The following packages will be REMOVED:
        cgmanager* libcgmanager0* libsystemd-journal0* libsystemd-login0* upstart*
      0 upgraded, 0 newly installed, 5 to remove and 64 not upgraded.
      After this operation, 2152 kB disk space will be freed.
      Do you want to continue? [Y/n] y
      (Reading database ... 336880 files and directories currently installed.)
      Removing upstart (1.13.2-0ubuntu21.1) ...
      Removing libsystemd-login0:i386 (204-5ubuntu20.28) ...
      Removing libsystemd-journal0:i386 (204-5ubuntu20.28) ...
      Removing libcgmanager0:i386 (0.39-2ubuntu5) ...
      Processing triggers for libc-bin (2.27-3ubuntu1) ...
      Processing triggers for man-db (2.8.3-2) ...
      (Reading database ... 336792 files and directories currently installed.)
      Purging configuration files for libsystemd-login0:i386 (204-5ubuntu20.28) ...
      Purging configuration files for libsystemd-journal0:i386 (204-5ubuntu20.28) ...
      Purging configuration files for cgmanager (0.39-2ubuntu5) ...
      Purging configuration files for upstart (1.13.2-0ubuntu21.1) ...
      dpkg: warning: while removing upstart, directory '/var/log/upstart' not empty so not removed
      Processing triggers for ureadahead (0.100.0-20) ...
      ureadahead will be reprofiled on next reboot
      Processing triggers for systemd (237-3ubuntu10.3) ...
      Processing triggers for dbus (1.12.2-1ubuntu1) ...
      Going to reboot now ...
      Either will be back in a few minutes ... or ... my system will be dead. (time: 16:28 UTC)

      The system has come without any problems. (time: 16:31 UTC)
      (Had a "snack" break during the past 40 minutes. This is why it is 17:15 UTC now)

      Removed the no longer needed directory /Var/log/upstart including content (gzipped upstart logfiles)
      .
      .
    • More left behind software packages

      The case of the left-behind cgmanager and upstart packages reminded me that I had spotted a much longer list of left-behind software packages in Synaptic.
      Decided to get the complete list and go through it package by package.

      Sources to check whether a package is no longer needed or should be re-installed:
      • dpkg --list | grep "^rc" yields the list of all left-behind packages, which have not been uninstalled completely.
      • apt-cache policy <packagename> to determine whether no repo is given: very likely left-over by Mint 18.x
      • http://www.packages.linuxmint.com/list.php?release=Tara: if found here, very likely needs re-installation
      List of all left-behind packages

      Code: Select all

      dpkg --list | grep "^rc"
      rc  dleyna-server                                0.4.0-1.1                                   i386         DBus service to interact with DLNA Digital Media Servers
      rc  fonts-droid                                  1:4.3-3ubuntu1.2                            all          handheld device font with extensive style and language support
      rc  fonts-unfonts-core                           1:1.0.2-080608-14                           all          Un series Korean TrueType fonts
      rc  gnupg-agent                                  2.2.4-1ubuntu1.1                            all          GNU privacy guard - cryptographic agent (dummy transitional package)
      rc  libapache2-mod-dnssd                         0.6-3.2                                     i386         Zeroconf support for Apache 2 via avahi
      rc  libdleyna-core-1.0-3:i386                    0.4.0-1                                     i386         Utility functions for higher level dLeyna components
      rc  libdouble-conversion1v5:i386                 2.0.1-3ubuntu2                              i386         routines to convert IEEE floats to and from strings
      rc  libperl5.22:i386                             5.22.1-9ubuntu0.5                           i386         shared Perl library
      rc  libpython3.5-minimal:i386                    3.5.2-2ubuntu0~16.04.4                      i386         Minimal subset of the Python language (version 3.5)
      rc  libquvi7:i386                                0.4.1-3                                     i386         library for parsing video download links (runtime libraries)
      rc  libsane:i386                                 1.0.25+git20150528-1ubuntu2.16.04.1         i386         API library for scanners
      rc  libsidplay2v5                                2.1.1-14ubuntu2                             i386         SID (MOS 6581) emulation library
      rc  libvlccore8                                  2.2.2-5ubuntu0.16.04.4                      i386         base library for VLC and its modules
      rc  libwebrtc-audio-processing-0:i386            0.1-3ubuntu1~gcc5.1                         i386         AudioProcessing module from the WebRTC project.
      rc  mint-artwork-cinnamon                        5.7                                         all          Default artwork for the Cinnamon edition of Linux Mint
      rc  mint-artwork-common                          2.1.8.1                                     all          Common artwork for Linux Mint editions
      rc  mint-artwork-gnome                           2.6.49                                      all          Default artwork for Linux Mint
      rc  mint-artwork-xfce                            2017.12.13                                  all          Default artwork for Linux Mint
      rc  python3-aptdaemon.pkcompat                   1.1.1+bzr982-0ubuntu14                      all          PackageKit compatibilty for AptDaemon
      rc  python3.5-minimal                            3.5.2-2ubuntu0~16.04.4                      i386         Minimal subset of the Python language (version 3.5)
      rc  systemd-shim                                 9-1bzr4ubuntu1                              i386         shim for systemd
      rc  vlc-nox                                      2.2.2-5ubuntu0.16.04.4                      i386         multimedia player and streamer (without X support)
      Loop to display each package name one at a time and permit checking with "apt-cache policy" and on manually on package.linuxmint.com:

      Code: Select all

      for i in `dpkg --list | grep "^rc"| awk '{ print $2 }'`; do apt-cache policy $i; echo -e "Next \c" ; read answ; done
      Result:
      Potential candidate, which might have to be re-installed:
      + dleyna-server, libdleyna-core-1.0-3 (but decided against it at the moment)

      Conclusion:
      All listed package will be purged. Has been done using Synaptic.
Image
The people of Alderaan have been bravely fighting back the clone warriors sent out by the unscrupulous Sith Lord Palpatine for 762 days now.
Lifeline
User avatar
karlchen
Level 23
Level 23
Posts: 18173
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: Upgrade from Mint 17.1 to Mint 19 in-place (experiment)

Post by karlchen »

Step 4: Upgrade my Mint 18.3 to Mint 19.0 in-place using MintUpgrade 18.3.11
  • MintUpgrade to Mint 19 Aftercare and Troubleshooting (continued)
    • Second software update
      Merely the usual software update after 2 weeks of inactivity, offered by Update Manager.

      Code: Select all

      Commit Log for Sun Oct 14 20:08:50 2018
      
      The following packages have been updated:
      adobe-flash-properties-gtk (1:20180911.1-0ubuntu0.18.04.1) to 1:20181009.1-0ubuntu0.18.04.1
      adobe-flashplugin (1:20180911.1-0ubuntu0.18.04.1) to 1:20181009.1-0ubuntu0.18.04.1
      apparmor (2.12-4ubuntu5) to 2.12-4ubuntu5.1
      clamav (0.100.1+dfsg-1ubuntu0.18.04.3) to 0.100.2+dfsg-1ubuntu0.18.04.1
      clamav-base (0.100.1+dfsg-1ubuntu0.18.04.3) to 0.100.2+dfsg-1ubuntu0.18.04.1
      clamav-freshclam (0.100.1+dfsg-1ubuntu0.18.04.3) to 0.100.2+dfsg-1ubuntu0.18.04.1
      firefox (62.0+build2-0ubuntu0.18.04.5) to 62.0.3+build1-0ubuntu0.18.04.1
      firefox-locale-de (62.0+build2-0ubuntu0.18.04.5) to 62.0.3+build1-0ubuntu0.18.04.1
      firefox-locale-en (62.0+build2-0ubuntu0.18.04.5) to 62.0.3+build1-0ubuntu0.18.04.1
      flatpak (0.11.7-0ubuntu0.1) to 1.0.1-0ubuntu0.1
      ghostscript (9.22~dfsg+1-0ubuntu1.2) to 9.25~dfsg+1-0ubuntu0.18.04.1
      ghostscript-x (9.22~dfsg+1-0ubuntu1.2) to 9.25~dfsg+1-0ubuntu0.18.04.1
      gir1.2-flatpak-1.0 (0.11.7-0ubuntu0.1) to 1.0.1-0ubuntu0.1
      gir1.2-javascriptcoregtk-4.0 (2.20.5-0ubuntu0.18.04.1) to 2.22.2-0ubuntu0.18.04.2
      gir1.2-webkit2-4.0 (2.20.5-0ubuntu0.18.04.1) to 2.22.2-0ubuntu0.18.04.2
      grub-common (2.02-2ubuntu8.4) to 2.02-2ubuntu8.6
      grub-pc (2.02-2ubuntu8.4) to 2.02-2ubuntu8.6
      grub-pc-bin (2.02-2ubuntu8.4) to 2.02-2ubuntu8.6
      grub2-common (2.02-2ubuntu8.4) to 2.02-2ubuntu8.6
      imagemagick (8:6.9.7.4+dfsg-16ubuntu6.3) to 8:6.9.7.4+dfsg-16ubuntu6.4
      imagemagick-6-common (8:6.9.7.4+dfsg-16ubuntu6.3) to 8:6.9.7.4+dfsg-16ubuntu6.4
      imagemagick-6.q16 (8:6.9.7.4+dfsg-16ubuntu6.3) to 8:6.9.7.4+dfsg-16ubuntu6.4
      imagemagick-common (8:6.9.7.4+dfsg-16ubuntu6.3) to 8:6.9.7.4+dfsg-16ubuntu6.4
      initramfs-tools (0.130ubuntu3.3) to 0.130ubuntu3.5
      initramfs-tools-bin (0.130ubuntu3.3) to 0.130ubuntu3.5
      initramfs-tools-core (0.130ubuntu3.3) to 0.130ubuntu3.5
      inxi (3.0.24-1-1~18.04) to 3.0.26-1-1~18.04
      libapparmor1 (2.12-4ubuntu5) to 2.12-4ubuntu5.1
      libbrotli1 (1.0.3-1ubuntu1) to 1.0.3-1ubuntu1.2
      libclamav7 (0.100.1+dfsg-1ubuntu0.18.04.3) to 0.100.2+dfsg-1ubuntu0.18.04.1
      libflatpak0 (0.11.7-0ubuntu0.1) to 1.0.1-0ubuntu0.1
      libgs9 (9.22~dfsg+1-0ubuntu1.2) to 9.25~dfsg+1-0ubuntu0.18.04.1
      libgs9-common (9.22~dfsg+1-0ubuntu1.2) to 9.25~dfsg+1-0ubuntu0.18.04.1
      libjavascriptcoregtk-4.0-18 (2.20.5-0ubuntu0.18.04.1) to 2.22.2-0ubuntu0.18.04.2
      libkpathsea6 (2017.20170613.44572-8build1) to 2017.20170613.44572-8ubuntu0.1
      liblouis-data (3.5.0-1ubuntu0.2) to 3.5.0-1ubuntu0.3
      liblouis14 (3.5.0-1ubuntu0.2) to 3.5.0-1ubuntu0.3
      libmagickcore-6.q16-3 (8:6.9.7.4+dfsg-16ubuntu6.3) to 8:6.9.7.4+dfsg-16ubuntu6.4
      libmagickcore-6.q16-3-extra (8:6.9.7.4+dfsg-16ubuntu6.3) to 8:6.9.7.4+dfsg-16ubuntu6.4
      libmagickwand-6.q16-3 (8:6.9.7.4+dfsg-16ubuntu6.3) to 8:6.9.7.4+dfsg-16ubuntu6.4
      libmetacity1 (1:3.28.0-1) to 1:3.28.0-1ubuntu0.1
      libostree-1-1 (2018.4-2) to 2018.8-0ubuntu0.1
      libplymouth4 (0.9.3-1ubuntu7) to 0.9.3-1ubuntu7.18.04.1
      libwebkit2gtk-4.0-37 (2.20.5-0ubuntu0.18.04.1) to 2.22.2-0ubuntu0.18.04.2
      libwebkit2gtk-4.0-37-gtk2 (2.20.5-0ubuntu0.18.04.1) to 2.22.2-0ubuntu0.18.04.2
      libwoff1 (1.0.2-1) to 1.0.2-1build0.1
      linux-generic (4.15.0.34.36) to 4.15.0.36.38
      linux-headers-generic (4.15.0.34.36) to 4.15.0.36.38
      linux-image-generic (4.15.0.34.36) to 4.15.0.36.38
      linux-libc-dev (4.15.0-34.37) to 4.15.0-36.39
      metacity (1:3.28.0-1) to 1:3.28.0-1ubuntu0.1
      metacity-common (1:3.28.0-1) to 1:3.28.0-1ubuntu0.1
      plymouth (0.9.3-1ubuntu7) to 0.9.3-1ubuntu7.18.04.1
      plymouth-label (0.9.3-1ubuntu7) to 0.9.3-1ubuntu7.18.04.1
      plymouth-theme-ubuntu-text (0.9.3-1ubuntu7) to 0.9.3-1ubuntu7.18.04.1
      python3-louis (3.5.0-1ubuntu0.2) to 3.5.0-1ubuntu0.3
      python3-update-manager (1:18.04.11.4) to 1:18.04.11.5
      thunderbird (1:60.0+build4-0ubuntu0.18.04.4) to 1:60.2.1+build1-0ubuntu0.18.04.2
      thunderbird-gnome-support (1:60.0+build4-0ubuntu0.18.04.4) to 1:60.2.1+build1-0ubuntu0.18.04.2
      thunderbird-locale-de (1:60.0+build4-0ubuntu0.18.04.4) to 1:60.2.1+build1-0ubuntu0.18.04.2
      thunderbird-locale-en (1:60.0+build4-0ubuntu0.18.04.4) to 1:60.2.1+build1-0ubuntu0.18.04.2
      thunderbird-locale-en-us (1:60.0+build4-0ubuntu0.18.04.4) to 1:60.2.1+build1-0ubuntu0.18.04.2
      ubuntu-drivers-common (1:0.5.2) to 1:0.5.2.1
      update-manager-core (1:18.04.11.4) to 1:18.04.11.5
      
      The following packages have been installed:
      linux-headers-4.15.0-36 (4.15.0-36.39)
      linux-headers-4.15.0-36-generic (4.15.0-36.39)
      linux-image-4.15.0-36-generic (4.15.0-36.39)
      linux-modules-4.15.0-36-generic (4.15.0-36.39)
      linux-modules-extra-4.15.0-36-generic (4.15.0-36.39)
      Result:

      Code: Select all

      $ inxi -Sxxx
      System:    Host: unimatrix0 Kernel: 4.15.0-36-generic i686 bits: 32 compiler: gcc v: 7.3.0 
                 Desktop: Cinnamon 3.8.9 wm: muffin dm: LightDM 1.26.0 Distro: Linux Mint 19 Tara 
                 base: Ubuntu 18.04 bionic 
    • Uninstalling obsolete kernel series 4.4.0-xx
      Kernel 4.4.0-135 had been left behind. It has been uninstalled completely. Kernel series 4.4.0-xx is of no use on Mint 19.

      Code: Select all

      Commit Log for Sun Oct 14 21:44:26 2018
      
      The following packages have been purged:
      linux-headers-4.4.0-135
      linux-headers-4.4.0-135-generic
      linux-image-4.4.0-135-generic
      linux-image-extra-4.4.0-135-generic
      Result:

      Code: Select all

      $ ls -l /boot/init* /boot/vmlinuz*
      -rw-r--r-- 1 root root 55114164 Okt 14 20:40 /boot/initrd.img-4.15.0-34-generic
      -rw-r--r-- 1 root root 55110214 Okt 14 20:41 /boot/initrd.img-4.15.0-36-generic
      -rw------- 1 root root  7539696 Aug 27 16:45 /boot/vmlinuz-4.15.0-34-generic
      -rw------- 1 root root  7545648 Sep 24 16:08 /boot/vmlinuz-4.15.0-36-generic
    ---(the end for today)---
Image
The people of Alderaan have been bravely fighting back the clone warriors sent out by the unscrupulous Sith Lord Palpatine for 762 days now.
Lifeline
User avatar
karlchen
Level 23
Level 23
Posts: 18173
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: Upgrade from Mint 17.1 to Mint 19 in-place (experiment)

Post by karlchen »

Step 4: Upgrade my Mint 18.3 to Mint 19.0 in-place using MintUpgrade 18.3.11
  • MintUpgrade to Mint 19 Aftercare and Troubleshooting (continued)
    • HP Colour Laserjet & Scanner no longer fully functional
      Did we not have a similar issue before? This time the printer prints double-sided, but the scanner device interface mysteriously got lost.
      Seems to be an issue which is likely to return on each release upgrade, minor or major.
      Cf. Problems encountered and solved after upgrading to Mint 18.3.
      This time resolving the issue was extremely smooth:
      When Simple Scan tried to access the scanner device, an error message popped up alerting that the device could not be accessed.
      Without any further intervention another popup dialogue appeared on the screen offering to download the needed HP scanner plugin.
      Accepted. Downloaded. Installed.
      Result: Simple Scan works. I.e. scanner functional again. :D
    ---(the end for today)---
Image
The people of Alderaan have been bravely fighting back the clone warriors sent out by the unscrupulous Sith Lord Palpatine for 762 days now.
Lifeline
User avatar
karlchen
Level 23
Level 23
Posts: 18173
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: Upgrade from Mint 17.1 to Mint 19 in-place (epilogue)

Post by karlchen »

Epilogue

Considering the "Upgrade from Mint 17.1 to Mint 19 in-place" a success. The system is up and running. No hint something fundamental might be wrong. The system works as well as it had done in its initial incarnations as Mint 17.0 Qiana and as Mint 17.1 Rebecca.
Both desktop environments seem to work correctly, Cinnamon and xfce. Switching between them at login time works flawlessly.

Let me close the story by giving you the startup times as determined by systemd-analyze on this machine, when booted into
+ Linux Mint 19 Tara xfce + Cinnamon
+ Ubuntu 18.04.1 Mate
+ Linux Mint 18.1 xfce
  • Linux Mint 19 Tara xfce + Cinnamon
    Linux Mint 19 Tara xfce

    Code: Select all

    karl@unimatrix0 ~ $ inxi -Sxxx
    System:    Host: unimatrix0 Kernel: 4.15.0-36-generic i686 bits: 32 compiler: gcc v: 7.3.0 Desktop: Xfce 4.12.3 
               tk: Gtk 2.24.31 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 Distro: Linux Mint 19 Tara base: Ubuntu 18.04 bionic 
    karl@unimatrix0 ~ $ systemd-analyze
    Startup finished in 8.986s (kernel) + 58.166s (userspace) = 1min 7.153s
    graphical.target reached after 55.264s in userspace
    Linux Mint 19 Tara Cinnamon

    Code: Select all

    karl@unimatrix0 ~ $ inxi -Sxxx
    System:    Host: unimatrix0 Kernel: 4.15.0-36-generic i686 bits: 32 compiler: gcc v: 7.3.0 Desktop: Cinnamon 3.8.9 wm: muffin 
               dm: LightDM 1.26.0 Distro: Linux Mint 19 Tara base: Ubuntu 18.04 bionic 
    karl@unimatrix0 ~ $ systemd-analyze
    Startup finished in 8.997s (kernel) + 1min 52.279s (userspace) = 2min 1.276s
    graphical.target reached after 53.918s in userspace
    karl@unimatrix0 ~ $
  • Ubuntu 18.04.1 Mate

    Code: Select all

    karl@unimatrix0:~$ inxi -Sxxx
    System:    Host: unimatrix0 Kernel: 4.15.0-36-generic i686 bits: 32 compiler: gcc v: 7.3.0 Desktop: MATE 1.20.1 
               info: mate-panel wm: marco 1.20.1 dm: LightDM 1.26.0 Distro: Ubuntu 18.04.1 LTS (Bionic Beaver)
    karl@unimatrix0:~$ systemd-analyze
    Startup finished in 8.711s (kernel) + 1min 32.649s (userspace) = 1min 41.361s
    graphical.target reached after 39.468s in userspace
    karl@unimatrix0:~$
  • Linux Mint 18.1 xfce

    Code: Select all

    karl@unimatrix0 ~ $ inxi -Sxxx
    System:    Host: unimatrix0 Kernel: 4.4.0-138-generic i686 bits: 32 compiler: gcc v: 5.4.0 Desktop: Xfce 4.12.3 
               tk: Gtk 2.24.28 info: xfce4-panel wm: xfwm4 dm: MDM Distro: Linux Mint 18.1 Serena base: Ubuntu 16.04 xenial 
    karl@unimatrix0 ~ $ systemd-analyze
    Startup finished in 9.143s (kernel) + 34.273s (userspace) = 43.417s
    karl@unimatrix0 ~ $ 
    Note:
    To me it looks as if "systemd-analyze" on Mint 18.x only calculates the time, till the graphical.target has been reached (login screen displayed), whereas on Mint 19 and on Ubuntu 18.04 it seems to calculate the time, too, which it takes to load the DE after the login has been completed.
{ The End }
Last edited by karlchen on Sun Oct 28, 2018 7:14 am, edited 5 times in total.
Reason: added Mint 18.1 "systemd-analyze" time and a note on different ways of calculating the startup time: without DE loading (Mint 18.1) vs with DE loading (Mint 19); added "systemd-analyze" time for Mint 19 Cinnamon
Image
The people of Alderaan have been bravely fighting back the clone warriors sent out by the unscrupulous Sith Lord Palpatine for 762 days now.
Lifeline
michael louwe

Re: Upgrade from Mint 17.1 to Mint 19 in-place (experiment)

Post by michael louwe »

karlchen wrote: Sun Oct 21, 2018 2:38 pm Considering the "Upgrade from Mint 17.1 to Mint 19 in-place" a success.
.
Thank you for your efforts.

Seems to require tech-geeks to handle the inplace upgrades, especially for "Aftercare and Troubleshooting". IOW, newbies/novices should not do them and instead do clean installs to upgrade.
HaveaMint
Level 6
Level 6
Posts: 1088
Joined: Fri Feb 02, 2018 9:56 pm

Re: Upgrade from Mint 17.1 to Mint 19 in-place (experiment)

Post by HaveaMint »

The result of this exercise was;
Main cat moved outside to get some sleep.
sleeping.jpg
The kitten felt neglected;
neglected.jpg
One cat committed suicide.

suicide.jpg
"Tune for maximum Smoke and then read the Instructions".
User avatar
karlchen
Level 23
Level 23
Posts: 18173
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: Upgrade from Mint 17.1 to Mint 19 in-place (experiment)

Post by karlchen »

Statement under oath:
No cats have been harmed in the course of this exercise. :D

I would have expected the result of this exercise to be ...
+ Clem has decided to join a monastery.
+ The forum newbies feel completely neglected.
+ Two third of the experienced forum users have died from boredom.
Image
The people of Alderaan have been bravely fighting back the clone warriors sent out by the unscrupulous Sith Lord Palpatine for 762 days now.
Lifeline
User avatar
majpooper
Level 8
Level 8
Posts: 2084
Joined: Thu May 09, 2013 1:56 pm
Location: North Carolina, USA

Re: Upgrade from Mint 17.1 to Mint 19 in-place (experiment)

Post by majpooper »

Actually I think most found it an interesting exercise and followed along. I think the Devs could glean some insight as well.
Personally I just prefer a fresh install but get it that there are users, like the folks that I have installed Mint for and support that a seamless point and click upgrade would be fantastic for them and for me. I have at least 8 to 10 upgrades to accomplish prior to Apr 19. I have started on my own machines to gain some experience with 19 - all seems just fine no real issues. What worries me is a few folks that I have helped are running really old hardware and of course these are the people that struggle with computers and anything that appears the least bit different like a new version of the OS let alone a different OS and/or DE.
Locked

Return to “Chat about Linux Mint”