[Kernel-packages] [Bug 1730505] Re: [MacBookPro12, 1] SD Card Reader not working

2017-11-07 Thread Jim Hodapp
*** This bug is a duplicate of bug 1531653 ***
https://bugs.launchpad.net/bugs/1531653

I am away from home for a couple of months and don't have access to an
sdcard to test with at the moment. Is there anything that's still useful
for my to try with this latest kernel, even just if the kernel detects
the reader without a card in it since this doesn't currently work at
all.

-- 
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/1730505

Title:
  [MacBookPro12,1] SD Card Reader not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Related bug to this one: bug #1531653

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-98-generic 4.4.0-98.121
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jhodapp4369 F pulseaudio
   /dev/snd/pcmC1D0p:   jhodapp4369 F...m pulseaudio
   /dev/snd/controlC1:  jhodapp4369 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov  6 15:23:15 2017
  HibernationDevice: RESUME=UUID=a9029808-b026-4ab1-808a-d0058e8f30b6
  InstallationDate: Installed on 2015-08-02 (827 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 003: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 011: ID 05ac:12a8 Apple, Inc. iPhone5/5C/5S/6
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=8d74649d-74b5-4276-a1fe-275341c3578c ro libata.force=noncq quiet 
splash acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.157.13
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B07.1506051617
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B07.1506051617:bd06/05/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730505/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1730505] Re: [MacBookPro12, 1] SD Card Reader not working

2017-11-06 Thread Jim Hodapp
*** This bug is a duplicate of bug 1531653 ***
https://bugs.launchpad.net/bugs/1531653

Thanks Christopher, sounds good.

-- 
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/1730505

Title:
  [MacBookPro12,1] SD Card Reader not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Related bug to this one: bug #1531653

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-98-generic 4.4.0-98.121
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jhodapp4369 F pulseaudio
   /dev/snd/pcmC1D0p:   jhodapp4369 F...m pulseaudio
   /dev/snd/controlC1:  jhodapp4369 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov  6 15:23:15 2017
  HibernationDevice: RESUME=UUID=a9029808-b026-4ab1-808a-d0058e8f30b6
  InstallationDate: Installed on 2015-08-02 (827 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 003: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 011: ID 05ac:12a8 Apple, Inc. iPhone5/5C/5S/6
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=8d74649d-74b5-4276-a1fe-275341c3578c ro libata.force=noncq quiet 
splash acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.157.13
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B07.1506051617
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B07.1506051617:bd06/05/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730505/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1531653] Re: Macbook Pro Retina 11, 1 SD Card Reader Doesn't Work

2017-11-06 Thread Jim Hodapp
@Christopher: created bug #1730505

-- 
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/1531653

Title:
  Macbook Pro Retina 11,1 SD Card Reader Doesn't Work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Macbook Pro (MBP) Retina 11,1 with an SD card reader that
  will not work.

  The SD card reader:

  * has device code 05ac:8406
  * does work in OS X.
  * does not work in SystemRescueCD running kernel 3.14.56-std461-amd64
  - I have a friend with an identical Macbook Pro and his SD card reader 
does work in SystemRescueCD
  * Does not show up in lsusb
  * Does not display any messages in dmesg when an SD card is inserted
  * Device 05ac:8406 does not show up in dmesg
  * Does not work in kernel 4.2.0-22.27~14.04.1.  All issues reported here seem 
to be the same regardless if I use 3.13 or 4.2.
  * Uses the following drivers on my friends MBP: sd, usb-storage, usb, xhci_hcd

  The last point made me look closer at the xhci_hcd logs:

  rsyring@loftex:~$ dmesg | grep xhci_hcd
  [2.681478] xhci_hcd :00:14.0: xHCI Host Controller
  [2.681498] xhci_hcd :00:14.0: new USB bus registered, assigned bus 
number 1
  [2.681589] xhci_hcd :00:14.0: cache line size of 256 is not supported
  [2.681607] xhci_hcd :00:14.0: irq 63 for MSI/MSI-X
  [2.681755] usb usb1: Manufacturer: Linux 3.13.0-57-generic xhci_hcd
  [2.682098] xhci_hcd :00:14.0: xHCI Host Controller
  [2.682115] xhci_hcd :00:14.0: new USB bus registered, assigned bus 
number 2
  [2.682219] usb usb2: Manufacturer: Linux 3.13.0-57-generic xhci_hcd
  [3.980423] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
  [9.352422] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   14.560476] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   20.549170] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   25.757227] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   26.129482] usb 1-1: new high-speed USB device number 2 using xhci_hcd
  [   26.321707] usb 1-3: new full-speed USB device number 3 using xhci_hcd
  [   26.505802] usb 1-5: new full-speed USB device number 4 using xhci_hcd
  [   26.603224] usb 2-1.1: new SuperSpeed USB device number 6 using xhci_hcd
  [   26.754245] usb 1-1.2: new low-speed USB device number 5 using xhci_hcd
  [   26.954315] usb 1-1.4: new low-speed USB device number 6 using xhci_hcd
  [   27.050323] usb 1-3.1: new full-speed USB device number 7 using xhci_hcd
  [   27.142383] usb 1-3.2: new full-speed USB device number 8 using xhci_hcd
  [   27.234476] usb 1-3.3: new full-speed USB device number 9 using xhci_hcd
  [   81.685139] usb 1-1.4: new low-speed USB device number 10 using xhci_hcd

  The "Timeout while waiting" messages are suspicious to me.  dmesg on
  my friend's MBP  does not show those messages.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-57-generic 3.13.0-57.95
  ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
  Uname: Linux 3.13.0-57-generic x86_64
  NonfreeKernelModules: wl zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rsyring5051 F pulseaudio
   /dev/snd/controlC0:  rsyring5051 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Jan  6 17:57:28 2016
  HibernationDevice: RESUME=UUID=8b8a41c8-2030-4f92-b7d6-1143a081ec85
  InstallationDate: Installed on 2014-02-15 (690 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  MachineType: Apple Inc. MacBookPro11,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \vmlinuz-3.13.0-57-generic.efi.signed root=ZFS=/ROOT ro 
libata.force=noncq 
cryptopts=target=cryptdev,source=/dev/disk/by-uuid/6993c5ec-7308-420d-bbe2-1ed18c15e2bc,discard
 boot=zfs initrd=\initrd.img-3.13.0-57-generic
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-57-generic N/A
   linux-backports-modules-3.13.0-57-generic  N/A
   linux-firmware 1.127.19
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-07-21 (534 days ago)
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B16.1509081438
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B16.1509081438:bd09/08/2015:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.name: MacBookPro11,1
  

[Kernel-packages] [Bug 1730505] [NEW] [MacBookPro12, 1] SD Card Reader not working

2017-11-06 Thread Jim Hodapp
*** This bug is a duplicate of bug 1531653 ***
https://bugs.launchpad.net/bugs/1531653

Public bug reported:

Related bug to this one: bug #1531653

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-98-generic 4.4.0-98.121
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jhodapp4369 F pulseaudio
 /dev/snd/pcmC1D0p:   jhodapp4369 F...m pulseaudio
 /dev/snd/controlC1:  jhodapp4369 F pulseaudio
CurrentDesktop: Unity
Date: Mon Nov  6 15:23:15 2017
HibernationDevice: RESUME=UUID=a9029808-b026-4ab1-808a-d0058e8f30b6
InstallationDate: Installed on 2015-08-02 (827 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 05ac:0273 Apple, Inc. 
 Bus 001 Device 003: ID 05ac:8290 Apple, Inc. 
 Bus 001 Device 011: ID 05ac:12a8 Apple, Inc. iPhone5/5C/5S/6
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Apple Inc. MacBookPro12,1
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=8d74649d-74b5-4276-a1fe-275341c3578c ro libata.force=noncq quiet 
splash acpi_backlight=vendor vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-98-generic N/A
 linux-backports-modules-4.4.0-98-generic  N/A
 linux-firmware1.157.13
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/05/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP121.88Z.0167.B07.1506051617
dmi.board.name: Mac-E43C1C25D4880AD6
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro12,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-E43C1C25D4880AD6
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B07.1506051617:bd06/05/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
dmi.product.name: MacBookPro12,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug 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/1730505

Title:
  [MacBookPro12,1] SD Card Reader not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Related bug to this one: bug #1531653

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-98-generic 4.4.0-98.121
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jhodapp4369 F pulseaudio
   /dev/snd/pcmC1D0p:   jhodapp4369 F...m pulseaudio
   /dev/snd/controlC1:  jhodapp4369 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov  6 15:23:15 2017
  HibernationDevice: RESUME=UUID=a9029808-b026-4ab1-808a-d0058e8f30b6
  InstallationDate: Installed on 2015-08-02 (827 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 003: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 011: ID 05ac:12a8 Apple, Inc. iPhone5/5C/5S/6
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=8d74649d-74b5-4276-a1fe-275341c3578c ro libata.force=noncq quiet 
splash acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.157.13
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B07.1506051617
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B07.1506051617:bd06/05/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1531653] Re: Macbook Pro Retina 11, 1 SD Card Reader Doesn't Work

2017-11-03 Thread Jim Hodapp
I'm able to help test if that's helpful to anybody. I've got a mid-2015
MB Pro but I don't have the latest OS X installed (one off of latest)
and I rarely ever boot into 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/1531653

Title:
  Macbook Pro Retina 11,1 SD Card Reader Doesn't Work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Macbook Pro (MBP) Retina 11,1 with an SD card reader that
  will not work.

  The SD card reader:

  * has device code 05ac:8406
  * does work in OS X.
  * does not work in SystemRescueCD running kernel 3.14.56-std461-amd64
  - I have a friend with an identical Macbook Pro and his SD card reader 
does work in SystemRescueCD
  * Does not show up in lsusb
  * Does not display any messages in dmesg when an SD card is inserted
  * Device 05ac:8406 does not show up in dmesg
  * Does not work in kernel 4.2.0-22.27~14.04.1.  All issues reported here seem 
to be the same regardless if I use 3.13 or 4.2.
  * Uses the following drivers on my friends MBP: sd, usb-storage, usb, xhci_hcd

  The last point made me look closer at the xhci_hcd logs:

  rsyring@loftex:~$ dmesg | grep xhci_hcd
  [2.681478] xhci_hcd :00:14.0: xHCI Host Controller
  [2.681498] xhci_hcd :00:14.0: new USB bus registered, assigned bus 
number 1
  [2.681589] xhci_hcd :00:14.0: cache line size of 256 is not supported
  [2.681607] xhci_hcd :00:14.0: irq 63 for MSI/MSI-X
  [2.681755] usb usb1: Manufacturer: Linux 3.13.0-57-generic xhci_hcd
  [2.682098] xhci_hcd :00:14.0: xHCI Host Controller
  [2.682115] xhci_hcd :00:14.0: new USB bus registered, assigned bus 
number 2
  [2.682219] usb usb2: Manufacturer: Linux 3.13.0-57-generic xhci_hcd
  [3.980423] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
  [9.352422] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   14.560476] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   20.549170] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   25.757227] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   26.129482] usb 1-1: new high-speed USB device number 2 using xhci_hcd
  [   26.321707] usb 1-3: new full-speed USB device number 3 using xhci_hcd
  [   26.505802] usb 1-5: new full-speed USB device number 4 using xhci_hcd
  [   26.603224] usb 2-1.1: new SuperSpeed USB device number 6 using xhci_hcd
  [   26.754245] usb 1-1.2: new low-speed USB device number 5 using xhci_hcd
  [   26.954315] usb 1-1.4: new low-speed USB device number 6 using xhci_hcd
  [   27.050323] usb 1-3.1: new full-speed USB device number 7 using xhci_hcd
  [   27.142383] usb 1-3.2: new full-speed USB device number 8 using xhci_hcd
  [   27.234476] usb 1-3.3: new full-speed USB device number 9 using xhci_hcd
  [   81.685139] usb 1-1.4: new low-speed USB device number 10 using xhci_hcd

  The "Timeout while waiting" messages are suspicious to me.  dmesg on
  my friend's MBP  does not show those messages.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-57-generic 3.13.0-57.95
  ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
  Uname: Linux 3.13.0-57-generic x86_64
  NonfreeKernelModules: wl zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rsyring5051 F pulseaudio
   /dev/snd/controlC0:  rsyring5051 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Jan  6 17:57:28 2016
  HibernationDevice: RESUME=UUID=8b8a41c8-2030-4f92-b7d6-1143a081ec85
  InstallationDate: Installed on 2014-02-15 (690 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  MachineType: Apple Inc. MacBookPro11,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \vmlinuz-3.13.0-57-generic.efi.signed root=ZFS=/ROOT ro 
libata.force=noncq 
cryptopts=target=cryptdev,source=/dev/disk/by-uuid/6993c5ec-7308-420d-bbe2-1ed18c15e2bc,discard
 boot=zfs initrd=\initrd.img-3.13.0-57-generic
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-57-generic N/A
   linux-backports-modules-3.13.0-57-generic  N/A
   linux-firmware 1.127.19
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-07-21 (534 days ago)
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B16.1509081438
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 

[Kernel-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones

2017-10-25 Thread Jim Hodapp
Isak: yeah same here, that usually has to do with bluez still querying
for other devices in the background and sucking up all of the channel
bandwidth. It really needs someone to investigate if we can get bluez to
not consume so much bandwidth, or make the query period more context
sensitive such that it only happens when the BT settings UI is shown or
explicitly told to query for new devices on the command line.

-- 
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 Bose QC35 headphones

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  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
  bluetooth control panel brought up through the bluetooth indicator.

  I've attached some logs that show it failing to pair. If I can provide
  anymore useful information about the headphones, please let me know.

  Syslog with bluetoothd debugging enabled:
  http://pastebin.ubuntu.com/23141394/

  btmon output:
  http://pastebin.ubuntu.com/23141446/

  bluetoothctl output:
  http://pastebin.ubuntu.com/23141510/

  With Linux kernel 4.8.0 and bluez 4.52:
  ---

  bluetoothctl: http://pastebin.ubuntu.com/23256457/
  btmon: http://pastebin.ubuntu.com/23256471/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones

2017-09-25 Thread Jim Hodapp
Yes I've experienced the same kind of jitter. The volume level is pretty
decent for me, but not the streaming performance. I basically need to be
doing nothing else on my laptop for it to stream without jittering.

-- 
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 Bose QC35 headphones

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  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
  bluetooth control panel brought up through the bluetooth indicator.

  I've attached some logs that show it failing to pair. If I can provide
  anymore useful information about the headphones, please let me know.

  Syslog with bluetoothd debugging enabled:
  http://pastebin.ubuntu.com/23141394/

  btmon output:
  http://pastebin.ubuntu.com/23141446/

  bluetoothctl output:
  http://pastebin.ubuntu.com/23141510/

  With Linux kernel 4.8.0 and bluez 4.52:
  ---

  bluetoothctl: http://pastebin.ubuntu.com/23256457/
  btmon: http://pastebin.ubuntu.com/23256471/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1712024] Re: igb: Support using Broadcom 54616 as PHY

2017-08-24 Thread Jim Hodapp
SRU justification: The igb driver fails to work when using Broadcom
54616 as PHY, thus we need this patch to enable MAAS so that it can use
the management interface on switch platforms that contain this Broadcom
chipset.

-- 
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/1712024

Title:
  igb: Support using Broadcom 54616 as PHY

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  The igb driver fails to work when using Broadcom 54616 as PHY.

  00:14.0 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)
  00:14.1 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)
  00:14.2 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)

  $ dmesg | grep igb
  [3.472655] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.3.0-k
  [3.480475] igb: Copyright (c) 2007-2014 Intel Corporation.
  [3.584768] igb: probe of :00:14.0 failed with error -2
  [3.965971] igb :00:14.1: added PHC on eth0
  [3.971066] igb :00:14.1: Intel(R) Gigabit Ethernet Network Connection
  [4.010706] igb :00:14.1: eth0: PBA No: 002000-000
  [4.016458] igb :00:14.1: Using MSI-X interrupts. 4 rx queue(s), 4 tx 
