Summary: | [Timeline] and [search] not available if dolphin is starting during session restauration | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | m.wege |
Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | lukas.schneiderbauer, me |
Priority: | NOR | ||
Version: | 2.1 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/kde-baseapps/24609e78f87440606ce44d4f2559c4587fbd0e22 | Version Fixed In: | 4.10.4 |
Sentry Crash Report: |
Description
m.wege
2012-08-10 10:11:55 UTC
Just read that I should assign timeline-bugs to the timeline-component. In this case it may be also a dolphin bug. Thanks for the bug report! In this case, you might be right that the problem is not in the timeline kioslave. The cause of the bug might be (as you say) that the Nepomuk server is not fully initialised yet when Dolphin starts, but restarting Dolphin should indeed not be required to fix this. I have to add that the same problem occurs with the folderview desktop applet. So may be there could be a common solution. Resetting assignee to default as per bug #305719 Problem still exists in 4.10 RC2 It will continue to exist in all future releases unless anyone has a good idea how to fix it. Unfortunately, I don't - checking periodically if the Nepomuk server has appeared in the meantime and then re-initalising the Places Panel and other things looks like a rather complex and resource-wasting solution to me. Hmm, how about not checking if the Nepomuk-server is present on initialising the Places Panel but check if it is intended to be present? Either by configuration option or by checking if it Nepomuk is installed and by configuration intended to be running. If this is the case you could put those items in the panel. And could move the checking if the Nepomuk-server is present to the point when it is intended to be used. In that case this could be handled in a simular way than Kaddressbook waiting for Akonadi. "Waiting for Nepomuk to be present" until a timeout and then a button "Recheck", if that has failed. This could also solve the problem which occurs when timeline is made the homepage (via directly editing in the dolphin-configs because at the moment it can not be done directly, see my other bug report from yesterday) or is used in a plasma folderview (where the same problem occurs). (In reply to comment #7) > Hmm, how about not checking if the Nepomuk-server is present on initialising > the Places Panel but check if it is intended to be present? Either by > configuration option or by checking if it Nepomuk is installed and by > configuration intended to be running. Might be possible (but no new config option for such a minor thing, please), but then I see the problem that users complain if the 'timeline' entries are shown, but do not work because something went wrong. But maybe it's more important to make the probably not-so-uncommon 'session restauration' use case work, I'm not sure. > And could move the checking if the Nepomuk-server > is present to the point when it is intended to be used. In that case this > could be handled in a simular way than Kaddressbook waiting for Akonadi. > "Waiting for Nepomuk to be present" until a timeout and then a button > "Recheck", if that has failed. Im not really in favor of adding more checks to Dolphin. If a 'timeline' URL is opened and it doesn't work, then it doesn't work. No need for us to check if it won't work before applying the URL to the view. The KAddressBook/Akonadi comparison is IMHO not valid because KAdressBook does not work at all without Akonadi. > This could also solve the problem which > occurs when timeline is made the homepage (via directly editing in the > dolphin-configs because at the moment it can not be done directly, see my > other bug report from yesterday) or is used in a plasma folderview (where > the same problem occurs). Note that Dolphin and FolderView have basically nothing in common (except for the fact that they rely on KDirLister and Qt, obviously). So any 'fix' in Dolphin would have zero effect on the FolderView plasmoid. Git commit 24609e78f87440606ce44d4f2559c4587fbd0e22 by Vishesh Handa. Committed on 06/05/2013 at 15:11. Pushed by vhanda into branch 'KDE/4.10'. Dolphin Places: React to Nepomuk system changes Reload the places panel when Nepomuk starts up and shutsdown. This way the user does not need to restart Dolphin to see the custom searches and places after Nepomuk switches on. REVIEW: 110323 M +9 -0 dolphin/src/kitemviews/kstandarditemmodel.cpp M +1 -0 dolphin/src/kitemviews/kstandarditemmodel.h M +39 -1 dolphin/src/panels/places/placesitemmodel.cpp M +3 -0 dolphin/src/panels/places/placesitemmodel.h http://commits.kde.org/kde-baseapps/24609e78f87440606ce44d4f2559c4587fbd0e22 *** Bug 320703 has been marked as a duplicate of this bug. *** (In reply to comment #9) > Git commit 24609e78f87440606ce44d4f2559c4587fbd0e22 by Vishesh Handa. > Committed on 06/05/2013 at 15:11. > Pushed by vhanda into branch 'KDE/4.10'. > > Dolphin Places: React to Nepomuk system changes > > Reload the places panel when Nepomuk starts up and shutsdown. This way > the user does not need to restart Dolphin to see the custom searches and > places after Nepomuk switches on. > REVIEW: 110323 Could this fix be also applied to folderview on the Plasma desktop? > Could this fix be also applied to folderview on the Plasma desktop?
You might want to ask the Folderview people.
|