** Description changed:
- In a fresh install of Kubuntu 16.04 (beta2) on a ThinkPad t460s, I can
- connect wireless to the local WLAN, but I don't have an internet
- connection. It is established through LAN though. And without being able
- to reproduce it, it seems that after being connected
Confirmed here.
I did upgrade from xenial to yakkety. the error wasn't showing with xenial
The issue happens with both 4.7, 4.8 from yakkety repo and 4.8.6 (ppa)
tag: 'kernel-bug-exists-upstream'.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Same problem for me, I have a Lenovo X201 Tablet.
Using kernel 4.8.0-040800rc2-generic from [0] fixed the issue
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc2/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
confirmed on 4.9rc3 as well
downgrading xserver-xorg-video-intel to xenial doesn't fix it.
--
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/1621937
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1591704
I'm seeing this behavior on my Thinkpad x260:
[123678.466040] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU
pipe A FIFO underrun
[123742.876516] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
failure on pipe A (start=214815 end=214816) time 150 us, min 1073, max 1079,
Tested with 4.9rc3 and things are working again (sweet and thanks!). I
went back to 4.8.0.11 and it was still an issue there. As well as
checking 4.4.0.34 and zero issues with that. So seems to have happened
when going from 4.4 --> 4.8
** Tags added: kernel-fixed-upstream
--
You received this
Public bug reported:
{forward from James Troup}:
Just to followup to this with a little more information, we have now
reproduced this in the following scenarios:
* Ubuntu kernel 4.4 (i.e. 16.04) and kernel 4.8 (i.e. HWE-Y)
* With and without Bcache involved
* With both XFS and ext4
* With
tests ran: 36, failed: 1;
http://kernel.ubuntu.com/testing/4.4.0-47.68/dwalin__4.4.0-47.68__2016-11-02_07-48-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 141, failed: 28;
http://kernel.ubuntu.com/testing/4.4.0-46.67/kernel01__4.4.0-46.67__2016-11-02_09-03-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-46.67/kernel01__4.4.0-46.67__2016-11-02_09-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.
** 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-ti-omap4 in Ubuntu.
https://bugs.launchpad.net/bugs/1636539
Title:
linux-ti-omap4:
Public bug reported:
Unable to install the suggested amdgpu-pro drivers for AMD Radeon HD 6950.
Also, running in nomodeset, else I get a black screen with cursor.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-generic 4.8.0.26.35
ProcVersionSignature: Ubuntu
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => 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/1638526
Title:
Unable to install AMD Radeon
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/3.2.0-115.157/dwalin__3.2.0-115.157__2016-11-02_11-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.
I cant believe im saying this..
The problem is still apparent in LUbuntu 16.10
lucky the above commands : sudo modprobe ath5k nohwcrypt
sudo sh -c "echo 'options ath5k nohwcrypt' >/etc/modprobe.d/custom-
wireless.conf"
fix it
--
You received this bug notification because you are a member of
tests ran: 36, failed: 4;
http://kernel.ubuntu.com/testing/4.4.0-47.68/modoc__4.4.0-47.68__2016-11-02_10-01-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/1636941
tests ran: 33, failed: 1;
http://kernel.ubuntu.com/testing/4.4.0-47.68/onibi__4.4.0-47.68__2016-11-02_09-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/1636941
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/3.2.0-115.157/dwalin__3.2.0-115.157__2016-11-02_11-01-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi Joseph,
Sorry for the late response, I did not receive the notification for some
reason.
I did test at the time, with all latest 4.5.x, 4.6.x and 4.7.x kernels,
no change.
It would make sense to test with 4.8, or even better, wait for 4.9 and
test it with that?
** Changed in: linux (Ubuntu)
A workaround:
Add the line "net.ipv6.conf.eth0.use_tempaddr = 2" (with "eth0" being
the network inferface) to "/etc/sysctl.d/10-ipv6-privacy.conf"
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
*** This bug is a duplicate of bug 1066375 ***
https://bugs.launchpad.net/bugs/1066375
How is "Error 523 Ray ID: 2fb70607357137aa • 2016-11-02 10:50:09 UTC
Origin is unreachable" helpful?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** 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/1635428
Title:
linux-lts-vivid:
tests ran: 3, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-47.68/modoc__4.4.0-47.68__2016-11-02_08-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/bugs/1636941
tests ran: 64, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-46.67/kernel01__4.4.0-46.67__2016-11-02_09-36-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Flipped the wrong task, revert it.
** Changed in: kernel-sru-workflow/regression-testing
Status: Fix Released => Confirmed
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/verification-testing
As per http://kernel.ubuntu.com/sru/sru-report.html
No verification-needed bugs this time.
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/verification-testing
Assignee: Canonical Kernel Team
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/3.2.0-115.157/dwalin__3.2.0-115.157__2016-11-02_12-01-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Also, using the 32 bit tools package with a 64 bit kernel, should be
fine.
--
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/1619918
Title:
lsattr 32bit does not work on 64bit kernel
Huawei's upstream hio driver version 2.1.0.26 introduces two changes
relative to the current Ubuntu version:
#1. bio_endio() shim macro sets bi_error field {{ but note bug in
implementation! }}
#2. blk_queue_split() call inserted ssd_make_request()
James' initial test results indicate that #2
James, thanks for clarifying that. In that case, all my references to
"hio driver 2.1.0.26" should actually say "the patch set James is
testing", and the two fixes should still likely both be applied to the
Ubuntu hio driver.
--
You received this bug notification because you are a member of
Ming Lei comment #2 says you're the author of this patch to the hio
driver:
+#if (LINUX_VERSION_CODE >= KERNEL_VERSION(4,3,0))
+ blk_queue_split(q, , q->bio_split);
+#endif
+
Can you provide us with a short explanation for the git log, and also
your Signed-off-by line for that patch?
--
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
** Information type changed from Public Security to Private Security
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thanks for testing, Rolf. The error message from the regression appears
to be the same error message you were getting when you originally opened
the bug, is that correct? You are just now getting it with other btrfs
operations, but the original bug is fixed?
--
You received this bug
(Also 2.1.0.26 is not public yet for reasons Huawei are trying to figure
out, 2.1.0.25 is the last publicly available driver.)
--
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/1638700
Sorry - for the avoidance of doubt, neither of these changes are in
2.1.0.26 - 2.1.0.26 doesn't even include your patches. I was testing
2.1.0.26 + our patches + the 2 changes you mention. #1 does come from
Huawei, #2 comes from Ming Lei of Canonical.
--
You received this bug notification
One additional question. Are you only seeing this new regression on
Trusty, or does it also happen on Xenial? Would it be possible for you
to maybe test the Xenial and Yakkety kernels if it is unknown?
--
You received this bug notification because you are a member of Kernel
Packages, which is
[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.
[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.
[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.
[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.
[Expired for bcmwl (Ubuntu) because there has been no activity for 60
days.]
** Changed in: bcmwl (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
tests ran: 18, failed: 0;
http://kernel.ubuntu.com/testing/3.2.0-115.157/onza__3.2.0-115.157__2016-11-03_03-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.
tests ran: 141, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-47.68/modoc__4.4.0-47.68__2016-11-03_04-00-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/1636941
Public bug reported:
with default settings the laptop will immediately resume after sending
to sleep (regardless of by closing the LID or though the menu option
"suspend")
the workaround is disabling the LID ACPI action by running:
echo LID0 >/proc/acpi/wakeup
this will fix the problem.
sure, done: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638788
--
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/1311724
Title:
Macbook Air resumes immidiately after suspend
let me know if I can provide anything else
--
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/1638788
Title:
Macbook Air resumes immidiately after suspend
Status in linux package in
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => 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/1638788
Title:
Macbook Air resumes
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-47.68/modoc__4.4.0-47.68__2016-11-03_05-07-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/1636941
tests ran: 18, failed: 0;
http://kernel.ubuntu.com/testing/3.2.0-115.157/onibi__3.2.0-115.157__2016-11-03_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.
Hi Joe,
I finished the verification of test kernels provided in comment #8 and the
reported heartbeat issue is resolved with the patch included.
Please continue with marking this for proposed & release.
Thank you!
--
You received this bug notification because you are a member of Kernel
** 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
** 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
** 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
+
Sorry, hardware for the #5 is:
128:03:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
and I am open for trying things out ;)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
This problem still happens here with:
linux-firmware:
Installed: 1.161
Candidate: 1.161
linux-image-lowlatency:
Installed: 4.8.0.22.31
Candidate: 4.8.0.22.31
Temporary solving with:
sudo modprobe -r btusb
sudo modprobe btusb
But it happens very very often.
--
You received this bug
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
Public bug reported:
Steps to reproduce the problem
==
1. Plug-in PCIe card OCE14102-UM.
2. Install Ubuntu14.04.2 UEFI mode by PXE.
3. After OS installation finished, use WhiteList tool to check if there has
error messages or not.
Please help clarify below error
** Attachment added: "sosreport.7z"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638753/+attachment/4771466/+files/sosreport.7z
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1638753
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
Side-note about bug in hio driver 2.1.0.26 (#1: bio_endio() shim macro
sets bi_error field). This turns out NOT the cause of this data
corruption bug per James' testing, but should be corrected (both in the
upstream driver and Ubuntu).
The idea behind this change is correct (the macro shim
On Wed, Nov 2, 2016 at 2:08 PM, James Troup
wrote:
> I've confirmed the corruption is gone with the two fixes above on both
4.4 and 4.8.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Download the media installation ISO file at
https://www.ubuntu.com/download/server/arm and burn it to a CD-ROM. Then, put
it into the SATA CD drive to install Ubuntu into Mustang/Merlin boards (XGene
platform), the Installer does not detect the CD-ROM so it report a dialog
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1638779
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
Ketil (ubuntu-rytmisk), apologies for my confusing you. Please perform
the instructions noted in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616214/comments/8
, versus post attachments/comments in this report.
** Attachment removed: "dmesg.txt"
Stephen (scbash), it will help immensely if you filed a new report with the
Ubuntu via a terminal:
ubuntu-bug audio
Please feel free to subscribe me to it.
For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.
--
You received this bug notification because you are
mitico (miticotoby), it will help immensely if you filed a new report with
the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.
--
Garrett Warnell (warnellg-t), it will help immensely if you filed a new report
with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.
Karl-Philipp Richter, no need to file a new report about this issue.
Despite this, 4.8.0-26-generic is based off of upstream kernel version
4.8.0 as per http://people.canonical.com/~kernel/info/kernel-version-
map.html .
Hence, the next step is to fully reverse commit bisect from kernel 4.8.0
to
Stuart Bishop, please provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Wladimir Mutel, please test the latest upstream kernel to confirm your
problem is solved.
--
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/1519034
Title:
Asus X302LA, Elantech touchpad
The apport-collect command does not exist in the installer shell. So, can't run
the command. Trying to save debug log but Ubuntu just support writing to
floppy, web and mount folder.
Attachment contains logfile for installing Ubuntu. It just has information
until right before Ubuntu installer
tests ran: 18, failed: 0;
http://kernel.ubuntu.com/testing/3.2.0-115.157/onibi__3.2.0-115.157__2016-11-03_03-25-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for bcmwl (Ubuntu) because there has been no activity for 60
days.]
** Changed in: bcmwl (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
This is a similar issue to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491654
--
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/1638753
Title:
185175_[F06G]System dmesg and
On Thu, Nov 3, 2016 at 5:42 AM, Kamal Mostafa wrote:
> Ming Lei comment #2 says you're the author of this patch to the hio
> driver:
>
> +#if (LINUX_VERSION_CODE >= KERNEL_VERSION(4,3,0))
> + blk_queue_split(q, , q->bio_split);
> +#endif
> +
>
> Can you provide us with
Try this kernel (which fixes scheduling issues for other people having
trouble on 4.8):
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc3
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** 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/1638278
Title:
4.8 kernel, under heavy load desktop unusable
Status
tests ran: 19, failed: 5;
http://kernel.ubuntu.com/testing/4.4.0-47.68/modoc__4.4.0-47.68__2016-11-02_11-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/bugs/1636941
tests ran: 19, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-47.68/onza__4.4.0-47.68__2016-11-02_11-18-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/1636941
Karl-Philipp Richter, to clarify, it would seem you updated to 16.10,
and are now using the default Ubuntu kernel where this issue is now
fixed. Is this correct? If so, please feel free to mark this report
Status Invalid.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
bostjan, to keep this relevant to upstream, one would want check for,
and test the latest mainline kernel (now 4.9-rc3) as it is released.
Could you please advise?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
> I built a trusty test kernel with commits 33d99113b110 + a220445f9f43. It can
> be downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1634545/trusty
>
> Can you see if it resolves the bug for Trusty?
Test is ok, thank you.
--
You received this bug notification because you are a
js1, to keep this relevant to upstream, one would want check for, and
test the latest mainline kernel (now 4.9-rc3) as it is released.
Could you please advise?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Setting Incomplete for qemu-kvm as well, pending the reporter's response
on whether this is still an issue.
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Test is ok, thank you.
--
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/1633404
Title:
audit: prevent a new auditd to stop an old auditd still alive
Status in linux package in Ubuntu:
I'll take another look at the mainline kernels. I will say one of the
recent kernel apt-get updates (4.4.0-4[35]) seems not to have this
problem as frequently.
On Wed, Nov 2, 2016 at 9:00 AM, Christopher M. Penalver
wrote:
> js1, to keep this relevant to
** Changed in: hwe-next/xenial
Status: Confirmed => 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/1593124
Title:
Add proper palm detection support for MS Precision
You have been subscribed to a public bug:
bash-4.3$ + dpkg --configure nvidia-367
Setting up nvidia-367 (367.57-0ubuntu3) ...
update-initramfs: deferring update (trigger activated)
INFO:Enable nvidia-367
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
DEBUG:Parsing
Expiring
** Changed in: lirc (Ubuntu)
Status: Incomplete => 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/663651
Title:
Streamzap remote control not operating correctly
** Package changed: unity (Ubuntu) => dkms (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1638374
Title:
/usr/sbin/dkms: line 193: syntax error near unexpected token `<'
Status
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-47.68/onza__4.4.0-47.68__2016-11-02_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/bugs/1636941
tests ran: 18, failed: 1;
http://kernel.ubuntu.com/testing/4.4.0-46.67/s2lp6g001__4.4.0-46.67__2016-11-02_05-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.
tests ran: 18, failed: 1;
http://kernel.ubuntu.com/testing/4.4.0-46.67/kernel01__4.4.0-46.67__2016-11-02_05-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.
tests ran: 10, failed: 1;
http://kernel.ubuntu.com/testing/4.4.0-46.67/s2lp6g001__4.4.0-46.67__2016-11-02_06-10-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-47.68/onza__4.4.0-47.68__2016-11-02_05-52-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/1636941
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-47.68/modoc__4.4.0-47.68__2016-11-02_06-01-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/1636941
tests ran: 10, failed: 1;
http://kernel.ubuntu.com/testing/4.4.0-46.67/s2lp3__4.4.0-46.67__2016-11-02_06-10-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/1636941
tests ran: 5, failed: 3;
http://kernel.ubuntu.com/testing/4.4.0-46.67/s2lp6g001__4.4.0-46.67__2016-11-02_06-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.
1 - 100 of 128 matches
Mail list logo