from:"Jeremie Tamburini"

Just to confirm everything I've written in message #25.
I've repeated the same tests with the deily iso 20/4.

The workaround at message #13 is no more needed for Ubuntu 21.04, but it
can still be useful for Ubutnu 20.10

The step:
sudo apt install --reinstall grub-pc

can be more easily replaced by:
sudo update-grub

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924823

Title:
  ESP on install medium automatically configured as ESP for install,
  failing install

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1924823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1924856] Re: Ubiquity creates useless ESR (EFI) partition on Bios system

> juliank
> This is a feature, not a bug.

It's what I thought once I was aware of all these troubles:
https://discourse.ubuntu.com/t/groovy-to-use-grub2-for-booting-installer-media-in-any-modes-on-all-architectures/16871/34

But it looks like nobody knew about EFI partition with BIOS and I've
been asked to file a bug report about it.

Fortunately year after year we are going to have less old computers based on 
old BIOS and also Ubuntu 20.10 and 21.04 are not LTS version and therefore not 
so popular.
But a feature like this should have been "loudly" communicated to all users 
before landing into the installer, after decades with no need of EFI partition 
with BIOS. And should have been also bullet proof tested before landing to 
users.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924856

Title:
  Ubiquity creates useless ESR (EFI) partition on Bios system

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1924856/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1924823] Re: ESP on install medium automatically configured as ESP for install, failing install

Hi everybody,
As guiverc I have updated Ubiquity on a older Ubuntu iso image to get version  
21.04.19

In good part I can confirm good news!
...but there are still bizarre things

I've performed 2 test installation:

1- MANUALLY CHOSING A PARTITION
Same result reported by guiverc at comment #24
The bad thing is the message 'No EFI Partition found. This system will likely 
not be able to boot... please go back and add an EFI...'
This can be tricky!

2- INSTALL ALONGSIDE... (in remaining disk space - 3 partition already taken on 
MBR)
That's a typical situation seen many times on old computers with Windows7 that 
already takes 3 partitions.
It finally works! But it's quite weird.
During the installation the well known grub error message "Executing 
'grub-install /dev/sda' failed This is a fatal error" appears.
But rebooting the system everything is fine. I'm actually writhing from the 
installed system.
I'm afraid that the error message can be even trickier than the message in the 
previous case.

I've filed bug #1925187 before rebooting the system not knowing if the
system could boot. Then I've changed title and description... anyway,
log files are there for further information.


I presume there is no much time before the release dayleft for a 'cleaner' 
solution. It's a pity that only now someone is doing something against these 
issues.
Anyway... juliank and also jibel, thank you very much for all the efforts.


P.S. I'll probably repeat the tests when the new daily-build is out.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924823

Title:
  ESP on install medium automatically configured as ESP for install,
  failing install

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1924823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1925187] Re: Ubiquity 21.04.19 ends in 'error install grub' but Ubuntu get installed

** Description changed:

  Ubiquity 21.04.19 installed via apt on a previous iso daily-build as an
  iso with 21.04.19 at the moment is not available.
  
  DESCRIPTION:
  
  - Partition table: msdos (MBR)
  - /dev/sda1 with Ubuntu already installed
  - /dev/sda2 and /dev/sda3 both Ext4
  
  Installation modality: Install Ubuntu 21.04 alongside...
  
  As 3 primary partition are already used, the installer is forced to use
  the remaining space creating an extended partition with logical
  partition inside:
  
  - /dev/sda5 ESP (EFI)
  - /dev/sda6 Ext4 for Ubuntu
  
- But EFI partition should be primary, not logical.
+ EFI partition should be primary, not logical and as expected a popup:
+   Executing 'grub-install /dev/sda' failed 
+   This is a fatal error
  
- Then grub-install fails.
+ Despite this the system get installed and it is bootable.
+ Probably because of the recent changes on Ubiquity package.
+ 
+ Anyway, the 'grub error' message can be tricky!
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.19
  ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
  Uname: Linux 5.11.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  Date: Tue Apr 20 06:42:08 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210416)
  RebootRequiredPkgs:
-  linux-image-5.11.0-16-generic
-  linux-base
-  linux-image-5.11.0-14-generic
-  linux-base
+  linux-image-5.11.0-16-generic
+  linux-base
+  linux-image-5.11.0-14-generic
+  linux-base
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925187

