[Solved] Warning: In-place upgrade from Mint 18.3 to Mint 19 partially broken by a Mesa Update

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read how to get help
User avatar
karlchen
Level 19
Level 19
Posts: 9080
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

[Solved] Warning: In-place upgrade from Mint 18.3 to Mint 19 partially broken by a Mesa Update

Post by karlchen » Sat Jul 07, 2018 1:55 pm

There is news that the reported problem should no longer occur from today onwards:
Clem wrote: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
The warning below is obsolete.
~~~ ~~~ ~~~
Warning:
The In-place upgrade process from Mint 18.3 to Mint 19 is currently partially broken by a Mesa Update, which has been deployed to Ubuntu 16.04 / Mint18.x.

Please, read Clem's 2 posts here:
Affected Mint users:
Those Mint users who tried / try to upgrade from Mint 18.3 to Mint 19 by following Clem's instruction on "How to upgrade to Linux Mint 19", and whose Mint 18.3 has received the Mesa update Mesa 18.0.5.

Unaffected Mint users:
All those Mint users, who install Mint 19 from the Mint 19 live system.

Affected or not affected?
In case you are unsure whether you have been hit by this problem, after having read Clem's 2 posts carefully, here is a quick way to find out:
Execute the terminal commandline

Code: Select all

dpkg --list libegl1-mesa libgbm1 libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libgles2-mesa libosmesa6 libwayland-egl1-mesa
It will display a list of mesa related library packages.
In case you spot the version string "18.0.5" on your Mint 19 system, then you have been hit by the problem, which Clem has explained in detail in his 2 posts.
Last edited by karlchen on Mon Jul 09, 2018 3:09 pm, edited 1 time in total.
Reason: Prefixed Clem's blog post informing that the issue has been resolved. Marked the thread as [solved]. Thread no longer sticky.
Image
Old bugs good, new bugs bad! Updates are evil: might fix old bugs and introduce no new ones.

User avatar
Flemur
Level 15
Level 15
Posts: 5929
Joined: Mon Aug 20, 2012 9:41 pm
Location: Potemkin Village

Re: Warning: In-place upgrade from Mint 18.3 to Mint 19 partially broken by a Mesa Update

Post by Flemur » Sat Jul 07, 2018 3:01 pm

karlchen wrote:
Sat Jul 07, 2018 1:55 pm
Affected Mint users:
Those Mint users who tried / try to upgrade from Mint 18.3 to Mint 19 by following Clem's instruction on "How to upgrade to Linux Mint 19", and whose Mint 18.3 has received the Mesa update Mesa 18.0.5.
I upgraded 18.3 to 19 with Clem's instructions, no problems, and I have *some* v18.0.5 mesa stuff though most is v18.0.0.

Now, running in Mint 19, I get

Code: Select all

$ sudo apt-get upgrade
...
The following packages have been kept back:
  libegl1-mesa libgbm1 libgl1-mesa-dev libgl1-mesa-glx:i386 libgl1-mesa-glx libglapi-mesa:i386 libglapi-mesa libgles2-mesa
  libwayland-egl1-mesa mesa-common-dev
but other than that, no issues.

These are the 18.0.5 packages, about 8 to 10 other "*mesa*" packages are 18.0.0:

Code: Select all

ii  libgl1-mesa-dri:amd64      18.0.5-0ubuntu0~16 amd64 
ii  libgl1-mesa-dri:i386       18.0.5-0ubuntu0~16 i386   
Please edit your original post title to include [SOLVED] if/when it is solved!
Your data and OS are backed up....right?
Mint 18.3 Xfce/fluxbox/pulse-less
Xubuntu 17.10/fluxbox/pulse-less

gm10
Level 7
Level 7
Posts: 1675
Joined: Thu Jun 21, 2018 5:11 pm

Re: Warning: In-place upgrade from Mint 18.3 to Mint 19 partially broken by a Mesa Update

Post by gm10 » Sat Jul 07, 2018 4:05 pm

Flemur wrote:
Sat Jul 07, 2018 3:01 pm
These are the 18.0.5 packages, about 8 to 10 other "*mesa*" packages are 18.0.0:

Code: Select all

ii  libgl1-mesa-dri:amd64      18.0.5-0ubuntu0~16 amd64 
ii  libgl1-mesa-dri:i386       18.0.5-0ubuntu0~16 i386   
Just reinstall them and it will pull the 18.0.0 versions from the bionic repo.

