Ubuntu

chromium-browser, once told to use emacs key bindings, never forgets

Reported by Jeff Abrahamson on 2012-04-19
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Undecided
Unassigned

Bug Description

It appears that saying

    $ gconftool-2 -t string -s /desktop/gnome/interface/gtk_key_theme Emacs

works correctly (in the sense that it causes chromium-browser to adopt emacs key bindings), but that reversing the action

    $ gconftool-2 -t string -s /desktop/gnome/interface/gtk_key_theme Default

does not cause chromium-browser to revert to default keybindings.

Perhaps something in my testing has gone awry, and I'm open to suggestions. In any case, chromium-browser interprets C-w as clear text rather than closer window, C-a as beginning of line rather than select all, etc. And yet

    jeff@london:~ $ gconftool-2 --get /desktop/gnome/interface/gtk_key_theme
    Default
    jeff@london:~ $

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: chromium-browser 18.0.1025.142~r129054-0ubuntu0.11.10.1
ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22
Uname: Linux 3.0.0-17-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Thu Apr 19 21:11:03 2012
Desktop-Session:
 DESKTOP_SESSION = ubuntu
 XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg
 XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
EcryptfsInUse: Yes
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to oneiric on 2012-01-09 (101 days ago)
chromium-default: CHROMIUM_FLAGS=""

Jeff Abrahamson (jeff-purple) wrote :
Jeff Abrahamson (jeff-purple) wrote :

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.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers