plucky has 24.3.4-3ubuntu1, the fix is included in 24.3.4-1 and up
** Description changed:
[Impact]
In some cases upgrade to a newer mesa can leave libgbm1 behind, which
then could result in issues like the login screen showing a crash screen
instead.
libgl1-mesa-dri and libgbm1 s
oibaf: okay so that would suggest that mesa-va-drivers should match the
version of mesa-libgallium I guess
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098084
Title:
Add a more strict dependency b
..but it's out of scope for this bug. Will be fixed later.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098084
Title:
Add a more strict dependency between DRI drivers and libgbm
To manage notific
oh, there's a difference between 'apt' and 'apt-get'.
after installing 'libegl-mesa0 libglx-mesa0 mesa-vulkan-drivers mesa-va-
drivers' on a chroot, and enabling noble-updates I get
apt-get upgrade
...
The following packages have been kept back:
libegl-mesa0 libgbm1 libglapi-mesa libglx-mesa0 m
actually, it probably does the right thing now, preventing a partial
upgrade with 'apt upgrade'.. in order to upgrade (with apt) you'd need
'apt dist-upgrade' since there's the new mesa-libgallium which will get
installed as a result
--
You received this bug notification because you are a member
Ok thanks, I'll investigate what's going on
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098084
Title:
Add a more strict dependency between DRI drivers and libgbm
To manage notifications about th
It was suggested that I try adding the canonical-x staging PPA to check
a fix, but it seems the issue is still present. after update/upgrade the
system still attempts to keep back mesa packages. I've attached a full
list of the offered upgradeable packages to my comment.
Thanks,
-David
** Attac
Possibly also mesa-va-drivers, see https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1094190 :
"It might be possible that the issue was originally caused because I was
holding back the libglx-mesa0 package to an earlier version and mesa-va-
drivers did not depend on the newer version, but I'm not
** Description changed:
[Impact]
In some cases upgrade to a newer mesa can leave libgbm1 behind, which
then could result in issues like the login screen showing a crash screen
instead.
+
+ libgl1-mesa-dri and libgbm1 should always have matching versions
+ installed, just like libegl-me
