Aug 10, 2017 - 07:55am
I believe it has been an old issue since Miguel Alonso has mentioned it in https://01.org/linuxgraphics/forum/graphics-installer-discussions/new-ub... scroll to the bottom
The problem is the tool depdends on this very exact package https://launchpad.net/ubuntu/xenial/amd64/libegl1-mesa/12.0.6-0ubuntu0.1...
However, as the status indicated, the package is superceded. The current latest version as of this morning EDT time islibegl1-mesa/xenial-updates,now 17.0.7-0ubuntu0.16.04.1 amd64 [installed]
libegl1-mesa/xenial-updates,now 17.0.7-0ubuntu0.16.04.1 amd64 [installed]
So there is no point to depend on this package at all.
I even tried to install 12.0.6 manually but it doesn't work, as the dependencies expands so large it's gonna break other stuff so I eventually gave up. The very same issue is reported by others as well: https://firstname.lastname@example.org/msg5235475.html
Knowing so far 16.04 is the LTS version of ubuntu, why do you publish later versions for 17.04, only? I would assume the LTS version is supposed to be the top priority and the most stable one. After updating the Tool, the consequence is the driver is not able to be installed anymore. Any chance this can get fixed?
Hi - the goal of the update-tool project is to get the latest release of the 01.org stack onto the latest release of the distribution in question - in the case of LTS releases the difference in versions makes this increasingly difficult as time passes, so we don't re-target LTS releases.
However there is a better solution anyway: The hardware enablement packs for LTS releases are more comprehensive than the update-tool packages (in particular they update the whole kernel) and don't
require a backport of the i915 driver, so that's what we recommend to LTS users:
I launch on Ubuntu 16.04.3 LTS, the Intel Graphics update Tool fo Linux OS and I have this 2 fails.
I regret that the page of your site does not indicate in advance that I would have this problem and explicitly discouraged for Ubuntu 16.04.1, 16.04.2,16.04.3.
Is my system broken ? what should I do summarily to return to the normal ?