Red Hat Bugzilla – Bug 250099
Some keys on the botto. row of keyboard don't work
Last modified: 2018-04-11 07:50:53 EDT
Description of problem:
So.e keys on the botto. of the keyboard (guess whi.h ones?) of the laptop I use
just don't show up in Gno.e. I thought that the notebook is falling apart but
keyboard works perfe.tly well both in .onsole and in GDM.
Currently I a. using Xorg w/o the .onfiguration file whatsoe.er, but .y lo.ale
is CZeCh one (seeMs like upper-Case letter work!)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.write soMething soMewhere
soMe keys don't show up (MCXZV)
Created attachment 160246 [details]
Created attachment 160379 [details]
sCreenshot with displayed XEV
The strange thing is that it sees like whole keyboard departent is doing just
well thank you, but for GnoMe MMissing froM the piCture.
Created attachment 160425 [details]
Of course, (as a Czech proverb says) smith's horse is always barefoot, so I
forgot to attach the interesting info about this computer.
Created attachment 160426 [details]
There seems to be a way around this problem -- [caps lock] switched on,
[SHIFT]ed keys are working in writing correct lowercase letters. But it is a
darn inconvenient for writing longer texts.
After IRC chat on #desktop Behdad persuaded me, that the problem is not in Xorg,
but they I have some nonsense in gconf. After removal ~/.gconf keyboard works
again, but well -- removing of .gconf sucks ;-).
Currently, I have limited whole problem to 1.6MB gconf dump. Will try to
investigate more. Should I assign it?
Created attachment 160601 [details]
gconf dump corrupting my keyboard
I think I have managed to localize the problem to the attached gconf settings.
When I load error.xml it breaks my keyboard, when I load original settings and
unload error.xml everything is all right. Any ideas, what's wrong with it?
So either gnome-settings-daemon does something wrong when grabbing those key
combinations, or the super modifier is behaving wierd in your xkb setup
*sigh*, i know what's going on... one sec
which was bug 201176.
We "fixed" the problem by only allowing multimedia keys to be set to those
actions. <Super>-P just isn't allowed for x.
Either you somehow bypassed the checks that disallow it, or you had it set in
your configuration before we disallowed it (or we've since dropped the checks)
Not quite sure why this is assigned to behdad, moving to control-center-maint
(In reply to comment #11)
> Not quite sure why this is assigned to behdad, moving to control-center-maint
I was talking with him about it on IRC, of course, if you know better target for
my wrath, just go ahead. ;-)
And halfline asked me to note, that I haven't bothered with any setting tools (I
don't know if there is any) and set these values directly with gconf-editor.
Oh sorry, that's you :-)
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.
Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.
Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:
The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008.
Fedora 7 is no longer maintained, which means that it will not
receive any further security or bug fix updates. As a result we
are closing this bug.
If you can reproduce this bug against a currently maintained version
of Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.