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? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1723806 Title: 1.108ubuntu15.4 hangs on upgrade Status in console-setup package in Ubuntu: New Bug description: There is an SRU for 1.108ubuntu15.4 in xenial-proposed that hangs for me on upgrade, causing updates to get stuck across the system. Haven't tracked it down further than that but wanted to report a bug quickly to prevent further promotion of the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1723806/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
