Bug 182394

Summary: Crash report: downloading mail
Product: [Applications] kmail Reporter: envite
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED REMIND    
Severity: crash CC: andresbajotierra, Wurm.Ch
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed In:

Description envite 2009-01-30 10:38:16 UTC
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    Debian testing/unstable Packages

Just started to work (2 IMAP accounts and 3 POP accounts)

Good hunt!

Aplicación: KMail (kmail), señal SIGSEGV
[Current thread is 0 (LWP 5642)]

Thread 4 (Thread 0xb04b1b90 (LWP 5665)):
#0  0xb7f84424 in __kernel_vsyscall ()
#1  0xb561b025 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0
#2  0xb64277fd in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb6ee6542 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0xb5977bbb in ?? () from /usr/lib/libthreadweaver.so.4
#5  0x09fa6d48 in ?? ()
#6  0x0a046ed8 in ?? ()
#7  0xffffffff in ?? ()
#8  0x00000010 in ?? ()
#9  0x0a02db00 in ?? ()
#10 0x00000000 in ?? ()

Thread 3 (Thread 0xb0d6bb90 (LWP 5688)):
#0  0xb7f84424 in __kernel_vsyscall ()
#1  0xb6411ab1 in select () from /lib/i686/cmov/libc.so.6
#2  0xb6fb4660 in ?? () from /usr/lib/libQtCore.so.4
#3  0xb6ee552e in ?? () from /usr/lib/libQtCore.so.4
#4  0xb56174c0 in start_thread () from /lib/i686/cmov/libpthread.so.0
#5  0xb64196de in clone () from /lib/i686/cmov/libc.so.6

Thread 2 (Thread 0xacffbb90 (LWP 6415)):
#0  0xb7f84424 in __kernel_vsyscall ()
#1  0xb561b025 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0
#2  0xb64277fd in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb6ee6542 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0xb5977bbb in ?? () from /usr/lib/libthreadweaver.so.4
#5  0x09fa6d48 in ?? ()
#6  0x0a046ed8 in ?? ()
#7  0xffffffff in ?? ()
#8  0x00000010 in ?? ()
#9  0x0a02db00 in ?? ()
#10 0x00000000 in ?? ()

Thread 1 (Thread 0xb40efaa0 (LWP 5642)):
#0  0xb7f84424 in __kernel_vsyscall ()
#1  0xb63d4ef6 in nanosleep () from /lib/i686/cmov/libc.so.6
#2  0xb63d4d0f in sleep () from /lib/i686/cmov/libc.so.6
#3  0xb7e22fd8 in ?? () from /usr/lib/libkdeui.so.5
#4  0x00000000 in ?? ()
Comment 1 Christoph Wurm 2009-01-30 22:01:32 UTC
Thanks for taking the time to report this bug.
Unfortunately, that backtrace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. 
Can you get us a backtrace with debugging symbols? 
Please see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports for more information on how to do so. 

Thanks in advance!
Comment 2 envite 2009-01-30 22:50:15 UTC
I would like, but it depends on it happening again. This is not a testing system, but (would be) a production one.

I've installed the -dbg packages, but if I get another crash I will file a new bug, since I cann not be sure if it happens by the same cause.

Thanks to you all
Comment 3 Dario Andres 2009-01-31 14:46:48 UTC
Reopen this bug report when you experience the crash again. Thanks for reporting :)
Comment 4 Dario Andres 2009-06-05 15:35:34 UTC
Any news on this? Thanks