Title:
  Ubiquity 21.04.19 ends in 'error install grub' but Ubuntu get
  installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1925187/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1925187] Re: Ubiquity 21.04.19 ends in 'error install grub' but Ubuntu get installed

** Summary changed:

- Ubiquity 21.04.19 fails in 'install alongside' in extended partition
+ Ubiquity 21.04.19 ends in 'error install grub' but Ubuntu get installed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925187

Title:
  Ubiquity 21.04.19 ends in 'error install grub' but Ubuntu get
  installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1925187/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1925187] [NEW] Ubiquity 21.04.19 fails in 'install alongside' in extended partition

Public bug reported:

Ubiquity 21.04.19 installed via apt on a previous iso daily-build as an
iso with 21.04.19 at the moment is not available.

DESCRIPTION:

- Partition table: msdos (MBR)
- /dev/sda1 with Ubuntu already installed
- /dev/sda2 and /dev/sda3 both Ext4

Installation modality: Install Ubuntu 21.04 alongside...

As 3 primary partition are already used, the installer is forced to use
the remaining space creating an extended partition with logical
partition inside:

- /dev/sda5 ESP (EFI)
- /dev/sda6 Ext4 for Ubuntu

But EFI partition should be primary, not logical.

Then grub-install fails.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubiquity 21.04.19
ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
Uname: Linux 5.11.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.461
Date: Tue Apr 20 06:42:08 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210416)
RebootRequiredPkgs:
 linux-image-5.11.0-16-generic
 linux-base
 linux-image-5.11.0-14-generic
 linux-base
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute ubiquity-21.04.15 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925187

Title:
  Ubiquity 21.04.19 fails in 'install alongside' in extended partition

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1925187/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1924823] Re: ESP on install medium automatically configured as ESP for install, failing install

> juliank
> Jeremie, the correct workaround is to deselect the EFI system partition when
> you configure partitions in the installer, as I explained in comment #5.

Let's say that the EFI partition is not selected, it only shows the type (EFI) 
but it's not selected a mount point.
As reported in comment #10 I have also tried the installation explicitly 
selecting "don't use this partition" for the EFI on the USB stick. But it 
didn't work, same problems of the other attempts.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924823

Title:
  ESP on install medium automatically configured as ESP for install,
  failing install

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1924823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1893964] Re: Installation of Ubuntu Groovy with manual partitioning without an EFI System Partition fails on 'grub-install /dev/sda' even on non-UEFI systems

> juliank:
> Jeremie, you reported a separate bug for the issue of the installer 
> automatically picking
> up the USB stick's USB, please comment there if you have to.

I know and I apologize, but here is where many other users experienced
problems related to EFI/BIOS and I thought it could be a good thing to
let them know of this alternative workaround, surely less intimidating
than chroot.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893964

Title:
  Installation of Ubuntu Groovy with manual partitioning without an EFI
  System Partition fails on 'grub-install /dev/sda' even on non-UEFI
  systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1893964] Re: Installation of Ubuntu Groovy with manual partitioning without an EFI System Partition fails on 'grub-install /dev/sda' even on non-UEFI systems

@lproven
Good observation.

The EFI boot partition is created inside USB device at least with the latest 
versions of major gui utilities available in Ubuntu: gnome-disk-utility and 
usb-creator-gtk.
balenaEtcher also does it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893964

Title:
  Installation of Ubuntu Groovy with manual partitioning without an EFI
  System Partition fails on 'grub-install /dev/sda' even on non-UEFI
  systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1893964] Re: Installation of Ubuntu Groovy with manual partitioning without an EFI System Partition fails on 'grub-install /dev/sda' even on non-UEFI systems

There's an easier WORKAROUND in case you have no space for an extra EFI
partition.

First of all a resume of the issues related to 'EFI on BIOS'.
The system itself get installed. Problem is that Ubiquity thinks that an ESR 
(EFI) partition is needed even on computers with BIOS. And it does installs 
grub, but on the USB install device. This because it finds an EFI partition in 
the USB device and automatically selects it bug #1924823

It's still possible to boot the installed system just keeping the USB device 
connected to computer.
The WORKAROUND works like this: boot the system, modified /etc/fstab, remove 
grub-efi* package and re-installed grub-pc.

