On Monday 25 November 2002 12:52, Clayton Cornell wrote:

On Monday 25 November 2002 05:19, Bob S. wrote:

...

Hello SuSE people

What in h--- is going on. K mail is crashing when I try to delete messages from a folder. Signal 11 SIGSERV which brings up the bug [...]

Whatever it was, it only affected the SLE folder. The SLE folder still had one email unread even though all messages were marked as

Same here. What I did was to go to $KDEHOME/Mail, and remove the sle-folder.index* file. Then, I was able delete the mails. -- Verdi March --

On Sunday 24 November 2002 22:12, Rikard Johnels wrote:

On Monday 25 November 2002 06.31, Verdi March wrote:

...

On Monday 25 November 2002 12:52, Clayton Cornell wrote:

...

On Monday 25 November 2002 05:19, Bob S. wrote:

...

Hello SuSE people

What in h--- is going on. K mail is crashing when I try to delete messages from a folder. Signal 11 SIGSERV which brings up the bug

[...]

...

Whatever it was, it only affected the SLE folder. The SLE folder still had one email unread even though all messages were marked as

Same here. What I did was to go to $KDEHOME/Mail, and remove the sle-folder.index* file. Then, I was able delete the mails.

-- Verdi March --

Very odd. Seems like a whole lot of us have had the same problem. This is the second time i have this problem.

And also, after a powerout several mails got a freaky date stamp, and as i deleted them one by one, the next folowing mail got the same datestamp and went hay-wire.. (1970-xx-xx)

The sollution? To simply erase the files in the /cur directory for that list.

It's not just the delete command that's being affected. "Mark All Messages As Read" is also causing the crash.

Hi , I also had this problem, but i solved it. I copy the file to my netscape7 mail dir and delete the messases that i don't want. Compress the folder and copy back to kmail folder. On Monday 25 November 2002 13:17, Claudia Goldbrunner wrote:

On Monday 25 November 2002 11:07, Gregory Sawyer wrote:

...

On Sunday 24 November 2002 22:12, Rikard Johnels wrote:

...

On Monday 25 November 2002 06.31, Verdi March wrote:

...

On Monday 25 November 2002 12:52, Clayton Cornell wrote:

...

On Monday 25 November 2002 05:19, Bob S. wrote:

...

Hello SuSE people

What in h--- is going on. K mail is crashing when I try to delete messages from a folder. Signal 11 SIGSERV which brings up the bug

[...]

...

Whatever it was, it only affected the SLE folder. The SLE folder still had one email unread even though all messages were marked as

Same here. What I did was to go to $KDEHOME/Mail, and remove the sle-folder.index* file. Then, I was able delete the mails.

-- Verdi March --

Very odd. Seems like a whole lot of us have had the same problem. This is the second time i have this problem.

And also, after a powerout several mails got a freaky date stamp, and as i deleted them one by one, the next folowing mail got the same datestamp and went hay-wire.. (1970-xx-xx)

The sollution? To simply erase the files in the /cur directory for that list.

It's not just the delete command that's being affected. "Mark All Messages As Read" is also causing the crash.

