Closed Bug 911611 Opened 12 years ago Closed 10 years ago

[Bluetooth] Blank popup appear in pair request process.

Categories

(Firefox OS Graveyard :: Bluetooth, defect)

ARM
Gonk (Firefox OS)
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: leo.bugzilla.gecko, Unassigned)

References

Details

Attachments

(1 file)

Attached video pair_bug.avi
Dear Mozilla Team, I found UI bug in pair request process. Reproduce action is below, 1. Select Device B In bluetooth list of Device A 2. Pair request popup appear in both side 3. Click cancel button in pair popup of Device B 4. After few seconds, Select Device A again in bluetooth list of Device B 5. Click cancel button again in pair popup of Device B 6. After few seconds, Select Device A again in bluetooth list of Device B 7. Blank popup appear in Device A For your understand, I upload the reproduced video. Please check this. Thanks.
Ben will take a first look.
Assignee: nobody → btian
After discussion with gaia team Arthur, we found gecko sends system message to gaia again before previous attention screen is closed, so gaia opens the attention screen twice and results in blank popup. Arthur will add some check in gaia for this.
Assignee: btian → arthur.chen
See Also: → 907441
In bug 908556 we are trying to avoid multiple pairing requests during an ongoing pairing process. I think the solution there fixes this problem.
Hey Arthur, Since bug 908556 has landed, can we close this one?
Flags: needinfo?(arthur.chen)
I found this seems a different case as the connection was triggered from other devices.
Flags: needinfo?(arthur.chen)
Assignee: crh0716 → nobody
qawanted to confirm whether this bug occurs on Aries/Flame with the latest m-c.
Keywords: qawanted
This bug is not reproducible on latest Flame and Aries. Tested pairing between flame and aries. Tried to do the same thing as shown in the video, and I get an error on the sending device if I want to pair to a device that's currently showing a pair request, therefore preventing me from running into the bug. Device: Aries 2.6 Master BuildID: 20151120133504 Gaia: 94a821b49f4dca3f9321cd80e13c44c4a6696952 Gecko: ec628289d8b4ed310463a0729c3e60a7798dfcac Gonk: a19052e4389c3ae2d8fc3e7a74a475401baacc56 Version: 45.0a1 (2.6) Firmware Version: D5803_23.1.A.1.28_NCB.ftf User Agent: Mozilla/5.0 (Mobile; rv:45.0) Gecko/45.0 Firefox/45.0 Device: Flame 2.6 Master BuildID: 20151120030231 Gaia: 94a821b49f4dca3f9321cd80e13c44c4a6696952 Gecko: 3835b568092ae3b71adc931d24928670ad7141a7 Gonk: 205ac4204bbbb2098a8046444acba551ba5dc75a Version: 45.0a1 (2.6) Firmware Version: v18Dv4 User Agent: Mozilla/5.0 (Mobile; rv:45.0) Gecko/45.0 Firefox/45.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmercado)
Keywords: qawanted
Ben I think this could be closed WFM per comment 7.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmercado) → needinfo?(btian)
(In reply to Jayme Mercado [:JMercado] from comment #8) > Ben I think this could be closed WFM per comment 7. Agree. Resolve as WFM per comment 7.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(btian)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: