On Mon, Nov 29, 2010 at 2:22 AM, Modestas Vainius <email@example.com> wrote:
> tags 590147 help
> On antradienis 09 Lapkritis 2010 11:23:53 Bastien ROUCARIES wrote:
>> > But now there are too many
>> >variables. To make things worse, akregator developement isn't very active
>> I have not the skills to debug this bug, but they are some file that
>> coul allow youy to reproduce it at
> All that stuff in bug report is useless because both this debian bug and
> upstream bug deal with consequences. When you see this crash and backtrace,
> the archive file had already been cut short and the data had already been
> lost. akregator is simply unable to read corrupt archive file on startup and
> rather than handling this condition gracefully, it crashes
Do you agree that solving the first part of the problem will be really
nice. Instead of alway crashing following a cosmics ray it will prompt
and fix the error.
>. However, there is
> no information how and when akregator fails to write correct archive file or
> otherwise corrupts it.
I agree also with this part. But it is a second bug
Should I duplicate the bug ? The two are from my point of view RC
> So basically this bug is impossible to fix without a reliable way to reproduce
> it from the start to finish. During my 2 years of using akregator, I have
> never had this problem so there is not much I can do.
> Modestas Vainius <firstname.lastname@example.org>