Cannot use Windows key in keyboard shortcuts

[Andrew Bennetts]

I've just upgraded to hoary, and now I'm seeing something that looks a lot like
bug #8146: my windows key is no longer able to be assigned to keyboard
shortcuts, and the existing shortcuts I had that use it don't work anymore.

I've tried to use the altwin:super_win workaround described in comments 16 and
18 of #1390, but I get "Error activating XKB configuration". The output of the
commands that error dialog suggests are:

andrew@trogdor ~ $ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xfree86", "pc104", "us", "inet(hpi6)", ""
_XKB_RULES_NAMES(STRING) = "xfree86", "pc104", "us", "inet(hpi6)", ""
andrew@trogdor ~ $ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = [us inet(hpi6)]
 model = pc104
 overrideSettings = false
 options = [altwin altwin:super_win]

I'm not sure what package is responsible, so I'm leaving as UNKNOWN, but CCing
Daniel Stone because he probably knows :)

http://bugzilla.gnome.org/show_bug.cgi?id=165343: http://bugzilla.gnome.org/show_bug.cgi?id=165343

[Daniel Stone (daniels)]

Since Sunday is the day for incredibly difficult X bugs, judging by today's bug
flow, I'll take this one.

Under xev, what gets generated, a) when you press just your Windows key, b) when
you press Windows+somethingelse? With and without altwin:super_win would be
good. Although your options string looks weird. Does it work if you do
"setxkbmap -option 'altwin:super_win'", or possibly "setxkbmap -option
'altwin:superwin'"?

[Andrew Bennetts (spiv)]

> Under xev, what gets generated, a) when you press just your Windows key,

KeyPress event, serial 26, synthetic NO, window 0x3600001,
    root 0x40, subw 0x0, time 3693983, (409,186), root:(414,257),
    state 0x0, keycode 115 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 29, synthetic NO, window 0x3600001,
    root 0x40, subw 0x0, time 3694073, (409,186), root:(414,257),
    state 0x0, keycode 115 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:

> b) when you press Windows+somethingelse?

KeyPress event, serial 29, synthetic NO, window 0x3600001,
    root 0x40, subw 0x0, time 3715823, (409,186), root:(414,257),
    state 0x0, keycode 115 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyPress event, serial 29, synthetic NO, window 0x3600001,
    root 0x40, subw 0x0, time 3716018, (409,186), root:(414,257),
    state 0x0, keycode 41 (keysym 0x66, f), same_screen YES,
    XLookupString gives 1 bytes: (66) "f"
    XmbLookupString gives 1 bytes: (66) "f"
    XFilterEvent returns: False

KeyRelease event, serial 29, synthetic NO, window 0x3600001,
    root 0x40, subw 0x0, time 3716060, (409,186), root:(414,257),
    state 0x0, keycode 41 (keysym 0x66, f), same_screen YES,
    XLookupString gives 1 bytes: (66) "f"

KeyRelease event, serial 29, synthetic NO, window 0x3600001,
    root 0x40, subw 0x0, time 3716165, (409,186), root:(414,257),
    state 0x0, keycode 115 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:

> With and without altwin:super_win would be
> good. Although your options string looks weird. Does it work if you do
> "setxkbmap -option 'altwin:super_win'", or possibly "setxkbmap -option
> 'altwin:superwin'"?

andrew@trogdor ~ $ setxkbmap -option 'altwin:super_win'
Illegal map name '(inet(hpi6))+' in symbols name
'pc/pc(pc104)+pc/us(inet(hpi6))+altwin(super_win)'
andrew@trogdor ~ $ setxkbmap -option 'altwin:superwin'
Illegal map name '(inet(hpi6))' in symbols name 'pc/pc(pc104)+pc/us(inet(hpi6))'

Given these various errors, I'm not sure that I've successfully turned
altwin:super_win on :)

[Daniel Stone (daniels)]

I think the GNOME keyboard manager is massively broken (Seb, ideas?). Could you
please try whether any of the following fix it?
setxkbmap -symbols 'inet(hpi6)' -option 'altwin:super_win'
setxkbmap -symbols 'us(inet(hpi6))' -option 'altwin:super_win'
setxkbmap -symbols 'pc(pc104)+us(inet(hpi6))' -option 'altwin:super_win'
setxkbmap -symbols 'pc(pc104)+us(inet(hpi6))+altwin(super_win)' -option ''

[Daniel Stone (daniels)]

Seb, you win, dude. Setting symbols='us(pc104)+inet(hpi6)'
options='altwin:super_win' (which was my first guess as soon as Andrew called me
because I'd broken his XKB entirely, and I'm pretty sure is the right thing to
be doing) works fine, so reassigning to the GNOME keyboard thingy. Ez GTK boog. :)

[Sebastien Bacher (seb128)]

what happen when you press the window key in the keybinding UI ?

[Andrew Bennetts (spiv)]

(In reply to comment #5)
> what happen when you press the window key in the keybinding UI ?

It gives me e.g. <Mod4>1 with Daniel's workaround, and 0x73 (iirc) without.

[Sebastien Bacher (seb128)]

so it doesn't act as a modifier and get it as a keybinding ?

[Andrew Bennetts (spiv)]

(In reply to comment #7)
> so it doesn't act as a modifier and get it as a keybinding ?

Correct.

[Sebastien Bacher (seb128)]

An upstream bug about this:
http://bugzilla.gnome.org/show_bug.cgi?id=165343

[Sergey V. Udaltsov (svu)]

1. The bug in gnome and this one - are not relevant really
2. This is very odd configuration, actually. How did it happen that you got
layout 'us' with variant(!!!) 'inet(hpi6)'. Are you sure there is such a thing?

Actually, gnome-settings-daemon (2.9.x), executes:

setxkbmap -model 'pc104' -layout 'us(inet(hpi6))' -options 'altwin:super_win'

Does this command work? If not - there is a problem with your XKB configuration
repository. I would be interested to see your xkb/rules/xfree86.xml and
xkb/symbols/pc/us if possible.

[Andrew Bennetts (spiv)]

(In reply to comment #10)
> 1. The bug in gnome and this one - are not relevant really
> 2. This is very odd configuration, actually. How did it happen that you got
> layout 'us' with variant(!!!) 'inet(hpi6)'. Are you sure there is such a thing?

My laptop is an HP NC6000. I believe hpi6 is the right setting for this
keyboard, or at least close enough to make my volume buttons work ;)

> Actually, gnome-settings-daemon (2.9.x), executes:
>
> setxkbmap -model 'pc104' -layout 'us(inet(hpi6))' -options 'altwin:super_win'
>
> Does this command work? If not - there is a problem with your XKB configuration
> repository. I would be interested to see your xkb/rules/xfree86.xml and
> xkb/symbols/pc/us if possible.

No, it doesn't work:

andrew@trogdor ~ $ setxkbmap -model 'pc104' -layout 'us(inet(hpi6))' -options
'altwin:super_win'
Error! Option "-options" not recognized

I'll attach the files you're asking for.

[Andrew Bennetts (spiv)]

Created an attachment (id=1448)
xkb/rules/xfree86.xml

[Andrew Bennetts (spiv)]

Created an attachment (id=1449)
xkb/symbols/pc/us

[Sergey V. Udaltsov (svu)]

Andrew: Well, what you probably should do is: in gnome-keyboard-properties,
choose your MODEL: "Hewlett Packard Internet Keyboard", then LAYOUT "USA",
OPTION "Super is mapped to the Win-keys (default)". I do not understand how you
managed to choose the HP (hpi6) as VARIANT - it is simply _incorrect_.
Sorry, the right command line is:
setxkbmap -model 'pc104' -layout 'us(inet(hpi6))' -option 'altwin:super_win'
(not 'options' but 'option') - and it should fail. But this one should work:
setxkbmap -model 'hpi6' -layout 'us' -option 'altwin:super_win'

[Daniel Stone (daniels)]

Sorry, try this:
setxkbmap -model pc104 -layout 'us(inet(hpi6))' -option 'altwin:super_win'

(note s/options/option/)

[Andrew Bennetts (spiv)]

(In reply to comment #15)
> Sorry, try this:
> setxkbmap -model pc104 -layout 'us(inet(hpi6))' -option 'altwin:super_win'
>
> (note s/options/option/)

No luck:

andrew@trogdor ~ $ setxkbmap -model pc104 -layout 'us(inet(hpi6))' -option
'altwin:super_win'
Illegal map name '(inet(hpi6))+' in symbols name
'pc/pc(pc104)+pc/us(inet(hpi6))+altwin(super_win)'

[Andrew Bennetts (spiv)]

(In reply to comment #14)
> Andrew: Well, what you probably should do is: in gnome-keyboard-properties,
> choose your MODEL: "Hewlett Packard Internet Keyboard", then LAYOUT "USA",
> OPTION "Super is mapped to the Win-keys (default)". I do not understand how you
> managed to choose the HP (hpi6) as VARIANT - it is simply _incorrect_.
> Sorry, the right command line is:
> setxkbmap -model 'pc104' -layout 'us(inet(hpi6))' -option 'altwin:super_win'
> (not 'options' but 'option') - and it should fail. But this one should work:
> setxkbmap -model 'hpi6' -layout 'us' -option 'altwin:super_win'

You're right, that second setxkbmap line works just fine.

Also, configuring gnome-keyboard-properties as you describe seems to work,
although I get the "Error activating XKB configuration." dialog. I suspect that
may be due to misconfiguration in my xorg.conf file, though (where hpi6 is set
as the variant)?

It's too long ago for me to remember, but I think I probably set hpi6 as the
variant based on searching google for how to make the keys on this laptop work,
but I honestly don't remember, and can't find any such page on google now.

Thanks for your help!

[Sergey V. Udaltsov (svu)]

Ghm. I'm happy you got your configuration working. But I am unhappy with the
error dialog. Which version of gnome-control-center/libxklavier do you use?
Could you play around your configuration (for example, remove the option and add
it again - or change keyboard to something like "generic pc 105") - and find out
which configuration element, when used, causes the trouble?

[Danilo Piazzalunga (danilopiazza)]

*** Bug 13153 has been marked as a duplicate of this bug. ***

[Jussi Pakkanen (jpakkane)]

Same problem here. My specs:

- fresh Hoary install (no earlier Ubuntu experience)
- keyboard model is Generic 105 (intl) PC
- Finnish key layout
- Keyboard Shortcuts gives either Super_L or Super_R when attempting to bind
- Super mapped to Win-keys

[Sebastien Bacher (seb128)]

is that still an issue for somebody?

[Andrew Bennetts (spiv)]

(In reply to comment #21)
> is that still an issue for somebody?

Works ok for me on Breezy, once I set "Super is mapped to the Win-keys" in my
System -> Preferences -> Keyboard -> Layout Options -> Alt/Win key behaviour.

[Sebastien Bacher (seb128)]

*** Bug 21785 has been marked as a duplicate of this bug. ***

[Gorka Navarrete (emrys)]

It Works with Andrew's trick. But this should be the default beaviour.

[Lionel Dricot (ploum-deactivatedaccount)]

Is this bug still relevant or was it fixed ?

[Steven Brown (steven-w-j-brown)]

I am using Dapper and I have this problem. Perhaps it is related to Bug #19493?

[Steven Brown (steven-w-j-brown)]

The Alt/Win key behaviour on the Keyboard Preferences has 2 defaults. I'm assuming this is a typo, but has no effect on the selection. Regardless, none of these options allows my windows key(s) to be used as a modifier in keyboard shortcuts.

I have a logitech iTouch keyboard.

[Danny Rathjens (launchpad-rathjens)]

I had a similar problem; I could assign Super as shortcut, but not use it as a modifier for a shortcut.

 dkr@eos:~% xmodmap -pm |grep Super
mod4 Super_L (0x7f), Hyper_L (0x80)

 I "set "Super is mapped to the Win-keys" in my
System -> Preferences -> Keyboard -> Layout Options -> Alt/Win key behaviour." as per above advice.

 dkr@eos:~% xmodmap -pm |grep Super
mod4 Super_L (0x73), Super_R (0x74), Super_L (0x7f), Hyper_L (0x80)

Now I can use windows key as a modifier key in keyboard-shortcuts(shows up as <Mod4>)

[Danny Rathjens (launchpad-rathjens)]

I forgot to mention that this was with Breezy upgraded to Dapper.

[Bert Hekman (bert-demontpx)]

I have the same sort of problem with breezy and dapper. I mapped the windows key to super, and i can use winkey+t to start a terminal and i can use winkey+1...4 to switch to desktop 1...4.

I can also set winkey+e to home folder, and winkey+l to lock screen.. but when I press the keys, nothing happens.

[Aaron Whitehouse (aaron-whitehouse)]

Thanks Danny. After changing from the default in Alt/Win keys to a different setting also marked default - not to be confused with the third setting marked default) I can now set <mod4>+l to lock my screen.

Like Demon, this doesn't actually work. Thankfully the upstream bug explains it.

There are two bugs here:
- A default that is different to what we expected in the keyboard defaults; and
- Gnome not carrying out some functions set using the Windows key.

[hunger (hunger)]

It would be great if this issue could get fixed without remapping the key in xmodmap. It works great as is in KDE and remapping the key will break the setup of Kubuntu users.

[Bert Hekman (bert-demontpx)]

I got <Mod4>+L to lock my screen working in a rather filthy way.
I changed command_1 in /apps/metacity/keybinding_commands to gnome-screensaver-command --lock
And I also changed run_command_1 in /apps/metacity/global_keybindings to <Mod4>L

This seems to be working...

[Philipp Kohlbecher (xt28)]

Bert's work-around works for me as well.
Any progress on fixing this, though? (Enabling users to set this in System->Preferences->Keyboard Shortcuts?)

[Brandon Williams (brandon-magma)]

I'm having this problem in the latest Feisty beta, and even the gconf-editor work-around seems to not function anymore. I'm using xbindkeys as a fallback but the problem seems to be getting worse...

[Bogdan Butnaru (bogdanb)]

This is still not working in Feisty. This thread seems a bit complex, bug #16815 seems to more closely match my problem. The key is recognized as a modifier (Mod4), but it only works for some commands. For instance, it works for starting a new terminal, but it doesn't work for locking the screen.

[der_vegi (m-may)]

same problem on feisty final, amd64. if i try to assign a key combination - let's say win-key+x - to "execute" i hit the win-key and then the dialog ends, and "super l" is stored. when i hit the windows key, keep it pressed, then click on the desired action, then hit x, the combination "Mod4+x" is stored and everything works.

[Cardy (andrei-bogomolov)]

SUPER (WIN) modification -key can be binded in gconf: /apps/gnome_settings_daemon/keybindings. I successfully set volume control to <WIN>KP_Down, <WIN>KP_Up in Feisty.

[emags (magius-eternal)]

For what it's worth, IceWM in Feisty supports the use of the Windows key as a modifier (in a key combination) and as a stand-alone shortcut simultaneously, i.e., the correct behavior.

This should be supported in Gnome via Preferences->Keyboard Shorcuts.

[Aaron C. de Bruyn (darkpixel2k)]

I have done a completely fresh install of Feisty on my laptop. (Compaq Presario 2100)
In keyboard preferences I set the keyboard model to "Laptop/notebook Compaq (eg. Presario) Internet Keyboard"
On the layout options tab I set the "Alt/Win key behavior" to "Super is mapped to the win-keys (default)"

If I go into Keyboard Shortcuts I can assign shortcuts based on the windows key.
For example Win+L to lock the screen and Win+T to open a terminal window.
They assign as Mod4+L and Mod4+T respectively.

If I hit Win+L, the screen doesn't lock. Nothing happens.
If I hit Win+T, I get a new terminal window.

Could a lot of people in this thread be talking about a similar issue. Trying to get Win+L to lock their screen?
What would cause the keyboard shortcuts to work for everything else, but not locking the screen?

[Philipp Kohlbecher (xt28)]

The difference seems to be that the shortcut for launching the terminal is set in gconf setting /apps/metacity/global_keybindings (as is the shortcut for minimizing all windows to show the desktop, for example), while the shortcut for locking the screen is set in /apps/gnome_settings_daemon/keybindings (as is the shortcut for launching the web browser, for example).

I have the exact same problem (albeit with dapper) and in addition, the shortcut "Win+D" works for showing the desktop, while "Win+F" does not work for launching the browser, corroborating the assumption above.

[Philipp Kohlbecher (xt28)]

See bug #16815 for more information on this particular problem.

(This doesn't seem to be the only problem discussed on this bug page, though, so I am not marking it as a duplicate.)

[Karl Hegbloom (karl.hegbloom)]

On Mon, 2007-06-04 at 22:58 +0000, Philipp Kohlbecher wrote:
> The difference seems to be that the shortcut for launching the terminal
> is set in gconf setting /apps/metacity/global_keybindings (as is the
> shortcut for minimizing all windows to show the desktop, for example),
> while the shortcut for locking the screen is set in
> /apps/gnome_settings_daemon/keybindings (as is the shortcut for
> launching the web browser, for example).
>
> I have the exact same problem (albeit with dapper) and in addition, the
> shortcut "Win+D" works for showing the desktop, while "Win+F" does not
> work for launching the browser, corroborating the assumption above.

There really needs to be a desktop-wide key-binding manager of some kind
that serves all applications. I love the Emacs idea of 'keymaps' and
'keymap prefix' keys. I'd like to reserve combinations involving the
"windows logo" key for the window manager, and have it never use a key
not involving that one.

Could the key with the little "menu" on it be used as a prefix for panel
and application menu-bar commands?

[Eduardo Romero (foxteck)]

I'm on Ubuntu 7.04, I asigned Win + E to open my home folder which doesn't work. Win+E to open run dialog works.
Any updates or ideas on how to fix it?

Thanks.
- Eduardo Romero

[Thierry Daucourt (thierry-daucourt)]

In reply to EduardoRomero, the following just work for me. It assigns "<left windows key>e" to nautilus.
I admit that I never had success in doing this through GUI of System/Preferences/Keyboard shortcuts that try to assign "Super L" key unsuccessfully.

 gconftool-2 -t str --set /apps/metacity/global_keybindings/run_command_1 "<mod4>e"
 gconftool-2 -t str --set /apps/metacity/keybinding_commands/command_1 "nautilus"

[sibidiba (sibidiba)]

I can confirm Aaron C. de Bruyn said on 2007-06-03.

When in the 'Keyboard' 'Layout Options' 'Alt/Win key behavior' is set to 'Super is mapped to the Win-keys (default)', I'm able to assign keybindings in 'Keyboard Shortcuts'.

Where for example I get the text Mod4+R. In gconf-edit stands <Mod4><Hyper>s.

And everything works fine _except_ the keybindings located under /apps/gnome_settings_daemon/keybindings/ .
Any keybinding located here (calculator, browser etc.) can be set, but if it is assigned to a Win+Any key, it does not happen anything.

Other keybindings like 'Take a screenshot' work well, even with the Win key involved.

Where is the difference???

[Aaron C. de Bruyn (darkpixel2k)]

I started testing Gutsy a few days ago. This issue is fixed in Gutsy.

[Jos Dehaes (jos-dehaes)]

It doesn't work for me in gutsy (uptodate), I'm trying win-e for home folder (keyboard shortcuts, not gconf), but no luck yet.

[Aaron C. de Bruyn (darkpixel2k)]

Meh. My Gutsy broke as well.

[Joseph Garvin (k04jg02)]

The issue is not fixed for me either as of the Gutsy beta. If I try to set a shortcut to use the Windows/Super key, it just sets the shortcut to be SuperL and ignores whatever else I press (so it's treated as a normal key instead of a modifier). In case it's relevant, I'm using a Dell Vostro 1400, which is supposedly hardware identical to the officially supported Inspiron 1420's, so I would guess they have this issue as well. I haven't tried selecting a different keyboard layout, but there's no generic "Dell Laptop" option, only specifically Latitude. Maybe I'll try that later. In any case it should work out of the box.

[Aaron C. de Bruyn (darkpixel2k)]

I am running Gutsy and having trouble too.
Mine lets me set it--it shows up as Mod4+L in the shortcuts dialog, but the key combo won't activate the screensaver.
If I set it to something like CTRL+ALT+L it works perfectly.

[der_vegi (m-may)]

Still there on Gutsy daily 20071003 (amd64). It works, if you press the 'win-key', keep it pressed and then select the shortcut.

[Steven Brown (steven-w-j-brown)]

I am having the same behaviour as Joseph Garvin on Gutsy. The Keyboard Shortcuts application is treating the SuperL and SuperR keys as regular keys, not accelerator keys. But this is better than not registering at all, as was happening earlier, I guess. :)

[Mikel Ward (mikelward)]

On Gutsy, I can first assign Win+L to lock screen, but if I try to then assign Win+R to run, I get the error message:
The shortcut "Super L" is already used for:
 "Lock screen"

[Bogdan Butnaru (bogdanb)]

The funny thing is that using compiz's settings manager (ccsm) this works without any problem.

[Thomas David Baker (bakert)]

I can reproduce this on MacBook Pro running Gutsy upgraded from Feisty.

If I try to set a keyboard shortcut to Apple+R (or any letter) it just sets it to "Super L" or "Super R" (the left and right side apple keys respectively).

This may or may not be related to the fact that almost any keyboard setting I change results in the "Error activating XKB configuration" error.

bakert@fenchurch:~$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "macintosh", "us", "intl", ""
_XKB_RULES_NAMES(STRING) = "xorg", "pc104", "us", "mac", ""

bakert@fenchurch:~$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = []
 model =
 options = [altwin altwin:super_win]
 overrideSettings = true

[Bogdan Butnaru (bogdanb)]

Note that this with Compiz this works without any hassle.

[zelrik (zelrikriando)]

My 'Super' Key seems to be not working at all.

KeyPress event, serial 31, synthetic NO, window 0x3600001,
    root 0x216, subw 0x0, time 629785657, (612,323), root:(624,416),
    state 0x2000, keycode 115 (keysym 0xffeb, Super_L), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

when I do 'Super+e' , I get e

I have an up to date Gusty Gibbon, and I wanted to use that Key with Compiz Fusion and that's not working.

I you want more info tell me (with the commands to get them...I am such a noob)

[Roberto Sarrionandia (rbs-tito)]

In Gutsy with the desktop effects super+e zooms back for me to see my workspaces.

[Nelson Benitez (gnel)]

This bug has been fixed upstream in http://bugzilla.gnome.org/show_bug.cgi?id=165343 but this will not be fixed in Ubuntu until Ubuntu sets by default the option "Hyper is mapped to the Win-keys" in all keyboard layouts, as said in http://bugzilla.gnome.org/show_bug.cgi?id=165343#c57

[Pedro Villavicencio (pedro)]

Fixed upstream, thanks.

[KarlGoetz (kgoetz)]

On Tue, 2007-12-04 at 13:59 +0000, Pedro Villavicencio wrote:
> Fixed upstream, thanks.
>
> ** Changed in: control-center (Ubuntu)
> Status: Triaged => Fix Committed
>

should fix commited be used when the fix has made it to ubuntu?

[Pedro Villavicencio (pedro)]

No, When the fix has been landed into Ubuntu the status is Fix Released, since the bug has been fixed upstream and still hasn't made it into Ubuntu the status is Fix Committed, thanks !.

[KarlGoetz (kgoetz)]

On Thu, 2007-12-06 at 19:07 +0000, Pedro Villavicencio wrote:
> No, When the fix has been landed into Ubuntu the status is Fix Released,
> since the bug has been fixed upstream and still hasn't made it into
> Ubuntu the status is Fix Committed, thanks !.

seems odd, but ok :)
kk

>

[Launchpad Janitor (janitor)]

This bug was fixed in the package gnome-control-center - 1:2.21.4-0ubuntu1

---------------
gnome-control-center (1:2.21.4-0ubuntu1) hardy; urgency=low

  * New upstream version:
    about-me:
    - Add a translation hint
    - Don't mark empty and padding strings for translation
    - Remove non-functional Help button
    accessibility:
    - Don't mark padding strings for translation and add translation
      comments for the pixel order strings
    - Enable the preferred applications button
    appearance:
    - Free metacity theme after use
    - Don't mark padding string as translatable
    - Make "Open" the default action for the file choosers
    - Fix .desktop to be valid
    - Fix detection of image mimetype (LP: #173432)
    - Add shortcut for /usr/share/backgrounds to background file chooser
      and also consider it when setting the initial directory
    default applications:
    - Add support for Midori web browser
    - Don't list the oudated evolution versions nor the text web browsers
    keyboard:
    - Implement layout printing
    - Don't mark padding strings and stock items for translation
    mouse:
    - Don't mark padding string as translatable
    network:
    - Add 48x48 PNG icon version
    settings daemon:
    - Prefer beagle and tracker to gnome-search-tool
    - Use new setting from libgnome to make toolbar icon size setting work
    - Launch Nautilus with --no-desktop for the home key so we don't mess
      up the desktop for people using something else to manage the background
    - Move display settings here from gnome-session
    - Allow key bindings using Super and Meta combinations (LP: #12153, #16815)
    window:
    - Add a comment for translators
    common:
    - Don't even try to open NULL filenames, and don't leak filenames when
    detecting recursions
    - Printing NULL strings crashes on Solaris so don't do that
  * debian/control.in:
    - updated libgnomekbd requirement
  * debian/patches/16_preferred_applications_list_cleanup.patch:
    - updated, some of the changes have been applied upstream now
  * debian/patches/25_window_manager_settings.patch,
    debian/patches/99_autoreconf.patch:
    - updated
  * debian/patches/18_add_onboard_to_preferred_apps.patch,
    debian/patches/101_gnome_at_properties_active_preferred_apps_without_at.patch:
    - dropped, fixed with the new upstream version

 -- Sebastien Bacher <email address hidden> Wed, 09 Jan 2008 16:13:19 +0100

[Stefan Bethge (kjyv)]

zelrik:
I had this exact problem too and found that it was caused by an old xorg.conf from feisty that I copied over. The culprit was this line:
Option XKbVariant "de"
I removed it and all was fine again, so it might be because of a non-existing variant in there for some.

[der_vegi (m-may)]

Still present in Hardy Alpha 5 (amd64).

[sibidiba (sibidiba)]

I can confirm this bug on current Hardy (alpha 5).

The solution was to switch system / preferences / keyboard / layouts / layout options... / alt//win behavior from default to super .

Now it works fine.

I didn't modify my kbd section in xorg.conf :

Section "InputDevice"
        Identifier "Generic Keyboard"
        Driver "kbd"
        Option "XkbRules" "xorg"
        Option "XkbModel" "pc105"
        Option "XkbLayout" "hu"
        Option "XkbVariant" "102_qwertz_dot_nodead"
        Option "XkbOptions" "lv3:ralt_switch"
EndSection

[der_vegi (m-may)]

Yes, I agree with Gabor, changing the Alt/Win key behaviour to "Super is mapped to the Win-keys", fixes this.

So is the status "Fix Released" for this bug really right, as it does not work by default? This bug is also discussed in Brainstorm http://brainstorm.ubuntu.com/idea/2051/ , the people commenting are also wondering, why it is "Fix Released"...

[Daniel Sargeant (dsargeant)]

Changing the keyboard layout does work for me as well, using Gutsy (that I believe was upgraded from at least Feisty, so is not a fresh install). I noticed that the "Super is mapped to the Win-keys (default)" claims it's default. The problem, I think, is that "Alt and Meta are on the Alt keys (default)" also claims it is default and is higher in the list of options.

[Daniel Sargeant (dsargeant)]

I'm changing this to confirmed since the gnome bug (http://bugzilla.gnome.org/show_bug.cgi?id=165343) was reopened and the issue persists in default Ubuntu installs.

[Brian Pontarelli (brian-pontarelli)]

I tried the layout tweak with "Super is mapped to the Win-keys" and it doesn't work for me. The keyboard-shortcuts application then interprets the Win-key as Mod4 and will allow me to set things to something like "Mod4+P", but the rest of Gnome doesn't see the key event once set. I don't have anything funky in my xorg.conf file and something else that is odd is that compiz settings interpret the Win-key just fine. They allow me to set shortcuts using it and get the correct signals.

[aidave (aidave)]

I have this issue too. Super key and another key just wont map. Isnt that a song by Loverboy? Anyways, I wonder if there is a text file we can edit, and manually set these, and see if it works that way? Maybe its just an issue with the Keyboard Shortcuts applet?

[Ralf Nieuwenhuijsen (ralf-nieuwenhuijsen)]

I'm not sure if it's related, but I'm hitting this weird behavior:

 - super key is treated as normal key rather than a modifier in gnome-shortcuts settings
 - super key is treated as a modifer in compiz-config-advanced

So, when i use ccsm i can setup the super-key to do take care of all window related settings.
When I then go to gnome-shortcuts settings, all the keys are displays without the <super> modifier.

Super should be a modifier in gnome, yet it seems specifically for gnome, it's not.

[Ralf Nieuwenhuijsen (ralf-nieuwenhuijsen)]

Oh forgot to say: this is with hardy!

[Nicolas Piguet (npiguet)]

I can confirm the behavior reported by Ralf Nieuwenhuijsen. Additionally, I can also confirm that the Windows key is treated as a normal key when setting up the shortcuts through the keyboard shortcuts application. Every time I try to set up a shortcut that uses the WinKey, it is set as "Super L", which I think means "Left Super" and not "<Super>L". ccsm captures the shortcuts properly. I managed to setup the shortcut to my desktop to <Super>D with gconf-editor, and it works properly, so this sems to be a bug that is purely into the keyboard shortcuts application.

I'm also using Hardy, and I think this is definitely worth fixing before the final release.

[Martin Olsson (mnemo)]

I just upgraded to the pre-release hardy and this bug is my biggest wish-list item. I really prefer to use my regular keyboard short cuts (especially since I have to use Windows a lot at work and it turns out it's sort of difficult to keep switching between ubuntu and windows keyboard reflexes).

[Paul Natsuo Kishimoto (khaeru)]

Cardy's (#38 above) solution works for me in Gutsy.

I am observing the same behaviour as noted above:
- Setting "Super is mapped to the Win-keys (default)" in Keyboard Preferences causes
Keyboard Shortcuts to accept the Win-key as a modifier
- The displayed result is "Mod4+Page_Down" or similar
- In gconf-editor, the corresponding key in /apps/gnome_settings_daemon/keybindings/ has a value of e.g. "<Mod4><Hyper>Page_Down"
- The shortcut doesn't actually work.

Some additional things I've observed:
- Manually changing the gconf key to "<Mod4>Page_Down" or "<Hyper>Page_Down" has no effect.
- Trying the same process with "Hyper is mapped to the Win-Keys" set in Keyboard Preferences produces *identical* results (including the values of the gconf keys).
- Setting "Press any of Win-keys to choose 3rd level" in Keyboard Preferences causes "Mod5+Key" to be recorded in Keyboard Shortcuts, with a matching "<Mod5>Key" visible via gconf-editor. However, the shortcut does not work.
- The fix suggested by Cardy (manually entering <Win>Key in gconf-editor) works regardless of *any* settings concerning the Win-keys in Keyboard Preferences.

I hope this extra information helps.

[ross (ross-rossmoore)]

I'm on Gutsy, on a PC, with a UK keyboard. I've had similar problems to some of the posters here. Pressing <Left windows>+t launches a terminal, which is good - I asked it to do this.
Pressing <Left windows>+e does not launch my home folder, despite me asking it to do so in exactly the same way.

I liked Cardy's solution of manually typing <Win>e into gconf-editor. This worked, kind of - except it soon became clear that Gnome was just ignoring the <Win> part, and was launching Nautilus every time I pressed the 'e' key. Not ideal.

Are others finding this problem with Cardy's solution (and backed up by Paul K)? Any other work-arounds? I can live without <Win>e launching nautilus, but I'm not sure my wife can!

[Ralf Nieuwenhuijsen (ralf-nieuwenhuijsen)]

You can use compiz's advanced settings tool. That seems to work fine for me.

2008/4/21, ross <email address hidden>:
> I'm on Gutsy, on a PC, with a UK keyboard. I've had similar problems to some of the posters here. Pressing <Left windows>+t launches a terminal, which is good - I asked it to do this.
> Pressing <Left windows>+e does not launch my home folder, despite me asking it to do so in exactly the same way.
>
> I liked Cardy's solution of manually typing <Win>e into gconf-editor.
> This worked, kind of - except it soon became clear that Gnome was just
> ignoring the <Win> part, and was launching Nautilus every time I pressed
> the 'e' key. Not ideal.
>
> Are others finding this problem with Cardy's solution (and backed up by
> Paul K)? Any other work-arounds? I can live without <Win>e launching
> nautilus, but I'm not sure my wife can!
>
>
> --
> Cannot use Windows key in keyboard shortcuts
> https://bugs.launchpad.net/bugs/12153
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[ross (ross-rossmoore)]

Ralf,
Thanks, but that doesn't work for me. Compiz advanced settings->General Options->Actions
If I set Command 0 set to run nautilus, and set Run Command 0 to Super+Y, then pressing <Win>y launches nautilus.
If I set Run Command 0 to Super+E, pressing <Win>e does nothing.

The <Win>e combination is being treated differently to the <Win>y combination. It's almost like something else already has <Win>e reserved for some other function, but that function isn't doing anything.

[Bogdan Butnaru (bogdanb)]

I just tried and <Super>+E works for me in Compiz. You can check if it's already grabbed by something else:

1) Check in the gnome keyboard shortcuts if it's assigned to anything, even if it doesn't work there disable it. (I disabled all gnome's shortcuts and re-done them in compiz.)

2) In ccsm (compiz advanced settings) go to "Advanced Search" (on the left, bottom), check only "settings value" on the left, and enter "super" (lower-case; I don't know why "Super" doesn't work for search). It'll show you on the right all settings that use it. It might be taken by something else. (I just disabled all shortcuts I don't use, to be sure.)

[Bogdan Butnaru (bogdanb)]

Oh, Amarok also has some global shortcuts, if you use it look at its settings, too.

[matrix35 (musallam001)]

unsubscribe

----- Original Message ----
From: Bogdan Butnaru <email address hidden>
To: <email address hidden>
Sent: Monday, April 21, 2008 9:51:51 AM
Subject: [Bug 12153] Re: Cannot use Windows key in keyboard shortcuts

I just tried and <Super>+E works for me in Compiz. You can check if it's
already grabbed by something else:

1) Check in the gnome keyboard shortcuts if it's assigned to anything,
even if it doesn't work there disable it. (I disabled all gnome's
shortcuts and re-done them in compiz.)

2) In ccsm (compiz advanced settings) go to "Advanced Search" (on the
left, bottom), check only "settings value" on the left, and enter
"super" (lower-case; I don't know why "Super" doesn't work for search).
It'll show you on the right all settings that use it. It might be taken
by something else. (I just disabled all shortcuts I don't use, to be
sure.)

--
Cannot use Windows key in keyboard shortcuts
https://bugs.launchpad.net/bugs/12153
You received this bug notification because you are a direct subscriber
of the bug.

      __________________________________________________________________
Be smarter than spam. See how smart SpamGuard is at giving junk email the boot with the All-new Yahoo! Mail. Click on Options in Mail and switch to New Mail today or register for free at http://mail.yahoo.ca

[ross (ross-rossmoore)]

Thanks all. Seems to be working now. I think gconf-editor and compiz were arguing with each other; it went after I deleted all appropriate references in gconf-editor (even where they were launching nautilus themselves), and just let compiz do the work.

[Christoffer Gurell (orbit-0x63)]

In 8.04 I cannot use windows key as a modifier for keyboard shortcuts. When i press the key it says Super-L and I cannot type any additional key for that shortcut.

[ross (ross-rossmoore)]

Christoffer,

I remember having this, but can't quite remember the solution. I _think_ it was fixed by doing this:
System->Keyboard
Then on one of the tabs there's a list of options that you can switch on/off. One of them is about alt keys and the windows key. You have to toggle that switch, which stops the windows key being picked up as a single key press and makes it a modifier.

Sorry I can't confirm, my ubuntu machine is dead at the moment - I'm ordering a new laptop!

[Christoffer Gurell (orbit-0x63)]

Thanks!

Under System->Preferences->Keyboard . Layouts->Layout Options->Alt/Win Key behaviour i can select "Meta is mapped to the win keys" to make the windows key work as a modifier!

[Pedro Villavicencio (pedro)]

this has been fixed upstream, thanks for reporting.

[Sam Illingworth (mazz0)]

Hi Guys - firstly I apologise for not being very technial here - I'm quite new to Linux.

For me setting "Super is mapped to the win keys" or "Meta is mapped to the win keys" (they appear to do the same thing, and shouldn't one of them be selected by default anyway? I've installed Ubuntu on four completely different kinds of machine and have had this problem on all of them) only partially resolves the issue.

I can now assign "Windows+T" for launching the terminal, "Windows+D" for showing the desktop, but I can't assign "Windows+N" (or, indeed, Windows+anything) for opening the home folder (ie starting Nautilus). I /can/ assign Ctrl+Alt+N to open the Home Folder, just not anything beginning with the Windows key. Same thing with lock screen - "Ctrl_Alt_L" works, "Windows+L" doesn't.

For clarification - when I say "Windows+Key" I'm talking about "Mod4+Key" (as I said, I turned on "Super is mapped to the win keys" - without that I could only use the Windows key (super as it was called then, not Mod4) on its own).

I don't know how relevant it is, but I've always been able to use the windows key properly in CompizConfig, and I note that settings such as the Expo can be changed in Keyboard Shortcuts in gnome or in CompizConfig.

When Pedro says "this has been fixed upstream" does that mean the fix is yet to be released, or has been released? If the fix involves users changing the "Super is mapped to the win keys" setting then I really think the default should be changed on there - a novice would never find that!

Sorry for the over-use of brackets in the post, I just love brackets.

[Nelson Benitez (gnel)]

Sam, as far as I understand the fix will be shipped in the next version of Ubuntu (intrepid).

[Andreas Moog (ampelbein)]

Fixed in Intrepid

[Ralf Nieuwenhuijsen (ralf-nieuwenhuijsen)]

Not fixed in intrepid!

In intrepid we need to go:

System -> Preferences -> Keyboard -> Setup

"Meta is mapped to the win keys" to make the windows key work as a modifier!

[Nelson Benitez (gnel)]

Yes, as I previously commented[1], the keyboard layouts need to be changed to incorporate that setting by default!!

[1] https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/12153/comments/60

[der_vegi (m-may)]

I also confirm that is not fixed in Intrepid final. Reopen?

[Endolith (endolith)]

This is still a problem in Intrepid. It registers "Super L", but not "Super L + something". I previously would work around this by holding down Super, then clicking "New shortcut" and then pressing the letter, but this doesn't work anymore.

[Alois (flugtiger)]

In intrepid we need to go:

System -> Preferences -> Keyboard -> Setup

"Meta is mapped to the win keys" to make the windows key work as a modifier!

but now I've got another problem: When this option above is not choosen (and Super is not mapped to the Mod4) the Super_L key has no affect when trying to use any shortcut (for exemple I want to set Strg+SuperL to open my Homefolder, but when i use this combination nothing happens)
I'm useing Intrepid (in Hardy it worked fine for me.

Alex

[Endolith (endolith)]

> In intrepid we need to go:
>
> System -> Preferences -> Keyboard -> Setup

It's System -> Preferences -> Keyboard -> Layouts tab -> Other Options... button

> "Meta is mapped to the win keys" to make the windows key work as a modifier!

That's not really a solution; just a workaround. the Windows key maps to Super by default, so we should be able to use Super in keyboard shortcuts.

[Alois (flugtiger)]

This is the point, you're right, it is mapped to Super by default but when I try to use Super in a shortcut it has no affect. (declaring a shortcut with Super works and in Hardy Heron even using Super worked...)

Alex

[Joby Joseph (badjoby)]

Same issue in Jaunty alpha5.
 Super not acting as starting main menu eventhough in the keyboard short cut settings it is mapped correctly.

[Sebastien Bacher (seb128)]

somebody having the issue should open the bug on GNOME

[Aidan Fitzpatrick (afit)]

Yes -- broken on Hardy, Intrepid and Jaunty. Changing "Super is mapped to Win keys" fixes it.

Is this really an issue for GNOME now, rather than a default configuration issue with Ubuntu?

I don't see how bug #1 will ever get fixed with this one open. It's nothing to do with unusual keyboards: it's something trivial, used by many computer users, which is broken out of the box.

The GNOME bugzilla bug is unhelpfully marked as FIXED RESOLVED. I will reopen it.

[Aidan Fitzpatrick (afit)]

Original upstream http://bugzilla.gnome.org/show_bug.cgi?id=165343 is still marked as fixed; some disagreement as to what that bug was about.

I have opened a new upstream bug in libgnomekbd over the default layouts, as per Nelson's comment above. http://bugzilla.gnome.org/show_bug.cgi?id=579658

[smkururu (smkururu)]

I think this would fix the problem:
System > Preferences > Keyboard > Layouts > Layout Options > Alt/Win key behavior > Meta is mapped to Win keys

[Aidan Fitzpatrick (afit)]

That's a workaround, not a fix, and has been mentioned in this and the upstream tickets.

It's fixed when it's not broken out of the box.

[alca (alcaweb)]

i have the same problem in Jaunty (after the upgrade from intepid).

a have a question about this issue:
Does smkururu's suggestion resolve the problem or it will appear at each reboot?
does his suggestion provoke any side-effect?

[alca (alcaweb)]

yesterday i tried the workaround proposed by smkururu and i answered some questions written by me (see https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/12153/comments/106):
changing 'System > Preferences > Keyboard > Layouts > Layout Options > Alt/Win key behavior' to 'Meta is mapped to Win keys' the effect is that the AltGr button does not have a behaviour like before: no key-combination is available (i cannot use the character '@' with AltGr + ò, for example).

i think this is a bad side-effect.

any news about this issue?

[Thierry Daucourt (thierry-daucourt)]

Yesterday, I tried the workaround proposed by smkururu.
The side effect is that in Emacs Meta key is know <Win> key, and <Alt> is no more usable in Emacs.
This is not an acceptable workaround.

[gidantribal (aedo999)]

any news?

[Martin Albisetti (beuno)]

Thank you for bringing this bug to our attention. Unfortunately a paper cut should be a small usability issue that affects many people and is quick and easy to fix. I'm afraid this bug can't be addressed as part of this project.
A paper cut is a minor usability annoyance that an average user would encounter on his/her first day of using a new installation of Ubuntu 9.10.

[Sam Illingworth (mazz0)]

I've just read through this entire thread - to summarize:

It seems we have two/three issues:

1) The out-of-the-box behaviour only allows the windows key to be used on it's own, not as part of a shortcut using the keyboard shortcut applet

