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 422390 - Allow bypassing multimedia keys
Allow bypassing multimedia keys
Status: RESOLVED OBSOLETE
Product: gnome-screensaver
Classification: Deprecated
Component: general
CVS HEAD
Other All
: Normal enhancement
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
: 333505 484601 538066 562354 562875 590188 658356 665729 688608 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-03-24 19:22 UTC by Priit Laes (IRC: plaes)
Modified: 2014-08-19 21:00 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
multimedia-bypass.patch (4.27 KB, patch)
2007-09-17 21:50 UTC, Priit Laes (IRC: plaes)
needs-work Details | Review

Description Priit Laes (IRC: plaes) 2007-03-24 19:22:25 UTC
It should be possible for user to change audio volume when the screensaver is active.
Comment 1 Vincent Untz 2007-04-24 12:43:07 UTC
And stop music.
Comment 2 Allison Karlitskaya (desrt) 2007-09-17 21:40:16 UTC
programs that are interested in receiving these keypresses should just listen on the system dbus for the key-press events that hal generates:

signal sender=:1.0 -> dest=(null destination) path=/org/freedesktop/Hal/devices/usb_device_5ac_20b_noserial_if1_logicaldev_input; interface=org.freedesktop.Hal.Device; member=Condition
   string "ButtonPressed"
   string "volume-down"


these keypresses are captured directly from the event device from hal itself and are completely independent of X.



problem of course is how to deal with multiple active sessions -- i guess you could ask consolekit :)
Comment 3 Priit Laes (IRC: plaes) 2007-09-17 21:50:30 UTC
Created attachment 95767 [details] [review]
multimedia-bypass.patch

I have been experimenting a bit with this feature, but ran into one problem:
   * How could I emit the key so gnome-settings-daemon would pick it up? :)

