Closed Bug 1171022 Opened 10 years ago Closed 10 years ago

Sliders in Settings app are non working

Categories

(Firefox OS Graveyard :: General, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:2.5+, b2g-v2.2 unaffected, b2g-master verified)

VERIFIED FIXED
2.2 S14 (12june)
blocking-b2g 2.5+
Tracking Status
b2g-v2.2 --- unaffected
b2g-master --- verified

People

(Reporter: gerard-majax, Assigned: alessarik)

References

Details

(Keywords: dogfood, regression)

STR: 0. Flash uptodate Gecko/Gaia 1. Open Settings, Display 2. Try to adjust luminosity Expected: I can pickup the slider and move it Actual: I cannot. None of the slider in the app works (Display, Sound, etc.)
Gecko 8e2e7660aed97a051dfbe03c0acaee26a8e45eba Gaia 5ef5d283279c339b54a45c206e12b01ccb1c5b77 Android 5.1
No repro on 2.2 [1]. QAWanted for a branch check. [Blocking Requested - why for this release]: Regression which may impact the first experience. [1] Build ID 20150603002503 Gaia Revision a9aeb08263f1a727136e8ae78425e52431c82770 Gaia Date 2015-06-02 13:04:40 Gecko Revision https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/5b3f1796ddf6 Gecko Version 37.0 Device Name flame Firmware(Release) 4.4.2 Firmware(Incremental) eng.cltbld.20150603.035922 Firmware Date Wed Jun 3 03:59:33 EDT 2015 Bootloader L1TC000118D0
blocking-b2g: --- → spark?
blocking-b2g: spark? → spark+
QA Contact: jmercado
This issue occurs on 3.0 flame builds but does not occur on 2.2 flame builds so it is a regression. Issue DOES occur Environmental Variables: Device: Flame 3.0 BuildID: 20150602041216 Gaia: 6d477a7884273886605049b20f60af5c1583a150 Gecko: 9eae3880b132 Version: 41.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0 Issue does NOT occur Environmental Variables: Device: Flame 2.2 BuildID: 20150602103614 Gaia: a9aeb08263f1a727136e8ae78425e52431c82770 Gecko: 5b3f1796ddf6 Version: 37.0 (2.2) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
Flags: needinfo?(ktucker)
Keywords: qaurgent, qawanted
Flags: needinfo?(ktucker)
This is possibly caused by the changes for Bug 1133417. Please see the pushlog as I am not sure on that. All changes came from the FX inbound however, we do not get builds from the FX inbound so I cannot narrow this window down further at this time. Central Regression Window: Last Working Environmental Variables: Device: Flame 3.0 BuildID: 20150602025913 Gaia: 6d477a7884273886605049b20f60af5c1583a150 Gecko: 2184bfef3eea Version: 41.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0 First Broken Environmental Variables: Device: Flame 3.0 BuildID: 20150602040015 Gaia: 6d477a7884273886605049b20f60af5c1583a150 Gecko: f0112e6128c0 Version: 41.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0 Last Working gaia / First Broken gecko - Issue DOES occur Gaia: 6d477a7884273886605049b20f60af5c1583a150 Gecko: f0112e6128c0 First Broken gaia / Last Working gecko - Issue does NOT occur Gaia: 6d477a7884273886605049b20f60af5c1583a150 Gecko: 2184bfef3eea Gaia Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=2184bfef3eea&tochange=f0112e6128c0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Maksim, can you take a look at this please? We are completely guessing here but could the work done for bug 1133417 be the cause here?
Blocks: 1133417
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker) → needinfo?(alessarik)
Might be fixed by backout of 1166347. Can we test again with a build that has the backout?
No way bug 1133417 caused this, it only affected some tests.
Flags: needinfo?(alessarik)
No longer blocks: 1133417
Bug 1166347 was backed out 10 hours ago. QA wanted to check if the issue is now fixed.
Keywords: qawanted
(In reply to KTucker [:KTucker] from comment #5) > Maksim, can you take a look at this please? We are completely guessing here > but could the work done for bug 1133417 be the cause here? Bug 1133417 is not a reason. Reason is bug 1166347. PE should not been enabled on Android and B2G for some time. Feel free to recheck after backout bug 1166347.
This issue does not reproduce on today's Nightly Flame 3.0 build. Actual Results: The brightness slider works as expected and can be slid back and forth. Environmental Variables: Device: Flame 3.0 KK (Full Flash) (319 MB) Build ID: 20150604010200 Gaia: 9e10483c5808f94f4a0a9f6afe30aae2c5b42b4c Gecko: 98820360ab66 Gonk: 040bb1e9ac8a5b6dd756fdd696aa37a8868b5c67 Version: 41.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: qawanted
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Based on comment 6 and comment 10.
Resolution: WORKSFORME → DUPLICATE
Not a dup. Fixed by the backout, but need to watch out for the updated patch on bug 1166347 breaking this again...
Blocks: 1166347
Resolution: DUPLICATE → FIXED
blocking-b2g: spark+ → 2.5+
Assignee: nobody → alessarik
Target Milestone: --- → 2.2 S14 (12june)
This issue is verified fixed on Aries and Flame. Display brightness slider can be slided and the brightness setting can be changed once I let go of finger on slider. Device: Aries BuildID: 20150803200840 Gaia: dbacf8364f4505d021b7d8fb9cabea325004dbcc Gecko: abc56d57f6e1 Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd Version: 42.0a1 (2.5 Master) Firmware Version: D5803_23.1.A.1.28_NCB.ftf User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0 Device: Flame (319MB, full flashed, KK) BuildID: 20150803030210 Gaia: 2ca27bbdd84526c6a3b198d9cf10f2caff1dadde Gecko: 32712cd01159 Gonk: 41d3e221039d1c4486fc13ff26793a7a39226423 Version: 42.0a1 (2.5 Master) Firmware Version: v18D User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0
Status: RESOLVED → VERIFIED
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
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.