Launchpad has imported 2 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=32210.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help
This bug was fixed in the package linux - 2.6.32-61.124
---
linux (2.6.32-61.124) lucid; urgency=low
[ Luis Henriques ]
* Revert "sysctl net: Keep tcp_syn_retries inside the boundary"
- LP: #1326473
* Revert "net: check net.core.somaxconn sysctl values"
- LP: #1326473
This bug was fixed in the package linux - 3.13.0-29.53
---
linux (3.13.0-29.53) trusty; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi=1)
- LP: #1326367
- CVE-2014-3
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-stable-Prepare-packa
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Adam Conrad
(adconrad)
** Changed in: kernel-sru-workflow/promote-to-updates
This bug was fixed in the package linux - 2.6.32-61.124
---
linux (2.6.32-61.124) lucid; urgency=low
[ Luis Henriques ]
* Revert "sysctl net: Keep tcp_syn_retries inside the boundary"
- LP: #1326473
* Revert "net: check net.core.somaxconn sysctl values"
- LP: #1326473
This bug was fixed in the package linux-ec2 - 2.6.32-365.79
---
linux-ec2 (2.6.32-365.79) lucid; urgency=low
[ Brad Figg ]
* Rebased to Ubuntu-2.6.32-61.124
-- Brad FiggWed, 04 Jun 2014 15:25:02 -0700
** Changed in: linux-ec2 (Ubuntu Lucid)
Status: New => Fix Release
The verification of the Stable Release Update for linux 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 re
The verification of the Stable Release Update for linux 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 re
This bug was fixed in the package linux - 3.13.0-29.53
---
linux (3.13.0-29.53) trusty; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi=1)
- LP: #1326367
- CVE-2014-3
** Description changed:
This bug is for tracking the 2.6.32-61.123 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-stable-
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Adam Conrad
(adconrad)
** Changed in: kernel-sru-workflow/promote-to-updates
This bug was fixed in the package linux - 2.6.32-61.124
---
linux (2.6.32-61.124) lucid; urgency=low
[ Luis Henriques ]
* Revert "sysctl net: Keep tcp_syn_retries inside the boundary"
- LP: #1326473
* Revert "net: check net.core.somaxconn sysctl values"
- LP: #1326473
This bug was fixed in the package linux - 3.13.0-29.53
---
linux (3.13.0-29.53) trusty; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi=1)
- LP: #1326367
- CVE-2014-3
This bug was fixed in the package linux - 3.13.0-29.53
---
linux (3.13.0-29.53) trusty; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi=1)
- LP: #1326367
- CVE-2014-3
This bug was fixed in the package linux-ec2 - 2.6.32-365.79
---
linux-ec2 (2.6.32-365.79) lucid; urgency=low
[ Brad Figg ]
* Rebased to Ubuntu-2.6.32-61.124
-- Brad FiggWed, 04 Jun 2014 15:25:02 -0700
--
You received this bug notification because you are a member of Ubuntu
This bug was fixed in the package linux - 3.13.0-29.53
---
linux (3.13.0-29.53) trusty; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi=1)
- LP: #1326367
- CVE-2014-3
This bug was fixed in the package linux - 3.13.0-29.53
---
linux (3.13.0-29.53) trusty; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi=1)
- LP: #1326367
- CVE-2014-3
This bug was fixed in the package linux - 3.13.0-29.53
---
linux (3.13.0-29.53) trusty; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi=1)
- LP: #1326367
- CVE-2014-3
This bug was fixed in the package linux - 3.13.0-29.53
---
linux (3.13.0-29.53) trusty; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi=1)
- LP: #1326367
- CVE-2014-3
This bug was fixed in the package linux - 2.6.32-61.124
---
linux (2.6.32-61.124) lucid; urgency=low
[ Luis Henriques ]
* Revert "sysctl net: Keep tcp_syn_retries inside the boundary"
- LP: #1326473
* Revert "net: check net.core.somaxconn sysctl values"
- LP: #1326473
This bug was fixed in the package linux - 3.13.0-29.53
---
linux (3.13.0-29.53) trusty; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi=1)
- LP: #1326367
- CVE-2014-3
This bug was fixed in the package linux - 2.6.32-61.124
---
linux (2.6.32-61.124) lucid; urgency=low
[ Luis Henriques ]
* Revert "sysctl net: Keep tcp_syn_retries inside the boundary"
- LP: #1326473
* Revert "net: check net.core.somaxconn sysctl values"
- LP: #1326473
This bug was fixed in the package linux - 2.6.32-61.124
---
linux (2.6.32-61.124) lucid; urgency=low
[ Luis Henriques ]
* Revert "sysctl net: Keep tcp_syn_retries inside the boundary"
- LP: #1326473
* Revert "net: check net.core.somaxconn sysctl values"
- LP: #1326473
This bug was fixed in the package linux-ec2 - 2.6.32-365.79
---
linux-ec2 (2.6.32-365.79) lucid; urgency=low
[ Brad Figg ]
* Rebased to Ubuntu-2.6.32-61.124
-- Brad FiggWed, 04 Jun 2014 15:25:02 -0700
** Changed in: linux-ec2 (Ubuntu Lucid)
Status: Fix Committed => F
This bug was fixed in the package linux-ec2 - 2.6.32-365.79
---
linux-ec2 (2.6.32-365.79) lucid; urgency=low
[ Brad Figg ]
* Rebased to Ubuntu-2.6.32-61.124
-- Brad FiggWed, 04 Jun 2014 15:25:02 -0700
--
You received this bug notification because you are a member of Ubuntu
This bug was fixed in the package linux - 3.13.0-29.53
---
linux (3.13.0-29.53) trusty; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi=1)
- LP: #1326367
- CVE-2014-3
This bug was fixed in the package linux - 2.6.32-61.124
---
linux (2.6.32-61.124) lucid; urgency=low
[ Luis Henriques ]
* Revert "sysctl net: Keep tcp_syn_retries inside the boundary"
- LP: #1326473
* Revert "net: check net.core.somaxconn sysctl values"
- LP: #1326473
This bug was fixed in the package linux-lts-quantal -
3.5.0-51.77~precise1
---
linux-lts-quantal (3.5.0-51.77~precise1) precise; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_
This bug was fixed in the package linux-lts-quantal -
3.5.0-51.77~precise1
---
linux-lts-quantal (3.5.0-51.77~precise1) precise; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_
This bug was fixed in the package linux - 3.11.0-23.40
---
linux (3.11.0-23.40) saucy; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi=1)
- LP: #1326367
- CVE-2014-31
This bug was fixed in the package linux-lts-raring -
3.8.0-42.62~precise1
---
linux-lts-raring (3.8.0-42.62~precise1) precise; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi
This bug was fixed in the package linux-lts-saucy -
3.11.0-23.40~precise1
---
linux-lts-saucy (3.11.0-23.40~precise1) precise; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi
This bug was fixed in the package linux-lts-saucy -
3.11.0-23.40~precise1
---
linux-lts-saucy (3.11.0-23.40~precise1) precise; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi
This bug was fixed in the package linux - 3.11.0-23.40
---
linux (3.11.0-23.40) saucy; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi=1)
- LP: #1326367
- CVE-2014-31
This bug was fixed in the package linux - 3.11.0-23.40
---
linux (3.11.0-23.40) saucy; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi=1)
- LP: #1326367
- CVE-2014-31
This bug was fixed in the package linux - 3.11.0-23.40
---
linux (3.11.0-23.40) saucy; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi=1)
- LP: #1326367
- CVE-2014-31
This bug was fixed in the package linux-lts-trusty -
3.13.0-29.53~precise1
---
linux-lts-trusty (3.13.0-29.53~precise1) precise; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_
This bug was fixed in the package linux-lts-trusty -
3.13.0-29.53~precise1
---
linux-lts-trusty (3.13.0-29.53~precise1) precise; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_
This bug was fixed in the package linux - 3.13.0-29.53
---
linux (3.13.0-29.53) trusty; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi=1)
- LP: #1326367
- CVE-2014-3
This bug was fixed in the package linux-lts-raring -
3.8.0-42.62~precise1
---
linux-lts-raring (3.8.0-42.62~precise1) precise; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi
This bug was fixed in the package linux - 3.11.0-23.40
---
linux (3.11.0-23.40) saucy; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi=1)
- LP: #1326367
- CVE-2014-31
This bug was fixed in the package linux-lts-raring -
3.8.0-42.62~precise1
---
linux-lts-raring (3.8.0-42.62~precise1) precise; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi
To correct my previous post, I tested the fixed kernel on
debian/jessie/xfce (and kde), not mint/xfce. This is a desktop not a
laptop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1283938
Title:
[S
This bug was fixed in the package linux-lts-raring -
3.8.0-42.62~precise1
---
linux-lts-raring (3.8.0-42.62~precise1) precise; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi
This bug was fixed in the package linux - 3.13.0-29.53
---
linux (3.13.0-29.53) trusty; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi=1)
- LP: #1326367
- CVE-2014-3
Public bug reported:
When I want to send a file to a Mac via bluetooth in Ubuntu 14.04
(Gnome), I have to type "bluetooth-sendto" in a terminal in order to be
able to browse a file and send it.
When I am connected to an Android Smartphone (in my tests Galaxy Note II
and Note III), I see a button
*** This bug is a duplicate of bug 848115 ***
https://bugs.launchpad.net/bugs/848115
yuval, I cannot reproduce this bug by following steps you provided on
Ubuntu 14.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
** Patch added: "libreoffice-dictionaries_trusty.patch"
https://bugs.launchpad.net/ubuntu/+source/libreoffice-dictionaries/+bug/1308771/+attachment/4126011/+files/libreoffice-dictionaries_trusty.patch
** Tags added: patch
** Description changed:
- While the libreoffice-dictionaries source pa
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Adam Conrad
(adconrad)
** Changed in: kernel-sru-workflow/promote-to-updates
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Adam Conrad
(adconrad)
** Changed in: kernel-sru-workflow/promote-to-updates
This bug was fixed in the package linux - 3.2.0-64.97
---
linux (3.2.0-64.97) precise; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi=1)
- LP: #1326367
- CVE-2014-31
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Adam Conrad
(adconrad)
** Changed in: kernel-sru-workflow/promote-to-updates
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Adam Conrad
(adconrad)
** Changed in: kernel-sru-workflow/promote-to-updates
This bug was fixed in the package linux - 3.2.0-64.97
---
linux (3.2.0-64.97) precise; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi=1)
- LP: #1326367
- CVE-2014-31
Ah! The log always contains as the only entry:
"(unity-settings-daemon:13702): color-plugin-WARNING **: failed to
connect to device: Failed to connect to missing device
/org/freedesktop/ColorManager/devices/cups_Hewlett_Packard_HP_LaserJet_Professional_P_1102w"
I have a printer of that type (colo
This bug was fixed in the package linux - 3.2.0-64.97
---
linux (3.2.0-64.97) precise; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi=1)
- LP: #1326367
- CVE-2014-31
This bug was fixed in the package linux - 3.2.0-64.97
---
linux (3.2.0-64.97) precise; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi=1)
- LP: #1326367
- CVE-2014-31
This bug was fixed in the package linux - 3.2.0-64.97
---
linux (3.2.0-64.97) precise; urgency=low
[ Upstream Kernel Changes ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
uaddr2 in futex_requeue(..., requeue_pi=1)
- LP: #1326367
- CVE-2014-31
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Adam Conrad
(adconrad)
** Changed in: kernel-sru-workflow/promote-to-updates
Public bug reported:
This error report is there after boot up, I do not have any further info
ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: linux-image-extra-3.11.0-22-generic 3.11.0-22.38
ProcVersionSignature: Ubuntu 3.11.0-22.38-generic 3.11.10.8
Uname: Linux 3.11.0-22-generic x86_6
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Adam Conrad
(adconrad)
** Changed in: kernel-sru-workflow/promote-to-updates
I have had another look at this bug. There are a log of issues. Looking at
Museo Sans Rounded with FontForge and some print statements inside Inkscape one
finds:
Name PS Weight TTF Style Pango Pango Weight
100 Extra Light 100300 Light
300 Light300
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Description changed:
This bug is for tracking the 3.2.0-1634.49 upload package. This bug will
contain status and tes
** Changed in: kernel-sru-workflow/verification-testing
Status: New => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Assignee: Canonical Platform QA Team (canonical-platform-q
This bug was fixed in the package linux-armadaxp - 3.2.0-1634.49
---
linux-armadaxp (3.2.0-1634.49) precise-proposed; urgency=low
[ Ike Panhc ]
* Release Tracking Bug
- LP: #1326748
* Rebase to Ubuntu-3.2.0-64.97
[ Ubuntu: 3.2.0-64.97 ]
* futex-prevent-requeue-pi-on-s
This bug was fixed in the package linux-armadaxp - 3.2.0-1634.49
---
linux-armadaxp (3.2.0-1634.49) precise-proposed; urgency=low
[ Ike Panhc ]
* Release Tracking Bug
- LP: #1326748
* Rebase to Ubuntu-3.2.0-64.97
[ Ubuntu: 3.2.0-64.97 ]
* futex-prevent-requeue-pi-on-s
*** This bug is a duplicate of bug 1326748 ***
https://bugs.launchpad.net/bugs/1326748
This bug was fixed in the package linux-armadaxp - 3.2.0-1634.49
---
linux-armadaxp (3.2.0-1634.49) precise-proposed; urgency=low
[ Ike Panhc ]
* Release Tracking Bug
- LP: #1326748
This bug was fixed in the package linux-armadaxp - 3.2.0-1634.49
---
linux-armadaxp (3.2.0-1634.49) precise-proposed; urgency=low
[ Ike Panhc ]
* Release Tracking Bug
- LP: #1326748
* Rebase to Ubuntu-3.2.0-64.97
[ Ubuntu: 3.2.0-64.97 ]
* futex-prevent-requeue-pi-on-s
This bug was fixed in the package linux-armadaxp - 3.2.0-1634.49
---
linux-armadaxp (3.2.0-1634.49) precise-proposed; urgency=low
[ Ike Panhc ]
* Release Tracking Bug
- LP: #1326748
* Rebase to Ubuntu-3.2.0-64.97
[ Ubuntu: 3.2.0-64.97 ]
* futex-prevent-requeue-pi-on-s
Public bug reported:
When you print a PDF document, and you choose a print paper size which is
different from the document's paper size, you can shrink or fit to printable
area (or neither), but there is no way to:
- break big pages into smaller ones, such as for example break each A3 page
into
** Changed in: linux-ti-omap4 (Ubuntu)
Status: New => Invalid
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
** Tags removed: update
** Tags added: upgrade-software-version utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303564
Title:
Please update rkhunter to 1.4.2
To manage notifications about thi
** Also affects: android-udev (Arch Linux)
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/1306747
Title:
lsusb shows wrong name of the connected phone
To
** Branch linked: lp:ubuntu/precise-proposed/linux-lts-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1326367
Title:
exploitable futex vulnerability
To manage notifications about this bug go
I've verified this was fixed in 3.13.0-29.53. Thanks!
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318848
Title:
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Adam Conrad
(adconrad)
** Changed in: kernel-sru-workflow/promote-to-updates
Public bug reported:
Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1
Card: Sierra Wireless EM7305 (PCI Express M.2 form factor)
Expected: Sierra plugin is used
Happens: Generic plugin is used instead
After cold start the card seems to work almost fine, but does not come
back after suspend or
** Attachment added: "Screenshot"
https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1326953/+attachment/4126039/+files/gnome-font-viewer.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Public bug reported:
Menu buttons "<" (Back), Info and Install are duplicated on each font
open on the same font viewer instance.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gnome-font-viewer 3.8.0-1build1
ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
Uname: Linux 3.13.0-27-
I still have this bug in my AMD A8 Trinity APU laptop with
linux-3.15.0-031500rc8-generic x86_64 and updated system. Still,
Catalyst driver is working fine in 3.13 linux kernel. I'm up to try a
solution to use free drivers, but, as I use this machine for production
I'll go back to Catalyst, since s
Changing status temporarily, so this bug report shows up in the
sponsorship queue.
** Changed in: libreoffice-dictionaries (Ubuntu)
Status: Fix Released => In Progress
** Changed in: openoffice.org-hyphenation (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug n
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1326905
Title:
precise has wrong PTRACE_EVENT_SECCOMP value
To manage notifications about this bug go to:
https://bugs.launchpad.n
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
@ginggs, Sorry for the vague report. I was trying to install
playonlinux which was requiring that it remove nvidia-libopencl1-331. I
updated the nvidia packages using your PPA but still saw the message
requiring the removal of nvidia-libopencl1-331 in order to install
playonlinux.
I followed the
** Description changed:
This bug is for tracking the 3.11.0-23.39 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-stable-P
This is happening to me, I just installed Ubuntu 14.04 using the same
/home folders as a previous Debian 7.5 install. I get 9-10
notifications for every message that comes in empathy.
** Attachment added: "Multiple Alerts Per Message Received"
https://bugs.launchpad.net/ubuntu/+source/empathy
** Changed in: duo-unix (Ubuntu Precise)
Status: New => In Progress
** Changed in: duo-unix (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: duo-unix (Ubuntu Precise)
Importance: Undecided => High
** Changed in: duo-unix (Ubuntu Precise)
Assignee: (unassigned) => K
** Changed in: kernel-sru-workflow/security-signoff
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/1326747
Title:
linux-ti-omap4: 3.2.0-1449.68 -proposed trac
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results
This bug was fixed in the package linux-ti-omap4 - 3.2.0-1449.68
---
linux-ti-omap4 (3.2.0-1449.68) precise; urgency=low
* Release Tracking Bug
- LP: #1326747
[ Paolo Pisati ]
* rebased on Ubuntu-3.2.0-64.97
[ Ubuntu: 3.2.0-64.97 ]
* futex-prevent-requeue-pi-on-same-
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Adam Conrad
(adconrad)
** Changed in: kernel-sru-workflow/promote-to-updates
This bug was fixed in the package linux-ti-omap4 - 3.2.0-1449.68
---
linux-ti-omap4 (3.2.0-1449.68) precise; urgency=low
* Release Tracking Bug
- LP: #1326747
[ Paolo Pisati ]
* rebased on Ubuntu-3.2.0-64.97
[ Ubuntu: 3.2.0-64.97 ]
* futex-prevent-requeue-pi-on-same-
*** This bug is a duplicate of bug 1326747 ***
https://bugs.launchpad.net/bugs/1326747
This bug was fixed in the package linux-ti-omap4 - 3.2.0-1449.68
---
linux-ti-omap4 (3.2.0-1449.68) precise; urgency=low
* Release Tracking Bug
- LP: #1326747
[ Paolo Pisati ]
* reb
*** This bug is a duplicate of bug 1326747 ***
https://bugs.launchpad.net/bugs/1326747
This bug was fixed in the package linux-ti-omap4 - 3.2.0-1449.68
---
linux-ti-omap4 (3.2.0-1449.68) precise; urgency=low
* Release Tracking Bug
- LP: #1326747
[ Paolo Pisati ]
* reb
This bug was fixed in the package linux-ti-omap4 - 3.2.0-1449.68
---
linux-ti-omap4 (3.2.0-1449.68) precise; urgency=low
* Release Tracking Bug
- LP: #1326747
[ Paolo Pisati ]
* rebased on Ubuntu-3.2.0-64.97
[ Ubuntu: 3.2.0-64.97 ]
* futex-prevent-requeue-pi-on-same-
This bug was fixed in the package linux-ti-omap4 - 3.2.0-1449.68
---
linux-ti-omap4 (3.2.0-1449.68) precise; urgency=low
* Release Tracking Bug
- LP: #1326747
[ Paolo Pisati ]
* rebased on Ubuntu-3.2.0-64.97
[ Ubuntu: 3.2.0-64.97 ]
* futex-prevent-requeue-pi-on-same-
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: tzdata (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/1326902
Title:
Mor
Upstream discussion: mm.icann.org/pipermail/tz/2014-June/thread.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1326902
Title:
Morocco to Return to Standard Time GMT on June 28
To manage notific
** Description changed:
This bug is for tracking the 3.11.0-23.39~precise1 upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel
501 - 600 of 856 matches
Mail list logo