Comment 9 for bug 1747744

Revision history for this message
Doug McMahon (mc3man) wrote :

Going the other way, i.e. 17.10 updated, then slowly upgraded to bionic found this.
Updating totem, the eventually all of gstreamer inc. the vaapi plugin, installing libva2 packages produced no issues & did provide vaapi in totem once libva was fully on bionic versions. (restarts after all changes..
Updating libdrm2 caused no issues.
However as soon as this group was updated & a reboot corruption in totem occurred

Upgraded the following packages:
libdrm-amdgpu1 (2.4.83-1) to 2.4.89-1
libegl1-mesa (17.2.8-0ubuntu0~17.10.1) to 17.3.3-0ubuntu1
libgbm1 (17.2.8-0ubuntu0~17.10.1) to 17.3.3-0ubuntu1
libgl1-mesa-dri (17.2.8-0ubuntu0~17.10.1) to 17.3.3-0ubuntu1
libgl1-mesa-glx (17.2.8-0ubuntu0~17.10.1) to 17.3.3-0ubuntu1
libglapi-mesa (17.2.8-0ubuntu0~17.10.1) to 17.3.3-0ubuntu1
libgles2-mesa (17.2.8-0ubuntu0~17.10.1) to 17.3.3-0ubuntu1
libmirclient9 (0.28.0+17.10.20171011.1-0ubuntu1) to 0.29.0-0ubuntu1
libmircommon7 (0.28.0+17.10.20171011.1-0ubuntu1) to 0.29.0-0ubuntu1
libmircore1 (0.28.0+17.10.20171011.1-0ubuntu1) to 0.29.0-0ubuntu1
libmirprotobuf3 (0.28.0+17.10.20171011.1-0ubuntu1) to 0.29.0-0ubuntu1
libwayland-egl1-mesa (17.2.8-0ubuntu0~17.10.1) to 17.3.3-0ubuntu1
mesa-va-drivers (17.2.8-0ubuntu0~17.10.1) to 17.3.3-0ubuntu1
mesa-vdpau-drivers (17.2.8-0ubuntu0~17.10.1) to 17.3.3-0ubuntu1