queue(s)
  [4.399662] igb :00:14.2: added PHC on eth1
  [4.404738] igb :00:14.2: Intel(R) Gigabit Ethernet Network Connection
  [4.412489] igb :00:14.2: eth1: PBA No: 002000-000
  [4.418235] igb :00:14.2: Using MSI-X interrupts. 4 rx queue(s), 4 tx 
queue(s)
  [4.428206] igb :00:14.1 enp0s20f1: renamed from eth0
  [4.465744] igb :00:14.2 enp0s20f2: renamed from eth1

  A patch can be found in OpenNetworkLinux:
  
https://github.com/opencomputeproject/OpenNetworkLinux/blob/master/packages/base/any/kernels/3.18.25/patches
  /driver-support-intel-igb-bcm54616-phy.patch

  It should be safe to include this in an SRU release since the new code
  is only functioning when certain ID is found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1712024/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1398193] Re: The bluetooth headset cannot control media playback

2017-02-02 Thread Jim Hodapp
** Summary changed:

- The bluetooth headset can not control the media playback
+ The bluetooth headset cannot control media playback

-- 
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/1398193

Title:
  The bluetooth headset cannot control media playback

Status in Canonical System Image:
  Triaged
Status in bluez package in Ubuntu:
  Triaged
Status in media-hub package in Ubuntu:
  Invalid
