severity 590147 important
thanks
On Sun, May 27, 2012 at 11:50:08AM +0200, Moritz Mühlenhoff wrote:
> On Mon, Nov 29, 2010 at 11:28:31AM +0200, Modestas Vainius wrote:
> > > The two are from my point of view RC
> >
> > No, the first part is not RC because:
> >
> > 1) it is rare enough
> > 2) th
On Mon, Nov 29, 2010 at 11:28:31AM +0200, Modestas Vainius wrote:
> > The two are from my point of view RC
>
> No, the first part is not RC because:
>
> 1) it is rare enough
> 2) there is no data loss involved
>
> There is no info about the 2nd part and according to upstream, the bug has
> been
Hello,
On pirmadienis 29 Lapkritis 2010 10:21:13 Bastien ROUCARIES wrote:
> >. 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 ?
On Mon, Nov 29, 2010 at 2:22 AM, Modestas Vainius wrote:
> tags 590147 help
> thanks
>
> Hello,
>
> 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
>> >upstream.
>>
tags 590147 help
thanks
Hello,
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
> >upstream.
>
> I have not the skills to debug this bug, but they are some file that
>> No this bug occurs after an upgrade.
>Upgrade from what version?
upgrade to 1.6.5
>> I could start agregator after
>> deleting all my archive... So crash each time or loss all archive.
>This supports my assumption that the problem is cache corruption.
No it is an archive problem. Not a cahc
6 matches
Mail list logo
