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 569197 - Support 0xa0 for keyboard models that don't have XF86AudioMute
Support 0xa0 for keyboard models that don't have XF86AudioMute
Status: RESOLVED WONTFIX
Product: gnome-settings-daemon
Classification: Core
Component: plugins
2.25.x
Other Linux
: Normal enhancement
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2009-01-26 14:57 UTC by Vincent Untz
Modified: 2009-01-28 18:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Vincent Untz 2009-01-26 14:57:12 UTC 
(this is also valid for other keys)

While discussing https://bugzilla.novell.com/show_bug.cgi?id=460565, we were wondering if it makes sense for the media-keys plugin to detect that the keyboard model used in the X configuration doesn't have a XF86AudioMute, and therefore should handle 0xa0 directly.

The thing is that it can happen that the keyboard is not properly configured after installation, and the user will think it's just broken (instead of looking at the keyboard capplet). Sure, the user can also remap the keybinding in the keybindings capplet, but working out of the box is still better.

So I'd like to know what you think.

Another option, that I think is better that X should just send XF86AudioMute when there's some 0xa0. Not sure if it's possible, though.
Comment 1 Jens Granseuer 2009-01-26 21:44:17 UTC 
If anything, the keyboard plugin should automatically change the keymap to include those symbols. It's none of the business of the keybinding plugin.

However, if it is that simple, I'm wondering why we need keysyms at all. Is 0xa0 guaranteed (or at least reasonably safe to be assumed) to be equivalent to XF86AudioMute? Why? X just assuming certain symbols sounds rather broken and unportable to me.
Comment 2 Vincent Untz 2009-01-26 21:54:33 UTC 
(In reply to comment #1)
> If anything, the keyboard plugin should automatically change the keymap to
> include those symbols. It's none of the business of the keybinding plugin.

Yeah, maybe.

> However, if it is that simple, I'm wondering why we need keysyms at all. Is
> 0xa0 guaranteed (or at least reasonably safe to be assumed) to be equivalent to
> XF86AudioMute? Why?

I *think* it's rather safe to assume this, since this is the default we shipped for quite some time and it worked well :-) But I have no other reason.

> X just assuming certain symbols sounds rather broken and unportable to me.

Nod, I take your point. Feel free to close the bug as WONTFIX. Maybe I should just open a bug against X.
Comment 3 Jens Granseuer 2009-01-28 18:23:47 UTC 
(In reply to comment #2)
> Maybe I should just open a bug against X.

I'd be interested in their response.