Status in media-hub package in Ubuntu RTM:
  Invalid

Bug description:
  [Preconditions]
  1.The DUT pair with bluetooth headset

  [Procedures]
  1.Play a video using the mediaplayer-app
  2.Play/pause video by bluetooth headset

  [Expect results]
  The bluetooth headset can play/pause video
  [Actual results]
  The bluetooth headset can not control the video playback.

  [Reproduce]
  Always

  Same for audio playback

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398193/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1398193] Re: The bluetooth headset can not control the media playback

2017-01-24 Thread Jim Hodapp
** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => Jim Hodapp (jhodapp)

-- 
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/1398193

Title:
  The bluetooth headset can not control the media playback

Status in Canonical System Image:
  Triaged
Status in bluez package in Ubuntu:
  Triaged
Status in media-hub package in Ubuntu:
  Invalid
Status in media-hub package in Ubuntu RTM:
  Invalid

Bug description:
  [Preconditions]
  1.The DUT pair with bluetooth headset

  [Procedures]
  1.Play a video using the mediaplayer-app
  2.Play/pause video by bluetooth headset

  [Expect results]
  The bluetooth headset can play/pause video
  [Actual results]
  The bluetooth headset can not control the video playback.

  [Reproduce]
  Always

  Same for audio playback

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398193/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones

2017-01-20 Thread Jim Hodapp
@Wesley: I would also add, did you know that you can place this
headphone in BT pairing mode by first switching it on and then holding
that same switch as far away from the off position as possible for a
second or two? You don't need the Bose Connect app to put it in pairing
mode then.

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => Jim Hodapp (jhodapp)

-- 
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 Bose QC35 headphones

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  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
  bluetooth control panel brought up through the bluetooth indicator.

  I've attached some logs that show it failing to pair. If I can provide
  anymore useful information about the headphones, please let me know.

  Syslog with bluetoothd debugging enabled:
  http://pastebin.ubuntu.com/23141394/

  btmon output:
  http://pastebin.ubuntu.com/23141446/

  bluetoothctl output:
  http://pastebin.ubuntu.com/23141510/

  With Linux kernel 4.8.0 and bluez 4.52:
  ---

  bluetoothctl: http://pastebin.ubuntu.com/23256457/
  btmon: http://pastebin.ubuntu.com/23256471/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones

2016-12-13 Thread Jim Hodapp
@Robin: yeah after a reboot or after simply turning the headphones on
and off again, pairing doesn't work. I need to use the Bose Connect app
on my phone to delete the remembered pairing, delete it from Ubuntu, and
add a new pairing from the app and pair from Ubuntu. Only then does it
work.

