** Patch added: "Debdiff for hirsute"
https://bugs.launchpad.net/ubuntu/+source/lxqt-policykit/+bug/1875774/+attachment/5538459/+files/lxqt-policykit_hirsute.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
** Patch removed: "lxqt-policykit_focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lxqt-policykit/+bug/1875774/+attachment/5523557/+files/lxqt-policykit_focal.debdiff
** Patch removed: "lxqt-policykit_hirsute.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lxqt-policykit/+bug/18
debdiff for focal
** Description changed:
[Impact]
On Lubuntu systems with more than one sudoer, lxqt-policykit prior to version
0.17.0 crashes due to calling g_object_unref twice on the same object.
[Test Plan]
STEPS TO REPRODUCE
==
1. Boot post-18.04 Lubuntu
debdiff for hirsute
** Patch added: "lxqt-policykit_hirsute.debdiff"
https://bugs.launchpad.net/lxqt/+bug/1875774/+attachment/5523268/+files/lxqt-policykit_hirsute.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
** Description changed:
+ [Impact]
+ On Lubuntu systems with more than one sudoer, lxqt-policykit prior to version
0.17.0 crashes due to calling g_object_unref twice on the same object.
+
+ [Test Plan]
STEPS TO REPRODUCE
==
- 1. Boot post-18.04 Lubuntu
- 2. Use lxqt-admin-u
The support for Lubuntu 18.04 ended
** Changed in: leafpad (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775980
Title:
Add PolicyKit action to leafpad packag
@supernoob3000
20.10 is still using kernel 5.8.
If you want help, you should open a new bug report and describe all the
steps and configuration changes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
I had the same issue with emacs-nox, but I have installed it on Windows
10 inside of WSL2 with Ubuntu 18.04.
I was able to workaround the issue with:
gpg --homedir ~/.emacs.d/elpa/gnupg --keyserver hkps://keyserver.ubuntu.com:443
--receive-keys 066DAFCB81E42C40
After successfully importing the k
Thank you for this solution. It is working again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878045
Title:
doing dist-upgrade got error related do Broadcom
To manage notifications about this bu
*** This bug is a duplicate of bug 1878045 ***
https://bugs.launchpad.net/bugs/1878045
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1878045, so it is being marked as such. Please look
*** This bug is a duplicate of bug 1878045 ***
https://bugs.launchpad.net/bugs/1878045
** This bug is no longer a duplicate of bug 1876919
6.30.223.271+bdcom-0ubuntu6 fails when building on kernel 5.4.0-28-generic
x86_64 (Ubuntu Groovy 20.10 dev.branch)
** This bug has been marked a duplic
*** This bug is a duplicate of bug 1878045 ***
https://bugs.launchpad.net/bugs/1878045
** This bug has been marked a duplicate of bug 1878045
doing dist-upgrade got error related do Broadcom
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
*** This bug is a duplicate of bug 1876919 ***
https://bugs.launchpad.net/bugs/1876919
Public bug reported:
Output from apt full-upgrade
bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu6) wird eingerichtet ...
Removing old bcmwl-6.30.223.271+bdcom DKMS files...
--
Public bug reported:
[Summary]
During the installation process, the file /etc/apt/sources.list is
generated from a template. If an HTTPError occurs, then instead of
logging a message, an AttributeError is raised.
[Test Case]
Steps to reproduce
--
1. Start the installer.
2. When
*** This bug is a duplicate of bug 1871884 ***
https://bugs.launchpad.net/bugs/1871884
** This bug has been marked a duplicate of bug 1871884
"EFI system partition flag not set" - false pop-up
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
*** This bug is a duplicate of bug 1873008 ***
https://bugs.launchpad.net/bugs/1873008
** This bug has been marked a duplicate of bug 1873008
package lubuntu-grub-theme (not installed) failed to install/upgrade: error
creating symbolic link
'./boot/grub/themes/lubuntu-grub-theme/icons/ubu
** Also affects: lubuntu-artwork (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lubuntu-artwork (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/b
@jibel Your typical use case (install in BIOS mode and reboot into UEFI
mode) ends typically in an error. There is no bootloader installed on
/boot/efi/EFI/ubuntu and there is no boot entry in the NVRAM, which
would point to shim or grub on the ESP.
The typical user has to replace grub-pc with gru
@jibel Thank you for explaining this.
Is it somewhere documented, why a EFI system partition is created on a
system, which is installed in BIOS mode?
I would expect a separate /boot partition with ext2 or ext4 and the ESP
(with the efi images for grub, shim and mok) only for systems which are
boo
Thank you for reporting this bug. I can confirm this behaviour with:
- virtual machine (qemu)
- booted in BIOS mode
- use the empty disk and choose ZFS automatism
I am not sure, if the created /etc/fstab is product of a bug or an
feature.
** Changed in: lubuntu-artwork (Ubuntu)
Status: Inc
Where does the fstab entry "/boot/efi/grub /boot/grub none defaults,bind
0 0" come from? Was it added automatically by the installer? Or did you
add it manually?
** Changed in: lubuntu-artwork (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a membe
*** This bug is a duplicate of bug 1873008 ***
https://bugs.launchpad.net/bugs/1873008
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Marking this as a duplicate of bug 1873008. Please look
at the other bug report to see if there is any missing information
After installing snapd, do a logout and login. Then you should see, that
both $PATH and $XDG_DATA_DIRS contain the paths for snappy applications.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871602
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.
** Changed in: snapd (Ubuntu)
Sta
Maybe the snapd packagers should not rely on the assumption, that every
user is using bash as login shell? More and more programs are only
available as snaps, e.g. chromium-browser.
Meanwhile I have added "emulate sh -c 'source /etc/profile'" to
/etc/zsh/zprofile to work around this issue. But a
No, pkexec per default does not start a graphical application for security
reasons.
If you want to start a graphical application with pkexec, you need a policy in
/usr/share/polkit-1/actions.
But, nowadays, it mostly isn't necessary to start a graphical
application with elevated privileges, beca
Setting to incomplete, because 18.10 is out of support and with 19.04 I
could not reproduce it.
** Changed in: lxqt-panel (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Hi Chris Guiver,
Thank you for testing. I think, you are getting the results as described
in "Current behaviour". And yes, you should not install "lxlock".
Please check the installed version of "lubuntu-default-settings" with `apt
policy lubuntu-default-settings`.
If you have version 0.54.2, the
** Patch added: "lubuntu-default-settings_0.54.3.debdiff"
https://bugs.launchpad.net/ubuntu/bionic/+source/lubuntu-default-settings/+bug/1812594/+attachment/5279787/+files/lubuntu-default-settings_0.54.3.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Description changed:
+ [Summary]
+
+ Instead to light-locker-command, the keyboard shortcut to lock the screen is
bound to lxlock. The problem is, that lxlock is not included in the iso of the
first two point releases (18.04 and 18.04.1) and therefore, the shortcut does
not work.
+ The abil
Thank you for filing this bug report.
In my opinion, this bug is not caused by grub2, but by a configuration
file in calamares-settings-ubuntu.
During installation the variable GRUB_DISTRIBUTOR in /etc/default/grub
is set to 'Lubuntu 19.04' instead of `lsb_release -i -s 2> /dev/null ||
echo Debia
** Changed in: calamares-settings-ubuntu (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/1833490
Title:
lubuntu grub-install puts efi in the wrong directory -
** Also affects: calamares-settings-ubuntu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833490
Title:
lubuntu grub-install puts efi in the wron
** Changed in: lubuntu-default-settings (Ubuntu)
Status: Triaged => In Progress
** Changed in: lubuntu-default-settings (Ubuntu)
Assignee: (unassigned) => apt-ghetto (apt-ghetto)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Hi @rinni,
On Lubuntu 19.10, the value for gpgExecutable in ~/.config/IJHack/QtPass.conf
is not set.
After installing gnupg2 and moving/deleting ~/.config/IJHack/QtPass.conf and
starting QtPass, it recreates the config file with gptExecutable=/usr/bin/gpg2
and it works.
After git grepping:
I g
Now I understand, what you mean with the asterisks.
I think, it is normal to hide the passwords. And you have to enter the password
twice, to ensure, that there are no typos. (And from a security point of view,
it would be even better not to show the asterisks)
During the installation, it uses th
Thank you for reporting this issue.
I have made a new installation of Lubuntu 19.04 in a virtual machine
(Fedora 30 with Gnome Boxes). I choose the automatic installation with
full disk encryption in BIOS mode (legacy mode: bootloader in the MBR).
Calamares creates one encrypted LUKS container.
A
Hi,
I was unable to reproduce this bug on an up-to-date Lubuntu 19.04. But
then I tried it also on an up-to-date Lubuntu 18.10 and found out, that
this bug is reproducible under certain circumstances. Additionally I
used also xprop WM_CLASS:
On 18.10:
- install first gnome-terminal and in a sec
** Package changed: leafpad (Ubuntu) => lubuntu-default-settings
** Also affects: leafpad (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775980
Ti
** Tags removed: lubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775980
Title:
Add PolicyKit action to leafpad package
To manage notifications about this bug go to:
https://bugs.launchpad.ne
Public bug reported:
The package gksu has been removed from 18.04 and sudo should not be used
to start a graphical application, because of problems caused by
environment variables (e.g. $HOME, $XAUTHORITY) not set in the right
way.
Please add a PolicyKit action to the package, so that you can edi
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
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
The installation fails because you have booted the installer in UEFI
mode and there is no EFI-System-Partition.
Your workaround describes how to install Grub in the BIOS legacy mode,
which works because Grub can be installed into the MBR.
First of all, the workaround is not really necessary becau
@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
You started the installer in UEFI mode, but your installation is in the BIOS
legacy mode.
Booting the installer in BIOS mode should resolve your installation problem.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
You try to install Ubuntu in EFI mode, but you do not have an EFI System
partition.
But if you have Windows installed on the disk, you should boot the installer in
BIOS legacy mode and you will get a working dualboot (no EFI System partition
needed).
** Changed in: grub-installer (Ubuntu)
You try to install Ubuntu in EFI mode, but you do not have an EFI System
partition.
If you have a Windows installed on the same disk, you should boot the installer
in the BIOS legacy mode to get a working dualboot.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You
You try to install Ubuntu in EFI mode, but you do not have an EFI System
partition.
Either create a EFI System partition and install in UEFI mode, or boot the
installer in the BIOS legacy mode and install Ubuntu (no ESP needed).
** Changed in: grub-installer (Ubuntu)
Status: New => Incomp
You try to install Ubuntu in UEFI mode, but you do not have an EFI System
Partition.
I see some NTFS partitions, so if you have a Windows installed on the disk, you
should boot the installer in the BIOS legacy mode t get a working dualboot.
** Changed in: grub-installer (Ubuntu)
Status: N
You try to install in UEFI mode, but you do not have an EFI System
Partition.
** Changed in: grub-installer (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
The custom mode is for experienced users. And experienced users should
know the basics about booting an OS and partitioning.
** Changed in: grub-installer (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
You try to install Ubuntu in UEFI mode, but you do not have an EFI-
System-Partition.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
You try to install Ubuntu in UEFI mode, but you do not have an EFI-
System-Partition. If you have a Windows installed on the same disk, then
you should install Ubuntu in BIOS mode to get a working dual boot.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received
You try to install Ubuntu in UEFI mode, but you do not have an EFI-
System-Partition. Your Windows seems to be installed in BIOS mode on
your first disk. To get a working dual boot, you have to start the
installer in BIOS mode and create an bios_grub partition on your GPT
disk for Grub or install G
You try to install Ubuntu in UEFI mode, but you do not have an EFI-
System-Partition. If you have a Windows installed on the same disk, then
you should install Ubuntu in BIOS mode to get a working dual boot.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received
This bug report is being closed due to your last comment. For future
reference you can manage the status of your own bugs by clicking on the
current status in the yellow line and then choosing a new status in the
revealed drop down box. You can learn more about bug statuses at
https://wiki.ubuntu.c
You try to install Ubuntu in EFI mode, but you do not have an
EFI-System-Partition.
I recommend you to use GPT as partition table for an EFI installation.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ub
You try to install Ubuntu in EFI mode, but you do not have an
EFI-System-Partition.
I recommend you to use GPT as partition table for an EFI installation.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ub
You try to install Ubuntu in EFI mode, but you do not have an EFI-
System-Partition.
I recommend you to use GPT as partition table for an EFI installation.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of U
You try to install Ubuntu in EFI mode, but you do not have an EFI-
System-Partition.
If you have Windows installed on the same disk, install Ubuntu in BIOS
mode to get a working dual boot.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notifica
You try to install Ubuntu in EFI mode, but you do not have an EFI-
System-Partition.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
You try to install Ubuntu in EFI mode, but you do not have an EFI-
System-Partition.
If you have Windows installed on the same disk, install Ubuntu in BIOS
mode to get a working dual boot.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notifica
*** This bug is a duplicate of bug 1639374 ***
https://bugs.launchpad.net/bugs/1639374
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1639374, so it is being marked as such. Please look
You try to install Ubuntu in EFI mode, but you do not have an EFI-
System-Partition.
If you have Windows installed on the same disk, install Ubuntu in BIOS
mode to get a working dual boot.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notifica
*** This bug is a duplicate of bug 1639374 ***
https://bugs.launchpad.net/bugs/1639374
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1639374, so it is being marked as such. Please look
You try to install Ubuntu in EFI mode, but you do not have an EFI-
System-Partition.
If you have Windows installed on the same disk, install Ubuntu in BIOS
mode to get a working dual boot.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notifica
You try to install Ubuntu in EFI mode, but you don not have an EFI-
System-Partition.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
You try to install Ubuntu in EFI mode, but you don not have an EFI-
System-Partition.
If you wish to have a dualboot with Windows, please check first in which
mode Windows is installed.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
You try to install Ubuntu in EFI mode, but you do not have an EFI-
System-Partition.
If you have Windows installed on the same disk, install Ubuntu in BIOS
mode to get a working dual boot.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notificat
*** This bug is a duplicate of bug 1639374 ***
https://bugs.launchpad.net/bugs/1639374
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1639374, so it is being marked as such. Please look
*** This bug is a duplicate of bug 1639374 ***
https://bugs.launchpad.net/bugs/1639374
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1639374, so it is being marked as such. Please look
You try to install in EFI mode on a disc without an EFI-System-
Partition.
I recommend you to use GPT as partition table instead of MBR/MSDOS
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
*** This bug is a duplicate of bug 1639374 ***
https://bugs.launchpad.net/bugs/1639374
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1639374, so it is being marked as such. Please look
You do not have an EFI-System-Partition, so Grub cannot be installed.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682836
Tit
You do not have an EFI-System-Partition, so Grub could not be installed.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683019
This bug report is being closed due to your last comment regarding this
being fixed with an update. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more a
You try to install Xubuntu in BIOS mode and choose as target for Grub a
disk with GPT as partition table.
You have also an EFI-System-Partition on this disk, so it is probable,
that you have a Windows installed in EFI mode. To get a dualboot you
have to start the installer also in EFI mode.
If yo
*** This bug is a duplicate of bug 1639374 ***
https://bugs.launchpad.net/bugs/1639374
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1639374, so it is being marked as such. Please look
This bug report is being closed due to your last comment regarding this
being fixed with an update. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more a
If you have a Windows installed on the disk, you have to boot the
installer in BIOS mode for a dualboot.
If you do not have Windows, either you start the installer in BIOS mode
or create an EFI-System-Partition.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You rece
Your Windows seems to be installed in efi mode. To get a dualboot, you
have to boot the installer also in efi mode.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
*** This bug is a duplicate of bug 1677358 ***
https://bugs.launchpad.net/bugs/1677358
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1677358, so it is being marked as such. Please look
You do not have an EFI-System-Partition, so it is impossible to install
Grub. Either you create an ESP on your disk or you boot the installer in
BIOS mode.
I recommend to use GPT as partition table.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug
But if you have Windows installed on the disk, you have to start the
installer in efi mode. Otherwise you will not have a dualboot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676270
Title:
Ive s
To install Ubuntu in bios mode on a disk with GPT as partition table,
you have to create a "bios_grub"-partition as first parition on the
disk, size: 1 MiB, without filesystem.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because y
To install Ubuntu in efi mode, you have to create an EFI-System-
Partition. Otherwise Grub cannot be installed.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
If you have a Windows on the disk, you should start the installer in
bios mode to get a dualboot.
If you do not have Windows, then you should create an EFI-System-
Partitition.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because
To install Ubuntu in efi mode, you have to create an EFI-System-
Partition.
And I recommend to use GPT as partition table instead of MBR/MSDOS.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
To install in efi mode, you must have the 64 bit iso.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677233
Title:
failed ins
If you have Windows installed, then you should start the installer in
bios mode to get a dualboot.
If you do not have Windows, you should create an EFI-System-Partition
to install Ubuntu in efi mode.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this b
Your Windows is installed in bios mode, but your installer booted in EFI
mode. To get a dualboot, you have to start the installer in bios
(legacy, CSM) mode.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1639374 ***
https://bugs.launchpad.net/bugs/1639374
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1639374, so it is being marked as such. Please look
You try to install Ubuntu in UEFI mode, but you do not have an
EFI-System-Partition.
But if you have Windows installed on disk, you will not get a working dualboot.
For a working dualboot, you have to install Ubuntu in BIOS mode.
If you like to install Ubuntu in UEFI mode, add an EFI-System-Part
You do not have an EFI-System-Partition, so Grub cannot be installed.
As partition table I recommend you to use GPT instead of MBR/MSDOS
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
You had problems with downloading the packages.
Please retry to install with a working internet connection (better use a
wired connection instead of wireless).
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member
You do not have an EFI-System-Partition, so Grub cannot be installed in
UEFI mode.
Try the installation again with an EFI-System-Partition or install in
the old BIOS mode.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you a
You try to install Ubuntu in UEFI mode without an EFI-System-Partition.
If you have a Windows installed, you should install Ubuntu in BIOS mode
to get a dualboot.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a memb
*** This bug is a duplicate of bug 1639374 ***
https://bugs.launchpad.net/bugs/1639374
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1639374, so it is being marked as such. Please look
You do not have an EFI-System-Partition, so Grub cannot be installed.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1663940
Tit
1 - 100 of 171 matches
Mail list logo
