On Thursday 2 March 2006 19:15, Gonéri Le Bouder wrote: > > Ok, i close the bug. > > The bug isn't fixed! I've had klibido corrupt its databases several > times. Would you like me to run klibido compiled with debug symbols so I > can get a useful backtrace? I suppose what's needed is to catch it > corrupting the database, not crashing when it tries to use it again.
Correct. But the crash seems to be totally random and not KLibido-related. > Doing db updates while files are still downloading seems to provoke > crashes easily. Changing the "group properties" settings, such as > disabling on of the two news servers while klibido is doing other things > might is another thing I've done that I think is correlated with DB > corruption. This is the "typical" Debian behavior, which I'm investigating with a friend of mine. It seems a problem of Debian unstable and derived distro (e.g.: Ubuntu), and seems related to the backports from Bdb CVS. Compiling the db from source (and assuring the Debian one isn't used) seems to fix things. It would be nice to have a .deb package of Bdb with the vanilla sources to test...or to investigate things with the Debian package maintainer a/o the Sleepycat guys, that are very nice and responsive. Unfortunately, I really don't have time to fix such things: I never have this behavior and never have db corruptions, even if I treat my Dbs really bad on my devel pc... Gonéri, is it hard a/o time-expensive to package the vanilla sources of Bdb? -- Bauno - Eurydices, oro, properata retexite fata! "God is real, unless declared integer"