HERE ALL THE STEPS:

1. Make sure 'first boot from hard disk' is set in the BIOS settings.
2. Connect the USB installer device and start the computer.

3. Open /etc/fstab and comment the line related to /boot/efi:
sudo -H gedit /etc/fstab

4. find a line like this:
UUID=BF7E1-08E7  /boot/efi  vfat  umask=0077  0  1

5. put the character # at the beginning of the line:
#UUID=BF7E1-08E7  /boot/efi  vfat  umask=0077  0  1

6. Save the file and exit from gedit.

7. Un-mount e mount the partitions:
sudo umount -a && sudo mount -a

8. Uninstall all grub-efi related packages:
sudo apt purge grub-efi*

9. Reinstall grub-pc:
sudo apt install --reinstall grub-pc

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893964

Title:
  Installation of Ubuntu Groovy with manual partitioning without an EFI
  System Partition fails on 'grub-install /dev/sda' even on non-UEFI
  systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1924823] Re: ESP on install medium automatically configured as ESP for install, failing install

Got the WORKAROUND and it's quite easy :D
(Thanks guiverc, you gave the idea!)

As you have done I tried to boot the system keeping the USB installer device 
connected to the computer. I've just set 'first boot from hard disk' inside 
bios settings... and the system boots.
Then I've uninstalled grub-efi* package, modified /etc/fstab and re-installed 
grub-pc. It worked!

HERE ALL THE STEPS:

1. Make sure 'first boot from hard disk' is set in the BIOS settings.
2. Connect the USB installer device and start the computer.

3. Open /etc/fstab and comment the line related to /boot/efi:
sudo -H gedit /etc/fstab

4. find a line like this:
UUID=BF7E1-08E7  /boot/efi  vfat  umask=0077  0  1

5. put the character # at the beginning of the line:
#UUID=BF7E1-08E7  /boot/efi  vfat  umask=0077  0  1

6. Save the file and exit from gedit.

7. Un-mount e mount the partitions:
sudo umount -a && sudo mount -a

8. Uninstall all grub-efi related packages:
sudo apt purge grub-efi*

9. Reinstall grub-pc:
sudo apt install --reinstall grub-pc

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924823

Title:
  ESP on install medium automatically configured as ESP for install,
  failing install

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1924823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1924856] Re: Ubiquity creates useless ESR (EFI) partition on Bios system

** Description changed:

  Ubuntu 21.04 - 16/4 daily build - Ubiquity 21.04.15
  
  Even on computers with old BIOS an ESR (EFI) partition will be
  automatically created when installing Ubuntu using one of the automatic
  options like "Erase disk and install Ubuntu", "Install Ubuntu alongside
  other system", etc..
  
  This should not happens. No ESR partition should be created on systems
  with old BIOS.
  
  In this case:
  - 2 partition where already existing:
    - /dev/sda1 Ext4 with Ubuntu 21.04 already installed
    - /dev/sda2 Ext4 empty
  - Performed the "Install Ubuntu alongside other system" install option".
  - After install:
-   - /dev/sda3 Fat32 ESP 
-   - /dev/sd4  extended
-   - /dev/sda5 Ext4 with new Ubuntu 21.04
+   - /dev/sda3 Fat32 ESP
+   - /dev/sd4  extended
+   - /dev/sda5 Ext4 with new Ubuntu 21.04
  
  I've set just 2 existing primary partition because if the installer
  doesn't find a primary partition for ESR, installation will fail and
  that's another bug, see bug #1924823
  
  In this case installation will succeed, but just think about all the
- system on old BIOS that are already using 3 primary partitions and
+ systems with old BIOS that are already using 3 primary partitions and
  there's no extra primary partition for ESR.. in that case installation
  fails.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.15
  ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
  Uname: Linux 5.11.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 17 16:04:41 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs:
   linux-image-5.11.0-14-generic
   linux-base
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924856

Title:
  Ubiquity creates useless ESR (EFI) partition on Bios system

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1924856/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1924856] Re: Ubiquity creates useless ESR (EFI) partition on Bios system

** Description changed:

  Ubuntu 21.04 - 16/4 daily build - Ubiquity 21.04.15
  
  Even on computers with old BIOS an ESR (EFI) partition will be
  automatically created when installing Ubuntu using one of the automatic
  options like "Erase disk and install Ubuntu", "Install Ubuntu alongside
  other system", etc..
  
