Verification-done on bionic with shim-signed/1.34.9.1:
I checked that you can no longer backtrack in the GNOME debconf frontend
from the "enable secure boot" question to cause the dialog to fail.
Backtracking is no longer accepted, only allowed as part of the password
handling steps.
** Tags remo
Verification-done on bionic with shim-signed/1.34.9.1:
update-secureboot-policy now properly accepts passwords with spaces, and
passes them cleanly to mokutil.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notifi
** Also affects: nplan (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nplan (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770082
Titl
** Changed in: installation-guide (Ubuntu)
Assignee: Dimitri John Ledkov 🌈 (xnox) => (unassigned)
** Summary changed:
- adjust the s390x parts of the 16.04 install guide
+ adjust the s390x parts of the install guide
--
You received this bug notification because you are a member of Ubuntu
B
MIR approved.
Please make sure to move the packaging source to someplace other than
~rbalint's own tree; it probably should be modifiable by others.
** Changed in: gce-compute-image-packages (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a mem
** Description changed:
+ [Impact]
+ Usage of juju to deploy systems with bridge configurations is severely broken
if using layer3+4 bonding, as renaming might be attempted and break the
application of config.
+
+ [Test case]
+ 1) Deploy a system using MaaS and Juju, with a network configuratio
** Changed in: nplan (Ubuntu)
Status: In Progress => Triaged
** Summary changed:
- No virtual interfaces
+ No support for interface labels
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743200
If you are seeing this issue, what image are you using? Have you tried
booting to Ubuntu without the ISO connected?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798171
Title:
System fails to boot
Resetting the tags to verification-done as per the discussion above.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
--
You received this bug notification because you are a member of Ubun
This was already landed in a prior SRU. Closing as Fix Released.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done-xenial
** Changed in: grub2-signed (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806379
Title:
[
Verification-done on bionic: netplan.io 0.40.1~18.04.3
Verification-done on cosmic: netplan.io 0.40.2.2
I have checked that the new package in proposed now skips devices that
can't be identified as physical interfaces or that are known to be
members of bonds/bridges, etc. so as not to attempt to r
Resetting the tags to verification-done as per the discussion in
https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
The SRU had been rolled back due to a regression that needed to be
fixed, but we still consider the previous verification to be valid.
** Tags removed: verification-needed
*** This bug is a duplicate of bug 1736965 ***
https://bugs.launchpad.net/bugs/1736965
Resetting the tags to verification-done as per the discussion in
https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
The SRU had been rolled back due to a regression that needed to be
fixed, but we
Resetting the tags to verification-done as per the discussion in
https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
The SRU had been rolled back due to a regression that needed to be
fixed, but we still consider the previous verification to be valid.
** Tags removed: verification-needed
Resetting the tags to verification-done as per the discussion in
https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
The SRU had been rolled back due to a regression that needed to be
fixed, but we still consider the previous verification to be valid.
** Tags removed: verification-needed
Resetting the tags to verification-done as per the discussion in
https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
The SRU had been rolled back due to a regression that needed to be
fixed, but we still consider the previous verification to be valid.
** Tags removed: verification-needed
Resetting the tags to verification-done as per the discussion in
https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
The SRU had been rolled back due to a regression that needed to be
fixed, but we still consider the previous verification to be valid.
** Tags removed: verification-needed
Resetting the tags to verification-done as per the discussion in
https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
The SRU had been rolled back due to a regression that needed to be
fixed, but we still consider the previous verification to be valid.
** Tags removed: verification-needed
Resetting the tags to verification-done as per the discussion in
https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
The SRU had been rolled back due to a regression that needed to be
fixed, but we still consider the previous verification to be valid.
** Tags removed: verification-needed
Resetting the tags to verification-done as per the discussion in
https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
The SRU had been rolled back due to a regression that needed to be
fixed, but we still consider the previous verification to be valid.
** Tags removed: verification-needed
Resetting the tags to verification-done as per the discussion in
https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
The SRU had been rolled back due to a regression that needed to be
fixed, but we still consider the previous verification to be valid.
** Tags removed: verification-needed
Resetting the tags to verification-done as per the discussion in
https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
The SRU had been rolled back due to a regression that needed to be
fixed, but we still consider the previous verification to be valid.
** Tags removed: verification-needed
Resetting the tags to verification-done as per the discussion in
https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
The SRU had been rolled back due to a regression that needed to be
fixed, but we still consider the previous verification to be valid.
** Tags removed: verification-needed
Please help to validate this SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784347
Title:
ISST-LTE: KVM:UBUNTU1804: BostonLC: fdisk -l shows the conflicting
partitions name for the mpath
To
Resetting the tags to verification-done as per the discussion in
https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
The SRU had been rolled back due to a regression that needed to be
fixed, but we still consider the previous verification to be valid.
** Tags removed: verification-needed
Looks like there are some cases where syslinux will fail to load modules
with the proposed rebuild patch with the new gnu-efi. This is a
regression in syslinux; marking as verification-failed.
** Tags removed: verification-needed-bionic
** Tags added: verification-failed-bionic
** Tags removed: v
I disagree.
We'd be working around a real design issue in systemd, rather that
possibly matching against Type=ethernet (if that existed). I think we
should instead prioritize on avoiding this broken case in the other
parts of the networking stack, and make sure we fix systemd to provide
the right
Verification-done with the xenial grub2/grub2-signed versions:
$ dpkg -l grub\* | grep ii
ii grub-common 2.02~beta2-36ubuntu3.20 amd64GRand
Unified Bootloader (common files)
ii grub-efi-amd642.02~beta2-36ubuntu3.20 amd64GRand
Unified Bootloader
The problem is that DEVTYPE is unreliable at best. Using the MAC of one
of the member interfaces is fine, but only if you really know what
you're doing.
I think we're otherwise back to matching by name instead of by MAC
address (or matching both), if you want to match "like ifupdown was
doing".
T
Gert, could you provide us with an email address so we can correctly
attribute the changes to you, given that you contributed the major part
of the patches that will go in plymouth?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
** Package changed: ubiquity (Ubuntu Disco) => casper (Ubuntu Disco)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796275
Title:
Screen reader is not auto-enabled on first login if enabled when
i
It doesn't matter which process we use, it will be a big SRU regardless.
Also, of course it's an easy fix in MAAS, and it obviously works. I've
shown that setting no "macaddress" field in the netplan syntax does what
it should. Just don't specify a default for that value, and don't write
the macad
Please include the *.network, *.netdev, *.link files from
/etc/systemd/network or /run/systemd/network as well for the
configuration, after making sure you sanitized them if there are any
information (IPs?) that you don't want public.
Thanks!
** Changed in: systemd (Ubuntu)
Status: New =>
Public bug reported:
[Impact]
All users on UEFI systems.
Gnu-efi needs to be backported everywhere to support new shim releases.
This applies to bionic, xenial, and trusty.
This is to properly build the new shim releases on these releases of
Ubuntu.
[Test cases]
-- build tests --
Validate that
lso affects: syslinux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: syslinux (Ubuntu)
Status: New => In Progress
** Changed in: syslinux (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: syslinux (Ubuntu)
I
Public bug reported:
[Impact]
All UEFI users.
[Test case]
== shim ==
1) Enable Secure Boot in firmware.
2) Update to new shim and shim-signed packages (shim 15+, shim-signed 1.37~)
3) Validate that the system still boots and validates the shim image as well as
the grub binary.
== MokManager ==
** Description changed:
[Impact]
All users on UEFI systems.
Gnu-efi needs to be backported everywhere to support new shim releases.
This applies to bionic, xenial, and trusty.
This is to properly build the new shim releases on these releases of
Ubuntu.
-
[Test cases]
-- b
shim and shim-signed 15 / 1.37 are already in Cosmic.
** Also affects: shim (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: shim (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: shim (Ubuntu Cosmic)
Importance: Undecided
Status:
** Also affects: grub2-signed (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/1785033
Title:
GRUB needs to support 64-bit efi linear frame buffer a
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan
Status: New => Fix Committed
** Changed in: netplan.io (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan.io (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736
: Undecided
Status: New
** Changed in: grub2 (Ubuntu Bionic)
Status: New => In Progress
** Changed in: grub2-signed (Ubuntu Bionic)
Status: New => In Progress
** Changed in: grub2-signed (Ubuntu Bionic)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (
Verification-done for bionic with initramfs-tools 0.130ubuntu3.3:
Verified that at boot the system does get the additional config for
netplan in /run/netplan and that it forces systemd-networkd not to
release the IP lease.
** Tags removed: verification-needed verification-needed-artful
verificat
Verification-done on bionic with initramfs-tools 0.130ubuntu3.3:
Verified that with the SRU applied, the initramfs configured to use
MODULES=dep can still determine that the root is over ZFS, and
accordingly add the files needed in the initramfs.
** Description changed:
[Impact]
- Ubuntu users
This confirms the system boots and is in Secure Boot mode. Do you have
time to run through the other test cases using mokutil?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708245
Title:
shim can't
Verification-done for shim, shim-signed on bionic:
shim 15+1533136590.3beb971-0ubuntu1
shim-signed 1.37~18.04.1+15+1533136590.3beb971-0ubuntu1
System is booting as expected with the new shim, and mokutil allows for
importing a certificate and enabling validation at the same time (or any
multiple
Rebuilds in PPA have all passed -- the failures for efitools are exactly
the same as they previously were and due to EFI not being available (or
sbsigntool, efivar, etc.) on those architectures:
https://launchpad.net/~cyphermox/+archive/ubuntu/rebuild-tests/+packages
In any case, amd64 (the only
Assignee: Canonical Foundations Team (canonical-foundations) => Mathieu
Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767918
Title:
Login password from GDM is shown in
There does not appear to be a patch attached? What do you need
sponsored?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789786
Title:
SRU ledmon into Bionic
To manage notifications about this bug
** Tags removed: verification-needed verification-needed-bionic
verification-needed-trusty verification-needed-xenial
** Tags added: verification-done-bionic verification-done-trusty
verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Shim 15+1533136590.3beb971-0ubuntu1
MokSBStateRT isn't on /sys/firmware/efi/efivars when validation is
disabled.
** Affects: shim (Ubuntu)
Importance: High
Status: New
** Changed in: shim (Ubuntu)
Importance: Undecided => High
--
You received this bug not
Are you able to reproduce this bug easily? How would I go about seeing
this?
If I build a new VM with multipath enabled, I do not see this issue, on
trusty or otherwise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Is this running on real hardware or in a virtual machine? If it's on
metal, what kind of hardware?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796260
Title:
UEFI installation alongside BIOS insta
Autopkgtests are passing now for 0.40.1~18.04.1; and the individual bugs
for features / bugfixes have all been verified. Marking verification-
done.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification becau
I'm unsure whether this is NM or n-m-openvpn. Looks more like NM, since
downgrading n-m-openvpn alone didn't seem to change anything.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797236
Title:
net
Public bug reported:
I'm seeing some weird issue with the new NM + openvpn; if I create a new
VPN connection, and add certificate options (verify name exactly, plus
TLS auth), these options are not saved, leading to the connection
failing.
The following versions lead to an invalid connection:
ii
** Changed in: grub2 (Ubuntu)
Status: Triaged => In Progress
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: grub2 (Ubuntu Bionic)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received
Needs to be New for the release team to approve (process is to set to
Triaged)
** Changed in: grub2 (Ubuntu)
Status: Triaged => New
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you
I have reviewed the HTTP code in grub, it looks sane .. no obvious
issues that would break Secure Boot validation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787630
Title:
[FFe] Include HTTP sup
I uploaded a test package to my ppa:
sudo add-apt-repository ppa:cyphermox/ppa
@Gert, would you mind giving it a try, see if this works for you,
assuming that you can reproduce this bug easily?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
SRU to 18.10 and 18.04.
** Changed in: util-linux (Ubuntu)
Assignee: Canonical Foundations Team (canonical-foundations) => Mathieu
Trudel-Lapierre (cyphermox)
** Changed in: util-linux (Ubuntu)
Status: New => Triaged
** Changed in: ubuntu-power-systems
Assignee: Canonical
** Description changed:
+
+ [Impact]
+ Any user of Ubuntu on multipath, where the default path separator has been
changed to something else. This possibly affects other scenarios where the
partition separator can be changed.
+
+ [Test case]
+ 1) Install Ubuntu on multipath system
+ 2) Change /
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1797975/+attachment/5201399/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1797975/+attachment/5201400/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797975
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1797975/+attachment/5201398/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797975
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1797975/+attachment/5201397/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797975
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1797975/+attachment/5201404/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797975
Ti
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1797975/+attachment/5201402/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797975
Public bug reported:
The follow error is shown in dmesg on my Raspberry Pi 2:
[4.380151] device-mapper: uevent: version 1.0.3
[4.388525] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised:
dm-de...@redhat.com
[4.396718] bcm2835-cpufreq: min=60 max=90
[4.407362] s
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1797975/+attachment/5201401/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/179
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1797975/+attachment/5201403/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797975
Title:
[a
This appears to be reproducible again on 18.10, except at very early
boot (premount):
Quiescing Open Firmware ...
Booting Linux via __start() @ 0x0200 ...
Linux ppc64le
#11-Ubuntu SMP T[0.795638] integrity: Unable to open file:
/etc/keys/x509_ima.der (-2)
[0.795640] integrity:
Public bug reported:
I'm unsure what piece is actually causing this, possibly multipath
postinst for mini.iso:
instantiating rtas at 0x2fff... done
prom_hold_cpus: skipped
copying OF device tree...
Building dt strings...
Building dt structure...
Quiescing Open Firmware ...
#11-Ubuntu
This is an efivar bug, that's what will generate file paths for
efibootmgr, specifically in efi_va_generate_file_device_path_from_esp()
and the code it calls.
** Changed in: efibootmgr (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Can you please boot on a live CD and run "sudo efibootmgr -v"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798171
Title:
System fails to boot with \EFI\BOOT\mmx64.efi - Not Found
To manage notif
mokutil now allows exporting the various keys, we'll still need to
integrate this with grub to check for what signs the kernels (and check
for blacklists)
** Changed in: mokutil (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of
I think we'll also need to see what's in /boot/efi in general:
sudo ls -latrR /boot/efi
There is absolutely no reason for mmx64.efi to be missing, ever -- it's
the indication of an incomplete install, or at the very least an issue
with the firmware of the system. We always install mmx64.efi.
--
Clearly not a bug in mokutil if we're having issues with booting -- I'm
removing the task.
** No longer affects: mokutil (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798171
Title:
System
Confirming, I saw this too. It's partman-auto not doing what it should,
and it should be easy enough to fix the recipe (although there undoubtly
are other bugs that will show up then).
LVM+multipath on ppc64el has been broken for a while, unfortunately...
** Package changed: ubiquity (Ubuntu) =>
I will check on that.
** Changed in: partman-crypto (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: partman-crypto (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
m
Assignee: Mathieu Trudel-Lapierre (cyphermox)
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/1798512
Title:
[ppc64el] LVM+crypto on ppc64el points to an invalid crypto_so
It's not reproducible every time; I've done a few more installs and it
looks fine now. Perhaps it's racy.
I was using a VM with 2 disks multipathed.
** Changed in: multipath-tools (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
partman-crypto looks fine at first glance, but I'm starting to suspect
multipath-tools might be addressing devices differently in d-i; possibly
because of how we build the udeb, or what we have in multipath.conf?
** Also affects: multipath-tools (Ubuntu)
Importance: Undecided
Status: New
It appears grub-installer has failed because of an I/O error:
Oct 19 07:56:43 ubuntu ubiquity: grub-install : erreur : efibootmgr failed to
register the boot entry: Erreur d'entrée/sortie.
Oct 19 07:56:43 ubuntu ubiquity: dpkg: error processing package
grub-efi-amd64-signed (--configure):
Oct 19
I don't see any error relating to /cow, but I do see the following:
Oct 19 11:47:40 ubuntu grub-installer: info: Installing grub on '/dev/sda'
Oct 19 11:47:40 ubuntu grub-installer: info: grub-install does not support
--no-floppy
Oct 19 11:47:40 ubuntu grub-installer: info: Running chroot /target
How did you set up the partitioning for that system? Please tell us more
about the disks attached and how you configured the partitions,
including which filesystems you added.
Thanks!
** Changed in: ubiquity (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because
Is this a resized installation, where you selected to install Ubuntu
alongside Windows and let the installer resize partitions?
Oct 23 12:48:56 ubuntu ubiquity: Setting up grub-efi-amd64-signed
(1.93.7+2.02-2ubuntu8.6) ...
Oct 23 12:48:56 ubuntu ubiquity: Instalando para a plataforma x86_64-efi.
This looks a lot like a hardware issue, but we should look into it more:
Setting up grub-efi-amd64-signed (1.110+2.02+dfsg1-5ubuntu8) ...
Installation pour la plate-forme x86_64-efi.
Could not add entry to BootOrder: Interrupted system call
grub-install : erreur : efibootmgr failed to register the
What hardware is this installation done on? Is it partitioned to do
RAID?
I see some errors that possibly indicate a hardware issue:
Oct 22 17:01:12 ubuntu grub-installer: info: Running chroot /target
grub-install --force "/dev/sdc"
Oct 22 17:01:12 ubuntu grub-installer: Installing for x86_64-ef
Do you really mean you are hand-crafting /etc/fstab, or do you mean
partitioning?
Furthermore, it looks like your system is booting in UEFI mode (you see
a grub menu when you start the live CD rather than a purple background
and images). In this case, you also need to create a separate EFI
partiti
Marking Incomplete for now, in case there's more to it than a
connectivity checking issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788659
Title:
network manager assigns ethernet default route
This is working as designed.
NetworkManager now uses a metric "penalty" when connectivity cannot be
detected as full for a connection, and reduces the metric accordingly.
This makes it so that if you're connected to both wired and wireless,
and your wired connection becomes bad but the wireless c
How is your system partitioned? Is it a RAID?
** Changed in: grub2-signed (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/bugs/1795807
Title:
package grub-e
Please run 'sudo grub-install -v" from the live image; we should have a
look at the full debug output to see why md126,1 isn't found.
That said, typically RAIDs are installed by installing grub to each
member separately; which is handled by grub-installer. You don't run
through these steps when do
Confirming, we've used this change (_IO_ftrylockfile replaced by
_IO_EOF_SEEN) in other packages that FTBFS with the new toolchain.
Please also make sure _IO_IN_BACKUP is defined (to 0x100) if it's being
used.
cf. similar changes in coreutils:
Index: coreutils-8.28/lib/fseterr.c
You misunderstand, I think. Why put it in main at all, if you're not
going to be installing it by default? There's just about no use; it's
still only Suggested to install. People can install it from universe
when they want a hardware time source.
--
You received this bug notification because you
No, this is dnsmasq:
udp 0 0 0.0.0.0:67 0.0.0.0:* 5382/dnsmasq
Please make sure you dnsmasq is correctly configured for your use case
(and probably, not configured at all if you want to use isc-dhcp)
** Changed in: isc-dhcp (Ubuntu)
Status
It looks to me like this is happening because your hard drive is
failing:
Oct 22 05:02:56 ubuntu kernel: [ 1943.328046] ata4.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x0
Oct 22 05:02:56 ubuntu kernel: [ 1943.328051] ata4.00: irq_stat 0x4001
Oct 22 05:02:56 ubuntu kernel: [ 1943.328055
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop ISO of the newest
release. It would help us greatly if you could test with it so we can
work on getting it fixe
1 - 100 of 7915 matches
Mail list logo
