Bug 259392 - Could not send messages when "automatic" encoding is selected
Summary: Could not send messages when "automatic" encoding is selected
Status: RESOLVED DUPLICATE of bug 259391
Alias: None
Product: kmail2
Classification: Applications
Component: composer (show other bugs)
Version: 2.0.89
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-10 01:32 UTC by Jakub Schmidtke
Modified: 2010-12-12 15:47 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jakub Schmidtke 2010-12-10 01:32:39 UTC
Version:           2.0.89
OS:                Linux

When I compose a new message and try to send it, I get following error twice:
"Could not compose message: No charsets were available for encoding. Please report this bug.". When I click OK it appears again, and after next 'OK' it's gone. But the message is not sent.
I added several encodings to the list of supported charsets in kmail's configuration, but it didn't help.
What helped was changing the encoding from 'default' to anything else.
But I can't find a way to set it permanently to something else, so I have to do this every time I compose a new email.


Reproducible: Always

Steps to Reproduce:
Create a new message, try to send it.



OS: Linux (x86_64) release 2.6.36-ARCH
Compiler: gcc
Comment 1 Tobias Koenig 2010-12-12 15:47:54 UTC
Hej Jakub,

that's a different symptom for the same bug, default settings seems not to be migrated/initialized correctly. So I'll close this one as duplicate. See my quetsion in the other bug report.

Ciao,
Tobias

*** This bug has been marked as a duplicate of bug 259391 ***