Closed Bug 1049426 Opened 10 years ago Closed 10 years ago

[Flame] Screen is shifted some pixels up

Categories

(Firefox OS Graveyard :: Gaia, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(b2g-v2.1 unaffected)

RESOLVED WORKSFORME
Tracking Status
b2g-v2.1 --- unaffected

People

(Reporter: frsela, Unassigned)

Details

(Keywords: regression)

Attachments

(3 files)

Attached image 2014-08-06-11-12-47.png
The screen is shifted some pixels up.

To reproduce it:

1.- Set Airplane mode on
2.- Set Airplane mode off
3.- In the PIN screen: introduce a bad PIN
4.- Set the correct PIN

The screen is shifted.
QA Wanted for branch checks.
Keywords: qawanted
QA Contact: rkuhlman
The screen will be displayed incorrectly if time the user user inputs an incorrect SIM PIN followed by entering the correct SIM PIN on today's Master build

1) Launch Settings >> SIM Manager >> SIM Security >> Enable SIM PIN
2) Toggle airplane mode off/on.
3) Enter incorrect SIM and press 'OK'
4) Enter correct SIM and press 'Submit'


Issue DOES repro on today's Master M/C
Device: Flame Master M/C
BuildID: 20140806040201
Gaia: 88295e1ec6d52bd63d45ea0e3673a3f933f4a6b9
Gecko: 6cbdd4d523a7
Version: 34.0a1
Firmware Version: v123
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Issue DOES NOT repro on v2.0
Device: Flame v2.0
BuildID: 20140806000200
Gaia: 5ba22d458fdb63bd72c59de53c701d0efe35c1e2
Gecko: 6fbc60a80c6d
Version: 32.0
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Issue DOES NOT occur on v1.4
Device: Flame v1.4
BuildID: 20140806000204
Gaia: 6bbf43f22812a3c53225f62960fa7e9be4d45f6b
Gecko: f215ba345b9b
Version: 30.0
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

adding regression and regression-window-wanted tags
Flags: needinfo?
Attached file WrongSIMPIN.txt
Attaching Logcat of issue occuring
Flags: needinfo?
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
qa-triage - not nomming - seems a bit of a fringe case with those steps, especially first entering the wrong sim-pin.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
(In reply to Joshua Mitchell [:Joshua_M] from comment #5)
> qa-triage - not nomming - seems a bit of a fringe case with those steps,
> especially first entering the wrong sim-pin.

I think the STR seems realistic to me - this is a basic use case when someone gets their pin incorrect & gets it right on the next shot.
Flags: needinfo?(jmitchell)
(In reply to Jason Smith [:jsmith] from comment #6)
> (In reply to Joshua Mitchell [:Joshua_M] from comment #5)
> > qa-triage - not nomming - seems a bit of a fringe case with those steps,
> > especially first entering the wrong sim-pin.
> 
> I think the STR seems realistic to me - this is a basic use case when
> someone gets their pin incorrect & gets it right on the next shot.

This is typical of someone who does a type-o on the first pin attempt, realizes they typed it incorrectly, and fixes it on the next attempt.
(In reply to Jason Smith [:jsmith] from comment #7)
> (In reply to Jason Smith [:jsmith] from comment #6)
> > (In reply to Joshua Mitchell [:Joshua_M] from comment #5)
> > > qa-triage - not nomming - seems a bit of a fringe case with those steps,
> > > especially first entering the wrong sim-pin.
> > 
> > I think the STR seems realistic to me - this is a basic use case when
> > someone gets their pin incorrect & gets it right on the next shot.
> 
> This is typical of someone who does a type-o on the first pin attempt,
> realizes they typed it incorrectly, and fixes it on the next attempt.


I don't dispute that - but to occur immediately following toggling air-plane mode on and then off? it seems an odd combo of behavior
Flags: needinfo?(jmitchell) → needinfo?(jsmith)
Are you able to reproduce this without toggling airplane mode on/off?
Flags: needinfo?(jsmith) → needinfo?(jmitchell)
[Blocking Requested - why for this release]:

After conferring with Ross - the QA-Wanted tester who served this task - it does occur without the air-plane mode toggle but at a reduced rate. Based on this new info I would nom this
blocking-b2g: --- → 2.1?
Flags: needinfo?(jmitchell)
Hello, I have tested with Flame (Gecko-ca5d875 - Gaia-fee004d) and the bug seems to be solved.
QA Contact: rkuhlman → pcheng
Unable to reproduce this bug on Flame 2.1 latest build.

Actual Result: No screen shifting is seen when following either sets of STR's listed above. Also checked without airplane mode.

Repro Rate: 0/15 attempts

Environmental Variables:
Device: Flame Master
Build ID: 20140807084328
Gaia: 54c3c19d439f7dbafda5c6cc3b4850b545a068ba
Gecko: 2f198e81ed98
Version: 34.0a1 (Master)
Firmware Version: v123
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Keywords: qawanted
QA Contact: pcheng → croesch
bug no longer reproduces in the latest
Status: NEW → RESOLVED
Closed: 10 years ago
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
Resolution: --- → WORKSFORME
blocking-b2g: 2.1? → ---
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: