** Changed in: hwe-next
Status: New = Won't Fix
** Changed in: hwe-next
Importance: Undecided = Medium
--
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/1410309
Title:
[HP
** Also affects: hwe-next
Importance: Undecided
Status: New
--
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/1410309
Title:
[HP EliteBook 725 G2 Notebook PC] mute LED does not
@tai271828,
If you install the latest alsa dkms and the problem disappears, it means
the fix was already in the upstream, but due to the pin quirk framework,
it was not backported to linux-3.13.
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: linux (Ubuntu)
Assignee: Hui Wang (hui.wang) = (unassigned)
** Changed in: linux (Ubuntu)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: 201405-15063
--
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/1410309
Title:
[HP EliteBook 725 G2 Notebook PC] mute LED does not work. it always
keeps the same color
HP ProBook 440 G2 Notebook PC
CID: 201405-15063
could reproduce this issue.
The attachment
201405-15063.apport.linux.log
shows the log.
** Attachment added: 201405-15063.apport.linux.log
@Hui
I could understand the pin quirk framework to make it hard to backport to
linux-3.13.
Is anyway for us to confirm the pin quirk configuration or this is also
caused by the pin quirk framework?
We have more and more systems have this issue
If there is such a way, I may summarize these
According to comment #3, 3.19 cannot reproduce this bug, because Hui already
upstreamed the fix in bug 1329580.
Hui, can you see if the fix can be backported?
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Hui Wang (hui.wang)
--
You received this bug notification because you are a
The fix was already in the upstream, but the fix depends on the pin
quirk framework, it is hard to backport to linux-3.13.
--
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/1410309
Title:
apport information
** Tags added: apport-collected trusty
** Description changed:
The way to reproduce this bug and the basic debug information are at LP:
#1409721
I separate LP: #1409721 to several bug reports because there are different
failed features from the same system.
+ ---
+
HP ProBook 430 G2 Notebook PC
CID: 201405-15209
has the same issue.
Comment 4 to comment 16 are the log files of this machine.
** Tags added: 201405-15209
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
3.19.0-031900rc4-generic #201501112135
was tested, and this bug could NOT be reproduced.
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.19 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
13 matches
Mail list logo