Patch also requires eggaccelerators.[ch] from gnome-control-center/capplets/keybindings/
Comment 4 Vincent Untz 2007-09-18 07:03:08 UTC
(In reply to comment #2)
> programs that are interested in receiving these keypresses should just listen
> on the system dbus for the key-press events that hal generates:
> 
> signal sender=:1.0 -> dest=(null destination)
> path=/org/freedesktop/Hal/devices/usb_device_5ac_20b_noserial_if1_logicaldev_input;
> interface=org.freedesktop.Hal.Device; member=Condition
>    string "ButtonPressed"
>    string "volume-down"
> 
> 
> these keypresses are captured directly from the event device from hal itself
> and are completely independent of X.

This doesn't work if I change the keybindings in the GNOME capplet, I guess.
Comment 5 Allison Karlitskaya (desrt) 2007-09-18 07:15:32 UTC
vincent: you're right.  it doesn't.

i think we should probably decide on the one way that we want to handle this.  it seems excessively silly to have both ways setup.

i personally view the multimedia keys as sort of "out of band" with respect to the rest of the keyboard, so for me, it makes sense to have them delivered separately.


in any case, i prefer to have one channel for the delivery of this information that is always active (rather than multiple channels that are active depending on who has X keyboard grab).  consider the case of gksudo or ssh-askpass grabbing keyboard input.  the user would probably find it a little bit counter-intuitive that their multimedia keys don't work while these apps are running.
Comment 6 Teppo Turtiainen 2007-12-08 17:57:47 UTC
*** Bug 333505 has been marked as a duplicate of this bug. ***
Comment 7 Teppo Turtiainen 2007-12-08 18:21:48 UTC
*** Bug 484601 has been marked as a duplicate of this bug. ***
Comment 8 Teppo Turtiainen 2007-12-08 18:22:44 UTC
Confirming because of the duplicates.
Comment 9 Pander 2008-02-29 11:44:15 UTC
Some laptops have special keys for volume up, volume down and mute but lack special multi media play, pause, next, previous keys.

E.g. with Amarok, which I use, I have configured combinations of SHIFT, ALT and CTRL with F11 or F12 to do just that. Ans also would like to be able to do so when the screensaver has locked my keyboard.

What I would like to suggest is to (also) provide a way that users can specify a list of keys or key combinations that can be 'whitelisted' from the screensaver keyboard lock.

Implementing this feature will allow users with what kind of special or non special keys on their keyboard or laptop to configure it just they way they would like to.
Comment 10 Vincent Untz 2008-02-29 11:53:33 UTC
It should just read the keybindings from gconf. No need to add some configuration in the screensaver for this.
Comment 11 William Jon McCann 2008-11-13 18:34:53 UTC
*** Bug 538066 has been marked as a duplicate of this bug. ***
Comment 12 Bastien Nocera 2008-12-12 13:07:03 UTC
*** Bug 562354 has been marked as a duplicate of this bug. ***
Comment 13 Bastien Nocera 2008-12-12 13:07:03 UTC
*** Bug 562875 has been marked as a duplicate of this bug. ***
Comment 14 Richard Laager 2008-12-12 17:34:19 UTC
I suggested in a duplicate that additional information be passed to applications so that pressing "Play/Pause" would only ever pause, never start playing from a locked session.
Comment 15 Bastien Nocera 2009-11-02 15:28:24 UTC
This is also needed to make buttons on Bluetooth headsets work when the screensaver is on.
Comment 16 Mark Edgington 2011-06-09 16:52:15 UTC
Despite this request being a bit old, I think it's still valid, and would be a welcome feature.

I think a nice solution to partially deal with security concerns would be to have an additional "Enable Media-keys Passthrough" button on the normal locked-screen 'enter-password' dialog.  This would require that the user type their password, and click this button instead of the 'unlock' button.  Then the machine would remain locked, but the passthrough would be enabled (by default it is disabled).

Furthermore, there could be some kind of optional 'passthrough timeout' that the user can select in the gnome-screensaver-settings, which would disable the passthrough after x minutes / hours of enabling it.
Comment 17 Pander 2011-07-06 16:00:44 UTC
Mark, good ideas!

What would be the media keys? I would like to propose:
- volume up
- volume down
- volume mute toggle
- play/pause song
- stop song
- next song
- previous song
- brightness up
- brightness down
Comment 18 Carlos Eduardo Rodrigues Diógenes 2011-07-06 18:30:02 UTC
For me don't make sense type the password to "enable media-keys passthrough", since I don't want to type my password anyway only to change the volume level.

I think that media keys are the ones that you have in your keyboard.
Comment 19 Stefan Sauer (gstreamer, gtkdoc dev) 2011-07-06 18:53:04 UTC
+1 to carlos. No password typing please. If someone has physical access to your computer then can do worse things (like turning it off).
Comment 20 Pander 2011-07-20 07:44:37 UTC
See also http://issues.workrave.org/show_bug.cgi?id=1028 perhaps implementation can be re-used.
Comment 21 Ray Strode [halfline] 2011-09-07 04:04:06 UTC
*** Bug 658356 has been marked as a duplicate of this bug. ***
Comment 22 Ray Strode [halfline] 2011-09-07 04:07:44 UTC
There's a patch to pass through the video mode switch key to g-s-d in bug
590188 .  We should see if the same approach would be applicable for volume
keys.
Comment 23 Emmanuele Bassi (:ebassi) 2011-12-07 14:23:10 UTC
*** Bug 665729 has been marked as a duplicate of this bug. ***
Comment 24 Allison Karlitskaya (desrt) 2012-11-19 03:04:52 UTC
*** Bug 688608 has been marked as a duplicate of this bug. ***
Comment 25 Bastien Nocera 2014-08-19 20:50:00 UTC
gnome-screensaver is obsolete, and this particular bug has been fixed in
gnome-shell itself, and in gnome-settings-daemon (which handles the multimedia keys).
Comment 26 Bastien Nocera 2014-08-19 21:00:55 UTC
*** Bug 590188 has been marked as a duplicate of this bug. ***