Closed Bug 1135006 Opened 10 years ago Closed 10 years ago

March appears twice in date/time picker (no February)

Categories

(Firefox OS Graveyard :: Gaia::System, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(b2g-v2.1 affected, b2g-v2.2 affected, b2g-master affected)

RESOLVED WORKSFORME
Tracking Status
b2g-v2.1 --- affected
b2g-v2.2 --- affected
b2g-master --- affected

People

(Reporter: davehunt, Unassigned)

Details

Attachments

(2 files)

Attached image 2015-02-20-11-10-42.png
Steps to reproduce: 1. Flash Flame with latest build (reproduced on mozilla-central, 2.2, 2.1). 2. Complete FTU steps (with defaults) 3. Open Settings > Date & Time 4. Disable 'Set Automatically' 5. Tap Date Expected: Months dial should contain all months of the year once. Actual: February is missing and March appears twice. Reproduced on mozilla-central: Gaia-Rev e4f7c67378e33e83f88d38ddb4a6c2cabf1423c3 Gecko-Rev https://hg.mozilla.org/mozilla-central/rev/1b4c5daa7b7a Build-ID 20150220010206 Version 38.0a1 Device-Name flame FW-Release 4.4.2 FW-Incremental eng.cltbld.20150220.043045 FW-Date Fri Feb 20 04:30:55 EST 2015 Bootloader L1TC100118D0 Also reproduced on v2.2: Gaia-Rev ce79d35b92261e7cbfeaefebf87859ebeb0979b4 Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/b864abe1c6b3 Build-ID 20150220002501 Version 37.0a2 Device-Name flame FW-Release 4.4.2 FW-Incremental eng.cltbld.20150220.035502 FW-Date Fri Feb 20 03:55:13 EST 2015 Bootloader L1TC100118D0 Potentially related to bug 858468 and bug 842139.
Is this reproducible?
Doesnt reproduce for me (moz-central/master) using the Launch FTU from Settings > Developer. But actual first time use could differ. QA Note: you need to not have a valid SIM inserted and have no connected wifi to see the Date & Time screen, otherwise it gets skipped.
Keywords: qawanted
Also didn't reproduce using moz-central/master and the STR (complete FTU with defaults, go to Settings -> Date & Time). Sorry I misread STR, you can probably ignore comment #2
I was unable to reproduce this issue on the reported build. Besides following the STR, I also tried without SIM cards, Wi-Fi on, data connection on, and in French, but unsuccessful reproducing the issue. Result: February is displayed properly. Repro rate: 0/10 Environmental Variables: Device: Flame 3.0 (KK, 319mb, full & shallow flash) Build ID: 20150220010206 Gaia: e4f7c67378e33e83f88d38ddb4a6c2cabf1423c3 Gecko: 1b4c5daa7b7a Gonk: e7c90613521145db090dd24147afd5ceb5703190 Version: 38.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:38.0) Gecko/38.0 Firefox/38.0 ============================= leaving qawanted for others to try.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
I cannot reproduce this issue on the two reported builds at comment 0 with full flash 319MB mem on Flame. Followed STR with no repro. Played around with timezones and Set Automatically toggle with no repro. Removing qawanted tag due to unsuccessful repro attempts by 3 different individuals.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: qawanted
Looks like we have to resolve this worksforme, again. I wonder if this is a graphics glitch? Still, unless we can get some reproducible STR there's not much we can do here. OP: Please re-open if it happens again and you can get a logcat.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
I cannot reproduce this when I remove the SIM and sdcard from the device. As soon as I replace the SIM and reflash the issue is reproducible. As far as I can tell my SIM card is no longer active, but the original report came from a relative that is dogfooding Firefox OS with an active (UK) SIM. I'm flashing using https://github.com/Mozilla-TWQA/B2G-flash-tool and the command line: $ ./flash_tbpl.py -v b2g-inbound -d flame-kk -f --eng
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Attached file logcat.txt
The person that originally reported this says they can no longer reproduce it.
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: