"Martin, the bug as described in the bug description is not random and does not affect default shortcuts."
Then perhaps the bug description should be ammended, given the slightly wider set of reports here from a variety of people. See my comment above on race conditions. Just because the original description fits you and Edwin best does not mean that it is fully accurate.
"Any other problems should be reported separately, whatever others have commented."
And who is to define what exactly is a different problem? Where do you draw the line? Did your problem happen at exactly the same time of day as the original in the bug description? Did it happen on exactly the same hardware, with exactly the same configuration? If not, then I suggest you open a separate bug report. </sarcasm> The answer is, devs are the only ones capable of deciding which problems are related, and which aren't.
"Apart from anything else it is always better to report a new bug unless it is absolutely clear that one is seeing identical symptoms to those in the bug description. It is best left to the developers to decide whether a slightly different symptom is actually caused by the same bug."
References please. Who, other than a dev (at best), can be absolutely clear? If a handful of similar yet slightly different bug reports are scattered all over the place, with nothing linking them save perhaps the odd keyword, how is a dev supposed to get a handle on the scope of the problem? The slight differences can be key to solving the problem. You see them only as distraction. What you propose is fragmentation and purity. What I propose is practicality.
"Also unless anyone is still seeing the bug (as described at the top) on 14.04 it should probably be marked as fixed."
If you'd feel inclined enough to go through some of the reports here, you'd know that the bug is alive and well in 14.04, both Ubuntu and Xubuntu. See #19, #22, #25, #27, #28, #29, plus my own (#34).
"Martin, the bug as described in the bug description is not random and does not affect default shortcuts."
Then perhaps the bug description should be ammended, given the slightly wider set of reports here from a variety of people. See my comment above on race conditions. Just because the original description fits you and Edwin best does not mean that it is fully accurate.
"Any other problems should be reported separately, whatever others have commented."
And who is to define what exactly is a different problem? Where do you draw the line? Did your problem happen at exactly the same time of day as the original in the bug description? Did it happen on exactly the same hardware, with exactly the same configuration? If not, then I suggest you open a separate bug report. </sarcasm> The answer is, devs are the only ones capable of deciding which problems are related, and which aren't.
"Apart from anything else it is always better to report a new bug unless it is absolutely clear that one is seeing identical symptoms to those in the bug description. It is best left to the developers to decide whether a slightly different symptom is actually caused by the same bug."
References please. Who, other than a dev (at best), can be absolutely clear? If a handful of similar yet slightly different bug reports are scattered all over the place, with nothing linking them save perhaps the odd keyword, how is a dev supposed to get a handle on the scope of the problem? The slight differences can be key to solving the problem. You see them only as distraction. What you propose is fragmentation and purity. What I propose is practicality.
"Also unless anyone is still seeing the bug (as described at the top) on 14.04 it should probably be marked as fixed."
If you'd feel inclined enough to go through some of the reports here, you'd know that the bug is alive and well in 14.04, both Ubuntu and Xubuntu. See #19, #22, #25, #27, #28, #29, plus my own (#34).