My suggestion was actually for something simpler. A complete report from the application might be too ambitious, but something simple like dmesg, and maybe uname, etc.<br><br><br><br><br><br><div><span class="gmail_quote">
On 3/16/06, <b class="gmail_sendername">John Nilsson</b> <<a href="mailto:john@milsson.nu">john@milsson.nu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Wed, 2006-03-15 at 13:33 -0800, Daniel Robitaille wrote:<br>> *) Malone can receive reports that are related to any of 15,000+<br>> packages. I'm skeptical that a script could deal for that wide range<br>> of possibility of what went wrong, and what pieces of info are needed
<br>> for the developers.<br><br>One possibility would be to have each package provide its own set of bug<br>report scripts and/or other bug reporting policies. The bug reporting<br>application would call these scripts and attach their output while
<br>guiding the user through the bug submission.<br><br>Regards,<br>John<br><br><br>--<br>ubuntu-devel mailing list<br><a href="mailto:ubuntu-devel@lists.ubuntu.com">ubuntu-devel@lists.ubuntu.com</a><br><a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel">
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel</a><br></blockquote></div><br>