I also had the same crash, only in the folder where the mails from this lists arrive. I couldn't delete a single mail, could not mark as read and couln't expire the folder. Everytime I tried one of these things Kmail crashed. The only thing that worked was to remove the whole folder ;-(

BTW: SuSE 8.1 KDE 3.04 KMAIL 1.4.3

-- Best regards ******************************** Nick Katsamas Systems Administration Athens NOC - FORTHnet S.A. e-Mail: nkat@forthnet.gr ********************************

On Monday 25 November 2002 08:20, Peter B Van Campen wrote:

Dear Gregory,

On the 19th of Nov, I replied to the list how to eliminate the KMail errors as was told to the list months before by an experianced KDE'er

Here it is again:

You may have had a sys hang or power glitch. On my systems when this happens KMail gets confused and its index files get mixed up. 1. Shutdown KMail 2.Go to your {home} directory then to the "Mail" directory, note upper case M, and delete the files there that end in .index; there are probably several. ex. mine has a .inbox.index file. Caution: If you use Konqi of other GUI File Mgr you may need to enable "Show hidden files" since the index files are normally hidden (they start with a dot ). 3. Restart KMail

PeterB.

On Monday 25 November 2002 04:07 am, Gregory Sawyer wrote:

...

On Sunday 24 November 2002 22:12, Rikard Johnels wrote:

...

On Monday 25 November 2002 06.31, Verdi March wrote:

...

On Monday 25 November 2002 12:52, Clayton Cornell wrote:

...

On Monday 25 November 2002 05:19, Bob S. wrote:

...

Hello SuSE people

What in h--- is going on. K mail is crashing when I try to delete messages from a folder. Signal 11 SIGSERV which brings up the bug

[...]

...

Whatever it was, it only affected the SLE folder. The SLE folder still had one email unread even though all messages were marked as

Same here. What I did was to go to $KDEHOME/Mail, and remove the sle-folder.index* file. Then, I was able delete the mails.

-- Verdi March --

Very odd. Seems like a whole lot of us have had the same problem. This is the second time i have this problem.

And also, after a powerout several mails got a freaky date stamp, and as i deleted them one by one, the next folowing mail got the same datestamp and went hay-wire.. (1970-xx-xx)

The sollution? To simply erase the files in the /cur directory for that list.

It's not just the delete command that's being affected. "Mark All Messages As Read" is also causing the crash.

Thanks Peter -- I will keep that in my Admin notebook for The Next Time. The problem wasn't all that annoying for me since (a) it only happened in my SLE mailbox and (b) its about time for that box to be rolled off into archive-land -- let the problem sink into a tar(1)-pit. Thanks, --Gregory

On Monday 25 November 2002 17:06, Dan Am wrote:

and same here too, obviously a currupted message. Has anybody found out which one it was ? Regards Dan

I'm not sure/not remember, but with "threaded message view", it should be somewhere between the message with subject "USB hardisk" (with no reply) and "Haven't quite figured out backup to CD from Linux command line". I can't tell the time/date since the messages are threaded. And just fyi, I can deleted with pine. -- Verdi March --

Sure thing, I *moved* the mail folder , too. But what remains is the fact that s'body manages to mess up our clients with their mail, and it would be rather interesting to see what's caused it, not so ? Regards Dan Am Montag, 25. November 2002 18:33 schrieb dries:

Dan Am wrote : | and same here too, | obviously a currupted message. Has anybody found out which one it was ? | Regards | Dan | | Am Montag, 25. November 2002 06:31 schrieb Verdi March: | > On Monday 25 November 2002 12:52, Clayton Cornell wrote: | > > On Monday 25 November 2002 05:19, Bob S. wrote: | > > > Hello SuSE people | > > > | > > > What in h--- is going on. K mail is crashing when I try to delete | > > > messages from a folder. Signal 11 SIGSERV which brings up the bug

Yep, have seen that too, i deleted the mail folder (OK it's a bit of a 'just chop the head off' method but it is fixed now.

Grtz. Dries Pruimboom

I've tracked down the offending message (from Patrick Shanahan in the "Strange Mouse Problems" thread, Message-ID 20021123T205545.GAdc6e4.pat@wahoo.no-ip.org), but I don't see anything obviously wrong with it. If anyone wants to take a go at it, I still have a copy that I moved out of my mail folders if you already deleted it.

Just turn off header threading in the config panels (Configure KMail -> Appearance -> Layout -> Thread list of message headers). Delete the offending message. Turn on threading again. Seems to have fixed it, as I can now mark all messages as read without crashing again. -- James Sanders mailto:james@tartarus.org.uk

Did someone already make a bug report at http://bugs.kde.org?? To prevent that this will ever happen again in the future. Can you do this Scott as you seem to have identified the message(s) that are the root cause. Op maandag 25 november 2002 13:07, schreef Scott Jones:

On Monday 25 November 2002 3:56 am, Dan Am wrote:

...

Sure thing, I *moved* the mail folder , too. But what remains is the fact that s'body manages to mess up our clients with their mail, and it would be rather interesting to see what's caused it, not so ?

I've tracked down the offending message (from Patrick Shanahan in the "Strange Mouse Problems" thread, Message-ID 20021123T205545.GAdc6e4.pat@wahoo.no-ip.org), but I don't see anything obviously wrong with it. If anyone wants to take a go at it, I still have a copy that I moved out of my mail folders if you already deleted it.

Op maandag 25 november 2002 17:49, schreef James Sanders:

...

I've tracked down the offending message (from Patrick Shanahan in the "Strange Mouse Problems" thread, Message-ID 20021123T205545.GAdc6e4.pat@wahoo.no-ip.org), but I don't see anything obviously wrong with it. If anyone wants to take a go at it, I still have a copy that I moved out of my mail folders if you already deleted it.

Just turn off header threading in the config panels (Configure KMail -> Appearance -> Layout -> Thread list of message headers). Delete the offending message. Turn on threading again. Seems to have fixed it, as I can now mark all messages as read without crashing again.

-- Richard Bos Without a home the journey is endless

On Monday 25 November 2002 4:53 pm, Scott Jones wrote:

On Monday 25 November 2002 1:39 pm, Richard Bos wrote:

...

Did someone already make a bug report at http://bugs.kde.org?? To prevent that this will ever happen again in the future. Can you do this Scott as you seem to have identified the message(s) that are the root cause.

Done. Bug ID is 51200.

Followup to myself. I did get a reply from Ingo Kloecker, as follows: ------- Additional Comments From kloecker@kde.org 2002-11-26 01:00 ------- Subject: Re: New: Duplicate Message-ID's in a thread cause SIGSEGV I often have dupes (only a couple of hours ago I had the last one) and KMail never crashed because of this. Moreover the backtrace you provided is completely useless since the precompiled binaries are missing all useful debug information. Unless you can compile KMail yourself and provide a meaningful backtrace I will have to close this bug report. Alternatively please provide a folder in mbox format which can be used to reproduce the problem. ------ If anyone else who had this problem could add any additional info or comments to the bug report, please do (http://bugs.kde.org/show_bug.cgi?id=51200). I'm sending him the affected folder, but it's going to take a little while uploading a 5MB tarball over dialup.

On Tuesday 26 November 2002 5:03 am, Kevin Donnelly wrote:

On Monday 25 November 2002 12:07 pm, Scott Jones wrote:

...

I've tracked down the offending message (from Patrick Shanahan in the

Just for curiosity, and future reference, how did you do this?

Kevin

Short answer? It was the one that was different. Really, it was the only message in that folder that wasn't marked as read. Do an 'ls' in your mail folder; read messages should have ":2,S" appended to the filename, where this one didn't. rm'ing it from the folder did the trick. For the record, I got a response from Ingo: ------ ------- Additional Comment #5 From Ingo Kl�cker 2002-11-26 16:27 ------- The problem seems to be caused by a message with these headers: Message-ID: <20021123T205545.GAdc6e4.pat@wahoo.no-ip.org> References: <97c85d994b.john@xl-cambridge.com> <20021123T205545.GAdc6e4.pat@wahoo.no-ip.org> In-Reply-To: <20021123T205545.GAdc6e4.pat@wahoo.no-ip.org> User-Agent: Mutt/1.4i For some reason Message-ID == In-Reply-To. KMail probably doesn't handle this case (which should never happen) correctly. -----

* Scott Jones [11-26-02 15:04]:

On Tuesday 26 November 2002 5:03 am, Kevin Donnelly wrote:

...

On Monday 25 November 2002 12:07 pm, Scott Jones wrote:

...

I've tracked down the offending message (from Patrick Shanahan in the

Just for curiosity, and future reference, how did you do this?

Short answer? It was the one that was different. Really, it was the only message in that folder that wasn't marked as read. Do an 'ls' in your mail folder; read messages should have ":2,S" appended to the filename, where this one didn't. rm'ing it from the folder did the trick.

For the record, I got a response from Ingo:

------

------- Additional Comment #5 From Ingo Kl???cker 2002-11-26 16:27 ------- The problem seems to be caused by a message with these headers:

Message-ID: <20021123T205545.GAdc6e4.pat@wahoo.no-ip.org> References: <97c85d994b.john@xl-cambridge.com> <20021123T205545.GAdc6e4.pat@wahoo.no-ip.org> In-Reply-To: <20021123T205545.GAdc6e4.pat@wahoo.no-ip.org> User-Agent: Mutt/1.4i

For some reason Message-ID == In-Reply-To. KMail probably doesn't handle this case (which should never happen) correctly.

The subject post(s) resulted from editing/resending a post. It should not have been a problem. I will do the same with this post for a check. This post is an edited original. Check the Message-ID. -- Patrick Shanahan Registered Linux User #207535 @ http://counter.li.org

On Tuesday 26 November 2002 8:17 pm, Christopher Mahmood wrote:

Can you guys do me a favor and play on test-list@suse.com...this is a little ridiculous. Thanks,

I've taken it off-list. As for word of a fix: ----- ------- Additional Comments From kloecker@kde.org 2002-11-26 23:08 ------- Subject: Re: Duplicate Message-ID's in a thread cause SIGSEGV On Tuesday 26 November 2002 20:21, Scott Jones wrote:

Any guess on when this might be fixed?

Not before KDE 3.1.1 (unless you use the cvs version). -----