https://bugs.kde.org/show_bug.cgi?id=363961
Harald Sitter <sit...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |UPSTREAM
--- Comment #14 from Harald Sitter <sit...@kde.org> ---
Right. So.
The two sections in the settings are two different applications, they both use
PulseAudio for the actual hardware integration though. What you are seeing in
the video is basically the visual presentation of PulseAudio indicating that
the a2dp device is not detected as connected. This can have multiple causes,
they are all a level deeper than the KDE software stack though.
Firstly you'll want to make sure that your bluetooth device is properly
connected to begin with. If it is I suggest you disconnect, reboot, reconnect
and check if that fixes a2dp.
If that is the case, then something went wrong on shutdown while the device is
still connected.
If it is not connected, make sure to connect your device first ;)
Regardless this is probably a bug in either PulseAudio or Bluez (the bluetooth
support stack), I suggest you file a bug against PulseAudio to help with
investigating the ultimate problem here.
On a related note: I think you actually crashed pulseaudio towards the end
which is why the second settings module stopped working.
--
You are receiving this mail because:
You are watching all bug changes.
