Bug 215514 - crash while trying to save attachment (in offline mode)
Summary: crash while trying to save attachment (in offline mode)
Status: RESOLVED WORKSFORME
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:
: 216917 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-11-21 03:26 UTC by Tim Richardson
Modified: 2010-03-07 09:32 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 Tim Richardson 2009-11-21 03:26:44 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.3
Operating System: Linux 2.6.31-6.slh.2-sidux-686 i686
Distribution: Debian GNU/Linux unstable (sid)

What I was doing when the application crashed:
I switched to offline mode while not having a connection. From the message list I tried the option save attachments, and crash

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#6  QBasicAtomicInt::ref (this=0x973a778) at /usr/include/qt4/QtCore/qatomic_i386.h:120
#7  QList (this=0x973a778) at /usr/include/qt4/QtCore/qlist.h:111
#8  KMail::FolderJob::msgList (this=0x973a778) at ../../kmail/folderjob.cpp:120
#9  0xb6c0da4b in KMAcctImap::ignoreJobsForMessage (this=0x8fbad68, msg=0x950dea8) at ../../kmail/kmacctimap.cpp:215
#10 0xb6c249f5 in KMFolderImap::ignoreJobsForMessage (this=0x8f902a0, msg=0x950dea8) at ../../kmail/kmfolderimap.cpp:1564
#11 0xb6b4737b in KMFolder::ignoreJobsForMessage (this=0x8fe6818, m=0x950dea8) at ../../kmail/kmfolder.cpp:388
#12 0xb6d38784 in KMCommand::transferSelectedMsgs (this=0x94e6000) at ../../kmail/kmcommands.cpp:334
#13 0xb6d38d03 in KMCommand::slotStart (this=0x94e6000) at ../../kmail/kmcommands.cpp:266
#14 0xb6d2987b in KMCommand::qt_metacall (this=0x94e6000, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbf8059f8) at ./kmcommands.moc:86
#15 0xb6d3798a in KMSaveAttachmentsCommand::qt_metacall (this=0x94e6000, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbf8059f8) at ./kmcommands.moc:794
#16 0xb67d7303 in QMetaObject::activate (sender=0x94cf0d0, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112
#17 0xb67d7f42 in QMetaObject::activate (sender=0x94cf0d0, m=0xb68b2d88, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186
#18 0xb67dd007 in QSingleShotTimer::timeout (this=0x94cf0d0) at .moc/release-shared/qtimer.moc:76
#19 0xb67dd12c in QSingleShotTimer::timerEvent (this=0x94cf0d0) at kernel/qtimer.cpp:298
#20 0xb67d239f in QObject::event (this=0x94cf0d0, e=0xbf805e7c) at kernel/qobject.cpp:1074
#21 0xb5e01a94 in QApplicationPrivate::notify_helper (this=0x8e553d8, receiver=0x94cf0d0, e=0xbf805e7c) at kernel/qapplication.cpp:4065
#22 0xb5e09bee in QApplication::notify (this=0xbf806198, receiver=0x94cf0d0, e=0xbf805e7c) at kernel/qapplication.cpp:3605
#23 0xb75670fd in KApplication::notify (this=0xbf806198, receiver=0x94cf0d0, event=0xbf805e7c) at ../../kdeui/kernel/kapplication.cpp:302
#24 0xb67c21eb in QCoreApplication::notifyInternal (this=0xbf806198, receiver=0x94cf0d0, event=0xbf805e7c) at kernel/qcoreapplication.cpp:610
#25 0xb67f0e21 in QCoreApplication::sendEvent (this=0x8e16234) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#26 QTimerInfoList::activateTimers (this=0x8e16234) at kernel/qeventdispatcher_unix.cpp:580
#27 0xb67ed317 in timerSourceDispatch (source=0x8e16270) at kernel/qeventdispatcher_glib.cpp:184
#28 idleTimerSourceDispatch (source=0x8e16270) at kernel/qeventdispatcher_glib.cpp:231
#29 0xb3f12e98 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#30 0xb3f16623 in ?? () from /lib/libglib-2.0.so.0
#31 0xb3f167a8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#32 0xb67ed041 in QEventDispatcherGlib::processEvents (this=0x8dec900, flags=...) at kernel/qeventdispatcher_glib.cpp:407
#33 0xb5ea1305 in QGuiEventDispatcherGlib::processEvents (this=0x8dec900, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#34 0xb67c083a in QEventLoop::processEvents (this=0xbf8060a0, flags=...) at kernel/qeventloop.cpp:149
#35 0xb67c0c82 in QEventLoop::exec (this=0xbf8060a0, flags=...) at kernel/qeventloop.cpp:201
#36 0xb67c30d9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#37 0xb5e01917 in QApplication::exec () at kernel/qapplication.cpp:3525
#38 0x0804a6d0 in main (argc=0, argv=0x0) at ../../kmail/main.cpp:146

Reported using DrKonqi
Comment 1 FiNeX 2009-12-01 17:42:15 UTC
*** Bug 216917 has been marked as a duplicate of this bug. ***
Comment 2 Björn Ruberg 2009-12-12 00:29:11 UTC
I cannot reproduce your bug. Can you reproduce it and help me?
Comment 3 Tim Richardson 2009-12-12 02:49:15 UTC
My distribution just upgraded to KDE 4.3.4. I'll see if I can reproduce this bug over the next week.
Comment 4 Björn Ruberg 2010-03-06 23:56:37 UTC
Did you have any luck?
Comment 5 Tim Richardson 2010-03-07 09:25:39 UTC
Can not reproduce
Comment 6 Björn Ruberg 2010-03-07 09:32:58 UTC
Then I'm closing this. Sadly, developers can hardly fix something they cannot see. Maybe there even was some other problem that had nothing to do with kmail.