If you run "restart mediascanner-2.0" in the console, it will restart the existing instance and should see the contents of the bind mount.
Mediascanner uses inotify to track changes to the directories it watches. I guess the events we're watching don't cover mount operations. That said, the usual way we handle removable media is to scan it if it is mounted under /media rather than relying on the user to perform bind mount tricks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1522012 Title: Error finalising statement: Could not finalize statement: database is locked Status in mediascanner2 package in Ubuntu: New Bug description: Hi, When i launch manually the mediascanner-service-2.0 command on freshly mounted folder, after several media scanned i got this error message : "Error finalising statement: Could not finalize statement: database is locked Error when indexing: database is locked terminate called after throwing an instance of 'std::runtime_error' what(): database is locked Aborted (core dumped)" Most of the medias are recognized in the picture app and music app My phone is a nexus 4 with Rc-proposed version. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1522012/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
