On 10/7/07, Daniel Jacobowitz <[EMAIL PROTECTED]> wrote: > Package: liferea > Version: 1.4.3-1 > Severity: normal > > I never quit liferea. It runs until either it crashes or my entire > system crashes. This used to be fine, but today I've discovered that > it isn't caching updated feeds to disk. So after a crash I restart it > and it has three hundred "new" articles that I've already read through > liferea, plus five at the bottom that are new since the crash.
Known problem. No solution in sight. I already tried reproducing the effect with a test program using the same schema and similar SQL statements as Liferea, but it doesn't show the same problem. I have the feeling this might be caused by some threading effects in Liferea, but know nothing certain... > I don't have any useful debug output, just things like this which > I don't think are related: > > ** (liferea:11306): WARNING **: Dropping view failed (no such table: > view_gbqxdin) SQL: DROP VIEW view_gbqxdin; > > ** (liferea:11306): WARNING **: Dropping view failed (no such table: > view_rlfnxtd) SQL: DROP VIEW view_rlfnxtd; These two messages are no real problem. But are fixed with upstream release 1.4.4 > ** (gecko:11306): WARNING **: Fatal: no node with id "cvvyivo" found! > > ** (gecko:11306): WARNING **: Fatal: no node with id "cvvyivo" found! Also not really critical usually triggered by using comment feeds. I'll work on this in the future. Regards, Lars -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
