[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@Christian Mint is based on Ubuntu 22.04 which is from 2022 so uses old pulse-audio. > When I switch to A2DP I cannot use the headset mic. This is expected, A2DP is one direction only. > When I switch to HFP the sound in conversations is horrible. pulse-audio is kind of abandoned and actively developed. There are some fixes added but it seams that all effort goes to pipewire now. Give it a try. Add repositories for latest version: sudo add-apt-repository ppa:pipewire-debian/wireplumber-upstream sudo add-apt-repository ppa:pipewire-debian/pipewire-upstream Follow instructions to install and enable pipewire. There are multiple guide on the Internet, for example: https://trendoceans.com/enable-pipewire-and-disable-pulseaudio-in-ubuntu/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: Fix Released Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2008053] [NEW] Screen corruption and laggy mouse cursor in lower quarter of screen
Public bug reported: After a software upgrade yesterday, I see screen glitches and a "stumbling" mouse cursor whenever I move the mouse in the lower quarter of my laptop screen. When I have connected an external display, the external display doesn't show any issues, but the problem remains on the laptop screen. (This is my first bug report and I used the "ubuntu-bug" utility to collect the necessary data. I hope it is attached here somewhere.) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 22 08:58:07 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-60-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:46a8] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b04] InstallationDate: Installed on 2022-11-30 (83 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Latitude 5430 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2022 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 04X33N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd09/05/2022:br1.6:svnDellInc.:pnLatitude5430:pvr:rvnDellInc.:rn04X33N:rvrA00:cvnDellInc.:ct10:cvr:sku0B04: dmi.product.family: Latitude dmi.product.name: Latitude 5430 dmi.product.sku: 0B04 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption jammy ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2008053 Title: Screen corruption and laggy mouse cursor in lower quarter of screen Status in xorg package in Ubuntu: New Bug description: After a software upgrade yesterday, I see screen glitches and a "stumbling" mouse cursor whenever I move the mouse in the lower quarter of my laptop screen. When I have connected an external display, the external display doesn't show any issues, but the problem remains on the laptop screen. (This is my first bug report and I used the "ubuntu-bug" utility to collect the necessary data. I hope it is attached here somewhere.) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 22 08:58:07 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-60-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:46a8] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b04] InstallationDate: Installed on 2022-11-30 (83 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Latitude 5430 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2022 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc.
[Touch-packages] [Bug 1936864] Re: Samsung printer can't print after 21.04 update
> Workaround === > downgrade cups and libcups2 to version 2.3.3-3ubuntu1 (from Ubuntu 20.10 > Groovy) how to do this downgrade? I am affected by this issue too and basically my business is stopped now :( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1936864 Title: Samsung printer can't print after 21.04 update Status in cups package in Ubuntu: Confirmed Bug description: Hi, Since 21.04 update, I can't print any document with my Samsung ML-1665 laser printer. When I send a 1 page PDF, the printer warms up, the job appears to be successful, but no document is printed. A few minutes later, the printer prints this message : "INTERNAL ERROR - Incomplete Session by time out POSITION : 0x46069 (286825) SYSTEM : h6fw_5.37/os_hook LINE : 1226 VERSION : SPL 5.37 09-04-2009 " If I send the PDF to the printer twice in a row, the printer prints this message : "INTERNAL ERROR - Incomplete Corrupted Data POSITION : 0x38f72 (20) SYSTEM : h6fw_5.37/xl_image LINE : 154 VERSION : SPL 5.37 09-04-2009 " The problem happens with either Splix or Postscript-Samsung driver. Workaround === downgrade cups and libcups2 to version 2.3.3-3ubuntu1 (from Ubuntu 20.10 Groovy) After these 2 package downgrade, all work as expected. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: cups 2.3.3op2-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 19 21:27:14 2021 Lpstat: device for ml1665: usb://Samsung/ML-1660%20Series?serial=Z4ZFBKBZ807421A. device for ml1665-recto-verso: usb://Samsung/ML-1660%20Series?serial=Z4ZFBKBZ807421A. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2105 Dell Computer Corp. Model L100 Keyboard Bus 001 Device 002: ID 04e8:3301 Samsung Electronics Co., Ltd ML-1660 Series Bus 001 Device 004: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Printer, Driver=, 12M |__ Port 8: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 10: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Gigabyte Technology Co., Ltd. B360M H Papersize: a4 PpdFiles: ml1665-recto-verso: Samsung ML-1660, 2.0.0 ml1665: Samsung ML-1660 Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic root=/dev/mapper/vg_acer-lv_root ro SourcePackage: cups UpgradeStatus: Upgraded to hirsute on 2021-06-04 (45 days ago) dmi.bios.date: 03/14/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: Default string dmi.board.name: B360M H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd03/14/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB360MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB360MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B360M H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.cups.cupsd.conf: 2021-06-09T13:29:52.283606 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1936864/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1888316] [NEW] Corrupted gridlines on Dslstats on Intel HD 5500 (Dell Latitude E7250)
Public bug reported: On Ubuntu MATE 20.04 (and other releases of Ubuntu) I've noticed a problem with Dslstats (http://dslstats.me.uk/). I see corrupted gridlines as it is shown here. https://i.postimg.cc/Fz6TJ8pc/corrupted-gridlines.png On Intel Xorg driver I don't see this problem. https://i.postimg.cc/zv4kfWDF/normal-gridlines.png Configurations when the problem occurs: Dell Latitude E7250 (Intel HD 5500 graphics card) on Xorg with modesetting driver Dell Latitude E7250 (Intel HD 5500 graphics card) on Wayland Configurations when the problem does not occur: Dell Latitude E7250 on Xorg with intel driver Dell Optiplex 745 with AMD Radeon HD6450 graphis card Dell Optiplex 745 with integrated Intel GMA 3000 on Xorg with modesetting driver Dell Optiplex 745 with integrated Intel GMA 3000 on Xorg with intel driver ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: MATE Date: Mon Jul 20 20:13:44 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:062d] InstallationDate: Installed on 2020-06-05 (44 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Latitude E7250 ProcEnviron: LANGUAGE=pl PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=a072e6bc-e343-4720-9683-3754537c1cc5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: A24 dmi.board.name: 0V8RX3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA24:bd04/10/2020:svnDellInc.:pnLatitudeE7250:pvr:rvnDellInc.:rn0V8RX3:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7250 dmi.product.sku: 062D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1888316 Title: Corrupted gridlines on Dslstats on Intel HD 5500 (Dell Latitude E7250) Status in xorg package in Ubuntu: New Bug description: On Ubuntu MATE 20.04 (and other releases of Ubuntu) I've noticed a problem with Dslstats (http://dslstats.me.uk/). I see corrupted gridlines as it is shown here. https://i.postimg.cc/Fz6TJ8pc/corrupted-gridlines.png On Intel Xorg driver I don't see this problem. https://i.postimg.cc/zv4kfWDF/normal-gridlines.png Configurations when the problem occurs: Dell Latitude E7250 (Intel HD 5500 graphics card) on Xorg with modesetting driver Dell Latitude E7250 (Intel HD 5500 graphics card) on Wayland Configurations when the problem does not occur: Dell Latitude E7250 on Xorg with intel driver Dell Optiplex 745 with AMD Radeon HD6450 graphis card Dell Optiplex 745 with integrated Intel GMA 3000 on Xorg with modesetting driver Dell Optiplex 745 with integrated Intel GMA 3000 on Xorg with intel driver ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: MATE Date: Mon Jul 20 20:13:44 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:062d] InstallationDate: Installed on 2020-06-05 (44 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64
[Touch-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones
** Changed in: bluez (Ubuntu) Assignee: Konrad Zapałowicz (kzapalowicz) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC
** Changed in: bluez (Ubuntu) Assignee: Konrad Zapałowicz (kzapalowicz) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1731467 Title: Cannot pair BLE remote devices when using combo BT SoC Status in bluez package in Ubuntu: In Progress Status in linux package in Ubuntu: Fix Released Status in bluez source package in Xenial: New Status in linux source package in Xenial: Fix Released Status in bluez source package in Zesty: New Status in linux source package in Zesty: Fix Released Status in bluez source package in Artful: New Status in linux source package in Artful: Fix Released Bug description: It has been observed that sometimes it is not possible to pair with BLE remote devices when the host system is using combo (WiFi + BT) chip. The root cause of the disconnection has been identified as coming from the internal to bluez timeout. If bluez does not hear any reply from for two seconds the link is automagically disconnected. The reason fro the silence is not however a failure of the remote device but quite often a delay in the WiFi/BT combo driver that causes the packages not to reach the bluez stack. [Impact] Not possible to pair BLE remote devices such as sensors and such with Ubuntu when the host system uses BT+WiFi combo SoC. The connection attempt is disturbed with a timeout. [Fix] It has been fixed by increasing the timeout value from 2 seconds to 4 seconds. It is enough for the events to reach the stack (measured that it takes between 3 and 3.5 seconds). [Testcase] Tested with the device that failed to connect to Ubuntu Core gateway. It fails w/o the patch, it connects just fine with the patch applied. [Regression Potential] Very small. The increased timeout is taken into consideration only for new and scan report triggered connections. It will not make any already working device to fail to pair. [Other Info] The bug has been discussed and fixed here: https://marc.info/?l=linux-bluetooth=150824844606937=2 [Patch] https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth- next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571 The patch has been accepted by the upstream and will be a part of the next kernel release. Currently in the bluetooth-next tree. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731467/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809754] [NEW] x
Public bug reported: Ich habe zwei Bildschirme, 1x Laptop, 1x groß stationär Das Bild vom Laptop wird nur unvollständig auf den 2. Bildschirm übertragen. Es fehlen z.B. die Zeile für das Passwort zur Anmeldung und die Möglichkeit durch anklicken den Computer auszuschalten. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Dec 26 01:10:45 2018 DistUpgraded: 2018-10-11 19:33:52,049 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21da] InstallationDate: Installed on 2017-05-23 (581 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 4291BD2 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=71ccb682-9ba5-4c82-8ab3-e914e7f1835d ro rootflags=sync splash quiet SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-10-11 (75 days ago) dmi.bios.date: 04/18/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET75WW (1.45 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291BD2 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: BB70354824 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET75WW(1.45):bd04/18/2018:svnLENOVO:pn4291BD2:pvrThinkPadX220:rvnLENOVO:rn4291BD2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X220 dmi.product.name: 4291BD2 dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Oct 11 18:41:18 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 723 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1809754 Title: x Status in xorg package in Ubuntu: New Bug description: Ich habe zwei Bildschirme, 1x Laptop, 1x groß stationär Das Bild vom Laptop wird nur unvollständig auf den 2. Bildschirm übertragen. Es fehlen z.B. die Zeile für das Passwort zur Anmeldung und die Möglichkeit durch anklicken den Computer auszuschalten. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Dec 26 01:10:45 2018 DistUpgraded: 2018-10-11 19:33:52,049 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21da] InstallationDate: Installed on 2017-05-23 (581 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 4291BD2 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=71ccb682-9ba5-4c82-8ab3-e914e7f1835d ro rootflags=sync splash quiet SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-10-11 (75 days ago) dmi.bios.date: 04/18/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET75WW (1.45 )
[Touch-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor
same here, when monitor is plugged in I mouse coursor is flickering on host display, additionally sometimes sites do not work correctly when on screen 2, coursor is flickering too (but much less). When I've tried to apply solution from #108 after the reboot the second monitor was not detected at all, I had to revert back my settings. - Ubuntu 16.04 version: Linux 4.15.0-38-generic #41~16.04.1-Ubuntu SMP Wed Oct 10 20:16:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Graphic cards (when connected): *-display description: VGA compatible controller product: Broadwell-U Integrated Graphics vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:44 memory:f600-f6ff memory:d000-dfff ioport:f000(size=64) memory:c-d *-display description: VGA compatible controller product: Opal XT [Radeon R7 M265] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:08:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:45 memory:e000-efff memory:f700-f703 ioport:e000(size=256) memory:f704-f705 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1278223 Title: Mouse Flickering after adding 3rd Monitor Status in xorg package in Ubuntu: Incomplete Bug description: *PLEASE READ FIRST BEFORE CONSIDERING MAKING A COMMENT* If you are having an issue and want it addressed, it is most helpful to file a new report. If you were led here by DisplayLink's website, you were led here in error as no useful debugging information has been provided by the original reporter, which is necessary to root cause, and solve the issue he reported. Posting comments about how you think you have the same problem isn't helpful here. My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse flickers (or blinks) when the cursor is on monitors one or two, but not 3. Monitor 1: 1440 x 900 - Laptop's Native Monitor Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor Here's the video card that feeds my laptop's native monitor, monitor 2 (hdmi). lspci | grep 'VGA\|Display' 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) The 3rd Monitor is powered through a Display Link certified SIIG USB 2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but it is a sticker on back of the device): lsusb -tv /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M dmesg [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [1.688351] usb 2-1: Product: VGA Display Adapter [1.688353] usb 2-1: Manufacturer: DisplayLink [1.688356] usb 2-1: SerialNumber: 119785 Additionally, unity-control-center crashes sometimes after I "Restore previous settings", after selecting a resolution too high. This freezed my laptop, requiring a hard reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 9 18:43:13 2014 InstallationDate: Installed on 2014-02-02 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1510570] Re: Bluetooth LE pairing fail
** Description changed: [Impact] When the Bluetooth adapter is not powered on it is not possible to use it in normal way. We used to have a hack to force powering on by using an udev rule but this doe snot work anymore. Luckily the BlueZ has introduced "AutoEnable" option that makes the stack power on adapters by itself. Backporting this to xenial will improve life of the desktop users and will not require them to hack the solution on their own. The fix itself uses the well known solution to this problem that is floating around there for a while. The upload fixes the bug by enabling the 'AutoEnable' option in the bluetoothd config file. [Original Report] . 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 [Test Case] - Edit the /etc/bluetooth/main.conf and disable the 'AutoEnable' option. - Remove file 50-bluetooth-hci-auto-poweron.rules located in - /lib/udev/rules.d. Now reboot the machine. The BT adapter shall be - powered off now. + On xenial install from ppa: + https://launchpad.net/~bluetooth/+archive/ubuntu/bluez + + Now reboot the machine. The BT adapter shall be + powered on. [Regression Potential] - Cannot think of any + If things go wrong the adapter will not be powered on after the system + boots up. Therefore while testing please focus on the adapter state, + i.e. powered on or off. [Other Info] This fix is included in the development release, see: http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22 ** Description changed: [Impact] When the Bluetooth adapter is not powered on it is not possible to use it in normal way. We used to have a hack to force powering on by using an udev rule but this doe snot work anymore. Luckily the BlueZ has introduced "AutoEnable" option that makes the stack power on adapters by itself. Backporting this to xenial will improve life of the desktop users and will not require them to hack the solution on their own. The fix itself uses the well known solution to this problem that is floating around there for a while. The upload fixes the bug by enabling the 'AutoEnable' option in the bluetoothd config file. [Original Report] . 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 [Test Case] On xenial install from ppa: https://launchpad.net/~bluetooth/+archive/ubuntu/bluez Now reboot the machine. The BT adapter shall be powered on. [Regression Potential] If things go wrong the adapter will not be powered on after the system boots up. Therefore while testing please focus on the adapter state, i.e. powered on or off. [Other Info] This fix is included in the development release, see: http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22 + + [What to upload] + + For xenial as in: + + ) https://launchpad.net/~bluetooth/+archive/ubuntu/bluez + ) https://launchpadlibrarian.net/347480725/bluez_5.37-0ubuntu5_5.37-0ubuntu5.2~build1.diff.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1510570 Title: Bluetooth LE pairing fail Status in OEM Priority Project: Confirmed Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Xenial: Confirmed Bug description: [Impact] When the Bluetooth adapter is not powered on it is not possible to use it in normal way. We used to have a hack to force powering on by using an udev rule but this doe snot work anymore. Luckily the BlueZ has introduced "AutoEnable" option that makes the stack power on adapters by itself. Backporting this to xenial will improve life of the desktop users and will not require them to hack the solution on their own. The fix itself uses the well known solution to this problem that is floating around there for a while. The upload fixes the bug by enabling the 'AutoEnable' option in the
[Touch-packages] [Bug 1547297] Re: No auto login in Ubuntu GNOME Xenial
I can confirm this bug on Ubuntu 18.04 (20180104). I checked the auto log in option in the installer, but I still need to log in manually. ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1547297 Title: No auto login in Ubuntu GNOME Xenial Status in Ubuntu GNOME: Fix Released Status in accountsservice package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Confirmed Status in sddm package in Ubuntu: Confirmed Bug description: Just installed Ubuntu GNOME Xenial 20160218 amd64 and selected to auto login during installation, but once the installation was complete and I booted into Ubuntu GNOME I was asked for my password. I looked in the user UI and auto login was set to off, so I unlocked it, selected auto login = on, clicked on lock again, and rebooted but was once again asked for my password and the user UI once again showed auto login = off. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gdm3 3.18.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Feb 18 20:26:14 2016 InstallationDate: Installed on 2016-02-19 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1547297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1510570] Re: Bluetooth LE pairing fail
Testing:: 1. using the bluez without the patch - reboot - try to pair and connect 2. using bluez with patch - reboot - try to pair and connect In some cases pairing and connecting works better with the patch applied. There is no negative behavior observed with patch applied compared to w/o the patch. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1510570 Title: Bluetooth LE pairing fail Status in OEM Priority Project: Confirmed Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Xenial: Confirmed Bug description: [Impact] When the Bluetooth adapter is not powered on it is not possible to use it in normal way. We used to have a hack to force powering on by using an udev rule but this doe snot work anymore. Luckily the BlueZ has introduced "AutoEnable" option that makes the stack power on adapters by itself. Backporting this to xenial will improve life of the desktop users and will not require them to hack the solution on their own. The fix itself uses the well known solution to this problem that is floating around there for a while. The upload fixes the bug by enabling the 'AutoEnable' option in the bluetoothd config file. [Original Report] . 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 [Test Case] Edit the /etc/bluetooth/main.conf and disable the 'AutoEnable' option. Remove file 50-bluetooth-hci-auto-poweron.rules located in /lib/udev/rules.d. Now reboot the machine. The BT adapter shall be powered off now. [Regression Potential] Cannot think of any [Other Info] This fix is included in the development release, see: http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1510570] Re: Bluetooth LE pairing fail
** Changed in: bluez (Ubuntu Xenial) Assignee: (unassigned) => Konrad Zapałowicz (kzapalowicz) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1510570 Title: Bluetooth LE pairing fail Status in OEM Priority Project: Confirmed Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Xenial: Confirmed Bug description: [Impact] When the Bluetooth adapter is not powered on it is not possible to use it in normal way. We used to have a hack to force powering on by using an udev rule but this doe snot work anymore. Luckily the BlueZ has introduced "AutoEnable" option that makes the stack power on adapters by itself. Backporting this to xenial will improve life of the desktop users and will not require them to hack the solution on their own. The fix itself uses the well known solution to this problem that is floating around there for a while. The upload fixes the bug by enabling the 'AutoEnable' option in the bluetoothd config file. [Original Report] . 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 [Test Case] Edit the /etc/bluetooth/main.conf and disable the 'AutoEnable' option. Remove file 50-bluetooth-hci-auto-poweron.rules located in /lib/udev/rules.d. Now reboot the machine. The BT adapter shall be powered off now. [Regression Potential] Cannot think of any [Other Info] This fix is included in the development release, see: http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones
Hey, I just have tried to pair the QC35 using bluez 5.42 and 5.46 and it did pair. Could you capture HCI trace for me while you are pairing? Type: $ sudo btmon --write ~/bose-qc35.snoop Then start searching for the headset and try to pair. Once pairing fails kill the btmon and attach the .snoop file to this bug report. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC
** Tags removed: verification-needed-xenial verification-needed-zesty ** Tags added: verification-done-xenial verification-done-zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1731467 Title: Cannot pair BLE remote devices when using combo BT SoC Status in bluez package in Ubuntu: In Progress Status in linux package in Ubuntu: Incomplete Status in bluez source package in Xenial: New Status in linux source package in Xenial: Fix Committed Status in bluez source package in Zesty: New Status in linux source package in Zesty: Fix Committed Status in bluez source package in Artful: New Status in linux source package in Artful: Fix Committed Bug description: It has been observed that sometimes it is not possible to pair with BLE remote devices when the host system is using combo (WiFi + BT) chip. The root cause of the disconnection has been identified as coming from the internal to bluez timeout. If bluez does not hear any reply from for two seconds the link is automagically disconnected. The reason fro the silence is not however a failure of the remote device but quite often a delay in the WiFi/BT combo driver that causes the packages not to reach the bluez stack. [Impact] Not possible to pair BLE remote devices such as sensors and such with Ubuntu when the host system uses BT+WiFi combo SoC. The connection attempt is disturbed with a timeout. [Fix] It has been fixed by increasing the timeout value from 2 seconds to 4 seconds. It is enough for the events to reach the stack (measured that it takes between 3 and 3.5 seconds). [Testcase] Tested with the device that failed to connect to Ubuntu Core gateway. It fails w/o the patch, it connects just fine with the patch applied. [Regression Potential] Very small. The increased timeout is taken into consideration only for new and scan report triggered connections. It will not make any already working device to fail to pair. [Other Info] The bug has been discussed and fixed here: https://marc.info/?l=linux-bluetooth=150824844606937=2 [Patch] https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth- next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571 The patch has been accepted by the upstream and will be a part of the next kernel release. Currently in the bluetooth-next tree. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731467/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC
merged: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/xenial/commit/?id=1b1356e92b7ee81f7a83a7c5a67272f5ecbc3d38 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1731467 Title: Cannot pair BLE remote devices when using combo BT SoC Status in bluez package in Ubuntu: In Progress Status in linux package in Ubuntu: Incomplete Status in bluez source package in Xenial: New Status in linux source package in Xenial: Fix Committed Status in bluez source package in Zesty: New Status in linux source package in Zesty: Fix Committed Status in bluez source package in Artful: New Status in linux source package in Artful: Fix Committed Bug description: It has been observed that sometimes it is not possible to pair with BLE remote devices when the host system is using combo (WiFi + BT) chip. The root cause of the disconnection has been identified as coming from the internal to bluez timeout. If bluez does not hear any reply from for two seconds the link is automagically disconnected. The reason fro the silence is not however a failure of the remote device but quite often a delay in the WiFi/BT combo driver that causes the packages not to reach the bluez stack. [Impact] Not possible to pair BLE remote devices such as sensors and such with Ubuntu when the host system uses BT+WiFi combo SoC. The connection attempt is disturbed with a timeout. [Fix] It has been fixed by increasing the timeout value from 2 seconds to 4 seconds. It is enough for the events to reach the stack (measured that it takes between 3 and 3.5 seconds). [Testcase] Tested with the device that failed to connect to Ubuntu Core gateway. It fails w/o the patch, it connects just fine with the patch applied. [Regression Potential] Very small. The increased timeout is taken into consideration only for new and scan report triggered connections. It will not make any already working device to fail to pair. [Other Info] The bug has been discussed and fixed here: https://marc.info/?l=linux-bluetooth=150824844606937=2 [Patch] https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth- next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571 The patch has been accepted by the upstream and will be a part of the next kernel release. Currently in the bluetooth-next tree. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731467/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC
The only relevant log files that can be provided for this issue is a HCI trace. It is in .snoop format therefore can be viewed in wireshark. Attaching two log files: 1) failure-case: without proposed patch 2) success-case: with proposed patch ** Attachment added: "1731467-success-case.snoop" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731467/+attachment/5009472/+files/1731467-success-case.snoop -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1731467 Title: Cannot pair BLE remote devices when using combo BT SoC Status in bluez package in Ubuntu: In Progress Status in linux package in Ubuntu: Incomplete Status in bluez source package in Xenial: New Status in linux source package in Xenial: Confirmed Bug description: It has been observed that sometimes it is not possible to pair with BLE remote devices when the host system is using combo (WiFi + BT) chip. The root cause of the disconnection has been identified as coming from the internal to bluez timeout. If bluez does not hear any reply from for two seconds the link is automagically disconnected. The reason fro the silence is not however a failure of the remote device but quite often a delay in the WiFi/BT combo driver that causes the packages not to reach the bluez stack. [Impact] Not possible to pair BLE remote devices such as sensors and such with Ubuntu when the host system uses BT+WiFi combo SoC. The connection attempt is disturbed with a timeout. [Fix] It has been fixed by increasing the timeout value from 2 seconds to 4 seconds. It is enough for the events to reach the stack (measured that it takes between 3 and 3.5 seconds). [Testcase] Tested with the device that failed to connect to Ubuntu Core gateway. It fails w/o the patch, it connects just fine with the patch applied. [Regression Potential] Very small. The increased timeout is taken into consideration only for new and scan report triggered connections. It will not make any already working device to fail to pair. [Other Info] The bug has been discussed and fixed here: https://marc.info/?l=linux-bluetooth=150824844606937=2 [Patch] https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth- next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571 The patch has been accepted by the upstream and will be a part of the next kernel release. Currently in the bluetooth-next tree. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731467/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC
** Attachment added: "1731467-failure-case.snoop" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731467/+attachment/5009473/+files/1731467-failure-case.snoop ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1731467 Title: Cannot pair BLE remote devices when using combo BT SoC Status in bluez package in Ubuntu: In Progress Status in linux package in Ubuntu: Incomplete Status in bluez source package in Xenial: New Status in linux source package in Xenial: Confirmed Bug description: It has been observed that sometimes it is not possible to pair with BLE remote devices when the host system is using combo (WiFi + BT) chip. The root cause of the disconnection has been identified as coming from the internal to bluez timeout. If bluez does not hear any reply from for two seconds the link is automagically disconnected. The reason fro the silence is not however a failure of the remote device but quite often a delay in the WiFi/BT combo driver that causes the packages not to reach the bluez stack. [Impact] Not possible to pair BLE remote devices such as sensors and such with Ubuntu when the host system uses BT+WiFi combo SoC. The connection attempt is disturbed with a timeout. [Fix] It has been fixed by increasing the timeout value from 2 seconds to 4 seconds. It is enough for the events to reach the stack (measured that it takes between 3 and 3.5 seconds). [Testcase] Tested with the device that failed to connect to Ubuntu Core gateway. It fails w/o the patch, it connects just fine with the patch applied. [Regression Potential] Very small. The increased timeout is taken into consideration only for new and scan report triggered connections. It will not make any already working device to fail to pair. [Other Info] The bug has been discussed and fixed here: https://marc.info/?l=linux-bluetooth=150824844606937=2 [Patch] https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth- next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571 The patch has been accepted by the upstream and will be a part of the next kernel release. Currently in the bluetooth-next tree. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731467/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC
** Description changed: It has been observed that sometimes it is not possible to pair with BLE remote devices when the host system is using combo (WiFi + BT) chip. The root cause of the disconnection has been identified as coming from the internal to bluez timeout. If bluez does not hear any reply from for two seconds the link is automagically disconnected. The reason fro the silence is not however a failure of the remote device but quite often a delay in the WiFi/BT combo driver that causes the packages not to reach the bluez stack. + [Impact] + + Not possible to pair BLE remote devices such as sensors and such with + Ubuntu when the host system uses BT+WiFi combo SoC. The connection + attempt is disturbed with a timeout. + + [Fix] + + It has been fixed by increasing the timeout value from 2 seconds to + 4 seconds. It is enough for the events to reach the stack (measured + that it takes between 3 and 3.5 seconds). + + [Testcase] + + Tested with the device that failed to connect to Ubuntu Core gateway. + It fails w/o the patch, it connects just fine with the patch applied. + + [Regression Potential] + + Very small. The increased timeout is taken into consideration only for + new and scan report triggered connections. It will not make any already + working device to fail to pair. + + [Other Info] + The bug has been discussed and fixed here: https://marc.info/?l=linux-bluetooth=150824844606937=2 [Patch] https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth- next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571 - [Impact] - - Fixing this bug will enable xenial based Ubuntu core devices such as - gateways connect to various BLE sensors. - - [Regression Potential] - - Although the timeout has been increased the value is still very low - (4 seconds) therefore should not have a negative impact. It is - taken into consideration only during pairing and for connections that - are triggered by the scan report. - - [Other Info] - The patch has been accepted by the upstream and will be a part of the next kernel release. Currently in the bluetooth-next tree. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1731467 Title: Cannot pair BLE remote devices when using combo BT SoC Status in bluez package in Ubuntu: In Progress Bug description: It has been observed that sometimes it is not possible to pair with BLE remote devices when the host system is using combo (WiFi + BT) chip. The root cause of the disconnection has been identified as coming from the internal to bluez timeout. If bluez does not hear any reply from for two seconds the link is automagically disconnected. The reason fro the silence is not however a failure of the remote device but quite often a delay in the WiFi/BT combo driver that causes the packages not to reach the bluez stack. [Impact] Not possible to pair BLE remote devices such as sensors and such with Ubuntu when the host system uses BT+WiFi combo SoC. The connection attempt is disturbed with a timeout. [Fix] It has been fixed by increasing the timeout value from 2 seconds to 4 seconds. It is enough for the events to reach the stack (measured that it takes between 3 and 3.5 seconds). [Testcase] Tested with the device that failed to connect to Ubuntu Core gateway. It fails w/o the patch, it connects just fine with the patch applied. [Regression Potential] Very small. The increased timeout is taken into consideration only for new and scan report triggered connections. It will not make any already working device to fail to pair. [Other Info] The bug has been discussed and fixed here: https://marc.info/?l=linux-bluetooth=150824844606937=2 [Patch] https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth- next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571 The patch has been accepted by the upstream and will be a part of the next kernel release. Currently in the bluetooth-next tree. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731467/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1731467] [NEW] Cannot pair BLE remote devices when using combo BT SoC
Public bug reported: It has been observed that sometimes it is not possible to pair with BLE remote devices when the host system is using combo (WiFi + BT) chip. The root cause of the disconnection has been identified as coming from the internal to bluez timeout. If bluez does not hear any reply from for two seconds the link is automagically disconnected. The reason fro the silence is not however a failure of the remote device but quite often a delay in the WiFi/BT combo driver that causes the packages not to reach the bluez stack. [Impact] Not possible to pair BLE remote devices such as sensors and such with Ubuntu when the host system uses BT+WiFi combo SoC. The connection attempt is disturbed with a timeout. [Fix] It has been fixed by increasing the timeout value from 2 seconds to 4 seconds. It is enough for the events to reach the stack (measured that it takes between 3 and 3.5 seconds). [Testcase] Tested with the device that failed to connect to Ubuntu Core gateway. It fails w/o the patch, it connects just fine with the patch applied. [Regression Potential] Very small. The increased timeout is taken into consideration only for new and scan report triggered connections. It will not make any already working device to fail to pair. [Other Info] The bug has been discussed and fixed here: https://marc.info/?l=linux-bluetooth=150824844606937=2 [Patch] https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth- next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571 The patch has been accepted by the upstream and will be a part of the next kernel release. Currently in the bluetooth-next tree. ** Affects: bluez (Ubuntu) Importance: Undecided Assignee: Konrad Zapałowicz (kzapalowicz) Status: In Progress ** Attachment added: "0001-bluetooth-increase-timeout-for-le-auto-connections.patch" https://bugs.launchpad.net/bugs/1731467/+attachment/5006899/+files/0001-bluetooth-increase-timeout-for-le-auto-connections.patch ** Changed in: bluez (Ubuntu) Status: New => In Progress ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Konrad Zapałowicz (kzapalowicz) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1731467 Title: Cannot pair BLE remote devices when using combo BT SoC Status in bluez package in Ubuntu: In Progress Bug description: It has been observed that sometimes it is not possible to pair with BLE remote devices when the host system is using combo (WiFi + BT) chip. The root cause of the disconnection has been identified as coming from the internal to bluez timeout. If bluez does not hear any reply from for two seconds the link is automagically disconnected. The reason fro the silence is not however a failure of the remote device but quite often a delay in the WiFi/BT combo driver that causes the packages not to reach the bluez stack. [Impact] Not possible to pair BLE remote devices such as sensors and such with Ubuntu when the host system uses BT+WiFi combo SoC. The connection attempt is disturbed with a timeout. [Fix] It has been fixed by increasing the timeout value from 2 seconds to 4 seconds. It is enough for the events to reach the stack (measured that it takes between 3 and 3.5 seconds). [Testcase] Tested with the device that failed to connect to Ubuntu Core gateway. It fails w/o the patch, it connects just fine with the patch applied. [Regression Potential] Very small. The increased timeout is taken into consideration only for new and scan report triggered connections. It will not make any already working device to fail to pair. [Other Info] The bug has been discussed and fixed here: https://marc.info/?l=linux-bluetooth=150824844606937=2 [Patch] https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth- next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571 The patch has been accepted by the upstream and will be a part of the next kernel release. Currently in the bluetooth-next tree. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731467/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1729030] Re: [bluez] regression: bluetoothd crash with Bose QC35
** Project changed: snappy-hwe-snaps => bluez (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1729030 Title: [bluez] regression: bluetoothd crash with Bose QC35 Status in bluez package in Ubuntu: New Bug description: Bose QC35 with latest firmware Ubuntu 17.10 This is a regression from 17.04 Ubuntu Gnome. In 17.04, you had to temporarily disable `le` mode to pair but after pairing, everything worked flawlessly. In 17.10, pairing works out of the box, but the following issue appears: After a few hours of being connected, the connection between bose qc35 and Ubuntu seemingly breaks: the headphones don't play any sound anymore. re-pairing fails and restarting the headphones doesn't fix the issue. It seems bluetoothd crashed conmpletely since `bluetoothctl` doesn't work anymore.. Restarting Ubuntu fixes the issue. syslog contains a bunch of kernel stacktraces including a nullpointer dereference.. Oct 31 16:41:06 travers dbus-daemon[3888]: Activating via systemd: service name='org.bluez.obex' unit='dbus-org.bluez.obex.service' Oct 31 16:41:06 travers systemd[3874]: Starting Bluetooth OBEX service... Oct 31 16:41:06 travers bluetoothd[1128]: Failed to set mode: Busy (0x0a) Oct 31 16:41:06 travers obexd[29587]: OBEX daemon 5.46 Oct 31 16:41:06 travers dbus-daemon[3888]: Successfully activated service 'org.bluez.obex' Oct 31 16:41:06 travers systemd[3874]: Started Bluetooth OBEX service. Oct 31 16:41:06 travers bluetoothd[1128]: Failed to set mode: Busy (0x0a) Oct 31 16:41:06 travers bluetoothd[1128]: Failed to set mode: Busy (0x0a) Oct 31 16:41:12 travers kernel: Bluetooth: hci0 link tx timeout Oct 31 16:41:12 travers kernel: Bluetooth: hci0 killing stalled connection 04:52:c7:60:d6:2c Oct 31 16:41:12 travers acpid[1126]: input device has been disconnected, fd 24 Oct 31 16:41:12 travers kernel: Bluetooth: hci0 link tx timeout Oct 31 16:41:12 travers kernel: Bluetooth: hci0 killing stalled connection 04:52:c7:60:d6:2c Oct 31 16:41:14 travers bluetoothd[1128]: Disconnecting failed: already disconnected Oct 31 16:41:18 travers bluetoothd[1128]: Close: Connection timed out (110) Oct 31 16:41:18 travers kernel: Bluetooth: hci0 link tx timeout Oct 31 16:41:18 travers kernel: Bluetooth: hci0 killing stalled connection 04:52:c7:60:d6:2c Oct 31 16:41:20 travers bluetoothd[1128]: Abort: Connection timed out (110) Oct 31 16:41:20 travers kernel: Bluetooth: hci0 link tx timeout Oct 31 16:41:20 travers kernel: Bluetooth: hci0 killing stalled connection 04:52:c7:60:d6:2c Oct 31 16:41:20 travers kernel: Bluetooth: hci0 link tx timeout Oct 31 16:41:20 travers kernel: Bluetooth: hci0 killing stalled connection 04:52:c7:60:d6:2c Oct 31 16:41:20 travers dbus[1074]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.86" (uid=1000 pid=3997 comm="/usr/bin/pulseaudio --start --log-target=syslog ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.7" (uid=0 pid=1128 comm="/usr/lib/bluetooth/bluetoothd ") Oct 31 16:41:20 travers gsd-media-keys[4157]: Unable to get default sink Oct 31 16:41:32 travers kernel: sysfs: cannot create duplicate filename '/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:256' Oct 31 16:41:32 travers kernel: [ cut here ] Oct 31 16:41:32 travers kernel: WARNING: CPU: 2 PID: 19117 at /build/linux-XO_uEE/linux-4.13.0/fs/sysfs/dir.c:31 sysfs_warn_dup+0x56/0x70 Oct 31 16:41:32 travers kernel: Modules linked in: rfcomm ip6t_MASQUERADE nf_nat_masquerade_ipv6 ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 xt_comment zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm cmac xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bnep nls_iso8859_1 arc4 hid_alps snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm dell_rbtn dell_laptop iwlmvm irqbypass dell_smm_hwmon mac80211 crct10dif_pclmul crc32_pclmul snd_hda_codec_realtek snd_hda_codec_generic Oct 31 16:41:32 travers kernel: ghash_clmulni_intel pcbc iwlwifi rtsx_pci_ms uvcvideo cfg80211 memstick videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf snd_hda_intel snd_hda_codec joydev snd_hda_core snd_hwdep snd_pcm btusb btrtl snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device input_leds snd_timer serio_raw snd dell_wmi
[Touch-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
Hey, let me chime in into the discussion. First I'm terribly sorry to see that people are affected by this kind of issue. I remember a similar one on Ubuntu Phone which we have finally tracked down to the hardware side but were never able to fix completely. Canonical as a company and we as a developers working on Ubuntu do actually care about Bluetooth. Myself, Daniel and a few others formed an informal group that meets regularly and strives to set the course for improvement. Believe me, we would be delighted to see it working flawlessly because well... among other reasons we also use Bluetooth devices on daily basis. However, sadly, it is not that easy as the underlying technology itself is fairly complex and requires both hardware, software and remote side to click in. We are not searching for the white flag though :) this would be too easy. Instead we plan our work in a way that we are able to take down issues and gradually improve the overall experience. This is a step by step process where we tackle problems one by one aiming for these that have the best chance to be solved in order to deliver improvements with each cycle. In this case the audio in under running, PulseAudio tries to catch up and this is why you see skipped bytes messages. There might be multiple reasons for this starting from PulseAudio (and it's Bluetooth modules), through bluez, system load and such and ending on the hardware configuration itself. For example hugely popular WiFi+BT combo chipsets are prone to such issues as Bluetooth and WiFi have to compete for throughput. If I were you I would start from reporting this issue to Pulse Audio developers through their mailing list (perhaps also on bluez) and start working from there. We do keep an eye on these so if there is something interesting coming up in the discussions we will pick it up. We will also remember about this one and for an upcoming bluez 5.47 testing we will include high-load tests to see if we can even experience this issue (so far we did not) with the hardware we test with. Does it make sense? Hope that at some point in the near future we will learn enough about this one so that we can fix it. Hope this helps, K -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1688663] Re: udev 97-hid2hci.rules missing usb id for logitech dinovo 2
Meaning that it is out :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1688663 Title: udev 97-hid2hci.rules missing usb id for logitech dinovo 2 Status in bluez package in Ubuntu: Fix Released Bug description: Trying to install kubuntu 16.04.2 (Xenial Xerus) today, the Logitech dinovo 2 bluetooth keyboard and mouse didn't work, nor in live cd nor after being installed using another keyboard and mouse. In /lib/udev/rules.d/97-hid2hci.rules there are two lines for Logitech devices: # Logitech devices KERNEL=="hiddev*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[345abce]|c71[3bc]", \ RUN+="hid2hci --method=logitech-hid --devpath=%p" # Logitech, Inc. diNovo Edge Keyboard KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c714", \ RUN+="hid2hci --method=logitech-hid --devpath=%p" lsusb shows in my computer: Bus 001 Device 006: ID 046d:c704 Logitech, Inc. diNovo Wireless Desktop The id is almost equal (c714 <> c704). After adding a new line with the missing id, the keyboard and mouse started to work: # Logitech, Inc. diNovo 2 KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c704", \ RUN+="hid2hci --method=logitech-hid --devpath=%p" I've also followed these other bugs to find out the file that I needed to modify and that my keyboard needs hidraw instead of hiddev: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/872940 https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/123920 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1688663/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1688663] Re: udev 97-hid2hci.rules missing usb id for logitech dinovo 2
This shall be released ** Changed in: bluez (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1688663 Title: udev 97-hid2hci.rules missing usb id for logitech dinovo 2 Status in bluez package in Ubuntu: Fix Released Bug description: Trying to install kubuntu 16.04.2 (Xenial Xerus) today, the Logitech dinovo 2 bluetooth keyboard and mouse didn't work, nor in live cd nor after being installed using another keyboard and mouse. In /lib/udev/rules.d/97-hid2hci.rules there are two lines for Logitech devices: # Logitech devices KERNEL=="hiddev*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[345abce]|c71[3bc]", \ RUN+="hid2hci --method=logitech-hid --devpath=%p" # Logitech, Inc. diNovo Edge Keyboard KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c714", \ RUN+="hid2hci --method=logitech-hid --devpath=%p" lsusb shows in my computer: Bus 001 Device 006: ID 046d:c704 Logitech, Inc. diNovo Wireless Desktop The id is almost equal (c714 <> c704). After adding a new line with the missing id, the keyboard and mouse started to work: # Logitech, Inc. diNovo 2 KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c704", \ RUN+="hid2hci --method=logitech-hid --devpath=%p" I've also followed these other bugs to find out the file that I needed to modify and that my keyboard needs hidraw instead of hiddev: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/872940 https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/123920 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1688663/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1712495] Re: Please sponsor bluez 5.46-0ubuntu2 to artful
@Timo, thanks man, appreciated. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1712495 Title: Please sponsor bluez 5.46-0ubuntu2 to artful Status in bluez package in Ubuntu: In Progress Bug description: Please sponsor bluez 5.46-0ubuntu2 to artful This fixes a crash of zyga's that's been discussed a lot in the past but never opened as an official bug report. It has however already been fixed upstream and will be included in 5.47. It's not yet clear exactly which existing LP bug/error reports this will resolve. We'll find out later by tracking errors.ubuntu.com (I suspect it might resolve a couple). If you need a proper bug report then please ask zygmunt.kryni...@canonical.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1712495/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1696075] Re: Please sponsor bluez 5.45 in artful
@jibel thanks, got it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1696075 Title: Please sponsor bluez 5.45 in artful Status in bluez package in Ubuntu: Fix Committed Bug description: Please sponsor bluez 5.45 in artful Debdiff attached. Source code for the debdiff: https://git.launchpad.net/~bluetooth/bluez/log/?h=artful Upstream releases information: http://www.bluez.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1696075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1696075] Re: Please sponsor bluez 5.45 in artful
So it is released now? /K W dniu śr., 7.06.2017 o 18:21 Sebastien Bachernapisał(a): > Thanks for the work, I uploaded it > https://launchpad.net/ubuntu/+source/bluez/5.45-0ubuntu1 > > Next time please include the bug reference as "(lp: #nnn)" in the > changelog so the bug gets autoclosed on upload > > Note that the package is blocked in proposed, see > http://people.canonical.com/~ubuntu-archive/proposed- > migration/update_excuses.html#bluez > > ** Changed in: bluez (Ubuntu) >Importance: Undecided => Low > > ** Changed in: bluez (Ubuntu) >Status: New => Fix Committed > > ** Changed in: bluez (Ubuntu) > Assignee: (unassigned) => Daniel van Vugt (vanvugt) > > -- > You received this bug notification because you are a member of > Bluetooth, which is subscribed to bluez in Ubuntu. > https://bugs.launchpad.net/bugs/1696075 > > Title: > Please sponsor bluez 5.45 in artful > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1696075/+subscriptions > > -- > Ubuntu-bluetooth mailing list > ubuntu-blueto...@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bluetooth > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1696075 Title: Please sponsor bluez 5.45 in artful Status in bluez package in Ubuntu: Fix Committed Bug description: Please sponsor bluez 5.45 in artful Debdiff attached. Source code for the debdiff: https://git.launchpad.net/~bluetooth/bluez/log/?h=artful Upstream releases information: http://www.bluez.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1696075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1688663] Re: udev 97-hid2hci.rules missing usb id for logitech dinovo 2
** Tags added: papercuts2017 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1688663 Title: udev 97-hid2hci.rules missing usb id for logitech dinovo 2 Status in bluez package in Ubuntu: New Bug description: Trying to install kubuntu 16.04.2 (Xenial Xerus) today, the Logitech dinovo 2 bluetooth keyboard and mouse didn't work, nor in live cd nor after being installed using another keyboard and mouse. In /lib/udev/rules.d/97-hid2hci.rules there are two lines for Logitech devices: # Logitech devices KERNEL=="hiddev*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[345abce]|c71[3bc]", \ RUN+="hid2hci --method=logitech-hid --devpath=%p" # Logitech, Inc. diNovo Edge Keyboard KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c714", \ RUN+="hid2hci --method=logitech-hid --devpath=%p" lsusb shows in my computer: Bus 001 Device 006: ID 046d:c704 Logitech, Inc. diNovo Wireless Desktop The id is almost equal (c714 <> c704). After adding a new line with the missing id, the keyboard and mouse started to work: # Logitech, Inc. diNovo 2 KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c704", \ RUN+="hid2hci --method=logitech-hid --devpath=%p" I've also followed these other bugs to find out the file that I needed to modify and that my keyboard needs hidraw instead of hiddev: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/872940 https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/123920 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1688663/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1688663] Re: udev 97-hid2hci.rules missing usb id for logitech dinovo 2
@jesusdf you have written that: "the Logitech dinovo 2 bluetooth keyboard and mouse didn't work, nor in live cd nor after being installed using another keyboard and mouse." I wonder - were you able to pair it or that did not work too? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1688663 Title: udev 97-hid2hci.rules missing usb id for logitech dinovo 2 Status in bluez package in Ubuntu: New Bug description: Trying to install kubuntu 16.04.2 (Xenial Xerus) today, the Logitech dinovo 2 bluetooth keyboard and mouse didn't work, nor in live cd nor after being installed using another keyboard and mouse. In /lib/udev/rules.d/97-hid2hci.rules there are two lines for Logitech devices: # Logitech devices KERNEL=="hiddev*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[345abce]|c71[3bc]", \ RUN+="hid2hci --method=logitech-hid --devpath=%p" # Logitech, Inc. diNovo Edge Keyboard KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c714", \ RUN+="hid2hci --method=logitech-hid --devpath=%p" lsusb shows in my computer: Bus 001 Device 006: ID 046d:c704 Logitech, Inc. diNovo Wireless Desktop The id is almost equal (c714 <> c704). After adding a new line with the missing id, the keyboard and mouse started to work: # Logitech, Inc. diNovo 2 KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c704", \ RUN+="hid2hci --method=logitech-hid --devpath=%p" I've also followed these other bugs to find out the file that I needed to modify and that my keyboard needs hidraw instead of hiddev: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/872940 https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/123920 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1688663/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1688663] Re: udev 97-hid2hci.rules missing usb id for logitech dinovo 2
Interesting. Will look into this. ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Konrad Zapałowicz (kzapalowicz) ** Tags added: bluez-desktop -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1688663 Title: udev 97-hid2hci.rules missing usb id for logitech dinovo 2 Status in bluez package in Ubuntu: New Bug description: Trying to install kubuntu 16.04.2 (Xenial Xerus) today, the Logitech dinovo 2 bluetooth keyboard and mouse didn't work, nor in live cd nor after being installed using another keyboard and mouse. In /lib/udev/rules.d/97-hid2hci.rules there are two lines for Logitech devices: # Logitech devices KERNEL=="hiddev*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[345abce]|c71[3bc]", \ RUN+="hid2hci --method=logitech-hid --devpath=%p" # Logitech, Inc. diNovo Edge Keyboard KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c714", \ RUN+="hid2hci --method=logitech-hid --devpath=%p" lsusb shows in my computer: Bus 001 Device 006: ID 046d:c704 Logitech, Inc. diNovo Wireless Desktop The id is almost equal (c714 <> c704). After adding a new line with the missing id, the keyboard and mouse started to work: # Logitech, Inc. diNovo 2 KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c704", \ RUN+="hid2hci --method=logitech-hid --devpath=%p" I've also followed these other bugs to find out the file that I needed to modify and that my keyboard needs hidraw instead of hiddev: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/872940 https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/123920 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1688663/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1442896] Re: Bluetooth mouse disconnects and reconnects every few seconds
@mcumpa could you post the syslog as well as HCI trace for your case? 1. syslog Please enable the debug output first by typing: $ sudo sed -i 's/bluetoothd/bluetoothd \-d/g' /lib/systemd/system/bluetooth.service 2. HCI trace Execute: $ sudo btmon --write ~/hcitrace.snoop before you start reproducing the issue [but might be after pairing to limit the log size]. It is important not to make the test too long so that the HCI trace is easier to read and understand. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1442896 Title: Bluetooth mouse disconnects and reconnects every few seconds Status in Bluez Utilities: New Status in bluez package in Ubuntu: Incomplete Bug description: I have a bluetooth mouse (Genius Traveller 9005BT) that I have been using without problems with Ubuntu for over a year. Since a few weeks ago, however, it started disconnecting and reconnected from the computer. The symptoms are like this: 1. The mouse works, and the bluetooth icon on the computer is visible (in gnome-shell's top bar) 2. The mouse stops working, but the bluetooth icon is still visible. This state lasts between 1 and 10 seconds. 3. The bluetooth icon vanishes. This can last for half a second if I keep trying to use the mouse, to forever I I leave the mouse alone 4. The bluetooth icon reappears and the mouse starts working again. This state last from 2-3 seconds if I don't move the mouse, to seemingly forever if I continuously move the mouse This seems to occur only after a suspend/resume cycle, and rebooting the computer fixes the issue. The only thing I see in syslog is this when the mouse reconnects: Apr 11 10:03:10 tadzim3 kernel: [52026.494469] hid-generic 0005:0458:0139.002F: unknown main item tag 0x0 Apr 11 10:03:10 tadzim3 kernel: [52026.494540] input: Traveler 9005BT as /devices/pci:00/:00:14.0/usb2/2-4/2-4:1.0/bluetooth/hci0/hci0:512/0005:0458:0139.002F/input/input59 Apr 11 10:03:10 tadzim3 kernel: [52026.494899] hid-generic 0005:0458:0139.002F: input,hidraw3: BLUETOOTH HID v3.12 Mouse [Traveler 9005BT] on e8:2a:ea:8b:a5:5f ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Apr 11 09:49:37 2015 InstallationDate: Installed on 2015-01-23 (77 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) InterestingModules: bnep rfcomm btusb bluetooth MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-34-generic.efi.signed root=UUID=eecad38d-4fff-462c-92bc-357fa12e5515 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to utopic on 2015-01-31 (69 days ago) dmi.bios.date: 03/25/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN35WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN35WW:bd03/25/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: E8:2A:EA:8B:A5:5F ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING PSCAN RX bytes:1873821 acl:123158 sco:0 events:2377 errors:0 TX bytes:29044 acl:238 sco:0 commands:218 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1442896/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1565940] Re: bluetoothctl systematically hangs when there is no bluetooth hardware
Now I understand your use-case. You probably could achieve similar with $ systemctl status bluetooth.service. Also hcitool can tell if the adapter is up and running but keep in mind that hcitool is depreciated and no longer maintained by the upstream. As for the man entry suggestion yes that could be something to consider given that the default man page is quite vague nevertheless this, as whole bluez, comes straight from the upstream. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1565940 Title: bluetoothctl systematically hangs when there is no bluetooth hardware Status in bluez package in Ubuntu: New Bug description: On a machine WITH bluetooth hardware, the 'bluetoothctl' command works correctly. For example, the command 'bluetoothctl < /dev/null' terminates correctly. On a machine WITHOUT bluetooth hardware, the 'bluetoothctl' command systematically hangs. Even the command 'bluetoothctl < /dev/null' systematically hangs. $ bluetoothctl & [1] 6208 $ ps -l $! F S UID PID PPID C PRI NI ADDR SZ WCHAN TTYTIME CMD 0 T 1001 6208 2525 0 80 0 - 9578 signal pts/1 0:00 bluetoothctl [1]+ Stopped bluetoothctl ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 4 20:09:39 2016 InstallationDate: Installed on 2015-07-20 (259 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterestingModules: bluetooth MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed root=UUID=0d11df61-c758-41b1-9ec3-8310bf038b07 ro quiet splash vt.handoff=7 SourcePackage: bluez UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-22 (165 days ago) dmi.bios.date: 06/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. hciconfig: rfkill: syslog: avril 03 15:10:45 urbah-sirius systemd[1]: Starting Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5)... avril 03 15:10:45 urbah-sirius NetworkManager[986]: Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) avril 03 15:10:50 urbah-sirius systemd[1]: Started Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1565940/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1565940] Re: bluetoothctl systematically hangs when there is no bluetooth hardware
I'm afraid that this is how the bluetoothctl is designed. This tool is a command-line interface to the bluetoothd and requires it up and running. It will not quit however when it is not running for a situations where the daemon might come back online. Ubuntu does not do anything special here, the bluetoothctl tool is packaged as is from the upstream. For Ubuntu this normally should not be a problem because a user is expected to use {unity,gnome}-system-settings anyway to interact with BT subsystem. Is there a particular use-case that is failing on this behavior? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1565940 Title: bluetoothctl systematically hangs when there is no bluetooth hardware Status in bluez package in Ubuntu: New Bug description: On a machine WITH bluetooth hardware, the 'bluetoothctl' command works correctly. For example, the command 'bluetoothctl < /dev/null' terminates correctly. On a machine WITHOUT bluetooth hardware, the 'bluetoothctl' command systematically hangs. Even the command 'bluetoothctl < /dev/null' systematically hangs. $ bluetoothctl & [1] 6208 $ ps -l $! F S UID PID PPID C PRI NI ADDR SZ WCHAN TTYTIME CMD 0 T 1001 6208 2525 0 80 0 - 9578 signal pts/1 0:00 bluetoothctl [1]+ Stopped bluetoothctl ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 4 20:09:39 2016 InstallationDate: Installed on 2015-07-20 (259 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterestingModules: bluetooth MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed root=UUID=0d11df61-c758-41b1-9ec3-8310bf038b07 ro quiet splash vt.handoff=7 SourcePackage: bluez UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-22 (165 days ago) dmi.bios.date: 06/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. hciconfig: rfkill: syslog: avril 03 15:10:45 urbah-sirius systemd[1]: Starting Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5)... avril 03 15:10:45 urbah-sirius NetworkManager[986]: Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) avril 03 15:10:50 urbah-sirius systemd[1]: Started Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1565940/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1510570] Re: Bluetooth LE pairing fail
** Description changed: - On 15.10 we now have bluez 5 so we can pair BLE devices like the + [Impact] + + When the Bluetooth adapter is not powered on it is not possible to use + it in normal way. We used to have a hack to force powering on by using + an udev rule but this doe snot work anymore. Luckily the BlueZ has + introduced "AutoEnable" option that makes the stack power on adapters by + itself. + + Backporting this to xenial will improve life of the desktop users and + will not require them to hack the solution on their own. The fix itself + uses the well known solution to this problem that is floating around + there for a while. + + The upload fixes the bug by enabling the 'AutoEnable' option in the + bluetoothd config file. + + [Original Report] + + . 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. - Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. + Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used + instead of udev rules. - here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 - And a ppa to test it: https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable + here is a commit with this parameter: + http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 + + [Test Case] + + Edit the /etc/bluetooth/main.conf and disable the 'AutoEnable' option. + Remove file 50-bluetooth-hci-auto-poweron.rules located in + /lib/udev/rules.d. Now reboot the machine. The BT adapter shall be + powered off now. + + [Regression Potential] + + Cannot think of any + + [Other Info] ** Description changed: [Impact] When the Bluetooth adapter is not powered on it is not possible to use it in normal way. We used to have a hack to force powering on by using an udev rule but this doe snot work anymore. Luckily the BlueZ has introduced "AutoEnable" option that makes the stack power on adapters by itself. Backporting this to xenial will improve life of the desktop users and will not require them to hack the solution on their own. The fix itself uses the well known solution to this problem that is floating around there for a while. The upload fixes the bug by enabling the 'AutoEnable' option in the bluetoothd config file. [Original Report] . 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 [Test Case] Edit the /etc/bluetooth/main.conf and disable the 'AutoEnable' option. Remove file 50-bluetooth-hci-auto-poweron.rules located in /lib/udev/rules.d. Now reboot the machine. The BT adapter shall be powered off now. [Regression Potential] Cannot think of any [Other Info] + + This fix is included in the development release, see: + http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22 ** Changed in: bluez (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1510570 Title: Bluetooth LE pairing fail Status in bluez package in Ubuntu: Fix Released Bug description: [Impact] When the Bluetooth adapter is not powered on it is not possible to use it in normal way. We used to have a hack to force powering on by using an udev rule but this doe snot work anymore. Luckily the BlueZ has introduced "AutoEnable" option that makes the stack power on adapters by itself. Backporting this to xenial will improve life of the desktop users and will not require them to hack the solution on their own. The fix itself uses the well known solution to this problem that is floating around there for a while. The upload fixes the bug by enabling the 'AutoEnable' option in the bluetoothd config file. [Original Report] . 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a
[Touch-packages] [Bug 1531925] Re: Can't connect Logitech K830 - no PIN prompt [LE]
Fix for U-S-S is merged: https://code.launchpad.net/~kzapalowicz/ubuntu- system-settings/ubuntu-system-settings/+merge/301370 ** Changed in: ubuntu-system-settings (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1531925 Title: Can't connect Logitech K830 - no PIN prompt [LE] Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: Cannot connect a Logitech Illuminated Living Room keyboard to a device running bluez5. There are two versions of the keyboard, a unifying receiver version, and a Bluetooth version. The latter has a BT symbol on the 'del' key. To put the BT version in pairing mode, power on the keyboard, then briefly hold the FN and 'del' key together and release. A green LED at the top right of the keyboard should start flashing quickly. Once in pairing mode, the device will become visible on desktop using the BT settings UI, however it's *never* shown in the UI on a device running the latest Touch ( OTA9.1+ ). Note, this includes devices running a silo version of bluez 5.37, including both arale and krillin. On both devices, the keyboard *is* viewable using bluetoothctl. It should be noted that LE keyboard support on touch should be a considered a missing feature. Here's the reported attributes of the device from my macair running 15.10 + bluez 5.37: Device DF:08:A9:A0:13:93 Name: K830 Alias: K830 Appearance: 0x03c1 Icon: input-keyboard Paired: yes Trusted: no Blocked: no Connected: yes LegacyPairing: no UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Device Information (180a--1000-8000-00805f9b34fb) UUID: Battery Service (180f--1000-8000-00805f9b34fb) UUID: Human Interface Device (1812--1000-8000-00805f9b34fb) UUID: Vendor specific (0001--1000-8000-011f246d) Modalias: usb:v046DpB335d0010 From bluetoothctl on both my laptop and my desktop, I'm able to pair, trust and connect the device, and info reflects these changes, however the device never actually connects, it's LED remains blinking fast, and the keyboard cannot be used. Note, before pairing, I issued the command 'agent KeyboardOnly' and 'default-agent'. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1531925/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety
The ppa is: ppa:ubuntu-audio-dev/pulse-testing Feel free to add it to your system, update pulseaudio and test with your headsets. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1438510 Title: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in bluez source package in Vivid: Won't Fix Status in pulseaudio source package in Vivid: Won't Fix Bug description: Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 The bug is still present in 16.04 LTS and 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1438510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety
Hey, to everyone interested we are currently testing and reviewing an improvement to PA that fixes problems with selecting A2DP mode for BT headsets. Right now it is being tested internally with good results for Sony headsets, QC35 from Bose and BT speakers. Once it is in a silo/ppa I will share this information for much wider testing. Then it will be submitted as a SRU and will land in xenial. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1438510 Title: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in bluez source package in Vivid: Won't Fix Status in pulseaudio source package in Vivid: Won't Fix Bug description: Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 The bug is still present in 16.04 LTS and 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1438510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456711] Re: crash on incoming sms
Has this been every fixed? I currently have this problem with my BQ E4.5 OTA-15. When I receive any SMS, I press Power button, see the notification and then the phone crashes. It keeps trying to restart Unity8 (ubuntu logo with dots), but it does not succeed. I long press the power button to restart the phone. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1456711 Title: crash on incoming sms Status in unity8 package in Ubuntu: Confirmed Bug description: Mako running latest rtm v226 Sent an sms Screen off Received an incoming sms - the screen woke up - unity8 crashed and saw the ubuntu logo - unity8 back up and message in the indicator The attached crash file is from last week when I think the same thing occurred, unfortunately didnt get the crash file for this event. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1456711/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1660619] Re: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B
I saw this today on my Lenovo T400. Ubuntu 16.04.1 LTS, running 4.4.0-62-generic x86_64 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1660619 Title: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B Status in xorg package in Ubuntu: Confirmed Bug description: I've a dual monitor setup and I'm running latest version of kubuntu. After a few days of uptime the desktop becomes so slow that I've to reboot it. In the log I find those errors, I don't know if they are related: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=150051 end=150052) time 110 us, min 1073, max 1079, scanline start 1072, end 1080 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Jan 31 14:06:17 2017 DistUpgraded: 2016-10-16 19:45:53,200 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.8.0-30-generic, x86_64: installed bbswitch, 0.8, 4.8.0-32-generic, x86_64: installed bbswitch, 0.8, 4.8.0-34-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 530 [1462:7978] InstallationDate: Installed on 2013-04-25 (1376 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) LightdmGreeterLogOld: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: Unable to assign [undefined] to QString usersession MachineType: MSI MS-7978 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic root=UUID=f848f2e6-9d53-4c75-823a-fa97cfe10aa6 ro SourcePackage: xorg UpgradeStatus: Upgraded to yakkety on 2016-10-16 (106 days ago) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.60 dmi.board.asset.tag: Default string dmi.board.name: Z170A GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnZ170AGAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7978 dmi.product.version: 2.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Sat Jan 28 11:57:37 2017 xserver.configfile: default xserver.errors: Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1660619/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1510570] Re: BLE pairing fail
@All FYI: the fix discussed here is on it's way to zesty [currently being tested]. Moreover we are making efforts on getting it as an update to xenial. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1510570 Title: BLE pairing fail Status in bluez package in Ubuntu: Confirmed Bug description: On 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 And a ppa to test it: https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1510570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones
@All Let me explain a bit how the headset works so that you have the general understanding and perhaps an explanation to why there are some problems with how it works with Ubuntu. This headset supports both the BR/EDR mode also known as Bluetooth Classic and the Bluetooth Low Energy sometimes referred to as Smart. The important bit however is the fact that on the Low Energy side it does not support pairing. The pairing is expected to happen on the BR/EDR. As far as I remember the bluez prioritizes the LE mode over BR/EDR and initiates pairing on this channel that for the reasons stated above fails. BlueZ 5.42 contains improvements for transport selection (BR/EDR vs LE). This is not yet a full support offering seamless experience however things might look better using it. For you to know we currently package: - xenial with bluez 5.37 - yakkety with bluez 5.41 - zesty with bluez 5.41 With the ongoing work to have zesty being packaged with the latest upstream bluez which is atm 5.43. Also we plan to update xenial with bluez 5.43 however this is nothing certain yet as we need to make sure that the update will play nice with the LTS release and not break anything. Hope this helps -- You received this bug notification because you are a member of Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones
@Wesley Understood. Can you use it w/ the Bose app on the phone? -- You received this bug notification because you are a member of Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654782] Re: Can not pair with bluetooth headphones
** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Konrad Zapałowicz (kzapalowicz) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1654782 Title: Can not pair with bluetooth headphones Status in bluez package in Ubuntu: Incomplete Bug description: I can not pair computer and Bluetooth headset (sennheiser momentum 2.0 wireless aebt). (If it matters, I *CAN* pair and use it on another laptop with Linux and with my android smartphone. So headset itself is working well.) Here is how I try to pair: $ bluetoothctl [NEW] Controller 54:27:1E:33:4B:85 impedance [default] [bluetooth]# power on Changing power on succeeded [bluetooth]# agent on Agent registered [bluetooth]# default-agent Default agent request successful [bluetooth]# scan on Discovery started [CHG] Controller 54:27:1E:33:4B:85 Discovering: yes [bluetooth]# scan on I tried to put my headset in pairing mode just before and after issuing "scan on" command. It ends up with nothing - I waited for 3-5 minutes. For example, my smartphone pairs with the headset within 5-15 seconds, my laptop pairs with the headset within about 30 seconds. = Here is info $ hciconfig -a hci0: Type: Primary Bus: USB BD Address: 54:27:1E:33:4B:85 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:4475 acl:0 sco:0 events:565 errors:0 TX bytes:7214 acl:0 sco:0 commands:487 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'impedance' Class: 0x1c0104 Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Desktop workstation HCI Version: 4.0 (0x6) Revision: 0x1000 LMP Version: 4.0 (0x6) Subversion: 0x220e Manufacturer: Broadcom Corporation (15) = rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no = Bluez packages installed: $ dpkg -l | grep bluez ii bluez ii bluez-btsco ii bluez-cups ii bluez-hcidump ii bluez-obexd ii bluez-tools ii libkf5bluezqt-data ii libkf5bluezqt6:amd64 ii qml-module-org-kde-bluezqt:amd64 = $ dmesg | grep -i blue [4.632406] Bluetooth: Core ver 2.21 [4.632414] Bluetooth: HCI device and connection manager initialized [4.632416] Bluetooth: HCI socket layer initialized [4.632417] Bluetooth: L2CAP socket layer initialized [4.632420] Bluetooth: SCO socket layer initialized [4.644619] Bluetooth: hci0: BCM: chip id 63 [4.660554] Bluetooth: hci0: impedance [4.661552] Bluetooth: hci0: BCM20702A1 (001.002.014) build [4.661798] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0b05-17cf.hcd failed with error -2 [4.661799] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0b05-17cf.hcd not found [ 15.061603] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.061604] Bluetooth: BNEP filters: protocol multicast [ 15.061606] Bluetooth: BNEP socket layer initialized [ 48.001553] Bluetooth: RFCOMM TTY layer initialized [ 48.001558] Bluetooth: RFCOMM socket layer initialized [ 48.001562] Bluetooth: RFCOMM ver 1.11 [ 615.404052] Modules linked in: rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack rpcsec_gss_krb5 nfnetlink_queue nfsv4 nfnetlink xt_tcpudp bridge xt_NFQUEUE nfs xt_owner iptable_filter fscache cmac bnep binfmt_misc nls_iso8859_1 intel_rapl edac_core x86_pkg_temp_thermal coretemp btrfs xor snd_hda_codec_hdmi eeepc_wmi asus_wmi sparse_keymap video mxm_wmi raid6_pq btusb btrtl btbcm btintel bluetooth kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw glue_helper ablk_helper cryptd intel_cstate input_leds intel_rapl_perf 8021q garp mrp stp serio_raw llc b43 mac80211 snd_hda_codec_realtek snd_hda_codec_generic ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: bluez 5.41-0ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE Date: Sat Jan 7 22:36:22 2017 InstallationDate: Installed on 2014-07-05 (917 days ago) Inst
[Touch-packages] [Bug 1654782] Re: Can not pair with bluetooth headphones
Hey, Thanks for the report. I will mark it as "needs information" because I need a follow up from your side. Once I get the log files I ask about below I will change the status to further. - what kind of Ubuntu version is installed on the Linux computer that works just wine with your headset? Also, could you capture a somewhat more verbose logs. I would love to see at least a HCI trace. You can capture it with sudo btmon --write ~/hcitrace.snoop. Just start it and then try to pair with your headset. Also please do not make the test case really long so that it is easier to understand the output :) Finally please read also https://wiki.ubuntu.com/DebuggingBluetooth to understand how different logs for BT debugging can be captured. Thanks. ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1654782 Title: Can not pair with bluetooth headphones Status in bluez package in Ubuntu: Incomplete Bug description: I can not pair computer and Bluetooth headset (sennheiser momentum 2.0 wireless aebt). (If it matters, I *CAN* pair and use it on another laptop with Linux and with my android smartphone. So headset itself is working well.) Here is how I try to pair: $ bluetoothctl [NEW] Controller 54:27:1E:33:4B:85 impedance [default] [bluetooth]# power on Changing power on succeeded [bluetooth]# agent on Agent registered [bluetooth]# default-agent Default agent request successful [bluetooth]# scan on Discovery started [CHG] Controller 54:27:1E:33:4B:85 Discovering: yes [bluetooth]# scan on I tried to put my headset in pairing mode just before and after issuing "scan on" command. It ends up with nothing - I waited for 3-5 minutes. For example, my smartphone pairs with the headset within 5-15 seconds, my laptop pairs with the headset within about 30 seconds. = Here is info $ hciconfig -a hci0: Type: Primary Bus: USB BD Address: 54:27:1E:33:4B:85 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:4475 acl:0 sco:0 events:565 errors:0 TX bytes:7214 acl:0 sco:0 commands:487 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'impedance' Class: 0x1c0104 Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Desktop workstation HCI Version: 4.0 (0x6) Revision: 0x1000 LMP Version: 4.0 (0x6) Subversion: 0x220e Manufacturer: Broadcom Corporation (15) = rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no = Bluez packages installed: $ dpkg -l | grep bluez ii bluez ii bluez-btsco ii bluez-cups ii bluez-hcidump ii bluez-obexd ii bluez-tools ii libkf5bluezqt-data ii libkf5bluezqt6:amd64 ii qml-module-org-kde-bluezqt:amd64 = $ dmesg | grep -i blue [4.632406] Bluetooth: Core ver 2.21 [4.632414] Bluetooth: HCI device and connection manager initialized [4.632416] Bluetooth: HCI socket layer initialized [4.632417] Bluetooth: L2CAP socket layer initialized [4.632420] Bluetooth: SCO socket layer initialized [4.644619] Bluetooth: hci0: BCM: chip id 63 [4.660554] Bluetooth: hci0: impedance [4.661552] Bluetooth: hci0: BCM20702A1 (001.002.014) build [4.661798] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0b05-17cf.hcd failed with error -2 [4.661799] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0b05-17cf.hcd not found [ 15.061603] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.061604] Bluetooth: BNEP filters: protocol multicast [ 15.061606] Bluetooth: BNEP socket layer initialized [ 48.001553] Bluetooth: RFCOMM TTY layer initialized [ 48.001558] Bluetooth: RFCOMM socket layer initialized [ 48.001562] Bluetooth: RFCOMM ver 1.11 [ 615.404052] Modules linked in: rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack rpcsec_gss_krb5 nfnetlink_queue nfsv4 nfnetlink xt_tcpudp bridge xt_NFQUEUE nfs xt_owner iptable_filter fscache cmac bnep binfmt_misc nls_iso8859_1 intel_rapl edac_core x86_pkg_temp_thermal coretemp btrfs xor snd_hda_codec_hdmi eeepc_wmi asus_wmi sparse_keymap video mxm_wmi raid6_pq btusb btrtl btbcm
[Touch-packages] [Bug 1653314] Re: package bluez:i386 5.37-0ubuntu5 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1
Hey, Could you share some more information about the nature of the failure. Right now I cannot tell what has happened. Thanks ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1653314 Title: package bluez:i386 5.37-0ubuntu5 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 Status in bluez package in Ubuntu: Incomplete Bug description: i can'conekt bluetooth ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bluez:i386 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Fri Dec 30 19:39:34 2016 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 InstallationDate: Installed on 2016-11-29 (31 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) InterestingModules: bnep bluetooth MachineType: To be filled by O.E.M. To be filled by O.E.M. PackageArchitecture: i386 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic root=UUID=fb1fce69-ec71-4461-85dd-690d60245405 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: bluez Title: package bluez:i386 5.37-0ubuntu5 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CROSSHAIR V FORMULA-Z dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1302:bd01/11/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVFORMULA-Z:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. hciconfig: rfkill: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1653314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones
@Wesley You mean with Sony or Bose? -- You received this bug notification because you are a member of Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1283003] Re: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates
** Tags added: papercuts2017 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1283003 Title: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates Status in Blueman: New Status in blueman package in Ubuntu: Fix Released Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: Hi, I found a bug in Ubuntu 14.04 ! I tried to pair a bluetooth stereo headset (A2DP compatible). The pairing process goes well, but after that I can't select it on the audio preferences. When I select it, it only shows the last selected item options and don't do anything. (he should switch to the headset output). I must mention that it worked very well on Ubuntu 12.04. This bug can be in the bluetooth stack or in unity-control-center or maybe pulseaudio. I actually have no idea. To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/1283003/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1546603] Re: Bluetooth mouse connects but doesn't work
** Tags added: papercuts2017 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1546603 Title: Bluetooth mouse connects but doesn't work Status in bluez package in Ubuntu: Confirmed Bug description: I have a bluetooth mouse that I can get to connect via the gnome bluetooth settings panel, but even after it's connected it doesn't move the pointer or register any clicks. the following shows up in the journal : $ $ journalctl -b 0 |grep bluetooth Feb 17 07:18:22 spiny bluetoothd[1009]: Bluetooth daemon 5.36 Feb 17 07:18:22 spiny bluetoothd[1009]: Starting SDP server Feb 17 07:18:22 spiny bluetoothd[1009]: Bluetooth management interface 1.10 initialized Feb 17 07:18:22 spiny bluetoothd[1009]: Failed to obtain handles for "Service Changed" characteristic Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Error adding Link Loss service Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Current Time Service could not be registered Feb 17 07:18:22 spiny bluetoothd[1009]: gatt-time-server: Input/output error (5) Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Sap driver initialization failed. Feb 17 07:18:22 spiny bluetoothd[1009]: sap-server: Operation not permitted (1) Feb 17 07:18:22 spiny NetworkManager[1062]: Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) Feb 17 07:18:24 spiny bluetoothd[1009]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2DPSource Feb 17 07:18:24 spiny bluetoothd[1009]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2DPSink Feb 17 07:18:42 spiny bluetoothd[1009]: Endpoint registered: sender=:1.71 path=/MediaEndpoint/A2DPSource Feb 17 07:18:42 spiny bluetoothd[1009]: Endpoint registered: sender=:1.71 path=/MediaEndpoint/A2DPSink Feb 17 07:18:42 spiny bluetoothd[1009]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98) Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** (gnome-control-center.real:2717): WARNING **: Ignoring launcher gufw (missing desktop file) Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** (gnome-control-center.real:2717): WARNING **: Ignoring launcher landscape-client-settings (missing desktop file) Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** (gnome-control-center.real:2717): WARNING **: Ignoring launcher language-selector (missing desktop file) Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** (gnome-control-center.real:2717): WARNING **: Ignoring launcher ubuntuone-installer (missing desktop file) Feb 17 07:19:00 spiny gnome-bluetooth-panel.desktop[2717]: (gnome-control-center.real:2717): GLib-CRITICAL **: g_ascii_strdown: assertion 'str != NULL' failed Feb 17 07:19:01 spiny bluetoothd[1009]: No cache for F2:3F:5C:A1:F9:F7 Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with handle 0x000c for device F2:3F:5C:A1:F9:F7 Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with handle 0x001b for device F2:3F:5C:A1:F9:F7 Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with handle 0x003f for device F2:3F:5C:A1:F9:F7 Feb 17 07:19:06 spiny bluetoothd[1009]: Report Map read failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Protocol Mode characteristic read failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: HID Information read failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Feb 17 07:19:08 spiny gnome-bluetooth-panel.desktop[2717]: (gnome-control-center.real:2717): GLib-CRITICAL **: g_ascii_strdown: assertion 'str != NULL' failed Feb 17 07:19:08 spiny gnome-bluetooth-panel.desktop[2717]:
[Touch-packages] [Bug 1398193] Re: The bluetooth headset can not control the media playback
** Tags added: papercuts2017 -- You received this bug notification because you are a member of Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1531925] Re: Can't connect Logitech K830 - no PIN prompt [LE]
** Tags added: papercuts2017 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1531925 Title: Can't connect Logitech K830 - no PIN prompt [LE] Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: Cannot connect a Logitech Illuminated Living Room keyboard to a device running bluez5. There are two versions of the keyboard, a unifying receiver version, and a Bluetooth version. The latter has a BT symbol on the 'del' key. To put the BT version in pairing mode, power on the keyboard, then briefly hold the FN and 'del' key together and release. A green LED at the top right of the keyboard should start flashing quickly. Once in pairing mode, the device will become visible on desktop using the BT settings UI, however it's *never* shown in the UI on a device running the latest Touch ( OTA9.1+ ). Note, this includes devices running a silo version of bluez 5.37, including both arale and krillin. On both devices, the keyboard *is* viewable using bluetoothctl. It should be noted that LE keyboard support on touch should be a considered a missing feature. Here's the reported attributes of the device from my macair running 15.10 + bluez 5.37: Device DF:08:A9:A0:13:93 Name: K830 Alias: K830 Appearance: 0x03c1 Icon: input-keyboard Paired: yes Trusted: no Blocked: no Connected: yes LegacyPairing: no UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Device Information (180a--1000-8000-00805f9b34fb) UUID: Battery Service (180f--1000-8000-00805f9b34fb) UUID: Human Interface Device (1812--1000-8000-00805f9b34fb) UUID: Vendor specific (0001--1000-8000-011f246d) Modalias: usb:v046DpB335d0010 From bluetoothctl on both my laptop and my desktop, I'm able to pair, trust and connect the device, and info reflects these changes, however the device never actually connects, it's LED remains blinking fast, and the keyboard cannot be used. Note, before pairing, I issued the command 'agent KeyboardOnly' and 'default-agent'. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1531925/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1454450] Re: Bluetooth mouse laggy and erratic
** Tags added: papercuts2017 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1454450 Title: Bluetooth mouse laggy and erratic Status in bluez package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: I installed Ubuntu 15.04 (64 bit) on a DELL XPS 13 (model 9343, bios A03) notebook. I use a DELL bluetooth mouse but sometimes it behaves erratically (laggy, jumpy). The problem happens after a few (sometimes one) suspend and resume. I am attaching below some info on my system. Thank you. cribari@darwin4:~$ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth Linux darwin4 3.19.0-17-generic #17-Ubuntu SMP Wed May 6 16:46:12 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux 02:00.0 Network controller [0280]: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03) Subsystem: Dell Device [1028:0019] Kernel driver in use: wl Bus 003 Device 002: ID 8087:8001 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:216f Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [2.174367] Bluetooth: Core ver 2.20 [2.174669] Bluetooth: HCI device and connection manager initialized [2.174792] Bluetooth: HCI socket layer initialized [2.174795] Bluetooth: L2CAP socket layer initialized [2.175449] Bluetooth: SCO socket layer initialized [2.592936] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [3.203438] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [3.542418] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [3.542421] Bluetooth: BNEP filters: protocol multicast [3.542425] Bluetooth: BNEP socket layer initialized [3.551641] Bluetooth: RFCOMM TTY layer initialized [3.551649] Bluetooth: RFCOMM socket layer initialized [3.551654] Bluetooth: RFCOMM ver 1.11 [ 26.569283] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 26.569287] Bluetooth: HIDP socket layer initialized [ 26.576971] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0003/input/input15 [ 26.577172] hid-generic 0005:046D:B00E.0003: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 72.448281] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:12/0005:046D:B00E.0004/input/input16 [ 72.448526] hid-generic 0005:046D:B00E.0004: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 2994.842547] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:13/0005:046D:B00E.0005/input/input17 [ 2994.842810] hid-generic 0005:046D:B00E.0005: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 3694.214037] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1000 lmp_ver=06 lmp_subver=220e [ 3694.861578] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [ 3811.777260] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0006/input/input20 [ 3811.777571] hid-generic 0005:046D:B00E.0006: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 5579.876192] Modules linked in: huawei_cdc_ncm cdc_wdm cdc_ncm option usb_wwan usbserial usbnet mii uas usb_storage hid_generic hidp nvram msr binfmt_misc rfcomm bnep nls_iso8859_1 intel_rapl iosf_mbi x86_pkg_temp_thermal dell_wmi sparse_keymap intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul dell_laptop dcdbas btusb crc32_pclmul bluetooth ghash_clmulni_intel hid_multitouch aesni_intel aes_x86_64 lrw uvcvideo gf128mul videobuf2_vmalloc glue_helper wl(POE) videobuf2_memops ablk_helper videobuf2_core cryptd v4l2_common videodev media joydev i915_bpo serio_raw i915 dell_led rtsx_pci_ms intel_ips memstick snd_hda_codec_realtek snd_soc_rt286 snd_hda_codec_generic cfg80211 snd_soc_core drm_kms_helper mei_me lpc_ich shpchp mei snd_compress snd_hda_intel snd_hda_controller drm snd_hda_codec i2c_algo_bit [ 5579.876223] Workqueue: hci0 hci_power_on [bluetooth] [ 5579.876261] [] hci_dev_do_open+0xe1/0xa90 [bluetooth] [ 5579.876266] [] hci_power_on+0x40/0x200 [bluetooth] [ 5579.876284] bluetooth hci0: firmware: brcm/BCM20702A0-0a5c-216f.hcd will not be loaded [ 5579.876286] Bluetooth: hci0: BCM:
[Touch-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety
** Tags added: papercuts2017 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1438510 Title: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety Status in PulseAudio: Unknown Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in bluez source package in Vivid: Won't Fix Status in pulseaudio source package in Vivid: Won't Fix Bug description: Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 The bug is still present in 16.04 LTS and 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1438510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1510570] Re: BLE pairing fail
** Tags added: papercuts2017 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1510570 Title: BLE pairing fail Status in bluez package in Ubuntu: Confirmed Bug description: On 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 And a ppa to test it: https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1510570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607390] Re: serious bug on bluetooth (Ubuntu 16.04 LTS)
** Tags added: papercuts2017 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1607390 Title: serious bug on bluetooth (Ubuntu 16.04 LTS) Status in bluez package in Ubuntu: Confirmed Bug description: I've recently installed ubuntu 16.04 LTS twice -and i discovered that the problem was from the tool katoolin so i didn't install it- after i installed ubuntu the bluetooth didn't work for me. P.S:the bluetooth was working when my laptop was ubuntu 15.04 when i turn bluetooth on to connect my mouse the switch was on but it said that Bluetooth is disabled i entered the command sudo rfkill unblock bluetooth it worked but didn't connect to the mouse even after the next restart i also tried to editing the file /etc/rc.local (putting sudo rfkill unblock bluetooth before last line and restarting) and i've tried **sudo hciconfig hci0 reset** with output > Can't init device hci0: Connection timed out (110) my lsusb; rfkill list output: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 014: ID 04ca:3005 Lite-On Technology Corp. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 04d9:1503 Holtek Semiconductor, Inc. Keyboard Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 0: asus-wlan: Wireless LAN Soft blocked: no Hard blocked: no 1: asus-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 11: hci0: Bluetooth Soft blocked: no Hard blocked: no and output of **dmesg | grep -Ei 'ath3k|blue'** [1.727681] usb 1-1.1: Product: Bluetooth USB Host Controller [ 34.157120] Bluetooth: Core ver 2.21 [ 34.157135] Bluetooth: HCI device and connection manager initialized [ 34.157138] Bluetooth: HCI socket layer initialized [ 34.157140] Bluetooth: L2CAP socket layer initialized [ 34.157145] Bluetooth: SCO socket layer initialized [ 35.604410] usbcore: registered new interface driver ath3k [ 51.744300] usb 1-1.1: Product: Bluetooth USB Host Controller [ 53.810045] Bluetooth: hci0 command 0x0c25 tx timeout [ 55.814079] Bluetooth: hci0 command 0x0c38 tx timeout [ 57.818111] Bluetooth: hci0 command 0x0c39 tx timeout [ 59.822149] Bluetooth: hci0 command 0x0c05 tx timeout [ 66.997548] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 66.997552] Bluetooth: BNEP filters: protocol multicast [ 66.997556] Bluetooth: BNEP socket layer initialized [ 195.105902] usb 1-1.1: Product: Bluetooth USB Host Controller [ 195.328480] Bluetooth: RFCOMM TTY layer initialized [ 195.328488] Bluetooth: RFCOMM socket layer initialized [ 195.328495] Bluetooth: RFCOMM ver 1.11 [ 199.131870] Bluetooth: hci0 command 0x1009 tx timeout [ 276.169130] usb 1-1.1: Product: Bluetooth USB Host Controller [ 294.258992] Bluetooth: hci0 command 0x1005 tx timeout [ 296.263065] Bluetooth: hci0 command 0x0c23 tx timeout [ 298.267076] Bluetooth: hci0 command 0x0c14 tx timeout [ 306.361529] usb 1-1.1: Product: Bluetooth USB Host Controller [ 346.417970] Bluetooth: hci0 command 0x0c56 tx timeout [ 348.421916] Bluetooth: hci0 command 0x0c45 tx timeout [ 350.425782] Bluetooth: hci0 command 0x0c58 tx timeout [ 352.429744] Bluetooth: hci0 command 0x1004 tx timeout [ 366.099802] usb 1-1.1: Product: Bluetooth USB Host Controller [ 368.145218] Bluetooth: hci0 command 0x1001 tx timeout [ 370.149130] Bluetooth: hci0 command 0x1009 tx timeout [ 410.346611] usb 1-1.1: Product: Bluetooth USB Host Controller [ 421.612041] Bluetooth: hci0 command 0x0c23 tx timeout [ 423.616060] Bluetooth: hci0 command 0x0c14 tx timeout [ 425.620018] Bluetooth: hci0 command 0x0c25 tx timeout [ 427.623984] Bluetooth: hci0 command 0x0c38 tx timeout [ 442.650168] usb 1-1.1: Product: Bluetooth USB Host Controller [ 444.727752] Bluetooth: hci0 command 0x0c52 tx timeout [ 446.731800] Bluetooth: hci0 command 0x0c45 tx timeout [ 448.735743] Bluetooth: hci0 command 0x0c58 tx timeout [ 450.739762] Bluetooth: hci0 command 0x1004 tx timeout [ 4000.639722] usb 1-1.1: Product: Bluetooth USB Host Controller [ 4011.801141] Bluetooth: hci0 command 0x2002 tx timeout [ 4013.805106] Bluetooth: hci0 command 0x2003 tx timeout [ 4015.809139] Bluetooth: hci0 command
[Touch-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones
** Tags added: papercuts2017 -- You received this bug notification because you are a member of Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1651433] Re: bluetooth mouse random disconnects
** Tags added: papercuts2017 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1651433 Title: bluetooth mouse random disconnects Status in bluez package in Ubuntu: Confirmed Bug description: I received the Dell XPS 13 DE (9350) accompanied by the WD15 docking station last September. Ever since I used it with my Logitech MX Master bluetooth mouse. This worked very well and reliably for September through November. But Since about start of December, it disconnects frequently and without any apparent reason. I can get it back to order by disabling and re-enabling the bluetooth radio of the notebook. After I re-enable the bt radio and move the mouse it work immediately without any delay. Sometimes it disconnects after 10 seconds. Sometimes I can work for 10 hours without any disconnect. For the entire lifetime the device has been running xenial. Currently I'm on kernel Linux XPS13ulr 4.4.0-53-generic #74-Ubuntu SMP Because the issue started happening at a certain date, I strongly believe that it was caused by and upgrade, possibly kernel. I wanted to see if the same disconnects also happen with other BT devices. But for as long as I had the Jabra Halo 2 headset connected, also the mouse worked reliably. The mouse is my only BT LE device. Maybe that makes a difference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1651433/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
** Tags added: papercuts2017 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: Confirmed Bug description: Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd641.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 Reproduce steps: 1. Install fwts by `sudo apt-get install fwts`. 2. Run the suspend & resume stress test. sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 --s3-delay-delta=5 Expected result: The WiFi still functioned. Actual result: The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again. P.S. Ubuntu 16.04 also has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1653506] [NEW] Not possible to connect to Ubuntu from remote device
Public bug reported: The Ubuntu is not letting the remote device in in case when the remote device is the initiator of the connection request. It drops connection request on the L2CAP level with 'security block' error code. The step-by-step example: 1. Ubuntu pairs & connects to remote device 2. Ubuntu disconnects 3. Remote device tries to reconnect It is seen from the HCI trace that the root cause is the problem in finding the agent that could carry the auth process on. In this case however the agent has been registered previously. The HCI trace: > ACL Data RX: Handle 12 flags 0x02 dlen 12 > > [hci0] 941.214394 L2CAP: Connection Request (0x02) ident 38 len 4 PSM: 25 (0x0019) Source CID: 65 < ACL Data TX: Handle 12 flags 0x00 dlen 16 [hci0] 941.214473 L2CAP: Connection Response (0x03) ident 38 len 8 Destination CID: 64 Source CID: 65 Result: Connection pending (0x0001) Status: Authorization pending (0x0002) = bluetoothd: Authentication attempt without agent [hci0] 941.214871 = bluetoothd: Access denied: org.bluez.Error.Rejected 941.214921 < ACL Data TX: Handle 12 flags 0x00 dlen 16 [hci0] 941.214916 L2CAP: Connection Response (0x03) ident 38 len 8 Destination CID: 64 Source CID: 65 Result: Connection refused - security block (0x0003) Status: No further information available (0x) ** Affects: bluez (Ubuntu) Importance: Undecided Assignee: Konrad Zapałowicz (kzapalowicz) Status: New ** Tags: bluez ** Description changed: The Ubuntu is not letting the remote device in in case when the remote - device is the initiator if the connection request. It drops connection + device is the initiator of the connection request. It drops connection request on the L2CAP level with 'security block' error code. The step-by-step example: 1. Ubuntu pairs & connects to remote device 2. Ubuntu disconnects 3. Remote device tries to reconnect It is seen from the HCI trace that the root cause is the problem in finding the agent that could carry the auth process on. In this case however the agent has been registered previously. The HCI trace: > ACL Data RX: Handle 12 flags 0x02 dlen 12 [hci0] 941.214394 - L2CAP: Connection Request (0x02) ident 38 len 4 - PSM: 25 (0x0019) - Source CID: 65 + L2CAP: Connection Request (0x02) ident 38 len 4 + PSM: 25 (0x0019) + Source CID: 65 < ACL Data TX: Handle 12 flags 0x00 dlen 16 [hci0] 941.214473 - L2CAP: Connection Response (0x03) ident 38 len 8 - Destination CID: 64 - Source CID: 65 - Result: Connection pending (0x0001) - Status: Authorization pending (0x0002) + L2CAP: Connection Response (0x03) ident 38 len 8 + Destination CID: 64 + Source CID: 65 + Result: Connection pending (0x0001) + Status: Authorization pending (0x0002) = bluetoothd: Authentication attempt without agent [hci0] 941.214871 = bluetoothd: Access denied: org.bluez.Error.Rejected 941.214921 < ACL Data TX: Handle 12 flags 0x00 dlen 16 [hci0] 941.214916 - L2CAP: Connection Response (0x03) ident 38 len 8 - Destination CID: 64 - Source CID: 65 - Result: Connection refused - security block (0x0003) - Status: No further information available (0x) + L2CAP: Connection Response (0x03) ident 38 len 8 + Destination CID: 64 + Source CID: 65 + Result: Connection refused - security block (0x0003) + Status: No further information available (0x) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1653506 Title: Not possible to connect to Ubuntu from remote
[Touch-packages] [Bug 1649144] Re: Bluetooth audio quality bad
** Tags added: bluez-touch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1649144 Title: Bluetooth audio quality bad Status in bluez package in Ubuntu: New Bug description: Listening to music using a2dp compatible bt headphones, the audio is bad. Let me explain. If I plug in a pare of headphones with a 3.5 mm stereo plug and compare it to the bluetooth audio, I cannot tell the difference in most devices. I know that a2dp is done with lossy compression, so in theory the audio quality suffers. However, the difference is minimal, something that you can either barely notice, or at times other links in the audio-to-ear chain are way worse masking the quality difference from compression. I have tested this on Android, Debian, Ubuntu etc. and I have to admit that most of the time there appears to be no difference to me. However, on Ubuntu touch (arale OTA-14) there is a difference that any one can notice immediately. The bluetooth audio is really poor, sounds as if it were distoreted and compressed or sample rate lowered or something. Not poor enough to make it unusable but poor enough that you notice it right away. I have no idea what package is causing this, but I suspect that it has something to do with either audio mixer or bluetooth. But everything seems to be OK. AFAIK the audio settings are as I would expect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1649144/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1535829] Re: [bluetooth] "Forget this device" doesn't work if bluetooth off
** Changed in: bluez (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1535829 Title: [bluetooth] "Forget this device" doesn't work if bluetooth off Status in Canonical System Image: Fix Committed Status in bluez package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: Forget this device doesnt' work when BT not on, so should be made to work or less ideally don't display it if BT is off To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1535829/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones
@Alexis, I would like to ask you to register the Sony bug as a new one as this will allow us to track it more efficiently. As for the logs, try sending us syslog with debugging enabled. Instructions on how to capture it are here https://wiki.ubuntu.com/DebuggingBluetooth Also, could you share which Ubuntu version are you using? Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576951] Re: System hangs if apple magic mouse is connected via bluetooth
** Tags added: bluez-touch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1576951 Title: System hangs if apple magic mouse is connected via bluetooth Status in Canonical System Image: Confirmed Status in turbo: New Status in bluez package in Ubuntu: New Bug description: If you connect apple magic mouse via bluetooth the system hangs completely. After 1 minute the system restarts. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1576951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1283003] Re: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates
Hey, @all this is to inform that we are aware of these issues and will be investing time into improving the headsets experience. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1283003 Title: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates Status in Blueman: New Status in blueman package in Ubuntu: Fix Released Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: Hi, I found a bug in Ubuntu 14.04 ! I tried to pair a bluetooth stereo headset (A2DP compatible). The pairing process goes well, but after that I can't select it on the audio preferences. When I select it, it only shows the last selected item options and don't do anything. (he should switch to the headset output). I must mention that it worked very well on Ubuntu 12.04. This bug can be in the bluetooth stack or in unity-control-center or maybe pulseaudio. I actually have no idea. To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/1283003/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1473043] Re: bluetoothd -n consuming 100% after device disconnects
Hey, do you observe such behavior on more recent Ubuntu versions? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1473043 Title: bluetoothd -n consuming 100% after device disconnects Status in bluez package in Ubuntu: Confirmed Bug description: On a regular basis after disconnecting a bluetooth device, usually my headset, the laptop starts to heat up and "/usr/sbin/bluetoothd -n" consumes 100% CPU. A temporary solution is to run "sudo service bluetooth restart". This is bluez 4.101-0ubuntu25 on 15.04 with all updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1473043/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435040] Re: Ubuntu Phone does not connect to car-bluetooth
@Stefan Sorry to hear that it still does not work for you. I imagine that this is frustrating and at the same time please be patient. We are doing serious commitment into improving the overall Bluetooth experience however it takes time due to the complexity of the technology and variety of devices. Best! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1435040 Title: Ubuntu Phone does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488170] Re: Bluetooth initiated after quitting airplane mode
** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1488170 Title: Bluetooth initiated after quitting airplane mode Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Fix Released Status in urfkill package in Ubuntu: Confirmed Bug description: This happens despite bluetooth not being enabled when entering airplane mode. On Aquaris E5 OTA-5. Boot with bluetooth disabled Turn on flight mode turn off flight mode Bluetooth gets enabled See bug #1421249 for related symptoms To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488170/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones
Also worth remembering of: https://developer.bluetooth.org/TechnologyOverview/pages/le- security.aspx -- You received this bug notification because you are a member of Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones
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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones
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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590844] Re: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition
Stefan, as it has been said the bug has slipped through and please accept our apologies for that. For you to know we have prioritized this one over some other story and are struggling to find the resolution. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1590844 Title: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition Status in Canonical System Image: Confirmed Status in turbo: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: My bluetooth headset perfectly connects to my Meizu Pro 5. However, the sound quality is so poor (a lot of noise) such that you don't understand your communication partner. Note that the headset works perfectly together with Ubuntu on my Nexus 4. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1543179] Re: Audio does not get routed to BT headset/speaker
It is not true that the audio is silent because the volume levels are muted. [pulseaudio] module-bluez5-device.c: Failed to set default profile a2dp_sink. Happens because there is a problem acquiring transport due to I/O error -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1543179 Title: Audio does not get routed to BT headset/speaker Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: STEPS: 1. Flash the latest daily rc-proposed image to a phone 2. Connect a bluetooth headset to the phone 3. Connect a speaker to the phone. EXPECTED: I expect the devices to connect and play audio ACTUAL: Speakers just connect and instantly disconnect Headsets don't get trusted and disconnect instantly, Once you trust it and then turn the headset off and back on again it connect can accept calls but the audio from both the mic and earpiece don't function. Image: 242 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1543179/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1543179] Re: Audio does not get routed to BT headset/speaker
paplay produces sound as expected. phablet@ubuntu-phablet:~$ paplay /usr/share/sounds/alsa/Front_Left.wav pactl info before the Bluetooth is disabled then enabled phablet@ubuntu-phablet:~$ pactl info Server String: /run/user/32011/pulse/native Library Protocol Version: 30 Server Protocol Version: 30 Is Local: yes Client Index: 11 Tile Size: 65496 User Name: phablet Host Name: ubuntu-phablet Server Name: pulseaudio Server Version: 6.0 Default Sample Specification: s16le 2ch 44100Hz Default Channel Map: front-left,front-right Default Sink: sink.primary Default Source: source.primary Cookie: 120b:adfe Here Bluetooth is disabled then enabled and the headset connects paplay does not output anything to the speakers after the headset is connected. phablet@ubuntu-phablet:~$ paplay /usr/share/sounds/alsa/Front_Left.wav pactl info after the Bluetooth is disabled then enabled phablet@ubuntu-phablet:~$ pactl info Server String: /run/user/32011/pulse/native Library Protocol Version: 30 Server Protocol Version: 30 Is Local: yes Client Index: 13 Tile Size: 65496 User Name: phablet Host Name: ubuntu-phablet Server Name: pulseaudio Server Version: 6.0 Default Sample Specification: s16le 2ch 44100Hz Default Channel Map: front-left,front-right Default Sink: sink.primary Default Source: source.primary Cookie: 120b:adfe phablet@ubuntu-phablet:~$ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1543179 Title: Audio does not get routed to BT headset/speaker Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: STEPS: 1. Flash the latest daily rc-proposed image to a phone 2. Connect a bluetooth headset to the phone 3. Connect a speaker to the phone. EXPECTED: I expect the devices to connect and play audio ACTUAL: Speakers just connect and instantly disconnect Headsets don't get trusted and disconnect instantly, Once you trust it and then turn the headset off and back on again it connect can accept calls but the audio from both the mic and earpiece don't function. Image: 242 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1543179/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1543179] Re: Audio does not get routed to BT headset/speaker
When tested with a2dp music such as mp3 playback the following scenario works as expected, i.e. the audio is transferred to the correct output: connect BT headset play music disable BT (audio is transferred to the phone and paused) enable BT (playing audio is transferred to the headset that connects automatically) On the other hand, the same steps fail to produce any audio in step 4 [through both phone speakers and headset] if it is call audio instead of a2dp. Perhaps ofono is breaking the way the streams are set up for subsequent connections. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1543179 Title: Audio does not get routed to BT headset/speaker Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: STEPS: 1. Flash the latest daily rc-proposed image to a phone 2. Connect a bluetooth headset to the phone 3. Connect a speaker to the phone. EXPECTED: I expect the devices to connect and play audio ACTUAL: Speakers just connect and instantly disconnect Headsets don't get trusted and disconnect instantly, Once you trust it and then turn the headset off and back on again it connect can accept calls but the audio from both the mic and earpiece don't function. Image: 242 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1543179/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590844] Re: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition
I have tested flyme version of Android on Pro5 and the sound is good. Also I have tested the Ubuntu version with the same .hcd config that is being used by the flyme - sound is bad. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1590844 Title: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition Status in Canonical System Image: Confirmed Status in turbo: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: My bluetooth headset perfectly connects to my Meizu Pro 5. However, the sound quality is so poor (a lot of noise) such that you don't understand your communication partner. Note that the headset works perfectly together with Ubuntu on my Nexus 4. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590844] Re: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition
I have tried the Bluetooth chip firmware embedded in updates as on this page http://www.flymeos.com/firmwarelist?modelId=10=1 and the .hcd file there is exact the same that we already have on Ubuntu enabled Pro5. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1590844 Title: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition Status in Canonical System Image: Confirmed Status in turbo: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: My bluetooth headset perfectly connects to my Meizu Pro 5. However, the sound quality is so poor (a lot of noise) such that you don't understand your communication partner. Note that the headset works perfectly together with Ubuntu on my Nexus 4. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590844] Re: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition
I've spent time debugging this and it looks like the problem is with the BT chip firmware that potentially contains not ideal parameters. I've also captured an audio sample directly from pcm and the sound is clear at the beginning however the quality decreases over time with the noise overtaking the voice eventually [like the noise volume increases step by step]. At the same time the voice through BT headset is polluted with the noise from the beginning. I have also used a different firmware for the BT chip and as it produced no audio at all through the BT it has also made the pcm record perfectly clean from the beginning till the end. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1590844 Title: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition Status in Canonical System Image: Confirmed Status in turbo: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: My bluetooth headset perfectly connects to my Meizu Pro 5. However, the sound quality is so poor (a lot of noise) such that you don't understand your communication partner. Note that the headset works perfectly together with Ubuntu on my Nexus 4. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435040] Re: Ubuntu Phone does not connect to car-bluetooth
For you to know a fix for in-car Bluetooth that addresses the pairing problems when pairing is initiated by the car will be released in OTA13 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1435040 Title: Ubuntu Phone does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
Hey, we are releasing the major update to the Bluetooth for our phones with OTA13. First there is an updated BlueZ version; second there is a fix for in-car Bluetooth in a situation where the pairing has been initiated by the device [not the phone]. @Stefan I understand your frustration however let me assure you that we are struggling to get things right with Bluetooth however we need to take things bit by bit and first we've tackled the pairing problems. The others will come next. -- You received this bug notification because you are a member of Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
For you to know that silo has landed and will be a part of OTA13 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Hey, Silo 46 is next in queue to land just needs a little bit of tweaking after the recent landings of Ubuntu System Settings. I expect it to be the part of OTA13. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1490347] Re: [Regression] 16:04 + 15:10 - Cannot pair with devices using (legacy LMP Link Management Protocol) PIN codes
Right, I'll find out. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1490347 Title: [Regression] 16:04 + 15:10 - Cannot pair with devices using (legacy LMP Link Management Protocol) PIN codes Status in Bluez Utilities: New Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in bluez package in Ubuntu: Triaged Status in bluez source package in Wily: Triaged Status in bluez source package in Xenial: Confirmed Bug description: Bluez 5.3 does not have support for pairing with devices (such as keyboards) that use a PIN code for pairing. A mouse pairs correctly. From my research it seems as if the ChromeOS project developed patches to fix this and they are supposed to have been included in Bluez 5.4 (that statement dated April 2013) but I've not yet identified them. "The agent's implementation in bt_console/bluetoothctl upstream is incomplete, missing some functions like DisplayPincode." https://code.google.com/p/chromium/issues/detail?id=222661 Along with the loss of Headset profiles meaning VoIP applications can no longer use HSP/HFP profiles (requiring functionality yet to land in Ofono) this cripples the use of Bluetooth for much else than A2DP or mouse input. Attempting to pair with, for example, an Apple Wireless Keyboard that pairs and works correctly with 14.04 LTS, fails totally on 15.10. The mouse shown below is already paired, connected, and working. $ bluetoothctl [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse [bluetooth]# agent on Agent registered [bluetooth]# default-agent Default agent request successful [bluetooth]# scan on Discovery started [CHG] Controller 00:1F:3A:E0:0A:AF Discovering: yes [CHG] Device 00:0A:95:4B:BD:C2 LegacyPairing: yes [CHG] Device 00:0A:95:4B:BD:C2 RSSI: -48 [bluetooth]# pair 00:0A:95:4B:BD:C2 Attempting to pair with 00:0A:95:4B:BD:C2 >>> at this point nothing is happening >>> so I press Enter on the keyboard and... [agent] PIN code: 791166 >>> I type 791166 Enter and ... [agent] PIN code: 237744 >>> I type 237744 Enter and... [agent] PIN code: 358866 >>> I type 358866 Enter and... Request PIN code [agent] Enter PIN code: 1234 >>> I type 1234 Enter on the keyboard and 1234 at the prompt... Failed to pair: org.bluez.Error.AuthenticationFailed This cycle repeats in various permuations. Sometimes the final "Request PIN code" does not appear. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1490347/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Hey, We might have fix for issues where the pairing is initiated by the car. It is currently in silo 46 and we are working towards including it in the next OTA update. Best, Konrad -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1572577] Re: Can't pair with a Volvo car kit
*** This bug is a duplicate of bug 1539158 *** https://bugs.launchpad.net/bugs/1539158 There is a high chance that silo 46 contains fix for this bug -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1572577 Title: Can't pair with a Volvo car kit Status in bluez package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Bug description: For a while now I'm unable to pair with my car kit. It's a reverse- pair procedure, so the car is trying to initiate the pairing, shows the PIN to enter and goes "failed" - with the phone never showing anything. Syslog shows, possibly relevant: Apr 20 15:21:40 ubuntu-phablet bluetoothd[891]: src/device.c:new_auth() Requesting agent authentication for 00:1A:77:F6:D5:2B [...] Apr 20 15:21:40 ubuntu-phablet bluetoothd[891]: Agent /com/canonical/SettingsBluetoothAgent/adapteragent replied with an error: org.bluez.Error.Rejected, The request was rejected: RequestPinCode [...] Apr 20 15:21:40 ubuntu-phablet bluetoothd[891]: src/device.c:device_cancel_authentication() Canceling authentication request for 00:1A:77:F6:D5:2B Please find logs, as directed by https://wiki.ubuntu.com/DebuggingBluetooth, attached. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ubuntu-system-settings 0.3+15.04.20160407-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] Uname: Linux 3.4.67 armv7l ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf Date: Wed Apr 20 15:31:32 2016 InstallationDate: Installed on 2016-04-14 (6 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20160414-020305) SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2016-04-14 (6 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20160414-020305) Lsusb: Error: [Errno 2] No such file or directory Package: bluez 5.37-0ubuntu5~overlay1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] PackageArchitecture: armhf ProcKernelCmdLine: console=ttyMT0,921600n1 vmalloc=496M slub_max_order=0 fixrtc lcm=1-hx8389_qhd_dsi_vdo_truly fps=6657 bootprof.pl_t=511 bootprof.lk_t=1724 printk.disable_uart=1 boot_reason=4 datapart=/dev/mmcblk0p7 systempart=/dev/mmcblk0p6 androidboot.serialno=JB011540 � lcm=1-hx8389_qhd_dsi_vdo_truly fps=6657 bootprof.pl_t=511 bootprof.lk_t=1724 printk.disable_uart=1 boot_reason=4 datapart=/dev/mmcblk0p7 systempart=/dev/mmcblk0p6 androidboot.serialno=JB011540 � ProcModules: Tags: vivid third-party-packages UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.4.67 armv7l UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip plugdev sudo tty video _MarkForUpload: True hciconfig: hci0:Type: BR/EDR Bus: UART BD Address: B8:64:91:48:2B:21 ACL MTU: 1021:4 SCO MTU: 184:1 UP RUNNING PSCAN RX bytes:4361 acl:59 sco:0 events:213 errors:0 TX bytes:6120 acl:60 sco:0 commands:131 errors:0 modified.conffile..etc.init.bluetooth.conf: [modified] mtime.conffile..etc.init.bluetooth.conf: 2016-04-20T15:11:43.487387 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1572577/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590844] Re: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition
Hey, @Stefan the best would be providing the Bluetooth and PulseAudio logs. These are part of the syslog however you need to configure them both to be verbose. Here https://wiki.ubuntu.com/DebuggingBluetooth you can learn how to do it. Let me know if you have further questions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1590844 Title: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition Status in Canonical System Image: Confirmed Status in turbo: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: My bluetooth headset perfectly connects to my Meizu Pro 5. However, the sound quality is so poor (a lot of noise) such that you don't understand your communication partner. Note that the headset works perfectly together with Ubuntu on my Nexus 4. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Marco, this is super strange, I will think of possible solutions however in the meantime what is the output from info 60:38:0E:59:32:39 Thanks, K On Fri, Jul 29, 2016 at 12:40 PM, Marco Graziotti <graziottima...@gmail.com> wrote: > Hi Konrad, > > I tried to remove the "Nissan Connect" device, but i got this error: "*Failed > to remove device: org.bluez.Error.NotReady*". > Here you can read what I'm doing: > > *user@user-laptop:~$ adb shell* > * daemon not running. starting it now on port 5037 * > * daemon started successfully * > > phablet@ubuntu-phablet:~$ $ bluetoothctl > bash: $: command not found > > *phablet@ubuntu-phablet:~$ bluetoothctl* > [NEW] Controller 38:BC:1A:29:69:4B MX4 Ubuntu Edition [default] > [NEW] Device 90:F1:AA:7B:80:0F [Samsung] Soundbar > [NEW] Device 60:38:0E:59:32:39 NISSAN CONNECT > > *[bluetooth]# devices* > Device 90:F1:AA:7B:80:0F [Samsung] Soundbar > Device 60:38:0E:59:32:39 NISSAN CONNECT > > *[bluetooth]# remove 60:38:0E:59:32:39* > *Failed to remove device: org.bluez.Error.NotReady* > > What can I do? > > Thank you > > > Il 28/07/2016 10:54, Konrad Zapałowicz ha scritto: > > Hey, > > I'll try to help a bit here. > > First as for the unknown or unwanted entries on the paired devices lists > [and such] you can try to remove them from the bluetoothctl level. > > ) enable developers mode & connect it via usb cable > ) login with adb shell to the deivce > ) type $ bluetoothctl > ) then type: devices - to list the known devices > ) to remove type: remove $BDADDR - where BDADDR is a Bluetooth address of the > device [not it's name] > > Second we are in the of releasing the newest bluez 5.41 which is now in > silo 37. If you are familiar with installing silos on your device you > can try it out and check if it improves anything. It includes fixes for > link management and pairing therefore there is a chance [although not > certain] that there might be joy. > > If unsure please ask. > > Best, > Konrad > > > > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
What is your phone? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Hey, the procedure is not very difficult and once all the tools are installed it is straightforward however if you do not feel confident, given that it is not certain that it will help for issues with cars, I would recommend waiting till OTA-13. Best, Konrad On Thu, Jul 28, 2016 at 1:05 PM, Marco Graziotti <graziottima...@gmail.com> wrote: > Hi Konrad, > > thank you for your answer, I will try to apply the procedure that you have > described during this weekend. > I never installed a silos, so maybe it's better to wait the OTA-13 that > incude bluez 5.41. > > Thank you, > Marco > > Il 28/07/2016 10:54, Konrad Zapałowicz ha scritto: > >> Hey, >> >> I'll try to help a bit here. >> >> First as for the unknown or unwanted entries on the paired devices lists >> [and such] you can try to remove them from the bluetoothctl level. >> >> ) enable developers mode & connect it via usb cable >> ) login with adb shell to the deivce >> ) type $ bluetoothctl >> ) then type: devices - to list the known devices >> ) to remove type: remove $BDADDR - where BDADDR is a Bluetooth address of >> the device [not it's name] >> >> Second we are in the of releasing the newest bluez 5.41 which is now in >> silo 37. If you are familiar with installing silos on your device you >> can try it out and check if it improves anything. It includes fixes for >> link management and pairing therefore there is a chance [although not >> certain] that there might be joy. >> >> If unsure please ask. >> >> Best, >> Konrad >> >> > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Hey, I'll try to help a bit here. First as for the unknown or unwanted entries on the paired devices lists [and such] you can try to remove them from the bluetoothctl level. ) enable developers mode & connect it via usb cable ) login with adb shell to the deivce ) type $ bluetoothctl ) then type: devices - to list the known devices ) to remove type: remove $BDADDR - where BDADDR is a Bluetooth address of the device [not it's name] Second we are in the of releasing the newest bluez 5.41 which is now in silo 37. If you are familiar with installing silos on your device you can try it out and check if it improves anything. It includes fixes for link management and pairing therefore there is a chance [although not certain] that there might be joy. If unsure please ask. Best, Konrad -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1531925] Re: Can't connect Logitech K830 - no PIN prompt [LE]
@Pat you may want to try silo 60 - it shall enable displaying BLE devices on the u-s-s level. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1531925 Title: Can't connect Logitech K830 - no PIN prompt [LE] Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: Cannot connect a Logitech Illuminated Living Room keyboard to a device running bluez5. There are two versions of the keyboard, a unifying receiver version, and a Bluetooth version. The latter has a BT symbol on the 'del' key. To put the BT version in pairing mode, power on the keyboard, then briefly hold the FN and 'del' key together and release. A green LED at the top right of the keyboard should start flashing quickly. Once in pairing mode, the device will become visible on desktop using the BT settings UI, however it's *never* shown in the UI on a device running the latest Touch ( OTA9.1+ ). Note, this includes devices running a silo version of bluez 5.37, including both arale and krillin. On both devices, the keyboard *is* viewable using bluetoothctl. It should be noted that LE keyboard support on touch should be a considered a missing feature. Here's the reported attributes of the device from my macair running 15.10 + bluez 5.37: Device DF:08:A9:A0:13:93 Name: K830 Alias: K830 Appearance: 0x03c1 Icon: input-keyboard Paired: yes Trusted: no Blocked: no Connected: yes LegacyPairing: no UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Device Information (180a--1000-8000-00805f9b34fb) UUID: Battery Service (180f--1000-8000-00805f9b34fb) UUID: Human Interface Device (1812--1000-8000-00805f9b34fb) UUID: Vendor specific (0001--1000-8000-011f246d) Modalias: usb:v046DpB335d0010 From bluetoothctl on both my laptop and my desktop, I'm able to pair, trust and connect the device, and info reflects these changes, however the device never actually connects, it's LED remains blinking fast, and the keyboard cannot be used. Note, before pairing, I issued the command 'agent KeyboardOnly' and 'default-agent'. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1531925/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1490347] Re: [Regression] 16:04 + 15:10 - Cannot pair with devices using (legacy LMP Link Management Protocol) PIN codes
Hey, could you retest with silo 68 installed? Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1490347 Title: [Regression] 16:04 + 15:10 - Cannot pair with devices using (legacy LMP Link Management Protocol) PIN codes Status in Bluez Utilities: New Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in bluez package in Ubuntu: Triaged Status in bluez source package in Wily: Triaged Status in bluez source package in Xenial: Confirmed Bug description: Bluez 5.3 does not have support for pairing with devices (such as keyboards) that use a PIN code for pairing. A mouse pairs correctly. From my research it seems as if the ChromeOS project developed patches to fix this and they are supposed to have been included in Bluez 5.4 (that statement dated April 2013) but I've not yet identified them. "The agent's implementation in bt_console/bluetoothctl upstream is incomplete, missing some functions like DisplayPincode." https://code.google.com/p/chromium/issues/detail?id=222661 Along with the loss of Headset profiles meaning VoIP applications can no longer use HSP/HFP profiles (requiring functionality yet to land in Ofono) this cripples the use of Bluetooth for much else than A2DP or mouse input. Attempting to pair with, for example, an Apple Wireless Keyboard that pairs and works correctly with 14.04 LTS, fails totally on 15.10. The mouse shown below is already paired, connected, and working. $ bluetoothctl [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse [bluetooth]# agent on Agent registered [bluetooth]# default-agent Default agent request successful [bluetooth]# scan on Discovery started [CHG] Controller 00:1F:3A:E0:0A:AF Discovering: yes [CHG] Device 00:0A:95:4B:BD:C2 LegacyPairing: yes [CHG] Device 00:0A:95:4B:BD:C2 RSSI: -48 [bluetooth]# pair 00:0A:95:4B:BD:C2 Attempting to pair with 00:0A:95:4B:BD:C2 >>> at this point nothing is happening >>> so I press Enter on the keyboard and... [agent] PIN code: 791166 >>> I type 791166 Enter and ... [agent] PIN code: 237744 >>> I type 237744 Enter and... [agent] PIN code: 358866 >>> I type 358866 Enter and... Request PIN code [agent] Enter PIN code: 1234 >>> I type 1234 Enter on the keyboard and 1234 at the prompt... Failed to pair: org.bluez.Error.AuthenticationFailed This cycle repeats in various permuations. Sometimes the final "Request PIN code" does not appear. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1490347/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1557298] Re: [Xenial][Bluez5] Low Energy Keyboard is paired incorrectly
Just have tested with silo 68 installed and I'm able to pair and connect & use the MS Designer Keyboard quite smoothly. Could you retest with silo 68 installed and let me know how it is on your end, thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1557298 Title: [Xenial][Bluez5] Low Energy Keyboard is paired incorrectly Status in Unity Control Center: New Status in bluez package in Ubuntu: New Bug description: Failed to pair low energy(bluetooth smart, 4.0) keyboard correctly. Bluetooth smart keyboard is unable to use after bluetooth-wizard says "OK". Also the passcode input is also not acting interactively like when pairing with bluetooth 3.0(LegacyPairing) keyboard. Above scenario also being verified with bluetoothctl and blueman. Step to reproduce: 1. open Bluetooth Settings 2. click on Add New Device button 3. select the bluetooth le keyboard 4. input the passcode display on GUI Expected result: After bluetooth-wizard telling user is okay the keyboard should work Actual result: Pairing mode stop on keyboard, but still not work. - More details about versions: Environment: xenial daily (20160307) bluez 5.37-0ubuntu5 gnome-bluetooth 3.18.2-1ubuntu2 blueman 2.0.3-1ubuntu1 bluetooth controller 0cf3:e005 Atheros Communications, Inc. (hci version: 4.1) Tested devices: Designer Mouse, bluetooth smart (pairable, work, re-pair work) Designer Keyboard, bluetooth smart (paired, not working) BT3.0 keyboard, bluetooth classic (pair and work) BT3.0 mouse, bluetooth classic (pair and work) - In control environment with the same hardware system and devices: trusty 14.04.1 + dist-upgrade (stay with 3.13 kernel) bluez5 5.35 (ppa: https://launchpad.net/~vidplace7/+archive/ubuntu/bluez5) It works with all above devices but can only be pairing through bluetoothctl manually, since the older bluetooth-wizard does not understand bluez 5.x. Everything seems works fine, although there are a lot more error messages, but since this bug is more about xenial, please let me know if we need more information about this, I'm able to reproduce this trusty scenario in anytime. - Additional note: A little clarification, since I'm not sure how far the Bluetooth SIG is going to use Bluetooth Smart(Low Energy, or even Smart-Ready) to cover the versioning, I decided to just use what ever I saw on the product box. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 15 11:40:12 2016 InstallationDate: Installed on 2016-03-14 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Latitude E5550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic.efi.signed root=UUID=1079eca4-4293-4e51-ba0e-84f7d681cb2c ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0141B2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/18/2015:svnDellInc.:pnLatitudeE5550:pvr:rvnDellInc.:rn0141B2:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5550 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:71:CC:39:BD:22 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:862538 acl:39687 sco:0 events:2668 errors:0 TX bytes:26235 acl:904 sco:0 commands:1021 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/unity-control-center/+bug/1557298/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1454450] Re: Bluetooth mouse laggy and erratic
Hey, I have checked with our hardware team and it seems the Intel error that you are experiencing should have nothing to do with Bluetooth performance. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1454450 Title: Bluetooth mouse laggy and erratic Status in bluez package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: I installed Ubuntu 15.04 (64 bit) on a DELL XPS 13 (model 9343, bios A03) notebook. I use a DELL bluetooth mouse but sometimes it behaves erratically (laggy, jumpy). The problem happens after a few (sometimes one) suspend and resume. I am attaching below some info on my system. Thank you. cribari@darwin4:~$ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth Linux darwin4 3.19.0-17-generic #17-Ubuntu SMP Wed May 6 16:46:12 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux 02:00.0 Network controller [0280]: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03) Subsystem: Dell Device [1028:0019] Kernel driver in use: wl Bus 003 Device 002: ID 8087:8001 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:216f Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [2.174367] Bluetooth: Core ver 2.20 [2.174669] Bluetooth: HCI device and connection manager initialized [2.174792] Bluetooth: HCI socket layer initialized [2.174795] Bluetooth: L2CAP socket layer initialized [2.175449] Bluetooth: SCO socket layer initialized [2.592936] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [3.203438] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [3.542418] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [3.542421] Bluetooth: BNEP filters: protocol multicast [3.542425] Bluetooth: BNEP socket layer initialized [3.551641] Bluetooth: RFCOMM TTY layer initialized [3.551649] Bluetooth: RFCOMM socket layer initialized [3.551654] Bluetooth: RFCOMM ver 1.11 [ 26.569283] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 26.569287] Bluetooth: HIDP socket layer initialized [ 26.576971] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0003/input/input15 [ 26.577172] hid-generic 0005:046D:B00E.0003: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 72.448281] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:12/0005:046D:B00E.0004/input/input16 [ 72.448526] hid-generic 0005:046D:B00E.0004: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 2994.842547] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:13/0005:046D:B00E.0005/input/input17 [ 2994.842810] hid-generic 0005:046D:B00E.0005: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 3694.214037] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1000 lmp_ver=06 lmp_subver=220e [ 3694.861578] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [ 3811.777260] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0006/input/input20 [ 3811.777571] hid-generic 0005:046D:B00E.0006: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 5579.876192] Modules linked in: huawei_cdc_ncm cdc_wdm cdc_ncm option usb_wwan usbserial usbnet mii uas usb_storage hid_generic hidp nvram msr binfmt_misc rfcomm bnep nls_iso8859_1 intel_rapl iosf_mbi x86_pkg_temp_thermal dell_wmi sparse_keymap intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul dell_laptop dcdbas btusb crc32_pclmul bluetooth ghash_clmulni_intel hid_multitouch aesni_intel aes_x86_64 lrw uvcvideo gf128mul videobuf2_vmalloc glue_helper wl(POE) videobuf2_memops ablk_helper videobuf2_core cryptd v4l2_common videodev media joydev i915_bpo serio_raw i915 dell_led rtsx_pci_ms intel_ips memstick snd_hda_codec_realtek snd_soc_rt286 snd_hda_codec_generic cfg80211 snd_soc_core drm_kms_helper mei_me lpc_ich shpchp mei snd_compress snd_hda_intel snd_hda_controller drm snd_hda_codec i2c_algo_bit [ 5579.876223] Workqueue: hci0 hci_power_on [bluetooth] [ 5579.876261] [] hci_dev_do_open+0xe1/0xa90 [bluetooth] [ 5579.876266] [] hci_power_on+0x40/0x200 [bluetooth] [
[Touch-packages] [Bug 1454450] Re: Bluetooth mouse laggy and erratic
** Attachment added: "Syslog as recieved from the reporter" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1454450/+attachment/4692716/+files/syslog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1454450 Title: Bluetooth mouse laggy and erratic Status in bluez package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: I installed Ubuntu 15.04 (64 bit) on a DELL XPS 13 (model 9343, bios A03) notebook. I use a DELL bluetooth mouse but sometimes it behaves erratically (laggy, jumpy). The problem happens after a few (sometimes one) suspend and resume. I am attaching below some info on my system. Thank you. cribari@darwin4:~$ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth Linux darwin4 3.19.0-17-generic #17-Ubuntu SMP Wed May 6 16:46:12 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux 02:00.0 Network controller [0280]: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03) Subsystem: Dell Device [1028:0019] Kernel driver in use: wl Bus 003 Device 002: ID 8087:8001 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:216f Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [2.174367] Bluetooth: Core ver 2.20 [2.174669] Bluetooth: HCI device and connection manager initialized [2.174792] Bluetooth: HCI socket layer initialized [2.174795] Bluetooth: L2CAP socket layer initialized [2.175449] Bluetooth: SCO socket layer initialized [2.592936] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [3.203438] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [3.542418] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [3.542421] Bluetooth: BNEP filters: protocol multicast [3.542425] Bluetooth: BNEP socket layer initialized [3.551641] Bluetooth: RFCOMM TTY layer initialized [3.551649] Bluetooth: RFCOMM socket layer initialized [3.551654] Bluetooth: RFCOMM ver 1.11 [ 26.569283] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 26.569287] Bluetooth: HIDP socket layer initialized [ 26.576971] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0003/input/input15 [ 26.577172] hid-generic 0005:046D:B00E.0003: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 72.448281] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:12/0005:046D:B00E.0004/input/input16 [ 72.448526] hid-generic 0005:046D:B00E.0004: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 2994.842547] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:13/0005:046D:B00E.0005/input/input17 [ 2994.842810] hid-generic 0005:046D:B00E.0005: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 3694.214037] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1000 lmp_ver=06 lmp_subver=220e [ 3694.861578] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [ 3811.777260] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0006/input/input20 [ 3811.777571] hid-generic 0005:046D:B00E.0006: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 5579.876192] Modules linked in: huawei_cdc_ncm cdc_wdm cdc_ncm option usb_wwan usbserial usbnet mii uas usb_storage hid_generic hidp nvram msr binfmt_misc rfcomm bnep nls_iso8859_1 intel_rapl iosf_mbi x86_pkg_temp_thermal dell_wmi sparse_keymap intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul dell_laptop dcdbas btusb crc32_pclmul bluetooth ghash_clmulni_intel hid_multitouch aesni_intel aes_x86_64 lrw uvcvideo gf128mul videobuf2_vmalloc glue_helper wl(POE) videobuf2_memops ablk_helper videobuf2_core cryptd v4l2_common videodev media joydev i915_bpo serio_raw i915 dell_led rtsx_pci_ms intel_ips memstick snd_hda_codec_realtek snd_soc_rt286 snd_hda_codec_generic cfg80211 snd_soc_core drm_kms_helper mei_me lpc_ich shpchp mei snd_compress snd_hda_intel snd_hda_controller drm snd_hda_codec i2c_algo_bit [ 5579.876223] Workqueue: hci0 hci_power_on [bluetooth] [ 5579.876261] [] hci_dev_do_open+0xe1/0xa90 [bluetooth] [ 5579.876266] [] hci_power_on+0x40/0x200 [bluetooth]
[Touch-packages] [Bug 1454450] Re: Bluetooth mouse laggy and erratic
** Attachment added: "Syslog as recieved from the reporter" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1454450/+attachment/4692717/+files/syslog.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1454450 Title: Bluetooth mouse laggy and erratic Status in bluez package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: I installed Ubuntu 15.04 (64 bit) on a DELL XPS 13 (model 9343, bios A03) notebook. I use a DELL bluetooth mouse but sometimes it behaves erratically (laggy, jumpy). The problem happens after a few (sometimes one) suspend and resume. I am attaching below some info on my system. Thank you. cribari@darwin4:~$ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth Linux darwin4 3.19.0-17-generic #17-Ubuntu SMP Wed May 6 16:46:12 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux 02:00.0 Network controller [0280]: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03) Subsystem: Dell Device [1028:0019] Kernel driver in use: wl Bus 003 Device 002: ID 8087:8001 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:216f Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [2.174367] Bluetooth: Core ver 2.20 [2.174669] Bluetooth: HCI device and connection manager initialized [2.174792] Bluetooth: HCI socket layer initialized [2.174795] Bluetooth: L2CAP socket layer initialized [2.175449] Bluetooth: SCO socket layer initialized [2.592936] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [3.203438] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [3.542418] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [3.542421] Bluetooth: BNEP filters: protocol multicast [3.542425] Bluetooth: BNEP socket layer initialized [3.551641] Bluetooth: RFCOMM TTY layer initialized [3.551649] Bluetooth: RFCOMM socket layer initialized [3.551654] Bluetooth: RFCOMM ver 1.11 [ 26.569283] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 26.569287] Bluetooth: HIDP socket layer initialized [ 26.576971] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0003/input/input15 [ 26.577172] hid-generic 0005:046D:B00E.0003: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 72.448281] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:12/0005:046D:B00E.0004/input/input16 [ 72.448526] hid-generic 0005:046D:B00E.0004: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 2994.842547] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:13/0005:046D:B00E.0005/input/input17 [ 2994.842810] hid-generic 0005:046D:B00E.0005: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 3694.214037] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1000 lmp_ver=06 lmp_subver=220e [ 3694.861578] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [ 3811.777260] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0006/input/input20 [ 3811.777571] hid-generic 0005:046D:B00E.0006: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 5579.876192] Modules linked in: huawei_cdc_ncm cdc_wdm cdc_ncm option usb_wwan usbserial usbnet mii uas usb_storage hid_generic hidp nvram msr binfmt_misc rfcomm bnep nls_iso8859_1 intel_rapl iosf_mbi x86_pkg_temp_thermal dell_wmi sparse_keymap intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul dell_laptop dcdbas btusb crc32_pclmul bluetooth ghash_clmulni_intel hid_multitouch aesni_intel aes_x86_64 lrw uvcvideo gf128mul videobuf2_vmalloc glue_helper wl(POE) videobuf2_memops ablk_helper videobuf2_core cryptd v4l2_common videodev media joydev i915_bpo serio_raw i915 dell_led rtsx_pci_ms intel_ips memstick snd_hda_codec_realtek snd_soc_rt286 snd_hda_codec_generic cfg80211 snd_soc_core drm_kms_helper mei_me lpc_ich shpchp mei snd_compress snd_hda_intel snd_hda_controller drm snd_hda_codec i2c_algo_bit [ 5579.876223] Workqueue: hci0 hci_power_on [bluetooth] [ 5579.876261] [] hci_dev_do_open+0xe1/0xa90 [bluetooth] [ 5579.876266] [] hci_power_on+0x40/0x200 [bluetooth]
[Touch-packages] [Bug 1454450] Re: Bluetooth mouse laggy and erratic
Thanks. The keyboard that yo use is a Bluetooth Classic one and we do not have much issues with those. Of course, there are high chances that we have not been performing our tests using the same model that you use but just for you to know that the issues with BT Classic are something unusual. I will check if we are able to link the Intel error to the performance penalty. Best -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1454450 Title: Bluetooth mouse laggy and erratic Status in bluez package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: I installed Ubuntu 15.04 (64 bit) on a DELL XPS 13 (model 9343, bios A03) notebook. I use a DELL bluetooth mouse but sometimes it behaves erratically (laggy, jumpy). The problem happens after a few (sometimes one) suspend and resume. I am attaching below some info on my system. Thank you. cribari@darwin4:~$ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth Linux darwin4 3.19.0-17-generic #17-Ubuntu SMP Wed May 6 16:46:12 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux 02:00.0 Network controller [0280]: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03) Subsystem: Dell Device [1028:0019] Kernel driver in use: wl Bus 003 Device 002: ID 8087:8001 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:216f Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [2.174367] Bluetooth: Core ver 2.20 [2.174669] Bluetooth: HCI device and connection manager initialized [2.174792] Bluetooth: HCI socket layer initialized [2.174795] Bluetooth: L2CAP socket layer initialized [2.175449] Bluetooth: SCO socket layer initialized [2.592936] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [3.203438] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [3.542418] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [3.542421] Bluetooth: BNEP filters: protocol multicast [3.542425] Bluetooth: BNEP socket layer initialized [3.551641] Bluetooth: RFCOMM TTY layer initialized [3.551649] Bluetooth: RFCOMM socket layer initialized [3.551654] Bluetooth: RFCOMM ver 1.11 [ 26.569283] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 26.569287] Bluetooth: HIDP socket layer initialized [ 26.576971] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0003/input/input15 [ 26.577172] hid-generic 0005:046D:B00E.0003: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 72.448281] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:12/0005:046D:B00E.0004/input/input16 [ 72.448526] hid-generic 0005:046D:B00E.0004: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 2994.842547] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:13/0005:046D:B00E.0005/input/input17 [ 2994.842810] hid-generic 0005:046D:B00E.0005: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 3694.214037] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1000 lmp_ver=06 lmp_subver=220e [ 3694.861578] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [ 3811.777260] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0006/input/input20 [ 3811.777571] hid-generic 0005:046D:B00E.0006: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 5579.876192] Modules linked in: huawei_cdc_ncm cdc_wdm cdc_ncm option usb_wwan usbserial usbnet mii uas usb_storage hid_generic hidp nvram msr binfmt_misc rfcomm bnep nls_iso8859_1 intel_rapl iosf_mbi x86_pkg_temp_thermal dell_wmi sparse_keymap intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul dell_laptop dcdbas btusb crc32_pclmul bluetooth ghash_clmulni_intel hid_multitouch aesni_intel aes_x86_64 lrw uvcvideo gf128mul videobuf2_vmalloc glue_helper wl(POE) videobuf2_memops ablk_helper videobuf2_core cryptd v4l2_common videodev media joydev i915_bpo serio_raw i915 dell_led rtsx_pci_ms intel_ips memstick snd_hda_codec_realtek snd_soc_rt286 snd_hda_codec_generic cfg80211 snd_soc_core drm_kms_helper mei_me lpc_ich shpchp mei snd_compress snd_hda_intel
[Touch-packages] [Bug 1454450] Re: Bluetooth mouse laggy and erratic
Hey, thanks for the updates and the investigation. However just to clarify, you are talking about this keyboard http://www.sonymobile.com /global-en/products/accessories/bluetooth-keyboard-bkb10/ right? Also, do I understand rightly that once it is paired the connection gets disconnected? As an addition to that could you paste the syslog with Bluetooth debug options enabled [you can find instructions there https://wiki.ubuntu.com/DebuggingBluetooth]? This is going to be really useful for us when we start working on this issue. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1454450 Title: Bluetooth mouse laggy and erratic Status in bluez package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: I installed Ubuntu 15.04 (64 bit) on a DELL XPS 13 (model 9343, bios A03) notebook. I use a DELL bluetooth mouse but sometimes it behaves erratically (laggy, jumpy). The problem happens after a few (sometimes one) suspend and resume. I am attaching below some info on my system. Thank you. cribari@darwin4:~$ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth Linux darwin4 3.19.0-17-generic #17-Ubuntu SMP Wed May 6 16:46:12 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux 02:00.0 Network controller [0280]: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03) Subsystem: Dell Device [1028:0019] Kernel driver in use: wl Bus 003 Device 002: ID 8087:8001 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:216f Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [2.174367] Bluetooth: Core ver 2.20 [2.174669] Bluetooth: HCI device and connection manager initialized [2.174792] Bluetooth: HCI socket layer initialized [2.174795] Bluetooth: L2CAP socket layer initialized [2.175449] Bluetooth: SCO socket layer initialized [2.592936] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [3.203438] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [3.542418] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [3.542421] Bluetooth: BNEP filters: protocol multicast [3.542425] Bluetooth: BNEP socket layer initialized [3.551641] Bluetooth: RFCOMM TTY layer initialized [3.551649] Bluetooth: RFCOMM socket layer initialized [3.551654] Bluetooth: RFCOMM ver 1.11 [ 26.569283] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 26.569287] Bluetooth: HIDP socket layer initialized [ 26.576971] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0003/input/input15 [ 26.577172] hid-generic 0005:046D:B00E.0003: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 72.448281] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:12/0005:046D:B00E.0004/input/input16 [ 72.448526] hid-generic 0005:046D:B00E.0004: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 2994.842547] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:13/0005:046D:B00E.0005/input/input17 [ 2994.842810] hid-generic 0005:046D:B00E.0005: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 3694.214037] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1000 lmp_ver=06 lmp_subver=220e [ 3694.861578] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [ 3811.777260] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0006/input/input20 [ 3811.777571] hid-generic 0005:046D:B00E.0006: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 5579.876192] Modules linked in: huawei_cdc_ncm cdc_wdm cdc_ncm option usb_wwan usbserial usbnet mii uas usb_storage hid_generic hidp nvram msr binfmt_misc rfcomm bnep nls_iso8859_1 intel_rapl iosf_mbi x86_pkg_temp_thermal dell_wmi sparse_keymap intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul dell_laptop dcdbas btusb crc32_pclmul bluetooth ghash_clmulni_intel hid_multitouch aesni_intel aes_x86_64 lrw uvcvideo gf128mul videobuf2_vmalloc glue_helper wl(POE) videobuf2_memops ablk_helper videobuf2_core cryptd v4l2_common videodev media joydev i915_bpo serio_raw i915 dell_led rtsx_pci_ms intel_ips
[Touch-packages] [Bug 1557298] Re: [Xenial][Bluez5] Low Energy Keyboard is paired incorrectly
On the other hand it is impossible for me to pair on regular xenial. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1557298 Title: [Xenial][Bluez5] Low Energy Keyboard is paired incorrectly Status in Unity Control Center: New Status in bluez package in Ubuntu: New Bug description: Failed to pair low energy(bluetooth smart, 4.0) keyboard correctly. Bluetooth smart keyboard is unable to use after bluetooth-wizard says "OK". Also the passcode input is also not acting interactively like when pairing with bluetooth 3.0(LegacyPairing) keyboard. Above scenario also being verified with bluetoothctl and blueman. Step to reproduce: 1. open Bluetooth Settings 2. click on Add New Device button 3. select the bluetooth le keyboard 4. input the passcode display on GUI Expected result: After bluetooth-wizard telling user is okay the keyboard should work Actual result: Pairing mode stop on keyboard, but still not work. - More details about versions: Environment: xenial daily (20160307) bluez 5.37-0ubuntu5 gnome-bluetooth 3.18.2-1ubuntu2 blueman 2.0.3-1ubuntu1 bluetooth controller 0cf3:e005 Atheros Communications, Inc. (hci version: 4.1) Tested devices: Designer Mouse, bluetooth smart (pairable, work, re-pair work) Designer Keyboard, bluetooth smart (paired, not working) BT3.0 keyboard, bluetooth classic (pair and work) BT3.0 mouse, bluetooth classic (pair and work) - In control environment with the same hardware system and devices: trusty 14.04.1 + dist-upgrade (stay with 3.13 kernel) bluez5 5.35 (ppa: https://launchpad.net/~vidplace7/+archive/ubuntu/bluez5) It works with all above devices but can only be pairing through bluetoothctl manually, since the older bluetooth-wizard does not understand bluez 5.x. Everything seems works fine, although there are a lot more error messages, but since this bug is more about xenial, please let me know if we need more information about this, I'm able to reproduce this trusty scenario in anytime. - Additional note: A little clarification, since I'm not sure how far the Bluetooth SIG is going to use Bluetooth Smart(Low Energy, or even Smart-Ready) to cover the versioning, I decided to just use what ever I saw on the product box. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 15 11:40:12 2016 InstallationDate: Installed on 2016-03-14 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Latitude E5550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic.efi.signed root=UUID=1079eca4-4293-4e51-ba0e-84f7d681cb2c ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0141B2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/18/2015:svnDellInc.:pnLatitudeE5550:pvr:rvnDellInc.:rn0141B2:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5550 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:71:CC:39:BD:22 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:862538 acl:39687 sco:0 events:2668 errors:0 TX bytes:26235 acl:904 sco:0 commands:1021 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/unity-control-center/+bug/1557298/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Yes, you can try it -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1557298] Re: [Xenial][Bluez5] Low Energy Keyboard is paired incorrectly
Tested with x230 and kernel 4.7-rc2 and finally managed to pair & connect & use the MS Designer keyboard. I had to, however, jump over fancy hops to accomplish that using u-s-s as there were glitches every now and then [like multiple devices found even though there is only one physical keyboard] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1557298 Title: [Xenial][Bluez5] Low Energy Keyboard is paired incorrectly Status in Unity Control Center: New Status in bluez package in Ubuntu: New Bug description: Failed to pair low energy(bluetooth smart, 4.0) keyboard correctly. Bluetooth smart keyboard is unable to use after bluetooth-wizard says "OK". Also the passcode input is also not acting interactively like when pairing with bluetooth 3.0(LegacyPairing) keyboard. Above scenario also being verified with bluetoothctl and blueman. Step to reproduce: 1. open Bluetooth Settings 2. click on Add New Device button 3. select the bluetooth le keyboard 4. input the passcode display on GUI Expected result: After bluetooth-wizard telling user is okay the keyboard should work Actual result: Pairing mode stop on keyboard, but still not work. - More details about versions: Environment: xenial daily (20160307) bluez 5.37-0ubuntu5 gnome-bluetooth 3.18.2-1ubuntu2 blueman 2.0.3-1ubuntu1 bluetooth controller 0cf3:e005 Atheros Communications, Inc. (hci version: 4.1) Tested devices: Designer Mouse, bluetooth smart (pairable, work, re-pair work) Designer Keyboard, bluetooth smart (paired, not working) BT3.0 keyboard, bluetooth classic (pair and work) BT3.0 mouse, bluetooth classic (pair and work) - In control environment with the same hardware system and devices: trusty 14.04.1 + dist-upgrade (stay with 3.13 kernel) bluez5 5.35 (ppa: https://launchpad.net/~vidplace7/+archive/ubuntu/bluez5) It works with all above devices but can only be pairing through bluetoothctl manually, since the older bluetooth-wizard does not understand bluez 5.x. Everything seems works fine, although there are a lot more error messages, but since this bug is more about xenial, please let me know if we need more information about this, I'm able to reproduce this trusty scenario in anytime. - Additional note: A little clarification, since I'm not sure how far the Bluetooth SIG is going to use Bluetooth Smart(Low Energy, or even Smart-Ready) to cover the versioning, I decided to just use what ever I saw on the product box. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 15 11:40:12 2016 InstallationDate: Installed on 2016-03-14 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Latitude E5550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic.efi.signed root=UUID=1079eca4-4293-4e51-ba0e-84f7d681cb2c ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0141B2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/18/2015:svnDellInc.:pnLatitudeE5550:pvr:rvnDellInc.:rn0141B2:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5550 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:71:CC:39:BD:22 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:862538 acl:39687 sco:0 events:2668 errors:0 TX bytes:26235 acl:904 sco:0 commands:1021 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/unity-control-center/+bug/1557298/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1557298] Re: [Xenial][Bluez5] Low Energy Keyboard is paired incorrectly
Tested with the ThinkPad X230 BT 4.0 module and the result is that I can pair and use the mouse however it fails to pair/connect the keyboard. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1557298 Title: [Xenial][Bluez5] Low Energy Keyboard is paired incorrectly Status in Unity Control Center: New Status in bluez package in Ubuntu: New Bug description: Failed to pair low energy(bluetooth smart, 4.0) keyboard correctly. Bluetooth smart keyboard is unable to use after bluetooth-wizard says "OK". Also the passcode input is also not acting interactively like when pairing with bluetooth 3.0(LegacyPairing) keyboard. Above scenario also being verified with bluetoothctl and blueman. Step to reproduce: 1. open Bluetooth Settings 2. click on Add New Device button 3. select the bluetooth le keyboard 4. input the passcode display on GUI Expected result: After bluetooth-wizard telling user is okay the keyboard should work Actual result: Pairing mode stop on keyboard, but still not work. - More details about versions: Environment: xenial daily (20160307) bluez 5.37-0ubuntu5 gnome-bluetooth 3.18.2-1ubuntu2 blueman 2.0.3-1ubuntu1 bluetooth controller 0cf3:e005 Atheros Communications, Inc. (hci version: 4.1) Tested devices: Designer Mouse, bluetooth smart (pairable, work, re-pair work) Designer Keyboard, bluetooth smart (paired, not working) BT3.0 keyboard, bluetooth classic (pair and work) BT3.0 mouse, bluetooth classic (pair and work) - In control environment with the same hardware system and devices: trusty 14.04.1 + dist-upgrade (stay with 3.13 kernel) bluez5 5.35 (ppa: https://launchpad.net/~vidplace7/+archive/ubuntu/bluez5) It works with all above devices but can only be pairing through bluetoothctl manually, since the older bluetooth-wizard does not understand bluez 5.x. Everything seems works fine, although there are a lot more error messages, but since this bug is more about xenial, please let me know if we need more information about this, I'm able to reproduce this trusty scenario in anytime. - Additional note: A little clarification, since I'm not sure how far the Bluetooth SIG is going to use Bluetooth Smart(Low Energy, or even Smart-Ready) to cover the versioning, I decided to just use what ever I saw on the product box. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 15 11:40:12 2016 InstallationDate: Installed on 2016-03-14 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Latitude E5550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic.efi.signed root=UUID=1079eca4-4293-4e51-ba0e-84f7d681cb2c ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0141B2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/18/2015:svnDellInc.:pnLatitudeE5550:pvr:rvnDellInc.:rn0141B2:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5550 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:71:CC:39:BD:22 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:862538 acl:39687 sco:0 events:2668 errors:0 TX bytes:26235 acl:904 sco:0 commands:1021 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/unity-control-center/+bug/1557298/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1557298] Re: [Xenial][Bluez5] Low Energy Keyboard is paired incorrectly
Got the keyboard working using bluetoothctl. My system os 16.04. @Yung Shen, could you try apt-get udpate and try to reproduce this issue also the adapter that you are using is build it or this si a bt usb dongle? Thanks, Konrad -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1557298 Title: [Xenial][Bluez5] Low Energy Keyboard is paired incorrectly Status in Unity Control Center: New Status in bluez package in Ubuntu: New Bug description: Failed to pair low energy(bluetooth smart, 4.0) keyboard correctly. Bluetooth smart keyboard is unable to use after bluetooth-wizard says "OK". Also the passcode input is also not acting interactively like when pairing with bluetooth 3.0(LegacyPairing) keyboard. Above scenario also being verified with bluetoothctl and blueman. Step to reproduce: 1. open Bluetooth Settings 2. click on Add New Device button 3. select the bluetooth le keyboard 4. input the passcode display on GUI Expected result: After bluetooth-wizard telling user is okay the keyboard should work Actual result: Pairing mode stop on keyboard, but still not work. - More details about versions: Environment: xenial daily (20160307) bluez 5.37-0ubuntu5 gnome-bluetooth 3.18.2-1ubuntu2 blueman 2.0.3-1ubuntu1 bluetooth controller 0cf3:e005 Atheros Communications, Inc. (hci version: 4.1) Tested devices: Designer Mouse, bluetooth smart (pairable, work, re-pair work) Designer Keyboard, bluetooth smart (paired, not working) BT3.0 keyboard, bluetooth classic (pair and work) BT3.0 mouse, bluetooth classic (pair and work) - In control environment with the same hardware system and devices: trusty 14.04.1 + dist-upgrade (stay with 3.13 kernel) bluez5 5.35 (ppa: https://launchpad.net/~vidplace7/+archive/ubuntu/bluez5) It works with all above devices but can only be pairing through bluetoothctl manually, since the older bluetooth-wizard does not understand bluez 5.x. Everything seems works fine, although there are a lot more error messages, but since this bug is more about xenial, please let me know if we need more information about this, I'm able to reproduce this trusty scenario in anytime. - Additional note: A little clarification, since I'm not sure how far the Bluetooth SIG is going to use Bluetooth Smart(Low Energy, or even Smart-Ready) to cover the versioning, I decided to just use what ever I saw on the product box. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 15 11:40:12 2016 InstallationDate: Installed on 2016-03-14 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Latitude E5550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic.efi.signed root=UUID=1079eca4-4293-4e51-ba0e-84f7d681cb2c ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0141B2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/18/2015:svnDellInc.:pnLatitudeE5550:pvr:rvnDellInc.:rn0141B2:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5550 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:71:CC:39:BD:22 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:862538 acl:39687 sco:0 events:2668 errors:0 TX bytes:26235 acl:904 sco:0 commands:1021 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/unity-control-center/+bug/1557298/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp