Music app crashes with unsupported schema version with latest v0.105+15.04.20150127-0ubuntu1 on Vivid

Bug #1415318 reported by Victor Thompson
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu Music App
Invalid
Critical
Unassigned
mediascanner2 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

The music app is crashing on the latest vivid images. The following error is seen on console prior to the crash in image #80 for mako and #79 for flo--both of which update mediascanner2 to version 0.105+15.04.20150127-0ubuntu1.

terminate called after throwing an instance of 'std::runtime_error'
  what(): Tried to open a db with an unsupported schema version.

Was the something not updated? It seems like the daemon is the same schema version (8), but the plugin does not support this version.

Related branches

Changed in music-app:
importance: Undecided → High
importance: High → Critical
Revision history for this message
Jussi Pakkanen (jpakkane) wrote :

Thank you for noticing this. I can replicate and am investigating.

David Planella (dpm)
Changed in music-app:
status: New → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mediascanner2 - 0.105+15.04.20150127.is.0.105+15.04.20150122-0ubuntu1

---------------
mediascanner2 (0.105+15.04.20150127.is.0.105+15.04.20150122-0ubuntu1) vivid; urgency=medium

  * Revert mediascanner2 to the previous working version as the newest
    upload broke the music-app (LP: #1415318)
 -- Lukasz 'sil2100' Zemczak <email address hidden> Wed, 28 Jan 2015 14:00:55 +0100

Changed in mediascanner2 (Ubuntu):
status: New → Fix Released
Revision history for this message
Leo Arias (elopio) wrote :

This needs a test, right?
How can we check that a new release of media scanner won't break the apps that depend on it?

Revision history for this message
Victor Thompson (vthompson) wrote :

Leo, this is a great point. If such a thing could be made testable it'd be very appreciated by our team. I don't think it'd require much more than exercising a minimal AP test to load the models that ms2 retains (maybe a unit test?). We'd really appreciate it in the future. Currently we're pretty good at catching regressions, but I'd rather automate testing--since it really is not our responsibility.

Revision history for this message
Ken VanDine (ken-vandine) wrote :

This is still broken for me, with mediascanner2=0.105+15.04.20150128-0ubuntu1

Revision history for this message
Ken VanDine (ken-vandine) wrote :

OK, I was able to work around it by moving .cache/mediascanner-2.0 out of the way and restarting. We really need this to be more resilient to keep users from getting in this situation without the need to enable developer mode.

Revision history for this message
Andrew Hayzen (ahayzen) wrote :

@Leo, can we not just run the music-app AP tests each time ms2 changes? or as Victor said create a mini app that has all of the models we use (maybe we could write a small set of QML Unit tests todo this) ?

Changed in music-app:
status: Triaged → Invalid
no longer affects: mediascanner2
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.