Comment 156 for bug 1268257

Got a different error message during an update today, but it was marked as a duplicate of this one.
Worth reporting anyway since the update might have been intended to fix the problem, and reporting it is the only way anyone will know that the update did not fix it.
Also worth mentioning that this problem did not occur at all with Xubuntu 14.10, maybe someone should look into what Xubuntu is doing differently.