On Sunday 14 May 2006 00:29, A. Costa wrote: > > The "no information from user" claim is unfair; I have received no > such query. > > When the bug was closed, the BTS emailed me, so I checked the > BTS today... and discovered this reply from 4/14/06: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=354029;msg=10 > > That message's "To:" field reads: > > To: 354029@bugs.debian.org, control@bugs.debian.org > > My email address isn't there, and there's no 'CC:' field. Sorry, I didn't realize that you wouldn't receive the e-mail. > > ---- > > Anyway, here's a reply to that query: > > On Sun, 16 Apr 2006, Adam Porter wrote: > > Did this just start happening? > > I forget. I think it happened after various upgrades. > > > Does it happen if you run kmail under > > a different user account? > > Coincidentally, a few days after submitting the bug report, I did try > running 'kmail' under other accounts a few weeks ago and the other > accounts didn't have the bug. Therefore it seemed like the bug was > triggered by a bad config file. > > So I did some trial and error by gradually deleting stuff from the bad > config file, then moving stuff over from the good one. This eventually > fixed the problem. But I haven't yet been so thorough as to figure out > exactly which line or lines triggered the bug. It seems to me that what we really need is to know what lines caused the crash. Without that, what can be done? > > I kept a copy of the bad config. > > > Do any other KDE PIM apps crash? > > I'm not sure. This is at a demo machine at a friend's** house, and > he's a Linux novice who doesn't know how to report bugs. (My regular > system is XFCE with Sylpheed for a mail client.) > > (**my friend doesn't have 'root' access though, which simplifies things.) The fact that it's not doing it on your computer will make it extra hard to diagnose. I'm a little doubtful about this really going anywhere. :) > > > Could you attach the backtrace from the kcrash handler? > > Now, no; later yes, if you still think it would help. If you want to submit it to the KMail devs, then yes, I would think so. But I wouldn't send it without the problem config file lines too. > > NB: While I've relieved the symptom, I don't consider this bug > "fixed", as it seems buggy for an email client config parameter, wrong > or not, to produce such behavior. Seems like there's two possible > causes of the crash: > > 1) kmail has buggy crash-causing code. > 2) For some necessary reason, certain config file parameters > will inevitably cause kmail to crash. > > Case #1, if true, should be fixed. > > Case #2, if the crash is to be expected given the config, then it would > be better, if at all possible, that the config file should be parsed > before loading to check for bad parameters that would cause a crash, > and then the user should be warned. > > HTH...
Attachment:
pgp2o9Hl2TRS2.pgp
Description: PGP signature