Bug 249442 - kmail crashes while Locked Screen
Summary: kmail crashes while Locked Screen
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 257123 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-08-29 20:13 UTC by Christian
Modified: 2012-08-19 11:00 UTC (History)
1 user (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 Christian 2010-08-29 20:13:46 UTC
Application: kontact (4.4.5)
KDE Platform Version: 4.4.4 (KDE 4.4.4) "release 2"
Qt Version: 4.6.3
Operating System: Linux 2.6.34-12-desktop x86_64
Distribution: "openSUSE 11.3 (x86_64)"

-- Information about the crash:
Firefox was open this time but idle (no down- or uploads or some other activities).

The crash does not seem to be reproducible.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  0x00007ffed14871a8 in parent (this=0xb8b230, folder=0xbd0700) at /usr/src/debug/kdepim-4.4.4/kmail/kmmsgbase.h:110
#6  KMAcctImap::ignoreJobsForFolder (this=0xb8b230, folder=0xbd0700) at /usr/src/debug/kdepim-4.4.4/kmail/kmacctimap.cpp:231
#7  0x00007ffed15c78e1 in KMSearch::stop (this=0xb7e610) at /usr/src/debug/kdepim-4.4.4/kmail/kmfoldersearch.cpp:235
#8  0x00007ffed15c7f87 in KMFolderSearch::executeSearch (this=0xb2eac0) at /usr/src/debug/kdepim-4.4.4/kmail/kmfoldersearch.cpp:432
#9  0x00007ffed15c9738 in KMFolderSearch::qt_metacall (this=0xb2eac0, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff6929a440) at /usr/src/debug/kdepim-4.4.4/build/kmail/kmfoldersearch.moc:186
#10 0x00007ffee9bf3a1f in QMetaObject::activate (sender=0xbb0010, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3295
#11 0x00007ffee9bf122e in QObject::event (this=0xbb0010, e=0x7fff6929abe0) at kernel/qobject.cpp:1212
#12 0x00007ffee8fd14d4 in QApplicationPrivate::notify_helper (this=0x63f640, receiver=0xbb0010, e=0x7fff6929abe0) at kernel/qapplication.cpp:4302
#13 0x00007ffee8fd9aca in QApplication::notify (this=<value optimized out>, receiver=0xbb0010, e=0x7fff6929abe0) at kernel/qapplication.cpp:4185
#14 0x00007ffeea4c2c06 in KApplication::notify (this=0x7fff6929b020, receiver=0xbb0010, event=0x7fff6929abe0) at /usr/src/debug/kdelibs-4.4.4/kdeui/kernel/kapplication.cpp:302
#15 0x00007ffee9bdfe4c in QCoreApplication::notifyInternal (this=0x7fff6929b020, receiver=0xbb0010, event=0x7fff6929abe0) at kernel/qcoreapplication.cpp:726
#16 0x00007ffee9c0b0c9 in sendEvent (this=0x6447c0) at kernel/qcoreapplication.h:215
#17 QTimerInfoList::activateTimers (this=0x6447c0) at kernel/qeventdispatcher_unix.cpp:618
#18 0x00007ffee9c07ff8 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#19 idleTimerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:231
#20 0x00007ffee1709a93 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#21 0x00007ffee170a270 in ?? () from /usr/lib64/libglib-2.0.so.0
#22 0x00007ffee170a510 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#23 0x00007ffee9c0867f in QEventDispatcherGlib::processEvents (this=0x613220, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#24 0x00007ffee907214e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#25 0x00007ffee9bdf292 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#26 0x00007ffee9bdf495 in QEventLoop::exec (this=0x7fff6929af70, flags=...) at kernel/qeventloop.cpp:201
#27 0x00007ffee9be388b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#28 0x000000000040417e in _start ()

Reported using DrKonqi
Comment 1 Christophe Marin 2011-02-14 15:45:48 UTC
*** Bug 257123 has been marked as a duplicate of this bug. ***
Comment 2 Myriam Schweingruber 2012-08-19 11:00:40 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