Comment 313 for bug 124406

Regarding splitting the bug reports up rather than having this one gargantuan 300+-post bug...

I do typically prefer having separate bug reports per person/machine, as having to read through hundreds of comments is akin to having to read a car manual just to change a flat tire... :-) These long thread bugs also tend to accumulate people with similar-but-not-the-same bug, so that adds confusion and also makes it less likely that we can get *all* the problems solved (and makes it hard to verify fixes).

However, in this case, the general underlying issue is the X.org input handling design implementation, and I'm not sure having it broken up into separate bug reports will necessarily help. Ultimately, the work to solve the general issue needs done upstream, and I think this bug report and its upstream linkages is sufficient. So, I'll leave it open so people can share workarounds and commiserate over it being relegated to wishlist status and so on. (However, note that we're going to have a session at the upcoming UDS to discuss xserver wishlist bugs, so ironically setting it to wishlist should give it a bit more visibility this time around).

The one situation where I *would* like to see separate bug reports on this issue is where you are encountering severe, repetitive problems. I.e., the keyboard goes crazy daily, or you have a set of steps that reproduces the problem more than half of the time. I'd like to handle these individually because they are almost certainly HW-specific oddities and there may be things we can do to work around the issue or paper it over. But be very clear in your description, and make sure to include full debugging info and detail all the work you've done to diagnose it. We may end up duping the bug reports back here, but I think this will make it easier for us to handle the severe exceptional cases.