[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-75.83-generic/ms10-34-mcdivittB0-kernel__3.19.0-75.83__2016-11-17_04-26-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
tests ran: 33, failed: 1;
http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/s2lp6g002__4.8.0-28.30__2016-11-17_03-55-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
As per http://kernel.ubuntu.com/sru/sru-report.html
Looks like there is no bug need to be verified this time.
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/regression-testing
Assignee: Canonical Kernel Team (c
tests ran: 18, failed: 1;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/kernel01__4.4.0-49.70__2016-11-17_04-08-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Fix Released
--
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/1640621
Title:
linux-lts-vivid:
--- Comment From bssrika...@in.ibm.com 2016-11-16 23:51 EDT---
I have tested the patch on 4.8.0-28-generic.. now I do not see any errors while
booting guest with VFIO device..
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
tests ran: 5, failed: 3;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/kernel01__4.4.0-49.70__2016-11-17_04-42-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
tests ran: 19, failed: 7;
http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/s2lp6g002__4.8.0-28.30__2016-11-17_04-39-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
tests ran: 33, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/s2lp6g001__4.4.0-49.70__2016-11-17_04-22-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
Public bug reported:
For some new Dell laptops, they are using Matrox graphics cards.
And in order to let Xorg mga driver work. We need to enable CONFIG_DRM_MGAG200.
MGAG200 is disabled by this bug.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1042903
Since Dell's laptops needs this to b
tests ran: 19, failed: 7;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/s2lp6g001__4.4.0-49.70__2016-11-17_05-05-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety
--
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/1591810
Title:
[Feature] SKX: perf uncore PMU support
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1642470
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a commen
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/s2lp6g002__4.8.0-28.30__2016-11-17_05-30-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
tests ran: 141, failed: 28;
http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/s2lp6g002__4.8.0-28.30__2016-11-17_05-02-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
tests ran: 33, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/s2lp3__4.4.0-49.70__2016-11-17_04-20-00/results-index.html
--
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/
tests ran: 141, failed: 28;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/s2lp6g001__4.4.0-49.70__2016-11-17_05-21-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
tests ran: 10, failed: 7;
http://kernel.ubuntu.com/testing/3.19.0-75.83-generic/ms10-34-mcdivittB0-kernel__3.19.0-75.83__2016-11-17_04-49-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/s2lp6g001__4.4.0-49.70__2016-11-17_05-38-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
tests ran: 64, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/s2lp6g002__4.8.0-28.30__2016-11-17_05-34-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
tests ran: 19, failed: 7;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/s2lp3__4.4.0-49.70__2016-11-17_05-40-00/results-index.html
--
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/
tests ran: 64, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/s2lp6g001__4.4.0-49.70__2016-11-17_05-41-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
tests ran: 4, failed: 1;
http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/onibi__4.8.0-28.30__2016-11-17_04-56-00/results-index.html
--
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/
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/s2lp3__4.4.0-49.70__2016-11-17_06-20-00/results-index.html
--
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/
tests ran: 141, failed: 28;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/s2lp3__4.4.0-49.70__2016-11-17_05-54-00/results-index.html
--
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
tests ran: 33, failed: 5;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/kernel01__4.4.0-49.70__2016-11-17_04-57-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
tests ran: 19, failed: 8;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/kernel01__4.4.0-49.70__2016-11-17_06-16-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
tests ran: 30, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-75.83-generic/dwalin__3.19.0-75.83__2016-11-17_05-31-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
tests ran: 64, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/s2lp3__4.4.0-49.70__2016-11-17_06-23-00/results-index.html
--
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/
tests ran: 36, failed: 3;
http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/modoc__4.8.0-28.30__2016-11-17_04-49-00/results-index.html
--
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/
tests ran: 141, failed: 140;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/kernel01__4.4.0-49.70__2016-11-17_06-32-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/kernel01__4.4.0-49.70__2016-11-17_06-42-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
tests ran: 64, failed: 1;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/kernel01__4.4.0-49.70__2016-11-17_06-45-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
> I noticed the comment does not have the download link. It is:
> http://kernel.ubuntu.com/~jsalisbury/lp1626436/mailine-with-two-commits/
Bazinga! Perhaps unexpectedly, this is a GOOD kernel -- boot speed is
comparable with 4.4, there is no high load after booting any more, and
shutdown is fast a
tests ran: 19, failed: 6;
http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/modoc__4.8.0-28.30__2016-11-17_07-15-00/results-index.html
--
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/
@Christopher M. Penalver:
The newest kernel 4.9-rc5-generic gives a kernel panic at boot.
"stack guard page was hit at ..."
What to do now?
--
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/
** Summary changed:
- Need a patched 4.9 kernel to compile nvidia drivers
+ [ 4.9 ] Greeter loop with a nvidia driver
** Description changed:
- As the unstable kernel ppa now has 4.9 kernel, i've installed it on a
- system using a nvidia-370/375 driver, but both fails at compile dkms
- time.
-
Public bug reported:
I noticed a forever-looping test of linuxinfo on i386 this morning. This
test upgrades the kernel to 4.9 in -proposed; as soon as that reboots,
the VM never comes back. nova console-log shows:
[1.581188] Freeing unused kernel memory: 996K (dcc37000 - dcd3)
[1.5825
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1642192
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a commen
** Changed in: hwe-next
Status: New => Triaged
--
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/1642114
Title:
ThinkPad T460 hotkeys stop working in Ubuntu 16.04
Status in HWE Next
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-
xenial' to 'verification-done-xenial'.
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-
xenial' to 'verification-done-xenial'.
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-
xenial' to 'verification-done-xenial'.
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-
xenial' to 'verification-done-xenial'.
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-
xenial' to 'verification-done-xenial'.
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-
xenial' to 'verification-done-xenial'.
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-
xenial' to 'verification-done-xenial'.
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-
xenial' to 'verification-done-xenial'.
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-
xenial' to 'verification-done-xenial'.
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-
xenial' to 'verification-done-xenial'.
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-
xenial' to 'verification-done-xenial'.
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-
xenial' to 'verification-done-xenial'.
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-
xenial' to 'verification-done-xenial'.
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-
xenial' to 'verification-done-xenial'.
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-
xenial' to 'verification-done-xenial'.
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-
xenial' to 'verification-done-xenial'.
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-
xenial' to 'verification-done-xenial'.
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-
xenial' to 'verification-done-xenial'.
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-
xenial' to 'verification-done-xenial'.
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-
xenial' to 'verification-done-xenial'.
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-
xenial' to 'verification-done-xenial'.
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-
yakkety' to 'verification-done-yakkety'.
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-
yakkety' to 'verification-done-yakkety'.
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-
yakkety' to 'verification-done-yakkety'.
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-
xenial' to 'verification-done-xenial'.
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-
yakkety' to 'verification-done-yakkety'.
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-
yakkety' to 'verification-done-yakkety'.
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-
xenial' to 'verification-done-xenial'.
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-
yakkety' to 'verification-done-yakkety'.
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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1642192
Title:
i386 4.9 in -proposed fails to boot in cloud instances
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-
yakkety' to 'verification-done-yakkety'.
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-
yakkety' to 'verification-done-yakkety'.
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-
yakkety' to 'verification-done-yakkety'.
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-
yakkety' to 'verification-done-yakkety'.
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-
yakkety' to 'verification-done-yakkety'.
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-
yakkety' to 'verification-done-yakkety'.
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-
yakkety' to 'verification-done-yakkety'.
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-
yakkety' to 'verification-done-yakkety'.
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-
yakkety' to 'verification-done-yakkety'.
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-
yakkety' to 'verification-done-yakkety'.
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-
yakkety' to 'verification-done-yakkety'.
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-
yakkety' to 'verification-done-yakkety'.
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-
yakkety' to 'verification-done-yakkety'.
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-
yakkety' to 'verification-done-yakkety'.
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-
yakkety' to 'verification-done-yakkety'.
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-
yakkety' to 'verification-done-yakkety'.
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-
yakkety' to 'verification-done-yakkety'.
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-
xenial' to 'verification-done-xenial'.
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-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
Hi
I've worked out I had a problem with micro usb cable. Ive replaced the cables
and it is working fine now. sorry about all the trouble. Thanks Koli
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
Hi, all resolved, it was due to a faulty micro usb cable. Sorry about all the
trouble and thanks.
Koli
--
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/1641075
Title:
connected my android
DimanNe
See https://workingninja.com/installing-asus-bt400-raspberry-pi-raspbian-wheezy
It will show how to get the firmware needed for the broadcom bluetooth device
and see if the issue still exists after the firmware install
--
You received this bug notification because you are a member of Ker
You have been subscribed to a public bug:
== Comment: #0 - Breno Henrique Leitao - 2016-10-20
08:51:24 ==
Hello Canonical,
There are important kernel modules that are required on POWER systems,
and they are currently on the linux-image-extra packages.
So, in this case, every Power system needs
Got the same problem with Logitech RX250 on Xubuntu 16.04.01
--
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/1581088
Title:
Middle mouse (wheel-click) button stopped working after upgrad
Public bug reported:
== Comment: #0 - Breno Henrique Leitao - 2016-10-20
08:51:24 ==
Hello Canonical,
There are important kernel modules that are required on POWER systems,
and they are currently on the linux-image-extra packages.
So, in this case, every Power system needs to install the -extr
Thats kernel 4.4.07.68
--
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/1581088
Title:
Middle mouse (wheel-click) button stopped working after upgrade to
16.04
Status in linux package i
@acarbura yes it does
--
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/1566302
Title:
Ubuntu 16.04: Suspend freezes the system after upgrade to linux image
4.4.0-16
Status in linux pack
1 - 100 of 203 matches
Mail list logo