User avatar
Flemur
Level 15
Level 15
Posts: 5929
Joined: Mon Aug 20, 2012 9:41 pm
Location: Potemkin Village

Re: Warning: In-place upgrade from Mint 18.3 to Mint 19 partially broken by a Mesa Update

Post by Flemur » Sat Jul 07, 2018 4:26 pm

gm10 wrote:
Sat Jul 07, 2018 4:05 pm
Flemur wrote:
Sat Jul 07, 2018 3:01 pm
These are the 18.0.5 packages, about 8 to 10 other "*mesa*" packages are 18.0.0:

Code: Select all

ii  libgl1-mesa-dri:amd64      18.0.5-0ubuntu0~16 amd64 
ii  libgl1-mesa-dri:i386       18.0.5-0ubuntu0~16 i386   
Just reinstall them and it will pull the 18.0.0 versions from the bionic repo.
???

Code: Select all

sudo apt-get install libgl1-mesa-dri:amd64 --reinstall
sudo apt-get install libgl1-mesa-dri:i386 --reinstall
sudo apt-get install libgles1-mesa --reinstall
(no errors or warnings)

Code: Select all

$  dpkg -l "*mesa*" | grep 18.0.5
ii  libgl1-mesa-dri:amd64      18.0.5-0ubuntu0~16.04.1 amd64    ...
ii  libgl1-mesa-dri:i386       18.0.5-0ubuntu0~16.04.1 i386     ...
ii  libgles1-mesa              18.0.5-0ubuntu0~16.04.1 all    
Please edit your original post title to include [SOLVED] if/when it is solved!
Your data and OS are backed up....right?
Mint 18.3 Xfce/fluxbox/pulse-less
Xubuntu 17.10/fluxbox/pulse-less

User avatar
karlchen
Level 19
Level 19
Posts: 9080
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: Warning: In-place upgrade from Mint 18.3 to Mint 19 partially broken by a Mesa Update

Post by karlchen » Sat Jul 07, 2018 4:41 pm

Hi, Flemur.

The result of trying to re-install mesa confirms what Clem had explained. The Ubuntu 16.04 / Mint 18.3 mesa version 18.0.5 is higher than the Ubuntu 18.04 / Mint 19 mesa version 18.0.0rc5. apt will not downgrade 18.0.5 to 18.0.0rc5. This in turn leads to further errors and kept Ubuntu 16.04 packages or the removal of needed packages.
If I remember right, you change the window manager and the desktop environment, which come with Mint by default, to some alternative window manager and desktop environment. If this applied to your previous Mint 18.3 as well, which you upgraded to Mint 19, then you may see slightly different symptoms on your current Mint 19 from users who upgrade a stock Mint 18.3 to Mint 19.

Regards,
Karl
Image
Old bugs good, new bugs bad! Updates are evil: might fix old bugs and introduce no new ones.

gm10
Level 7
Level 7
Posts: 1675
Joined: Thu Jun 21, 2018 5:11 pm

Re: Warning: In-place upgrade from Mint 18.3 to Mint 19 partially broken by a Mesa Update

Post by gm10 » Sat Jul 07, 2018 4:43 pm

Flemur wrote:
Sat Jul 07, 2018 4:26 pm
???
My bad, reinstall was a bad choice words. Try this:

Code: Select all

apt install libgl1-mesa-dri:amd64=18.0.0~rc5-1ubuntu1
apt install libgl1-mesa-dri:i386=18.0.0~rc5-1ubuntu1
The other one doesn't seem to exist in the repo so just remove it.

JeremyB
Level 18
Level 18
Posts: 8854
Joined: Fri Feb 21, 2014 8:17 am

Re: Warning: In-place upgrade from Mint 18.3 to Mint 19 partially broken by a Mesa Update

Post by JeremyB » Sat Jul 07, 2018 4:45 pm

gm10 wrote:
Sat Jul 07, 2018 4:43 pm
Flemur wrote:
Sat Jul 07, 2018 4:26 pm
???
My bad, reinstall was a bad choice words. Try this:

Code: Select all

apt install libgl1-mesa-dri:amd64=18.0.0~rc5-1ubuntu1
apt install libgl1-mesa-dri:i386=18.0.0~rc5-1ubuntu1
The other one doesn't seem to exist in the repo so just remove it.
You actually need to fix the version in Linux Mint 18

