scope doesn't handle exception during start()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mediascanner2 (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
unity-scope-mediascanner (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I just ran up the scope while the mediascanner was still indexing a large collection I had dropped into the music folder.
When I switched to the mediascanner scope, I ended up with a completely blank screen, nothing shown at all. In registry log, I found this:
scoperunner: unity::
Tried to open a db with schema versino -1, while supported version is 10.
Trying to refresh didn't do anything. The bouncing bar showed up for a while, and I was still left with a blank screen.
It seems that the scope eventually recovers. I left the phone sitting there for a while and, next time I glanced at it, the scope had populated the screen.
I think this is basically the same problem as the one I reported 2 years ago: https:/ /bugs.launchpad .net/ubuntu/ +source/ unity-scope- mediascanner/ +bug/1288170