Chromium browser does not respect defined input method

Bug #1309781 reported by David Cesarino de Sousa on 2014-04-18
38
This bug affects 7 people
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Undecided
Unassigned

Bug Description

= Steps to reproduce
====================

1. Use “im-config” to select “xim” as input method. It will change your “~/.xinputrc” file to define “xim” as selected method.

= Expected behavior
===================

1. You should be able to use your “~/.XCompose” sequences in any program inside Ubuntu.

= Current behavior
==================

1. Your “XCompose” sequences won't work anywhere inside the Chromium window, and any input in Chromium will behave sometimes as the standard input (“ibus”, if I recall correctly), other times it will ignore dead keys completely (apostrophe, quotes and grave have no effect).

1.1. I say “sometimes” because I couldn't figure out what makes/when it behave in any of the two ways. But both are wrong anyway, so it does not really matter. Other programs I've tried so far (gedit, firefox and others) work correctly all the time, i.e., I can normally use my XCompose escape sequencies as expected.

= Rationale
===========

As of now, I need “XCompose” sequences in order to type special characters and diacritics easily and correctly, for portuguese. As it happens, the standard input does not provide an easy way to type c-cedilla (ç), as the input sequence (apostrophe-c) ends with a c-acute (ć) instead.

Therefore, I'd like Chromium to behave as the other programs do, i.e., using “xim” as the input method.

= lsb_release -rd
=================

Description: Ubuntu 14.04 LTS
Release: 14.04

= apt-cache policy pkgname
==========================

chromium-browser:
  Installed: 34.0.1847.116-0ubuntu2
  Candidate: 34.0.1847.116-0ubuntu2
  Version table:
 *** 34.0.1847.116-0ubuntu2 0
        500 http://br.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: chromium-browser 34.0.1847.116-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Apr 18 18:54:32 2014
Desktop-Session:
 DESKTOP_SESSION = ubuntu
 XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
 XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
DetectedPlugins:

Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
InstallationDate: Installed on 2014-04-18 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
chromium-default: CHROMIUM_FLAGS=""
gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
modified.conffile..etc.default.chromium.browser: [deleted]

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in chromium-browser (Ubuntu):
status: New → Confirmed
Akira Tanaka (popo1897) wrote :

Also I confirmed this bug with fcitx + mozc(one of Japanese Input Method)

When I open a new window (including first run) and try to input
Japanese characters into address bar but Japanese Input Method never enable.
Of course, expected behavior is that Input Method is enabled,
and I can input Japanese character into the address bar.

However, when I opened a web page with some textbox (e.g. Twitter),
I can use mozc in the textbox and after this, I can also use it in the
chromium's address bar.

I believe my comment is supplementary to David's "Current behavior."

tags: added: chromium input
description: updated

I do not know if this is useful to the maintainers, but Google Chrome (the amd64 .deb you download from Google) does NOT have this problem. It behaves just fine. This is the relevant info:

Chromium chrome://version
======================

Chromium 34.0.1847.116 (Developer Build 260972) Ubuntu 14.04 aura
OS Linux
Blink 537.36 (@170605)
JavaScript V8 3.24.35.22
Flash (Disabled)
User Agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/34.0.1847.116 Chrome/34.0.1847.116 Safari/537.36
Command Line /usr/lib/chromium-browser/chromium-browser --enable-pinch --flag-switches-begin --flag-switches-end
Executable Path /usr/lib/chromium-browser/chromium-browser
Profile Path /home/david/.config/chromium/Default
Variations 24dca50e-7ffa59d
ca65a9fe-91ac3782
5e29d81-f23d1dea
246fb659-a5822863
f296190c-a90023b1
4442aae2-a90023b1
ed1d377-e1cc0f14
75f0f0a0-d7f6b13c
e2b18481-6e597ede
e7e71889-4ad60575

Chrome chrome://version
====================

