Reproducible: Always Steps to Reproduce: 1. Write a scripted service with 3 levels that populates level 2 items based on terms typed into the search bar. Do not set a playableUrl for level 2 items. 2. Expand a level 2 item, then a level 1 item under it to populate level 0. 3. Try to expand a different level 2 item. 4. Enter a different search term in the search bar. Actual Results: 3. Level 2 item fails to expand. 4. Tree is cleared and never repopulates (until restarting Amarok). When entering another search term, Amarok tries to populate level 2, and the script executes the populate function, but Amarok does not load any items. Debugging output shows: amarok: BEGIN: int ScriptableServiceScript::donePopulating() const amarok: BEGIN: void ScriptableServiceManager::donePopulating(const QString&, int) amarok: Service name: "SoundCloud Integration" , parent id: -1 amarok: BEGIN: void Collections::ScriptableServiceCollection::donePopulating(int) amarok: BEGIN: void Collections::ScriptableServiceQueryMaker::slotScriptComplete() amarok: [ScriptableServiceQueryMaker] there are 0 artists amarok: END__: void Collections::ScriptableServiceQueryMaker::slotScriptComplete() [Took: 0s] amarok: END__: void Collections::ScriptableServiceCollection::donePopulating(int) [Took: 0s] amarok: END__: void ScriptableServiceManager::donePopulating(const QString&, int) [Took: 0s] amarok: END__: int ScriptableServiceScript::donePopulating() const [Took: 0s] Expected Results: 3. Level 1 is populated under the expanded level 2 item. 4. Tree is repopulated, populating level 2 based on new search terms. These bugs do not occur if level 2 items have a playableUrl set to an empty string. This does not make sense, since level 2 items should not be playable.
Upon further testing, it appears that level 1 items must have playableUrl set to an empty string as well. If it is unset, then those level 1 items will not load when expanding other level 2 items.
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!