Comment 77 for bug 1333140

This isn't caused by ubiquity if it's at startup, since ubiquity would only care about it w/r/t partitioning, and that hasn't been the case since somewhere during the development cycle of 16.04 -- when we updated partman-base to stop trying to partition rpmb devices.

Closing the ubiquity task as Invalid. Clearly, there's something else that breaks there.