© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
I examined the patches mentioned above, and compared them against the xserver code in lucid. All the changes from the patches[1] are in the lucid xserver.
I've tried to reproduce the issue on karmic but didn't have success there, so I can't be sure I'm testing lucid correctly to verify it as fixed. You guys are going to need to do this, since you know what you're looking for. But I figure it's safe to assume if adding those patches fixed it before, then since they're in the xserver now the issue is resolved.
For future reference, if you attach patches to the bug report itself (as opposed to simply referencing them by link) then the bug will bubble up to the top of various bug listings I look at[2,3] and will be much more likely to gain attention.
Also, if you've gone to the trouble of applying a patch to the source package and building it locally, you've gone 80% of the way to fixing the package yourself. The last 20% is to create a debdiff[4] and request an SRU[5]. Not to say you *have* to do that (like I said, if you just post patches to the bug report, it brings them to my attention), but it's totally something you could do if you needed to.
Finally, I would *highly* recommend updating the description of bug reports like this one, where the original problem statement is a bit terse, and there's an explosion of comments to have to wade through to understand the current state of the problem.
1: From http://<email address hidden>
2: http://
3: http://
4: https:/
5: https:/