Summary: | Storage Crash on Migration | ||
---|---|---|---|
Product: | [Unmaintained] nepomuk | Reporter: | RussianNeuroMancer <russianneuromancer> |
Component: | storage | Assignee: | Nepomuk Bugs Coordination <nepomuk-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | aaronw, abakar.mirzakerimov, me, rain.roman |
Priority: | HI | Keywords: | drkonqi |
Version: | 4.10.97 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
RussianNeuroMancer
2013-08-11 04:01:28 UTC
*** Bug 322878 has been marked as a duplicate of this bug. *** Created attachment 83246 [details]
New crash information added by DrKonqi
nepomukstorage (4.11.2) on KDE Platform 4.11.2 using Qt 4.8.5
- What I was doing when the application crashed:
When I start the nepomuk server it complains that it can't start Virtuoso.
-- Backtrace (Reduced):
#6 0x00007f228b115be3 in Soprano::FilterModel::executeQuery (this=0xb94d80, query=..., language=Soprano::Query::QueryLanguageSparql, userQueryLanguage=...) at /usr/src/debug/soprano-2.9.4/soprano/filtermodel.cpp:171
#7 0x0000000000414c34 in Nepomuk2::Storage::hasMigrationData (this=0xb818e0) at /usr/src/debug/nepomuk-core-4.11.2/services/storage/storage.cpp:195
#8 0x0000000000415685 in Nepomuk2::Storage::migrateGraphsByBackup (this=0xb818e0) at /usr/src/debug/nepomuk-core-4.11.2/services/storage/storage.cpp:209
#9 0x0000000000415c15 in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at /usr/src/debug/nepomuk-core-4.11.2/build/services/storage/storage.moc:97
#10 Nepomuk2::Storage::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /usr/src/debug/nepomuk-core-4.11.2/build/services/storage/storage.moc:82
Thank you for taking the time to file a bug report. The Nepomuk project is no longer included in the KDE Software Compilation. With Plasma 5, we have replaced most of the underlying technology with Baloo and other components. Hopefully this will have addressed your concern. We encourage you to try out Plasma 5 (+Baloo) and let us know if your problem persists. This issue is already no longer reproducible with latest releases of KDE 4. |