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 sure." ** Bug watch added: Debian Bug tracker #1094190 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094190 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2098084 Title: Add a more strict dependency between DRI drivers and libgbm Status in mesa package in Ubuntu: New Status in mesa source package in Noble: New Status in mesa source package in Oracular: New Bug description: [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-mesa0 and libgbm1 currently have. [Test case] WIP [Where things could go wrong] This just adds a necessary safe-guard for upgrades, so hard to think where it might cause issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2098084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
