Bug 225117 - Force a complete Collection Rescan and suggest to restart Amarok after a database version change
Summary: Force a complete Collection Rescan and suggest to restart Amarok after a data...
Status: RESOLVED WORKSFORME
Alias: None
Product: amarok
Classification: Applications
Component: Collections/Local (show other bugs)
Version: 2.2.2
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-01 11:22 UTC by Marco De Rosa
Modified: 2010-02-01 13:47 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Marco De Rosa 2010-02-01 11:22:46 UTC 
Version:           2.2.2 (using Devel)
Compiler:          gcc-4.3.4 
OS:                Linux
Installed from:    Compiled sources

After updating from 2.2.0 to 2.2.2 track lengths are not shown anymore in the
playlist. They are all shown as 0:00.

Workaround: Fully rescan collection. 

This is the same problem that was shown in Bug 214599 for version 2.2.1, which has been closed, but is not resolved in my opinion: the user should be aware that due to changes in the DB format, the collection needs to be rescanned.

Proposed resolution: At the first start of the updated version, a warning message should open asking the user if he wants to rescan the collection, due to changes in the DB format.
Comment 1 Myriam Schweingruber 2010-02-01 11:52:43 UTC 
Confirmed.
Comment 2 Jeff Mitchell 2010-02-01 13:47:44 UTC 
How on earth is this confirmed?

It already forces a database rescan. Why it didn't work in this particular case is unknown.