- This should not happens. No ESR partition should be created.
+ This should not happens. No ESR partition should be created on systems
+ with old BIOS.
  
  In this case:
  - 2 partition where already existing:
    - /dev/sda1 Ext4 with Ubuntu 21.04 already installed
    - /dev/sda2 Ext4 empty
- - Performed the "Install Ubuntu alongside other system" install option.
+ - Performed the "Install Ubuntu alongside other system" install option".
+ - After install:
+   - /dev/sda3 Fat32 ESP 
+   - /dev/sd4  extended
+   - /dev/sda5 Ext4 with new Ubuntu 21.04
  
  I've set just 2 existing primary partition because if the installer
  doesn't find a primary partition for ESR, installation will fail and
  that's another bug, see bug #1924823
  
  In this case installation will succeed, but just think about all the
  system on old BIOS that are already using 3 primary partitions and
  there's no extra primary partition for ESR.. in that case installation
  fails.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.15
  ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
  Uname: Linux 5.11.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 17 16:04:41 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs:
   linux-image-5.11.0-14-generic
   linux-base
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924856

Title:
  Ubiquity creates useless ESR (EFI) partition on Bios system

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1924856/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1924823] Re: ESP on install medium automatically configured as ESP for install, failing install

Some more info:

- I repeated the installation selecting the "don't use this partition" option 
for the EFI partition of the USB device.
The result is still the same like in the example of guiverc:
/dev/sda1 on /target type ext4
/dev/sdb2 on /target/boot/efi

- I filed a new bug report: bug #1924856
I thought it might be useful to have some data when installation succeed using 
one of the automatic option. In this case I've selected "Install Ubuntu 
alongside other system".
An ESR partition is automatically created on /dev/sda3.

Till Ubuntu 20.04 everything was fine. There still were two different modality 
to boot the USB/dvd device: "uefi modality" and "old bios modality".
All these issues started with Ubuntu 20.10 where the way to boot the USB/dvd 
device is now unified.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924823

Title:
  ESP on install medium automatically configured as ESP for install,
  failing install

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1924823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1924856] Re: Ubiquity creates useless ESR (EFI) partition on Bios system

** Description changed:

  Ubuntu 21.04 - 16/4 daily build - Ubiquity 21.04.15
  
  Even on computers with old BIOS an ESR (EFI) partition will be
  automatically created when installing Ubuntu using one of the automatic
  options like "Erase disk and install Ubuntu", "Install Ubuntu alongside
  other system", etc..
  
  This should not happens. No ESR partition should be created.
  
  In this case:
  - 2 partition where already existing:
-   - /dev/sda1 Ext4 with Ubuntu 21.04 already installed
-   - /dev/sda2 Ext4 empty
+   - /dev/sda1 Ext4 with Ubuntu 21.04 already installed
+   - /dev/sda2 Ext4 empty
+ - Performed the "Install Ubuntu alongside other system" install option.
  
  I've set just 2 existing primary partition because if the installer
  doesn't find a primary partition for ESR, installation will fail and
  that's another bug, see bug #1924823
  
  In this case installation will succeed, but just think about all the
  system on old BIOS that are already using 3 primary partitions and
  there's no extra primary partition for ESR.. in that case installation
  fails.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.15
  ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
  Uname: Linux 5.11.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 17 16:04:41 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210416)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=it_IT.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=it_IT.UTF-8
+  SHELL=/bin/bash
  RebootRequiredPkgs:
-  linux-image-5.11.0-14-generic
-  linux-base
+  linux-image-5.11.0-14-generic
+  linux-base
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924856

Title:
  Ubiquity creates useless ESR (EFI) partition on Bios system

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1924856/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1924856] [NEW] Ubiquity creates useless ESR (EFI) partition on Bios system

Public bug reported:

Ubuntu 21.04 - 16/4 daily build - Ubiquity 21.04.15

Even on computers with old BIOS an ESR (EFI) partition will be
automatically created when installing Ubuntu using one of the automatic
options like "Erase disk and install Ubuntu", "Install Ubuntu alongside
other system", etc..

This should not happens. No ESR partition should be created.

In this case:
- 2 partition where already existing:
  - /dev/sda1 Ext4 with Ubuntu 21.04 already installed
  - /dev/sda2 Ext4 empty

