Bug 280011 - Akonadi Agent (akonadi_nepomuk_email_feeder) crash on shutdown
Summary: Akonadi Agent (akonadi_nepomuk_email_feeder) crash on shutdown
Status: RESOLVED DUPLICATE of bug 251795
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Nepomuk Feeder Agents (show other bugs)
Version: 4.7
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Tobias Koenig
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-13 08:35 UTC by CisBug
Modified: 2011-08-28 16:24 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description CisBug 2011-08-13 08:35:08 UTC
Application: akonadi_nepomuk_email_feeder (4.7)
KDE Platform Version: 4.7.00 (4.7.0) "release 6"
Qt Version: 4.7.3
Operating System: Linux 2.6.37.6-0.7-desktop x86_64
Distribution: "openSUSE 11.4 (x86_64)"

-- Information about the crash:
Akonadi Agent crashed during logout from KDE 4.7.0 and computer shutdown. Kwin already closed when the crash occured.

-- Backtrace:
Application: Akonadi Agent (akonadi_nepomuk_email_feeder), signal: Segmentation fault
[KCrash Handler]
#6  0x00007f86a61889bc in QMutex::lock (this=0x827e98) at thread/qmutex.cpp:151
#7  0x00007f86a7727512 in Soprano::Client::SocketHandler::~SocketHandler() () from /usr/lib64/libsopranoclient.so.1
#8  0x00007f86a7727699 in Soprano::Client::SocketHandler::~SocketHandler() () from /usr/lib64/libsopranoclient.so.1
#9  0x00007f86a618b612 in QThreadStorageData::set (this=0x7bc060, p=0x0) at thread/qthreadstorage.cpp:165
#10 0x00007f86a43ac30a in qt_cleanup () at kernel/qapplication_x11.cpp:2647
#11 0x00007f86a4336c60 in QApplication::~QApplication (this=0x7fffa48a6fc0, __in_chrg=<value optimized out>) at kernel/qapplication.cpp:1172
#12 0x000000000040f9c2 in main ()

Possible duplicates by query: bug 277139, bug 268369, bug 263203, bug 259454, bug 259453.

Reported using DrKonqi
Comment 1 Christophe Marin 2011-08-28 16:24:03 UTC

*** This bug has been marked as a duplicate of bug 251795 ***