Bug 214471 - Kmail crashes when trying to move messages between folders within an imap account
Summary: Kmail crashes when trying to move messages between folders within an imap acc...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 219698 221198 223722 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-11-14 02:01 UTC by Ralph Janke
Modified: 2012-08-19 10:53 UTC (History)
4 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 Ralph Janke 2009-11-14 02:01:30 UTC
Application that crashed: kmail
Version of the application: 1.12.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-14-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
 

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#6  KMFolder::isOpened (this=0x9ade480) at ../../kmail/kmfolder.cpp:560
#7  0x00f4dba2 in KMCommand::slotPostTransfer (this=0xbfbe27b4, result=176886012) at ../../kmail/kmcommands.cpp:274
#8  0x00f5815f in KMCommand::qt_metacall (this=0x9ade480, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfbe2988) at ./kmcommands.moc:87
#9  0x00f6a5fa in KMMoveCommand::qt_metacall (this=0x9ade480, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfbe2988) at ./kmcommands.moc:1706
#10 0x00774263 in QMetaObject::activate (sender=0x9ade480, from_signal_index=4, to_signal_index=4, argv=0xbfbe2988) at kernel/qobject.cpp:3113
#11 0x00774ec2 in QMetaObject::activate (sender=0x9ade480, m=0x1386634, local_signal_index=0, argv=0xbfbe2988) at kernel/qobject.cpp:3187
#12 0x00f49bd3 in KMCommand::messagesTransfered (this=0x9ade480, _t1=KMCommand::OK) at ./kmcommands.moc:102
#13 0x00f67156 in KMCommand::transferSelectedMsgs (this=0x9ade480) at ../../kmail/kmcommands.cpp:368
#14 0x00f673a2 in KMCommand::slotStart (this=0x9ade480) at ../../kmail/kmcommands.cpp:266
#15 0x00f5813b in KMCommand::qt_metacall (this=0x9ade480, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfbe2b8c) at ./kmcommands.moc:86
#16 0x00f6a5fa in KMMoveCommand::qt_metacall (this=0x9ade480, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfbe2b8c) at ./kmcommands.moc:1706
#17 0x00774263 in QMetaObject::activate (sender=0x91abd10, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#18 0x00774ec2 in QMetaObject::activate (sender=0x91abd10, m=0x84e908, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#19 0x00779387 in QSingleShotTimer::timeout (this=0x91abd10) at .moc/release-shared/qtimer.moc:76
#20 0x0077949c in QSingleShotTimer::timerEvent (this=0x91abd10) at kernel/qtimer.cpp:298
#21 0x0076e3bf in QObject::event (this=0x91abd10, e=0xbfbe3020) at kernel/qobject.cpp:1075
#22 0x031bbf54 in QApplicationPrivate::notify_helper (this=0x8eb3cb0, receiver=0x91abd10, e=0xbfbe3020) at kernel/qapplication.cpp:4056
#23 0x031c367c in QApplication::notify (this=0xbfbe3420, receiver=0x91abd10, e=0xbfbe3020) at kernel/qapplication.cpp:3603
#24 0x00a2bbfa in KApplication::notify (this=0xbfbe3420, receiver=0x91abd10, event=0xbfbe3020) at ../../kdeui/kernel/kapplication.cpp:302
#25 0x0075e6cb in QCoreApplication::notifyInternal (this=0xbfbe3420, receiver=0x91abd10, event=0xbfbe3020) at kernel/qcoreapplication.cpp:610
#26 0x0078b7ce in QCoreApplication::sendEvent (this=0x8eac6b4) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#27 QTimerInfoList::activateTimers (this=0x8eac6b4) at kernel/qeventdispatcher_unix.cpp:572
#28 0x007890e0 in timerSourceDispatch (source=0x8eac680) at kernel/qeventdispatcher_glib.cpp:165
#29 0x022d4e78 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#30 0x022d8720 in ?? () from /lib/libglib-2.0.so.0
#31 0x022d8853 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#32 0x0078902c in QEventDispatcherGlib::processEvents (this=0x8e85180, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#33 0x0325cbe5 in QGuiEventDispatcherGlib::processEvents (this=0x8e85180, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#34 0x0075cc79 in QEventLoop::processEvents (this=0xbfbe32e4, flags=) at kernel/qeventloop.cpp:149
#35 0x0075d0ca in QEventLoop::exec (this=0xbfbe32e4, flags=...) at kernel/qeventloop.cpp:201
#36 0x0075f53f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#37 0x031bbdd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#38 0x0804a702 in main (argc=3, argv=0xbfbe35d4) at ../../kmail/main.cpp:146

Reported using DrKonqi
Comment 1 Björn Ruberg 2010-03-10 23:38:28 UTC
*** Bug 221198 has been marked as a duplicate of this bug. ***
Comment 2 Björn Ruberg 2010-03-14 01:20:38 UTC
*** Bug 223722 has been marked as a duplicate of this bug. ***
Comment 3 Christophe Marin 2010-03-28 05:07:37 UTC
*** Bug 219698 has been marked as a duplicate of this bug. ***
Comment 4 Myriam Schweingruber 2012-08-19 10:53:23 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