apport appears broken in latest updates/dailies

[Jeremy Foshee]

On Sun, 2010-03-14 at 16:15 -0700, Bryce Harrington wrote:
> On Sun, Mar 14, 2010 at 10:53:54AM +0000, Andy Whitcroft wrote:
> > On Sun, Mar 14, 2010 at 03:16:36AM -0400, Jeremy Foshee wrote:
> > > On Sat, 2010-03-13 at 18:05 -0800, Bryce Harrington wrote:
> > > > On Sat, Mar 13, 2010 at 08:35:25PM -0500, Jeremy Foshee wrote:
> > > > > Folks,
> > > > > 	I'm not saying it is in-fact broken, but I have seen an inordinate
> > > > > amount of bug reporters having problems reporting and/or collecting
> > > > > logging for bugs.
> > > > 
> > > > Got an example?
> > > 
> > > Here is a recent example of what folks have been seeing.
> > > https://bugs.launchpad.net/bugs/408991
> > > Comment #3.
> > 
> > I thought the -p was no longer required on Karmic? and later?  Looks
> > like its no longer supported.  apport is supposed to self classify the
> > parameters these days, package or bug #.

This has not been my understanding in Karmic, not have I seen any error
like the one being mentioned in all of the reports. we have been asking
for the command with -p and only recently began seeing these problems.

> 
> Pitti, probably would be a good idea even if -p is now unneeded, to
> leave it supported as a depricated option for the period of one release
> cycle.
> 
> (This is probably a good general rule for apport, to give time to get
> docs and tools updated.  I recall we went through this once before with
> ubuntu-bug.)

Here is another description of behavior. This time with additional pains
it would seem.

https://bugs.launchpad.net/bugs/385372

> 
> Bryce