Bug 467796 - Volume keys are not mapped on XO
Summary: Volume keys are not mapped on XO
Alias: None
Product: Fedora
Classification: Fedora
Component: hal-info
Version: 10
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
Depends On: FedoraXOKeyboard
Blocks: FedoraOnXO
TreeView+ depends on / blocked
Reported: 2008-10-20 21:51 UTC by Steve Salevan
Modified: 2009-05-08 03:07 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-05-08 03:07:51 UTC
Type: ---

Attachments (Terms of Use)
xev output for accelerator keypresses (16.00 KB, text/plain)
2008-10-25 15:00 UTC, Steve Salevan
no flags Details

Description Steve Salevan 2008-10-20 21:51:57 UTC
Description of problem:
The volume keys on the XO keyboard do not modify the system volume

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Boot the XO and log in
2. Press the volume keys
Actual results:
Volume is not modified

Expected results:
Volume is modified

Additional info:

Comment 1 Jeremy Katz 2008-10-21 00:32:47 UTC
Are they being recognized or do they cause messages in dmesg?

If the former, can you run xev and press them and see what it reports?

Comment 2 Martin Dengler 2008-10-24 15:49:51 UTC
The keys are just F9 (volume down) and F10 (volume up).

Comment 3 Martin Dengler 2008-10-24 15:55:32 UTC
(In reply to comment #2)
> The keys are just F9 (volume down) and F10 (volume up).

sorry, F11 and F12 for vol down and vol up, respectively (F9 and F10 are brightness down and brightness up).

Comment 4 Steve Salevan 2008-10-25 15:00:08 UTC
Created attachment 321506 [details]
xev output for accelerator keypresses

I've attached the xev output from pressing the volume up/down accelerator keys, and it appears that, indeed, they are mapped to F11/F12 (down/up, respectively).

Comment 6 Bug Zapper 2008-11-26 04:03:11 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:

Comment 7 Simon Schampijer 2009-02-25 09:09:15 UTC
Not sure - to fully understand the bug here. 

If it is about matching the available keyboard keys to alter the volume, see this upstream bug http://dev.sugarlabs.org/ticket/430

Comment 8 Bastien Nocera 2009-05-08 03:07:51 UTC
You can change which key does volume up/volume down in the "keyboard shortcuts" preferences. If you want this to work by default, you'll need to fix your keymap to throw XF86VolumeUp/XF86VolumeDown. We can't guess whether you want to press F11 or change the volume :)

You probably access the volume up/down function through an Fn key combination though, in which case this needs to be fixed in hal-info. See also:

Note You need to log in before you can comment on or make changes to this bug.