Google Chrome 34.0.1847.116 (Official Build 260972)
OS Linux
Blink 537.36 (@170605)
JavaScript V8 3.24.35.22
Flash 13.0.0.182
User Agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.116 Safari/537.36
Command Line /usr/bin/google-chrome-stable --flag-switches-begin --flag-switches-end
Executable Path /opt/google/chrome/google-chrome
Profile Path /home/david/.config/google-chrome/Default
Variations 24dca50e-837c4893
ca65a9fe-91ac3782
5e29d81-cf4f6ead
246fb659-6754d7b7
f296190c-90ee1655
4442aae2-75cb33fc
ed1d377-e1cc0f14
75f0f0a0-4ad60575
e2b18481-a90023b1
e7e71889-e1cc0f14

Just in case.

Chrome recently updated to version 35, and it DOES have the same problem. Details below. Don't mind the changed flags, it happens without them as well.

Google Chrome 35.0.1916.114 (Official Build 270117)
OS Linux
Blink 537.36 (@173968)
JavaScript V8 3.25.28.16
Flash 13.0.0.214
User Agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.114 Safari/537.36
Command Line /usr/bin/google-chrome-stable --flag-switches-begin --enable-google-now-integration --new-profile-management --enable-accelerated-overflow-scroll --force-compositing-mode --enable-threaded-compositing --flag-switches-end
Executable Path /opt/google/chrome/google-chrome
Profile Path /home/david/.config/google-chrome/Default
Variations 6dcb530d-954431d1
c70841c8-4866ef6e
3664a344-be9e69ba
9e5c75f1-ad69ceb0
c7d93845-766fa2d
24dca50e-837c4893
ca65a9fe-91ac3782
8d790604-9cb2a91c
4ea303a6-3d47f4f4
b2612322-f8cf70e2
5a3c10b5-e1cc0f14
244ca1ac-4ad60575
5e29d81-cf4f6ead
3ac60855-486e2a9c
246fb659-6754d7b7
f296190c-5192b0cf
4442aae2-e1cc0f14
ed1d377-e1cc0f14
75f0f0a0-e1cc0f14
e2b18481-6754d7b7
e7e71889-4ad60575
9992d385-61b2b4c1
cbf0c14e-bf3e6cfd

In-gu Kang (igxactly) wrote :

Affects me too.

OS Version: Ubuntu 14.04 x86_64
Desktop Environment: KDE Plasma Desktop
Input Method: uim

Chrome version info:
Chrome 35.0.1916.114 (Official Build 270117)
OS Linux
Blink 537.36 (@173968)
JavaScript V8 3.25.28.16
Flash 13.0.0.214
Variations 6dcb530d-8bcdf7a4
c70841c8-4866ef6e
9e5c75f1-ad69ceb0
c7d93845-766fa2d
24dca50e-837c4893
ca65a9fe-91ac3782
8d790604-9cb2a91c
4ea303a6-3d47f4f4
b2612322-f8cf70e2
5a3c10b5-e1cc0f14
244ca1ac-4ad60575
5e29d81-cf4f6ead
3ac60855-486e2a9c
246fb659-7564fb06
f296190c-96d26288
4442aae2-a90023b1
ed1d377-e1cc0f14
75f0f0a0-6bdfffe7
e2b18481-6e3b1976
e7e71889-e1cc0f14
cbf0c14e-bf3e6cfd

Hello everyone! I have good news.

With the release of Chrome 36 this week, Chrome 37 went into beta. So, while Chrome 36 still has this problem, I was gladly surprised when I installed the beta and noticed the issue seems to be fixed upstream. Looks like it was fixed!

Of course: this will only apply to Ubuntu when those changes are eventually pulled to everyone else using default Ubuntu packages, but if you really want to see and try, you can install the beta — which as far as I can tell is pretty stable for my daily use — right now and see for yourself.

Besides the em dash that I just typed above, here are some more for your amusement, all typed easily thanks to the flexibility of Linux systems and XCompose sequences:

©®µ—ßẞ, besides the obvious ‘single quotes’ and “double quotes” as well.

Cheers!

filipposan87 (filipposan87) wrote :

i have also noticed that in lubuntu 14.04 lte and chrome Version 42.0.2311.135 (64-bit) with SCIM japanese i can type almost everywhere on my pc and it will type japanese, but on chrome i can only type japanese IF i press right key on my mouse and then type 1 character 1 by one

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

Other bug subscribers