Closed
Bug 1197085
Opened 9 years ago
Closed 9 years ago
[Dialer] White screen displayed instead of call log in some situations
Categories
(Firefox OS Graveyard :: Gaia::Dialer, defect)
Tracking
(blocking-b2g:2.5+, b2g-v2.2 unaffected, b2g-master affected)
RESOLVED
DUPLICATE
of bug 1190790
blocking-b2g | 2.5+ |
Tracking | Status | |
---|---|---|
b2g-v2.2 | --- | unaffected |
b2g-master | --- | affected |
People
(Reporter: julienw, Unassigned)
Details
(Keywords: foxfood, regression)
Attachments
(2 files)
STR: 1. Ensure the Dialer is not running. 2. Receive 2 missing calls (so that there are 2 "missing calls" notifications). 3. Dismiss one of the "missing call" notification. 4. Tap on the remaining "missing call" notification. => The dialer is displayed, but there is a white screen instead of the call log information. I found this on the latest foxfood build on Aries. qawanted to do a branch check.
Comment 1•9 years ago
|
||
This issue can be repro on latest build of Flame KK v2.5 and Aries KK v2.5 but cannot repro on latest build of Flame KK v2.2 with the same steps in comment 0. Results: When user dismisses one of the "missed call" notification and tap the other "missed call" notification, the Dialer app is displayed, but there is a white screen instead of the call log information. Attachment: Aries_KK_v2.5.3gp & logcat1535.zip Rate:5/5 (v2.5), 0/5 (v2.2) Device: Aries KK 2.5 (affected) Build ID 20150827170125 Gaia Revision d784c81961d82cbe9e111405468c590a8345856c Gaia Date 2015-08-27 12:29:28 Gecko Revision https://hg.mozilla.org/mozilla-central/rev/ca086f9ef8bca2d6cdfa79bfc4c854f56a59859e Gecko Version 43.0a1 Device Name aries Firmware(Release) 4.4.2 Firmware(Incremental) eng.worker.20150827.162303 Firmware Date Thu Aug 27 16:23:10 UTC 2015 Bootloader s1 Device: Flame KK 2.5 (affected) Build ID 20150827150209 Gaia Revision d784c81961d82cbe9e111405468c590a8345856c Gaia Date 2015-08-27 12:29:28 Gecko Revision https://hg.mozilla.org/mozilla-central/rev/ca086f9ef8bca2d6cdfa79bfc4c854f56a59859e Gecko Version 43.0a1 Device Name flame Firmware(Release) 4.4.2 Firmware(Incremental) eng.cltbld.20150827.190412 Firmware Date Thu Aug 27 19:04:26 EDT 2015 Firmware Version v18D v4 Bootloader L1TC000118D0 Device: Flame KK 2.2 (unaffected) Build ID 20150827032504 Gaia Revision 335cd8e79c20f8d8e93a6efc9b97cc0ec17b5a46 Gaia Date 2015-08-14 19:06:41 Gecko Revision https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/16d864d163de Gecko Version 37.0 Device Name flame Firmware(Release) 4.4.2 Firmware(Incremental) eng.cltbld.20150827.064425 Firmware Date Thu Aug 27 06:44:37 EDT 2015 Firmware Version v18D v4 Bootloader L1TC000118D0
Comment 2•9 years ago
|
||
Updated•9 years ago
|
QA Whiteboard: [MGSEI-Triage+]
status-b2g-v2.2:
--- → unaffected
status-b2g-master:
--- → affected
Keywords: qawanted
Comment 3•9 years ago
|
||
[Blocking Requested - why for this release]: Functional regression
blocking-b2g: --- → 2.5?
Keywords: regression
Reporter | ||
Updated•9 years ago
|
Keywords: regressionwindow-wanted
Comment 5•9 years ago
|
||
This is most likely a duplicate of bug 1190790 I have completed a regression window for a very similar issue (bug 1198361). Cause of this bug: Bug 1188544 - [Dialer][NGA] Remove navigation based on hashchange r=a…
QA Whiteboard: [MGSEI-Triage+] → [MGSEI-Triage+][QAnalyst-Triage?]
Flags: needinfo?(jmercado)
Keywords: regressionwindow-wanted
QA Contact: ddixon
Comment 6•9 years ago
|
||
As Duane said, this seems to be the same issue as bug 1198361 and bug 1190790. Please see this pushlog: http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=c574db1b372e997a8d6389ccae2e207c264d0197&tochange=7b24a94110d066be3b8f9c28e6439605a5e02a29
Status: NEW → RESOLVED
Closed: 9 years ago
QA Whiteboard: [MGSEI-Triage+][QAnalyst-Triage?] → [MGSEI-Triage+][QAnalyst-Triage+]
Flags: needinfo?(jmercado)
Resolution: --- → DUPLICATE
Reporter | ||
Comment 7•9 years ago
|
||
It's similar but not exactly the same. Please don't forget to check this case once the dupe is fixed.
You need to log in
before you can comment on or make changes to this bug.
Description
•