Application: nepomukservicestub (0.2) KDE Platform Version: 4.7.2 (4.7.2) Qt Version: 4.7.4 Operating System: Linux 3.0.0-12-generic i686 Distribution: Ubuntu 11.10 -- Information about the crash: Starting system. after upgrade nepomuk disabled. nepomuk returns a segmentation fault. The crash can be reproduced every time. -- Backtrace: Application: Nepomuk Service Stub (nepomukservicestub), signal: Segmentation fault [KCrash Handler] #7 0x03e23ecc in Nepomuk::Repository::close (this=0x985e708) at ../../../../nepomuk/services/storage/repository.cpp:86 #8 0x03e2401c in Nepomuk::Repository::~Repository (this=0x985e708, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:75 #9 0x03e24122 in Nepomuk::Repository::~Repository (this=0x985e708, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:76 #10 0x082ceaaf in Soprano::Server::ServerCore::~ServerCore() () from /usr/lib/libsopranoserver.so.1 #11 0x03e22920 in Nepomuk::Core::~Core (this=0x985aa30, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/nepomukcore.cpp:45 #12 0x03e22a12 in Nepomuk::Core::~Core (this=0x985aa30, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/nepomukcore.cpp:48 #13 0x005bd841 in QObjectPrivate::deleteChildren (this=0x9859828) at kernel/qobject.cpp:1955 #14 0x005c2439 in QObject::~QObject (this=0x9827cc0, __in_chrg=<optimized out>) at kernel/qobject.cpp:946 #15 0x00166f98 in Nepomuk::Service::~Service (this=0x9827cc0, __in_chrg=<optimized out>) at ../../nepomuk/core/nepomukservice.cpp:41 #16 0x03e217da in ~Storage (this=0x9827cc0, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/storage.cpp:54 #17 Nepomuk::Storage::~Storage (this=0x9827cc0, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/storage.cpp:56 #18 0x005bd841 in QObjectPrivate::deleteChildren (this=0x9856e20) at kernel/qobject.cpp:1955 #19 0x005c2439 in QObject::~QObject (this=0x9827d20, __in_chrg=<optimized out>) at kernel/qobject.cpp:946 #20 0x0804b920 in Nepomuk::ServiceControl::~ServiceControl (this=0x9827d20, __in_chrg=<optimized out>) at ../../../nepomuk/servicestub/servicecontrol.cpp:39 #21 0x005bd841 in QObjectPrivate::deleteChildren (this=0x970b548) at kernel/qobject.cpp:1955 #22 0x005c2439 in QObject::~QObject (this=0xbfd285c4, __in_chrg=<optimized out>) at kernel/qobject.cpp:946 #23 0x005ac648 in QCoreApplication::~QCoreApplication (this=0xbfd285c4, __in_chrg=<optimized out>) at kernel/qcoreapplication.cpp:671 #24 0x064ad943 in QApplication::~QApplication (this=0xbfd285c4, __in_chrg=<optimized out>) at kernel/qapplication.cpp:1093 #25 0x01048378 in KApplication::~KApplication (this=0xbfd285c4, __in_chrg=<optimized out>) at ../../kdeui/kernel/kapplication.cpp:894 #26 0x0804aecb in main (argc=-1138898104, argv=0x8c09784e) at ../../../nepomuk/servicestub/main.cpp:102 This bug may be a duplicate of or related to bug 286096. Possible duplicates by query: bug 286096, bug 286010, bug 285896, bug 285886, bug 285870. Reported using DrKonqi
Created attachment 65721 [details] New crash information added by DrKonqi nepomukservicestub (0.2) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4 - What I was doing when the application crashed: Starting Nepomuk Service It crashes a once after activating in the system settings or after reboot just after logging in. -- Backtrace (Reduced): #6 0x00007f0e7cb30b8e in Nepomuk::Repository::close (this=0x23bc3a0) at ../../../../nepomuk/services/storage/repository.cpp:86 #7 0x00007f0e7cb30ccc in Nepomuk::Repository::~Repository (this=0x23bc3a0, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:75 #8 0x00007f0e7cb30da9 in Nepomuk::Repository::~Repository (this=0x23bc3a0, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:76 #9 0x00007f0e7c8f7ed7 in Soprano::Server::ServerCore::~ServerCore() () from /usr/lib/libsopranoserver.so.1 #10 0x00007f0e7cb2f9fc in Nepomuk::Core::~Core (this=0x2364160, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/nepomukcore.cpp:45
*** This bug has been marked as a duplicate of bug 283604 ***