2) The workaround of setting super or meta is mapped to the windows key only makes it work for some commands but not others - someone suggested this is due to whether the shortcuts are stored in different places:
  Philipp Kohlbecher wrote on 2007-06-04:
  The difference seems to be that the shortcut for launching the terminal is set in gconf setting /apps/metacity/global_keybindings (as is the shortcut for minimizing all windows to show the desktop, for example), while the shortcut for locking the screen is set in /apps/gnome_settings_daemon/keybindings (as is the shortcut for launching the web browser, for example)

3) The workaround apparently breaks the behaviour of Alt Gr:
   alca wrote on 2009-04-27:
  yesterday i tried the workaround proposed by smkururu and i answered some questions written by me (see https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/12153/comments/106):
changing 'System > Preferences > Keyboard > Layouts > Layout Options > Alt/Win key behavior' to 'Meta is mapped to Win keys' the effect is that the AltGr button does not have a behaviour like before: no key-combination is available (i cannot use the character '@' with AltGr + ò, for example)

Anyone have anything to add? More details, more complaints, progress updates? Do we have any developers looking into this?

[Karl Hegbloom (karl.hegbloom)]

On Mon, 2009-06-22 at 15:56 +0000, Sam Illingworth wrote:h
> The difference seems to be that the shortcut for launching the
> terminal is set in gconf setting /apps/metacity/global_keybindings (as
> is the shortcut for minimizing all windows to show the desktop, for
> example), while the shortcut for locking the screen is set
> in /apps/gnome_settings_daemon/keybindings (as is the shortcut for
> launching the web browser, for example)

