Was there another instance of mediascanner-service-2.0 running at the time?
The mediascanner is designed to run with only a single process writing to the database and all other processes being read-only, so starting a second copy of the daemon could cause this kind of problem. Dumping core in this situation sounds like a bug, but it isn't a supported mode of operation. -- 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
