Can you use latest mainline list and latest linux-firmware? If this
issue still happens, please attach output of `journalctl -b`.
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Thanks Simon, do you (or dguido) have a chance to test on Yakkety as
well or would that be too much setup effort?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687711
Title:
strongSwan 5.3.5 has a
** Description changed:
- Expectation:
+ [Impact]
fakeroot ./debian/rules tests
from ubiquity 17.04.1 package, from zesty-proposed to build
successfully.
It does in zesty-release. It does in zesty-proposed too, if one
downgrades: libgl1-mesa-glx libglapi-mesa
If one uses
Nowadays We find in nghttp2-client there exists other bug .
In @src/nghttp.cc:
int HttpClient::initiate_connection()
{
[...]
ssl = SSL_new(ssl_ctx);
[...]
SSL_set_fd(ssl.fd);
SSL_set_connect_state(ssl);
[...]
writefn = ::connected;
}
The function
** Also affects: libepoxy (Ubuntu Xenial)
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/1647600
Title:
Xvfb fails with new mesa, results in ubiquity
Ubuntu does not maintain the gdal package, so filing bugs in Launchpad
does not get your issues fixed.
If you look at the buildlogs, e.g. for xenial [0], you'll see that PGEO
support is enabled:
PGeo support: yes
And that ogrsf_frmts/pgeo is built.
[0]
This bug was fixed in the package ceph - 10.2.7-0ubuntu0.17.04.1
---
ceph (10.2.7-0ubuntu0.17.04.1) zesty; urgency=medium
* New upstream point release (LP: #1684527):
- d/p/disable-openssl-linking.patch: Dropped, no longer required.
- d/control: Add BD on libssl-dev to
This bug was fixed in the package ceph - 10.2.7-0ubuntu0.16.10.1
---
ceph (10.2.7-0ubuntu0.16.10.1) yakkety; urgency=medium
* New upstream point release (LP: #1684527):
- d/p/disable-openssl-linking.patch: Dropped, no longer required.
- d/control: Add BD on libssl-dev to
This bug was fixed in the package ceph - 10.2.7-0ubuntu0.16.04.1
---
ceph (10.2.7-0ubuntu0.16.04.1) xenial; urgency=medium
[ Billy Olsen ]
* Start ceph-all after static-network-up (LP: #1636322):
- d/p/start-ceph-all-after-network.patch: add dependency on
the
This bug was fixed in the package software-properties - 0.96.20.7
---
software-properties (0.96.20.7) xenial; urgency=medium
* software-properties-gtk:
- fix the backend code to set the gnome debconf frontend, without which
libgtk2-perl goes unused.
- depend on
This bug was fixed in the package ceph - 10.2.7-0ubuntu0.16.04.1
---
ceph (10.2.7-0ubuntu0.16.04.1) xenial; urgency=medium
[ Billy Olsen ]
* Start ceph-all after static-network-up (LP: #1636322):
- d/p/start-ceph-all-after-network.patch: add dependency on
the
The verification of the Stable Release Update for ceph has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
May be it is related to
https://bugzilla.redhat.com/show_bug.cgi?id=1441601#c8
?
Are patches from there in ubuntu?
** Bug watch added: Red Hat Bugzilla #1441601
https://bugzilla.redhat.com/show_bug.cgi?id=1441601
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
after todays update to 52.1.1 while sending message using smtp server with
STARTTLS and auth thunderbird reports unknown error:
Ошибка отправления сообщения.
Отправка сообщения с использованием Сервера исходящей почты (SMTP) «» не
удалась по неизвестной причине
Public bug reported:
The same problem as reported upstream in https://github.com/Bumblebee-
Project/Bumblebee/issues/704 - secondary Xorg fails to start because it
is being executed SUID by Xorg.wrap. Disabling executable bits on
/usr/lib/xorg/Xorg.wrap makes it work.
Patch in
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]
** Changed in: firefox (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633634
[Expired for vim (Ubuntu) because there has been no activity for 60
days.]
** Changed in: vim (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638122
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673250
[Expired for mysql-5.7 (Ubuntu) because there has been no activity for
60 days.]
** Changed in: mysql-5.7 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for thermald (Ubuntu) because there has been no activity for 60
days.]
** Changed in: thermald (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673635
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611742
Title:
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
And all earlier versions have also reached end of life.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
This appears to still be an issue in Ubuntu 17.10. Although that might
just be because libdrm on my machine reports "unknown" subpixel ordering
for my monitor. So greyscale is the correct fallback...
Can anyone confirm if this bug was fixed?
** Changed in: gnome-shell (Ubuntu)
Importance:
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Seems to be fixed now. See also bug 889858.
** Changed in: gnome-shell (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/893730
Title:
notification
Thank you for reporting this bug to Ubuntu.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
This appears to be fixed in the current release. Probably earlier...
** Changed in: gnome-shell (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/889353
This bug appears to be fixed in Ubuntu 17.10. Probably earlier releases
too.
** Changed in: gnome-shell (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I don't fully understand the description here. Can you please explain
the utility in integrating "places" with context menus?
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Turns out that gnome-software has explicitly disabled interactivity in
the packagekit plugins, this is why the debconf doesn't work:
pk_client_set_interactive (PK_CLIENT (priv->task), FALSE);
I'll ask upstream why this is...
--
You received this bug notification because you are a member of
Thank you for reporting this bug to Ubuntu.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
** Changed in: gnome-shell (Ubuntu)
Importance: Wishlist => High
** Changed in: gnome-shell (Ubuntu)
Status: New => Triaged
** Also affects: ubuntu-themes (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-themes (Ubuntu)
Importance: Undecided => High
**
Thank you for reporting this bug to Ubuntu.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
** Also affects: yubikey-piv-manager (Ubuntu Zesty)
Importance: Undecided
Status: New
** Changed in: yubikey-piv-manager (Ubuntu Zesty)
Status: New => In Progress
** Changed in: yubikey-piv-manager (Ubuntu Zesty)
Assignee: (unassigned) => Luke Faraone (lfaraone)
** Changed
*** This bug is a duplicate of bug 882022 ***
https://bugs.launchpad.net/bugs/882022
** This bug has been marked a duplicate of bug 882022
Gnome-shell needs some Ubuntu design/theming integration (font, on-off
swithch, etc.)
--
You received this bug notification because you are a member
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Medium
** Changed in: gnome-shell (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/851654
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Medium
** Changed in: gnome-shell (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/864369
Thank you for reporting this bug to Ubuntu.
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
*** This bug is a duplicate of bug 1647600 ***
https://bugs.launchpad.net/bugs/1647600
** This bug is no longer a duplicate of bug 1574886
All gtk applications Segfault if no GLX context is active
** This bug has been marked a duplicate of bug 1647600
Xvfb fails with new mesa, results
*** This bug is a duplicate of bug 1647600 ***
https://bugs.launchpad.net/bugs/1647600
** This bug is no longer a duplicate of bug 1574886
All gtk applications Segfault if no GLX context is active
** This bug has been marked a duplicate of bug 1647600
Xvfb fails with new mesa, results
*** This bug is a duplicate of bug 1647600 ***
https://bugs.launchpad.net/bugs/1647600
** This bug is no longer a duplicate of bug 1574886
All gtk applications Segfault if no GLX context is active
** This bug has been marked a duplicate of bug 1647600
Xvfb fails with new mesa, results
*** This bug is a duplicate of bug 1647600 ***
https://bugs.launchpad.net/bugs/1647600
** This bug has been marked a duplicate of bug 1647600
Xvfb fails with new mesa, results in ubiquity FTBFS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1647600 ***
https://bugs.launchpad.net/bugs/1647600
** This bug is no longer a duplicate of bug 1574886
All gtk applications Segfault if no GLX context is active
** This bug has been marked a duplicate of bug 1647600
Xvfb fails with new mesa, results
** Tags added: xenial
** Tags added: regression-release
** Tags added: zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647600
Title:
Xvfb fails with new mesa, results in ubiquity FTBFS
To
1) At the very least, 16.10. I think it was working ever since I
installed libinput as noted in the earlier bug, which might have been
around 16.04 or 15.10.
2) I don't think that's a BIOS setting? Not sure where you're getting
that from, I think it's a Windows driver setting. In any case, both
Public bug reported:
Summary:
/etc/chromium-browser/customizations/10-flash sets --ppapi-flash-version to
empty string.
I apologize if this is a poor description. See discussion section after
"Required information" for speculation.
Required information:
1. lsb_release -rd
Description:
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~17.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~17.04.1) zesty; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream snapshot.
*** This bug is a duplicate of bug 1647600 ***
https://bugs.launchpad.net/bugs/1647600
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574886
Title:
All gtk applications
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~17.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~17.04.1) zesty; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream snapshot.
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~17.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~17.04.1) zesty; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream snapshot.
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~17.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~17.04.1) zesty; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream snapshot.
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~17.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~17.04.1) zesty; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream snapshot.
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~17.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~17.04.1) zesty; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream snapshot.
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~17.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~17.04.1) zesty; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream snapshot.
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~17.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~17.04.1) zesty; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream snapshot.
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~17.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~17.04.1) zesty; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream snapshot.
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.10.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.10.1) yakkety; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.10.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.10.1) yakkety; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.10.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.10.1) yakkety; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.10.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.10.1) yakkety; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.10.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.10.1) yakkety; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.10.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.10.1) yakkety; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.10.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.10.1) yakkety; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.10.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.10.1) yakkety; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
Hi,
Sorry for the silence, I'm in a busy spell and not able to look at
Ubuntu stuff right now. I do intend to follow up and propose the patch
for a stable update when I can; anyone else is welcome to beat me to it
in the meantime.
--
You received this bug notification because you are a
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.10.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.10.1) yakkety; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
The verification of the Stable Release Update for cloud-init has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
The verification of the Stable Release Update for cloud-init has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for cloud-init has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
The verification of the Stable Release Update for cloud-init has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for cloud-init has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for cloud-init has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
The verification of the Stable Release Update for cloud-init has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for cloud-init has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
1 - 100 of 868 matches
Mail list logo