Which begs the question... Why isn't there a central place for all
keybindings and mouse + stylus gestures? That would be the best thing,
so that there's less of a question as to what application controls
bindings where, perhaps... ?

--
Karl Hegbloom <email address hidden>

[Aidan Fitzpatrick (afit)]

Great comment, Sam. This is getting complicated. Can I propose a simple solution?

In comment 103 of this I described the original upstream bug: http://bugzilla.gnome.org/show_bug.cgi?id=165343

The maintainer insist it's fixed but I disagreed, so I opened another against libgnomekbd as per his suggestion: http://bugzilla.gnome.org/show_bug.cgi?id=579658

Neither one seems to have gone anywhere.

PROBLEM: We can't bind-meta key combinations out of the box without changing configuration and getting unpleasant side-effects.

OBSERVATION: Compiz' CCSM tool captures the right keys perfectly out of the box.

SOLUTION: Delete the code in GNOME keyboard settings and replace it with CCSM code.

Perhaps I'm overlooking some huge technical complexity here, and maybe God kills a kitten every time the CCSM code is run, but really... it better be a big kitten for us not to use it. I'm sure the right fix involves patching libgnomekbd and blah blah blah but life is too short. And 4 years of open bug is too long.

[gidantribal (aedo999)]

how can a "medium" severity bug be OPEN for 4 years... 4 years is long...

