Wonderful news! I'm glad we finally have a proper bug we can track.
Thanks for the update.
--
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' f
There used to be a prompt that while worded poorly, did give you the
ability to switch to a bios mode install even though you booted the
installer in UEFI mode, but it was removed in 18.04. Unfortunately,
instead of making it switch to a bios mode install by default, it keeps
with the UEFI install
I have also tried to install 18.04 LTS and it failed several times.
Seeking a solution I read somewhere about leaving 1-2 MB of space before efi
partition. In the beginning of linux era as I remember there was a practice of
leaving some space before adding partitions.
So I did so through Ubuntu i
For the record, this bug is in the top 30 out of ALL of Ubuntu by bug
heat: https://bugs.launchpad.net/ubuntu/+bugs?orderby=-heat&start=0
--
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:
> I did get the warning.
I'm sure you did. With 293 people affected by this bug I'm sure there
are some that got a warning and ignored it.
I agree with Till; there is definitely something wrong with the
detection in some component somewhere.
--
You received this bug notification because you are
I didn't get any warning either.
So there is probably something wrong with the detection, if a warning
should be displayed.
--
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
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for
Windows 10
From: Graham Mitchell<mailto:1767...@bugs.launchpad.net>
Sent: 07 June 2018 03:30
To: redbubb...@hotmail.com<mailto:redbubb...@hotmail.com>
Subject: [Bug 1767703] Re: Calling 'apt-install grub-e
> A warning message prompted you that this could be a problem
Why do you keep saying this?
I ran the installer maybe five or six times and NEVER saw ANY warning
message. Stop claiming that I did.
This bug is NOT invalid.
** Changed in: grub-installer (Ubuntu)
Status: Invalid => Incomple
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. A warning message prompted you that this
could be a problem and recommended performing a bios mode install
instead, but you chose not to. You either need to perform the bios mode
install, or partition
El problema ha sido solucionado muchas gracias a todos.
** Changed in: grub-installer (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: grub-installer (Ubuntu)
Assignee: (unassigned) => Carlos centurión (carloscent2)
--
You received this bug notification because you are a memb
: boun...@canonical.com on behalf of apt-ghetto
<1767...@bugs.launchpad.net>
Sent: Tuesday, May 22, 2018 4:21:02 PM
To: redbubb...@hotmail.com
Subject: [Bug 1767703] Re: Calling 'apt-install grub-efi-amd64-signed' failed
To get a working dual boot, you have to install both operating systems
To get a working dual boot, you have to install both operating systems in the
same mode.
Of course, if you have a lot of time and patience, you can reinstall Windows.
Reinstalling Ubuntu in the same mode as Windows is normally the faster way.
--
You received this bug notification because you ar
Thanks for the info.
On Tue 22 May, 2018, 12:06 PM phyzzy2008, <1767...@bugs.launchpad.net>
wrote:
> Lenovo Z570
> If you create a /boot/efi partition (Fat32) first Ubuntu 18.04 installs BUT
> you cannot boot Windows 7 which is install legacy/bios boot. The only way I
> could solve it was to dele
Lenovo Z570
If you create a /boot/efi partition (Fat32) first Ubuntu 18.04 installs BUT
you cannot boot Windows 7 which is install legacy/bios boot. The only way I
could solve it was to delete all the partitions and reinstall Windows 7 in
UEFI boot mode. Then you can install 18.04 and boot either O
As far as I can see, the problem occurs only if the disk is MBR/MSDOS
formatted and the installer is booted in the EFI mode. So we should
create some test cases and test.
Test case 1:
Prerequisites:
- one disk; partition table -> GPT
- no EFI-System-Partition
- The installer is booted in EFI m
Is this a "grub-installer" bug -or- is the use of grub in "ubiquity" the
problem ???
If the latter, then this bug should be assigned to the "ubiquity"
package...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
I've tried boot-repair and many other solutions, but I was always
getting an error that boot/efi directory was not found. Finally I tried
disabling the UEFI mode and it worked like a charm. I don't know why
I've never seen anyone mention to disable this, instead I just found
more discription of how
e live
> dvd or usb too.
>
>
> Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for
> Windows 10
>
>
>
> From: boun...@canonical.com on behalf of uthi <
> a132...@yandex.ru>
> Sent: Friday, May 18, 2018 4:35
ows 10
From: boun...@canonical.com on behalf of uthi
Sent: Friday, May 18, 2018 4:35:52 AM
To: johnnie...@hotmail.com
Subject: [Bug 1767703] Re: Calling 'apt-install grub-efi-amd64-signed' failed
> In ubuntu 18.04 you need to select it manually while booting up.
Yes, user can
> In ubuntu 18.04 you need to select it manually while booting up.
Yes, user can select UEFI mode or BIOS at boot time of installation, but
somehow UEFI mode installation of opensuse (thumbleweed) works fine, but
1804 is not (on same disk and machine).
Also UEFI mode installation 1804 on that mac
I believe that some message during installation should appear. It should
explain issue about UEFI and give the recommendation to change the drive
or to reboot in legacy mode.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
This should be the same if you use a bootable DVD instead of bootable
flash drive.
--
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
May be I was too rude in my previous comment.
But this is actually as simple as selecting the right mode while booting up
your machine.
In ubuntu 14.04 and 16.04 the selection window ware coming while installation.
In ubuntu 18.04 you need to select it manually while booting up.
The process is e
@Kamrul Hasan
> This is just a user fault.
Once again - installation of 1404 and 1604 on same disk was fine.
But installation 1804 has error - is it user fault of that ?
Is user need to wipe disk and install 1804 ? (yes, that works ok)
Or repartition disk, or buy the new one ?
On same disk opensu
True.
I faced the same problems at first.
Anyway, a Linux user should be a little more advanced.
And as because we do not have the possibility to get the fixed version very
soon, we as a user should try to learn a bit more.
Yes, I have realized later that it is a bug and also an user fault.
I a
> Is this really a bug?
When the previous LTS had not problems in these situations, then it's
not only a bug but a regression as well.
When a large portion of your user-base is experiencing trouble where
they don't expect it and/or had none before, it should be fixed.
Especially when a fix is (ea
Sorry, but I used a CD from Umbuntu. And Not all User been so smart like
you.
Kamrul Hasan schrieb am Do., 17. Mai 2018, 18:21:
> Is this really a bug?
> In my opinion it is not.
> This is just a user fault.
>
> The solution of this problem relies on two basic steps. At first you
> need to creat
I am just an user, not an linux expert. In my opinion your reaction is
very inapropiate !
Numai bine !
Alexandru Butoi
Tel. 0720015213
On Thursday, May 17, 2018, 7:41:30 PM GMT+3, Yasin Balcancı
<1767...@bugs.launchpad.net> wrote:
Yes I learnt about it afterwards and solved the proble
Yes I learnt about it afterwards and solved the problem somehow. Thanks.
17 May 2018 Per, saat 19:21 tarihinde Kamrul Hasan şunu
yazdı:
> Is this really a bug?
> In my opinion it is not.
> This is just a user fault.
>
> The solution of this problem relies on two basic steps. At first you
> need
Is this really a bug?
In my opinion it is not.
This is just a user fault.
The solution of this problem relies on two basic steps. At first you
need to create your Ubuntu 18.04 bootable flash drive correctly. And
secondly, you need to bootup you machine using the bootable flash drive
in the correct
For the people who are looking for a workaround; I think you have three
options:
- Use a GPT partition table on the disk
- Boot the installer in legacy mode
- When both are not an option (or fail), use the workaround described in:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/17716
Sorry I could not find the old edit link to go and edit my post so I
repeat the part that need modifications/
My conclusion is Moderator must now file this as real bugs in 18.04
The bugs lies in the 4 parts.
1. It did not detect that we have BIOS mode installations in place,
like the 16.04.4
Can anybody confirm that the workaround in the bug report below works?
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1771651
If so, then it could be a duplicate...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
@Graham Mitchell (graham-grahammitchell)
I view the same as yours.
More though, there is or are the bugs somewhere in the new 18.04 Ubuntu, Kylyn,
Lubuntu.
I confirmed the problems.
https://askubuntu.com/questions/1028921/the-grub-efi-amd64-signed-
package-failed-to-install-into-target-during-in
ink/?LinkId=550986> for
Windows 10
From: boun...@canonical.com on behalf of Graham
Mitchell <1767...@bugs.launchpad.net>
Sent: Tuesday, May 15, 2018 11:08:44 AM
To: johnnie...@hotmail.com
Subject: [Bug 1767703] Re: Calling 'apt-install grub-efi-amd64-signe
Thanks for weighing in.
I don't mean to imply that there's a bug in Ubiquity. But there's
clearly a failure somewhere in the installation process.
And I'm going to complain every time this bug is closed as "invalid"
until there's a more appropriate bug to reference.
--
You received this bug not
@Graham & others complaining
Take note that the installer has been designed more than a decade ago; but
recent hardware have introduced some ubknown concept a few years back:
uefi/efi, gpt, nvme.
That is way different than the 'legacy' mode known by ubiquity.
Server has already a new installer,
There are some edge cases when the user's disk is partitioned to boot in
bios mode, but the EFI mode installer doesn't detect it.
There is supposed to be a warning message about this combination but it
does not always show up -- as evidenced by this thread.
For these users, there is NO indication
** Changed in: grub-installer (Ubuntu)
Status: Invalid => Confirmed
--
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
@Luis Tobias
Why "Invalid" again ?
Many users has that problem and no solution.
--
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 m
** Changed in: grub-installer (Ubuntu)
Status: Incomplete => Invalid
--
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
@Abheek Gogoi
You think it is the solution ? )
Last time i tried install on my sdf disk in UEFI mode - at end grub failed to
install on disk sda, why sda ?
In BIOS mode installation was succesfull, but then nvdidia drivers bings black
screen
(https://bugs.launchpad.net/ubuntu/+source/nvidia-gr
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.
>
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 Jul
On same system (disk) older 1604 intalls fine, but 1804 is not - this is not
enough for bug to be accepted ?
Maybe installer should call not grub-efi-amd64-signed but something else ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
@psusi
you have answered (#37) to the OP and was right to set the report as
'invalid'. But a lot of dupes also exist; that is why some links have
been added on top of the report to teach and educate users hiting such
issue.
Please let that report opened to let people find it and give them some
pa
Greetings!!
The disk originally had only windows 10, a diagnostics partition and a
system restore partition.
I can not wipe windows to let Linux use the entire disk.
Also, there is no room to create a larger boot area on /dev/sda.
I burned a DVD from the iso using Brasero - and I have no id
I booted windows 10 and ubuntu 16.04 uefi before trying to I stall
18.04.
I did NOT receive any such warning whatsoever when trying to I stall
18.04.. Don't know where you got that idea.
I tried custom partitioning and creating an efi partition but 18.04
simply will not install grub.
I booted 16
--
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/+sourc
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. A warning message prompted you that this
could be a problem and recommended performing a bios mode install
instead, but you chose not to. You either need to perform the bios mode
install, or partition
My problem was due to a previous Windows installation which was done in
Legacy mode. Thus, installing ubuntu in legacy mode solved the issue.
This is not a bug rather a fail on my side because I did not realised
the Windows installation had created a NTFS recovery partition instead
of an EFI one. M
** Description changed:
/plugininstall.py: Exception during installation:
/plugininstall.py: Traceback (most recent call last):
/plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1739,
in
/plugininstall.py: install.run()
/plugininstall.py: File "/usr/share/ubi
** Description changed:
/plugininstall.py: Exception during installation:
/plugininstall.py: Traceback (most recent call last):
/plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1739,
in
/plugininstall.py: install.run()
/plugininstall.py: File "/usr/share/ubi
To create an efi-partition during install, just create a partition and choose
efi instead of ext4.
If I remember correctly, it should be at least 100MB and the default one,
Ubuntu creates on automatic installation is about 500MB.
--
You received this bug notification because you are a member of
Thank you
On Tue, May 8, 2018, 16:41 dino99 <1767...@bugs.launchpad.net> wrote:
> ** Description changed:
>
> /plugininstall.py: Exception during installation:
> /plugininstall.py: Traceback (most recent call last):
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
>
** Description changed:
/plugininstall.py: Exception during installation:
/plugininstall.py: Traceback (most recent call last):
/plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1739,
in
/plugininstall.py: install.run()
/plugininstall.py: File "/usr/share/ubi
Actually, I just shift to an older version of lubuntu, 16 if I'm correct.
It worked perfectly. Thanks for your help everyone.
Le mardi 8 mai 2018, Tommi <1767...@bugs.launchpad.net> a écrit :
> I can confirm, that it affected my system as well (see
> https://bugs.launchpad.net/ubuntu/+source/grub
I can confirm, that it affected my system as well (see
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1769732) trying
to install on a non-UEFI system.
BIOS settings for USB-Boot were set to UEFI-Boot, though.
I changed the settings in BIOS, no need to change anything on the
instal
** Description changed:
/plugininstall.py: Exception during installation:
/plugininstall.py: Traceback (most recent call last):
/plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1739,
in
/plugininstall.py: install.run()
/plugininstall.py: File "/usr/share/ubi
How do i create an efi-partition during install of 18.04.i also want manual
partitioning as i also have multiple drives.TIA
On Sat, May 5, 2018 at 5:59 PM, Till wrote:
> I chose to manually create the partitions during install, to optimize the
> use of multiple hard drives. And I just forgot to
I chose to manually create the partitions during install, to optimize the use
of multiple hard drives. And I just forgot to create an efi-partition.
Since this was a fresh install on a new computer, that was easy to fix, so for
me everything is fine now. A warning "You don't have an efi-partitio
Boot repair failed for me with "grub-efi-amd04signed" package failed to install
Partitioning from a Live CD to create an EFI system partition failed as there
were already four partitions on the drive (dual boot with W7).
Trying grub-install . error: failed to get canonical path of `/cow'
Tried
Thank you everyone.
Actually I solved the problem using an older version of Lubuntu.
I don't know what was the problem but it works perfectly now.
2018-05-04 18:57 GMT+03:00 ziya <1767...@bugs.launchpad.net>:
> Thanks!
>
> On Fri 4 May, 2018, 1:41 AM Mohammad Hossein Shakouri, <
> mhshako...@g
Thanks!
On Fri 4 May, 2018, 1:41 AM Mohammad Hossein Shakouri,
wrote:
> I was trying to install ubuntu 18.04.14 on a surface pro 4 and using all
> the disk for installation when it failed. I've tried to install it while
> formatting the whole disk and I've not yet tried to install it along
> sid
I was trying to install ubuntu 18.04.14 on a surface pro 4 and using all
the disk for installation when it failed. I've tried to install it while
formatting the whole disk and I've not yet tried to install it along
side windows. I will see what goes on while doing that.
--
You received this bug n
** Tags added: id-5aeac9d8ebe9d61d64e1304e
--
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
when i try to use legacy instead of uefi it says that i have to update my
microcode to 0x20
i am using lenovo z50 70 and i have tried alot of solutions there but it
did nothing
On Wed, 2 May 2018, 7:21 pm Niranjan Shrestha, <1767...@bugs.launchpad.net>
wrote:
> I solved the problem using legacy b
@apt-ghetto (apt-ghetto)
yes, also, as it is fully described in the links above.
Tschüß
--
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' faile
@Gil0224, that is not true.
GPT is part of the UEFI standard, but you can install a Linux OS also in
BIOS Legacy mode on a GPT formatted disk (you need a bios_grub-
partition). On the other side you can install a Linux OS on a MBR
formatted disk in UEFI mode.
If you install in the UEFI mode, you
Hi
Just a precision for the installation of a Linux OS.
To use the UEFI mode, a "gpt" partition is needed to load the OS (not a
"mbr" formatted disk, compatible with the "BIOS-legacy" mode).
Here to find more information:
https://help.ubuntu.com/community/UEFI
https://www.happyassassin.net/201
Success!
On Wed 2 May, 2018, 10:51 PM Niranjan Shrestha, <1767...@bugs.launchpad.net>
wrote:
> I solved the problem using legacy boot mode rather than UEFI.
>
> On 2 May 2018 at 19:38, Keshav Parankusham
> wrote:
>
> > I tried to use boot-repair, but it's giving the error efi directory not
> > f
I solved the problem using legacy boot mode rather than UEFI.
On 2 May 2018 at 19:38, Keshav Parankusham
wrote:
> I tried to use boot-repair, but it's giving the error efi directory not
> found. I tried fresh download and also tried multiple times by trying to
> format a partition in the front o
I tried to use boot-repair, but it's giving the error efi directory not
found. I tried fresh download and also tried multiple times by trying to
format a partition in the front of the disk, every time some booting
problem occurs, but boot-repair used to work.
--
You received this bug notification
Extreme Thanks, UEFI failed also destroyed my boot loader and I had a
dead machine for a while. Working again now.
Sent from Mail for Windows 10
From: Dhanraj Prem Kotian
Sent: Tuesday, May 1, 2018 12:51 PM
To: gvf0...@yahoo.com
Subject: [Bug 1767703] Re: Calling 'apt-install grub-efi-
Awesome, thanks!
On Wed 2 May, 2018, 1:21 AM Dhanraj Prem Kotian, <1767...@bugs.launchpad.net>
wrote:
> The way I solved this problem was simple. I had the option of installing
> Ubuntu 18.04 LTS, either using uefi mode or the device boot option
> (invoked through the BIOS startup by pressing ESC
The way I solved this problem was simple. I had the option of installing
Ubuntu 18.04 LTS, either using uefi mode or the device boot option
(invoked through the BIOS startup by pressing ESC or F2). When I
installed using uefi mode, I got this error. What I did next was to boot
my USB through the de
Thanks a lot!
On Wed 2 May, 2018, 12:11 AM TaHkictOnlin,
wrote:
> I do not know what to say to you, because I solved my problem. discuss
> the topic further yourself, and I'm leaving, the forum is too
> complicated for my understanding, goodbye.
>
> --
> You received this bug notification becaus
I do not know what to say to you, because I solved my problem. discuss
the topic further yourself, and I'm leaving, the forum is too
complicated for my understanding, goodbye.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
I formatted my laptop... I couldnt install grub..hence i freshly installed
windows and then ubuntu as a dual boot..this time i didn't find error.
Before formatting:
i was unable to instal grub..i tried boot repair..even it was able to
rectify during the repair process..but while installing ubunt
Done
On Tue 1 May, 2018, 8:41 PM dino99, <1767...@bugs.launchpad.net> wrote:
> ** Description changed:
>
> /plugininstall.py: Exception during installation:
> /plugininstall.py: Traceback (most recent call last):
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 173
** Description changed:
/plugininstall.py: Exception during installation:
/plugininstall.py: Traceback (most recent call last):
/plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1739,
in
/plugininstall.py: install.run()
/plugininstall.py: File "/usr/share/ubi
Boot repair Works for me. Thanks a lot for attention.
Em seg, 30 de abr de 2018 07:50, Alejandro <1767...@bugs.launchpad.net>
escreveu:
> I run kill disk. Then reinstall ubuntu 18.04 lts. It works
>
> On Mon, Apr 30, 2018, 6:31 PM massimo roccaforte <
> 1767...@bugs.launchpad.net>
> wrote:
>
> >
I run kill disk. Then reinstall ubuntu 18.04 lts. It works
On Mon, Apr 30, 2018, 6:31 PM massimo roccaforte <1767...@bugs.launchpad.net>
wrote:
> It worked.
>
> Il Lun 30 Apr 2018, 12:20 TaHkictOnlin <1767...@bugs.launchpad.net> ha
> scritto:
>
> > boot repair is a special recovery disk that allo
It worked.
Il Lun 30 Apr 2018, 12:20 TaHkictOnlin <1767...@bugs.launchpad.net> ha
scritto:
> boot repair is a special recovery disk that allows, for example, to
> restore the windows boot after installing linux and vice versa. You can
> download it at SourceForge.net.
>
> --
> You received this b
boot repair is a special recovery disk that allows, for example, to
restore the windows boot after installing linux and vice versa. You can
download it at SourceForge.net.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
i'm used bios "legacy" boot
intallation ok
thank's
2018-04-30 3:06 GMT+02:00 Eduardo D. Dequilla :
> Dear Sir:
> Kindly clarify what do you mean by recovery disk Boot-repair ? How did you
> solve the problem using this disk?
>
> Thank you very much.
>
>
> On Sun, Apr 29, 2018 at 8:39 PM, TaHkictO
Dear Sir:
Kindly clarify what do you mean by recovery disk Boot-repair ? How did you
solve the problem using this disk?
Thank you very much.
On Sun, Apr 29, 2018 at 8:39 PM, TaHkictOnlin <1767...@bugs.launchpad.net>
wrote:
> I use the recovery disk Boot-repair solved the problem, I apologize fo
I use the recovery disk Boot-repair solved the problem, I apologize for
the trouble, now everything works.
--
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-
** Description changed:
/plugininstall.py: Exception during installation:
/plugininstall.py: Traceback (most recent call last):
/plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1739,
in
/plugininstall.py: install.run()
/plugininstall.py: File "/usr/share/ubi
** Description changed:
/plugininstall.py: Exception during installation:
/plugininstall.py: Traceback (most recent call last):
/plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1739,
in
/plugininstall.py: install.run()
/plugininstall.py: File "/usr/share/ubi
Ok
Reinstallato con BIOS legacy
Il Dom 29 Apr 2018, 09:30 dino99 <1767...@bugs.launchpad.net> ha
scritto:
> ** Summary changed:
>
> - bootmanger : Calling 'apt-install grub-efi-amd64-signed' failed
> + Calling 'apt-install grub-efi-amd64-signed' failed
>
> --
> You received this bug notification
** Description changed:
- i dont now.
+ /plugininstall.py: Exception during installation:
+ /plugininstall.py: Traceback (most recent call last):
+ /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1739,
in
+ /plugininstall.py: install.run()
+ /plugininstall.py: File "
** Summary changed:
- bootmanger : Calling 'apt-install grub-efi-amd64-signed' failed
+ Calling 'apt-install grub-efi-amd64-signed' failed
--
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:
93 matches
Mail list logo