-- 
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 Bose QC35 headphones

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  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
  bluetooth control panel brought up through the bluetooth indicator.

  I've attached some logs that show it failing to pair. If I can provide
  anymore useful information about the headphones, please let me know.

  Syslog with bluetoothd debugging enabled:
  http://pastebin.ubuntu.com/23141394/

  btmon output:
  http://pastebin.ubuntu.com/23141446/

  bluetoothctl output:
  http://pastebin.ubuntu.com/23141510/

  With Linux kernel 4.8.0 and bluez 4.52:
  ---

  bluetoothctl: http://pastebin.ubuntu.com/23256457/
  btmon: http://pastebin.ubuntu.com/23256471/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones

2016-11-28 Thread Jim Hodapp
@Robin: Yeah I've been able to get mine working as well. Were you trying
with Ubuntu desktop or on Ubuntu Touch? The choppiness seems to be bluez
doing other device scans. So on Touch, if you make sure that system
settings is in the background, it should remain nearly chop-free. On the
desktop, it stopped scanning if I closed system settings and then got a
lot better quality.

-- 
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 Bose QC35 headphones

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  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
  bluetooth control panel brought up through the bluetooth indicator.

  I've attached some logs that show it failing to pair. If I can provide
  anymore useful information about the headphones, please let me know.

  Syslog with bluetoothd debugging enabled:
  http://pastebin.ubuntu.com/23141394/

  btmon output:
  http://pastebin.ubuntu.com/23141446/

  bluetoothctl output:
  http://pastebin.ubuntu.com/23141510/

  With Linux kernel 4.8.0 and bluez 4.52:
  ---

  bluetoothctl: http://pastebin.ubuntu.com/23256457/
  btmon: http://pastebin.ubuntu.com/23256471/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones

2016-09-30 Thread Jim Hodapp
** Description changed:

  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 bluetooth
  control panel brought up through the bluetooth indicator.
  
  I've attached some logs that show it failing to pair. If I can provide
  anymore useful information about the headphones, please let me know.
  
  Syslog with bluetoothd debugging enabled:
  http://pastebin.ubuntu.com/23141394/
  
  btmon output:
  http://pastebin.ubuntu.com/23141446/
  
  bluetoothctl output:
  http://pastebin.ubuntu.com/23141510/
+ 
+ With Linux kernel 4.8.0 and bluez 4.52:
+ ---
+ http://pastebin.ubuntu.com/23256457/

** Description changed:

  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 bluetooth
  control panel brought up through the bluetooth indicator.
  
  I've attached some logs that show it failing to pair. If I can provide
  anymore useful information about the headphones, please let me know.
  
  Syslog with bluetoothd debugging enabled:
  http://pastebin.ubuntu.com/23141394/
  
  btmon output:
  http://pastebin.ubuntu.com/23141446/
  
  bluetoothctl output:
  http://pastebin.ubuntu.com/23141510/
  
  With Linux kernel 4.8.0 and bluez 4.52:
  ---
- http://pastebin.ubuntu.com/23256457/
+ 
+ bluetoothctl: http://pastebin.ubuntu.com/23256457/
+ btmon: http://pastebin.ubuntu.com/23256471/

** Changed in: bluez (Ubuntu)
 Assignee: (unassigned) => Konrad Zapałowicz (kzapalowicz)

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => John McAleely (john.mcaleely)

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Changed in: bluez (Ubuntu)
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
   Status: New => Triaged

