© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
No worries, Alexander: I'm on your side. :) I found your bug report because I, too, was unable to play my favorite games on my favorite operating system.
While it's true that Marcin's patch is small, don't forget that it hasn't yet appeared in xorg-server-
This means that if some enterprising Ubuntu developer wanted to roll the fix into the X.Org server shipped with 12.04, it would be his responsibility to make sure that the change didn't break anything across any of the other 70 xserver-xorg-* packages. That alone is hard enough to do-- even trivial changes tend to expose bugs elsewhere. But even if the enterprising developer did all that work, he should expect his support from upstream to be minimal, given that he'd be integrating pieces that hadn't yet been "signed off" as ready to use. And woe be him if even one bug would appear elsewhere: he'd have people asking him why he introduced bugs into a stable LTS release.
So in effect, when we ask a maintainer to integrate the mousewheel patch, we're asking them to take on 71 high-profile packages' worth of risk-- with the understanding that they will likely not receive any support-- on unreleased code that no one has yet had a chance to hammer on.
Viewed from this angle, the developer would make better use of his time (and not risk his reputation) by waiting for Marcin's bugfix to be merged into an official release of the X.Org server upstream. Then, after the fix found its way into Debian testing, he could submit an SRU request (see https:/
This is why I say it's unlikely we'll see this bug fixed in 12.04.
We've got to wait for a new upstream release of the X.Org server that incorporates this change, then we've got to wait for Debian to accepting the new version into Debian testing, and then we've got to lobby a developer to submit an SRU request for the new version of X.Org.