Comment 237 for bug 196277

@svaens, please respect the code of conduct, such comments are less than helpful.

> Bryce: I don't understand why you are closing this bug. True it is fixed in
> 8.10, but it is not fixed in 8.04, which is still supposed to be supported.

It is standard to close bugs when they are fixed in the current development version. If it is desired to have the fix for a previous release, you nominate it for that release, which someone has done and I've approved.

> Some workarounds have been offered above. Why not use them to fix it in
> 8.04, or backport the fix from 8.10?

Unfortunately, upstream did not flag a specific patch but a range of patches in which they think the fix might be, and the quantity of code is more than can be easily backported. So someone will first need to go through the changes and narrow it down. In general, the SRU team prefers simple patches with 0 chance of regression; at this point it is not clear whether that will hold true in this case.

What I need someone able to reproduce this bug to do is git bisect the xserver between commits de4936d7482f820728efeef338a2041c7a9186d2 and c06e27b2f6fd9f7b9f827623a48876a225264132 to see exactly which change resulted in the fixed behavior. If you can identify which change resulted in the fix, I can take the action to port the patch for hardy and get it into the xserver.

Meanwhile, I'll look into the feasibility of doing the setxkbmap workaround, but my guess is that it's not going to be acceptable by the SRU team.

> Someone else can speak for me, but I think a SRU or backport would be the
> correct procedure here. Someone would have to approve an SRU (as per the
> procedure here: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure)

This is correct; I can take care of doing this part, if someone can identify the change that fixes it for me.