Bug#361805: bug-buddy: fails to update bug information and crashes afterwards

[Dirk De Groote]

On Tue, 2006-04-11 at 16:53 -0700, Steve Langasek wrote:
> On Tue, Apr 11, 2006 at 02:42:31PM +0200, Dirk De Groote wrote:
> > On Mon, 2006-04-10 at 20:05 -0700, Steve Langasek wrote:
> > > severity 361805 important
> > > thanks
> 
> > > On Mon, Apr 10, 2006 at 02:38:46PM +0200, Dirk De Groote wrote:
> > > > Package: bug-buddy
> > > > Version: 2.8.0-3
> > > > Severity: grave
> > > > Justification: renders package unusable
> 
> > > > tested on 2 computers, with same result : lauching "bug-buddy" proposes
> > > > you to update your bug-information. Clicking "update" starts downloading
> > > > 6 (4 on the other box) updates. Then an error message appears :
> > > > "application has quit unexpectedly" and you get 3 options : "restart
> > > > app", "close" or "inform developpers" ( the latter being impossible
> > > > since that one tries to launch "bug-buddy" ...). Selecting "restart"
> > > > puts you back in the "update" loop , this time only requiering 2 updates
> > > > , but those never succeed ... same loop all over : crash --> restart -->
> > > > update --> crash --> restart ... etc.
> 
> > > So click the "don't update" button instead?
> 
> > > I'm not sure why this functionality is enabled at all in the Debian package
> > > of bug-buddy, since updates should happen through the Debian package system
> > > and *not* by pulling updates from third-party websites; but in any case, you
> > > don't have to agree to update in order to use bug-buddy, so I don't think
> > > this warrants a grave severity.
> 
> > Thanks for your reply, I agree, severity shouldn't be "important" , but
> > that what the "report-bug" tool assigns automatically when the package
> > itself becomes unusable. It does not affect any functionality of other
> > packages on the system whatsoever, true.
> > The "don't update" suggestion above however has no effect and crashes
> > "bug-buddy" in the same way.
> 
> Hrm, this is bad; the bug-buddy package shouldn't let itself get into such
> an unusable state.  Probably still not severity: grave, but I do hope this
> gets fixed for etch.
> 
> Does apt-get install --reinstall bug-buddy fix this problem for you?
> 

Hi Steve,

Today I tried bug-buddy again and this time it retreived 3 updates
(instead of 2) and guess ... it launched normally afterwards and seems
to be 100% functional again. I guess one of the updates caused the
"loop" which seems to be fixed by this new 3th update ( these are not
version-updates but rather "bug-information-updates"). Think the bug can
be closed now ?