Version:           4.7 (using KDE 4.7.2) 
OS:                Linux

On a new system, KMail Account Wizard crashed when creating an IMAP account, probably because of a duplicate account "IMAP-Konto 3", when out of nowhere some undefined bogus accounts named "IMAP-Konto 3" (sic!), "IMAP-Konto 4" and "IMAP-Konto 5" appeared in the account list.

For some reason, the crash information remained "unusable" even after installing the debug symbols:

Application: Konten-Assistent (accountwizard), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f59121a5780 (LWP 4373))]

Thread 3 (Thread 0x7f58fe19c700 (LWP 4391)):
#0  0xffffffffff60017b in ?? ()
#1  0x00007f58fe19baf0 in ?? ()
#2  0x00007fff922647e7 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 2 (Thread 0x7f58fc933700 (LWP 4405)):
#0  0x00007f590d25d04c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0
#1  0x00007f590cadefe2 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x00007f590cadf019 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x00007f590d258efc in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#4  0x00007f590dfd789d in clone () from /lib/x86_64-linux-gnu/libc.so.6
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f59121a5780 (LWP 4373)):
[KCrash Handler]
#6  0x000000000043c803 in _start ()


Reproducible: Didn't try

Steps to Reproduce:
These bogus accounts seem to appear quite often with the Akonadi implementation of KDEPIM 2. However it remains unclear, why the wizard didn't just count up and called the new account "IMAP-Konto 6".

Actual Results:  
The new IMAP-Account was correctly configured, while the SMTP account wasn't even though the information had already been collected.
After removing the duplicate "IMAP-Konto 3" account, the account correctly worked.

Expected Results:  
No crash. No duplicate bogus accounts. The SMTP account being configured as well.