I've set just 2 existing primary partition because if the installer
doesn't find a primary partition for ESR, installation will fail and
that's another bug, see bug #1924823

In this case installation will succeed, but just think about all the
system on old BIOS that are already using 3 primary partitions and
there's no extra primary partition for ESR.. in that case installation
fails.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubiquity 21.04.15
ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
Uname: Linux 5.11.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.461
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 17 16:04:41 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210416)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
RebootRequiredPkgs:
 linux-image-5.11.0-14-generic
 linux-base
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute ubiquity-21.04.15 ubuntu

** Summary changed:

- Ubiquity create useless ESR (EFI) partition on Bios system
+ Ubiquity creates useless ESR (EFI) partition on Bios system

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924856

Title:
  Ubiquity creates useless ESR (EFI) partition on Bios system

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1924856/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1924823] Re: ESP on install medium automatically configured as ESP for install, failing install

Hi and thanks for your reply.
I'm going to do some more tests.

Anyway, if you select "Erase the disk and install Ubuntu" the installer
is going to create an ESP on /dev/sda (see the attached picture). I
didn't perform this type of installation (I did it few months ago and it
actually create the ESP partition) I just wanted to see if the installer
was still doing this.

It looks like it doesn't matter what your are doing, the installer is
"acting" like the only existing system is UEFI.

** Attachment added: "Picture of ESP + / before installling Ubuntu"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1924823/+attachment/5489212/+files/automatic_esp.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924823

Title:
  ESP on install medium automatically configured as ESP for install,
  failing install

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1924823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1893964] Re: Installation of Ubuntu Groovy with manual partitioning without an EFI System Partition fails on 'grub-install /dev/sda' even on non-UEFI systems

2021-04-16 Thread Jeremie Tamburini

Hi,
I've tried to install the 16/4 daily build with Ubiquity 21.04.15, but I'm 
still experiencing the same problems.

I've just in case filed this bug report: bug #1924823

I've tried to manually install Ubuntu on one of the Ext4 primary partition.
Didn't try any other modality, just seen that selecting the "install on the 
entire disk" option a popup window tells that an ESR partition will be created.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893964

Title:
  Installation of Ubuntu Groovy with manual partitioning without an EFI
  System Partition fails on 'grub-install /dev/sda' even on non-UEFI
  systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1924823] [NEW] Ubiquity Ubuntu 21.04 install fail on legacy bios

2021-04-16 Thread Jeremie Tamburini

Public bug reported:

This bug report is a duplicated of bug #1902269 performed with Ubuntu 21.10.
Basically installation fail when the installer doesn't find an EFI (ESR) 
partition on computers with legacy BIOS.

This time I have used Ubuntu 21.04 also to test the new version of
Ubiquity package (21.04.15) which, as reported here:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964/comments/22
should have fixed the issue.

Unfortunately I'm still experiencing the same problem.


 Partition details:
- msdos partition table
- 4 primary partitions, all ext4

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubiquity 21.04.15
ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
Uname: Linux 5.11.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.461
Date: Sat Apr 17 02:20:20 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210416)
RebootRequiredPkgs:
 linux-image-5.11.0-14-generic
 linux-base
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute ubiquity-21.04.15 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924823

Title:
  Ubiquity Ubuntu 21.04 install fail on legacy bios

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1924823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1893964] Re: Installation of Ubuntu Groovy with manual partitioning without an EFI System Partition fails on 'grub-install /dev/sda' even on non-UEFI systems

2021-02-11 Thread Jeremie Tamburini

Same problem on 21.04, Ubuntu installer thinks that BIOS is UEFI.

Just 2 months left before the the final release. Any chance for a fix?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893964

Title:
  Installation of Ubuntu Groovy with manual partitioning without an EFI
  System Partition fails on 'grub-install /dev/sda' even on non-UEFI
  systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1864871] Re: Failed to init Intel sound card in 20.04

2021-02-07 Thread Jeremie Tamburini

After many months, I had the opportunity to put my hands on the computer that 
had these audio problems:
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864871/comments/31)

...and now the audio works without any workaround.

Current Ubuntu version: 20.04.2
Kernel: 5.8.0-41

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864871

Title:
  Failed to init Intel sound card in 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864871/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1898462] Re: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-shell

