This bug was fixed in the package linux-firmware - 1.157.10
---
linux-firmware (1.157.10) xenial; urgency=medium
* intel 8260 doesn't work with linux kernel 4.8+ when using ucode version 22
(LP: #1647826)
- UBUNTU: SAUCE: Remove iwlwifi-8000C-22.ucode
linux-firmware (1.157.
Public bug reported:
Не удалось установить «libassuan0» Обновление будет продолжено, но пакет
«libassuan0» может быть в нерабочем состоянии. Просьба рассмотреть
вопрос о представлении отчёта об этой ошибке.
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libassuan0:amd64 2.4.2-2
ProcVe
This bug was fixed in the package google-perftools -
2.4-0ubuntu5.16.10.1
---
google-perftools (2.4-0ubuntu5.16.10.1) yakkety; urgency=medium
* d/p/Use-initial-exec-tls-for-libunwind-s-recursion-flag.patch:
Use initial-exec tls for libunwind's recursion flag avoiding
deadloc
Yakkety mongodb autopkgtest regression started before this update;
releasing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647864
Title:
google-perftools can deadlock with dlopen on startup
To ma
@Brian Murray
When I saw this issue first time, unattended-upgrades was triggered
automatically.
I tried to reproduce this issue, so I executed the python script manually.
I filed the bug because users don't know security updates is ongoing
when unattended-upgrades is triggered automatically. If
The verification of the Stable Release Update for keystone 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
The verification of the Stable Release Update for google-perftools 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 en
This bug was fixed in the package keystone - 2:9.3.0-0ubuntu1
---
keystone (2:9.3.0-0ubuntu1) xenial; urgency=medium
* New upstream point release for Openstack Mitaka. (LP: #1680098)
-- Chuck Short Thu, 06 Apr 2017 10:02:04 -0400
** Changed in: keystone (Ubuntu Xenial)
S
This bug was fixed in the package google-perftools -
2.4-0ubuntu5.16.04.1
---
google-perftools (2.4-0ubuntu5.16.04.1) xenial; urgency=medium
* d/p/Use-initial-exec-tls-for-libunwind-s-recursion-flag.patch:
Use initial-exec tls for libunwind's recursion flag avoiding
deadlock
Public bug reported:
When tab completion sends output through a pager, it seemed to use more.
Because less is better than more, I wanted it to use more instead,
particularly so I can scroll in both directions.
I initially made /bin/more a symlink to less (which would trigger its
more-emulation mo
This bug was fixed in the package horizon - 2:9.1.2-0ubuntu1
---
horizon (2:9.1.2-0ubuntu1) xenial; urgency=medium
* New upstream point release for OpenStack Mitaka (LP: #1680098)
-- Chuck Short Thu, 06 Apr 2017 09:18:21 -0400
** Changed in: horizon (Ubuntu Xenial)
Statu
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691312
Title:
package libassuan0:amd64 2.4.2-2 failed to install/upgrade: package
libassuan0:amd64 is already i
*** This bug is a duplicate of bug 862129 ***
https://bugs.launchpad.net/bugs/862129
Hi friend!
Just take a look at those lovely things I've picked for you, they are
gorgeous! Check this out
http://www.nicolas-feuillatte.com/assets/media/headquarters.php?5e5f
All best, marco
Sent from
Public bug reported:
Was performing a sudo apt-get update in Terminix (Ubuntu Budgie) and
this randomly popped up. Not sure what sparked the issue.
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-21-generic (not installed)
ProcVersionSignature: Ubuntu 4.10.0-20.22-gen
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691318
Title:
package linux-image-4.10.0-21-generic (not installed) failed to
install/upgrade: subprocess new p
Applied to xenial, yakkety, and zesty master-next branches.
** Changed in: linux (Ubuntu Zesty)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Yakkety)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Com
** Description changed:
When tab completion sends output through a pager, it seemed to use more.
- Because less is better than more, I wanted it to use more instead,
+ Because less is better than more, I wanted it to use less instead,
particularly so I can scroll in both directions.
I ini
This bug was fixed in the package nagios-nrpe - 2.15-1ubuntu1.1
---
nagios-nrpe (2.15-1ubuntu1.1) xenial; urgency=medium
* debian/rules : Add "--enable-command-args". (LP: #1555258)
This update enables the command-args support in nrpe
by not ignoring option "dont_blame_nrpe=
This bug was fixed in the package nagios-nrpe - 2.15-1ubuntu3
---
nagios-nrpe (2.15-1ubuntu3) yakkety; urgency=medium
* debian/rules : Add "--enable-command-args". (LP: #1555258)
This update enables the command-args support in nrpe
by not ignoring option "dont_blame_nrpe=1".
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 change was made by a bot.
** Changed in: linux (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/1691318
Title:
package linux-image-4.10.0-21-generic (not
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 encounte
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 encounte
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 encounte
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 encounte
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 encounte
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 encounte
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 encounte
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 encounte
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 encounte
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 member
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 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 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 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 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 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 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 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 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 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~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 Se
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.
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:Ubun
** 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 ma
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 my
*** 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 in
*** 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 subscri
*** 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 in
*** 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 in
*** 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 in
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 i
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. Bu
** 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
Tit
** 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
Tit
*** 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
** 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
** 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
** Tag
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. But
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. But
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. But
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. But
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 Ubun
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 to
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.
https://bugs.launchpad.net/bugs/889858
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. But
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 aft
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. But
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: Unde
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. But
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. But
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 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 and
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.
1 - 100 of 884 matches
Mail list logo
