GNOME Bugzilla – Bug 531279
space character breaks search functionality with some keyboard layout
Last modified: 2012-01-06 14:56:20 UTC
Please describe the problem: Please describe the problem: A bug report has been opened on launchpad here: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/221112 If the user has a French Alternative keyboard layout and tries to enter a space bar when focus is on the search bar, the currently selected song starts playing instead of inserting a space character into the search string. Steps to reproduce: Steps to reproduce: 1. Set Keyboard layout to French Alternative (prefs->keyboard->layout tab->new in ubuntu) 2. Open Rhythmbox and attempt to search for a song with a space character separating words Actual results: The currently selected song plays Expected results: The space character is inserted into the search string. Does this happen every time? Yes - Using Ubuntu 8.04 Other information: Check linked bug report for xorg.conf and gconf files for those experiencing this bug. bug reported to Freedesktop.org : http://bugs.freedesktop.org/show_bug.cgi?id=15804
One workaround is to select "France (Legacy) Alternative" layout
This has nothing to do with libgnomekbd. It is either app issue or gtk issue - as far as we proved that from XKB POV your key always generate normal space.
Seems to be actually linked to https://bugs.freedesktop.org/show_bug.cgi?id=9529 Not a GNOME bug.
*** Bug 540203 has been marked as a duplicate of this bug. ***
This one should be reopened.
OK, I'm reopening the bug. Please provide any information you have that lead to the conclusion that this is actually an app bug.
To make that long story short : => It first identified this bug as a probable xkeyboard bug => I spend much time with xkeyboard-config guys (discussion here : http://bugs.freedesktop.org/show_bug.cgi?id=15804). We finally came to the conclusion that every thing was ok on this side and that there should be something to do on the application level.
Hmm. I can't make much sense of any of that, and what little I can understand makes it seem like xorg's failure is somehow our problem. That's mostly irrelevant, though, because bug 402882 gives a solid reason for changing the shortcut that mere mortal application developers like myself can actually understand. *** This bug has been marked as a duplicate of 402882 ***
Great news!!! And furthermore it IS the same bug ...
What Comment #7 said seems to be outdated, see references on the more exact duplicate report. *** This bug has been marked as a duplicate of bug 566712 ***