touch-packages team mailing list archive

[Michi Henning <michi.henning@xxxxxxxxxxxxx>]

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?

** Changed in: unity-scope-mediascanner (Ubuntu)
       Status: New => Confirmed

** Changed in: unity-scope-mediascanner (Ubuntu)
     Assignee: (unassigned) => James Henstridge (jamesh)

** Changed in: unity-scope-mediascanner (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scope-mediascanner
in Ubuntu.
https://bugs.launchpad.net/bugs/1288170

Title:
  Potential race on first boot when local db doesn't exist yet

Status in unity-scope-mediascanner package in Ubuntu:
  Confirmed

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1288170/+subscriptions