** Changed in: bluez (Ubuntu)
   Status: New => In Progress

** Changed in: canonical-devices-system-image
   Status: Triaged => In Progress

-- 
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 Bose QC35 headphones

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  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
  bluetooth control panel brought up through the bluetooth indicator.

  I've attached some logs that show it failing to pair. If I can provide
  anymore useful information about the headphones, please let me know.

  Syslog with bluetoothd debugging enabled:
  http://pastebin.ubuntu.com/23141394/

  btmon output:
  http://pastebin.ubuntu.com/23141446/

  bluetoothctl output:
  http://pastebin.ubuntu.com/23141510/

  With Linux kernel 4.8.0 and bluez 4.52:
  ---

  bluetoothctl: http://pastebin.ubuntu.com/23256457/
  btmon: http://pastebin.ubuntu.com/23256471/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1620636] [NEW] Fails to pair with Bose QC35 headphones

2016-09-06 Thread Jim Hodapp
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 bluetooth
control panel brought up through the bluetooth indicator.

I've attached some logs that show it failing to pair. If I can provide
anymore useful information about the headphones, please let me know.

Syslog with bluetoothd debugging enabled:
http://pastebin.ubuntu.com/23141394/

btmon output:
http://pastebin.ubuntu.com/23141446/

bluetoothctl output:
http://pastebin.ubuntu.com/23141510/

** Affects: bluez (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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 Bose QC35 headphones

Status in bluez package in Ubuntu:
  New

Bug description:
  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
  bluetooth control panel brought up through the bluetooth indicator.

  I've attached some logs that show it failing to pair. If I can provide
  anymore useful information about the headphones, please let me know.

  Syslog with bluetoothd debugging enabled:
  http://pastebin.ubuntu.com/23141394/

  btmon output:
  http://pastebin.ubuntu.com/23141446/

  bluetoothctl output:
  http://pastebin.ubuntu.com/23141510/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1620636/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1398193] Re: The bluetooth headset can not control the media playback

2016-08-01 Thread Jim Hodapp
** Changed in: bluez (Ubuntu)
   Status: In Progress => Triaged

** Changed in: canonical-devices-system-image
   Status: Confirmed => Triaged

-- 
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/1398193

Title:
  The bluetooth headset can not control the media playback

Status in Canonical System Image:
  Triaged
Status in bluez package in Ubuntu:
  Triaged
Status in media-hub package in Ubuntu:
  Invalid
Status in media-hub package in Ubuntu RTM:
  Invalid

Bug description:
  [Preconditions]
  1.The DUT pair with bluetooth headset

  [Procedures]
  1.Play a video using the mediaplayer-app
  2.Play/pause video by bluetooth headset

  [Expect results]
  The bluetooth headset can play/pause video
  [Actual results]
  The bluetooth headset can not control the video playback.

  [Reproduce]
  Always

  Same for audio playback

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398193/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1519681] Re: Some media keys on keyboards do not work as expected

2016-05-10 Thread Jim Hodapp
** Changed in: qtubuntu-media (Ubuntu)
   Status: Confirmed => Invalid

-- 
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/1519681

Title:
  Some media keys on keyboards do not work as expected

Status in The Avila project:
  Confirmed
Status in Canonical System Image:
  Confirmed
Status in Canonical Pocket Desktop:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in qtubuntu-media package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  $ system-image-cli -i
  current build number: 75
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu-pd
  last update: 2015-11-24 05:39:02
  version version: 75
  version ubuntu: 20151124
  version device: 20150911
  version custom: 20150929-2-vivid

  Steps to reproduce:
  1. Windowed mode is enabled with BT mouse/keyboard connected
  2. Launch music app to play all of a playlist
  3. Press Pause/Play, Fast forward/Rewind keys on BT keyboard

  Actual results:
  Press media keys(Pause/Play, Fast forward/Rewind) on BT keyboard has no 
control for playback 
  currently only Volume Up/ Down and Mute/Unmute media keys work

  BT keyboard type: Logitech K480 and Rapoo E6350

