*** This bug is a duplicate of bug 1536366 ***
https://bugs.launchpad.net/bugs/1536366
** This bug has been marked a duplicate of bug 1536366
linux-lts-vivid: 3.19.0-48.54~14.04.1 -proposed tracker
--
You received this bug notification because you are a member of Kernel
Packages, which is
*** This bug is a duplicate of bug 1536775 ***
https://bugs.launchpad.net/bugs/1536775
** This bug is no longer a duplicate of bug 1536124
linux: 3.19.0-48.54 -proposed tracker
** This bug has been marked a duplicate of bug 1536775
linux: 3.19.0-49.55 -proposed tracker
--
You received
*** This bug is a duplicate of bug 1536775 ***
https://bugs.launchpad.net/bugs/1536775
** This bug is no longer a duplicate of bug 1536124
linux: 3.19.0-48.54 -proposed tracker
** This bug has been marked a duplicate of bug 1536775
linux: 3.19.0-49.55 -proposed tracker
--
You received
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1536775
Title:
linux: 3.19.0-49.55 -proposed tracker
Status in Kernel SR
*** This bug is a duplicate of bug 1536775 ***
https://bugs.launchpad.net/bugs/1536775
** This bug has been marked a duplicate of bug 1536775
linux: 3.19.0-49.55 -proposed tracker
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
*** This bug is a duplicate of bug 1536775 ***
https://bugs.launchpad.net/bugs/1536775
** This bug is no longer a duplicate of bug 1536124
linux: 3.19.0-48.54 -proposed tracker
** This bug has been marked a duplicate of bug 1536775
linux: 3.19.0-49.55 -proposed tracker
--
You received
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1536867
Title:
linux: 4.2.0-27.32 -proposed tracker
Status in Kernel SRU
*** This bug is a duplicate of bug 1536867 ***
https://bugs.launchpad.net/bugs/1536867
** This bug has been marked a duplicate of bug 1536867
linux: 4.2.0-27.32 -proposed tracker
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
*** This bug is a duplicate of bug 1536867 ***
https://bugs.launchpad.net/bugs/1536867
** This bug is no longer a duplicate of bug 1535795
linux: 4.2.0-26.31 -proposed tracker
** This bug has been marked a duplicate of bug 1536867
linux: 4.2.0-27.32 -proposed tracker
--
You received th
*** This bug is a duplicate of bug 1537013 ***
https://bugs.launchpad.net/bugs/1537013
** This bug is no longer a duplicate of bug 1536366
linux-lts-vivid: 3.19.0-48.54~14.04.1 -proposed tracker
** This bug has been marked a duplicate of bug 1537013
linux-lts-vivid: 3.19.0-49.55~14.04.1
*** This bug is a duplicate of bug 1537013 ***
https://bugs.launchpad.net/bugs/1537013
** This bug has been marked a duplicate of bug 1537013
linux-lts-vivid: 3.19.0-49.55~14.04.1 -proposed tracker
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: linux-lts-vivid (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
https://bugs.launchpad.net/bugs/1537013
Title:
linux-lts-vivid: 3.19.0-49.55~14.04.1 -propo
*** This bug is a duplicate of bug 1537013 ***
https://bugs.launchpad.net/bugs/1537013
** This bug is no longer a duplicate of bug 1536366
linux-lts-vivid: 3.19.0-48.54~14.04.1 -proposed tracker
** This bug has been marked a duplicate of bug 1537013
linux-lts-vivid: 3.19.0-49.55~14.04.1
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from today
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from tod
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from today
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from tod
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from today
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from tod
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from today
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from today
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from today
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from today
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from tod
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from tod
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from today
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from today
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from tod
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
** Changed in: linux-lts-utopic (Ubuntu Trusty)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1570872
Title:
Trusty update to 3.16.7-ckt27
The tracking bug for the Backport packages from packages has been
manually created. The linux-lts-saucy (precise) tracking bug is bug
1323190.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
** Summary changed:
- linux: 3.13.0-28.51 -proposed tracker
+ linux: 3.13.0-29.52 -proposed tracker
** Changed in: kernel-sru-workflow/package-testing
Status: In Progress => New
** Changed in: kernel-sru-workflow/prepare-package
Status: Fix Released => New
** Changed in: kernel-sr
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
saucy' to 'verification-done-saucy'.
If verification is not done by 5 working days from tod
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
I've been able to reproduce this issue in Lucid and I can confirm that
reverting the following commits actually fixes the problem:
d77028ffe1a3d6eb5f57c5e5ea87cbfc4ee05eb1 "net: check net.core.somaxconn sysctl
values"
2dc19ed6338a27a78c7a9d47d311ae4ac5302c83 "sysctl net: Keep tcp_syn_retries
ins
As per a chat on IRC with Adam ("< infinity> henrix: So, consider it
verified enough to release, but not actually fixed until next cycle."),
I'm tagging this bug as verified for trusty
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug no
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
Public bug reported:
This bug is for tracking the 3.11.0-24.41 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-packag
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
** Description changed:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating eit
** Description changed:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating eit
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
** Changed in: linux (Ubuntu)
Status: Fix Released => Fix Committed
** Changed in: linux (Ubuntu Precise)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
** Changed in: linux (Ubuntu)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Trusty)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/13
** Changed in: linux (Ubuntu)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Saucy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/132
** Changed in: linux (Ubuntu)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Saucy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/131
Public bug reported:
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-Prepare-packag
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
** Changed in: linux (Ubuntu)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Lucid)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/132
Public bug reported:
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-Prepare-packa
The following patch from 3.13.11.1 kernel has been dropped:
42d50463defd powerpc/tm: Disable IRQ in tm_recheckpoint (which is
e6b8fd028b584ffca7a7255b8971f254932c9fce in Linus tree)
It was breaking powerpc builds.
--
You received this bug notification because you are a member of Kernel
Packages
Public bug reported:
This bug is for tracking the 3.2.0-64.96 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-package
Patch "dmi: add support for exact DMI matches in addition to substring
matching" (upstream 5017b2851373ee15c7035151853bb1448800cae2) introduces
DMI_EXACT_MATCH macro, which was already defined in -lbm package
(updates/cw-3.11/backport-include/linux/mod_devicetable.h).
The definition of this macro
Public bug reported:
This bug is for tracking the 3.13.0-28.51 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-packag
can be verified that the bug is
actually fixed by this commit.
** Changed in: linux (Ubuntu)
Status: Expired => Triaged
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Luis Henriques (henrix)
** Bug watch added: freedesktop.org Bugzilla #52952
https://bugs.freedeskt
Ok, I've uploaded a test kernel containing the patch mentioned above on
top of Lucid 2.6.32-62.125 kernel. Here's the link to the test kernel:
http://people.canonical.com/~henrix/lp1030792/i386/
I've built 32-bits kernel only, but I can build the 64bits one if
needed. Thanks!
--
You received
Andy, could you please confirm you're running the kernel in -proposed
(2.6.32-62.125)? Because it looks like you're hitting the bug the fix
described above is supposed to fix.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubunt
Kevin, can you please boot with an older kernel, enable the -proposed
pocket (see comment #4) and install the 2.6.32-62.125? It should fix
the issue
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
** Changed in: linux (Ubuntu Lucid)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1335049
Title:
Lucid update to 2.6.32.63 stable release
Status in
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
** Changed in: linux (Ubuntu Saucy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1335084
Title:
Saucy update to 3.11.10.12 stable release
Status in
Moez, looks like you're hitting a bug that hasn't been fixed upstream
yet. I've took a look at the usb_wwan driver and it seems that function
usb_wwan_write() is missing a NULL check to 'this_urb' variable.
I've added this check (see patch attached) and compiled a test kernel .
Could you please g
Thanks a lot for testing. To be honest, I wasn't expecting the patch to
be this verbose... so, I've modified the patch and uploaded v2 of the
test kernel:
http://people.canonical.com/~henrix/lp1308537/v2/
The modified patch is also in this directory.
** Changed in: linux (Ubuntu)
Status:
I believe this should be fixed in recent Trusty kernels by upstream
commit:
commit 47587fc098451c2100dc1fb618855fc2e2d937af
Author: Fernando Luis Vázquez Cao
Date: Wed Feb 26 16:51:24 2014 +0900
HID: hidraw: fix warning destroying hidraw device files after parent
Could you please upgr
Kernel version 3.11.0-15.23 (currently in -updates) should have this bug
fixed. Marking bug as 'fix released'
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
*** This bug is a duplicate of bug 1250605 ***
https://bugs.launchpad.net/bugs/1250605
Seems to be the same as bug #1250605 (same card 10ec:5286). Marking as
duplicate.
** This bug has been marked a duplicate of bug 1250605
10ec:5286 [Clevo W310CZ] Realtek Card Reader not working.
--
Yo
Romano, this has already been backported to the 3.11 kernel (3.11.10.3
extended stable, currently under review) and it will eventually hit the
Saucy kernel during an SRU cycle. Thanks for reporting this bug.
--
You received this bug notification because you are a member of Kernel
Packages, which
es the
old behaviour in net/rose/af_rose.c and should get applied to all the
series that got these CVEs fixed.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Luis Henriques (henrix)
Status: Triaged
** Affects: linux (Ubuntu Lucid)
Importance: Undecided
S
Public bug reported:
This bug is for tracking the 2.6.32-63.126 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
Public bug reported:
This bug is for tracking the 3.11.0-25.42 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-packag
Public bug reported:
This bug is for tracking the 3.13.0-31.55 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-packag
** Summary changed:
- linux: 3.11.0-25.42 -proposed tracker
+ linux: 3.11.0-25.43 -proposed tracker
** Description changed:
- This bug is for tracking the 3.11.0-25.42 upload package. This bug will
+ This bug is for tracking the 3.11.0-25.43 upload package. This bug will
contain status and tes
Bot failed to generate the derivative bug for the lts kernel, so I
manually created it: linux-lts-saucy - bug 1336805
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1336203
Title:
linux:
The bot failed to update status of the bug, so manually updating
'promote-to-proposed' task to 'confirmed'
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Public bug reported:
This bug is for tracking the 3.13.0-32.56 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-packag
Public bug reported:
This bug is for tracking the 3.11.0-26.44 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-packag
Public bug reported:
This bug is for tracking the 3.2.0-67.100 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-packag
Public bug reported:
This bug is for tracking the 2.6.32-64.127 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
*** This bug is a duplicate of bug 1338524 ***
https://bugs.launchpad.net/bugs/1338524
** This bug has been marked a duplicate of bug 1338524
linux: 3.13.0-32.56 -proposed tracker
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
*** This bug is a duplicate of bug 1338556 ***
https://bugs.launchpad.net/bugs/1338556
** This bug has been marked a duplicate of bug 1338556
linux: 3.11.0-26.44 -proposed tracker
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
*** This bug is a duplicate of bug 1338946 ***
https://bugs.launchpad.net/bugs/1338946
** This bug has been marked a duplicate of bug 1338946
linux: 2.6.32-64.127 -proposed tracker
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
The linux-lts-saucy kernel 3.11.0-26.44~precise1 is now available in
-proposed. It contains the following upstream commit, that fixes this
bug:
commit 1fd819ecb90cc9b822cd84d3056ddba315d3340f
Author: Michael S. Tsirkin
Date: Mon Mar 10 19:28:08 2014 +0200
skbuff: skb_segment: orphan frags
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
precise' to 'verification-done-precise'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
401 - 500 of 1649 matches
Mail list logo
