Gnome Terminal letter e doesn't work

[Cay Horstmann]

I am running Ubuntu Jaunty, and have a very odd problem with gnome-terminal. In gnome-terminal, and only gnome-terminal, the lowercase e doesn't work. It had worked fine ever since I installed the Jaunty alpha on this machine and stopped working today. A reboot didn't cure it, and neither did changing the keyboard in System->Preferences->Keyboard.

Uppercase E works fine in gnome-terminal. In all other apps, e works fine.

This seems similar to https://answers.launchpad.net/ubuntu/+source/gnome-terminal/+question/12115, but the remedy suggested there, to run bind e:self-insert, does not work for me. In fact, running bind -p shows that e is already bound to self-insert.

I am not using xmodmap and I am not customizing X input in any other way.

$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04

$ apt-cache policy gnome-terminal
gnome-terminal:
  Installed: 2.26.0-0ubuntu2
  Candidate: 2.26.0-0ubuntu2
  Version table:
 *** 2.26.0-0ubuntu2 0
        500 http://us.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

[Cay Horstmann (cay)]

I had a look at Edit->Keyboard shortcuts in Gnome Terminal and noticed that the paste key was bound to Super+e. This was the problem. When I changed it to Ctrl+Shift+E, the e key worked fine again. Changing it to Super+e broke it once again. Look like a genuine bug in Gnome Terminal.

[Lars Ljung (larslj)]

I see the same behaviour with super+w and super+r, so I suppose the super key doesn't work at all with gnome-terminal.

[Pedro Villavicencio (pedro)]

Thanks for your report, that's something to send directly upstream at http://bugzilla.gnome.org by someone having the issue, for forwarding instructions please read http://wiki.ubuntu.com/Bugs/Upstream/GNOME, Thanks in advance.

[Pedro Villavicencio (pedro)]

any news on this, did you sent the bug upstream? may you tell us the bug number or it's ok to close the bug?

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.