Rockbox

Tasklist

FS#5043 - bookmark disappears after shutdown

Attached to Project: Rockbox
Opened by Markus Berndt (monnemer) - Wednesday, 05 April 2006, 17:48 GMT
Last edited by Dave Chapman (linuxstb) - Saturday, 20 May 2006, 08:48 GMT
Task Type Bugs
Category Operating System/Drivers
Status Closed
Assigned To No-one
Operating System All players
Severity High
Priority Normal
Reported Version
Due in Version Version 3.0
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Platform: H120

I am using the latest cvs source (as of April 5, 2006)

I am using the following bookmarking settings:

Bookmark on stop: yes
Load last bookmark: ask
Maintain a list of recent bookmarks: yes

The symptom is as follows:

I listen to a rather long mp3 file, and press stop. The player displays the message 'Bookmark Created'. When I look in the parent directory, I see a .bmark file for the directory that the mp3 file resides in. Now I turn the player off and turn it back on, and the .bmark file is gone, however, there is a .bmark.tmp file for the directory.

I marked the severity as high since bookmarking is an essential feature for listening to audio books.

- Markus
This task depends upon

Closed by  Linus Nielsen Feltzing (linusnielsen)
Sunday, 21 May 2006, 21:17 GMT
Reason for closing:  Fixed
Comment by Markus Berndt (monnemer) - Wednesday, 05 April 2006, 18:28 GMT
I forgot to mention that this only happens when the Directory Cache is enabled.
Comment by Ton van Rijn (Ton) - Thursday, 06 April 2006, 11:22 GMT
Same problem here. Also only with Directory Cache turned on.
Comment by Markus Berndt (monnemer) - Sunday, 09 April 2006, 19:27 GMT
This may be related to bug report http://www.rockbox.org/tracker/task/5041
Comment by Dave Chapman (linuxstb) - Saturday, 20 May 2006, 12:52 GMT
Can you confirm if this bug is still present in the latest builds? There was a dircache related bugfix on the 16 May which may (or may not...) have fixed this.
Comment by Markus Berndt (monnemer) - Sunday, 21 May 2006, 21:03 GMT
This bug was fixed by an earlier (not the May 16) bugfix.

Loading...