Bug 182291 - KMail crashes when cleaning trash: signal SIGABRT
Summary: KMail crashes when cleaning trash: signal SIGABRT
Status: RESOLVED DUPLICATE of bug 174839
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: 1.11.0
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-29 12:28 UTC by bou.gui
Modified: 2009-03-19 00:40 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 bou.gui 2009-01-29 12:28:43 UTC
Version:           1.11.0 (using 4.2.00 (KDE 4.2.0), Debian packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.26-1-686

Yesterday, with my first use of 1.11.0, KMail crashes when i try to clean it's trash.

Here is more information :

Application : KMail (kmail), signal SIGABRT
[Current thread is 0 (LWP 3627)]

Thread 3 (Thread 0xb0bd1b90 (LWP 3636)):
#0  0xb7eeb424 in __kernel_vsyscall ()
#1  0xb5589025 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0
#2  0xb63957fd in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb6e54542 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0xb5fc6312 in ?? () from /usr/lib/libQtNetwork.so.4
#5  0xb6e5352e in ?? () from /usr/lib/libQtCore.so.4
#6  0xb55854c0 in start_thread () from /lib/i686/cmov/libpthread.so.0
#7  0xb63876de in clone () from /lib/i686/cmov/libc.so.6

Thread 2 (Thread 0xb02a3b90 (LWP 3643)):
#0  0xb7eeb424 in __kernel_vsyscall ()
#1  0xb637fab1 in select () from /lib/i686/cmov/libc.so.6
#2  0xb6f22670 in ?? () from /usr/lib/libQtCore.so.4
#3  0xb6e5352e in ?? () from /usr/lib/libQtCore.so.4
#4  0xb55854c0 in start_thread () from /lib/i686/cmov/libpthread.so.0
#5  0xb63876de in clone () from /lib/i686/cmov/libc.so.6

Thread 1 (Thread 0xb405baa0 (LWP 3627)):
#0  0xb7eeb424 in __kernel_vsyscall ()
#1  0xb6342ef6 in nanosleep () from /lib/i686/cmov/libc.so.6
#2  0xb6342d0f in sleep () from /lib/i686/cmov/libc.so.6
#3  0xb7d90fd8 in ?? () from /usr/lib/libkdeui.so.5
#4  0x00000000 in ?? ()
Comment 1 Dario Andres 2009-01-29 15:01:11 UTC
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Thanks :)
Comment 2 Poborskiii 2009-01-30 20:22:57 UTC
I have the same problem, but before crash I had several failed attempts of emptying trash.
Comment 3 Jonathan Marten 2009-02-11 13:44:20 UTC
Reliably reproducible with current trunk.
Backtrace after crash:

Application: KMail (kmail), signal SIGABRT
Using host libthread_db library "/lib/libthread_db.so.1".

Thread 1 (Thread 0xb3e736d0 (LWP 12189)):
[KCrash Handler]
#6  0xb8080424 in __kernel_vsyscall ()
#7  0xb5e78101 in raise () from /lib/libc.so.6
#8  0xb5e798e8 in abort () from /lib/libc.so.6
#9  0xb6c36f26 in qt_message_output (msgType=QtFatalMsg,
    buf=0x840b260 "ASSERT: \"mCurrentItemToRestoreAfterViewItemJobStep->isViewable()\" in file /ws/trunk/kdepim-trunk/kmail/messagelistview/core/model.cpp, line 3788") at global/qglobal.cpp:2001
#10 0xb6c374be in qFatal (msg=0xb6de81a8 "ASSERT: \"%s\" in file %s, line %d") at global/qglobal.cpp:2196
#11 0xb6c379f5 in qt_assert (assertion=0xb7a04ab0 "mCurrentItemToRestoreAfterViewItemJobStep->isViewable()", file=0xb7a0468c "/ws/trunk/kdepim-trunk/kmail/messagelistview/core/model.cpp", line=3788)
    at global/qglobal.cpp:1772
#12 0xb790645b in KMail::MessageListView::Core::Model::viewItemJobStep (this=0x8286a28) at /ws/trunk/kdepim-trunk/kmail/messagelistview/core/model.cpp:3788
#13 0xb756f052 in KMail::MessageListView::Core::Model::qt_metacall (this=0x8286a28, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbff9b7c8)
    at /ws/BUILD.keelhaul/kdepim-trunk-BUILD/kmail/moc_model.cpp:76
#14 0xb6da1502 in QMetaObject::activate (sender=0x8211058, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3061
#15 0xb6da1c85 in QMetaObject::activate (sender=0x8211058, m=0xb6e4b9c4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3136
#16 0xb6de75e5 in QTimer::timeout (this=0x8211058) at .moc/debug-shared/moc_qtimer.cpp:128
#17 0xb6daaf70 in QTimer::timerEvent (this=0x8211058, e=0xbff9bc94) at kernel/qtimer.cpp:256
#18 0xb6d9bb5b in QObject::event (this=0x8211058, e=0xbff9bc94) at kernel/qobject.cpp:1077
#19 0xb61e6bd1 in QApplicationPrivate::notify_helper (this=0x8070dc8, receiver=0x8211058, e=0xbff9bc94) at kernel/qapplication.cpp:4051
#20 0xb61e770e in QApplication::notify (this=0xbff9c058, receiver=0x8211058, e=0xbff9bc94) at kernel/qapplication.cpp:3598
#21 0xb7ed0c17 in KApplication::notify (this=0xbff9c058, receiver=0x8211058, event=0xbff9bc94) at /ws/trunk/kdelibs-trunk/kdeui/kernel/kapplication.cpp:307
#22 0xb6d87b3d in QCoreApplication::notifyInternal (this=0xbff9c058, receiver=0x8211058, event=0xbff9bc94) at kernel/qcoreapplication.cpp:590
#23 0xb6dbe038 in QTimerInfoList::activateTimers (this=0x80715ec) at kernel/qcoreapplication.h:208
#24 0xb6dbf16c in QEventDispatcherUNIX::processEvents (this=0x8070da8, flags=@0xbff9bec8) at kernel/qeventdispatcher_unix.cpp:903
#25 0xb628e6e4 in QEventDispatcherX11::processEvents (this=0x8070da8, flags=@0xbff9befc) at kernel/qeventdispatcher_x11.cpp:147
#26 0xb6d87041 in QEventLoop::processEvents (this=0xbff9bf60, flags=@0xbff9bf38) at kernel/qeventloop.cpp:144
#27 0xb6d871da in QEventLoop::exec (this=0xbff9bf60, flags=@0xbff9bf68) at kernel/qeventloop.cpp:191
#28 0xb6d8980a in QCoreApplication::exec () at kernel/qcoreapplication.cpp:872
#29 0xb61e4e74 in QApplication::exec () at kernel/qapplication.cpp:3526
#30 0x0804a84d in main (argc=) at /ws/trunk/kdepim-trunk/kmail/main.cpp:146
Comment 4 Jonathan Marten 2009-02-11 16:28:51 UTC
The same crash and backtrace happens when using "Move all messages to the trash" in any other folder.
Comment 5 Jaime Torres 2009-02-11 17:22:18 UTC
As the backtraces are the same, this bug is marked as a duplicate.

Thank you for taking the time to report this bug and helping to make KDE better. This particular bug has already been reported and is a duplicate of bug 174839, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

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