Bluetooth audio skips while the settings dialog is open

Also side comment:
`Architecture: amd64` - though i am using: Intel(R) Core(TM) i7-4702MQ CPU @ 2.20GHz

The last bluez update was 3 months ago, so whatever changed for you recently it's not bluez. It's also not pulseaudio (4 months ago).

Most likely this is related to the kernel update that was released 8 days ago.

This change was made by a bot.

I'm experiencing this as well. After rebooting today for the first time since September 25, I noticed somewhat choppy audio over bluetooth, first with mp3s on disk, then tried Youtube and it was significantly worse. Same audio content over laptop speakers seems to play without problems. Attaching a pulseaudio verbose log in case that helps.

Ivan:

Please attach a copy of your:
  /var/log/apt/history.log
  /var/log/dpkg.log
So that we can see what packages changed around 10 October.

------

anlag:

Please open a new bug by running:
  ubuntu-bug pulseaudio
and also attach the same files requested above to your new bug.

Here they are, bu today I've tried to update with check box pre-release updates

and dpkg.log

but again, it doesn't work even with fresh installation over formatted partition, can try it again tomorrow

Thanks Ivan. It appears your bluez and pulseaudio packages last updated on 2018-07-25, so they won't be the cause of any recent regressions.

I think this kernel upgrade on 2018-10-09 might be what changed:
linux-generic:amd64 (4.15.0.29.31 --> 4.15.0.36.38)

Please try downgrading your kernel, like to version 4.14:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/

The change could also be a coincidence and environmental, like:

 * a new 2.4GHz wifi network or device was recently introduced nearby, degrading Bluetooth signal quality.

 * a new Bluetooth device was introduced nearby, degrading the signal quality of audio.

Thanks for you help.

doubt about environmental reason because this laptop also has windows and everything continue to work fine in windows. even tried to reconnect my headsets in windows - still works. but it not convenient to boot in to win in order to use my headset.
Anyway- trying to downgrade my kernel, will key you posted.

After downgrading core bluetooth device disappeared, and installing most recent one didn't help to bring it back.
I am just not enough familiar with linux to be able reinstall it manually.
had to reinstall whole ubuntu from scratch - still have same problems.

That's strange. Your Bluetooth chip looks like a common one that any Linux kernel version should support:
  https://ark.intel.com/products/66889/Intel-Centrino-Wireless-N-2230-Single-Band

As a quick check, please live boot the original 18.04.0 release:
  http://old-releases.ubuntu.com/releases/18.04.0/
and verify it was working in that version before any updates.

Hi,
it was a great idea to test by running without installation,
and i test it on:
ubuntu-16.04.1-desktop-amd64 - don't see my Bluetooth headset
ubuntu-17.10.1-desktop-amd64 - same problems with skipping as with current version
ubuntu-18.04-desktop-amd64 - same problems with skipping as with current version

so basically it doesn't work at all and the biggest mystery as for me is why i was able to use my headset on ubuntu at least for half a day when i installed it first time? and why it works perfect right now on windows...

so i guess the fact that bluetooth works under windows - excluded hardware problem.

hi,
FINALLY, i was able to localize problem :)

all my headsets are skipping only when setting window is open!
so basically when you click test left or test right - it is in settings window and thus it sounds terribly.
But, if you close setting window - every headset works just fine (on online radio for example).

my guess would be that while settings window is open - system constantly looking for available devices and thus interfere with present devices.

Sorry guys for all these troubles, meanwhile solution was so simple.

Thanks

Status changed to 'Confirmed' because the bug affects multiple users.

Can anyone experiencing this bug please report it upstream?

https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues

And then tell us the new issue ID.

Unsure if that's something settings could change though, it's probably due to the panel triggering bluetooth discovery automatically

Yeah OK... Anyone experiencing this bug please also report it to BlueZ upstream:

https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers&component=Bluetooth

and then tell us the new bug ID.

Hello,

Thank you for looking at this issue.

If source code propagate downstream, then I think it would be a good idea to come up with a system that propagates bug reports upstream.

If that effort is underway I will consider registering on arbitrary other bug trackers in the meantime as a stopgap solution.