Summary: | nepomuk's systray icon does not always show the correct state of the indexer | ||
---|---|---|---|
Product: | nepomuk | Reporter: | S. Burmeister <sven.burmeister> |
Component: | controller | Assignee: | Sebastian Trueg <sebastian> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bruno, me, trueg |
Priority: | NOR | ||
Version: | 4.2 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | screenshot |
Description
S. Burmeister
2009-02-17 23:28:40 UTC
Created attachment 31426 [details]
screenshot
The status shown in the systray never changed until the indexer stopped, which took way longer than 1 minute.
This is disc reading which checks if files changed. This is not treated as actual indexing work as files are not read but only the folder modification dates are checked - or every hour or so all files' modification dates. Would you like there to be another state like "Looking for changed and new files"? The reason why I assumed that even only reading shows up there is that if you start KDE, nepomuk's strigiservice reads/checks all folders in its index and that action is shown as "indexing". I think that users who check their process list and see nepomuk and then check in the systray what nepomuk does, should find the current action, no matter whether it is as detailed as: indexing, checking for changed files, working on semantics etc. or just: working on the index. The latter is not as informative of course, but least work. If they find no action, they might wonder why nepomuk is taking that much CPU or harddisk i/o although it is not indexing/working. SVN commit 960314 by trueg: Centralized the creation of the strigi status string. Also the file system checking is reported now. BUG: 184725 M +4 -0 interfaces/org.kde.nepomuk.ServiceManager.xml M +4 -0 interfaces/org.kde.nepomuk.Strigi.xml M +4 -15 kcm/nepomukserverkcm.cpp M +11 -0 server/servicemanager.cpp M +13 -1 server/servicemanager.h M +0 -26 services/strigi/eventmonitor.cpp M +0 -4 services/strigi/eventmonitor.h M +13 -0 services/strigi/filesystemwatcher.cpp M +9 -0 services/strigi/filesystemwatcher.h M +6 -18 services/strigi/statuswidget.cpp M +3 -3 services/strigi/statuswidget.h M +69 -3 services/strigi/strigiservice.cpp M +17 -0 services/strigi/strigiservice.h M +22 -14 services/strigi/strigiserviceadaptor.cpp M +8 -3 services/strigi/strigiserviceadaptor.h M +8 -22 services/strigi/systray.cpp M +3 -2 services/strigi/systray.h WebSVN link: http://websvn.kde.org/?view=rev&revision=960314 It seems we got a regression and this is my comment in bug 258473 I was also using it (mouse hover) to see what's is currently is indexing or if the state is idle. (In a perfect world, the icon should have a different state indicating the state of strigi (indexing yes/no) and nepomuk ( off, suspended, running) Hope this come back before final 4.6 Re-opening since this is not fixed until "idle" means that i/o and CPU are 0. Whatever nepomuk does it should show its state to the user, be it in systemsettings or a systray icon does not matter. If virtuoso uses cpu nepolum(+xy) is not "idle" but doing something that needs some transparency to the user in order give him the chance to know whether it is a bug or not. The systray shows the state of the indexer. It has no notion of the query service or others which can be active even if the indexer does nothing. So this is more of a wish than a bug. Actual nepomukcontroller do it's job related to strigi. With it's black/gray/white icon in systray I'm agree with the wish of having it able to report running query, and a more details report status :-) I'm closing this as 'nepomukcontroller' shows the appropriate status message. We have no plans of adding the current queries to the controller. It's too much information for the user. |