Red Hat Bugzilla – Bug 103279
gnome-character-map doesn't show keystrokes
Last modified: 2015-01-07 19:06:22 EST
For those ignorant of keymap stuff, gnome-character-map can be used to obtain
It would be really useful if it could decode the current keyboard setup and
display the keystrokes necessary to achieve each character -- and possibly even
also to allow you to _customise_ it.
I may be showing my ignorance of keyboard input stuff in X here -- but that's
sort of the _point_. People shouldn't be forced to learn the details just to be
able to enter section marks, letters with accents, etc.
I'm going through bugs assigned to me and attempting to clean some of the older,
fixed ones up.
This bug hasn't changed in over a year old now. Are you still seeing the problem?
(This a batch message is being sent to all my bugs that haven't changed in a year)
This bug has been in the NEEDINFO state for at least a couple of weeks now. I'm
going to close the bug, but if you can provide the required information feel
free to open a new report.
(This is a mass message being sent to a bunch of bug reports)
Reopening. It would still be useful for the user to be able to view and
customise the keyboard setup for non-ASCII characters somehow.
Red Hat Linux is no longer supported by Red Hat, Inc. If you are still running
Red Hat Linux, you are strongly advised to upgrade to a current Fedora Core
release or Red Hat Enterprise Linux or comparable. Some information on which
option may be right for you is available at
Red Hat apologizes that these issues have not been resolved yet. We do want to
make sure that no important bugs slip through the cracks. Please check if this
issue is still present in a current Fedora Core release. If so, please change
the product and version to match, and check the box indicating that the
requested information has been provided. Note that any bug still open against
Red Hat Linux by the end of 2006 will be closed as 'CANTFIX'. Thanks again for
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present. Since there haven't been any
updates to the report in quite a long time now after we've
requested additional information, we're assuming the problem
is either no longer present in our current OS release, or
that there is no longer any interest in tracking the problem.
Setting status to CANTFIX, however if you still
experience this problem after updating to our latest Fedora
Core release and are still interested in Red Hat tracking
the issue, and assisting in troubleshooting the problem,
please feel free to provide the information requested above,
and reopen the report.
Thank you in advance.
(this message is mass message)