[Sebastien Bacher (seb128)]

could somebody having the issue on jaunty take that to GNOME?

[gidantribal (aedo999)]

Aidan Fitzpatrick suggested the issue depends on gnome keyboard settings...

[gidantribal (aedo999)]

Moreover, I do appreciate irony, but kidding apart, how can a bug like this be 'low' priority?
According to 'medium' priority definition in launchpad:
   "The bug is an inconvenience for MANY users. The feature provides new ways of completing tasks.[...]"

Furthermore, IMHO a bug preventing any Ubuntu users from using a particular keyboard well known button simply can't be considered 'low'.

[Sam Illingworth (mazz0)]

Well, with Super mapped to the win keys I can now (in Jaunty) use the Windows key in any short-cut, so that appears to be part of this bug fixed. If other Jaunty users can confirm this is fixed then all that remains is to change the default setting when Ubuntu is installed.

Would that be a design decision though? If you change it to Super so you can use it as a modifier you lose the ability to use the Windows key on its own (anyone know of a workaround for that?). What's the procedure for proposing a change like this, and does everyone agree this is now working in Jaunty?

[Aaron C. de Bruyn (darkpixel2k)]

Fixed for me in Jaunty.
I can lock my screen by setting the shortcut MOD4+L.
It also works correctly when connected to a Windows machine via rdesktop.

