Verification was done earlier by dannf; this is the same SRU with more
patches included for a different issue.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Looks good to me here; I was able to have Windows 10 chainload from
grub2 2.02-2ubuntu8.6 / grub2-signed 1.93.7.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Verification-done on bionic, using netplan.io 0.40.1~18.04.1:
"""
parameters (mapping)
Customization parameters for special bridging options. Unless
otherwise specified, parameter values for
time intervals should be expressed in milliseconds, but can also
be e
Verification-done with netplan.io 0.40.1~18.04.1 on bionic:
ubuntu@new-man:~$ ls -l /run/systemd/network/
total 8
-rw-r--r-- 1 root root 83 Oct 9 17:14 10-netplan-ens6.link
-rw-r--r-- 1 root root 209 Oct 9 17:14 10-netplan-ens6.network
ubuntu@new-man:~$ sudo netplan generate
ubuntu@new-man:~$ l
ubuntu@new-man:~$ dpkg -l netplan.io | grep ii
ii netplan.io 0.40.1~18.04.1 amd64YAML network configuration
abstraction for various backends
Marking verification-done:
I have set a dummy route 9.9.9.0/24, with link scope, in netplan YAML.
The route gets correctly installed by system
*** This bug is a duplicate of bug 1736965 ***
https://bugs.launchpad.net/bugs/1736965
Marking verification-done since the master bug #1736965 was marked
verification-done.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You receive
ubuntu@new-man:~$ dpkg -l netplan.io | grep ii
ii netplan.io 0.40.1~18.04.1 amd64 YAML network configuration abstraction for
various backends
I have reverified this SRU using Trevor's netplan yaml. The bridge
interface is correctly brought up at boot, and the right addresses are
set to the right
ubuntu@new-man:~$ dpkg -l netplan.io | grep ii
ii netplan.io 0.40.1~18.04.1 amd64YAML network configuration
abstraction for various backends
Setting verification-done:
I have verified that error messages for 'netplan apply' or 'netplan try'
now correctly display error messages witho
ubuntu@new-man:~$ dpkg -l netplan.io | grep ii
ii netplan.io 0.40.1~18.04.1 amd64YAML network configuration
abstraction for various backends
Verification-done:
netplan now correctly reports either nothing at all (if the interface
does not exist on the system), or a meaningful error
Works for DHCP-managed interfaces as well:
ubuntu@new-man:~$ netplan ip leases ens6
# This is private data. Do not parse.
ADDRESS=10.3.21.28
NETMASK=255.255.240.0
ROUTER=10.3.16.1
SERVER_ADDRESS=10.3.21.25
NEXT_SERVER=10.3.21.25
T1=300
T2=525
LIFETIME=600
DNS=10.3.21.25
NTP=10.3.21.25
DOMAINNAME=c
ubuntu@new-man:~$ dpkg -l netplan.io | grep ii
ii netplan.io 0.40.1~18.04.1 amd64YAML network configuration
abstraction for various backends
I have verified that after hitting Control-C when running 'netplan try',
all characters typed are again being echoed on the terminal.
The same
ubuntu@new-man:~$ dpkg -l netplan.io | grep ii
ii netplan.io 0.40.1~18.04.1 amd64YAML network configuration
abstraction for various backends
I have verified that the 'mtu' property is now correctly documented in
the netplan manpages.
Marking verification-done.
** Tags removed: veri
root@harmless-perch:~# dpkg -l netplan.io | grep ii
ii netplan.io 0.40.1~18.04.1 amd64YAML network configuration
abstraction for various backends
I have verified that the manpage now correctly reads "gratuitous", and
includes a note that the previous misspelling "gratuitious" in also
root@harmless-perch:~# dpkg -l netplan.io | grep ii
ii netplan.io 0.40.1~18.04.1 amd64YAML network configuration
abstraction for various backends
Marking verfication-done:
I have checked that the excerpt:
link-local: [ ipv4 ]
(or ipv6)
Is accepted in netplan.io configuration file
root@harmless-perch:~# dpkg -l netplan.io | grep ii
ii netplan.io 0.40.1~18.04.1 amd64YAML network configuration
abstraction for various backend
I have verified that the manpage correctly reads "prohibit" instead of
"prohibited" as a valid value for route type.
Marking verification-
Marking verification-done based on Ryan's verification.
** Tags removed: regression verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
** Changed in: ledmon (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/1794219
Title:
[MIR] ledmon
To manage notifications about this bug go to:
https://bugs.
Yeah, I feared that might be the case. This is the problem when the bug
isn't so easy to reproduce.
There's a couple of things I want to try; let's proceed now with a
package in a PPA before we randomly upload stuff to the archive --
there's definitely some cleanup code that could be added to plym
** Description changed:
- Hello.
+ [Impact]
+ Any Netplan user leaving empty files in /etc/netplan.
- We see on our jenkins some failing tests on machines updated with the
- bionic-proposed repository.
-
- We found that netplan is crashing when there is an empty YAML
- configuration file.
-
-
Peter checked (I asked him, since they have hardware that clearly
exhibits the issue) and it looks like this is a verification-done:
grub2 2.02-2ubuntu8.6
grub2-signed 1.93.7
I still have to do a quick check with Windows 10 to make sure that
aspect of the fix also works correctly, and that shim-s
** Tags added: regression-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793309
Title:
Backport netplan.io 0.40 to bionic
To manage notifications about this bug go to:
https://bugs.launchp
I can't seem to be able to reproduce this problem (after testing again)
on a VM, so I'll need help to reproduce the bug, and then to validate
the fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792
I'm not convinced that this patch is necessarily what's the right thing
to do -- in your examples, you have mpatha1, for instance -- using no
sparator at all. In this case, fdisk would still display the device
incorrectly.
--
You received this bug notification because you are a member of Ubuntu
B
We'll at least address the upgrade process when the same kernel version
exists in both the vmlinuz file, and the vmlinuz.efi.signed file. We
shouldn't fail and thing this is an unsigned kernel when there's
obviously a signed copy of it also on disk, and grub config will use the
.efi.signed version.
*** This bug is a duplicate of bug 1788727 ***
https://bugs.launchpad.net/bugs/1788727
** This bug has been marked a duplicate of bug 1788727
upgrade crashing due to unsigned kernels
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Closing as Invalid: this is not a bug in grub,
/etc/grub.d/05_debian_theme was modified incorrectly.
At line 127, there is a comment, which makes the entire if statement
have no contained statements. You should remove the # or make the whole
block a comment...
** Changed in: grub2 (Ubuntu)
Thanks for taking the time to file a bug and helping to make Ubuntu
better! Could you please answer the following questions to help us
better understand the problem?
What system model are you installing on? Is this the i386 or the amd64
image (your bug says it's a i386 image, but have you tested b
*** This bug is a duplicate of bug 1792575 ***
https://bugs.launchpad.net/bugs/1792575
** Tags removed: regression-proposed
** This bug has been marked a duplicate of bug 1792575
Boot failure with efi shims from 20180913.0
--
You received this bug notification because you are a member of
You have extra spaces in /etc/default/grub when you changed
GRUB_CMDLINE_DEFAULT:
GRUB_CMDLINE_LINUX_DEFAULT = ""
There shouldn't be spaces around the =.
Closing as Invalid since this isn't a bug in grub.
** Changed in: grub2 (Ubuntu)
Status: New => Invalid
--
You received this bug not
New => Triaged
** Changed in: grub2 (Ubuntu)
Importance: Undecided => High
** Changed in: grub2 (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.
ht
** Changed in: grub2 (Ubuntu)
Status: New => Triaged
** Changed in: grub2 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792262
Title:
package grub-
A patch is attached, and it's a well-defined problem. Just needs that I
take the patch and test that it behaves correctly to land it.
** Changed in: grub2 (Ubuntu)
Status: New => Triaged
** Changed in: grub2 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification
This isn't a security issue.
You may have unsigned kernels on your system, but we're planning to have
grub enforce signed kernels if Secure Boot is enabled -- therefore we
need to catch the case where no kernel is appropriately signed by a key
that is known to the firmware or to shim.
There's cle
: mokutil (Ubuntu)
Importance: Undecided => High
** Changed in: mokutil (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
Not a kernel bug.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790586
Title:
The proposed grub package in Trusty / Bionic overri
My guess is lodygin fails to boot from the network, and cycles all the
way to booting from Hard drive (0004), in which case, since shim and
everything really /are/ installed on disk, it gets run to recreate the
missing "ubuntu" entry.
Assuming you can reproduce this issue easily, can you check if
** Changed in: grub2 (Ubuntu)
Status: New => Triaged
** Changed in: grub2 (Ubuntu)
Importance: Undecided => High
--
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:
Include HTTP
I disagree. This needs to be fixed in Debian as well -- none of the
options are crazy hacks, they are taken as explicit decisions meant to
fix actual problems that people are having.
I have to rebase the patches for Debian, sure; but I don't think we
should leave breadcrumbs around because a test
How is this system installed?
Shim 15 works quite well here to chainload Windows or boot to grub in
cosmic, and isn't yet available to users in other releases of Ubuntu.
** Changed in: grub2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783044
Title:
grub-efi-amd64 postinst fails to install GRUB if /boot/efi/EFI/ubuntu/
** Changed in: grub2 (Ubuntu)
Status: New => Triaged
** Changed in: grub2 (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780598
Title:
grub does
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Triaged
** Changed in: grub2 (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768312
Title:
EFI
Not a bug in ubiquity or grub2. This will need changes in debian-cd (if
I'm not mistaken) in how we generate the menu for live CDs.
** No longer affects: ubiquity (Ubuntu)
** Also affects: debian-cd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: debian-cd (Ubuntu)
Sta
Sadly, I looked into that already, and we don't have that option: the
firmware does not let us know that it really didn't create the entry.
Closing as "Invalid" since the issue was reportedly fixed by disabling
Boot Order Lock.
** Changed in: grub2 (Ubuntu)
Status: New => Invalid
--
You
Should be fixed in 2.02~beta3-4ubuntu7.3; the flashing should be solved
which should be avoiding the crashes (which are likely due to the
graphics card really not liking the flickering).
Can you please confirm whether updating to the new pacakge fixes the
problem?
Can you reach a good menu by hit
This is likely a duplicate of
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1758447
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762862
Title:
Install with encrypted lvm on reboot gives err
*** This bug is a duplicate of bug 1258597 ***
https://bugs.launchpad.net/bugs/1258597
Fix Released: this was fixed in grub2 2.02-2ubuntu12 (in cosmic), and
the work is tracked in bug https://bugs.launchpad.net/bugs/1258597
** This bug has been marked a duplicate of bug 1258597
[Patch] Set
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Triaged
** Changed in: grub2 (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763151
Title:
GRUB_
What filesystem did you use to install? Is it possible that you picked
XFS or another filesystem other than Ext2/3/4 ?
** Changed in: grub2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Triaged:
xfs is clearly not on the list of modules included in signed images, and
there's a very solid point in making sure the images we ship include all
the filesystems we support at install time (zfs is even listed).
** Changed in: grub2 (Ubuntu)
Status: New => Triaged
** Changed in: g
AFAIK, grub-installer (the udeb package) already has logic to install
correctly on RAID systems, by using the underlying devices. This should
be writing grub-*/install-devices as well, which should be taking care
of package upgrades.
diskfilter writes not being supported in grub is certainly not s
This is possibly a firmware issue, seeing as the default state for grub
as provided by maas/curtin config should be to skip modifying nvram.
However, how is the system booting in general? Was BootOrder really set
to booting to the network first? If it's set to other devices, and the
other device h
This would be an enhancement request.
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Triaged
** Changed in: grub2 (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Triaged
** Changed in: grub2 (Ubuntu)
Importance: Undecided => High
** Also affects: grub2 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: grub2 (Ubuntu Xenial)
Status: New => Triaged
** Changed in: g
Could you check in the devices' firmware Setup utility, if there is a
feature called "Boot Order Lock" that is enabled?
** Changed in: grub2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Closing as Fix Released:
grub2 (2.02~beta3-4ubuntu7.3) artful; urgency=medium
* Drop debian/patches/mkconfig_keep_native_term_active.patch, which can
lead to flickering between graphical and text mode when traversing the
menu. (LP: #1752767)
** Changed in: grub2 (Ubuntu)
Status
Landed in grub2 2.02+dfsg1-5ubuntu5.
** Changed in: grub2 (Ubuntu)
Status: Triaged => 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/1754586
Title:
[FFe request] Enable booting i
Are the disks changing in any way? Is this a Dell system? A Lenovo
system?
This has the earmarks of a firmware issue, where the BootEntry variables
are lost -- the system will then try to boot straight to disk, fail to
find a valid boot image, and be stuck; all this possibly because it
manages to
The menu looks about the way it should look, except for what appears
likely to be issues with the screen that displays the menu (the small
sections of black that mess with the text and the lines on top).
Could you please further describe what you see as being the problem?
** Changed in: grub2 (Ub
What are you attempting to do as the time? Is this an upgrade to a new
release of Ubuntu?
** Changed in: grub2 (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/
*** This bug is a duplicate of bug 1258597 ***
https://bugs.launchpad.net/bugs/1258597
We fixed this recently; this is effectively a duplicate of bug 1258597.
** This bug has been marked a duplicate of bug 1258597
[Patch] Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is
How was this system installed? Was it installed in BIOS mode and then
changed to UEFI?
Is shim-signed correctly installed on the system? Without shim-signed
installed and present on the ESP partition
(/boot/efi/EFI/ubuntu/bootx64.efi); as well as listed as the BootEntry
to load (sudo efibootmgr -v
It looks like your /boot partition has run out of space. You will want
to remove old kernels ('sudo apt remove linux-image-')
then run 'sudo apt -f install' to finish the installation.
** Changed in: grub2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you a
We don't currently support this form of full-disk encryption without the
manual interventions you mentioned, and the installer currently sets up
encryption is a way that things will work.
Setting Triaged/Wishlist as this constitutes an obviously valid
enhancement request.
** Changed in: grub2 (Ub
Assigning to linux to we can investigate whether this is caused by a
kernel bug.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: grub2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bu
How was this system installed? Have the disks been replaced or changed
in some way since it was installed?
Could you please run the following command and attach its output to this
bug?
debconf-show grub-pc
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: grub2
Is this still reproducible? We have changed the default gfx mode to stay
"text" on EFI.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720197
Title:
Every second(?) boot fails to display anything [M
Not a bug in shim, but we are adding a Breaks in shim-signed for the
purposes of SRUs to avoid people upgrading into a broken state. As such,
the task for cosmic in Invalid; but absolutely in progress / committed
for other releases.
** Changed in: shim-signed (Ubuntu)
Status: New => Invalid
This does not appear to be a bug in shim at all, closing the shim tasks
as Invalid.
** Changed in: shim (Ubuntu)
Status: New => Invalid
** Changed in: shim (Ubuntu)
Assignee: Canonical Foundations Team (canonical-foundations) =>
(unassigned)
** Changed in: shim (Ubuntu Xenial)
Is this a crash that people are able to easily reproduce? I can't figure
out how to get that crash here, but I have a patch likely to fix the
issue (and the patch is necessary anyway).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
*** This bug is a duplicate of bug 1766872 ***
https://bugs.launchpad.net/bugs/1766872
It's not quite a duplicate, because this message appears before the
network option is even attempted -- it's a bug in the menu code; but
we'll mark it as a duplicate anyway as it's only really apparent when
plan.io (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768783
Title:
mtu is missing in doc reference (only mentioned in
** Changed in: netplan.io (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768798
Title:
netplan try: terminal does
** Description changed:
- ## DRAFT ##
-
[Impact]
-
- "netplan ip leases " command is failing with a Traceback[1]
- when specifying an interface non-existing on the system. non-dhcp
- configured or non configured with netplan.
+ "netplan ip leases " command is failing with a Traceback[1] when
** Description changed:
+ [Impact]
+ Netplan documentation
+
+ [Test case]
+ 1) Run 'man netplan'
+ 2) Validate that the documentation contains a correctly spelled parameter
"gratuitous-arp".
+
+ [Regression potential]
+ This is a documentation-only fix. Watch out for documentation that fails t
** Changed in: netplan
Status: Fix Committed => 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/1771440
Title:
"//" at beginning of YAML file path when error in network config foun
** Changed in: netplan
Status: In Progress => 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/1771704
Title:
support for ipv4 link-local addressing
To manage notifications about t
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan.io (Ubuntu)
Status: New => Fix Released
** Description changed:
+ [Impact]
+ All Ubuntu users.
+
+ [Test case]
+ 1) Look at the netplan manpage:
+
+ man netplan
+
+ 2) Verify that th
netplan.io 0.40 in cosmic contains this fix.
** Description changed:
+ [Impact]
+ Users configuring IPv6 static address with NetworkManager as a backend.
+
+ [Test cases]
+ 1) Configure netplan for static addresses for IPv6, dns settings, but no IPv4
configuration:
+
+ [...]
+ ens8:
+
netplan.io 0.40 landed in cosmic.
** Changed in: netplan.io (Ubuntu)
Status: Confirmed => 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/1793309
Title:
Backport netplan.io 0.40 t
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan.io (Ubuntu)
Status: New => Fix Released
** Changed in: netplan
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bug
** Description changed:
[Impact]
All users of Ubuntu with network configurations using netplan.yaml.
[Test case]
+ 1) Configure network via netplan.yaml for the feature one wants to verify.
+
+ Individual bugs have been opened for separate bugs fixed / features
+ added.
+
+ 1) Run autop
** Description changed:
+ [Impact]
+ Netplan users setting up bridges.
+
+ [Test cases]
+ 1) Add a new bridge configuration in netplan yaml, without an IP address set:
+
+ [...]
+ bridges:
+ br0:
+ interfaces: [ interface ]
+ dhcp4: false
+ parameters:
+ stp:
** Changed in: netplan
Status: In Progress => 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/1736975
Title:
netplan does not bring up anonymous bridge on boot
To manage notificat
** Description changed:
+ [Impact]
+ netplan.io users who define custom routes
+
+ [Test case]
+ 1) Configure netplan.
+ 2) Add a route:
+ [...]
+ routes:
+ - to: 10.10.10.0/24
+ scope: link
+
+ 3) Validate that the route is correctly added to the routing table
+ (using 'sudo ip ro
** Description changed:
+ [Impact]
+ All netplan users.
+
+ [Test case]
+ 1) Run 'sudo netplan try' to "try" a new netplan config.
+ 2) Hit Control-C during the timer, to escape to the terminal without applying
the configuration.
+
+ Validate that text typed on the terminal after hitting Contro
** Description changed:
+ [Impact]
+ Ubuntu users who make use of IPv4 link-local addresses.
+
+ [Test case]
+ 1) Add 'link-local: [ ipv4 ]' to the netplan configuration.
+ 2) Run 'sudo netplan apply'
+
+ [Regression Potential]
+ Enabling link local means additional addresses are available on th
** Description changed:
+ [Impact]
+ Ubuntu users configuring a custom umask on their system
+
+ [Test case]
+ 1) set UMASK in /etc/login.defs to 077
+ 2) Configure netplan to use the networkd renderer, run 'sudo netplan apply'.
+ 3) Verify that systemd-network applies the correct network configu
** Description changed:
+ [Impact]
+ Chainloading grub via grub in a netboot context using MAAS's Boot to local
disk feature.
+
+ [Test cases]
+ 1) Deploy UEFI system using MAAS
+ 2) After deployment, have the system reboot to local disk (via netboot).
+
+ [Regression potential]
+ It is possibl
Bug was confirmed fix, although we don't have a formal version number
for the pacakge that was tested, let's mark this verification-done.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are
What is the status of this MIR? Is it still required to provide some
feature?
Changes were requested, they don't appear to be all done, but I wouldn't
necessarily block on needing to use something other than JAM if the
maintainability of the pacakge is good.
** Changed in: argyll (Ubuntu)
Desktop team NAKed maintaining it, and it looks like reverse-
dependencies would need changes (and for one, having written the nm-
applet patch, I rather this be removed to use standard status icon code
than appindicators). Setting to Incomplete.
If this needs to be in main to support software, pl
@Alan,
Can you confirm which version of plymouth you had installed?
You can use the following command to do so:
dpkg -l plymouth | cat
--
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:
Sponsored the package.
Woodrow, for next SRU uploads like this (which is effectively a
backport), or for other SRUs, please update the version number to be
above the one already in the archive, but below the version number for
the next release. For example:
in bionic right now: 0.79-2build1
the S
** Description changed:
[Impact]
All users of Ubuntu with network configurations using netplan.yaml.
[Test case]
[Regression potential]
-
---
Let's backport netplan.io 0.40 to bionic; as per policy for netplan.io
releases.
Given that it's a core component of the net
Public bug reported:
[Impact]
All users of Ubuntu with network configurations using netplan.yaml.
[Test case]
[Regression potential]
---
Let's backport netplan.io 0.40 to bionic; as per policy for netplan.io
releases.
Given that it's a core component of the networking story, and new
features
That's not what I mean though. For SRU verification we should aim to
have a positive identification of the exact version of the plymouth
package that was used for the tests.
For example, this can be achieved by looking at 'dpkg -l plymouth |
cat':
要望=(U)不明/(I)インストール/(R)削除/(P)完全削除/(H)保持
| 状態=(N)無/
@Alan, could you please confirm which version of plymouth you have
installed for the tests you did?
Thanks!
--
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 s
Not a regression in shim -- shim is doing what it should, but exposes an
actual latent bug in the grub2 EFI patchset. This is still 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/1790724
T
This is identified as a proper "typo" bug in grub, fixing.
** Description changed:
+ [Impact]
+ Dual-boot installs of Ubuntu and Windows 10, and other instances of
chainloading another bootloader from grub2.
+
+ [Test cases]
+ 1) Install Windows 10
+ 2) Install Ubuntu in a dual-boot setup with
801 - 900 of 10796 matches
Mail list logo