2020-12-22 Thread Jeremie Tamburini

@Timo Aaltonen
The new package fix the problem. Good job!

Here what I've done:
1. enabled the proposed repository
2. updated gnome-shell-extension-desktop-icons to version 
20.04.0+git20200908-5~ubuntu20.10.0
3. Test case: created a file in the desktop and tried drag & drop inside an 
open folder. As expected drag & drop doesn't work, but now the shell doesn't 
freeze.

** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898462

Title:
  [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-
  shell

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1898462/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1901137] Re: UEFI on Legacy - grub-install fails due to no space left on ESP

2020-11-13 Thread Jeremie Tamburini

My bug report #1902269 has been marked as duplicated of this one even if
the description it's not exactly the same.

In any case it looks the problem is related to the EFI (ESP) partition,
that should never be used on old BIOS or UEFI in Legacy Mode, but for
some reasons the installer want it... even if we are NOT in "UEFI mode".

This might be related to recent changes of the installer
https://discourse.ubuntu.com/t/groovy-to-use-grub2-for-booting-installer-media-in-any-modes-on-all-architectures/16871
You have probably noticed that now there's no difference between uefi or bios
mode. When you boot the live USB, you see the same grub menu.

After many tests, these are the case where the installation has been
successful:

- updating the system directly from Focal (from 20.04 to 20.10)

- creating an EFI partition during manual partitioning.
In this case the partition must be a primary partition.
(One user was able to set the EFI partition on a USB drive... it was not my
case).

- Installing Ubuntu using the "Erase the disk and install Ubuntu.." will also
succeed. EFI partition will be automatically created.
(Also the option "Install Ubuntu next Windows" should work, but there must be
enough space for a primary partition for the EFI).

As reported on bug #1893964 (comment #8), the user was able to install the
system skipping the "grub-install" launching Ubiquity with the command:
ubiquity -b
Then he manually recovered GRUB. I've tried the same, but with no success...
still had problems with efi. The log reported several errors and one of them
was:
## pc systemd[1]: Dependency failed for /boot/efi.
## Subject: L'unità boot-efi.mount è fallita
## Defined-By: systemd
## Support: http://www.ubuntu.com/support

I hope there will be a solution as soon as possible, this is one of the worst
bug ever :(
The only lucky thing is that Ubuntu 20.10 is NOT a LTS... other wise many more
users could have been in trouble.

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901137

Title:
UEFI on Legacy - grub-install fails due to no space left on ESP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1901137/+subscriptions

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1902269] Re: Ubuntu 20.10 on BIOS hardware - Installation with manual partitioning fails while executing "grub-install /dev/sda"

2020-10-30 Thread Jeremie Tamburini

** Description changed:

  (I'm duplicating this bug
  https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964 in order
  to provide more data to developers).
  
  Installation with manual partitioning of Ubuntu 20.10 on BIOS hardware
  fails while executing "grub-install /dev/sda".
  
  We already know as reported in bug #1893964 that this happens because for 
some reasons the installation system expect an existing EFI boot partition.
  On the same machine I have also tried to install Ubuntu 20.10 using the 
automatic option "Erase the disk and install Ubuntu..". In that case the 
installation succeeds, with the automatic creation of the EFI partition.
  
  Of course being an old computer with old BIOS, there should not be any
  need of an EFI partition on a msdos(mbr) partition table.
- 
  
  Here what I've done:
  
  ::: BEFORE INSTALLATION
  
  With Gparted I have:
  1- erased the hard disk
  2- created an msdos partion table
  3- created a 50GiB Ext4 partition
  
  ::: INSTALLATION
  
  I've run a standard installation:
  - enabled 3rd party software
  - chosen the manual partitioning
  - selected the only partition available, formatted as Ext4 and set "/" as 
mount point
  
  ::: CRASH
  
  At one point installation stops with popup window showing: "Executing
  'grub-install /dev/sda' failed. This is a fatal error."
  
+ ::: WORKAROUND
+ 
+ Just create an EFI partition before installing the system.
+ 
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubiquity 20.10.13
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 30 16:33:29 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=C.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=C.UTF-8
+  SHELL=/bin/bash
  RebootRequiredPkgs:
-  linux-image-5.8.0-25-generic
-  linux-base
+  linux-image-5.8.0-25-generic
+  linux-base
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902269

