| Summary: | bogus "body is binary but used as text" complaints | ||
|---|---|---|---|
| Product: | [Unmaintained] kmail | Reporter: | mi+kde |
| Component: | general | Assignee: | kdepim bugs <pim-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | kde |
| Priority: | NOR | ||
| Version First Reported In: | 1.6.2 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | FreeBSD | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
mi+kde
2004-06-18 00:16:03 UTC
Something similar happens to me too, with 1.6.1/3.2.1 on FreeBSD 4-something. I also haven't worked out exactly which mails provoke this behaviour, but it certainly isn't only vi recovery ones. I'm getting the warning twice on every mail message I get from the python-dev list. The KMail version of KDE 3.3.0 is crashing on some e-mails. It prints the following messages to stdout: kmail: WARNING: KMMessagePart::bodyDecoded(): body is binary but used as text! kmail: WARNING: KMMessagePart::bodyDecoded(): body is binary but used as text! kmail: WARNING: KMMessagePart::bodyDecoded(): body is binary but used as text! kmail: WARNING: KMMessagePart::bodyDecoded(): body is binary but used as text! kmail: WARNING: KMMessagePart::bodyDecoded(): body is binary but used as text! kmail: WARNING: KMMessagePart::bodyDecoded(): body is binary but used as text! QGDict::hashKeyString: Invalid null key kioslave: ####### CRASH ###### protocol = newimap pid = 1830 signal = 11 Please attach one of the messages that crash. KDE-PIM bugs day: cannot reproduce, many versions ago, information requested but none provided. Closing. |