Currently installing 16.04 final and I still got "ubi-prepare failed
with exit code 255", so I disabled secure boot. Will I have to reinstall
once this gets fixed so I can use secure boot. Or is it really enough to
run "sudo mokutil --disable-validation" and then enable secure boot in
BIOS ?
--
I tried the latest nightly with fix and didn't get this error. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567445
Title:
ubi-prepare failed with exit code 255
To manage notifications
@cyphermox what's the best way of trying the fix? Can I just get updated
packages with the beta2 or should I wait for this to get into a nightly
build (and if so when do the nightlies get made)?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug was fixed in the package ubiquity - 2.21.57
---
ubiquity (2.21.57) xenial; urgency=medium
[ Mathieu Trudel-Lapierre ]
* Automatic update of included source packages: localechooser
2.65ubuntu4. (LP: #1551285)
* scripts/simple-plugins: better handle passing the MokPW
** Branch linked: lp:ubiquity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567445
Title:
ubi-prepare failed with exit code 255
To manage notifications about this bug go to:
There's a couple of issues here, not just the one with mokutil -- looks
like your system is also failing to download all the right packages for
your third-party drivers.
I'll fix the failure because of mokutil now; this is simply because
mokutil and the kernel tend to disagree about the result of
I am, yes. The only change I made was to disable secure boot, I didn't
enable legacy ROMs and I left UEFI (?) turned on.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567445
Title:
ubi-prepare
@matthew-wilson - were you able to successfully install and dual boot
win 10 doing that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567445
Title:
ubi-prepare failed with exit code 255
To
Should have said, but this was on a Dell XPS 15 9550, with Windows 10
already pre-installed.
Workaround for me was to disable SecureBoot manually in the BIOS before
booting the 16.04 installer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'd also like to know how "now or never" this actually is. I've been
trying to find documentation about this feature but haven't succeeded so
far.
@matthew-wilson: once I had the error I'd always get it on retry no
matter what options I chose. On reboot (or maybe just restarting
ubiquity, can't
Incidentally the wording around this SecureBoot disabling stuff is very
"now or never" -- makes it sound like you'll never be able to install
the proprietary drivers unless you do this NOW, which is slightly scary.
Is that actually the case or can you do this later if you want?
--
You received
I have this issue too with 16.04 beta 2
Initially I tried the 'disable SecureBoot' option, but after trying
again with this option unchecked I still see the error.
I see this line in syslog:
ubuntu ubiquity: Failed to request new SB state
--
You received this bug notification because you are
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567445
Title:
ubi-prepare failed with exit code 255
To manage notifications
However choosing to not enable third-party repos and not download along
side installation seems to have solved the issue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567445
Title:
ubi-prepare
I have the same issue, although checking or unchecking secure boot has
no effect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567445
Title:
ubi-prepare failed with exit code 255
To manage
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567445
Title:
I tried running the installer again and determined that this only
happens if I tick the "disable secure boot" option.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567445
Title:
ubi-prepare failed
17 matches
Mail list logo
