Bug 189513 - KMail crashes on Startup
Summary: KMail crashes on Startup
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: 1.11.2
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 227812 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-04-13 10:41 UTC by Dominik Schulz
Modified: 2012-08-19 10:51 UTC (History)
4 users (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 Dominik Schulz 2009-04-13 10:41:57 UTC
Version:            (using KDE 4.2.2)
OS:                Linux
Installed from:    Debian testing/unstable Packages

KMail sometimes crashes on KDE Startup (when KMail is started by KDE).

Steps to Reproduce: None, since it does not happen always. I hope the stacktrace provides enogh information.

Anwendung: KMail (kmail), Signal SIGSEGV
0x00007f669cf288d1 in nanosleep () from /lib/libc.so.6
Current language:  auto; currently c
[Current thread is 0 (LWP 7466)]

Thread 3 (Thread 0x7f6684858950 (LWP 7584)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:217
#1  0x00007f669e3a97d7 in QWaitCondition::wait (this=0x152c888, mutex=0x152c880, time=30000) at thread/qwaitcondition_unix.cpp:85
#2  0x00007f669e39f2f9 in QThreadPoolThread::run (this=0x636170) at concurrent/qthreadpool.cpp:140
#3  0x00007f669e3a8802 in QThreadPrivate::start (arg=0x636170) at thread/qthread_unix.cpp:189
#4  0x00007f6698523faa in start_thread (arg=<value optimized out>) at pthread_create.c:297
#5  0x00007f669cf582cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#6  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f6683c26950 (LWP 7585)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:217
#1  0x00007f669e3a97d7 in QWaitCondition::wait (this=0x152c888, mutex=0x152c880, time=30000) at thread/qwaitcondition_unix.cpp:85
#2  0x00007f669e39f2f9 in QThreadPoolThread::run (this=0x147e870) at concurrent/qthreadpool.cpp:140
#3  0x00007f669e3a8802 in QThreadPrivate::start (arg=0x147e870) at thread/qthread_unix.cpp:189
#4  0x00007f6698523faa in start_thread (arg=<value optimized out>) at pthread_create.c:297
#5  0x00007f669cf582cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#6  0x0000000000000000 in ?? ()
Current language:  auto; currently asm

Thread 1 (Thread 0x7f669ffe7770 (LWP 7466)):
[KCrash Handler]
#5  KMFolder::unGetMsg (this=0x0, idx=-1) at ../../kmail/kmfolder.cpp:372
#6  0x00007f669ed69a56 in KMAcctImap::slotFilterMsg (this=0x9c1710, msg=0x171df60) at ../../kmail/kmacctimap.cpp:616
#7  0x00007f669ed6cf37 in KMAcctImap::qt_metacall (this=0x9c1710, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffa813f2a0) at ./kmacctimap.moc:88
#8  0x00007f669e4a6622 in QMetaObject::activate (sender=0x1726680, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x47fbf52) at kernel/qobject.cpp:3069
#9  0x00007f669eec284f in KMail::FolderJob::messageRetrieved (this=0x0, _t1=0x171df60) at ./folderjob.moc:97
#10 0x00007f669eece5d8 in KMail::ImapJob::slotGetMessageResult (this=0x1726680, job=0x17dc070) at ../../kmail/imapjob.cpp:460
#11 0x00007f669eed18d7 in KMail::ImapJob::qt_metacall (this=0x1726680, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffa813f4e0) at ./imapjob.moc:81
#12 0x00007f669e4a6622 in QMetaObject::activate (sender=0x17dc070, from_signal_index=<value optimized out>, to_signal_index=7, argv=0x47fbf52) at kernel/qobject.cpp:3069
#13 0x00007f669f599e92 in KJob::result (this=0x0, _t1=0x17dc070) at ./kjob.moc:186
#14 0x00007f669f59a20f in KJob::emitResult (this=0x17dc070) at ../../kdecore/jobs/kjob.cpp:294
#15 0x00007f6697586c10 in KIO::SimpleJob::slotFinished (this=0x17dc070) at ../../kio/kio/job.cpp:489
#16 0x00007f6697587e33 in KIO::TransferJob::slotFinished (this=0x17dc070) at ../../kio/kio/job.cpp:966
#17 0x00007f6697588eb5 in KIO::TransferJob::qt_metacall (this=0x17dc070, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffa813f8e0) at ./jobclasses.moc:336
#18 0x00007f669e4a6622 in QMetaObject::activate (sender=0x636550, from_signal_index=<value optimized out>, to_signal_index=8, argv=0x47fbf52) at kernel/qobject.cpp:3069
#19 0x00007f669763e461 in KIO::SlaveInterface::dispatch (this=0x636550, _cmd=104, rawdata=<value optimized out>) at ../../kio/kio/slaveinterface.cpp:175
#20 0x00007f669763afb2 in KIO::SlaveInterface::dispatch (this=0x636550) at ../../kio/kio/slaveinterface.cpp:91
#21 0x00007f669762c1b3 in KIO::Slave::gotInput (this=0x636550) at ../../kio/kio/slave.cpp:322
#22 0x00007f669762e4b8 in KIO::Slave::qt_metacall (this=0x636550, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffa813fd00) at ./slave.moc:75
#23 0x00007f669e4a6622 in QMetaObject::activate (sender=0x14952b0, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x47fbf52) at kernel/qobject.cpp:3069
#24 0x00007f6697552821 in KIO::ConnectionPrivate::dequeue (this=0x14aabe0) at ../../kio/kio/connection.cpp:82
#25 0x00007f6697552c7a in KIO::Connection::qt_metacall (this=0x14952b0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x1d1bb60) at ./connection.moc:72
#26 0x00007f669e4a0c78 in QObject::event (this=0x14952b0, e=0x1748a30) at kernel/qobject.cpp:1118
#27 0x00007f669d8d667d in QApplicationPrivate::notify_helper (this=0x63c9f0, receiver=0x14952b0, e=0x1748a30) at kernel/qapplication.cpp:4084
#28 0x00007f669d8de86a in QApplication::notify (this=0x7fffa8140870, receiver=0x14952b0, e=0x1748a30) at kernel/qapplication.cpp:4049
#29 0x00007f669fb3655b in KApplication::notify (this=0x7fffa8140870, receiver=0x14952b0, event=0x1748a30) at ../../kdeui/kernel/kapplication.cpp:307
#30 0x00007f669e490c4c in QCoreApplication::notifyInternal (this=0x7fffa8140870, receiver=0x14952b0, event=0x1748a30) at kernel/qcoreapplication.cpp:602
#31 0x00007f669e4918ba in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x608370) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#32 0x00007f669e4ba613 in postEventSourceDispatch (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#33 0x00007f669587ef7a in IA__g_main_context_dispatch (context=0x63e220) at /tmp/buildd/glib2.0-2.20.1/glib/gmain.c:1814
#34 0x00007f6695882640 in g_main_context_iterate (context=0x63e220, block=1, dispatch=1, self=<value optimized out>) at /tmp/buildd/glib2.0-2.20.1/glib/gmain.c:2448
#35 0x00007f66958827dc in IA__g_main_context_iteration (context=0x63e220, may_block=1) at /tmp/buildd/glib2.0-2.20.1/glib/gmain.c:2511
#36 0x00007f669e4ba29f in QEventDispatcherGlib::processEvents (this=0x61a980, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:323
#37 0x00007f669d96e74f in QGuiEventDispatcherGlib::processEvents (this=0x0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#38 0x00007f669e48f4f2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -1475082624}) at kernel/qeventloop.cpp:149
#39 0x00007f669e48f8bd in QEventLoop::exec (this=0x7fffa81406c0, flags={i = -1475082544}) at kernel/qeventloop.cpp:200
#40 0x00007f669e491b84 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#41 0x0000000000402f8b in main (argc=<value optimized out>, argv=<value optimized out>) at ../../kmail/main.cpp:146
#0  0x00007f669cf288d1 in nanosleep () from /lib/libc.so.6
Current language:  auto; currently c
Comment 1 Björn Ruberg 2010-03-15 00:24:19 UTC
*** Bug 205309 has been marked as a duplicate of this bug. ***
Comment 2 Björn Ruberg 2010-03-15 00:25:51 UTC
*** Bug 225291 has been marked as a duplicate of this bug. ***
Comment 3 Björn Ruberg 2010-03-15 00:26:11 UTC
*** Bug 227812 has been marked as a duplicate of this bug. ***
Comment 4 Myriam Schweingruber 2012-08-19 10:51:46 UTC
Thank you for your report. Kmail1 is currently unmaintained and the code has changed sufficiently in Kmail2 so the backtraces are not really useful anymore. Should you experience the same crash in Kmail 4.8.5 or later, please open a new report for Kmail2. Thank you for your understanding