1092608 - [keyboard] Number keyboard on first run shows only black area when entering SIM PIN in FTU app, taps show numbers

Status: RESOLVED DUPLICATE of bug 1092543

(Firefox OS Graveyard :: Gaia::Keyboard, defect)

Description

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

B2G 2.2 20141101040202 on Flame (v188 base image)

On first run (after a factory reset), the Number keyboard in the FTU app for entering the SIM PIN shows only a black area, but taps create numbers in the input.

Comment 1

[Rudy Lu [:rudyl] (inactive after 2015/7/3)]

I don't think this is a keyboard app regression or input management, as I cannot think of any changes that may cause this.

Asking for QA's help to find regression window on current master.

Comment 2

[John Lu [:mnjul][Please NI or I'll miss]]

Hi Jerry, I just found actually we have a bug for something I've just demo'ed you. Could you check? Thanks.

Rudy, I just encountered this and happened to demo this to Jerry. Something extra we found: if you use AppManager inspector to inspect keyboard frame, it shows (and if you "unfocus" it, it hides). We think it's probably a Gecko issue.

Comment 3

[John Lu [:mnjul][Please NI or I'll miss]]

Hi all,

I found an alternate STR that doesn't always require the condition of first run with reset:
- Just make sure you have SIM PIN enabled.
- Whenever you've just rebooted your device, Skip the SIM PIN dialog that pops up.
- Use AppManager or WebIDE to launch the FTU app.
- Following the usual FTU steps you'll see the SIM PIN dialog, where you can see the bug.

(Incidentally, I don't have lockscreen enabled.)

It does appear that you don't really need the FTU app; Messages and Phone apps can be used to reproduce the bug too.

Comment 4

[Pi Wei Cheng [:piwei] (inactive)]

Issue is NOT reproducible on the reported build. SIM pin keyboard correctly shows up on FTU in all attempts. Repro rate: 0/5

Device: Flame
BuildID: 20141101040202
Gaia: 5964f1339f37e7595aff7de7512b8529bc640b76
Gecko: 0e631971b841
Version: 36.0a1 (2.2 Master)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0


(In reply to John Lu [:mnjul] [MoCoTPE] from comment #3)
> It does appear that you don't really need the FTU app; Messages and Phone
> apps can be used to reproduce the bug too.

The behavior described here seems to be the same as bug 1093121.

Comment 5

[John Lu [:mnjul][Please NI or I'll miss]]

(In reply to Pi Wei Cheng [:piwei] from comment #4)
> (In reply to John Lu [:mnjul] [MoCoTPE] from comment #3)
> > It does appear that you don't really need the FTU app; Messages and Phone
> > apps can be used to reproduce the bug too.
> 
> The behavior described here seems to be the same as bug 1093121.

Sorry I should've been clearer: If you haven't input PIN after you boot the phone, when you launch Messages or Phone app you'll be asked to input PIN. At that moment you can see this bug.

Comment 6

[Rudy Lu [:rudyl] (inactive after 2015/7/3)]

Hi,

Please be informed this is not the same issue as bug 1093121.
For this issue, it will show a black area for the keyboard, and it is still functional that you can type on it.

Could you please help us to find the regression window again, with the following steps as comment 5 suggested? I can see this issue reproduced with current master.

Thanks.

Comment 7

[Rudy Lu [:rudyl] (inactive after 2015/7/3)]

FWIW, I found this issue could NOT be reproduced with 319MB config, so you may need to try >= 512 MB.
Guess this is related to Keyboard OOP (Out-of-Process), as we will run keyboard OOP when mem >= 512 MB.

Comment 8

[Marcia Knous [:marcia]]

I see this consistently after a fresh shallow flash of the Flame latest nightly:

Gaia   7c9e7cabbde941b976e0e40a3a1d94e21aa9c5e9
SourceStamp 62990ec7ad78
BuildID 20141105040206
Version 36.0a1
v 188
512 MB RAM

Easiest way for me to repro is to go and try to create a FX Account. The keyboard is black but receives input. Restarting the phone has no effect on fixing the issue.

Nominating for blocking as this is a clear regression.

Comment 9

[Pi Wei Cheng [:piwei] (inactive)]

(In reply to Rudy Lu [:rudyl] from comment #7)
> FWIW, I found this issue could NOT be reproduced with 319MB config, so you
> may need to try >= 512 MB.
> Guess this is related to Keyboard OOP (Out-of-Process), as we will run
> keyboard OOP when mem >= 512 MB.

Thanks for this key info on repro'ing the bug. I see the bug now with 512 mem on FTU when attempting to enter Wifi password. I've also done a quick branch check. Working on the regression window now.

Comment 10

[Pi Wei Cheng [:piwei] (inactive)]

mozilla-inbound regression window:

Last Working Environmental Variables:
Device: Flame
BuildID: 20141031020755
Gaia: 8ae6598f3ab7b0c34ac42a73083ddb74266affba
Gecko: 287ddaf9b9df
Version: 36.0a1 (2.2 Master)
Firmware: V188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0

First Broken Environmental Variables:
Device: Flame
BuildID: 20141031021654
Gaia: 8ae6598f3ab7b0c34ac42a73083ddb74266affba
Gecko: 52d9cbc1d78e
Version: 36.0a1 (2.2 Master)
Firmware: V188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0

Gaia is the same so it's a Gecko issue.

Gecko pushlog:
http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=287ddaf9b9df&tochange=52d9cbc1d78e

Caused by bug 1073252.

Comment 11

[Joshua Mitchell (Inactive)]

Caused by bug 1073252 ? can you take a look Robert?

Comment 12

[Robert O'Callahan (:roc) (email my personal email if necessary)]

Probably a duplicate of bug 1092543. Retest after that lands.

Comment 14

[John Lu [:mnjul][Please NI or I'll miss]]

FWIW, turning off Hardware Composer in Settings - Developers seems to eliminate this problem. (You need to turn on Developers menu first, of course)

Comment 15

[Jerry Shih[:jerry] (UTC+8) (inactive)]

If we turn of the hwc, we will not see this issue.
So... wait the bug 1092543 fixed and then test again.

Comment 16

[Jerry Shih[:jerry] (UTC+8) (inactive)]

Since bug 1092543 is fixed, could you test again?

Comment 17

[Pi Wei Cheng [:piwei] (inactive)]

(In reply to Jerry Shih[:jerry] (UTC+8) from comment #16)
> Since bug 1092543 is fixed, could you test again?

Verified the bug is fixed. Checked SIM pin in FTU, Wifi password in FTU, and Firefox account creation screen in Settings under 512MB memory. None of these circumstances reproduced the bug.

Device: Flame (512MB mem, shallow flash)
BuildID: 20141107063242
Gaia: 779f05fead3d009f6e7fe713ad0fea16b6f2fb31
Gecko: 002e8ed9ddf3
Version: 36.0a1 (2.2 Master)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0

Comment 18

[Rudy Lu [:rudyl] (inactive after 2015/7/3)]

Lets dupe this to bug 1092543.