If people could wait a week or so, Ubuntu might get this fixed as the newer mesa packages are in testing bionic-proposed repos now

gm10
Level 7
Level 7
Posts: 1675
Joined: Thu Jun 21, 2018 5:11 pm

Re: Warning: In-place upgrade from Mint 18.3 to Mint 19 partially broken by a Mesa Update

Post by gm10 » Sat Jul 07, 2018 4:59 pm

JeremyB wrote:
Sat Jul 07, 2018 4:45 pm
You actually need to fix the version in Linux Mint 18

If people could wait a week or so, Ubuntu might get this fixed as the newer mesa packages are in testing bionic-proposed repos now
I agree, but that won't help him now since he's already arrived on 19.

And yes, I know:

Code: Select all

$ apt list libgl1-mesa-dri -a
Listing... Done
libgl1-mesa-dri/bionic-proposed 18.0.5-0ubuntu0~18.04.1 amd64
libgl1-mesa-dri/bionic,now 18.0.0~rc5-1ubuntu1 amd64 [installed]

JeremyB
Level 18
Level 18
Posts: 8854
Joined: Fri Feb 21, 2014 8:17 am

Re: Warning: In-place upgrade from Mint 18.3 to Mint 19 partially broken by a Mesa Update

Post by JeremyB » Sat Jul 07, 2018 5:05 pm

I guess they could enable bionic proposed and just update the mesa packages

gm10
Level 7
Level 7
Posts: 1675
Joined: Thu Jun 21, 2018 5:11 pm

Re: Warning: In-place upgrade from Mint 18.3 to Mint 19 partially broken by a Mesa Update

Post by gm10 » Sat Jul 07, 2018 5:07 pm

JeremyB wrote:
Sat Jul 07, 2018 5:05 pm
I guess they could enable bionic proposed and just update the mesa packages
If you script it, sure, otherwise you just know they'll update everything from that repo and invariably run into issues. ;)

Seems easier to me to change the mintupgrade script to downgrade on 18 instead (for now).

User avatar
karlchen
Level 19
Level 19
Posts: 9080
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: Warning: In-place upgrade from Mint 18.3 to Mint 19 partially broken by a Mesa Update

Post by karlchen » Sat Jul 07, 2018 5:13 pm

If you read Clem's second post carefully, you will notice that Clem mentions the destructive side-effects which result from the problem that the mesa version 18.0.5 does not match the expected version on Mint 19. A number of needed libraries and needed software packages will even be uninstalled.
Now that the damage has been done it will not be sufficient to install the right mesa version. It will be necessary to identify all consequences which have resulted from this single first problem.
This is why Clem suggests to go back to Mint 18.3 by restoring with the help of timeshift. And it will be necessary to go back to a point in time when on Mint 18.3 mesa had not been updated to 18.0.5.
Only if this has been done, it makes sense trying mintupgrade again. Because now the mesa conflict will not occur. And mintupgrade has got a chance of completing the in-place upgrade correctly.
Image
Old bugs good, new bugs bad! Updates are evil: might fix old bugs and introduce no new ones.

User avatar
clem
Level 12
Level 12
Posts: 4067
Joined: Wed Nov 15, 2006 8:34 am
Contact:

Re: Warning: In-place upgrade from Mint 18.3 to Mint 19 partially broken by a Mesa Update

Post by clem » Sun Jul 08, 2018 4:32 am

mesa 18.0.5 is currently in bionic-proposed.

https://www.ubuntuupdates.org/pm/mesa
Image

drakend
Level 1
Level 1
Posts: 5
Joined: Tue Dec 05, 2017 9:36 am

Re: Warning: In-place upgrade from Mint 18.3 to Mint 19 partially broken by a Mesa Update

Post by drakend » Mon Jul 09, 2018 7:47 am

Hello,
an hour ago I updated the mintupgrade application. I was affected by the mesa issue and in fact I was stopped by the check in the application. Now if I digit

Code: Select all

mintupgrade check
the simulation of the installation goes fine.
There hasn't been any update on the mesa driver/library/whatever part, so how can this be possible? Did the Linux Mint cool boys invent some kind of trick or whatever?

User avatar
smurphos
Level 6
Level 6
Posts: 1166
Joined: Fri Sep 05, 2014 12:18 am
Location: Britisher...

