Formerly not existing track cannot be loaded

Bug #1800395 reported by Daniel Schürmann on 2018-10-28
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Medium
Daniel Schürmann

Bug Description

If a track was missing, but the user has restored it, it can happen the the "not existing" state is still cached in Mixxx an the track is rejected during load to a deck even though it actually exists.

Changed in mixxx:
status: New → In Progress
Changed in mixxx:
assignee: nobody → Daniel Schürmann (daschuer)
Uwe Klotz (uklotzde) wrote :

I've also experienced this situation after starting Mixxx, with all my audio files located on a separate disk that needs to be mounted manually. Thanks for adopting this bug, I will test the fix!

Changed in mixxx:
milestone: none → 2.2.0
Uwe Klotz (uklotzde) wrote :

The fix could also be targeted to 2.1.x, although it might be too late for 2.1.5.

Changed in mixxx:
importance: Undecided → Medium
Uwe Klotz (uklotzde) on 2018-10-31
Changed in mixxx:
milestone: 2.2.0 → 2.1.6
Be (be.ing) on 2018-11-01
summary: - Formaly not existing track cannot be loaded
+ Formerly not existing track cannot be loaded
RJ Skerry-Ryan (rryan) on 2018-11-04
Changed in mixxx:
status: In Progress → Fix Committed
Changed in mixxx:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers