Description of problem: logitech internet keyboard 350 ps/2 grey buttons (arrows,home,end,page up,page down,insert and delete do not work in GNOME. While they work fine in console (init level 3) and even in GDM. While there is no short cut is setup on arrows - each pressing on arrow calls screenshort application. This did not happen on Fedora 9 and happened after upgrade.
Seems this happens only under users created before upgrade from FC9 to FC10. On new created users arrows work fine.
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf, if available) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Created attachment 327593 [details] xorg.conf
Created attachment 327594 [details] Xorg.0.log the Xorg.log file you asked
This bug seems to be a 6 month old https://bugs.launchpad.net/gentoo/+bug/255008
(In reply to comment #1) > Seems this happens only under users created before upgrade from FC9 to FC10. > On new created users arrows work fine. make sure you have xkeyboard-config 1.4 installed and in the gnome keyboard configuration dialogs chose the keyboard model evdev for now. Does that fix it? If not, what keyboard configuration to you have in gnome?
Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as INSUFFICIENT_DATA.