Re: Warning: In-place upgrade from Mint 18.3 to Mint 19 partially broken by a Mesa Update

Post by smurphos » Mon Jul 09, 2018 7:53 am

The Bionic (Mint 19) Mesa update has come through this morning that should fix the issue - i.e. Xenial (Mint 18.3) Mesa is no longer a higher version than Bionic Mesa.

User avatar
MtnDewManiac
Level 6
Level 6
Posts: 1351
Joined: Fri Feb 22, 2013 5:18 pm
Location: United States

Re: [Solved] Warning: In-place upgrade from Mint 18.3 to Mint 19 partially broken by a Mesa Update

Post by MtnDewManiac » Tue Jul 10, 2018 7:41 pm

I am glad to read that this issue has likely been resolved (or is at least very nearly so, if everything hasn't "trickled down" yet).

However, I am rather disappointed in the forum staff. Unless I missed it (possible), this thread was at no time set to be a site-wide "announcement" thread. And this appears to have been a very serious issue. Although my understanding of said issue is both very slight and incomplete, I do distinctly remember reading a post that stated this issue could end up causing the removal/uninstallation of many things on a user's computer - which means that a simple "fixing of the broken part" would, for many people (potentially, at least), merely correct the cause of their issues at that point; it wouldn't, then, fix all of the resulting issues on their systems.

In short, this wasn't something mild(?), like something that prevented people's computers from updating - or even from booting - would. It could, in fact, potentially be a show-stopper for some. And, yet, we had this thread and some on-site links from a few other threads pointing to it.

All it would have taken would have been a staff member setting the flag on this thread that made it an "announcement" thread, and it would have appeared at the top of every sub-forum here.

That should have been done. Yes, this is arguably my opinion. But I would assume that many other people would feel the same way if they thought about it.

Someone on the staff should have thought of it.

As for the issue itself... Regrettably, these things happen from time to time. It was an "upstream" issue, and I doubt that anyone really blames the Mint developers or the staff at the forum for it. However, after the issue became known to the developers and forum staff... I find myself wondering how many people, out of the percentage of people who were affected by it from that point onward, feel that there is some blame due to the fact that those individuals did not expend every reasonable effort in attempting to minimize it.

And I wonder if there is some truth to that. Do said individuals (Mint developers AND forum staff) have a level of responsibility, when dealing with issues of this significance, that is greater than that of a "regular Mint user" does? I believe so. Otherwise, why are they here?

Regards,
MDM
Mint 18 Xfce 4.12.

If guns kill people, then pencils misspell words, cars make people drive drunk, and spoons made Rosie O'Donnell fat.

User avatar
karlchen
Level 19
Level 19
Posts: 9080
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: [Solved] Warning: In-place upgrade from Mint 18.3 to Mint 19 partially broken by a Mesa Update

Post by karlchen » Wed Jul 11, 2018 5:45 am

Hi, MDM.

This thread had been stickied here in "Installation & Boot" between Saturday (07 Jul 2018 19:55 CEST) and Monday (09 Jul 2018 21:09 CEST), when news was spread that the issue had been resolved. So this thread had been on top in this sub-forum.
Yet, more important, Clem had quickly implemented an emergency stop into mintupgrade, which would be triggered whenever mintupgrade found mesa 18.0.5 on a Mint 18.3 system.
This emergency exit will have prevented more failed in-place upgrades from Mint 18.3 to Mint 19 over the weekend, than a forum wide announcement would have done.
Remember: this thread had been stickied, just not forum-wide.

Regards,
Karl
Last edited by karlchen on Wed Jul 11, 2018 7:14 am, edited 1 time in total.
Reason: added exact times when thread had been created & stickied, Saturday 07 Jul 2018 19:55 CEST, and unstickied again, Monday 09 Jul 2018 21:09 CEST
Image
Old bugs good, new bugs bad! Updates are evil: might fix old bugs and introduce no new ones.

gm10
Level 7
Level 7
Posts: 1675
Joined: Thu Jun 21, 2018 5:11 pm

Re: [Solved] Warning: In-place upgrade from Mint 18.3 to Mint 19 partially broken by a Mesa Update

Post by gm10 » Wed Jul 11, 2018 5:56 am

karlchen wrote:
Wed Jul 11, 2018 5:45 am
Yet, more important, Clem had quickly implemented an emergency stop into mintupgrade, which would be triggered whenever mintupgrade found mesa 18.0.5 on a Mint 18.3 system.
This emergency exit will have prevented more failed in-place upgrades from Mint 18.3 to Mint 19 over the weekend, than a forum wide announcement would have done.
Yes and no. Remember that most users will use local mirrors, and those can take a long time to sync. See Ubuntu's nice overview for their mirrors as an example: https://launchpad.net/ubuntu/+archivemirrors (I don't think there is one for Mint mirrors, is there?).

