Bug 226248 - Folderview on KIO slaves like timeline or nepomuksearch does not update itself
Summary: Folderview on KIO slaves like timeline or nepomuksearch does not update itself
Status: RESOLVED UNMAINTAINED
Alias: None
Product: plasma4
Classification: Plasma
Component: widget-folderview (show other bugs)
Version: 4.8.1
Platform: Gentoo Packages Unspecified
: NOR normal
Target Milestone: ---
Assignee: Ignat Semenov
URL:
Keywords:
: 226246 226247 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-02-11 07:32 UTC by Patrick
Modified: 2018-06-08 19:37 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick 2010-02-11 07:32:21 UTC
Version:            (using KDE 4.4.0)
Installed from:    Gentoo Packages

I just set up two instances of the Folderview plasmoid, one with the location set to

timeline:/today/

and one with

nepomuksearch:/rating=10/

Initially they show the expected files, but then there is no update. After restarting KDE, they are now completely empty. Opening those URLs in Dolphin brings up the correct results.

I guess this is not limited to those two KIO slaves...
Comment 1 Patrick 2010-02-11 07:36:12 UTC
*** Bug 226247 has been marked as a duplicate of this bug. ***
Comment 2 Patrick 2010-02-11 07:36:51 UTC
*** Bug 226246 has been marked as a duplicate of this bug. ***
Comment 3 Dominik Tritscher 2010-06-29 23:08:46 UTC
I can confirm this bug using KDE 4.4.90 (installed from Kubuntu PPA packages) at least for the nepomuksearch kio-slave.
Comment 4 Dominik Tritscher 2010-09-19 09:56:30 UTC
This problem still exists in 4.5.1 - I also noticed that the content of the folderview applet is reloaded correctly if plasma is restarted during a running kde session.
Comment 5 Franz Trischberger 2011-02-12 11:18:42 UTC
Still present in 4.6.0.
Clicking into the folderview and Pressing F5 updates the view. But it is not that comfortable.
Comment 6 Giuseppe Calà 2012-03-12 10:43:23 UTC
Confirm this bug in kde 4.8.1; I have same behaviour with "nepomuksearch:/..." and "webdavs://..."; the only solution is killall and restart plasma-desktop
Comment 7 Giuseppe Calà 2012-03-12 14:03:53 UTC
It is definitely a start order issue. The plasma-desktop's desktop file has option X-KDE-autostart-phase=0, so it starts early when needed services (nepomuk and kio-slave) aren't available. I've tryed various settings and the only working one is X-KDE-autostart-phase=2; with this one plasma-desktop is started delayed when all needed services are ready. Drawback? When kde login splash fades out, you got a black desktop with only mouse pointer; after 7-8 secs plasma starts.

Alternatives?
Comment 8 Kevin Colyer 2012-09-17 10:25:33 UTC
Can confirm on kubuntu 12.04.1 with kde 4.9.1:

Folderview with timeline:/today can't access the underlying data base and leaves the plasmoid with a big red X and a Can't Access message.

A manual work around is to edit the properties, apply a fixed folder view and then re-apply the timeline view once KDE is fully loaded. 

Would appreciate a 60 second polling of the underlying service or a manual "click here to try again" link... 

Cheers and thanks!
Comment 9 Andy Potter 2012-12-28 12:38:23 UTC
I can also confirm this.

KDE Version 4.9.4 "release 5"

OpenSuse 12.2
Comment 10 Andy Potter 2012-12-28 12:43:59 UTC
*** This bug has been confirmed by popular vote. ***
Comment 11 Nate Graham 2018-06-08 19:37:54 UTC
Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham