| Summary: | KMail(Kontact) crashed while staying deactive on the background [KMKernel::config, KMKernel::slotRunBackgroundTasks] | ||
|---|---|---|---|
| Product: | [Unmaintained] kmail | Reporter: | radek novotny <rak> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | crash | CC: | andresbajotierra, btunell, charlesopondo, ea.grassete, helgast, k17031965, kde, maarten.vanraes, mark, mirceasava, noway, pauli84, philippe.cheval, seanbarman, vkrevs |
| Priority: | NOR | ||
| Version: | 1.12.0 | ||
| Target Milestone: | --- | ||
| Platform: | Unlisted Binaries | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
||
Do you think you would be able to get this crash again ? If you do, then you can install the "kdepim-dbg" package in order to get a complete backtrace the next time the crash happens. Thanks! *** Bug 204130 has been marked as a duplicate of this bug. *** *** Bug 204901 has been marked as a duplicate of this bug. *** *** Bug 205674 has been marked as a duplicate of this bug. *** *** Bug 209360 has been marked as a duplicate of this bug. *** *** Bug 212033 has been marked as a duplicate of this bug. *** *** Bug 212414 has been marked as a duplicate of this bug. *** *** Bug 215374 has been marked as a duplicate of this bug. *** *** Bug 220880 has been marked as a duplicate of this bug. *** From bug 212414: --- Version of the application: 4.3.2 [KCrash Handler] #6 0xb06f1c70 in KMKernel::config () at /usr/src/debug/kdepim-4.3.2/kmail/kmkernel.cpp:2154 #7 0xb06f2c29 in KMKernel::slotRunBackgroundTasks (this=0x82e1998) at /usr/src/debug/kdepim-4.3.2/kmail/kmkernel.cpp:2207 #8 0xb07043e8 in KMKernel::qt_metacall (this=0x82e1998, _c=QMetaObject::InvokeMetaMethod, _id=40, _a=0xbfc8fd68) at /usr/src/debug/kdepim-4.3.2/build/kmail/kmkernel.moc:226 ... From bug 220880: --- Kontact crashed sometimes reload of old session From bug 226808: -- What I was doing when the application crashed: At start it is telling me that another instance of Kontact is already running, but none can be seen.This happens at least often.Most of the time it happens when i switch to another application such as Firefox. *** Bug 226808 has been marked as a duplicate of this bug. *** *** Bug 238228 has been marked as a duplicate of this bug. *** *** Bug 250828 has been marked as a duplicate of this bug. *** Created attachment 53172 [details]
New crash information added by DrKonqi
kontact (4.4.6) on KDE Platform 4.5.2 (KDE 4.5.2) using Qt 4.7.0
- What I was doing when the application crashed:
I wasn't using the application directly, it was running in the background - it was only visible as an icon in the system tray. Also at startup the application is being launched twice.
- Custom settings of the application:
I'm using the IMAP and SMTP protocols and the aplication is set to run continuously in the system tray and show new messages as they arrive.
-- Backtrace (Reduced):
#7 operator bool () at /usr/include/kde4/ksharedptr.h:106
#8 KMKernel::config () at /usr/src/debug/kdepim-4.4.6/kmail/kmkernel.cpp:2321
#9 0xb331c6b6 in KMKernel::slotRunBackgroundTasks (this=0x851e5b8) at /usr/src/debug/kdepim-4.4.6/kmail/kmkernel.cpp:2380
#10 0xb33277e1 in KMKernel::qt_metacall (this=0x851e5b8, _c=QMetaObject::InvokeMetaMethod, _id=44, _a=0xbfc7042c) at /usr/src/debug/kdepim-4.4.6/i686-redhat-linux-gnu/kmail/kmkernel.moc:242
[...]
[...]
#13 0x013d77d8 in QTimer::timeout (this=0x858d270) at .moc/release-shared/moc_qtimer.cpp:134
Created attachment 56629 [details]
New crash information added by DrKonqi
kontact (4.4.9) on KDE Platform 4.6.00 (4.6.0) using Qt 4.7.0
- What I was doing when the application crashed: Logging in.
- Unusual behavior I noticed: Kontact opens two instances. When one is closed the other is unable to retrieve mail, and crashed a little while later.
-- Backtrace (Reduced):
#7 0xb311f6a3 in operator bool () at /usr/include/ksharedptr.h:106
#8 KMKernel::config () at ../../kmail/kmkernel.cpp:2320
#9 0xb31203f5 in KMKernel::slotRunBackgroundTasks (this=0x9f101e8) at ../../kmail/kmkernel.cpp:2379
#10 0xb3133ec3 in KMKernel::qt_metacall (this=0x9f101e8, _c=QMetaObject::InvokeMetaMethod, _id=44, _a=0xbfe66f5c) at ./kmkernel.moc:242
[...]
#13 0x01b7f1e7 in QTimer::timeout (this=0x9fc6a80) at .moc/release-shared/moc_qtimer.cpp:134
*** Bug 265538 has been marked as a duplicate of this bug. *** 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 |
Application that crashed: kontact Version of the application: 4.3.0 rc2 KDE Version: 4.2.96 (KDE 4.2.96 (KDE 4.3 RC2)) Qt Version: 4.5.0 Operating System: Linux 2.6.28-14-generic x86_64 Distribution: Ubuntu 9.04 What I was doing when the application crashed: kmail crashed while staying deactive/maybe minimized on the background. kde 4.3 rc2. kmail configured with pop3, imap, rss. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #5 0x00007f306c7d035f in KMKernel::config () from /usr/lib/libkmailprivate.so.4 #6 0x00007f306c7d122e in KMKernel::slotRunBackgroundTasks () from /usr/lib/libkmailprivate.so.4 #7 0x00007f306c7e26b5 in KMKernel::qt_metacall () from /usr/lib/libkmailprivate.so.4 #8 0x00007f307f2bb1f2 in QMetaObject::activate (sender=0x1bad3c0, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x7fff8cde05f0) at kernel/qobject.cpp:3069 #9 0x00007f307f2b54d3 in QObject::event (this=0x1bad3c0, e=0x0) at kernel/qobject.cpp:1082 #10 0x00007f307fe5e78d in QApplicationPrivate::notify_helper (this=0x15b59c0, receiver=0x1bad3c0, e=0x7fff8cde0ca0) at kernel/qapplication.cpp:4084 #11 0x00007f307fe6697a in QApplication::notify (this=0x7fff8cde0ff0, receiver=0x1bad3c0, e=0x7fff8cde0ca0) at kernel/qapplication.cpp:4049 #12 0x00007f308129663b in KApplication::notify (this=0x7fff8cde0ff0, receiver=0x1bad3c0, event=0x7fff8cde0ca0) at /build/buildd/kde4libs-4.2.96/kdeui/kernel/kapplication.cpp:302 #13 0x00007f307f2a575c in QCoreApplication::notifyInternal (this=0x7fff8cde0ff0, receiver=0x1bad3c0, event=0x7fff8cde0ca0) at kernel/qcoreapplication.cpp:602 #14 0x00007f307f2d27f6 in QTimerInfoList::activateTimers (this=0x15b0620) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #15 0x00007f307f2cef0d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:164 #16 0x00007f30789db20a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #17 0x00007f30789de8e0 in ?? () from /usr/lib/libglib-2.0.so.0 #18 0x00007f30789dea7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #19 0x00007f307f2cee6f in QEventDispatcherGlib::processEvents (this=0x15860a0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:323 #20 0x00007f307fef6bef in QGuiEventDispatcherGlib::processEvents (this=0x1b7de60, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #21 0x00007f307f2a4002 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -1931604208}) at kernel/qeventloop.cpp:149 #22 0x00007f307f2a43cd in QEventLoop::exec (this=0x7fff8cde0f50, flags={i = -1931604128}) at kernel/qeventloop.cpp:200 #23 0x00007f307f2a6694 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880 #24 0x0000000000404945 in _start () Reported using DrKonqi