*** This bug is a duplicate of bug 1577748 ***
https://bugs.launchpad.net/bugs/1577748
This is the same bug as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577748, which has
received more attention than this one, so I'm marking this one as a dupe
of the other one.
** This bug has
This is still an issue with 4.2.0-35-generic.
This is a very simple change that just requires a couple of additions to
the device id quirk table:
https://lkml.org/lkml/2015/12/11/165 for Broadwell
https://lkml.org/lkml/2016/1/27/905 for Haswell-ULT
This is how it looks in 4.5:
342 /* Device
I did one more test on Trusty today, running 3.13.0-57-generic kernel.
Installing keyutils (no other hacks needed), makes the keys turn
permanent (which serves as a workaround but leads to problems because of
the cache getting full).
Without keyutils, the keys do NOT get renewed as they should.
To clarify the above comment:
Precise running 3.2 kernel: not affected
Precise running 3.13 lts kernel: affected
Trusty running 3.13 kernel: not affected
In the Precise + lts kernel case, it's possible to hack around the
userland tools to make the keys become permanent (keyutils +
libkeyutils1 +
This bug affects Precise, but it's not marked so. Back in June, I had
mentioned that it was possible to make the keys permanent by using the
trusty versions of keyutils + libkeyutils1 + libnfsidmap2. This is now
not possible anymore with the latest kernel versions available on
Precise.
I
I'm running into this problem (keys don't get automatically renewed and
are expired after 10 minutes) on a precise server running the trusty lts
kernel.
I've just rebooted into the latest version (3.13.0.53.46), and the
problem is still present.
#33 mentions that installing keyutils fixes this.
You need to install the image-extra package.
--
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/1221995
Title:
0a12:0001 Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesn't work
with
Unfortunately upstream didn't deliver on their promise of backporting
the fix to 3.13. It's applied on 3.14 onwards
(http://article.gmane.org/gmane.linux.kernel/1611767), but Trusty is
still broken. Can we get either the patch version included here, or a
backport of the version included in 3.14
I really don't understand why this need of asking users to file
duplicate bugs. This is a bug with a specific piece of hardware. Any
user that has this piece of hardware is affected. Why do you want one
bug per user? This makes it much harder to track the progress on the
issue... For example, on
Adding more information from other sources.
The bugzilla bug (https://bugzilla.kernel.org/show_bug.cgi?id=60824)
says that it's working since 3.14.1
This is the commit where it's fixed:
Repeating information from the original bug:
The bugzilla bug (https://bugzilla.kernel.org/show_bug.cgi?id=60824)
says that it's working since 3.14.1
This is the commit where it's fixed:
My link was to specific file in the commit, but from it you can get to the
whole patch. Link to the full patch:
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/patch/?id=f9f462faa02777f497eb25255683a94e0c054de6
--
You received this bug notification because you are a member
Trusty is still affected by this bug. Please apply the patch to the
trusty kernel.
--
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/1221995
Title:
Bluetooth Dongle (Cambridge Silicon
I find it weird that this was marked as invalid when quite a bunch of
people reported that they were still seeing it and that it was still
present in mainline kernel. I'm moving it to Confirmed.
Also, it's likely that this is the same as:
This bug is a feature request, and therefore requires no apport traces.
Furthermore, it also includes a link to a patch. What's being asked
here is to apply that patch, no extra information should be needed.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Description
Hi,
I verified in precise for:
linux-image-3.2.0-56-generic
linux-image-3.5.0-43-generic
linux-image-3.8.0-33-generic
Works correctly in all of them.
--
Regards,
Marga
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Public bug reported:
The bug is described in detail in this mail:
https://lkml.org/lkml/2013/7/25/205
This bug affects any readline enabled program, like bash or psql. A
large paste is any paste of more than 4kb of data (4kb is the size of
the kernel buffer for reading from the console).
As
17 matches
Mail list logo