So just because Clem fixed something quickly doesn't mean that users aren't still getting the unfixed version the following weekend.

User avatar
karlchen
Level 19
Level 19
Posts: 9080
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: [Solved] Warning: In-place upgrade from Mint 18.3 to Mint 19 partially broken by a Mesa Update

Post by karlchen » Wed Jul 11, 2018 6:53 am

Hm. Maybe when making that warning post sticky 07 Jul 2018 19:55 CEST, I made the wrong choice by making it sticky in "Installation & Boot" only and by not making it a global announcement.
Image
Old bugs good, new bugs bad! Updates are evil: might fix old bugs and introduce no new ones.

User avatar
MtnDewManiac
Level 6
Level 6
Posts: 1351
Joined: Fri Feb 22, 2013 5:18 pm
Location: United States

Re: [Solved] Warning: In-place upgrade from Mint 18.3 to Mint 19 partially broken by a Mesa Update

Post by MtnDewManiac » Wed Jul 11, 2018 11:58 am

karlchen wrote:
Wed Jul 11, 2018 5:45 am
Yet, more important, Clem had quickly implemented an emergency stop into mintupgrade, which would be triggered whenever mintupgrade found mesa 18.0.5 on a Mint 18.3 system.
This emergency exit will have prevented more failed in-place upgrades from Mint 18.3 to Mint 19 over the weekend, than a forum wide announcement would have done.
Remember: this thread had been stickied, just not forum-wide.
I'm sorry, I should have showed more appreciation for what you (staff members) and Clem did do. I do appreciate it.

I just felt that... I am probably not a good example of the average Mint user, lol, being both ignorant and somewhat impulsive. Had I done the upgrade (or attempted to do so) and met with problems, I would have referred to that sub-forum with the intentions of posting a topic after glancing at the recent ones posted by others (both stickied and non-stickied).

I suppose that is backwards; in fact, I know it is - with important and (+/-) risky operations of this nature such as distro upgrades, we should check for known and posted issues before beginning the actual upgrade process. However, I do not always seem to think that way. Yes, that is MY failing, not yours, Clem's, or anyone else's (no dispute there).

I do, however, routinely visit the sub-forum of the DE that I use (Xfce). When I do, I glance at the Announcements (and stickies for that specific sub-forum).

As gm10 pointed out, not everyone's local mirrors would have synchronized in time to help. We cannot blame Clem for this, it's just how these things work. Sadly, this fact may not have made those who had to go to a great deal of effort to recover feel better.

Again, I appreciate what was done. Please consider my words to be more along the lines of a suggestion for the future, in case something of this magnitude occurs again. Even with the best of intentions (which I assume that everyone had), what Clem did, the decision to make the post a sticky, AND my suggestion... there would probably have been some that were affected. I suspect that, regardless of the steps taken, it would have been impossible to reduce the number of affected individuals to zero.

Please consider my suggestion for the future, in the event another potential "show-stopper" issue of this magnitude happens again. And, again, I appreciate what was done. I apologize for criticizing without also stating that.

Regards,
MDM
Mint 18 Xfce 4.12.

If guns kill people, then pencils misspell words, cars make people drive drunk, and spoons made Rosie O'Donnell fat.

User avatar
karlchen
Level 19
Level 19
Posts: 9080
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: [Solved] Warning: In-place upgrade from Mint 18.3 to Mint 19 partially broken by a Mesa Update

Post by karlchen » Wed Jul 11, 2018 12:17 pm

Hi, MDM.

I understand your point was about visibility. A global announcement is visible on top of the list in every sub-forum. The sticky thread could only be found in a single sub-forum. Let us hope that no reason to act accordingly will occur any time soon.

Regards,
Karl
Image
Old bugs good, new bugs bad! Updates are evil: might fix old bugs and introduce no new ones.

Post Reply

Return to “Installation & Boot”