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 694952 - Increasing/Decreasing Volume/Briteness with FN key combination or spetial laptopbuttons wont work
Increasing/Decreasing Volume/Briteness with FN key combination or spetial lap...
Status: RESOLVED DUPLICATE of bug 693016
Product: gdm
Classification: Core
Component: general
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2013-03-01 19:29 UTC by chris
Modified: 2013-03-01 20:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description chris 2013-03-01 19:29:13 UTC
hallo all,
For me its not possible to Mute/Unmute, Increase/ Decrease volume or briteness with the fn shortcut. 
I try it on my Dell vostro 1720 and on my Samsung NF210 netbook.
My Dell laptop has special keys for Play/Pause/Prev/next and the volume control.
if i try to use the volumecontroll keys nothing happens to.

I m blind and have the need to an screenreader. sometimes a buddy/my wife/ my son mute the sound in gdm (by accident or forget to turn the sound on again).

i have no chance to get the sound back without the screenreader voice.

reproduce:
Boot Laptop (not login)
turn on screenreader in accessiblity menu
mute or decrease the volume with the mouse over the menu
try to change the loudness with fn keys

expect:
loudness change

what happen:
nothing

this is realy not good for blind people :/. 

The same Problem happens in the Lockscreen (login and lock the screen an try to change the sound). i think caused by the same reason.

greetings from germany.
Comment 1 Ray Strode [halfline] 2013-03-01 20:38:13 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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