Closed Bug 808893 Opened 13 years ago Closed 13 years ago

Dock is empty after recent OTA update

Categories

(Firefox OS Graveyard :: Gaia, defect)

defect
Not set
major

Tracking

(blocking-basecamp:+)

VERIFIED FIXED
blocking-basecamp +

People

(Reporter: julienw, Unassigned)

References

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/18.0 Firefox/18.0 Build ID: 20121101042011 Steps to reproduce: * I started Gaia Actual results: * The dock is empty Expected results: * The dock has icons
Attached patch patchSplinter Review
Attachment #678601 - Flags: review?(21)
blocking-basecamp: --- → ?
I saw this last night on my 11/5 OTA. Let me know if you need my device to debug.
The most suspicious-looking errors from clee's phone were E/GeckoConsole( 389): [JavaScript Error: "NotFoundError: The operation failed because the requested database object could not be found. For example, an object store did not exist but was being opened." {file: "app://homescreen.gaiamobile.org/js/state.js" line: 68}] E/GeckoConsole( 108): [JavaScript Error: "NotFoundError: The operation failed because the requested database object could not be found. For example, an object store did not exist but was being opened." {file: "app://homescreen.gaiamobile.org/js/state.js" line: 68}]
Severity: normal → major
Status: UNCONFIRMED → NEW
blocking-basecamp: ? → +
Ever confirmed: true
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
The 11-6 stable update was promoted with this bug. It has decommissioned my dogfooding phone because of loss of core functionality. Considering that we respun a build for the *nightly* channel to pick up the fix to this bug, I suggest that we do the same for the stable channel.
(In reply to Chris Jones [:cjones] [:warhammer] from comment #5) > The 11-6 stable update was promoted with this bug. It has decommissioned my > dogfooding phone because of loss of core functionality. > > Considering that we respun a build for the *nightly* channel to pick up the > fix to this bug, I suggest that we do the same for the stable channel. I'll trigger the update today with this fix in it.
(In reply to Lukas Blakk [:lsblakk] from comment #6) > I'll trigger the update today with this fix in it. jgriffin beat me to it, should have an updated stable build within the hour.
(In reply to Chris Jones [:cjones] [:warhammer] from comment #5) > The 11-6 stable update was promoted with this bug. Actually, we promoted the 11-05 stable build which did not have this issue caught by QA/smoketests. There needs to be investigation into how such a regression could slip past.
Agree, we should fine out why this wasn't caught in our nightly->stable update process.
new update is available to testers on the stable channel now.
Confirmed, dogfooding phone back in commission. I had rearranged the icons on my homescreen, and I had installed an e.me app. Maybe one of those two things triggered the bug?
Chris, this bug was actually triggered by an error in Gaia code...
Blocks: 810346
Verified fixed after updating to 11-12 build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: