Hi Dexuan,
You might want to try this again. There were some delays in completely
processing all the required files for this SRU, which may have
translated in it not being available when you tried.
Judging from deploying a VM here with bionic-proposed enabled, it should
be available now:
ubuntu@
Verification-done for cosmic:
I've installed from mini.iso to get an Ubuntu Desktop; both
01-netcfg.yaml and 01-network-manager-all.yaml are present on disk as
expected. After installing netplan.io 0.96-0ubuntu0.18.10.3 I can see
the netplan-* connection from the installer in the Gnome Shell dropd
** Description changed:
- * Impact
+ [Impact]
+ When using a VPN the DNS requests might still be sent to a DNS server outside
the VPN when they should not
- When using a VPN the DNS requests might still be sent to a DNS server
- outside the VPN when they should not
+ [Test case]
+ 1) Set up a
Thanks! Marking verification-done-xenial since it's been confirmed to
fix the issue.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
** Also affects: grub2 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: grub2 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: grub2 (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: grub2 (Ubuntu)
Status: New => Fix Re
systemd's wpa-* job does not require verifying again; this will not have
changed in this new SRU. Marking verification-done again for bionic and
cosmic.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done-bionic verification-
Setting back to verification-done; tests are still passing for
test_terminal, as per the above comments.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
--
You received this bug notificat
This hasn't changed in bionic or cosmic; previously released SRU which
is again included in the changelog for this backport.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
--
You receive
I'm unable to reproduce this on an X230 or T450s. I would have thought
the firmware to be pretty similar, at least enough that I could see this
issue when a similar config is applied.
This needs more investigation in the code for the console module. I've
had a quick look, nothing obvious jumped ou
Setting back to verification-done; this is still verified for bionic and
cosmic (no change with new revision in -proposed).
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
--
You received
Setting back to verification-done; this is still verified for bionic and
cosmic (no change with new revision in -proposed).
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
--
You received
Setting back to verification-done; this is still verified for bionic and
cosmic (no change with new revision in -proposed).
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
** Tags removed: verification-needed verification-needed-cosmic
** Tags added: verificati
Setting back to verification-done; this is still verified for bionic and
cosmic (no change with new revision in -proposed).
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
--
You received
I've had a look, certainly seems fine packaging-wise; but should be
looked at by the Security Team.
** Changed in: libheif (Ubuntu)
Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
** This bug is no longer a duplicate of bug 1805490
[master] Grub2 Failed to install "efibootmgr failed to register the boot
entry: Block device required."
** Summary changed:
- package grub-efi-amd64-signed 1.93.8+2.02-2ubuntu8.7 failed to
install/upgrade: 'efibootmgr failed to register the
*** This bug is a duplicate of bug 1766945 ***
https://bugs.launchpad.net/bugs/1766945
** This bug is no longer a duplicate of bug 1805490
[master] Grub2 Failed to install "efibootmgr failed to register the boot
entry: Block device required."
** This bug has been marked a duplicate of bug
** Package changed: grub2 (Ubuntu) => efibootmgr (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509660
Title:
Fails to upgrade: `efibootmgr: Could not add entry to BootOrder: No
space lef
** Summary changed:
- [master] Grub2 Failed to install "efibootmgr failed to register the boot
entry: Block device required."
+ [master] Grub2 Failed to install "efibootmgr failed to register the boot
entry: Block device required. / Could not delete variable: Invalid argument"
--
You received
*** This bug is a duplicate of bug 1805490 ***
https://bugs.launchpad.net/bugs/1805490
** This bug has been marked a duplicate of bug 1805490
[master] Grub2 Failed to install "efibootmgr failed to register the boot
entry: Block device required. / Could not delete variable: Invalid argument
*** This bug is a duplicate of bug 1805490 ***
https://bugs.launchpad.net/bugs/1805490
** This bug is no longer a duplicate of bug 1767474
Could not delete variable: Invalid argument (package shim-signed
1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package
post-inst
*** This bug is a duplicate of bug 1805490 ***
https://bugs.launchpad.net/bugs/1805490
** This bug is no longer a duplicate of bug 1767474
Could not delete variable: Invalid argument (package shim-signed
1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package
post-inst
*** This bug is a duplicate of bug 1805490 ***
https://bugs.launchpad.net/bugs/1805490
** This bug is no longer a duplicate of bug 1767474
Could not delete variable: Invalid argument (package shim-signed
1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package
post-inst
Is anyone still seeing this bug on their system?
If so, could you please run the following command so we can see what
might be causing the firmware space to get filled?
ls /sys/firmware/efi/efivars/
Then attach the output to this bug report.
We would like to know, for example, if there are "du
*** This bug is a duplicate of bug 1767570 ***
https://bugs.launchpad.net/bugs/1767570
** This bug has been marked a duplicate of bug 1767570
Could not delete variable: No space left on device (package shim-signed
1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package
Verification-done for bionic:
After installing netplan 0.96-0ubuntu0.18.04.4 the wireless network on
my Thinkpad X230 is again available in Gnome-Shell's network drop-down
(you see the wifi icon); and 'nmcli dev' correctly reports wlp3s0 being
connected to a netplan-X connection.
** Tags remo
Confirmed this is still unchanged for bionic and cosmic SRUs:
netplan.io/0.96-0ubuntu0.18.04.4
netplan.io/0.96-0ubuntu0.18.10.3
NetworkManager renderer works as expected; files are being written with
the .nmconnection suffix and work correctly.
** Tags removed: verification-needed verification-n
This is still verification-done for bionic and cosmic; re-upload was to
address a regression in choosing the renderer; but switching renderers
has been confirmed to cause files to be removed/ re-created and the
services restarted.
** Tags removed: verification-needed verification-needed-bionic
ve
Verification-done for bionic:
ubuntu@ip-172-30-0-32:~$ lsb_release -cs
bionic
ubuntu@ip-172-30-0-32:~$ apt policy netplan.io
netplan.io:
Installed: 0.96-0ubuntu0.18.04.4
Candidate: 0.96-0ubuntu0.18.04.4
Version table:
*** 0.96-0ubuntu0.18.04.4 500
500 http://us-east-1.ec2.archive.ub
Verification-done for cosmic:
ubuntu@ip-172-30-0-50:~$ lsb_release -cs
cosmic
ubuntu@ip-172-30-0-50:~$ apt policy netplan.io
netplan.io:
Installed: 0.96-0ubuntu0.18.10.3
Candidate: 0.96-0ubuntu0.18.10.3
Version table:
*** 0.96-0ubuntu0.18.10.3 500
500 http://us-east-1.ec2.archive.ub
Still verification-done on bionic and cosmic; this hasn't changed with
the new revision in -proposed.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
--
You received this bug notification
Still verification-done on bionic and cosmic; this hasn't changed with
the new revision in -proposed.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
--
You received this bug notification
Still verification-done on bionic and cosmic; this hasn't changed with
the new revision in -proposed.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
--
You received this bug notification
This is still verification-done for bionic and cosmic:
netplan.io/0.96-0ubuntu0.18.04.4
netplan.io/0.96-0ubuntu0.18.10.3
Confirmed that this is still working as expected with the new SRUs after
quickly re-verifying given the changes uploaded to fix the regression in
bug #1825206.
** Tags remov
I am still unable to reproduce this failure case. I don't know what else
to try.
I'm leaving this open so I can discuss this with other developers; but
I'll leave the bug aside for now so we can get back to it and have a way
to track this issue if we manage to find something that needs fixing in
t
I'm not sure changing anything is casper will address this. Aren't the
nvidia drivers only installed towards the "end" of the installation
process, since they wouldn't be available at boot time for the live
image? AFAIK they aren't even shipped on the images.
--
You received this bug notification
Okay, this bug has absolutely nothing to do with grub or netplan.
Changing the renderer couldn't possibly affect the behavior of X, and
the grub configuration looks, at a glace, to be run-of-the mill; pretty
much default if you disregard that there is any number of different
installs on the system.
This appears to work here; if I start with the screen reader enabled in the
isolinux splash (F5,
hit arrow down three times, enter).
** Changed in: casper (Ubuntu Disco)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
The system booted, so it's not a syslinux issue. Maybe kernel? I'm
unsure, as I didn't see anything obviously wrong (to me) in the attached
logs, but the mtrr messages are unusual and warrant some further
investigation.
Reassigning to linux.
** Package changed: syslinux (Ubuntu) => linux (Ubuntu)
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Triaged
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1681
Verification-done on cosmic with partman-efi/71ubuntu4.1:
Starting a d-i install with proposed enabled; with partman-efi installed
in the d-i environment; I could verify that using manual partitioning
and omitting to create an ESP in UEFI mode leads to showing the error
message and blocking the us
syslinux 3:6.04~git20171011.af7e95c3+dfsg1-4ubuntu1.18.10.2
verification-done in cosmic:
I've build new d-i images (mini.iso for netboot) in a PPA with the use
of the new syslinux in cosmic-proposed; the images were bootable and
correctly showing the minimal gfxboot menu expected for mini.iso.
So
In addition to the above; if anyone has previously had Ubuntu 17.10
installed on the affected system, it is possible this is due to bug
1734147. Please see if the bug's description matched with what you are
seeing. If you're unsure, ask here for help.
--
You received this bug notification because
Please read this until the end before commenting. I am closing this bug
as "Invalid", because we can't deal with the many different types of
problems seen by people all on this same bug report.
This is, for most users, a firmware issue (in which case, if you're running a
Dell laptop, please chec
Alright; I think I've finally made some progress on this.
Turns out "Block device required" is really a red herring. It's some
random value (15) used in efibootmgr code, for any number of causes for
failure. We can't read anything into it.
The real error in indeed "Invalid argument", and very muc
After additional testing with hardware (instead of in VMs), it looks
like things are working fine on Lenovo hardware.
I managed to get access to a Lenovo SR670 server. I deployed it from an
existing MAAS, along with a second server (some random node we'll call
http-server) to be an HTTP server, si
: uwsgi (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => Ubuntu Security Team
(ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820227
Title:
[MIR] uwsgi as dependency of m
Thanks, I think we have all the information we need right now; this
needs further investigation by a developer.
** Changed in: efibootmgr (Ubuntu Disco)
Status: Incomplete => Triaged
** Changed in: efibootmgr (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notifica
I'm not sure I understand the request. This is a paperwork bug that was
Fix Released, as libnfs was moved to the right location; it does not
really affect anything for supported releases.
If you need some changes made to packages, please file a separate new
bug with your specific request so that i
Public bug reported:
Block grub2 (2.02+dfsg1-12ubuntu1) in disco-proposed for one last round
of manual testing.
** Affects: grub2 (Ubuntu)
Importance: Undecided
Assignee: Mathieu Trudel-Lapierre (cyphermox)
Status: In Progress
** Tags: block-proposed
** Changed in: grub2
** Changed in: grub2 (Ubuntu)
Status: New => In Progress
** 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.
Manual testing with grub-pc and grub-efi-amd64 looks fine on x86.
Closing Fix Released so grub can migrate from -proposed.
** Changed in: grub2 (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
*** This bug is a duplicate of bug 1818366 ***
https://bugs.launchpad.net/bugs/1818366
** This bug has been marked a duplicate of bug 1818366
[FFe] Carla: Please Upload to Universe
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
So; who did the packaging? Ross or Erich? I'm concerned with the two
names being in changelog because it will make it hard to figure out who
did what :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18
Please fix bug numbers to make sure you close the right bug (the FFE one
here) for the upload in changelog.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818366
Title:
[FFe] Carla: Please Upload to
Nevermind the comment above; I fixed it myself (there's no point in
having a roundtrip just for that); uploaded the package as retrieved via
the dsc (https://launchpad.net/~ubuntustudio-dev/+archive/ubuntu/dev-
testing/+sourcefiles/carla/1.9.13-0ubuntu1/carla_1.9.13-0ubuntu1.dsc).
--
You received
** Changed in: ubuntustudio
Status: Triaged => 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/1818366
Title:
[FFe] Carla: Please Upload to Universe
To manage notifications about
sting with a patched version shows
this delay can be completely eliminated by fixing the netplan-wpa
service and setting DefaultDependencies=no.
** Affects: netplan.io (Ubuntu)
Importance: Critical
Assignee: Mathieu Trudel-Lapierre (cyphermox)
Status: In Progress
** Chang
** Changed in: shim-signed (Ubuntu)
Status: Confirmed => Triaged
** Changed in: shim-signed (Ubuntu)
Importance: Undecided => Critical
** Changed in: shim-signed (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Also affects: shim (Ubuntu)
I
Reassigning to mokutil and marking Fix Released:
I fixed that a few weeks ago. Mokutil reports the state it knows how to,
and that was previously only checking the state of the SecureBoot-*
variable, which is separate from the state that can be toggled in shim.
Now, mokutil looks at SecureBoot, S
** Tags removed: rls-cc-incoming
** Tags added: rls-cc-notfixing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823649
Title:
strace ftbfs in cosmic
To manage notifications about this bug go to:
ht
** Tags removed: rls-dd-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832882
Title:
libcurl-gnutls segfaults spotify client
To manage notifications about this bug go to:
https://bugs.laun
** Changed in: vim (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823651
Title:
vim ftbfs in cosmic (i386 only)
To manage notifications about this bug go to:
** Tags removed: rls-cc-incoming
** Tags added: rls-cc-notfixing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791820
Title:
/usr/share/apport/apport-
gtk:http.client.IncompleteRead:/usr/share/ap
** Tags removed: rls-cc-incoming
** Tags added: rls-cc-notfixing
** Tags added: rls-ee-incoming
--
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 install onto an MBR disk, with a pr
** Tags removed: rls-cc-incoming
** Tags added: rls-cc-notfixing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777428
Title:
UpdateManager does not work behind proxy in many cases
To manage notifi
Public bug reported:
[Impact]
New service on Amazon AWS cloud, providing SSH access to instances; available
to any AWS users.
[Test Cases]
This is manually tested by Amazon:
0) Deploy an Amazon AWS instance with Instance Connect feature enabled
1) Install the ec2-instance-connect package
2) Ver
Package looks good to me; I've done a review of the source code as well
(and I was already somewhat familiar with it for having worked on it
some time ago).
MIR Approved.
** Changed in: probert (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because yo
Public bug reported:
[Availability]
ec2-instance-connect is in the Ubuntu archive, and available for all supported
releases. It is available on all architectures despite only being useful on
Amazon EC2 instances.
[Rationale]
This package is useful on Amazon EC2 instances to make use of a new feat
Adam mentioned fixing the Pre-Depends on adduser (moving adduser to
postinst rather than preinst) and the ancient coreutils Depends; I'll
take care of fixing those.
Aside from that, AFAIK the package is good to go, but asking for a
second opinion so I don't just approve my own MIR.
--
You receiv
** Changed in: ec2-instance-connect (Ubuntu Cosmic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834525
Title:
[SRU] Instance Connect release
To manage notificatio
** Changed in: ec2-instance-connect (Ubuntu Xenial)
Status: Fix Committed => Fix Released
** Changed in: ec2-instance-connect (Ubuntu Disco)
Status: Fix Committed => Fix Released
** Changed in: ec2-instance-connect (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Cha
No; by now this is working exactly as expected; netplan should return 0
as long as there is no actual syntax error in the netplan config; for
now everything else is left to the backends.
** Changed in: nplan (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: netplan
Status: C
** Tags added: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833234
Title:
grub2 ftbfs in eoan
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sourc
A final round of manual testing was completed for the upload in eoan-
proposed; removing block-proposed tag.
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833234
Titl
What are the contents of /etc/default/grub now?
Setting a GRUB_TIMEOUT to -1 should be sufficient to always show the
menu, I'd expect, or is that what is not working?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Verification is confirmed to have been done on all releases affected, by
the Azure team.
** Tags added: verification-done-bionic verification-done-cosmic
verification-done-disco verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Removing block-proposed. Patviafore confirmed that manual tests are
passing.
Pat, could you please give details here?
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/182
** Changed in: ec2-hibinit-agent (Ubuntu)
Status: New => In Progress
** Changed in: ec2-hibinit-agent (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: probert (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: probert (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Package changed: plan (Ubuntu) => netplan.io (Ubuntu)
** Changed in: netplan.io (Ubuntu)
Importance: Undecided => Medium
** Changed in: netplan.io (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
MIR approved. The package looks okay to me, nothing of it is crazy,
though I am surprised by the existence of debian/TODO.
** Changed in: ec2-hibinit-agent (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: ec2-hibinit-agent (Ubuntu)
Assignee: Mathieu Trudel-Lapie
** Tags removed: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798369
Title:
Reinstall Ubuntu (with preserving existing data) shows error message
due to "Could not get lock /targe
** Also affects: aptdaemon (Ubuntu Eoan)
Importance: Medium
Status: New
** Tags removed: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700810
Title:
aptdaemon's crash.py
** Changed in: update-manager (Ubuntu)
Status: Confirmed => Triaged
** Tags removed: rls-ee-incoming
** Also affects: update-manager (Ubuntu Eoan)
Importance: Medium
Status: Triaged
** Changed in: update-manager (Ubuntu Eoan)
Assignee: (unassigned) => Mathieu
** Also affects: initramfs-tools (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: initramfs-tools (Ubuntu Bionic)
Status: New => Triaged
** Tags removed: rls-ee-incoming
** Tags adde
** Tags removed: rls-ee-incoming
** Tags added: rls-ee-notfixing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779639
Title:
update-notifier does not always trigger apport for existing crashes
To
** Tags removed: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824195
Title:
Ubiquity offers network-required options where no network is available
To manage notifications about th
** Tags removed: rls-ee-incoming
** Tags added: bitesize rls-ee-notfixing rls-x-notfixing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809920
Title:
prompt to upgrade to 18.04 shows while upgrade
** Tags removed: rls-ee-incoming
** Also affects: ubuntu-release-upgrader (Ubuntu Eoan)
Importance: Medium
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727472
Title:
[RF
** Tags removed: rls-ee-incoming
** Tags added: rls-ee-notfixing
** Package changed: debian-installer (Ubuntu) => partman-lvm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782507
Title:
L
** Tags removed: rls-ee-incoming
** Tags added: rls-ee-notfixing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828483
Title:
SSL.pm cries about missing CTX_clear_m.al when used by libwww-perl
wit
** Changed in: grub2 (Ubuntu)
Status: New => In Progress
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: grub2 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a
Looks like noto sources now have the right glyphs (since their April 9
release, actually). It will need an update both in Debian and Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828884
Title
Sorry, we don't see it there. The emails are re-jiggled by Launchpad.
If you prefer, you can send it to me directly (cyphermox AT ubuntu.com),
or decline to provide one (since it would show up in the commit logs for
plymouth)
--
You received this bug notification because you are a member of Ubun
Setting to Triaged: it's easily reproduced by developers, and we have
all the information we need to debug it -- nothing is secret or hidden,
just needs someone to look at the packets and what resolved does with
them.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Triaged
--
You rec
Fair enough. I do credit you by name already in the commit messages:
https://gitlab.freedesktop.org/plymouth/plymouth/merge_requests/10
https://gitlab.freedesktop.org/cyphermox/plymouth/commit/c46f446fe44457f599805b685547c2258bb3fa96
https://gitlab.freedesktop.org/cyphermox/plymouth/commit/b082f424
** 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/1800668
Title:
Clarify MAC and MTU setting requirements
To manage notifications abo
That is a different issue we're solving elsewhere. You should be able to
override the UseMTU= field.
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nplan (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: netplan.io (Ubuntu)
Stat
Please see if this is solved by the fix for
https://bugs.launchpad.net/netplan/+bug/1807273 (setting use-mtu: false)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724895
Title:
MTU not applied on p
Won't Fix for nplan: we will not be backporting these fixes to releases
prior to 18.04.
** Changed in: nplan (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
801 - 900 of 7915 matches
Mail list logo
