STR: 1. Check OTA and there is a downloadable content 2. Download it 3. System would show it's unzipping 4. After unzipping, nothing happen. The notification still shows there is a downloadable content See: https://www.youtube.com/watch?v=s-dpffeoTEA It seems a platform corruption since the unzipping process. So I set general since I don't know which component it should be. The utility tray is also broken but I think the major error is irrelevant with that. The 'last updated' in Settings app also shows incorrect 1970/01/27. My Flame only updated with OTA updates without any refreshing. And it's updatable yesterday. Device Flame: Gecko: 34.0a1 20140818160207 Gaia: 2014-08-18 16:12:52 778c39b5

QA Wanted for branch checks.

The root cause of this bug is the same as bug 1021839 and 1036835.

Branch Checks I was unable to reproduce this issue using the STR listed in Comment 0. (All checks utilized Nightly builds) Device: Flame Master BuildID: 20140826040204 Gaia: 4d1d0ea5a82cddeeab497774cfa1703639e3c7d9 Gecko: dc352a7bf234 Version: 34.0a1 (Master) Firmware Version: v123 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 -------------------------------------------------------------------- Device: Flame 2.0 Build ID: 20140903000206 Gaia: 449d8db9b3ea1f9262db822c37ef2143477172b7 Gecko: 13b41e22c8f6 Version: 32.0 (2.0) Firmware Version: v123 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 -------------------------------------------------------------------- Device: Flame 1.4 BuildID: 20140819000201 Gaia: 3e53eb07bf1c2cafeba53812ebe91835089723d3 Gecko: c45814bfd93b Version: 30.0 (1.4) Firmware Version: v123 User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

No Nom without a solid repro

Although I don't actually know how QA usually test bug like this, but I think it can't be tested with flashing with any specific branch. Because the symptom is not caused by bug immediately: you need to OTA several times until it can't OTA anymore. It's caused by some bugs, of course, but the way to affect the device is a slow progress, with a serious damage (can't OTA anymore). It may be better if we can put some devices only updated with daily nightly OTA, to discover the problems like this, rather than waiting user reporting it. Maybe QA team has already do that, but I think the way to check bug like this may need to accomplish the way the error occurs.

Most likely a dup of bug 1085230. Note that the weird last update time in settings is bug 1051083.