I've managed to get my device into a state where the lockscreen refuses to unlock. Unlocking throws a JS exception: "W/GeckoConsole( 186): [JavaScript Error: "TypeError: this.element is null" {file: "app://system.gaiamobile.org/js/app_window.js" line: 231}]"

QA wanted, can you look into this issue and try to get a solid STR?

Hi Kyle, Could you provide some more information for us to digest when testing for this bug? 1. What device and build where you on? (Latest Master, 2.1, etc.) 2. Any other info such as what you did leading up to this issue? 3. Does it fix itself after a reset? Thank you!

I'm running master on a Nexus 5. I've seen this twice. The most recent time this happened I was killing apps in the task manager and somehow got the task manager into a confused state where the home button would not work. Once I did that, turning the screen off and back on again got it to the lockscreen that would not unlock. Unfortunately I haven't been able to figure out how to reproduce this despite trying many times. Rebooting the device fixes the issue.

Awesome! Thanks as that helps us a ton!

We are seeing the slider actually get stuck and not able to move at all. We are also seeing problems with the time display on the lockscreen moving down underneath the slider which is when it stops working. Not sure these bugs are the same but I wanted to check in with what I am seeing. 1. Is your slider able to be slid to the right and then you get the JS Error? 2. Did you notice any problems with the time display on the lock screen? I just don't want post steps for a bug that may not be yours.

(In reply to Cody Roesch [:croesch] from comment #6) > We are seeing the slider actually get stuck and not able to move at all. We > are also seeing problems with the time display on the lockscreen moving down > underneath the slider which is when it stops working. Not sure these bugs > are the same but I wanted to check in with what I am seeing. > > 1. Is your slider able to be slid to the right and then you get the JS Error? I was able to slide to the right before I got the error. > 2. Did you notice any problems with the time display on the lock screen? No, but I wasn't paying attention for it. > I just don't want post steps for a bug that may not be yours. If you see the same error in logcat go ahead and post the steps here. I can always open another bug if necessary. And if they have the same error message they might have the same root cause even if they have different symptoms.

Unfortunately I wasn't able to repro this bug. I found another serious blocker during this testing dealing with the slider but not this bug. I'm keeping QAWanted for another tester to try. This bug does NOT repro on Flame kk build: Flame 2.2 KK, Flame 2.1 KK, Flame 2.0 KK Actual Result: Unable to get a JS Error when trying to unlock the phone and it fails to unlock. Repro Rate: 0/25 Environmental Variables: Device: Flame Master KK BuildID: 20140930061521 Gaia: 77ef35f5429bc3dfe9ca192b9aacc3c0bf8857de Gecko: 2ae57957e4bb Version: 35.0a1 (Master) Firmware Version: L1TC10011800 User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0 ----------------------------------------------------------------- Environmental Variables: Device: Flame 2.1 KK BuildID: 20140930072157 Gaia: e9cbcbb12c1ec76e0ccdc88f1962f2afa3dd17b2 Gecko: 6b224957f0bd Version: 34.0a2 Firmware Version: L1TC10011800 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 ----------------------------------------------------------------- Environmental Variables: Device: Flame 2.0 KK BuildID: 20140930095020 Gaia: 5c2303ec4e367da060aa1b807d541a6549b3d72a Gecko: f19f4e07010a Version: 32.0 (2.0) Firmware Version: L1TC10011800 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

We'll keep trying

Yeah, it might require extended periods of usage or something. If I see it again I'll report what I can learn.

Could also be specific to Nexus 5 possibly. Do you have a Flame device to try and get it again? If not we'll try and get a nexus flashed and try on that but it's not one of our normal test devices.

Yeah, I can test on a Flame. It's certainly not easy to reproduce or I would have managed it by now, so I wouldn't waste time getting a nexus 5.

Hey Kyle - any luck on this bug? Maybe we should move it to back-log if we can't get steps?

I haven't seen it lately. I'll reopen if it happens again.