Comment 13 for bug 1272977

It would be interesting to know if those issues happened after a an upgrade from precise (or saucy) to trusty. It looks like from the report that it might be happening during upgrades when versions of the code in memory, and from the loaders on disk, are out of sync ... not sure how we could solve that though (out of stopping doing update in a running session)