ubuntu-x-swat team mailing list archive

[Bryce Harrington <bryce@xxxxxxxxxxxxx>]

On Thu, Feb 17, 2011 at 02:12:03PM -0000, yota wrote:
> @Bryce:
> 
> my KVM still doesn't toggle under X in maverick, while it toggles on a
> VT.
> 
> Since the problem still seems to apply to various KVMs and the issue
> just says "Scroll lock does not work in X" (which is true) it seems to
> me valuable to keep it open.

If this were a support forum I'd agree, but the usage pattern for a bug
tracker is different, and actually general practice is to keep bug
reports as fine grained as possible.

Especially with hardware problems like KVM switches it's not uncommon to
need a separate fix for each specific type of device.  In this sort of
situation, it's really helpful to have each person's problem as a
separate bug report, so as we generate or locate patches we can keep
track of which KVMs still need attention and which are solved.

Also, bug trackers tend to make it really cheap and easy to dupe
multiple bug reports, whereas splitting one bug report out into several
isn't possible.  So even in the case where everyone's KVM scroll lock
issue was identical, it's not hard for us developers to quickly verify
this, and then easily mark them as dupes.  Then, if later on we find
we've made a mistake we can undupe bugs on a case by case basis and
carry on.

Anyway, I'm belaboring the point.  But trust me, it really does help to
have separate bug reports for each person and each particular piece of
hardware.  :-)

> Moreover "scroll lock doesn't work in ubuntu" on a search engine is
> likely to land here, leaving this issue open helps collecting everyone's
> experience in one place.

Actually, if the bug is closed, the search engine will still be able to
link to it, so that's not a problem.

But I think what you are wanting in this case would be best served as a
discussion thread on a technical support forum such as askubuntu.com or
the ubuntu forums, which I think would be a really good idea.
Meanwhile, in the bug tracker we really should just focus development
efforts towards *fixing* the bug.