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 should always have matching versions
  installed, just like libegl-mesa0 and libgbm1 currently have.
  
  [Test case]
  
- WIP
+ On a clean chroot;
+ 
+ - disable updates in /etc/apt/sources.list
+ 
+ - install 'libegl-mesa0 libglx-mesa0'
+ 
+ - then enable updates again, run 'apt-get upgrade', and see how it would
+ upgrade libgl1-mesa-dri without upgrading libgbm1 too:
+ 
+ Reading package lists... Done
+ Building dependency tree... Done
+ Reading state information... Done
+ Calculating upgrade... Done
+ The following packages have been kept back:
+   libegl-mesa0 libgbm1 libglapi-mesa libglx-mesa0
+ The following packages will be upgraded:
+   libbsd0 libdrm-amdgpu1 libdrm-common libdrm-intel1 libdrm-nouveau2 
libdrm-radeon1 libdrm2 libelf1t64
+   libgl1-mesa-dri libicu74
+ 10 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
+ Need to get 11.2 MB of archives.
+ After this operation, 33.6 MB disk space will be freed.
+ Do you want to continue? [Y/n] n
+ 
+ - enable proposed, run the same thing, notice how libgl1-mesa-dri is kept back
+                           
+ Reading package lists... Done
+ Building dependency tree... Done
+ Reading state information... Done
+ Calculating upgrade... Done
+ The following packages have been kept back:
+   libegl-mesa0 libgbm1 libgl1-mesa-dri libglapi-mesa libglx-mesa0
+ The following packages will be upgraded:
+   libbsd0 libdrm-amdgpu1 libdrm-common libdrm-intel1 libdrm-nouveau2 
libdrm-radeon1 libdrm2 libicu74
+ 8 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
+ Need to get 11.1 MB of archives.
+ After this operation, 2048 B of additional disk space will be used.
+ Do you want to continue? [Y/n] 
+ 
  
  [Where things could go wrong]
  
  This just adds a necessary safe-guard for upgrades, so hard to think
  where it might cause issues.

** Changed in: mesa (Ubuntu)
       Status: New => Fix Released

** 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.
+ In some cases (apt-get vs apt) 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]
  
  On a clean chroot;
  
  - disable updates in /etc/apt/sources.list
  
  - install 'libegl-mesa0 libglx-mesa0'
  
  - then enable updates again, run 'apt-get upgrade', and see how it would
  upgrade libgl1-mesa-dri without upgrading libgbm1 too:
  
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  The following packages have been kept back:
-   libegl-mesa0 libgbm1 libglapi-mesa libglx-mesa0
+   libegl-mesa0 libgbm1 libglapi-mesa libglx-mesa0
  The following packages will be upgraded:
-   libbsd0 libdrm-amdgpu1 libdrm-common libdrm-intel1 libdrm-nouveau2 
libdrm-radeon1 libdrm2 libelf1t64
-   libgl1-mesa-dri libicu74
+   libbsd0 libdrm-amdgpu1 libdrm-common libdrm-intel1 libdrm-nouveau2 
libdrm-radeon1 libdrm2 libelf1t64
+   libgl1-mesa-dri libicu74
  10 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
  Need to get 11.2 MB of archives.
  After this operation, 33.6 MB disk space will be freed.
  Do you want to continue? [Y/n] n
  
- - enable proposed, run the same thing, notice how libgl1-mesa-dri is kept back
-                           
+ - enable proposed, run the same thing, notice how libgl1-mesa-dri is
+ kept back
+ 
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  The following packages have been kept back:
-   libegl-mesa0 libgbm1 libgl1-mesa-dri libglapi-mesa libglx-mesa0
+   libegl-mesa0 libgbm1 libgl1-mesa-dri libglapi-mesa libglx-mesa0
  The following packages will be upgraded:
-   libbsd0 libdrm-amdgpu1 libdrm-common libdrm-intel1 libdrm-nouveau2 
libdrm-radeon1 libdrm2 libicu74
+   libbsd0 libdrm-amdgpu1 libdrm-common libdrm-intel1 libdrm-nouveau2 
libdrm-radeon1 libdrm2 libicu74
  8 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
  Need to get 11.1 MB of archives.
  After this operation, 2048 B of additional disk space will be used.
- Do you want to continue? [Y/n] 
- 
+ Do you want to continue? [Y/n]
  
  [Where things could go wrong]
  
  This just adds a necessary safe-guard for upgrades, so hard to think
  where it might cause issues.

-- 
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:
  Fix Released
Status in mesa source package in Noble:
  New
Status in mesa source package in Oracular:
  New

Bug description:
  [Impact]

  In some cases (apt-get vs apt) 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]

  On a clean chroot;

  - disable updates in /etc/apt/sources.list

  - install 'libegl-mesa0 libglx-mesa0'

  - then enable updates again, run 'apt-get upgrade', and see how it
  would upgrade libgl1-mesa-dri without upgrading libgbm1 too:

  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  The following packages have been kept back:
    libegl-mesa0 libgbm1 libglapi-mesa libglx-mesa0
  The following packages will be upgraded:
    libbsd0 libdrm-amdgpu1 libdrm-common libdrm-intel1 libdrm-nouveau2 
libdrm-radeon1 libdrm2 libelf1t64
    libgl1-mesa-dri libicu74
  10 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
  Need to get 11.2 MB of archives.
  After this operation, 33.6 MB disk space will be freed.
  Do you want to continue? [Y/n] n

  - enable proposed, run the same thing, notice how libgl1-mesa-dri is
  kept back

  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  The following packages have been kept back:
    libegl-mesa0 libgbm1 libgl1-mesa-dri libglapi-mesa libglx-mesa0
  The following packages will be upgraded:
    libbsd0 libdrm-amdgpu1 libdrm-common libdrm-intel1 libdrm-nouveau2 
libdrm-radeon1 libdrm2 libicu74
  8 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
  Need to get 11.1 MB of archives.
  After this operation, 2048 B of additional disk space will be used.
  Do you want to continue? [Y/n]

  [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

Reply via email to