apport symptom based reporting

[Tim Gardner]

Andy Whitcroft wrote:
> I have just had a strange experience with the symptom based reporting
> in apport.  I have obviously had some kind of kernel issue, either a
> delayed failed suspend/resume report or perhaps an oops which has not
> had any physical effect I am aware of.  I get the apport report of a
> 'serious kernel issue' and asked to report it; note that I was previously
> unaware of the problem.  Now the first question is 'Has this issue been
> confirmed to exist with the upstream kernel?" and I have yes/no as options.
> But as I have no prior knowledge of the issue, and have yet to have had an
> option to see the report, it is impossible for me to answer this question
> meaningfully.  Perhaps we need some thought to this flow for these
> cases?
> 
> Do we have a flow chart or similar we can look at to see how its means
> to question you?
> 
> -apw
> 

I'm wondering if apport is just spooking at random noises. I had the
same thing happen, but I could not find _anything_ in dmesg or
/var/log/syslog that would indicate why apport was triggered.

rtg
-- 
Tim Gardner tim.gardner at canonical.com