Closed Bug 987391 Opened 6 years ago Closed 6 years ago

weird lockscreen situation where it shouldn't show up, but does and won't unlock

Categories

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

x86
macOS
defect
Not set

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 980549

People

(Reporter: dietrich, Unassigned)

References

Details

Nexus 4, seeing this regularly.

While this doesn't seem like a normal scenario at first glance, I'm concerned it might be a problem during updates, so reporting to get some eyes on it.

STR:

1. flash a build
2. disable lockscreen
3. back up all user data*
4. flash a newer build
5. stop b2g, restore the user data, start b2g

The lockscreen should be disabled at this point. However, not only does it show up, sliding to unlock doesn't work. Have to reboot, and then lockscreen is disabled.


* I'm backing up and restoring all the files/dirs listed here: https://github.com/autonome/fxos-scripts/blob/master/backup#L17
See Also: → 987804
Duplicate of this bug: 987804
I have seen this a few times now and it's super bad. I've seen this in the logs, and it may be related:

E/GeckoConsole( 4778): [JavaScript Error: "TransactionInactiveError: A request was placed against a transaction which is currently not active, or which is finished." {file: "jar:file:///system/b2g/omni.ja!/components/SettingsManager.js" line: 70}]
E/GeckoConsole( 4778): [JavaScript Error: "NS_ERROR_UNEXPECTED: " {file: "app://system.gaiamobile.org/js/lockscreen.js" line: 971}]
I don't know what the "TransactionInactiveError" means, but maybe it means that something failed to manipulate the mozSettings. This seems similar to the Bug 980549, although the log is different.
Fabrice, Gregor - any ideas what can cause us to see the error in comment 2?

https://github.com/mozilla-b2g/gaia/blob/9f21d2c750b4c642f77bd3bf638f0f2fea93fb08/apps/system/js/lockscreen.js#L970
Flags: needinfo?(fabrice)
Flags: needinfo?(anygregor)
That's gregor-land
Possibly a dupe of bug 980549
Flags: needinfo?(fabrice)
Flags: needinfo?(anygregor)
Duping against bug 980549 to consolidate efforts in one bug.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 980549
You need to log in before you can comment on or make changes to this bug.