Intrepid broke my Home key

[Jeff Bowden]

It seems to be a system-wide problem. The Home key makes the border color change in the location box in firefox, but it doesn't move the cursor to the beginning of the line. In emacs and gnome-terminal it makes the cursor go hollow but it doesn't register as a keypress. I've tried a bunch of other apps and so far I have not found one where it works.

Ctrl-Home *does* work and the End key works.

This is a Thinkpad T43.

Please let me know what further info I can supply.

[Bryce Harrington (bryce)]

Hi jlb,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

[Jeff Bowden (jlb)]

And FYI I've been keeping my system up-to-date but so far none of the updates have fixed the problem.

[Xzorg6 (xzorg666)]

My home key doesn't move the cursor to the beginning of the line since the upgrade from Hardy.
Now when I push the home key, an green OSD on the bottom show "Lancer" (French of "Launch").

[Bryce Harrington (bryce)]

I can't reproduce this behavior.

Are you able to see the same issue when using the -ati video driver? If so, follow the tips at http://wiki.ubuntu.com/Hotkeys for debugging the issue and report your findings here.

[Jarmo Puttonen (zopaci)]

I got this bug when I used command dpkg-reconfigure -phigh xserver-xorg

[Jeff Bowden (jlb)]

I did the first step in https://wiki.ubuntu.com/Hotkeys/Troubleshooting and there was no keypress event for the home key. It says "switch to the console to troubleshoot further". I did that and the home key works fine there (e.g. for moving to the beginning of the line in bash.)

I'll try the ATI driver next.

[Jeff Bowden (jlb)]

OK, I tried the ati driver (Section "Device" Driver "ati"). OpenGL stopped working but the home key still does the same thing.

I just tried xev by itself without the sed filter suggested by the hotkeytroubleshooting page and the following output is generated when I press Home:

FocusOut event, serial 30, synthetic NO, window 0x3e00001,
    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 30, synthetic NO, window 0x3e00001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 30, synthetic NO, window 0x0,
    keys: 69 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
           0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Working keys seem to generate KeyPress and KeyRelease events instead of FocusIn, FocusOut, KeymapNotify.

[Jeff Bowden (jlb)]

I do not have a ~/.Xmodmap file (anticipating the question)

[Jeff Bowden (jlb)]

HOME key works in rdesktop! When I use rdesktop to access a Vista box the home key works correctly in the remote session.

Same is not true of accessing a remote X11 session via VNC.

[James Crawford (james-crawford)]

I had the same problem. Killing the gnome-settings-daemon caused the home key to start working for me.

I would still like to know what the proper fix for this is though.

[Jeff Bowden (jlb)]

Must be a different version of the problem from mine. killing gnome-settings-daemon has no effect on my machine other than making all the fonts and colors turn ugly.

[James Crawford (james-crawford)]

Still have this problem after upgrading to latest (9.04) Ubuntu.
Happens on both my laptop (Dell XPS M1530) and desktop (Dell Optiplex 745).

[xteejx (xteejx)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test the current Ubuntu development version (10.10). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect <bug #>, and any other logs that are relevant for this particular issue.

[Jeff Bowden (jlb)]

I'm on 10.04 now and I don't see it anymore.

[xteejx (xteejx)]

Brilliant! Glad to hear the problem is resolved. I am marking this Fix Released as it is fixed in the latest release. Thank you again for reporting this to us.