1387396 - Accents from keyboard not working on Nightly+ubuntu

Status: UNCONFIRMED

(Core :: Widget: Gtk, defect, P5)

Description

[Wellington Torrejais da Silva]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:56.0) Gecko/20100101 Firefox/56.0
Build ID: 20170801070618

Steps to reproduce:

Hi,

recently my accents from keyboard typing not working.
Copy or language correction suggestion fix the words.

I think the problem with accents is related to the last Nightly Updates, I tried in private mode and problem still occurs.

My version: 56.0a1 (2017-08-01) (64-bit)

Complete info:
https://gist.github.com/wellington1993/cc4e57110a8e3de5a132f2d2b479cace




Actual results:

Typing Accents just not working, but copy and display work fine.


Expected results:

I need type accents.

Comment 1

[Makoto Kato [:m_kato] (PTO until May 6)]

What's current keyboard method?  ibus?  fcitx? uim?

Comment 2

[Wellington Torrejais da Silva]

Hi,

The current keyboar methos is: Fcitx
fcitx version: 4.2.9.1

But accents work at terminal and in other programs.
Only Nightly don't "accept" the accents.

The accents just ignored. At textareas, inputs and the same for searchbox and addressbar.

Thanks.

Comment 3

[Makoto Kato [:m_kato] (PTO until May 6)]

Although I test on Ubuntu 16.04 + latest Nightly, [Shift] + [Control] + [u], then [e], [9] and [enter] can input "é".

Please add details and steps to reproduce this.

Comment 4

[Wellington Torrejais da Silva]

Hi,

I have a ABNT2 keyboard (Brazilian), and I just pressed the accent key: ´ (https://en.wikipedia.org/wiki/Acute_accent)
and after the key e or another.

Just work out of browser. At Windows 10 the problem not occurred but still on my Lubuntu/Ubuntu 17.04

I'm here if you need more details.

Thanks.

Comment 5

[Makoto Kato [:m_kato] (PTO until May 6)]

Ah, Brazilian keyboard. Nakano-san may have it.

Comment 6

[Firefox Bug Husbandry Bot]

https://bugzilla.mozilla.org/show_bug.cgi?id=1552613

Comment 7

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)(PTO: 5/2-5/10)]

I don't have environment to check this right now. Reporter, do you still see this bug? And if so, do you check it in an editable element such as <input> or non-editable element like bug 1077411?