Closed
Bug 1089529
Opened 10 years ago
Closed 10 years ago
Lockscreen error after screen off and on when device shows NFC shrinking UI
Categories
(Firefox OS Graveyard :: Gaia::System::Lockscreen, defect)
Tracking
(blocking-b2g:2.1+, b2g-v2.0 verified, b2g-v2.0M fixed, b2g-v2.1 verified, b2g-v2.2 verified)
People
(Reporter: ashiue, Assigned: gweng)
References
Details
(Whiteboard: [2.1-bug-bash][TPE])
Attachments
(3 files)
*** Build Information
Gaia-Rev 0f76e0baac733cca56d0140e954c5f446ebc061f
Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/7d78ff7d25b6
Build-ID 20141023161200
Version 34.0
Device-Name flame
FW-Release 4.4.2
FW-Incremental eng.cltbld.20141023.194921
FW-Date Thu Oct 23 19:49:35 EDT 2014
Bootloader L1TC00011880
Base image: v188 base image
*** Description
Lockscreen error after screen off and on when device shows NFC shrinking UI
*** Steps to Reproduce
1. 2 devices enable NFC and enable screen lock
2. Device A open an URL
3. Tap 2 phones together
4. When device A shows shrinking UI, screen off device A
5. Screen on device
6. Rotate device and check the lock screen
*** Expected Results
1. Lock screen could not be rotated
*** Actual Results
1. Lock screen error, please refer: http://youtu.be/RCELrn_TTVw
*** Reproduction Frequency: 100%
Reporter | ||
Updated•10 years ago
|
Whiteboard: [2.1-FC-bug-bash][TPE]
Reporter | ||
Updated•10 years ago
|
QA Whiteboard: [COM=NFC]
Blocks: NFC-Gaia
Whiteboard: [2.1-FC-bug-bash][TPE] → [2.1-bug-bash][TPE]
Comment 1•10 years ago
|
||
[Blocking Requested - why for this release]:
nice bug. this unlocked the orientation lock of lockscreen via the NFC/power off steps.
blocking-b2g: --- → 2.1?
Comment 3•10 years ago
|
||
Issue is reproducible on Flame 2.2, Flame 2.1, Flame 2.0, and Flame base v188-1 (v2.0) only.
Observed behavior: Orientation on lockscreen can be rotated to horizontal after following STR. One minor UI difference - On 2.0 and 2.2 the lockscreen can be rotated fully without seeing the website beneath the lockscreen (as demonstrated by reporter's video), but user still can't unlock the device in horizontal orientation.
Device: Flame 2.2 Master
BuildID: 20141105120748
Gaia: 7918024c737c4570cacd784f267e28737ae05dea
Gecko: b6cd2dd85b26
Version: 36.0a1 (2.2 Master)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
Device: Flame 2.1
BuildID: 20141105132045
Gaia: 1ca22badfae2f9ce066c2405af3e85c4e2d5d380
Gecko: 1b076c5a760c
Version: 34.0 (2.1)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Device: Flame 2.0
BuildID: 20141105135049
Gaia: 5ee26701a4d8db266bfb203b2179f686ce14d8b6
Gecko: dbf49343e889
Version: 32.0 (2.0)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [COM=NFC] → [COM=NFC][QAnalyst-Triage?]
status-b2g-v2.0:
--- → affected
status-b2g-v2.1:
--- → affected
status-b2g-v2.2:
--- → affected
Flags: needinfo?(jmitchell)
Keywords: qawanted
Updated•10 years ago
|
QA Whiteboard: [COM=NFC][QAnalyst-Triage?] → [COM=NFC][QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
Comment 4•10 years ago
|
||
This seems like a lockscreen regression (despite it perhaps not being a regression when taking NFC into account). Greg, is this related to bug 1081132?
Triagers discussed this and think it should block.
blocking-b2g: 2.1? → 2.1+
Flags: needinfo?(gweng)
Assignee | ||
Comment 5•10 years ago
|
||
I think the Bug 1081132 should fix it, not result it. But I would do some bisect to make sure what's the first broken patch.
Flags: needinfo?(gweng)
Updated•10 years ago
|
Assignee: nobody → gweng
Assignee | ||
Comment 6•10 years ago
|
||
Wait a minute: this is not a regression and we didn't handle this case since v2.0 according to Comment 4. We need to take a look about the root cause.
Assignee | ||
Comment 7•10 years ago
|
||
Alive: another orientation series bug... And I can't submit the master version since on current master NFC is broken. I would submit the patch after the master is back.
Attachment #8519706 -
Flags: review?(alive)
Updated•10 years ago
|
Attachment #8519706 -
Flags: review?(alive) → review+
Assignee | ||
Comment 8•10 years ago
|
||
The 2.1 patch encountered serious CI issue:
https://treeherder.mozilla.org/ui/#/jobs?repo=gaia-try&revision=16488d64eb34
Some of the failures are intermittent (Gu and Gip). However, the Gij now is permanent red at #3 and #4 job, and it's also red at another test patch's test result:
https://treeherder.mozilla.org/ui/#/jobs?repo=gaia-try&revision=5bbd7556a22d
So I think my patch break nothing, and can submit the v2.1 approval.
Assignee | ||
Comment 9•10 years ago
|
||
Alive: almost the same patch except it's for v2.2 (master). And I need to submit v2.0 patch which may be very different...
Attachment #8519728 -
Flags: review?(alive)
Assignee | ||
Comment 10•10 years ago
|
||
Comment on attachment 8519706 [details] [review]
Patch v2.1
[Approval Request Comment]
[Bug caused by] (feature/regressing bug #): Orientation API design issue + Gaia didn't capture this case since 2.0
[User impact] if declined: Bug still open
[Testing completed]: Gaia-Try with intermittent and other irrelevant failures. See above comment.
[Risk to taking this patch] (and alternatives if risky): No obvious risk.
[String changes made]: No
Attachment #8519706 -
Flags: approval-gaia-v2.1?(fabrice)
Assignee | ||
Comment 11•10 years ago
|
||
Basically is copying the previous versions to this one.
The difference is v2.0 need no resizing which is necessary for v2.1 and v2.2 to avoid the splitting window issue, as the video shows.
Attachment #8519755 -
Flags: review?(alive)
Updated•10 years ago
|
Attachment #8519755 -
Flags: review?(alive) → review+
Comment 12•10 years ago
|
||
Comment on attachment 8519755 [details] [review]
Patch v2.0
r+ but I want to make sure the resize is a must-have.
Comment 13•10 years ago
|
||
Comment on attachment 8519728 [details] [review]
Patch
Please request review again for system-resize
Attachment #8519728 -
Flags: review?(alive)
Assignee | ||
Comment 14•10 years ago
|
||
Comment on attachment 8519728 [details] [review]
Patch
Update the patch as we discussed, so set the flag again.
Attachment #8519728 -
Flags: review?(alive)
Assignee | ||
Comment 15•10 years ago
|
||
The v2.1 patch is updated, too.
Updated•10 years ago
|
Attachment #8519728 -
Flags: review?(alive) → review+
Comment 16•10 years ago
|
||
waiting for master landing here before uplifting this on 2.1 branch.
Assignee | ||
Comment 17•10 years ago
|
||
Master patch seems good on Gaia-Try:
https://treeherder.mozilla.org/ui/#/jobs?repo=gaia-try&revision=85750260e054
Assignee | ||
Comment 18•10 years ago
|
||
The 2.0 patch only encountered one permanent failure which occurs on other PR like this:
https://tbpl.mozilla.org/?tree=Gaia-Try&rev=8ef3eefb56d4
My PR result is here:
https://tbpl.mozilla.org/?tree=Gaia-Try&rev=bc326dde5399
So I'll submit approval request.
Assignee | ||
Comment 19•10 years ago
|
||
Comment on attachment 8519755 [details] [review]
Patch v2.0
[Approval Request Comment]
[Bug caused by] (feature/regressing bug #): Orientation API design issue + Gaia didn't capture this case since 2.0
[User impact] if declined: Bug still open
[Testing completed]: Gaia-Try with intermittent and other irrelevant failures. See above comment.
[Risk to taking this patch] (and alternatives if risky): No obvious risk.
[String changes made]: No
Attachment #8519755 -
Flags: approval-gaia-v2.0?(fabrice)
Assignee | ||
Comment 20•10 years ago
|
||
Updated master patch is good on Gaia-Try with several re-runs:
https://treeherder.mozilla.org/ui/#/jobs?repo=gaia-try&revision=412c16cfed60
So I would land it.
Assignee | ||
Comment 21•10 years ago
|
||
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•10 years ago
|
Updated•10 years ago
|
Attachment #8519755 -
Flags: approval-gaia-v2.0?(fabrice) → approval-gaia-v2.0?(release-mgmt)
Updated•10 years ago
|
Attachment #8519706 -
Flags: approval-gaia-v2.1?(fabrice) → approval-gaia-v2.1+
Assignee | ||
Comment 22•10 years ago
|
||
Updated v2.1 patch status: intermittent Gij and irrelevant Gip failures ("Window.getComputedStyle is not an object" in a11y Gip test) only. Would land it.
Assignee | ||
Comment 23•10 years ago
|
||
Assignee | ||
Updated•10 years ago
|
Comment 24•10 years ago
|
||
Comment on attachment 8519755 [details] [review]
Patch v2.0
Requesting QA verification once this lands.
Attachment #8519755 -
Flags: approval-gaia-v2.0?(release-mgmt) → approval-gaia-v2.0+
Comment 25•10 years ago
|
||
Target Milestone: --- → 2.1 S9 (21Nov)
Comment 26•10 years ago
|
||
This issue is verified fixed on Flame 2.0, 2.1 and 2.2.
Result: The lockscreen does not rotate.
Device: Flame 2.0 (319mb, KK, Shallow Flash)
BuildID: 20141114040205
Gaia: 1e300eac2e56d98ad51d414766d031db7d33221f
Gecko: bbb68df450c2
Version: 36.0a1 (2.2)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
Device: Flame 2.1 (319mb, KK, Shallow Flash)
BuildID: 20141114001204
Gaia: af6533781356acc62b0f40c9e040aa5b47d3b709
Gecko: 551326425826
Version: 34.0 (2.1)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Device: Flame 2.2 (319mb, KK, Full Flash)
BuildID: 20141114040205
Gaia: 1e300eac2e56d98ad51d414766d031db7d33221f
Gecko: bbb68df450c2
Version: 36.0a1 (2.2)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
===============================================================
Alison, I verified this issue on 2.2 with full flash because shallow flash has an issue as mentioned in bug 1094527. Is it okay to go ahead and mark this bug as verified for all branches, including 2.2?
Thanks!
Flags: needinfo?(ashiue)
Updated•10 years ago
|
status-b2g-v2.0M:
--- → fixed
Reporter | ||
Comment 27•10 years ago
|
||
(In reply to Yeojin Chung [:YeojinC] from comment #26)
> This issue is verified fixed on Flame 2.0, 2.1 and 2.2.
>
> Result: The lockscreen does not rotate.
>
> Device: Flame 2.0 (319mb, KK, Shallow Flash)
> BuildID: 20141114040205
> Gaia: 1e300eac2e56d98ad51d414766d031db7d33221f
> Gecko: bbb68df450c2
> Version: 36.0a1 (2.2)
> Firmware Version: v188-1
> User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
>
> Device: Flame 2.1 (319mb, KK, Shallow Flash)
> BuildID: 20141114001204
> Gaia: af6533781356acc62b0f40c9e040aa5b47d3b709
> Gecko: 551326425826
> Version: 34.0 (2.1)
> Firmware: V188-1
> User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
>
> Device: Flame 2.2 (319mb, KK, Full Flash)
> BuildID: 20141114040205
> Gaia: 1e300eac2e56d98ad51d414766d031db7d33221f
> Gecko: bbb68df450c2
> Version: 36.0a1 (2.2)
> Firmware Version: v188-1
> User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
> ===============================================================
>
> Alison, I verified this issue on 2.2 with full flash because shallow flash
> has an issue as mentioned in bug 1094527. Is it okay to go ahead and mark
> this bug as verified for all branches, including 2.2?
>
> Thanks!
Yes, please mark this bug as verified. Thanks!
Flags: needinfo?(ashiue)
Updated•10 years ago
|
Status: RESOLVED → VERIFIED
QA Whiteboard: [COM=NFC][QAnalyst-Triage+] → [COM=NFC][QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Updated•10 years ago
|
QA Whiteboard: [COM=NFC][QAnalyst-Triage?] → [COM=NFC][QAnalyst-Triage+]
Flags: needinfo?(ktucker)
You need to log in
before you can comment on or make changes to this bug.
Description
•