Summary: | crash on specific email (no attachment) | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | Chani <chanika> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | andresbajotierra, oakad |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Chani
2010-02-15 03:53:36 UTC
If you can please attach the mail to this bug, otherwise you can sent it to me. Either way please make sure that you attach/send the complete unchanged message. Seems related to bug 186502 / bug 224414. Regards I forwarded the email... I think gmail screwed it up, though. and obviously I can't forward it or save it or anything from kmail because it crashes. I've encountered this (or related bug) on kde-4.4.0 as well (released version). I haven't encountered such problem with kmail shipped kde-4.2.4 (which I used for many months without any trouble), so this is definitely a regression. Given this, I want to make the following impolite comment: if kmail developer(s) needs an "offending message" to establish the reason for the crash, he's doing something really wrong. There are millions of corrupted/badly formatted/malicious messaged out there on the webs and we can't possibly try out every one of them. (In reply to comment #4) > Given this, I want to make the following impolite comment: if kmail > developer(s) needs an "offending message" to establish the reason for the > crash, he's doing something really wrong. > > There are millions of corrupted/badly formatted/malicious messaged out there on > the webs and we can't possibly try out every one of them. Well I didn't ask for one of these messages did I? I asked for the specific message that the reporter had problems with. Reason? I have no messages in my mailbox that crashes KMail, and I do have better use for my time then searching the web for possible "crashing" mails, remember this is done on my spare time... that's the way it works for khtml, too. and software in general. bugs happen. if the developer can't reproduce there's really no way he can investigate the crash. if we could magically secure against all possible content ever (without degrading the user experience) we could probably solve the spam problem, too. :P and hey, a crash is still a lot better than what'd probably happen on windows - yet another virus. torgny: I've got the full email now, I'll send it to you in a sec. :) While its not a place for a general discussion, I shall allow myself to reply. The issue in question is not "just a bug". The design of the whole thing is broken somehow. I'm using KDE for more than 10 years (since early betas) and I must say, KDE-4 is a worse release ever, by a margin. Stuff that used to work, more or less, in 4.2, is badly broken in 4.4 (I'm not even bothering to file bugs on everything). Some features are conceptually bad and add nothing, but annoyance. And on top of all this, tons of eye-candy and feature creep everywhere (the worst example is kget, which has a bittorrent plugin and what not, but cannot download 3 files from plain http server without getting stuck). In short - at present, the only thing that gives you more security on KDE is a minute user base (so nobody bothers with viruses). I used to recommend people to use KDE-3, but these days the only sane choice for a workstation is Windows (or MacOS for this matter). @Alex: please try to not mixup different things in the same bug report: you can discuss your opinions on KDE, its applications and its problems on forums.kde.org, in the mailing lists or in IRC. Thanks Changing component from "KMail 2" to "kmail", as this is a KMail 1 bug. Probably fixed in KMail 2. *** This bug has been marked as a duplicate of bug 186502 *** |