Yes Micheal, that's all anyone confronted with this bug needs to do initially so they can boot.
After booting they should also open a terminal and issue one of the following commands: For amd64 systems: sudo apt-mark hold libepoxy-dev libepoxy0 libepoxy0:i386 For i386 systems: sudo apt-mark hold libepoxy-dev libepoxy0 This will prevent libepoxy0 from being updated until this bug is fixed. Note that if you use programs like Synaptic libepoxy0 needs to be locked there as well. And by the way, the only reason I wasn't able to use recovery mode initially was because I didn't know libepoxy0 was the culprit. About 15 updates appeared together, with several of them being for Mir which is what I initially suspected caused the problem. Since I wasn't sure what was wrong it took awhile for me to whittle it down to libepoxy0. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1698233 Title: New libepoxy0 causes hang at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libepoxy/+bug/1698233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
