Closed
Bug 1082669
Opened 10 years ago
Closed 10 years ago
[Bluetooth] White screen displayed when pairing devices
Categories
(Firefox OS Graveyard :: Gaia::Bluetooth, defect)
Tracking
(blocking-b2g:2.1+, b2g-v2.0 unaffected, b2g-v2.1 affected, b2g-v2.2 unaffected)
RESOLVED
DUPLICATE
of bug 1081528
blocking-b2g | 2.1+ |
Tracking | Status | |
---|---|---|
b2g-v2.0 | --- | unaffected |
b2g-v2.1 | --- | affected |
b2g-v2.2 | --- | unaffected |
People
(Reporter: smiko, Unassigned)
References
()
Details
(Keywords: regression, smoketest, Whiteboard: [2.1-Daily-Testing])
Attachments
(1 file)
79.70 KB,
text/plain
|
Details |
Description: A white screen is displayed on both devices when accepting a bluetooth pairing request. Setup: Two bluetooth enabled devices. Repro Steps: 1: Update a Flame to 20141014001201 2: Open Settings > bluetooth > and search for other devices. 3: Locate the other device and click on it to send the pairing request. 4: Accept the pairing request on both devices Actual: A white screen is displayed. Expected: The users are returned to settings. Flame 2.1(319mb) Device: Flame 2.1 BuildID: 20141014001201 Gaia: 7e2e65a9668123b54c8cce5dacfdba6f4bd4672b Gecko: 2325da834971 Gonk: 52c909e821d107d414f851e267dedcd7aae2cebf Version: 34.0 (2.1) Firmware: V180 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Notes: 1: When this issue occurs, the devices do pair and can send/receive files. Repro frequency: 100% See attached logcat Video clip: http://youtu.be/YlJZuER7qSs
Reporter | ||
Comment 1•10 years ago
|
||
This issue does NOT occur on Flame 2.2 (319mb/full flash) Actual result: The user is returned to Settings. Device: Flame 2.2 BuildID: 20141014040203 Gaia: 4f86c631e0465c0e56ccebeb1324fd28be9ea32f Gecko: 54217864bae9 Gonk: 52c909e821d107d414f851e267dedcd7aae2cebf Version: 36.0a1 (2.2) Firmware: V180 User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0 Device: Flame 2.2 BuildID: 20141013040202 Gaia: 3b81896f04a02697e615fa5390086bd5ecfed84f Gecko: f547cf19d104 Gonk: 52c909e821d107d414f851e267dedcd7aae2cebf Version: 35.0a1 (2.2) Firmware: V180 User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.1:
--- → affected
status-b2g-v2.2:
--- → unaffected
Flags: needinfo?(pbylenga)
Keywords: smoketest
Whiteboard: [2.1-Daily-Testing]
Comment 2•10 years ago
|
||
[Blocking Requested - why for this release]: Functional Regression of a Core Feature. Requesting branch checks to verify Master reproduction and for 2.0 check.
blocking-b2g: --- → 2.1?
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Updated•10 years ago
|
QA Contact: pcheng
Comment 3•10 years ago
|
||
Confirmed that this issue occurs on Flame 2.1, and does NOT occur on Flame 2.2 or on Flame 2.0. The repro rate is 5/5 on 2.1. Tested with engineering builds + shallow flash.
Updated•10 years ago
|
Comment 4•10 years ago
|
||
2.1 Aurora branch regression window: Last Working Environmental Variables: Device: Flame BuildID: 20141010084606 Gaia: d18e130216cd3960cd327179364d9f71e42debda Gecko: 610ee0e6a776 Version: 34.0a2 (2.1) Firmware: V180 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 First Broken Environmental Variables: Device: Flame BuildID: 20141010090103 Gaia: 6cc93702284648c4f697cf89e3cecea6f26187dc Gecko: 6c30565dae54 Version: 34.0a2 (2.1) Firmware: V180 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 First Broken Gaia & Last Working Gecko - issue DOES repro Gaia: 6cc93702284648c4f697cf89e3cecea6f26187dc Gecko: 610ee0e6a776 First Broken Gecko & Last Working Gaia - issue does NOT repro Gaia: d18e130216cd3960cd327179364d9f71e42debda Gecko: 6c30565dae54 Gaia pushlog: https://github.com/mozilla-b2g/gaia/compare/d18e130216cd3960cd327179364d9f71e42debda...6cc93702284648c4f697cf89e3cecea6f26187dc Caused by Bug 1067649.
Comment 5•10 years ago
|
||
Broken by Bug 1067649 ? Can you take a look Sam?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell) → needinfo?(sfoster)
QA Contact: pcheng
Comment 6•10 years ago
|
||
(In reply to Joshua Mitchell [:Joshua_M] from comment #5) > Broken by Bug 1067649 ? Can you take a look Sam? Strongly suspect this is a dupe of bug 1081528, as an attention window is used. The patch on 1081528 (landed today on v2.1) should fix it.
Flags: needinfo?(sfoster)
Comment 7•10 years ago
|
||
QA-Wanted to re-test on a 2.1 build spun after 2014-10-14 11:50:51 PDT
Keywords: qawanted
Comment 8•10 years ago
|
||
I've been able to reproduce using the pvt 2.1 build, and just flashed the latest v2.1 and confirmed this is now fixed. Resolving as a dupe, will still need to be verified in the usual way.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Updated•10 years ago
|
blocking-b2g: 2.1? → 2.1+
You need to log in
before you can comment on or make changes to this bug.
Description
•