Yes, it would be best to file new bugs, so they can be tracked properly.
Thanks for all the assistance.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubunt
Yes, the original bug can be marked as fixed. What about the other
issues I raised in comment #4? Should I file new bugs for them or can we
recycle this one?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
So it sounds like this bug no longer exists in Saucy? If so, we should
mark this bug as Fix Released.
--
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/1212266
Title:
[LENOVO 4291AK7] hibe
On 08/14/2013 03:40 PM, Joseph Salisbury wrote:
> I'd like to perform a bisect to figure out what commit caused this
> regression. We need to identify the earliest kernel where the issue
> started happening as well as the latest kernel that did not have this
> issue.
>
> Can you test the following
I'd like to perform a bisect to figure out what commit caused this
regression. We need to identify the earliest kernel where the issue
started happening as well as the latest kernel that did not have this
issue.
Can you test the following kernels and report back? We are looking for
the first kerne
5 matches
Mail list logo