[Aidan Fitzpatrick (afit)]

The second upstream bug I created has run its course: http://bugzilla.gnome.org/show_bug.cgi?id=579658

Suggestion is that the symbols/pc file is out of date. I will test this on my Jaunty. Others, how does it work for you?

Remember NOT to use "Super is mapped to Win keys" when testing this. That is a workaround... which we already know works, but which causes other problems. I'm trying to get Windows shortcut keys working out of the box.

[Sebastien Bacher (seb128)]

upstream suggests it's an issue in xkeyboard-config

[Aidan Fitzpatrick (afit)]

Sebastien

Upstream suggested it's an issue in xkeyboard-config _if_ the /usr/share/X11/xkb/symbols/pc file provided didn't work.

I have just tested the file that Sergey attached to the upstream and it works perfectly.

I think it's reasonable to assume the problem is our xkeyboard-config symbols/pc files are out of date.

Frustratingly, both the default file on Jaunty and the "newer", working file that Sergey sent have the same timestamp: "// $XFree86: xc/programs/xkbcomp/symbols/pc,v 1.9 2003/06/09 19:59:46 dawes Exp $"

How can we get the distro symbols/pc file updated?

[Aidan Fitzpatrick (afit)]

Sorry for the comment spam. Last one. The difference between the working and broken pc files is this:

x@y:~$ diff pc.broken-jaunty pc.fixed-sergey
22,25c22
< key <BKSP> {
< type="CTRL+ALT",
< symbols[Group1]= [ BackSpace, Terminate_Server ]
< };
---
> key <BKSP> { [ BackSpace ] };
37a35
> modifier_map Mod4 { <LWIN> };
42a41
> modifier_map Mod4 { <RWIN> };

[Sebastien Bacher (seb128)]

the karmic version seems identic to the fixed one you added there, could you try on karmic?

[Aidan Fitzpatrick (afit)]

Sebastien

I've just installed Karmic Alpha 5 under VirtualBox 3.0.4: it is even more broken.

It recognises left Windows key + R as "Alt + R" ("Alt + R" comes up as "Alt + R", too).

It recognises right Windows key as "ISO Level 3 Shift" and won't accept a modifier.

The XKB xprop settings are the same as on Jaunty.

Maybe this is an artefact of VirtualBox's key mapping, rather than a new problem? I hope so.

[ramses delgado (ramsesdm)]

hi i have de same problem that aidan, i am using karmic koala beta

[Gorka Navarrete (emrys)]

The problem is definitely solved for me in a clean Karmic 32 and 64 bits installation.

Please confirm.

[Sam Illingworth (mazz0)]

Works for me in fresh Karmic install :)

[Joe Casadonte (jcasadonte)]

I'm using the Karmix Live CD on a Lenovo T61 and it doesn't work for me. I am unable to bind <Super><Shift>1 (for example), either by typing it into Metacity or using the Keyboard Shortcuts application.

[Marco Biscaro (marcobiscaro2112)]

Upstream marked as RESOLVED NOTGNOME.