To manage notifications about this bug go to:
https://bugs.launchpad.net/avila/+bug/1519681/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5

2016-03-29 Thread Jim Hodapp
I'm experiencing some similar difficulties with my 2016 VW GTI. I
haven't had a chance to gather any useful logs for it yet and need to
play around some more to see more precisely how it's failing and the
steps to reproduce.

-- 
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/1500242

Title:
  Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected
  with BQ Aquaris 4.5

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old 
one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi 
car kit (A3 2012 model)

  1. Put Jabra BT250 into receiving mode
  2. Phone searches automatically every 15 - 30 seconds for a new blue tooth 
device
  3. Phone finds Jabra BT250 and asks for pairing code
  4. Enter code into phone
  5. Jabra BT250 automatically exits the pairing mode (which is a sign that 
pairing should have worked)
  6. Phone looses connection to Jabra BT250
  7. Manual reconnection via phone works (shows Jabra BT250 as being connected) 
but ignores the device

  Same behaviour with Audi car kit (Audi A3, 2012 model)

  EXPECTED:
  I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 
model) where the blue tooth pairing etc. works great (except some bugs which 
are already filed).

  ACTUAL:
  No connection to the blue tooth device

  VERSIONS:
  OS-Build-Number: 25
  Ubuntu-Image: 20150825.1

  POSSIBLE ROOT CAUSE:
  Is this issue also solved as soon as bluez5 is implemented? When will this be?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1540478] Re: Audio not automatically moved to the internal speaker

2016-02-03 Thread Jim Hodapp
This is not a bug and is the intended functionality. This is exactly the
same thing as what iOS does.

** Changed in: bluez (Ubuntu)
   Status: New => Invalid

** Changed in: pulseaudio (Ubuntu)
   Status: New => Invalid

** Changed in: canonical-devices-system-image
   Status: Confirmed => Invalid

-- 
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/1540478

Title:
  Audio not automatically moved to the internal speaker

Status in Canonical System Image:
  Invalid
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Test case.
  - Connect the device to a Bluetooth speaker.
  - Open music app.
  - Play a song -> Song played in the Bluetooth speaker.
  - Switch off the Bluetooth speaker.

  Expected result.
  - The audio from music-app must automatically move to the internal speaker.

  Actual result.
  - Playback is stopped. Track is not played on the device.

  Tapping play in music app continues the playback on the device.

  current build number: 248
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en

  Also tested in OTA9.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1540478/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1169376] Re: 8086:0166 [Dell XPS 13 L322X] backlight stopped working after update 3.8.0-18.28

2013-10-09 Thread Jim Hodapp
This seems to be fixed for me now as well.

-- 
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/1169376

Title:
  8086:0166 [Dell XPS 13 L322X] backlight stopped working after update
  3.8.0-18.28

Status in Dell Sputnik:
  Confirmed
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I'm on 13.04 beta 2 and I've been updating daily. After today's
  update, I was asked to restart and, after the restart, the backlight
  stopped working. What's worse is that the backlight is stuck in the
  lowest possible setting. I can barely see enough to type out this bug
  report. This is not a hardware problem. When I restart the computer
  the backlight turns on property  but burns off when the Ubuntu
  encryption screen comes up (I'm using full disk encryption). Please
  fix this as soon as possible.

  XPS 13 version: L322x
  Display version: FHD (1080p)
  --- 
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cr45h  1901 F pulseaudio
  DistroRelease: Ubuntu 13.04
  HibernationDevice: RESUME=UUID=a5d2ab8b-a068-4a69-95a6-b4e955b290f5
  InstallationDate: Installed on 2013-04-08 (9 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130402.1)
  MachineType: Dell Inc. Dell System XPS L322X
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-18-generic N/A
   linux-backports-modules-3.8.0-18-generic  N/A
   linux-firmware1.105
  Tags:  raring
  Uname: Linux 3.8.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 01/22/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd01/22/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L322X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1169376/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp