Comment 4 for bug 1674327

My issue is now resolved.

I had already run the commands and rebooted and the issue went away. I was unsure, however, whether or not simply getting into this state was worthy of having the bug reported.

It had been several months since I had rebooted (even through several updates, etc.) so I wasn't too surprised when finally an update failed.