Potential race on first boot when local db doesn't exist yet
Bug #1288170 reported by
Paweł Stołowski
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| unity-scope-mediascanner (Ubuntu) |
Confirmed
|
High
|
James Henstridge | ||
Bug Description
There's a potential race when mediascanner scopes start and mediascanner db files don't exist yet. In that case the scope will throw an exception in start() and abort (but it will get restarted again as soon as user types a search query, and eventually the db will be there so it will work).
The window for this problem is extremely narrow (mediascanner service is started on boot with upstart, so a db file will be created soon after that) and it's easy to get out of it by just redoing the query. It can probably only affect a phone that e.g. is shipped with some preloaded videos/music files, but mediascanner db doesn't exist on first boot and need to be initialized - that could affect the surfacing results when viewing dash for the first time.
| no longer affects: | unity-scope-mediascanner |
Revision history for this message
| Michi Henning (michihenning) wrote | #1 |
| Changed in unity-scope-mediascanner (Ubuntu): | |
| status: | New → Confirmed |
| assignee: | nobody → James Henstridge (jamesh) |
| importance: | Undecided → High |
To post a comment you must log in.
If we ship preloaded music, we probably also should ship a pre-loaded mediascanner DB. Or, even better, make mediascanner deal with the situation correctly.
But the real question is whether it's worth fixing. Given that this pragmatically can't happen in normal deployment, I'd be inclined to close as "won't fix".
James, your opinion?