Closing as Invalid, these were requested for Build-Depends when the
process was required. If this ends up being needed for binary deps,
please don't hesitate to reopen.
** Changed in: cglib (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of
Desktop team, do you care about this package being in main?
** Changed in: gstreamer-vaapi (Ubuntu)
Assignee: Matthias Klose (doko) => Ubuntu Desktop (ubuntu-desktop)
** Changed in: gstreamer-vaapi (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification
Desktop team, do you care about this package being in main?
** Changed in: gstreamer-vaapi (Ubuntu)
Assignee: Matthias Klose (doko) => Ubuntu Desktop (ubuntu-desktop)
** Changed in: gstreamer-vaapi (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification
Public bug reported:
Autopkgtests for netplan.io / nplan are still flaky, and tend to fail to
run succesfully due to bad configuration rather than actually failing
tests.
Fix this.
** Affects: nplan (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
Public bug reported:
Autopkgtests for netplan.io / nplan are still flaky, and tend to fail to
run succesfully due to bad configuration rather than actually failing
tests.
Fix this.
** Affects: nplan (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
Verification-done for artful with nplan 0.32~17.10.4:
Verified behavior for 'critical: true'; when set the IPs are correcly
not released on systemd-networkd restart, which maintains connectivity
to the server.
** Tags removed: verification-needed verification-needed-artful
Verification-done for bionic with netplan.io 0.36.2:
Verified that critical: true is now recognized as a valid option and the
NFS connectivity is maintained when running 'netplan apply' when it is
set in config.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Verification-done with livecd-rootfs 2.408.31 on xenial:
Verified that a project can call on snap_preseed to add a snap to the
build, by providing both the "mountpoint" for the tree in use and the
snap name to add.
** Tags removed: verification-needed verification-needed-xenial
** Tags added:
In the existing bonds section, for the interface that is your bond
(eth1)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774666
Title:
Bond interfaces stuck at 1500 MTU on Bionic
To manage
Can you manually change the mtu in the netplan yaml under eth1? If you
do so, is the MTU then set correctly?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774666
Title:
Bond interfaces stuck at
Verification-done on bionic:
ii dkms 2.3-3ubuntu9.1
all Dynamic Kernel Module Support Framework
ii virtualbox-dkms5.2.10-dfsg-6
all x86 virtualization solution -
** Changed in: netplan.io (Ubuntu)
Status: New => In Progress
** Changed in: netplan.io (Ubuntu)
Importance: Undecided => Medium
** Changed in: netplan.io (Ubuntu)
Status: In Progress => Triaged
** Changed in: netplan
Importance: Undecided => Medium
--
You received this
You seem to have a bad /etc/init.d/netplan file on the system; it's not
coming from the netplan.io package. You should make sure you do not have
the 'netplan' package installed (the network plan server).
Please attach the contents of /etc/NetworkManager/NetworkManager.conf.
** Package changed:
=> In Progress
** Changed in: netplan
Importance: Undecided => Medium
** Changed in: netplan
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan.io (Ubuntu)
St
** Changed in: update-manager (Ubuntu)
Assignee: Adam Conrad (adconrad) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: update-manager (Ubuntu Bionic)
Assignee: Adam Conrad (adconrad) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: update-manager (Ubuntu)
Marking Won't Fix for now, since enabling it isn't in the plans for the
near future.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772893
Title:
netplan has no migrate command
To manage
systemd-networkd won't drop interfaces/ remove addresses for interfaces
that are "not managed".
There's some extra work that will be needed to handle some corner cases
like this one, to figure out some of the changes and enforcing some of
the changes.
** Changed in: netplan.io (Ubuntu)
The attached files look exactly the way they should. Could you please
also attach your netplan configuration?
If netplan specifies that the itnerface in managed by NetworkManager,
we'll need to see if Networkmanager knows to add the DNS information to
systemd-resolved.
** Changed in: netplan.io
The migrate command was deemed not mature enough to be enabled
everywhere; documentation was updated where necessary to not point to
the feature.
https://wiki.ubuntu.com/MigratingToNetplan is special in that it's a
specification for something that we wanted to do; it's only valid
inasmuch as
Yes, should enforce proper permissions on the generated files.
** Changed in: netplan.io (Ubuntu)
Status: Confirmed => Triaged
** Changed in: netplan.io (Ubuntu)
Importance: Undecided => Medium
** Also affects: netplan
Importance: Undecided
Status: New
** Changed in:
** Changed in: netplan.io (Ubuntu)
Status: New => In Progress
** Changed in: netplan.io (Ubuntu)
Importance: Undecided => High
** Changed in: netplan.io (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification be
Still a bug; if systemd-networkd requires a restart, then systemd-
networkd has something that it gets confused about, that we'll need to
figure out.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
** Changed in: netplan.io (Ubuntu)
Status: New => In Progress
** Changed in: netplan.io (Ubuntu)
Importance: Undecided => High
** Changed in: netplan.io (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification be
Won't this work?
network:
version: 2
renderer: networkd
ethernets:
ens3:
addresses:
- 10.20.30.40/32
routes:
- to: 0.0.0.0/0
via: 10.10.10.1
on-link: true
Clearly we need to do better for how to easily define a peer-to-peer
interface,
*** This bug is a duplicate of bug 1769682 ***
https://bugs.launchpad.net/bugs/1769682
This is essentially a duplicate of bug 1769682.
** This bug has been marked a duplicate of bug 1769682
NFS-based remote root hangs when running 'netplan apply'
--
You received this bug notification
Sounds like this is "expected behavior". While gateway4 is available for
all interfaces, it simply adds a new default route for the interface,
always at a metric of 100 (if I'm not mistaken, but definitely always at
the same metric value). In any case, the metric value is up to the
default for
This has been fixed upstream and in ubuntu 18.04:
netplan.io (0.34) bionic; urgency=medium
* New release 0.34 (LP: #1754019):
* Implement "optional: true" to correctly write systemd network definitions
with "RequiredForOnline=false", so that these networks do not block boot.
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan.io (Ubuntu)
Status: New => In Progress
** Changed in: netplan.io (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notifi
Attached is /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg.
This file was rewritten based on the same from another instance (since I
have to remove the file for the extra renaming step not to happen). The
name of the interface was changed from 'ens6' to 'cloud1' to better
display the rename that
** Attachment added: "grep rename from /var/log/syslog that shows the name
changes for interfaces"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1773397/+attachment/5144324/+files/renames.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Attached is the final netplan YAML that should be authoritative for the
system.
** Attachment added: "50-cloud-init.yaml"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1773397/+attachment/5144325/+files/50-cloud-init.yaml
--
You received this bug notification because you are a
** Attachment added: "start of cloud-init log at deployment date"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1773397/+attachment/5144306/+files/deployment.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Every time my VM boots (it was deployed via MAAS), cloud-init will
attempt to rename interfaces despite the system being configured
differently in /etc/netplan/*.yaml --
Whatever config may be in /etc/netplan, the original name of the
interfaces at deployment will be forced
** Attachment added: "date on system for which this report was generated"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1773397/+attachment/5144323/+files/date.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm not completely sure where the code lives in cloud-init; it looks a
bit like what's in:
cloudinit/net/netplan.py
But the code does read as though it should not be running 'udevadm test-
builtin net_setup_link'. However, deploying a system with MAAS shows a
netplan changes are available in git:
Daniel's patch to write udev rules (SRU material):
https://github.com/CanonicalLtd/netplan/commit/b0c51bfa8ba8b898a9feaed9cd7d8790d147d35d
Daniel's patch + dropping replug code + rework 'netplan apply' (code for
cosmic); in progress for upload to cosmic:
My recommended course of action for SRUs:
- write udev .rules files from netplan to enforce renaming
- drop udevadm (net_setup_link) call from cloud-init
The above should be sufficient and non-intrusive enough for SRU. The
tasks for cosmic are additional changes to clean up the behavior for
My recommended course of action for cosmic:
- drop udevadm (net_setup_link) call from cloud-init
- drop set-name "renaming" from cloud-init / maas
- drop replug code in netplan; replace with proper .link code, possibly call
to net_setup_link.
- maybe write udev rule for renaming in netplan
** Patch added: "draft systemd patch to skip should_rename(), adds extra debug
info"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1770082/+attachment/5144272/+files/debug.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
There are a couple of pieces in play here.
One aspect is that we don't really want to write the .link files for
systemd-networkd to /lib or get anything from /run into the initrd --
that defeats the purpose of netplan's config being dynamic.
The second aspect is that depending on how the systems
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan
Status: Incomplete => Confirmed
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Description changed:
+ [Impact]
+ All Ubuntu users for whom Secure Boot is enabled.
+
+ [Test cases]
+ 1) install dkms module (use virtualbox-dkms for example)
+ 2) Upgrade kernel (for example, install 4.15.0-22-generic on top of
4.15.0-20-generic).
+ 3) Verify that the generated module for
Verification-doen for xenial: nplan 0.32~16.04.5
Verified that booting a NFS-based remote root system works correctly
when /run/netplan/ens3.yaml is written; 'critical: true' is recognized
as a valid option in the YAML.
** Tags removed: verification-needed-xenial
** Tags added:
I have positively verified that an affected system (which has a 82599ES
10-Gigabit SFI/SFP+) exhibits the ARP storm behavior when booting with
MAAS using the grubnetx64.efi binary in xenial(-updates), leading to
stopping in the grub prompt; and with the grubnetx64.efi binary in
xenial-proposed no
I've been doing more testing on this, after finding a system with a
10GE NIC that seems affected. With 2.02~beta2-36ubuntu3.17 it's
unhappy, but with 2.02~beta2-36ubuntu3.18 it looks like things are
working just fine.
For now, I'm putting this back to verification-needed until I can
finish the
Well, the CI part confirms that there is no regression, but there is as
yet no indication that the issue is fixed aside from the cases where
firmware was updated (but then, it's not the SRU).
There's still a need to verify the fix positively on affected hardware.
Now, KingJ's comment says that
This is fixed in cosmic; there a new version of initramfs-tools
(0.130ubuntu6).
** Changed in: initramfs-tools (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Frank,
Are you able to help testing this? I do not have access to hardware with
qeth interfaces.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756322
Title:
'netplan apply' fails when trying to
Verification-done on xenial: nplan 0.32~16.04.5
Verification-done on artful: nplan 0.32~17.10.4
Verified that adding "dhcp-identifer: mac" to the configuration at the same
level as "dhcp4: true" lead to the system idenfying itself with its MAC address
instead of a DUID to the DHCP server.
Verification-done for artful: nplan 0.32~17.10.4
Verification-done for xenial: nplan 0.32~16.04.5
Verified that a random file "/run/netplan/toto.yaml" present on the
system is removed when running "netplan apply" with the previous version
of nplan, and remains in place when the new version is
Verification-done on xenial: nplan 0.32~16.04.5
Verification-done on artful: nplan 0.32~17.10.4
With the updated nplan; the mii-monitor-interval set in configuration is
correctly applied to the device as expected, and is processed as
milliseconds or seconds, as appropriate to the config:
676 -->
Verification-done on bionic: netplan.io 0.36.2
Verification-done on artful: nplan 0.32~17.10.4
Verification-done on xenial: nplan 0.32~16.04.5
The updated documentation is available in the SRU'ed packages:
"""
[...] Unless otherwise specified, parameter values for time intervals should be
Verification-done on artful: nplan 0.32~17.10.4
As above for the xenial tests: I get an IPv6 address when I should, and
no IPv6 address when I shouldn't, based on the setup of the LXD bridge.
Behavior is as expected.
** Tags removed: verification-needed verification-needed-artful
Verification-done on xenial: nplan 0.32~16.04.5
nplan-configured LXD container appears to behave as expected: on a setup
with IPv6 enabled, I get an IPv6 address on the container without a
startup delay. In a host with IPv6 disabled on the lxd bridge, the
container also starts up appropriately,
Verification-done on artful: nplan 0.32~17.10.4
Setting mii-monitor-interval to "5" indeed leads to miimon value of 5
(rather than 5000 as previously), as expected:
ubuntu@DellVostroV130:~$ cat /sys/class/net/bond0/bonding/miimon
5
ubuntu@DellVostroV130:~$ cat /etc/netplan/bond.yaml
network:
Verification-done on artful: nplan 0.32~17.10.4
On install of 0.32~17.10.4 on a new MAAS-installed VM and hardware,
/etc/network/interfaces is created and points to netplan.
** Tags removed: verification-needed verification-needed-artful
** Tags added: verification-done-artful
--
You received
This already works in 18.04 (SRU is backport of that code).
** Changed in: livecd-rootfs (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/1771177
Title:
Public bug reported:
[Impact]
Customized images built for 16.04
[Test case]
1) Install livecd-rootfs
2) Take a copy of the code tree for livecd-rootfs.
3) Prepare a project/subproject tree for hooks:
$ mkdir -p live-build/xyz/hooks/
$ echo < live-build/xyz/hooks/000-snap-preseed.binary
#!/bin/sh
Please don't do that.
resolv.conf is a symlink to /run/systemd/resolve/stub-resolv.conf and
should remain that way -- this makes sure any changes on the network are
reflected "automatically" in the resolver's behavior, since you'd be
asking systemd-resolved rather than the libc resolver, and it
MIR approved.
** Changed in: python-distro (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768719
Title:
[MIR] python-distro
To manage
python-distro is missing a team subscriber.
** Changed in: python-distro (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/1768719
Title:
[MIR] python-distro
Works for me. I've been using a config like this for a while, the system
sets the interface name at boot as expected:
network:
version: 2
renderer: networkd
ethernets:
mainif:
match:
macaddress: "b8:27:eb:b6:35:86"
set-name: mainif
addresses: [ "10.3.0.5/23" ]
Updating the bug tags to make it clear where we've landed this and where
it hasn't been fixed yet, given the rename of nplan -> netplan.io in
bionic.
** Changed in: nplan (Ubuntu)
Status: New => Invalid
** Also affects: nplan (Ubuntu Artful)
Importance: Undecided
Status: New
**
** Also affects: nplan (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: nplan (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubuntu
** Also affects: initramfs-tools (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: nplan (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects:
** Description changed:
+ [Impact]
+ All users of netplan on new installs of Ubuntu 18.04.
+
+ [Test case]
+ 1) Install 18.04.
+ 2) Open /etc/network/interfaces for editing.
+ 3) Verify that it contains text to notify the user that Ubuntu 18.04 now uses
netplan for network configuration.
+
+
** Description changed:
+ [Impact]
+ All users of netplan.
+
+ [Test case]
+
+ == LXD containers ==
+ 1) Start an LXD container (artful or bionic)
+ 2) Verify that an IPv6 address is present
+ 3) Verify that the system is brought up in a reasonable time (does not wait 2
minutes to be
This got landed in netplan.io 0.35 in bionic. The changes still should
be part of a SRU.
** 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.
** Also affects: nplan (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/1756587
Title:
mii-mon should have a consistent unit schema
To manage
** Description changed:
+ [Impact]
+ Netboot users with a remote filesystem over NFS (possibly over other
networked filesystems).
+
+ [Test cases]
+ 1) Boot a system with its root filesystem over NFS.
+ 2) Run 'sudo netplan apply'
+ 3) Validate that the system remains responsive and keeps
** Also affects: nplan (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nplan (Ubuntu)
Status: New => In Progress
** Description changed:
+ [Impact]
+ Netboot users, and any scenario where YAML configuration is written to
/run/netplan.
+
+ [Test case]
+ 1) Run 'sudo
Public bug reported:
With a system booted on the network, with its remote root fs on NFS:
Running 'netplan apply' restarts systemd-networkd, which releases the IP
received from DHCP. With no IP (and and IP potentially changing), the
NFS server can't be reached so the system hangs.
'netplan
Doc changes are applied in git now; SRU in progress, but I'm debugging
autopkgtest issues with intergration between it and systemd...
** Changed in: netplan
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
nce: Undecided => High
** Changed in: netplan.io (Ubuntu)
Importance: Undecided => High
** Changed in: netplan
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: netplan.io (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You rece
** Description changed:
+ [Impact]
+ Documentation is confusing to users wishing to tune bond and bridge
parameters. This potentially affects all users of netplan.
+
+
+ [Test case]
+ 1) Update the netplan.io package.
+ 2) Run 'man netplan'
+ 3) Verify that the documentation under "parameters"
The manpage is missing a doc update here, clearly.
We made sure the units were consistently milliseconds where appropriate
(some parameters are always seconds, no matter what backend is used)
late in the bionic cycle (LP: #1765833); the last of these updates
included a doc change, but it didn't
Could people please add the contents of /var/log/syslog from the
installer system after the crash (if they can still get to it)?
PJSingh5000's logs contain a crash in libglib; we should check if that's
how the issue presents for others too?
Is this all happening with standard, unmodified images
** Description changed:
- Steps to reproduce
+ [Impact]
+ Users of Ubuntu dealing with a DHCP server based on Windows Server, possibly
other DHCP server products that do no support RFC 4361.
- 1. Go to man page for netplan
- 2. search for "dhcp"
- 3. Find only on/off options for dhcp4 and
It is landed in 18.04; now looking at SRU to older releases:
netplan.io (0.35) bionic; urgency=medium
* debian/postinst: fix version check for when to write breadcrumbs.
(LP: #1756742)
* bonds/bridges: Support specifying time-based values with "ms" suffix when
the value should be in
** Description changed:
+ [Impact]
+ Users of bond and bridges devices requiring tuning of the default device
parameters.
+
+ [Test case]
+ == Configure MII monitor interval ==
+ 1) Configure a bond device
+ 2) Add parameters:
+
+ bonds:
+ mybond0:
+ parameters:
+
** This bug is no longer a duplicate of bug 1765833
bond intervals default to seconds; breaks existing configs
** Also affects: nplan (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nplan (Ubuntu)
Status: New => Fix Released
** Changed in: netplan
Status: In
** Description changed:
+ [Impact]
+ Server users on s390x configuring qeth devices.
+
+ [Test case]
+ 1) Reconfigure an interface for a QETH device
+ 2) Verify that 'netplan apply' completes successfully, without error.
+
+ [Regression potential]
+ This change has minimal potential for
*** This bug is a duplicate of bug 1765833 ***
https://bugs.launchpad.net/bugs/1765833
** This bug is no longer a duplicate of bug 1745597
mii-monitor-interval unit is undocumented, and may be wrong
** This bug has been marked a duplicate of bug 1765833
bond intervals default to
Public bug reported:
If I have existing data on disk built by a previous version of Ubuntu
(in BIOS (legacy) mode, or a previous Windows install, and no EFI system
partition on disk; the installer presents three choices:
- Replace $existing and reinstall. (if a previous Ubuntu install was
Anybody able to help verifying this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1437353
Title:
UEFI network boot hangs at grub for adapter 82599ES 10-Gigabit
SFI/SFP+
To manage notifications
*** This bug is a duplicate of bug 1766627 ***
https://bugs.launchpad.net/bugs/1766627
** This bug is no longer a duplicate of bug 1766338
package shim-signed 1.34.4+13-0ubuntu2 failed to install/upgrade: installed
shim-signed package post-installation script subprocess returned error
*** This bug is a duplicate of bug 1766627 ***
https://bugs.launchpad.net/bugs/1766627
** This bug is no longer a duplicate of bug 1766338
package shim-signed 1.34.4+13-0ubuntu2 failed to install/upgrade: installed
shim-signed package post-installation script subprocess returned error
*** This bug is a duplicate of bug 1766627 ***
https://bugs.launchpad.net/bugs/1766627
This would be a duplicate of bug 1766627.
** This bug has been marked a duplicate of bug 1766627
package shim-signed 1.34.7+13-0ubuntu2 failed to install/upgrade: installed
shim-signed package
*** This bug is a duplicate of bug 1766627 ***
https://bugs.launchpad.net/bugs/1766627
** This bug is no longer a duplicate of bug 1766338
package shim-signed 1.34.4+13-0ubuntu2 failed to install/upgrade: installed
shim-signed package post-installation script subprocess returned error
Not really; the error not showing up is because the firmware doesn't
report an error, but even if it did we can't necessarily tell the user
anything from it anyway (it might not be breaking because of Boot Order
Lock).
Fallback is a "new" feature to fix other systems that don't remember how
to
Thanks for filing a bug and helping to make Ubuntu better!
I believe the bug you have filed should be resolved with the new version
of shim-signed:
shim-signed (1.34.7) bionic; urgency=medium
* debian/shim-signed.postinst: it's not guaranteed that all linux-image
packages currently
Could MSI Fast Boot skip scanning devices which the EFI subsystem in the
ESP's copy of grub rely on?
There are also actually two "ubuntu" entries in firmware, one with extra
firmware-specific extra options appended. One may work with fastboot
while the other does not.
If you re-enable Fastboot
Could you please attach /etc/fstab?
Have you previously run BootRepair on this system (it is known to cause
issues like the one you're seeing)?
** Changed in: shim-signed (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
After 'netplan try', text is no longer echoed on screen and carriage
returns break prompt display.
Proper behavior can be restored using the 'reset' command.
** Affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
MIR approved.
** Changed in: libfastjson (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746327
Title:
[MIR] libfastjson
To manage notifications about
Public bug reported:
When attempting to load unsigned modules and the signatures are
enforced, a message shows in dmesg pointing to an inexistant manpage:
[...]
[5.154346] Adding 1003516k swap on /dev/mapper/10--3--99--105--vg-swap_1.
Priority:-2 extents:1 across:1003516k FS
[5.277619]
Let's get this reviewed by Security.
I have not looked at it at all yet, but it is a daemon dealing with Xen
domains, etc.
** Changed in: xe-guest-utilities (Ubuntu)
Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)
--
You received this bug notification because you are a
MIR approved.
** Changed in: pv (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746891
Title:
[MIR] pv
To manage notifications about this bug go to:
I'm uploading things now; let's keep them blocked in proposed just long
enough that I have the time for one last test before it reaches
everyone.
** Tags added: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There was a misunderstanding there: I never suggested we should use xkb-
keymap instead (or at least, that's not the message I was trying to
convey).
The intent was to reduce delta by not removing so much code, when
console-setup merges are already difficult. I didn't foresee that some
of that
901 - 1000 of 8586 matches
Mail list logo
