Bug 271726

Summary: Nepomuk crashed when launching kmail
Product: nepomuk Reporter: Christopher Heiny <christopherheiny>
Component: generalAssignee: Sebastian Trueg <sebastian>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra, me
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:

Description Christopher Heiny 2011-04-25 23:46:39 UTC
Application: nepomukservicestub (0.2)
KDE Platform Version: 4.6.1 (4.6.1)
Qt Version: 4.7.1
Operating System: Linux 2.6.35.12-88.fc14.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
With X11 forwarding over an ssh connection, I launched kmail after rebooting the XServer.  akonadi barfed (see https://bugs.kde.org/show_bug.cgi?id=269645), and then Nepomuk barfed too.

-- Backtrace:
Application: Nepomuk Service Stub (nepomukservicestub), signal: Segmentation fault
82	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[KCrash Handler]
#6  0x00007f7922602039 in Nepomuk::Repository::close (this=0x27815a0) at /usr/src/debug/kdebase-runtime-4.6.1/nepomuk/services/storage/repository.cpp:73
#7  0x00007f792260211d in Nepomuk::Repository::~Repository (this=0x27815a0, __in_chrg=<value optimized out>) at /usr/src/debug/kdebase-runtime-4.6.1/nepomuk/services/storage/repository.cpp:65
#8  0x00007f79226021e9 in Nepomuk::Repository::~Repository (this=0x27815a0, __in_chrg=<value optimized out>) at /usr/src/debug/kdebase-runtime-4.6.1/nepomuk/services/storage/repository.cpp:66
#9  0x0000003828a0e117 in qDeleteAll<QHash<QString, Soprano::Model*>::const_iterator> (begin=..., end=<value optimized out>) at /usr/include/QtCore/qalgorithms.h:322
#10 0x0000003828a0ca78 in qDeleteAll<QHash<QString, Soprano::Model*> > (this=0x2781360, __in_chrg=<value optimized out>) at /usr/include/QtCore/qalgorithms.h:330
#11 Soprano::Server::ServerCore::~ServerCore (this=0x2781360, __in_chrg=<value optimized out>) at /usr/src/debug/soprano-2.6.0/server/servercore.cpp:77
#12 0x00007f7922600f05 in Nepomuk::Core::~Core (this=0x2781360, __in_chrg=<value optimized out>) at /usr/src/debug/kdebase-runtime-4.6.1/nepomuk/services/storage/nepomukcore.cpp:45
#13 0x00007f7922600f89 in Nepomuk::Core::~Core (this=0x2781360, __in_chrg=<value optimized out>) at /usr/src/debug/kdebase-runtime-4.6.1/nepomuk/services/storage/nepomukcore.cpp:48
#14 0x000000327956e234 in QObjectPrivate::deleteChildren (this=0x272af00) at kernel/qobject.cpp:1949
#15 0x0000003279572d72 in QObject::~QObject (this=0x2773bb0, __in_chrg=<value optimized out>) at kernel/qobject.cpp:945
#16 0x00007f79226001a3 in ~Storage (this=0x2773bb0, __in_chrg=<value optimized out>) at /usr/src/debug/kdebase-runtime-4.6.1/nepomuk/services/storage/storage.cpp:50
#17 Nepomuk::Storage::~Storage (this=0x2773bb0, __in_chrg=<value optimized out>) at /usr/src/debug/kdebase-runtime-4.6.1/nepomuk/services/storage/storage.cpp:52
#18 0x000000327956e234 in QObjectPrivate::deleteChildren (this=0x2727440) at kernel/qobject.cpp:1949
#19 0x0000003279572d72 in QObject::~QObject (this=0x2726cf0, __in_chrg=<value optimized out>) at kernel/qobject.cpp:945
#20 0x00000000004043b9 in Nepomuk::ServiceControl::~ServiceControl (this=0x2726cf0, __in_chrg=<value optimized out>) at /usr/src/debug/kdebase-runtime-4.6.1/nepomuk/servicestub/servicecontrol.cpp:39
#21 0x000000327956e234 in QObjectPrivate::deleteChildren (this=0x262dba0) at kernel/qobject.cpp:1949
#22 0x0000003279572d72 in QObject::~QObject (this=0x7ffff578da90, __in_chrg=<value optimized out>) at kernel/qobject.cpp:945
#23 0x000000382bbc10f4 in QApplication::~QApplication (this=0x7ffff578da90, __in_chrg=<value optimized out>) at kernel/qapplication.cpp:1071
#24 0x0000000000403cc4 in main (argc=2, argv=0x7ffff578dee8) at /usr/src/debug/kdebase-runtime-4.6.1/nepomuk/servicestub/main.cpp:101

Possible duplicates by query: bug 270804, bug 270745, bug 270427, bug 270334, bug 269487.

Reported using DrKonqi
Comment 1 Dario Andres 2011-05-01 16:42:32 UTC
[Comment from a bug triager]
The bug is fixed since KDE SC 4.6.2. The issue was being tracked at bug 267666, merging.
Thanks

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