Bug 171159 - Kmail crashes after adding new cached IMAP account
Summary: Kmail crashes after adding new cached IMAP account
Status: RESOLVED NOT A BUG
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.10.0
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-16 15:01 UTC by michael papet
Modified: 2008-11-19 15:00 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description michael papet 2008-09-16 15:01:59 UTC
Version:           1.10.0 (using 4.1.00 (KDE 4.1.0), Debian packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.25-2-686

Steps to reproduce this bug:

1. Add new cached imap account to kmail.
2. In security settings, select TLS and some other authentication method unsupported by the server.  There may be another bug here because "Check what the server supports" returns methods that generate an authentication unsupported error.
3. OK/Apply out of the account setup dialog box.
4. Authentication fails.  Hit okay on failure message box.
5. New username/password  box opens for the failed account.  
6. Select the cancel button and kmail/kontact crashes with a signal 6. One chooses the cancel button to go back and fix the account settings... 

I can reproduce this bug always.  I'm using kontact from debian experimental KDE4,

Application: Kontact (kontact), signal SIGABRT
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb4ccc700 (LWP 3517)]
[New Thread 0xb0e10b90 (LWP 3851)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xb7f3e424 in __kernel_vsyscall ()
[Current thread is 0 (LWP 3517)]

Thread 2 (Thread 0xb0e10b90 (LWP 3851)):
#0  0xb7f3e424 in __kernel_vsyscall ()
#1  0xb553c025 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/i686/cmov/libpthread.so.0
#2  0xb6bc769d in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb6d7a4b2 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0xb56ccf32 in ?? () from /usr/lib/libQtNetwork.so.4
#5  0xb6d794a2 in ?? () from /usr/lib/libQtCore.so.4
#6  0xb55384c0 in start_thread () from /lib/i686/cmov/libpthread.so.0
#7  0xb6bb955e in clone () from /lib/i686/cmov/libc.so.6

Thread 1 (Thread 0xb4ccc700 (LWP 3517)):
#0  0xb7f3e424 in __kernel_vsyscall ()
#1  0xb6b74e26 in nanosleep () from /lib/i686/cmov/libc.so.6
#2  0xb6b74c3f in sleep () from /lib/i686/cmov/libc.so.6
#3  0xb7c98678 in ?? () from /usr/lib/libkdeui.so.5
#4  0x00000000 in ?? ()
#0  0xb7f3e424 in __kernel_vsyscall ()
Comment 1 Oliver Putz 2008-09-16 15:47:14 UTC
Hello,

Thanks for your report. Unfortunately your backtrace is not really usable as is. Can you have a look at http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and try to install the debugging packages for your distribution and post a more verbose backtrace?
Comment 2 Christophe Marin 2008-11-19 15:00:40 UTC
No useful backtrace was provided (comment #1). Closing.