The bug is still present in Ubuntu 22.10 on a Gigabyte Technology Co.,
Ltd. GA-990FXA-UD3, when attached to an HK Onyx Studio 6.
Usually a work around is to restart the Bluetooth stack twice.
My wild guess is that a (ring) buffer in the Bluetooth stack is filled,
and isn't reset because the sound
I'm pretty sure this is the same bug
https://bugs.freedesktop.org/show_bug.cgi?id=58746
There is a proposed patch at
https://bugs.freedesktop.org/show_bug.cgi?id=58746#c14
** Bug watch added: freedesktop.org Bugzilla #58746
https://bugs.freedesktop.org/show_bug.cgi?id=58746
--
You received t
If I restart and try to use my Sony headphones, then sound stutter and
fails. If I run `sudo hcidump --ext avdtp`, then it works… This is
weird!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/b
Several programs are updated, it could be that this works now even if
the sound breaks up from time to time. I'll do some more testing.
--
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/188671
While waiting for a new Bluetooth dongle I messed around with some other
equipment. It seems like I can't make a Herman/Kardon Onyx 4 to fail,
which is a bit strange. Tried to log it with hcidump and nothing unusual
showed up. Logging avdtp gave identical results.
So just to double-check what happ
As soon as I can get an [Asus USB BT500](https://www.asus.com/Networking
/USB-BT500/) I will try that, as I suspect this issue is somehow related
to the chip in the dongle. It seems like all dongles with the same chip
has the same issue. The sound problem is probably (?) a secondary
effect, but tha
Slightly different machine, running 20.04 LTS, but not too different I
guess. Uses the same BT-400 dongle as the other machine, the Hama dongle
seems to create additional problems even if it should use the same chip.
Also tried Fedora 32 from a live USB stick, it had the same problem.
I wonder if
apport information
** Attachment added: "syslog.txt"
https://bugs.launchpad.net/bugs/1886714/+attachment/5391493/+files/syslog.txt
--
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/1886714
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1886714/+attachment/5391479/+files/Dependencies.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1886714/+attachment/5391488/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "getfacl.txt"
https://bugs.launchpad.net/bugs/1886714/+attachment/5391491/+files/getfacl.txt
--
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/1886
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1886714/+attachment/5391484/+files/Lsusb-v.txt
--
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/1886
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1886714/+attachment/5391490/+files/UdevDb.txt
--
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/1886714
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1886714/+attachment/5391482/+files/Lsusb.txt
--
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/1886714
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1886714/+attachment/5391481/+files/Lspci-vt.txt
--
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/18
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1886714/+attachment/5391485/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1886714/+attachment/5391486/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1886714/+attachment/5391489/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "rfkill.txt"
https://bugs.launchpad.net/bugs/1886714/+attachment/5391492/+files/rfkill.txt
--
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/1886714
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1886714/+attachment/5391487/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1886714/+attachment/5391483/+files/Lsusb-t.txt
--
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/1886
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1886714/+attachment/5391480/+files/Lspci.txt
--
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/1886714
apport information
** Tags added: apport-collected focal
** Description changed:
This bug has persisted over several years, and several versions, and
after a lot of investigation I'm not really any closer on what's going
on.
I have two pretty old GA MA78gm S2H mainboards, configured s
>From second paragraph “I wonder if I started noticing the problem under
Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x.
I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the
bug also persisted in Ubu 18.04 for as long as I was using it.)”
The bug was infac
** Description changed:
This bug has persisted over several years, and several versions, and
after a lot of investigation I'm not really any closer on what's going
on.
I have two pretty old GA MA78gm S2H mainboards, configured slightly
different, and otherwise working properly. Both o
After the crash (hid hangs, could be a side effect) this is the dmesg.0
file still existing
john@hydra:~$ tail -100 /var/log/dmesg.0
[7.277226] kernel: nvidia-uvm: Loaded the UVM driver, major device number
237.
[7.498321] kernel: cfg80211: Loading compiled-in X.509 certificates for
regu
There are several reports on the net talking about random disconnects
with Bluetooth dongles reporting as BCM20702A0 and BCM20702A1, that
might be important.
Win10 experience the same problems, but it seems like they are able to
recover.
It seems like my HK Onyx Studio 4 has the same problem, but
Public bug reported:
This bug has persisted over several years, and several versions, and
after a lot of investigation I'm not really any closer on what's going
on.
I have two pretty old GA MA78gm S2H mainboards, configured slightly
different, and otherwise working properly. Both of them have run
28 matches
Mail list logo