Title:
  Ubuntu 20.10 on BIOS hardware - Installation with manual partitioning
  fails while executing "grub-install /dev/sda"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1902269/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1902269] [NEW] Ubuntu 20.10 on BIOS hardware - Installation with manual partitioning fails while executing "grub-install /dev/sda"

2020-10-30 Thread Jeremie Tamburini

Public bug reported:

(I'm duplicating this bug
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964 in order
to provide more data to developers).

Installation with manual partitioning of Ubuntu 20.10 on BIOS hardware
fails while executing "grub-install /dev/sda".

We already know as reported in bug #1893964 that this happens because for some 
reasons the installation system expect an existing EFI boot partition.
On the same machine I have also tried to install Ubuntu 20.10 using the 
automatic option "Erase the disk and install Ubuntu..". In that case the 
installation succeeds, with the automatic creation of the EFI partition.

Of course being an old computer with old BIOS, there should not be any
need of an EFI partition on a msdos(mbr) partition table.


Here what I've done:

::: BEFORE INSTALLATION

With Gparted I have:
1- erased the hard disk
2- created an msdos partion table
3- created a 50GiB Ext4 partition

::: INSTALLATION

I've run a standard installation:
- enabled 3rd party software
- chosen the manual partitioning
- selected the only partition available, formatted as Ext4 and set "/" as mount 
point

::: CRASH

At one point installation stops with popup window showing: "Executing
'grub-install /dev/sda' failed. This is a fatal error."

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubiquity 20.10.13
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.455
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 30 16:33:29 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
RebootRequiredPkgs:
 linux-image-5.8.0-25-generic
 linux-base
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy ubiquity-20.10.13 ubuntu

** Attachment added: "syslog"
   https://bugs.launchpad.net/bugs/1902269/+attachment/5429521/+files/syslog

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902269

Title:
  Ubuntu 20.10 on BIOS hardware - Installation with manual partitioning
  fails while executing "grub-install /dev/sda"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1902269/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1864871] Re: Failed to init Intel sound card in 20.04

2020-06-01 Thread Jeremie Tamburini

Similar problem with:
- Ubuntu 20.04 LTS
- Fujitsu LifeBook A530
- $ lspci | grep Audio
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High 
Definition Audio (rev 05)

THE PROBLEM:
No sound. Gnome audio system settings shows "Dummy Audio" as output device.

Trying with Lubuntu 20.04 on a different partition there's the same problem but 
running PulseAudio Volume Control it's possible to select: "analog stereo 
duplex" or "analog stereo output".
Unfortunately there is no setting like this for Gnome.


WORKAROUND:
As reported here https://forum.ubuntu-it.org/viewtopic.php?t=413914 it seems to 
be a problem related to udev which doesn't find the audio card.

1. Inside /etc/pulse/default.pa find the following code:

.ifexists module-udev-detect.so
load-module module-udev-detect
.else
### Alternatively use the static hardware detection module (for systems that
### lack udev support)
load-module module-detect
.endif

2. Comment the if/else statement:

### Automatically load driver modules depending on the hardware available
#.ifexists module-udev-detect.so
#load-module module-udev-detect
#.else
### Alternatively use the static hardware detection module (for systems that
### lack udev support)
load-module module-detect
#.endif

3. Save the file and restart.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864871

Title:
  Failed to init Intel sound card in 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864871/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1865169] Re: volume and light not working in Gnome Shell 3.35

2020-03-23 Thread Jeremie Tamburini

Just to confirm gjs version 1.63.92-1 fixes the problem.

(P.S. focal-proposed activated)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865169

Title:
  volume and light not working in Gnome Shell 3.35

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1865169/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1056101] Re: grub-efi overwrites an existing grub*.efi file

2020-03-05 Thread Jeremie Tamburini

Bug is still there.

Quick example when my computer starts:
if I don't do anything, Ubuntu 19.10 will be booted.
If I press [F12] I get the Boot Menu list, which shows:
1. ubuntu
2. deepin
3. CD/DVD Drive ...
4. Drive0 HDD ...

There is only 1 entry for Ubuntu (which is the one for 19.10) but on my 
computer there are totally 4 different Ubuntu releases:
- Ubuntu 14.04
- Ubuntu 19.04
- Ubuntu 19.10
- Ubuntu 20.04

