Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 119441 - Windows key inoperative
Windows key inoperative
Product: Fedora
Classification: Fedora
Component: xorg-x11 (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: John Dennis
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2004-03-30 10:44 EST by Wayne Walker
Modified: 2007-11-30 17:10 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-03-31 16:53:11 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Wayne Walker 2004-03-30 10:44:36 EST
Description of problem:

Upgraded to Fedora Core 2 test2 this morning (Thanks guys!!)
The "Windows" key on the keyboard is no longer active (I use icewm and
the key was working at Fedora Core 2 test1 yesterday)

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

How reproducible:

Steps to Reproduce:
1. Use a window manager that is sensitive to the "Windows" key.
2. Press the Windows key, see menu not open up...
Actual results:
See menu not open up.

Expected results:
See menu open up.

Additional info:
I did NOT perform any new X windows configuration.  This is the same
config I was using with Fedora Core 2 test1 (which was an upgrade from
production Fedora Core 1)
Comment 1 John Dennis 2004-03-30 10:49:30 EST
Since I'm looking at other keyboard issues in the xorg release I might
as well take this one too.
Comment 2 John Dennis 2004-03-31 16:53:11 EST
X is mapping both windows keys, you can verify this by running xev.
It's being mapped to the keysym SuperL and SuperR which is the same
mapping as in previous releases. I don't use icewm, but using the
standard gnome setup I can successsfully bind the windows key. I can
find no problem in the xorg-x11 component.

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