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 693465 - Buttons on a Bluetooth headset (play, pause, next, previous) don't work if the screen is locked
Buttons on a Bluetooth headset (play, pause, next, previous) don't work if th...
Status: RESOLVED DUPLICATE of bug 643111
Product: gnome-shell
Classification: Core
Component: lock-screen
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2013-02-09 08:50 UTC by Timur Kristóf
Modified: 2014-11-09 17:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Timur Kristóf 2013-02-09 08:50:17 UTC 
When I'm logged in to gnome-shell and the screen is locked, the buttons on my bluetooth headset don't work.

I have a Bluetooth headset which has buttons for music controls: one for play/pause and a next and previous button for switching tracks. These are recognized and work correctly (Rhythmbox can make use of them) when the shell is not locked. However they don't do anything when the lock screen is active. (The lock screen just does the same thing as it would do when I press a key on the keyboard: the wallpaper slides up a bit and then down.)

This means that when the screen is locked, I can't use the controls of my Bluetooth headset at all. When I want to switch tracks or pause the current song, I have to stop what I'm doing, get back to the computer, and unlock. This beats the purpose of a Bluetooth headset.

I recommend changing this behaviour and allowing the multimedia keys to work even when the screen is locked.
Comment 1 Timur Kristóf 2013-08-01 22:45:42 UTC 
Seems that it's working correctly now in Gnome 3.8 :)
Thank you guys for fixing it!
Comment 2 Bastien Nocera 2014-11-09 17:23:15 UTC 
(In reply to comment #1)
> Seems that it's working correctly now in Gnome 3.8 :)
> Thank you guys for fixing it!

Indeed. Closing as a duplicate.

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