They should be all mentioned in the Boot Menu, but there is just one
entry.


If you install one of the Ubuntu versions, it will be automatically set as the 
only "ubuntu" Boot Menu entry. It will also be set as the default system on 
boot.
To change it you have to boot the Ubuntu version you want as the default one at 
boot, and run the command "sudo grub-install".


P.S.
I apologize for my old messages (#2 and #3) as they were not strictly connected 
to this bug, sorry!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1056101

Title:
  grub-efi overwrites an existing grub*.efi file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1056101/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1820432] [NEW] Top bar Application Menu cannot be hidden

2019-03-16 Thread Jeremie Tamburini

Public bug reported:

Gnome Tweaks in Ubuntu 19.04

Selecting "Top Bar -> Application Menu", there is no way to hide the app
menu.

I suppose this happens because the app menu has been changed in the
latest Gnome Shell version and that's why the switch has no effect.

** Affects: gnome-tweaks (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/1820432

Title:
  Top bar Application Menu cannot be hidden

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1820432/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1733394] Re: Mines does not recognize a new high score has happened

2018-02-09 Thread Jeremie Tamburini

Mines 3.26.0 - Ubuntu 17.10

I found a related upstream bug report:
https://bugzilla.gnome.org/show_bug.cgi?id=789399

** Bug watch added: GNOME Bug Tracker #789399
   https://bugzilla.gnome.org/show_bug.cgi?id=789399

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733394

Title:
  Mines does not recognize a new high score has happened

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-mines/+bug/1733394/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-28 Thread Jeremie Tamburini

Hi,
Another main problem is that the *buntu 17.10 ISO images are still 
down-loadable. Not all the users read linux news and are aware of this bad bug.
Unfortunately a warning on the ubuntu.com download page is not enough. There 
are infinite ways to reach the download links of the 17.10. 

Also, does anyone know if the ISO images are going to be updated with an
updated kernel?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1631750] Re: Language installation doesn't work in Ubuntu GNOME 16.10 Settings app

I found the same problem with the language setup on Ubuntu 17.10.
This could be related to the new Gnome Settings (just let me know if you think 
I should open a new bug report).

I was running Ubuntu 17.10 in Italian language, previously installed
with the old Gnome Settings. I wanted to switch to English language but
I couldn't because of this bug.

Following the steps of the bug description, the only difference was the 
terminal warning: "Language it_IT not installed, trying to install it"
..which is a bit strange because the system was already set to Italian, I 
wanted to set the en_US.UTF-8.

I've noticed that while trying to change the language settings, the
strings in /etc/default/locale don't change at all.


:: WORKAROUND

1- sudo nano /etc/default/locale
2- Comment or delete the existing strings end write the following:

LANG="en_US.UTF-8"
LANGUAGE="en"

If I want to go back to the Italian setup I just need to write the
following:

LANG="it_IT.UTF-8"
LANGUAGE="it:en"

3- Press [Ctrl]+O and [Enter] to save the file. Press then [Ctrl]+X to exit 
from Nano editor.
4- Log-out and log-in again or restart the system. After the log-in the system 
is asking if you would like to update the names of the folders into $HOME 
(Desktop, Music, Video, etc..).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631750

Title:
  Language installation doesn't work in Ubuntu GNOME 16.10 Settings app

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1631750/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1716341] Re: Settings for external monitor are deleted after reboot, suspension, log out

** Summary changed:

- Settings for external monitor are delete after reboot, suspension, log out
+ Settings for external monitor are deleted after reboot, suspension, log out

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1716341

Title:
  Settings for external monitor are deleted after reboot, suspension,
  log out

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1716341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1714410] Re: Can't change display configuration, Method ApplyConfiguration is not implemented on interface org.gnome.Mutter.DisplayConfig

I have open a new bug related to the fact that gnome settings doesn't
"remember" the setup for external monitors after log out, restart..

Please add comment here: https://bugs.launchpad.net/ubuntu/+source
/gnome-control-center/+bug/1716341

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714410

Title:
  Can't change display configuration, Method ApplyConfiguration is not
  implemented on interface org.gnome.Mutter.DisplayConfig

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1714410/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1716341] [NEW] Settings for external monitor are delete after reboot, suspension, log out