Bug 188641 - kontact crashes in background with signal 6
Summary: kontact crashes in background with signal 6
Status: RESOLVED NOT A BUG
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Unspecified
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-02 09:37 UTC by bve
Modified: 2009-10-23 10:37 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
kcrash backtrace with "kdepim-dbg" (3.93 KB, application/octet-stream)
2009-04-15 10:03 UTC, Jens Schmidt
Details

Note You need to log in before you can comment on or make changes to this bug.
Description bve 2009-04-02 09:37:42 UTC
Version:            (using KDE 4.1.4)
Installed from:    Ubuntu Packages

Kontact crashes while running with kmail in the background. Didn't do anything. One pop3 without regular checking and one disconnected IMAP with regular  checking are set up. Happened twice today, so might be reproducable. 

Backtrace:
Anwendung: Kontact (kontact), Signal SIGABRT
0x00007f47f9c0c6b0 in nanosleep () from /lib/libc.so.6

Thread 1 (Thread 0x7f47fc5446f0 (LWP 7687)):
[KCrash Handler]
#5  0x00007f47f9b97015 in raise () from /lib/libc.so.6
#6  0x00007f47f9b98b83 in abort () from /lib/libc.so.6
#7  0x00007f47fad9b6b5 in qt_message_output () from /usr/lib/libQtCore.so.4
#8  0x00007f47fad9b7fd in qFatal () from /usr/lib/libQtCore.so.4
#9  0x00007f47e5573f28 in ?? () from /usr/lib/libkmailprivate.so.4
#10 0x00007f47e55ce4e3 in ?? () from /usr/lib/libkmailprivate.so.4
#11 0x00007f47e542ea09 in ?? () from /usr/lib/libkmailprivate.so.4
#12 0x00007f47e55d6892 in ?? () from /usr/lib/libkmailprivate.so.4
#13 0x00007f47e564204a in ?? () from /usr/lib/libkmailprivate.so.4
#14 0x00007f47e562717b in ?? () from /usr/lib/libkmailprivate.so.4
#15 0x00007f47e55fbb76 in ?? () from /usr/lib/libkmailprivate.so.4
#16 0x00007f47e55f1309 in ?? () from /usr/lib/libkmailprivate.so.4
#17 0x00007f47e55e9bf3 in ?? () from /usr/lib/libkmailprivate.so.4
#18 0x00007f47e55ea2b3 in ?? () from /usr/lib/libkmailprivate.so.4
#19 0x00007f47e575605f in ?? () from /usr/lib/libkmailprivate.so.4
#20 0x00007f47e5759fb4 in ?? () from /usr/lib/libkmailprivate.so.4
#21 0x00007f47faea0134 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#22 0x00007f47fb269fb2 in KJob::result () from /usr/lib/libkdecore.so.5
#23 0x00007f47fb26a377 in KJob::emitResult () from /usr/lib/libkdecore.so.5
#24 0x00007f47f8ba92b0 in KIO::SimpleJob::slotFinished () from /usr/lib/libkio.so.5
#25 0x00007f47f8bac703 in KIO::TransferJob::slotFinished () from /usr/lib/libkio.so.5
#26 0x00007f47f8ba7197 in KIO::SimpleJob::slotError () from /usr/lib/libkio.so.5
#27 0x00007f47f8ba7392 in KIO::SimpleJob::qt_metacall () from /usr/lib/libkio.so.5
#28 0x00007f47f8bad315 in KIO::TransferJob::qt_metacall () from /usr/lib/libkio.so.5
#29 0x00007f47faea0134 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#30 0x00007f47f8c61bb6 in KIO::SlaveInterface::error () from /usr/lib/libkio.so.5
#31 0x00007f47f8c65399 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5
#32 0x00007f47f8c62102 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5
#33 0x00007f47f8c53143 in KIO::Slave::gotInput () from /usr/lib/libkio.so.5
#34 0x00007f47f8c55868 in KIO::Slave::qt_metacall () from /usr/lib/libkio.so.5
#35 0x00007f47faea0134 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#36 0x00007f47f8b76be0 in ?? () from /usr/lib/libkio.so.5
#37 0x00007f47f8b76d1a in KIO::Connection::qt_metacall () from /usr/lib/libkio.so.5
#38 0x00007f47fae9ada5 in QObject::event () from /usr/lib/libQtCore.so.4
#39 0x00007f47fa3adc3d in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#40 0x00007f47fa3b59ba in QApplication::notify () from /usr/lib/libQtGui.so.4
#41 0x00007f47fb7e913b in KApplication::notify () from /usr/lib/libkdeui.so.5
#42 0x00007f47fae8bd61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#43 0x00007f47fae8c9fa in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4
#44 0x00007f47faeb44d3 in ?? () from /usr/lib/libQtCore.so.4
#45 0x00007f47f45b9d5b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#46 0x00007f47f45bd52d in ?? () from /usr/lib/libglib-2.0.so.0
#47 0x00007f47f45bd6eb in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#48 0x00007f47faeb415f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#49 0x00007f47fa43fa6f in ?? () from /usr/lib/libQtGui.so.4
#50 0x00007f47fae8a682 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#51 0x00007f47fae8a80d in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#52 0x00007f47fae8ccbd in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#53 0x00000000004048e5 in _start ()
Comment 1 Dario Andres 2009-04-02 14:57:59 UTC
The crash information isn't very useful. You can try to install the "kdepim-dbg" package in order to get a complete backtrace the next time. 
YOu can also run KMail/Kontact from the Konsole and then paste the shell output after the app crashed, here. (specially the "ASSERT" line)
Thanks for reporting.
Comment 2 Jens Schmidt 2009-04-14 11:54:17 UTC
Same behavior/backtrace for me. Having:
KDE 4.2.2
Kontact 1.4.2
KMail 1.11.2

Just installing "kdepim-dbg" right now to get a `better` backtrace for this bug.
Comment 3 Jens Schmidt 2009-04-15 10:03:38 UTC
Created attachment 32849 [details]
kcrash backtrace with "kdepim-dbg"

KCrash Backtrace, after Kontact-Crash. "kdepim-dbg" is installed.

Just added the same Attachement at Bug 187736. Just a Question: Why i didnt find "#188641" at "Search Existing-Report", only at "Check for Duplicate Bugs"?
Comment 4 Dario Andres 2009-04-25 13:31:54 UTC
@Jens Schmidt: your crash seems to be different from this report and even different from bug 187736. (the crash traces are indeed different, so it's a different crash). There are a lot of crash reports but a lot of them are different and unique.

Your crash seems to be more like bug 189376: (compare the functions name and order)
Anyway I can't assure that they are indeed duplicates. So the best is put every crash on a NEW bug report and let the bugs.kde.org maintainers / developers decide if they are the same crash or not.
Thanks
Comment 5 Christophe Marin 2009-10-23 10:37:37 UTC
Closing the old crash reports which don't have a useful backtrace. Thanks.