Anybody who still has this issue in Lucid, could you please open a new
bug about it, preferably using the 'ubuntu-bug network-manager' command,
so we can get full details of what is going on? Please make sure you add
how you got that system to Lucid, that is, whether it was a clean
install or an up
Arthur, not a sync because of runlevel changes. I will check if the changes
can be brought in debian.
On Aug 5, 2010 6:50 PM, "Artur Rona" wrote:
Maybe is it a sync?
-- Merge acct 6.5.4-2 (main) from Debian unstable (main)
https://bugs.launchpad.net/bugs/609754 Yo...
--
Merge acct 6.5.4-2 (ma
Debian testing now has 4.1.1-P1-9, please sync that version instead, as
it contains a number of packaging fixes:
isc-dhcp (4.1.1-P1-9) unstable; urgency=high
* debian/control: really don't make the new packages conflict with the
old/transitional packages (closes: #590186)
* debian/cont
** Summary changed:
- Sync isc-dhcp 4.1.1-P1-7 (universe) from Debian unstable (main)
+ Sync isc-dhcp 4.1.1-P1-9 (universe) from Debian unstable (main)
--
Sync isc-dhcp 4.1.1-P1-9 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/605685
You received this bug notification bec
Are you guys still able to reproduce this issue in Lucid? There has been
some additional changes in 0.8 which may have corrected the problem.
** Changed in: network-manager-pptp (Ubuntu Karmic)
Status: Confirmed => Incomplete
--
vpn fails to connect when server requires only 128 bit encry
Sidnei,
Could you please post the contents or an excerpt of /var/log/syslog when
the wireless connection fails both after a clean boot and after a
suspend, if possible?
** Changed in: bcmwl (Ubuntu)
Status: New => Incomplete
--
Firmware doesn't get properly reset
https://bugs.launchpad.n
As posted in the upstream bug:
Dan Williams [NetworkManager developer] 2010-09-07 17:53:03 UTC
CoopVoce and 3 Italy fixes pushed, thanks.
3fe0490d975f5aa493bf21b9e6a443e9d416a485
a1e55a4d7d081e7807bb611082dc685af06f5645
Fix is committed upstream, needs sync after an upload to Debian, or a
update
Public bug reported:
On this laptop using Lucid 10.04.1 with all the latest updates applied,
I cannot record using the integrated microphone which should be beside
the webcam, around the top side of the lid.
Recording using the external jack works as expected.
ProblemType: Bug
DistroRelease: Ubu
** Attachment added: "AlsaDevices.txt"
https://bugs.edge.launchpad.net/bugs/628961/+attachment/1537617/+files/AlsaDevices.txt
** Attachment added: "BootDmesg.txt"
https://bugs.edge.launchpad.net/bugs/628961/+attachment/1537618/+files/BootDmesg.txt
** Attachment added: "Card0.Amixer.value
Re: certification, this is system 201001-5167.
I will test on maverick shortly.
--
[IDT 92HD81B1C5] Can't record using on-board mic
https://bugs.launchpad.net/bugs/628961
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
Since this bug related to getting better diagnostic/error messages and
is more of an improvement to functionality than a bug in it, marking it
confirmed/wishlist.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
** Changed in: network-manager (Ubuntu)
Importance: Undecid
Braiam,
You're welcome to work on improvements to NM, nm-applet, and other items
in the stack. The only thing is that these things would really benefit
from being tested and getting some feedback from upstream, so I'd
encourage you to bring up your ideas for discussion on the
NetworkManager mailin
I'm almost certain I saw the proxy step pop up a couple of times before
on alpha3 and later images.
Just in case, as you go through the installation, is there a network
connection detected?
** Changed in: debian-installer (Ubuntu)
Status: New => Incomplete
--
Input for http proxy was not
Sorry if I expressed myself wrong, the goal was not to doubt your
results but rather to try to find a reason in configuration and choices
during the installer that would cause it not to ask for proxy info. I
tried d-i on server with a standard server install and a JeOS install on
ESX, as well as an
As per comments, marking fix released.
** Changed in: network-manager (Ubuntu)
Status: Fix Committed => Fix Released
--
File missing: "/usr/lib/pppd/2.4.x/nm-pppd-plugin.so"
https://bugs.launchpad.net/bugs/587915
You received this bug notification because you are a member of Ubuntu
Bugs,
Krzysztof,
With your permission I'd like to mark this bug Invalid. I uploaded NM
0.8.1 yesterday. Although it doesn't follow the debian packaging yet,
that's something we should keep in mind for the maverick+1 cycle, and
would very much belong in a blueprint for the next UDS; but I'm not sure
I ca
Alex,
As you've mentioned it, it should be fixed in the trunk PPA (and thus
also in maverick), please continue to test to be sure, but for now I'll
mark this as fix released for Maverick; please let me know if it pops up
again.
/ Matt
--
network-manager roams to (none) ((none)) - background sca
** Also affects: linux (Ubuntu Maverick)
Importance: High
Status: Incomplete
** Also affects: network-manager (Ubuntu Maverick)
Importance: Undecided
Status: Confirmed
** Changed in: network-manager (Ubuntu Maverick)
Importance: Undecided => High
** Changed in: network-man
d in: network-manager (Ubuntu Lucid)
Importance: Undecided => Low
** Changed in: network-manager (Ubuntu Maverick)
Status: Confirmed => Fix Released
** Changed in: network-manager (Ubuntu Maverick)
Assignee: Mathieu Trudel (mathieu-tl) => (unassigned)
--
Networking is disabled
Bartlomiej,
Please confirm you are indeed getting this bug on kubuntu.
Also, could you please specify which "latest update" you mean has made the
problem worse? If you could run the command 'dpkg -l network-manager
network-manager-kde', we could ascertain which versions are affected.
/ Matt
--
As per the above comments, marking this bug as Invalid.
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Invalid
--
Please merge network-manager 0.8.1 from debian sid
https://bugs.launchpad.net/bugs/615402
You received this bug notification because you are a member of Ubuntu
Hi Roman,
Thank you for taking the time to report and bug and helping to make
Ubuntu better!
Do you also need to click on the network-manager icon and select a
wireless, or does it automatically connect (without asking for a a
password) after the 30 seconds?
It's possible this is related to the
Hi Thomas,
The issue you're describing should be fixed in the latest version of
NetworkManager, which will in time be available in Ubuntu 10.10. In the
meantime, I shortly will post a location from which to get latest
packages if you would like to test them for Ubuntu 10.04.
** Changed in: networ
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/G
*** This bug is a duplicate of bug 524565 ***
https://bugs.launchpad.net/bugs/524565
Yup, as mentioned before, this is a duplicate of 524565, let's mark it
as such.
** This bug has been marked a duplicate of bug 524565
Suspend/hibernate breaks network and triggers itself.
* You can subscr
no-auto-default doesn't take care of this -- it's only purpose is to not
re-create the Auto eth0 connection when NM starts, since it already
exists.
There's apparently nothing wrong with your config. However, I see that
the ethernet interface is using the r8169 driver.
Are you able to reproduce a
I can't reproduce this on maverick with a ZTE MF636 modem. Can you
please test with the current development release (Maverick Meerkat) and
see if you can reproduce the same behavior?
** Changed in: network-manager-applet (Ubuntu)
Status: New => Incomplete
--
Disable mobile broadband takes
The file browser that shows up to get certificates for WPA2 Enterprise
indeed starts at $HOME, and I am forced to agree with the design here:
most people don't know that /etc/ssl/certs exists, and this directory
may be different depending on the OS, so it makes sense to start at the
user's home dir
I did this all wrong, not the right bug.
** This bug is no longer a duplicate of bug 524565
Suspend/hibernate breaks network and triggers itself.
--
nm-applet says "network disabled" on first startup/login after a failed
hibernate
https://bugs.launchpad.net/bugs/558919
You received this bug
ulson (chrisccoulson) => Mathieu Trudel (mathieu-tl)
--
keeps rewriting /etc/resolv.conf
https://bugs.launchpad.net/bugs/435874
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
DavorCubranic: 524565 mentions network is enabled but cannot be
connected to, and suspend triggers itself -- not the case here:
networking is disabled after suspend (and is not according to the info
we have from the reporter in the other bug). This is a bug that affects
Lucid (for which there are m
Marking Wishlist - low. There is already an error message in place and
it does mention "could not be read", so I'd say "all" options are
covered in one error message. There could be a way to split it into
different cases, but this kind of improvements should really be done
upstream. Could someone o
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
MaGoo, please open a separate bug for your issue, as it is related to
the openvpn plugin and not the VPNC plugin.
It appears to me like this bug has really been fixed since Intrepid or
Jaunty, following the initial description from the bug reporter: routes
now being imported by the plugin from vpn
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Boynas, tuXzero, please open a separate bug on this issue and add the
number here. The issue you're describing seems to be a different problem
than using single DES encryption.
--
gui does not support vnpc --enable-1des option
https://bugs.launchpad.net/bugs/295693
You received this bug notificat
This issue was fixed a long time ago, the policy provided by network-
manager-vpnc follows the above requirements, so I'm marking this as Fix
Released.
Steven, if you're still seeing issues with NeedSecrets dbus errors,
please report them in a separate bug, and/or reply with the bug number
if you'
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
** Changed in: network-manager-vpnc (Ubuntu)
Importance: Undecided => Wishlist
--
Importing vpnc configuration: uninformative error msg
https://bugs.launchpad.net/bugs/324939
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
Mikko,
Could you attach the pcf you're using (after removing the username and
password), so we can see which SAs are requested, and figure out why
vpnc fails? Thanks in advance.
** Changed in: network-manager-vpnc (Ubuntu)
Status: New => Incomplete
** Changed in: network-manager-vpnc (Ubu
*** This bug is a duplicate of bug 324939 ***
https://bugs.launchpad.net/bugs/324939
Apparently I had already triaged a similar bug, so there is an upstream
bugzilla bug already on this. Marking this bug as a duplicate of 324939,
which already tracks the gnome bug report on the subject.
** Th
Marking as Fixed as per the original reporter's last comment.
** Changed in: network-manager-vpnc (Ubuntu)
Status: New => Fix Released
--
VPN connects flawless, but no changes in behavior
https://bugs.launchpad.net/bugs/370816
You received this bug notification because you are a member of
Timothée,
Have you rebooted after installing network-manager-vpnc? Please advise
as to whether you are still seeing this issue and if it's fixed in a
reboot. Thanks!
** Changed in: network-manager-vpnc (Ubuntu)
Status: New => Incomplete
--
No add button (grayed) available: can't add new
NT Man,
When you save the PIN in the connection editor, can you then get back to
the PIN code in the gnome keyring? You can verify this by going under
System -> Preferences -> Passwords and Encryption Keys. Thanks!
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
netw
No, I think there is a few patches that require careful reviewing and would
probably need to be carried over. Also, this depends on the sync of
isc-dhcp in bug 605685.
On Aug 7, 2010 12:55 PM, "Thomas Bechtold"
wrote:
Public bug reported:
Binary package hint: network-manager
Please sync netw
Looking at this, it seems to me like PINs longer than 4 characters
should now be supported in network-manager 0.8 (lucid and later). Could
someone please confirm this works for them so we can close this bug?
Thanks!
--
Network-Manager-Applet asks for PUK and PIN of only up to 4 digits long while
ssignee: Liam Farrell (liamfez) => Mathieu Trudel (mathieu-tl)
** Changed in: network-manager (Ubuntu Maverick)
Assignee: (unassigned) => Mathieu Trudel (mathieu-tl)
--
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
You received thi
papukaija, do the patches you mentioned (which are the same as I found
but against the 0.8.1 tree), apply cleanly on top of 0.8-0ubuntu3?
--
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
You received this bug notification because you are a
Fabian, this is a different issue. It looks to be something different in
the way knetwork-manager (anyway, the NetworkManager plasma applet)
handles these settings.
** Package changed: network-manager (Ubuntu) => plasma-widget-
networkmanagement (Ubuntu)
--
[kubuntu] NetworkManager default unman
Agreed, so what I'll do is start working on porting the changes to the
new version, and once it's in shape we can send an email to ubuntu-devel
re: opinion on the transition?
** Branch unlinked: lp:~mathieu-tl/dhcp/isc-dhcp-4.1.1-P1-7ubuntu1
--
Please upload isc-dhcp 4.1.1-P1-9 (universe) from D
** Summary changed:
- Sync isc-dhcp 4.1.1-P1-9 (universe) from Debian unstable (main)
+ Please upload isc-dhcp 4.1.1-P1-9 (universe) from Debian unstable (main)
--
Please upload isc-dhcp 4.1.1-P1-9 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/605685
You received this bu
Krzysztof,
I'm sorry, I must have been unclear (and I shouldn't have responded from
my phone in the first place). There isn't only the fact that it's a
sync, which is essentially just changing the title and description. The
problem comes from the fact that NM 0.8.1 requires isc-dhcp 4.1.1, which
a
Reassigning to Ubuntu package network-manager, since this seems to be
what is affected.
** Package changed: ubuntu => network-manager (Ubuntu)
** Changed in: network-manager (Ubuntu)
Status: Invalid => New
--
DNS-servers unavailable in UNE
https://bugs.launchpad.net/bugs/579298
You recei
gerti,
Could you please add some more information to your bug report? I would
like to know what you mean by "no DHCP". Is it that there is no DHCP
server available, or is it that your computer does not get a response?
Also, as you set up eth0, what do you mean by configured with DNS IP
addresses b
This should have been confirmed a long time ago. Marking as Low priority
since it's a cosmetic issue that can be easily worked around:
pkill -HUP gnome-panel
Will restart the panel and redraw icons, usually fixing the problem.
** Changed in: network-manager (Ubuntu)
Status: New => Confirm
*** This bug is a security vulnerability ***
Public security bug reported:
As also reported in RedHat:
https://bugzilla.redhat.com/show_bug.cgi?id=585394
A flaw was recently discovered in dbus-glib where it didn't
respect the "access" flag on properties specified. Basically, core OS
services l
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
601 - 700 of 8571 matches
Mail list logo
