Summary: | kmail is crashing when replying using L with a « Could not compose message: No charsets were available for encoding. Please report this bug.» | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Balcaen John <balcaen.john> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | a.vanloon, jacob, tokoe |
Priority: | NOR | ||
Version: | 2.0.89 | ||
Target Milestone: | --- | ||
Platform: | Mandriva RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Balcaen John
2010-09-18 13:29:31 UTC
The exact sentence is in fact: « Could not compose message: No charsets were available for encoding. Please report this bug. » I can reproduce it all the time using simply in fact reply to this mailing list In fact i need to specify UTF-8 Encoding to be able to sent the mail, if i'm using something else it's crashing, for example choosing us-ascii prompt a pop up saying : Encoding the message with us-ascii will lose some characters. Do you want to continue? & if i accept to loose characters it's crashing. Hej, can you still reproduce this issue with current version (4.6beta)? The message about missing charsets can be caused by an empty 'pref-charsets' entry in $HOME/.kde/share/config/kmail2rc in the [Composer] section. Just remove this entry and the defaults will be used again -> sending should work out of the box. If you can reproduce the crash nevertheless, can you attach the console output of kmail when it is crashing, please? Ciao, Tobias I can't reproduce anymore by removing the empty pref-charsets as suggested. Sorry for the delay. Tests are done on kdepim beta2 (4.5.85) Regards, I also encountered this bug when I got the message 'No charsets were available for encoding'. However, it did not crash KMail if I remember correctly, all it did was refuse to save the e-mail as a Draft, KMail didn't stop working. Following the instruction to remove the 'pref-charsets' entry in $HOME/.kde/share/config/kmail2rc in the [Composer] section and starting Kontact again fixed it for me. However, this is on Kontact 4.6 beta 3. This is very fresh because I installed Kubuntu 10.10 today and immediately used Kubuntu's repositories to upgrade to KDE PIM 4.6 beta 3, so I didn Last sentence got eaten somehow, I wanted to say: so I didn't use any earlier beta. Unfortunately I haven't been able to reproduce it so far. Same as above comment, now running Kmail 2.0.89. Removing the line in kmail2rc worked, but it needs to be done automatically. |