Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8
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/1620677
Title:
package
** Tags removed: need-duplicate-check
--
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/1620677
Title:
package linux-image-extra-4.4.0-36-generic (not installed) failed to
Public bug reported:
Just a regular update using Synaptic.
The follow error message appeared at the end of the process:
E: /var/cache/apt/archives/linux-image-
extra-4.4.0-36-generic_4.4.0-36.55_amd64.deb: no se pudieron copiar los
datos extraídos de
Derivative packages from packages here can be worked on, the following tracking
bugs were opened for them:
linux-raspi2 - bug 1620664
linux-snapdragon - bug 1620666
Backport packages from packages here can be worked on, the following tracking
bugs were opened for them:
linux-lts-xenial
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => Confirmed
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: New => Confirmed
--
You received this bug
the machine info : Hp am-005nk with broadcom radio module bcm943142Y
this is a new laptop , I use it for the first time with the last version of
16.04.1 , any other driver work .
the router is a Tenda model W307R with firmware V5.07.46_en and it work fine
with all other devices ( smartphone ,
Public bug reported:
This bug is for tracking the 4.4.0-38.57 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
** Affects:
commit aeaa4a79ff6a5ed912b7362f206cf8576fca538b merged in v4.8-rc1
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Also affects: linux (Ubuntu Yakkety)
Importance: High
Assignee: Joseph Salisbury (jsalisbury)
Status: In Progress
** Changed in:
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
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/1613787
Title:
xfrm: ipsec crash when updating spd
** Description changed:
+ SRU Justification
+
+ Impact: A regression in the xenial kernel causes EPERM to be returned
+ when accessing dfs subfilesystems in a cifs mount.
+
+ Fix: Upstream cherry pick which uses the appropriate credentials for
+ these automounts.
+
+ Regression Potential: The
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
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/1614791
Title:
stress-ng freezes system
Status in linux package in Ubuntu:
*** This bug is a duplicate of bug 1572291 ***
https://bugs.launchpad.net/bugs/1572291
--- Comment on attachment From geral...@de.ibm.com 2016-09-06 10:25
EDT---
Debian kernel package with genwqe-bad-page.patch applied.
** Attachment added:
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/1620648
Title:
Pairing bluetooth 0a12:0001
*** This bug is a duplicate of bug 1572291 ***
https://bugs.launchpad.net/bugs/1572291
--- Comment on attachment From geral...@de.ibm.com 2016-09-06 10:23
EDT---
Fix double free in the genwqe code, resulting from missing pointer clearing in
genwqe_alloc_sync_sgl() error handling.
*** This bug is a duplicate of bug 1572291 ***
https://bugs.launchpad.net/bugs/1572291
--- Comment From geral...@de.ibm.com 2016-09-06 10:21 EDT---
I think I found the bug in the genwqe code:
ddcb_cmd_fixups() -> genwqe_alloc_sync_sgl() (fails in f/lpage, but
sgl->sgl != NULL and
I was able to reproduce the bug and test the fix, and it does work. Will
send for Xenial SRU.
--
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/1612135
Title:
CIFS client: access problems
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
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/1618572
Title:
apt-key add fails in overlayfs
Status in cloud-init:
Confirmed
Please, wait a bit, some people were on holidays.
--
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/1613787
Title:
xfrm: ipsec crash when updating spd thresholds
Status in linux package
Public bug reported:
I see the device in blueman-manager, but pairing fails. I could pair the
dongle with another device. And I could pair the Bose device with
another bluetooth device in Xubuntu 16.04.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-36-generic
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-
vivid' to 'verification-done-vivid'.
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-
vivid' to 'verification-done-vivid'.
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
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
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
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
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
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
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
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-
precise' to 'verification-done-precise'.
If verification is not done by 5 working days
Also worth remembering of:
https://developer.bluetooth.org/TechnologyOverview/pages/le-
security.aspx
--
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/1620636
Title:
Fails to pair with
Might be that the kernels since 3.19 have this included:
http://www.bluez.org/bluetooth-4-2-features-going-to-the-3-19-kernel-
release/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
According to information here
http://unix.stackexchange.com/questions/292189/pairing-bose-qc-35-over-
bluetooth-on-fedora this might be due to not yet supported feature from
BlueZ however this needs a further checking.
--
You received this bug notification because you are a member of Kernel
Public bug reported:
I am unable to pair the Bose QC35 BT headphones with Ubuntu, either
Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez 5.41
from installed from yakkety archive), nor using Ubuntu Touch rc-proposed
build for Turbo #174. I'm trying to pair through the normal
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
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
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
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
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
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
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
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
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
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
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-
trusty' to 'verification-done-trusty'.
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-
trusty' to 'verification-done-trusty'.
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
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-
trusty' to 'verification-done-trusty'.
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-
trusty' to 'verification-done-trusty'.
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
Test kernel at http://people.canonical.com/~rtg/radeon-lp600092/
wget
http://people.canonical.com/~rtg/radeon-lp600092/linux-image-4.4.0-38-generic_4.4.0-38.57_amd64.deb
wget
http://people.canonical.com/~rtg/radeon-lp600092/linux-image-extra-4.4.0-38-generic_4.4.0-38.57_amd64.deb
sudo dpkg -i
Installing Mellanox OFED in Xenial with Kernel 4.4:
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04
Codename: xenial
# uname -a
Linux heatmor 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:01:55 UTC 2016
x86_64
** Changed in: dpkg (Debian)
Status: Unknown => 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/1620525
Title:
sbuild with overlayfs fails in yakkety
Status in dpkg package
** Also affects: linux (Ubuntu Yakkety)
Importance: Medium
Status: Triaged
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Yakkety)
Status: Triaged => Fix Released
** Changed in: linux (Ubuntu Xenial)
See: https://lists.ubuntu.com/archives/kernel-
team/2016-September/079879.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/1618572
Title:
apt-key add fails in overlayfs
Status in
Hello Pedro, or anyone else affected,
Accepted snap-confine into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/snap-
confine/1.0.38-0ubuntu0.16.04.10 in a few hours, and then in the
-proposed repository.
Please help us by testing this new
Please test this kernel and see if it fixes the issue. Thanks!
http://people.canonical.com/~sforshee/lp1612135/
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
This bug was fixed in the package mesa - 11.2.0-1ubuntu2.2
---
mesa (11.2.0-1ubuntu2.2) xenial; urgency=medium
* bxt-add-2x6-variant.diff:
Update BXT pciids. (LP: #1577735)
* add-more-kbl-pciids.diff,
remove-obsolete-kbl-pciids.diff:
Update i965 pciids. (LP: #1600124)
** Changed in: mesa (Ubuntu)
Status: New => 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/1600124
Title:
Adjust KBL PCI-ID's
Status in libdrm package in Ubuntu:
Ok looks like I have found the underlying cause, a bad port of an
upstream stable patch to our Ubuntu code base. I will send out the fix
shortly.
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
**
** This bug is no longer a duplicate of bug 1408963
[Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945
:03:00.0: BSM uCode verification failed at addr ...; wlan0:
deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING),
--
You received this bug
Peter Ullinger, thank you for taking the time to report this bug and helping to
make Ubuntu better. Please execute the following command only once, as it will
automatically gather debugging information, in a terminal:
apport-collect 1408963
When reporting bugs in the future please use apport by
tests ran: 136, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-69.77~14.04.1/onibi__3.19.0-69.77~14.04.1__2016-09-06_11-20-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
** Also affects: linux (Ubuntu Xenial)
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/1619756
Title:
backport support for userspace access of
Same issue here on a Dell Vostro 1700 with Ubuntu 16.04.
Linux briga-laptop 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:01:55
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
[ 3125.120019] iwl3945 :0c:00.0: Queue 4 stuck for 2500 ms.
[ 3125.120026] iwl3945 :0c:00.0: On demand firmware reload
[
*** This bug is a duplicate of bug 1579190 ***
https://bugs.launchpad.net/bugs/1579190
Just moved to 16.04 lts and experiencing a similar problem. "[[C^"
echoes continuously in all VTs, but not Terminal. Another manifestation
is selecting the calendar and revised volume control starts a
tests ran: 136, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-69.77~14.04.1/onibi__3.19.0-69.77~14.04.1__2016-09-06_10-21-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
I've sent an email with what I believe are the required details to
linux-...@vger.kernel.org
I have not received an automated response yet.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Adding a script which can reproduce the problem without the need of
having an active overlayfs-root. Not elegant but does the job.
** Attachment added: "test-ovlmv.sh"
https://bugs.launchpad.net/cloud-init/+bug/1618572/+attachment/4735399/+files/test-ovlmv.sh
--
You received this bug
Similar problem with my Anker SoundBuds AK-A3233011: as the phone
(Aquaris E4.5) connect with the BT device the BT cease to function: I
cannot set BT of or set Airplane Mode; even a reboot will never
complete, I must force a full shutdown.
The device has some glitch with Ubuntu for desktop, also:
eddiewould, the issue you are reporting is an upstream one. Could you
please report this problem following the instructions verbatim at
https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing
list (TO Jiri Kosina and Benjamin Tissoires CC linux-usb)?
Please provide a direct URL to
tests ran: 20, failed: 1;
http://kernel.ubuntu.com/testing/3.19.0-69.77~14.04.1/onibi__3.19.0-69.77~14.04.1__2016-09-06_08-41-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
** Attachment added: "output from usb-devices command under 4.8-rc5 with
gamepad plugged in"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1606873/+attachment/4735383/+files/usb_devices.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is
Please see attachment for usb-devices output.
--
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/1606873
Title:
Logitech Precision Gamepad shows axis activity upon connection
Status in
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1620525
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
eddiewould, could you please plug the gamepad in, execute the following in a
terminal and post the results here uncompressed/untarred:
usb-devices
** Tags removed: bug-exists-upstream
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.8-rc5
** Changed in: linux (Ubuntu)
See debian bug report for details.
--
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/1620525
Title:
sbuild with overlayfs fails in yakkety
Status in dpkg package in Ubuntu:
New
Status
This should be fixed for release, one way or the other.
--
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/1620525
Title:
sbuild with overlayfs fails in yakkety
Status in dpkg package in
101 - 200 of 214 matches
Mail list logo
