This was not, in the end, a chromium-browser problem but a gnome problem. Oddly, gconftool showed the problem fixed when it wasn't. But gnome-tweak-tool showed the key bindings still to be emacs, and changing that back to Default fixed the problem immediately.
This is a bug -- it shouldn't be so difficult, and different tools shouldn't report different state. But it's not a bug in chromium- browser. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/985834 Title: chromium-browser, once told to use emacs key bindings, never forgets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/985834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs