Re: [trinity-users] ignored kmail crash reports.

Greetings all; Are you send those to /dev/null? I've sent a whole bunch of them. These crashes always seem to be preceded by a couple days of a kmail session burning up a core of 4 cores, bouncing to the next available core, at 99 to 100% at 15 second or so intervals. These seem to be related to kmail finding trash files in its database, causing problems while re-indexing. I have two folders which are subfolders with a given years messages manually sorted into that years corpus. When I relaunch kmail after one of these crashes, I am getting advisories that so-and-so has an index problem, and its generally the top level folder, and 2 or 3 of its subfolders that are named. And the older folders are slowly being emptied, as in messages are disappearing despite having no expiry set up. Can anything be done, or is there something I can check-uncheck someplace? Thanks. Cheers, Gene Heskett