Summary: | Nepomuk server crash after login | ||
---|---|---|---|
Product: | [Unmaintained] nepomuk | Reporter: | aaron.zakhrov |
Component: | general | Assignee: | Nepomuk Bugs Coordination <nepomuk-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | bugzilla, hrvoje.senjan, nepomuk-bugs, thing1138 |
Priority: | NOR | ||
Version: | 4.10.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
aaron.zakhrov
2013-02-09 06:11:11 UTC
Crashes again if application is restarted using the crash window Created attachment 77095 [details]
New crash information added by DrKonqi
nepomukservicestub (0.1.0) on KDE Platform 4.10.00 using Qt 4.8.4
- What I was doing when the application crashed:
Just restarted with File index enabled. Previous restarts without file indexing did not cause a crash.
-- Backtrace (Reduced):
#6 0x00007f9ba51d6d0c in Nepomuk2::IndexScheduler::slotScheduleIndexing() () from /usr/lib64/kde4/nepomukfileindexer.so
#7 0x00007f9ba51d7b74 in Nepomuk2::IndexScheduler::slotCleaningDone() () from /usr/lib64/kde4/nepomukfileindexer.so
#8 0x00007f9ba51d89ad in Nepomuk2::IndexScheduler::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib64/kde4/nepomukfileindexer.so
[...]
#10 0x00007f9bb54a940f in KJob::finished(KJob*) () from /usr/lib64/libkdecore.so.5
#11 0x00007f9bb54a9665 in KJob::emitResult() () from /usr/lib64/libkdecore.so.5
*** This bug has been marked as a duplicate of bug 314589 *** Shouldn't bug duplicates be restricted to version specific distributions of the OS? For example Hrvoje Senjan marked this bug report as a duplicate of bug 314589, but that bug report pertains to Kubuntu 12.10 while this one is for 12.04. I'm just not sure why wer are mixing and matching the bug reports between different setups. @think1138 It matters which KDE SC version are you using. The bug is fixed in 4.10.1, if you can still reproduce it with that version i suggest you open a new bug report. |