Comment 8 for bug 1086345

Either a bug in plymouth, or libdrm. Thanks for finally giving me data to back up my suspicion that renaming was a bad idea.

There are 2 possible paths forward:
- Plymouth always using the 'dumb' api, if available. This will probably need a new version of plymouth, however, and only has been the default on raring.
- Drop libdrm renaming, and just upload a new libdrm version. The only reason to put it in was for making plymouth pick up on the old libdrm anyway.

The third option, renaming plymouth, is nearly impossible without changing a LOT of packages.

Eventually we'll need to do the former, but I think for now we don't want to do that since it's only been the default in raring. As such I believe we should wait until the raring release before we do that, since I'm not comfortable just uploading a complete new version of plymouth this late in the cycle.