Comment 5 for bug 1723806

Whether ubiquity is installable is a different issue than console-setup breaking on upgrade though. The ubiquity change is being reverted, but we still need to figure out why the console-setup upgrade fails.

I've attempted to set up a virtual machine with Ubuntu Server, where I can approximate the upgrade procedure for both server or desktop (by changing whether and which plymouth splash shows). I haven't been able to reproduce the issue yet.

It really looks to me like it's an issue with speaking to plymouth while doing updates unattended, but am I wrong on that assumption?

And if it's indeed unattended upgrades, what does /boot/grub/grub.cfg look like on the affected system?