Closed
Bug 1058449
Opened 10 years ago
Closed 10 years ago
Tapping on the settings button in contacts doesn't have any effect
Categories
(Firefox OS Graveyard :: Gaia::Contacts, defect)
Firefox OS Graveyard
Gaia::Contacts
Tracking
(blocking-b2g:2.1+, b2g-v1.4 unaffected, b2g-v2.0 unaffected, b2g-v2.1 verified, b2g-v2.2 verified)
Tracking | Status | |
---|---|---|
b2g-v1.4 | --- | unaffected |
b2g-v2.0 | --- | unaffected |
b2g-v2.1 | --- | verified |
b2g-v2.2 | --- | verified |
People
(Reporter: pensacola_m2000, Assigned: jmcf)
References
Details
(Keywords: regression)
Attachments
(2 files)
256.21 KB,
text/plain
|
Details | |
191 bytes,
text/html
|
arcturus
:
review+
fabrice
:
approval-gaia-v2.1+
|
Details |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 (Beta/Release) Build ID: 20131028113308 Steps to reproduce: 1. Go to contacts and press to Settings Actual results: Contacts settings is not working, nothing happens after pressing it. Expected results: Contacts settings should be displayed with all the options. Note: I used for testing OS version 2.1.0.0 prerelease, platform version 34.0a1, build identifier: 20140825040204 nightly build.
Comment 1•10 years ago
|
||
Marcela: I am not seeing this using: Gaia 4d1d0ea5a82cddeeab497774cfa1703639e3c7d9 SourceStamp dc352a7bf234 BuildID 20140826040204 Version 34.0a1 Base image: v123 Can you please recheck with a later build?
Flags: needinfo?(pensacola_m2000)
Comment 2•10 years ago
|
||
I saw that problem this morning with the same build as you Marcia. I saw it during the Right to Left bug bash and I thought it was related to that. But now I can't repro neither in RTL or in LTR. Adding steps-wanted then.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(pensacola_m2000)
Keywords: steps-wanted
Comment 3•10 years ago
|
||
Changing the name to make it more precise.
Summary: [Flame] Contacts settings is not working → Tapping on the settings button in contacts doesn't have any effect
Comment 4•10 years ago
|
||
Hi Marcela, I was trying to work on this issue but even with the nightly build you provided, I'm unable to repro this bug. Can you provide a video of this issue? I tried this on a Flame AND OpenC device and did the following 1. Flash the Flame device to build 2. Launch Contacts 3. Tap settings (Nothing happens) Is there anything I'm missing here? Thank you!
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pensacola_m2000)
QA Contact: croesch
Updated•10 years ago
|
Flags: needinfo?(jmitchell)
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Reporter | ||
Comment 5•10 years ago
|
||
I updated the device build with: Gaia 6e804a42ab90f4251c7fe8c68731dc1c6abd8006 SourceStamp 0753f7b93ab7 BuildID 20140827040203 Version 34.0a1 It seems that the issue is no longer reproducing on this version.
Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(pensacola_m2000)
Updated•10 years ago
|
Comment 7•10 years ago
|
||
I am going to reopen this for further investigation as the issue is presenting itself again on one of my Flame devices. Gaia 3a838afca295c9db32e1a3ec76d49fb7fe7fd2d2 SourceStamp 3be45b58fc47 BuildID 20140828040204 Version 34.0a1 base image: v123 I not able to reproduce it 100%, but it definitely is happening intermittently.
Status: VERIFIED → REOPENED
Resolution: WORKSFORME → ---
Comment 8•10 years ago
|
||
restoring steps-wanted tag to loop in QA-wanted team for support.
Keywords: steps-wanted
Comment 9•10 years ago
|
||
Ok I finally got this issue to happen a few times. It's definitely intermittent though. I can't get it to happen every time I reset and try to narrow down the steps. Once it happens though, you can't recover your functionality without a reboot/reset. It happens most often when: 1. Opening a few apps along with Contacts. (camera,dialer,Sms) 2. Edge Gesturing between the apps 3. Then closing apps by bringing up card view and swiping up. 4. Reopen contacts and the Settings button has no function. These steps are the closest I can get right now but I'll try to narrow them down even more. I've encountered the issue 3 times in an hour. Just wanted to post something to possibly lead to ideas from other people. Environmental Variables: Device: Flame Master BuildID: 20140829061359 Gaia: 007f3c50cf69f044628a23c2376c6d88aa45f617 Gecko: d728b2f31c56 Version: 34.0a1 (Master) Firmware Version: v123
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Comment 10•10 years ago
|
||
Video Link: http://youtu.be/3Qjiq6NF6OI Ok, I narrowed this down and can reliably repro this bug. 1. Open Contacts app. 2. Open Camera app and take a photo. 3. Close out both the apps in card view. 4. Reopen both contacts and camera apps and close them again. 5. Open Contacts and settings button is broken. This bug repro's on: Flame 2.1 Actual Results: Settings button in Contacts stops having functionality. Repro Rate: 5/5 Environmental Variables: Device: Flame Master BuildID: 20140829120602 Gaia: 007f3c50cf69f044628a23c2376c6d88aa45f617 Gecko: 11e4f1678eab Version: 34.0a1 (Master) Firmware Version: v123 ------------------------------------------------ ------------------------------------------------ This bug does NOT repro on: Flame 2.0, Flame 1.4, OpenC 2.1 Actual Result: Settings button for Contacts stays functioning correctly. Repro Rate: 0/4 attempts Environmental Variables: Device: Flame 2.0 BuildID: 20140827201151 Gaia: ee5cf3aff7e66ec5e899bdffa27ef51bfa40f0f0 Gecko: 218771782328 Version: 32.0 (2.0) Firmware Version: v123 ----------------------------------------------- Environmental Variables: Device: Flame 1.4 BuildID: 20140827090228 Gaia: 05653cb12d324649687dad3eeb2ea373a2ad84d4 Gecko: baf01c5965ef Version: 30.0 (1.4) Firmware Version: v123 ----------------------------------------------- Environmental Variables: Device: Open_C Master BuildID: 20140829120602 Gaia: 007f3c50cf69f044628a23c2376c6d88aa45f617 Gecko: 11e4f1678eab Version: 34.0a1 (Master) Firmware Version: P821A10V1.0.0B06_LOG_DL
status-b2g-v1.4:
--- → unaffected
status-b2g-v2.0:
--- → unaffected
Flags: needinfo?(jmitchell)
Keywords: steps-wanted → regression
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?]
Comment 11•10 years ago
|
||
Traige analysis - I'm on the fence about nomming this issue. It IS a regression but the current STR are really off the main-use path. That being said - it has obviously been encountered by several people randomly. I'm learning toward no-nom but just barely.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
Reporter | ||
Comment 12•10 years ago
|
||
I was able to reproduce the issue using Aurora 2.1: Gaia a47ecb6368c015dd72148acde26413fd90ba3136 SourceStamp 757931d0149e BuildID 20140904000203 Version 34.0a2 Logs attached. Steps to reproduce: Perform some actions like, make a call, import contacts, browse some websites, and then open Contacts app. I was not able to open contacts settings anymore.
Reporter | ||
Comment 13•10 years ago
|
||
Comment 14•10 years ago
|
||
(In reply to Joshua Mitchell [:Joshua_M] from comment #11) > Traige analysis - I'm on the fence about nomming this issue. It IS a > regression but the current STR are really off the main-use path. That being > said - it has obviously been encountered by several people randomly. I'm > learning toward no-nom but just barely. Agree it's a tough one to evaluate. I think my main concern here is that this seems like a realistic dogfooding bug that users could hit during normal usage. It's also got an unpleasant recovery path (reboot the phone). My gut is leaning on the side of saying of putting this on nomination queue for being a bad dogfooding bug, but let's see what Bhavana thinks first before I do that.
Flags: needinfo?(bbajaj)
Comment 15•10 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #14) > (In reply to Joshua Mitchell [:Joshua_M] from comment #11) > > Traige analysis - I'm on the fence about nomming this issue. It IS a > > regression but the current STR are really off the main-use path. That being > > said - it has obviously been encountered by several people randomly. I'm > > learning toward no-nom but just barely. > > Agree it's a tough one to evaluate. I think my main concern here is that > this seems like a realistic dogfooding bug that users could hit during > normal usage. It's also got an unpleasant recovery path (reboot the phone). > My gut is leaning on the side of saying of putting this on nomination queue > for being a bad dogfooding bug, but let's see what Bhavana thinks first > before I do that. I went through the use case myself and watched the video, although the STR might be complex its easy to hit during dogfooding the phone or day-day use, I recommend nominating this bug.
Flags: needinfo?(bbajaj)
Comment 16•10 years ago
|
||
[Blocking Requested - why for this release]: Based on the above comments, we think this is a bad dogfooding regression. The STR might be complex, but the reality is that someone will hit this during basic usage of the phone. The recovery path is ugly too - it requires a phone reboot. On that regard, I think we need to block on this.
Comment 17•10 years ago
|
||
triage: let's plus it now per comment 16. Francisco will investigate on this.
blocking-b2g: 2.1? → 2.1+
Updated•10 years ago
|
QA Contact: croesch → jmercado
Comment 18•10 years ago
|
||
Bug 1040017 seems to be the cause for this bug Mozilla-inbound Regression Window Last working Environmental Variables: Device: Flame 2.1 BuildID: 20140821223018 Gaia: afcdd36f13e75adcdebe57d842a277fd587faf28 Gecko: c365e93b8e42 Version: 34.0a1 (2.1) Firmware Version: v123 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 First Broken Environmental Variables: Device: Flame 2.1 BuildID: 20140821224417 Gaia: afcdd36f13e75adcdebe57d842a277fd587faf28 Gecko: a9c2b0b7adac Version: 34.0a1 (2.1) Firmware Version: v123 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Last working gaia / First broken gecko - Issue DOES occur Gaia: afcdd36f13e75adcdebe57d842a277fd587faf28 Gecko: a9c2b0b7adac First broken gaia / Last working gecko - Issue does NOT occur Gaia: afcdd36f13e75adcdebe57d842a277fd587faf28 Gecko: c365e93b8e42 Gecko Pushlog: http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=c365e93b8e42&tochange=a9c2b0b7adac
Comment 19•10 years ago
|
||
Broken by Bug 1040017 ? Can you take a look Patrick?
Blocks: 1040017
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell) → needinfo?(kk1fff)
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → jmcf
Assignee | ||
Updated•10 years ago
|
Target Milestone: --- → 2.1 S5 (26sep)
Assignee | ||
Comment 20•10 years ago
|
||
The problem can be 100% reproduced on a flame device that has not any SDCARD
Updated•10 years ago
|
Attachment #8489386 -
Flags: review?(francisco) → review+
Comment 23•10 years ago
|
||
Comment on attachment 8489386 [details]
24053.html
[Approval Request Comment]
[Bug caused by] (feature/regressing bug #):
Regression caused by last feature work
[User impact] if declined:
Huge, for users without sdcard on devices with internal memory, contacts settings will stop working and the application will be unusable.
[Testing completed]:
Smoke test passed, and added more unit tests to check the especific error.
[Risk to taking this patch] (and alternatives if risky):
Risk low, the change is simple, we forget about all kinds of storage (internal memory) and always ask just for sdcard. It's about 5 lines of code and we ad more test cases to cover everything.
[String changes made]:
Attachment #8489386 -
Flags: approval-gaia-v2.1?(fabrice)
Comment 24•10 years ago
|
||
I'm confused here. Why are we trying to fix this with a Gaia patch? The regression range points this to being a gecko regression in Nuwa, which means we should patching gecko here, not Gaia. Unless we think a Gaia workaround is a safer fix to include here.
Comment 25•10 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #24) > I'm confused here. Why are we trying to fix this with a Gaia patch? The > regression range points this to being a gecko regression in Nuwa, which > means we should patching gecko here, not Gaia. Unless we think a Gaia > workaround is a safer fix to include here. The regression points to the nuwa change, but the bug is actually in gaia - it's broken by a gecko behavior change that it was not dealing with properly even though it's perfectly expectable. So I think the fix here is right.
Updated•10 years ago
|
Attachment #8489386 -
Flags: approval-gaia-v2.1?(fabrice) → approval-gaia-v2.1+
Assignee | ||
Comment 26•10 years ago
|
||
landed in master: https://github.com/mozilla-b2g/gaia/commit/3604b50af0161694381f5ebe1f6fe053fda022fb
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Flags: needinfo?(kk1fff)
Resolution: --- → FIXED
Comment 27•10 years ago
|
||
v2.1: https://github.com/mozilla-b2g/gaia/commit/194ad18eb64b96371d7d3e6dc09f6651c2a3b57e
status-b2g-v2.2:
--- → fixed
Comment 28•10 years ago
|
||
Verified fixed on Flame 2.2 (319mb/full flash) and Flame 2.1 (319mb/full flash) Issue does NOT occur using any of the above STRs. Actual result: Contacts settings are displayed with all the options. Device: Flame 2.2 BuildID: 20141011040204 Gaia: 95f580a1522ffd0f09302372b78200dab9b6f322 Gecko: 3f6a51950eb5 Gonk: 52c909e821d107d414f851e267dedcd7aae2cebf Version: 35.0a1 (2.2) Firmware: V180 User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0 Device: Flame 2.1 BuildID: 20141011000201 Gaia: f5d4ff60ffed8961f7d0380ada9d0facfdfd56b1 Gecko: d813d79d3eae Gonk: 52c909e821d107d414f851e267dedcd7aae2cebf Version: 34.0a2 (2.1) Firmware: V180 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Status: RESOLVED → VERIFIED
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: verifyme
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
You need to log in
before you can comment on or make changes to this bug.
Description
•