| Summary: | kde-base/nepomuk-4.9.0 file indexer doesn't work | ||
|---|---|---|---|
| Product: | [Unmaintained] nepomuk | Reporter: | Michael Mair-Keimberger <mmk+bugs> |
| Component: | fileindexer | Assignee: | Nepomuk Bugs Coordination <nepomuk-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | johu, me, stupor_scurvy343 |
| Priority: | NOR | ||
| Version: | 4.9 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| URL: | https://bugs.gentoo.org/show_bug.cgi?id=430296 | ||
| Latest Commit: | http://commits.kde.org/nepomuk-core/68dde513c437a218143fc8cd319b4897a64b8c20 | Version Fixed In: | |
| Sentry Crash Report: | |||
| Attachments: |
nepomuk debug output
nepomuk gdb output nepomuk gdb fileindexer output pid's of nepomuk via htop nepomuk gdb fileindexer output with debug enabled nepomuk gdb output with debug enabled |
||
|
Description
Michael Mair-Keimberger
2012-08-11 14:25:27 UTC
I'm not sure what 'kde-base/nepomuk-4.9.0' is. There is a nepomuk-core repository. I can only assume you meant that. In that case, I don't understand why gentoo would want to call it by such a different name.
Anyway, could you please gdb into the fileindexer and provide me with a backtrace?
> $ gdb
> attach <pid>
> thread apply all backtrace
> detach <pid>
This should do the trick. Also if possible could you switch of nepomuk (qdbus org.kde.NepomukServer /nepomukserver quit) and restart it by running 'nepomukserver'. I'd like to see the entire debug log, if possible.
Please make sure nepomuk is enabled in kdebugdialog. Thanks.
Created attachment 73115 [details]
nepomuk debug output
Created attachment 73116 [details]
nepomuk gdb output
Created attachment 73117 [details]
nepomuk gdb fileindexer output
Created attachment 73118 [details]
pid's of nepomuk via htop
For the name thing i simply don't know. there is a package called nepomuk-core which contains, regarding their description, the core libraries of nepomuk, while the nepomuk package just contains the kde4 client. Anyway, i really don't know about that :) I made what you said, i hope it's correct. I made a screenshot from htop, where you see the pid's of nepomuk. with gdb i made a backtrace once from nepomuk itself and once from the pid of "nepomukservicestub nepomukfileindexer". I checked kdebugdialog and enabled everything which contains nepomuk. I turned off nepomuk and started it again from konsole. You'll see the output in nepomuk-debug. (In reply to comment #4) > Created attachment 73117 [details] > nepomuk gdb fileindexer output Please could you install the debugging symbols for nepomuk and then try again? I need the symbols in order to be able to debug this. Hint: You shouldn't be getting stuff like this - #7 0xb53d1aaa in ?? () from /usr/lib/kde4/nepomukfileindexer.so #8 0xb53d1c61 in ?? () from /usr/lib/kde4/nepomukfileindexer.so #9 0xb53dd482 in ?? () from /usr/lib/kde4/nepomukfileindexer.so #10 0xb53ddc95 in ?? () from /usr/lib/kde4/nepomukfileindexer.so #11 0xb53ddf69 in ?? () from /usr/lib/kde4/nepomukfileindexer.so #12 0xb53cea81 in ?? () from /usr/lib/kde4/nepomukfileindexer.so The '??' should have proper names. Thanks Created attachment 73329 [details]
nepomuk gdb fileindexer output with debug enabled
Created attachment 73330 [details]
nepomuk gdb output with debug enabled
I've created another two gdb output's. This time with debug enabled. There are still a few "??" from QT libs, if you need them i can rebuild qt with debug too. :) Thanks for the backtraces. I've posted a review request, the fix should be there in 4.9.1 https://git.reviewboard.kde.org/r/106230/ Git commit 68dde513c437a218143fc8cd319b4897a64b8c20 by Vishesh Handa. Committed on 27/08/2012 at 11:44. Pushed by vhanda into branch 'KDE/4.9'. FileIndexer: Fix a deadlock by making the mutex recursive The following deadlock occurs during the first run of the nepomuk-fileindexer, if you're on batery QMutex::lockInternal() QMutexLocker::QMutexLocker Nepomuk2::IndexScheduler::suspend Nepomuk2::EventMonitor::pauseIndexing QMetaObject::activate(QObject*, QMetaObject Nepomuk2::IndexScheduler::indexingSuspended Nepomuk2::IndexScheduler::suspend Nepomuk2::EventMonitor::pauseIndexing Nepomuk2::EventMonitor::slotPowerManagementStatusChanged Nepomuk2::EventMonitor::EventMonitor Nepomuk2::FileIndexer::FileIndexer This only happens during first run cause that is when the EventMonitor is connected to the IndexScheduler REVIEW: 106230 M +1 -0 services/fileindexer/indexscheduler.cpp http://commits.kde.org/nepomuk-core/68dde513c437a218143fc8cd319b4897a64b8c20 |