If you're sure it's a problem represented by that bug, [**answer it**][1]. I've reopened it to allow that.

I consider this a much healthier option to just shutting the question down. I've been through [the reasoning][2] before but if nothing else, it gives us a duplicate target for future questions about the same problem.

I note that in this case we're talking about a bug you reported which is still currently un-triaged and hasn't progressed at all, and (as far as I can tell from the report) hasn't been pushed upstream. There are going to be some issues. I don't think that neccessarily rules it out from being a viable answer but point out its status and what it needs to be improved (perhaps other people can help).


  [1]: http://meta.askubuntu.com/a/8822/449
  [2]: http://meta.askubuntu.com/questions/7841/please-try-to-read-bug-reports-before-voting-to-close-something-as-a-bug