Symptom-based X.org bug reporting with apport

[Bryce Harrington]

Binary package hint: xorg

Bug reporters don't usually have a good clue on what package to file their X bug against (they may not even know what X is), nor do they usually know what data to collect and attach.

But they usually know the symptoms they're having.

Apport's new symptom-based bug reporting capabilities will facilitate a new, hopefully more user-friendly method for reporting bugs. Ideally it should also result in bug reports that are more easily machine-readable. Knowing the symptoms may enable better automated bug triage, better dupe detection, and better troubleshooting advice.

Work Tasks:

 * (DONE) Itemize a standard listing of symptoms/tags in wiki
 * Write a proof-of-concept script that displays a few symptoms and adds tags accordingly
 * Test proof-of-concept script
 * Design a question-tree to lead user through some symptoms and sub-symptoms, ref to wiki troubleshooting pages as appropriate
 * Code up question-tree into the xorg apport hook
 * Test xorg apport hook and deploy
 * Rinse and repeat as needed to flesh out the capabilities

[Bryce Harrington (bryce)]

Some preliminary code for this is now included in apport-symptoms. Further work will be trtacked in that package.