Patches are more or less never included in Ubuntu if they have not been commited upstream. This is, as you point out, because we need to make sure it doesn't mess up things for other graphics cards etc.
Once a patch is merged officially by the openchrome devs for your bug, then please take that patch and create a debdiff out of it (follow the instructions here: https://wiki.ubuntu.com/PackagingGuide/Recipes/Debdiff). The debdiff should have a single changelog entry and should not contain commented out code. Finally request sponsorship for karmic (steps described here: https://wiki.ubuntu.com/SponsorshipProcess). Assigning to a team is usually not the way it works. I think the best way forward for this bug would be to talk to the upstream dev about getting a fix merged there. When I had quick look at the upstream code I noticed that the first part of your patch (moving the F in the bitmask leftward) was actually merged in the middle of April: http://www.openchrome.org/trac/changeset/746 Is that change _alone_ sufficient to fix your issue you do you really need upstream to drop that call to close as well? Stable release updates (SRU) are also possible in some cases but those require extensive testing to ensure that regressions have a very very low probability. You can read about this process: https://wiki.ubuntu.com/StableReleaseUpdates In general if you're interested in learning how to package, bugfix and test X.org stuff properly, join us at #ubuntu-x on FreeNode IRC (we could definitely use some more OpenChrome people to help out). -- [HP 2133 MiniNote laptop] Unexpected and unrecoverable wireless disconnect with B43 driver https://bugs.launchpad.net/bugs/331952 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
