Please update libdrm for lts-raring

Bug #1171340 reported by Maarten Lankhorst on 2013-04-22
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
libdrm (Ubuntu)
Undecided
Unassigned
Precise
Undecided
Maarten Lankhorst
Quantal
Undecided
Maarten Lankhorst

Bug Description

[Impact]
 * libdrm versioning is a mess, and lying about the version will lead to all kinds of problems.
 * Changes between 2.4.39 in precise/quantal and 2.4.43:
   - some tiling changes for radeon SI and multisampled surfaces (SI support is not available on precise xserver, so this is harmless.)
   - Adding PCI ID's for newer chipsets on radeon.
   - Some fixes for intel, and adding support for newer chipsets.
   - A few small nouveau fixes, and adding support for selecting kepler engines
   - manpages no longer formatted with troff, using xml instead
   - adding support for freedreno (disabled in our package)
   - Exynos fixes (disabled too)
   - A small omap fix, which the pandaboard ppa already included.
 * Renaming libdrm hasn't worked correctly, it has been attempted before in LP #1086345
 * Lying about version numbers will break, there is a version in x-updates ppa that's the same version as quantal, so doing an upload with a version that's lower than what's available in quantal will break for anyone that followed the steam install instructions.
 * libdrm-nouveau1a should be patched in again, and re-enabled for precise and quantal.
   - plymouth needs this on quantal and precise
   - precise xserver and mesa require this, too

[Test Case]
 * Testing should be performed on quantal, precise lts-quantal, and precise original stack, with intel, radeon and nouveau.
 * Plymouth should still work correctly on precise and quantal with all the 3 kinds of cards
 * system should boot correctly, xserver, compiz and opengl applications must still work.

[Regression Potential]
 * I believe the regression potential is low, raring has been mostly on a stack similar to quantal for most of the release, with the bump to new mesa 9.1 only happening right
 before final freeze, so a lot of testing has already been done.
 * Old nouveau abi has not been tested however, with the plymouth update finally using the 'dumb' kms api instead of nouveau/intel/radeon directly.
 * The core libdrm api hasn't been changed however, libdrm-nouveau1a was only using that subset.
 * So if something breaks, it's likely going to be in a form similar to #1086345
 * It would be very unlikely to introduce new crashes in opengl applications, or xserver

[Other Info]
 * Provisional MRE granted, for updating libdrm in quantal and precise to the raring version.

[Original bug report]
For the lts-raring backports stack libdrm needs to be backported to quantal and precise. While the API is stable and I haven't noticed any new bugs being introduced, I fear that bumping the version number to beyond what quantal provides will make upgrading to quantal harder. Unfortunately, I think this is the only solution.

The ubuntu-x-swat/x-updates ppa was recommended to be enabled for steam, and was already providing a newer libdrm:
https://launchpad.net/~ubuntu-x-swat/+archive/x-updates/+packages

The only way out I see is removing libdrm from that ppa, pushing a newer libdrm version to precise, removing libdrm from that ppa, and make update-manager downgrade libdrm during an upgrade to quantal.

no longer affects: mesa (Ubuntu)
Changed in dh-exec (Ubuntu):
status: New → Invalid
Changed in dh-exec (Ubuntu Precise):
status: New → In Progress
assignee: nobody → Maarten Lankhorst (mlankhorst)
Changed in libdrm (Ubuntu Precise):
assignee: nobody → Maarten Lankhorst (mlankhorst)
Changed in llvm-3.2 (Ubuntu Precise):
assignee: nobody → Maarten Lankhorst (mlankhorst)
Changed in llvm-3.2 (Ubuntu):
status: New → Invalid
Changed in libdrm (Ubuntu):
status: New → Invalid
Changed in libdrm (Ubuntu Precise):
status: New → In Progress
Changed in llvm-3.2 (Ubuntu Precise):
status: New → In Progress
milestone: none → ubuntu-12.04.3
Changed in libdrm (Ubuntu Precise):
milestone: none → ubuntu-12.04.3
Changed in dh-exec (Ubuntu Precise):
milestone: none → ubuntu-12.04.3
description: updated
description: updated
no longer affects: llvm-3.2 (Ubuntu)
no longer affects: dh-exec (Ubuntu)
summary: - Please update dh-exec, llvm-3.2 and libdrm for lts-raring
+ Please update libdrm for lts-raring
no longer affects: dh-exec (Ubuntu Precise)
no longer affects: llvm-3.2 (Ubuntu Precise)
Maarten Lankhorst (mlankhorst) wrote :

It seems that dh-exec is not actually used during llvm-3.2 build, so I dropped it as build-depends.

Hello Maarten, or anyone else affected,

Accepted libdrm into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/libdrm/2.4.43-0ubuntu0.0.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in libdrm (Ubuntu Precise):
status: In Progress → Fix Committed
tags: added: verification-needed
Changed in libdrm (Ubuntu Quantal):
status: New → Fix Committed
Adam Conrad (adconrad) wrote :

Hello Maarten, or anyone else affected,

Accepted libdrm into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/libdrm/2.4.43-0ubuntu0.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in libdrm (Ubuntu Quantal):
assignee: nobody → Maarten Lankhorst (mlankhorst)
Maarten Lankhorst (mlankhorst) wrote :

some smoke tests, boot to desktop + testing 32/64 bits glxgears on a 64-bits cpu:

Precise:
- intel (IVB) OK (lts-quantal and precise)
- nouveau (NV96) OK (lts-quantal and precise)
- radeon (5570) OK (lts-quantal and precise)

Quantal:
- intel (IVB) OK
- nouveau (NV96) OK
- radeon (5570) OK

Maarten Lankhorst (mlankhorst) wrote :

32-bits precise and quantal worked on the same cards too.

tags: added: verification-done
removed: verification-needed
Maarten Lankhorst (mlankhorst) wrote :

Works on pandaboard (armhf) precise too.

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libdrm - 2.4.43-0ubuntu0.1

---------------
libdrm (2.4.43-0ubuntu0.1) quantal-proposed; urgency=low

  * Copy package from raring, and re-enable libdrm-nouveau1a. (LP: #1171340)
 -- Maarten Lankhorst <email address hidden> Mon, 22 Apr 2013 11:06:19 +0200

Changed in libdrm (Ubuntu Quantal):
status: Fix Committed → Fix Released
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libdrm - 2.4.43-0ubuntu0.0.1

---------------
libdrm (2.4.43-0ubuntu0.0.1) precise-proposed; urgency=low

  * Copy package from raring, and re-enable libdrm-nouveau1a. (LP: #1171340)
 -- Maarten Lankhorst <email address hidden> Mon, 22 Apr 2013 11:58:20 +0200

Changed in libdrm (Ubuntu Precise):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers