I successfully solved this problem by reinstalling windows and then installing Ubuntu.
On Thu, May 10, 2018, 9:41 PM Graham Mitchell <1767...@bugs.launchpad.net> wrote: > I've been running Linux as my sole OS since 2001 and have been dual- > booting Windows and Linux since the summer of 2015. > > In particular, Windows 7 with Ubuntu 15.04. > > Upgraded in-place to 15.10 in December 2015. Then to 16.04 in May 2016. > Upgraded the Windows side to Windows 10 without issue in July 2016. Then > Ubuntu 16.10 in October of that year. Then 17.04 when it came out then > 17.10, and finally 18.04 -- all upgraded in place. > > However, I managed to hit some Ubiquity bug, so video game performance was > degraded: > https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1733136 > > I tried following the steps in the bug and messed something up, > corrupting my graphical system. > > No worries! Just make a Ubuntu 18.04 boot disk and fix things that way! > Guess I'm due for a clean install anyway. > > Used my wife's Windows PC to make a bootable USB installer and booted my > machine off of that. Told it to install "alongside" the existing Ubuntu > partition. Install seems normal and takes fifteen minutes or so. At the > VERY end: ERROR. "Sorry, your system might be in an unusable state." Um, > thanks? > > Tried lots and lots of things. No dice. Everything I tried THOUGHT it > could install Ubuntu just fine but then would error out at the very end. > > Eventually I just had to remove all the partitions from the disk and > create one new single EXT4 partition and install Ubuntu from scratch. > Which actually worked. > > Lost all the files on my Windows partition, since I never dreamed that > an Ubuntu installer in 2018 would mess THAT up. Would have lost my Linux > files, too, but I actually back those up and in particular had done a > full backup the night before "just in case." > > This is a bug. > > If the installer can't successfully do its thing, it needs to tell the > user that BEFORE it has permanently altered partitions with gParted. > > Bugs happen. I get that. I ain't even mad. > > But to call a bug with 173 duplicates "invalid" just because the very > first person who successfully reported it theoretically had a workaround > is unacceptable. > > Our situations are not the same as theirs. > > > A warning message prompted you that this > > could be a problem and recommended performing a bios mode install > > instead, but you chose not to > > This is literally false. I never saw any such message. My bug is marked > as a duplicate of this bug. So either mine is not a duplicate or this > bug should still be OPEN. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1767418). > https://bugs.launchpad.net/bugs/1767703 > > Title: > Calling 'apt-install grub-efi-amd64-signed' failed > > Status in grub-installer package in Ubuntu: > Incomplete > > Bug description: > /plugininstall.py: Exception during installation: > /plugininstall.py: Traceback (most recent call last): > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line > 1739, in <module> > /plugininstall.py: install.run() > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line > 61, in wrapper > /plugininstall.py: func(self) > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line > 227, in run > /plugininstall.py: self.configure_bootloader() > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line > 971, in configure_bootloader > /plugininstall.py: "GrubInstaller failed with code %d" % ret) > /plugininstall.py: ubiquity.install_misc.InstallStepError: GrubInstaller > failed with code 1 > > ************************ > > +++++++++++++++++++++++++++++++++++++++++++++ > MBR-EFI-GPT explanations/requirements: > > > https://askubuntu.com/questions/500359/efi-boot-partition-and-biosgrub-partition > > https://askubuntu.com/questions/831216/how-can-i-reinstall-grub-to-the-efi-partition > > https://askubuntu.com/questions/578928/why-i-need-several-boot-partitions-efi-and-bios-grub > +++++++++++++++++++++++++++++++++++++++++++++ > > Manual fix: > > https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1766945/comments/3 > > also see: https://bugs.launchpad.net/ubuntu/+source/grub- > installer/+bug/1763441/comments/2 > > https://help.ubuntu.com/community/Boot-Repair > > https://ubuntuforums.org/showthread.php?t=2390700 > > ************************ > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: ubiquity 18.04.14 > ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 > Uname: Linux 4.15.0-20-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7 > Architecture: amd64 > CasperVersion: 1.394 > CurrentDesktop: ubuntu:GNOME > Date: Sat Apr 28 20:39:35 2018 > InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz > file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- > LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 > (20180426) > ProcEnviron: > LANGUAGE=de_DE.UTF-8 > PATH=(custom, no user) > XDG_RUNTIME_DIR=<set> > LANG=de_DE.UTF-8 > LC_NUMERIC=C.UTF-8 > SourcePackage: grub-installer > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1767703/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767703 Title: Calling 'apt-install grub-efi-amd64-signed' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1767703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
