Public bug reported:
After upgrading the Linux kernel to version 6.8.0-51 on Ubuntu 22.04,
the external monitor connected via DisplayPort through a docking station
over USB-C stopped functioning. The monitor is no longer detected by the
system, and no output is displayed. However, when connecting
@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 dev
I can confirm that disabling PSR fixes the problem on my laptop (see bug
#2008053). Thanks a lot to @vanvugt for suggesting the workaround. When
there is a real fix for this issue in Ubuntu 22.04, I will try to re-
enable PSR and check if it works.
--
You received this bug notification because yo
Same issue with Yamaha THR5 through USB on Ubuntu Studio 20.04.1.
Disabled JACK and was able to fix the stutter. Edit in
/etc/pulse/daemon.conf for 5.13.0-37 did not fix distorted audio.
5.13.0-39 exhibiting same problem.
--
You received this bug notification because you are a member of Kernel
Pa
** Changed in: bluez (Ubuntu)
Assignee: Konrad Zapałowicz (kzapalowicz) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1620636
Title:
Fails to pair with Bose Q
** Changed in: bluez (Ubuntu)
Assignee: Konrad Zapałowicz (kzapalowicz) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1731467
Title:
Cannot pair BLE remote devi
I also have this problem on my ThinkPad T470p with Pro Dock 40A1.
When I power on my laptop with connected dock, it's fine. I can log in
and work smoothly. The problem occurs when I lock my screen. Computer
freeze and I can do nothing. Only reset is a solution.
I attached logs before a reset.
**
** 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 t
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
** Changed in: bluez (Ubuntu Xenial)
Assignee: (unassigned) => Konrad Zapałowicz (kzapalowicz)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1510570
Title:
Bluetooth LE pair
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
** 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 Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1731467
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 Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1731467
** 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 me
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"
** 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
mmit/?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
** At
** Project changed: snappy-hwe-snaps => bluez (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1729030
Title:
[bluez] regression: bluetoothd crash with Bose QC35
Status in bluez
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 deve
Meaning that it is out :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1688663
Title:
udev 97-hid2hci.rules missing usb id for logitech dinovo 2
Status in bluez package in Ubuntu:
F
This shall be released
** Changed in: bluez (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1688663
Title:
udev 97-hid2hci.rules missing usb i
@Timo,
thanks man, appreciated.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1712495
Title:
Please sponsor bluez 5.46-0ubuntu2 to artful
Status in bluez package in Ubuntu:
In Progr
Still seeing the error message on the following setup:
- Kernel: 4.12.0-041200-generic (downloaded from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12/)
- Ubuntu 17.04
- ThinkStation P310
[ 1130.350050] drm: not enough stolen space for compressed buffer (need
29491200 more bytes), disablin
I upgraded from kernel 4.4 to 4.8 on 16.04 LTS in the hope the issue
would go away. My hang is in btrfs-cleaner, not sure if this is the same
bug or not.
This related thread is interesting but does not seem to resolve it:
https://patchwork.kernel.org/patch/8284721/
Linux nuc 4.8.0-54-generic #57~
@jibel thanks, got it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1696075
Title:
Please sponsor bluez 5.45 in artful
Status in bluez package in Ubuntu:
Fix Committed
Bug descript
So it is released now?
/K
W dniu śr., 7.06.2017 o 18:21 Sebastien Bacher
napisał(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 upl
** Tags added: papercuts2017
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1688663
Title:
udev 97-hid2hci.rules missing usb id for logitech dinovo 2
Status in bluez package in Ubuntu:
@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 mem
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 Kernel
Packages, which is subscribed to bluez in Ubuntu.
ht
@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 re
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 coul
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
** 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.
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 Kernel
Packages,
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 Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1438510
Tit
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 t
@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 Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpa
@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 ref
@Wesley
Understood. Can you use it w/ the Bose app on the phone?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1620636
Title:
Fails to pair with Bose QC35 headphones
Status in Canonic
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Konrad Zapałowicz (kzapalowicz)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1654782
Title:
Can not pair with blueto
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?
Al
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 Kernel
Packages, which is subscribed to
@Wesley
You mean with Sony or Bose?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1620636
Title:
Fails to pair with Bose QC35 headphones
Status in Canonical System Image:
In Progres
** Tags added: papercuts2017
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1283003
Title:
[Bluetooth + 14.04] Bluetooth headsets are not working after last
couple of updates
Status i
** Tags added: papercuts2017
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1438510
Title:
[REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial
and 16.10 yakkety
Sta
** Tags added: papercuts2017
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1398193
Title:
The bluetooth headset can not control the media playback
Status in Canonical System Image:
T
** Tags added: papercuts2017
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1510570
Title:
BLE pairing fail
Status in bluez package in Ubuntu:
Confirmed
Bug description:
On 15.10 w
** Tags added: papercuts2017
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1607390
Title:
serious bug on bluetooth (Ubuntu 16.04 LTS)
Status in bluez package in Ubuntu:
Confirmed
Bu
** Tags added: papercuts2017
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1454450
Title:
Bluetooth mouse laggy and erratic
Status in bluez package in Ubuntu:
Confirmed
Status in lin
** Tags added: papercuts2017
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1531925
Title:
Can't connect Logitech K830 - no PIN prompt [LE]
Status in Canonical System Image:
Fix Relea
** Tags added: papercuts2017
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1546603
Title:
Bluetooth mouse connects but doesn't work
Status in bluez package in Ubuntu:
Confirmed
Bug
** Tags added: papercuts2017
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1620636
Title:
Fails to pair with Bose QC35 headphones
Status in Canonical System Image:
In Progress
Status
** Tags added: papercuts2017
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1651433
Title:
bluetooth mouse random disconnects
Status in bluez package in Ubuntu:
Confirmed
Bug descrip
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)
** Tags added: bluez-touch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1649144
Title:
Bluetooth audio quality bad
Status in bluez package in Ubuntu:
New
Bug description:
Listeni
** Changed in: bluez (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1535829
Title:
[bluetooth] "Forget this device" doesn't work if bluetoo
@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 wh
** Tags added: bluez-touch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1576951
Title:
System hangs if apple magic mouse is connected via bluetooth
Status in Canonical System Image:
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 Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1283003
Tit
Hey, do you observe such behavior on more recent Ubuntu versions?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1473043
Title:
bluetoothd -n consuming 100% after device disconnects
Sta
ot ready
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: konrad 3522 F pulseaudio
CurrentDesktop: GNOME-Flashback:Unity
DistroRelease: Ubuntu 16.10
EcryptfsInUse: Yes
MachineType: TOSHIBA Satell
not ready
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: konrad 3522 F pulseaudio
CurrentDesktop: GNOME-Flashback:Unity
DistroRelease: Ubuntu 16.10
EcryptfsInUse: Yes
MachineType: TOSHIBA Sate
not ready
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: konrad 3522 F pulseaudio
CurrentDesktop: GNOME-Flashback:Unity
DistroRelease: Ubuntu 16.10
EcryptfsInUse: Yes
MachineType: TOSHIBA Sate
using
legacy interrupt.
[22688.304635] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: konrad 3522 F pulseaudio
CurrentDesktop: GNOME-Fl
0: link is not ready
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: konrad 3522 F pulseaudio
CurrentDesktop: GNOME-Flashback:Unity
DistroRelease: Ubuntu 16.10
EcryptfsInUse: Yes
MachineTyp
0: link is not ready
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: konrad 3522 F pulseaudio
CurrentDesktop: GNOME-Flashback:Unity
DistroRelease: Ubuntu 16.10
EcryptfsInUse: Yes
MachineTyp
not ready
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: konrad 3522 F pulseaudio
CurrentDesktop: GNOME-Flashback:Unity
DistroRelease: Ubuntu 16.10
EcryptfsInUse: Yes
MachineType: TOSHIBA Sate
+ Architecture: i386
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: konrad 3522 F pulseaudio
+ CurrentDesktop: GNOME-Flashback:Unity
+ DistroRelease: Ubuntu 16.10
+ EcryptfsInUse: Yes
+ MachineType: TOSHIBA Satellite P100
+ NonfreeKernelModules: nvidia
not ready
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: konrad 3522 F pulseaudio
CurrentDesktop: GNOME-Flashback:Unity
DistroRelease: Ubuntu 16.10
EcryptfsInUse: Yes
MachineType: TOSHIBA Sate
0: link is not ready
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: konrad 3522 F pulseaudio
CurrentDesktop: GNOME-Flashback:Unity
DistroRelease: Ubuntu 16.10
EcryptfsInUse: Yes
MachineTyp
ink is not ready
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: konrad 3522 F pulseaudio
CurrentDesktop: GNOME-Flashback:Unity
DistroRelease: Ubuntu 16.10
EcryptfsInUse: Yes
MachineTyp
P): enp2s0: link is not ready
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: konrad 3522 F pulseaudio
CurrentDesktop: GNOME-Flashback:Unity
DistroRelease: Ubuntu 16.10
EcryptfsInUse: Yes
M
0: link is not ready
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: konrad 3522 F pulseaudio
CurrentDesktop: GNOME-Flashback:Unity
DistroRelease: Ubuntu 16.10
EcryptfsInUse: Yes
MachineTyp
not ready
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: konrad 3522 F pulseaudio
CurrentDesktop: GNOME-Flashback:Unity
DistroRelease: Ubuntu 16.10
EcryptfsInUse: Yes
MachineType: TOSHIBA Sate
ink is not ready
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: konrad 3522 F pulseaudio
CurrentDesktop: GNOME-Flashback:Unity
DistroRelease: Ubuntu 16.10
EcryptfsInUse: Yes
MachineType: TOSHIBA
p2s0: link is not ready
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: konrad 3522 F pulseaudio
CurrentDesktop: GNOME-Flashback:Unity
DistroRelease: Ubuntu 16.10
EcryptfsInUse: Yes
MachineTyp
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1639016/+attachment/4772009/+files/version.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/163
Public bug reported:
After some time the Ethernet adapter resets itself and a reboot is required to
use it.
It started to happen with 4.8.0 kernel.
[22677.216049] [ cut here ]
[22677.216067] WARNING: CPU: 1 PID: 0 at
/build/linux-yFroJZ/linux-4.8.0/net/sched/sch_generic.
@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 devi
** Changed in: bluez (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1488170
Title:
Bluetooth initiated after quitting airplane mode
Sta
Also worth remembering of:
https://developer.bluetooth.org/TechnologyOverview/pages/le-
security.aspx
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1620636
Title:
Fails to pair with Bos
Might be that the kernels since 3.19 have this included:
http://www.bluez.org/bluetooth-4-2-features-going-to-the-3-19-kernel-
release/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/162063
According to information here
http://unix.stackexchange.com/questions/292189/pairing-bose-qc-35-over-
bluetooth-on-fedora this might be due to not yet supported feature from
BlueZ however this needs a further checking.
--
You received this bug notification because you are a member of Kernel
Packa
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 Kernel
Packages, which
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 Ker
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:
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 connec
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 Kernel
Packages, which is subscribed to bluez in
I have tried the Bluetooth chip firmware embedded in updates as on this
page http://www.flymeos.com/firmwarelist?modelId=10&type=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 Kernel
Packag
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 t
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 Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/
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
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 Kernel
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 up
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 Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://b
Right, I'll find out.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1490347
Title:
[Regression] 16:04 + 15:10 - Cannot pair with devices using (legacy
LMP Link Management Protocol) PI
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 Kernel
Packages, which is subscribed to bluez
*** 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 Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchp
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
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
wrote:
> Hi Konrad,
>
> I tried to remove the "Nissan Connect" device, b
What is your phone?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1539158
Title:
Unable to pair with in-car hands-free system after OTA-9 update
Status in Canonical System Image:
Fix
1 - 100 of 441 matches
Mail list logo
