Comment 11 for bug 107103

On Tue, 2008-10-28 at 09:58 +0000, Martin Pitt wrote:
> Hi Brian,

Hi Martin,

> Right. Just to be clear, I am not *really* happy about sending core
> dumps either, but it's currently the only practical method to get any
> helpful information out of most crashes.

Understood.

> If the stack trace has some information already, apport does offer to
> send a "reduced" report, which does not have the core dump.

Yeah, I had wondered what all was in a reduced report. Maybe it's
worthwhile noting in the dialog where you get that choice what won't be
included in a reduced report. Or maybe when one views the expanded list
of what's going in the report the reduced/full options are still
selectable and the expanded view changes to reflect what will be
included.

Of course all of this is moot if you were to...

>
> > I should be able to deselect sending any of the stack trace
> > attachments too.
>
> That's a possible enhancement indeed.

Do this instead/also.

> This would be a possible option for developers, yes. That's bug 75901.
> However, it isn't the standard mode of operation because it needs lots
> and lots of debug symbols to download.

Sure. I think you should still give users the option to do that:

        Rather than sending the CoreDump which has a likelihood of
        containing sensitive information, I need to install some
        packages to gather more debugging information. I will need to
        install 10MB of additional packages. Shall I go ahead and do
        this? Yes No.

        Shall I Remove additional packages when done? Yes No.

> Right, she can't, and I don't expect her to. That's why we disable
> apport in stable releases. :-)

Yeah. But if this reason is the only reason why GA releases get apport
disabled, if we could solve this, we could get apport reports from GA
users.

b.