Bug 260839

Summary:	amarok needs to be restarted to pick up new moodbar file
Product:	[Applications] amarok	Reporter:	Alexander Potashev <aspotashev>
Component:	Moodbar	Assignee:	Amarok Developers <amarok-bugs-dist>
Status:	RESOLVED WORKSFORME
Severity:	wishlist	CC:	baby-luck, konrad.zemek, maddiemadan, nhn, nsm.nikhil
Priority:	LO
Version:	2.6-git
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Alexander Potashev 2010-12-20 23:18:30 UTC

Version:           2.3.2
OS:                Linux



Reproducible: Always

Steps to Reproduce:
1. Add a track to playlist.
2. Generate a moodbar file for that track. The moodbar does not appear, even after removing and adding the same track again.

3. Restart Amarok. Now you can see the moodbar in track progress slider.

Comment 1 Myriam Schweingruber 2011-06-04 12:11:02 UTC

This is an automated message from the triager:

Amarok 2.4.1 has been released on May 8 already. Could you please upgrade and test if you can still reproduce this bug?

Without feedback within a month we will close this bug as resolved.

Thank you for your understanding.

Comment 2 Alexander Potashev 2011-06-04 14:50:14 UTC

Still happens with 2.4.1.

Comment 3 Myriam Schweingruber 2011-06-04 15:56:57 UTC

Thank you for the fast feedback :)

Comment 4 BL 2012-04-26 09:56:53 UTC

Still happens with 2.5.0.
It's kind of annoying, I've a script that will generate moodbars for any file in the playlist but of course it's effectiveness is somewhat reduced as the change cannot be seen till restart.

Comment 5 BL 2012-05-08 06:35:17 UTC

It seems that the "MoodbarManager" is in charge of finding the moodbar file and then it appears that "PrettyItemDelegate::paintItem" is called to render the moodbar. However, when MoodbarManager runs I do not know.

I have seen 12 files added to the playlist and subsequently the MoodbarManager looking at the files and my script starting (independently). The MoodbarManager looked at the first 7, finding and doing nothing. Only after that point had my script managed to finish any moodbar files. In fact it was able to complete all 12 moodbar files and touch the containing directory before the MoodbarManager ran again for files 8 onwards, where it found moodbar files and rendered them.

Why did it stop at 7? and why not, after the containing dir was touched, did it not update?

Comment 6 Mayank Madan 2012-11-30 10:22:48 UTC

problem persists with 2.6-git

Comment 7 Konrad Zemek 2013-08-06 15:05:03 UTC

Amarok doesn't need to be restarted to pick up moodbar files. As stated in the manual [1]: "Note that the moodbars will not appear in Amarok until Amarok rescans the collection."

After generating .mood files, just click on Tools -> Update Collection

This is by design; I'm changing this bug to wish.

[1] http://userbase.kde.org/Amarok/Manual/Various/Moodbar

Comment 8 Myriam Schweingruber 2013-08-06 19:44:33 UTC

That is not even a wish but should just be closed as it can't be reproduced.

FWIW: there was a caching bug with the collection prior to 2.7.90, might have been fixed in the same commit.