After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 744347 - Bluetooth speakers used for audio output immediately after connection - but I can't control the volume
Bluetooth speakers used for audio output immediately after connection - but I...
Status: RESOLVED DUPLICATE of bug 662382
Product: gnome-control-center
Classification: Core
Component: Sound
3.14.x
Other Linux
: Normal normal
: ---
Assigned To: Control center sound maintainer(s)
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-02-11 18:03 UTC by Stefan Nagy
Modified: 2015-05-13 14:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Stefan Nagy 2015-02-11 18:03:01 UTC 
When I connect my bluetooth speakers (Creative T30 Wireless) they are used for audio output immediately, as expected – but I can't control the volume, neither with my keyboard nor by using GOME system menu. To gain control, I have to enter GNOME audio settings and mark the bluetooth speakers' entry (pick the bluetooth speakers as audio output device).

I would expect to be able to control the active audio output device immediately.


I'm affected by this bug on Debian Jessie (GNOME 3.14.1) and reported a bug downstream, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776636

I tested this with the GNOME 3.14 live demo image from http://www.gnome.org/getting-gnome/ and had the exact same problem.

There's a related bug report (bug #741994). Since the original reporter seems to be affected only if he reconnects a previously connected bluetooth headset I decided to open a new report – I'm affected every time I connect my bluetooth speakers.

Please tell me if I can provide any more useful information.
Comment 1 Bastien Nocera 2015-05-13 14:56:55 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 662382 ***