Closed Bug 810138 Opened 13 years ago Closed 13 years ago

Can't download updates on my Unagi phone

Categories

(Core Graveyard :: DOM: Apps, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(blocking-basecamp:-)

RESOLVED INCOMPLETE
blocking-basecamp -

People

(Reporter: ehsan.akhgari, Unassigned)

Details

Attachments

(2 files)

The update process just seems to get stalled, and the UI goes into the downloading phase and never comes back. Here's what adb logcat tells me: E/GeckoConsole( 108): [JavaScript Error: "DOMApplicationRegistry: Could not read from /data/local/webapps/{885aa26a-0138-4154-a66f-773950cd930d}/update.webapp : [Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIChannel.asyncOpen]" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: resource://gre/modules/NetUtil.jsm :: NetUtil_asyncOpen :: line 165" data: no] E/GeckoConsole( 108): undefined" {file: "resource://gre/modules/Webapps.jsm" line: 516}] E/GeckoConsole( 108): Content JS WARN at app://costcontrol.gaiamobile.org/js/widget.js:219 in _requestUpdateBalance: No automatic updates allowed I'm not sure if this is an instance of bug 791829 or not...
blocking-basecamp: --- → ?
This is pretty serious, I think. Not sure how to draw more attention to it. :-)
Hrm, could you post a full logcat trace? The message from cost control isn't for system updates..
(In reply to comment #2) > Hrm, could you post a full logcat trace? The message from cost control isn't > for system updates.. There isn't anything related to the updater being reported in logcat...
Was there even a System Update in the download prompt? Or just apps? This could help narrowing down the possible issues a lot :)
I think it's a system update. The icon in the notification area just says that an update is available, and looks similar to the one that I got for previous system updates.
(In reply to Ehsan Akhgari [:ehsan] from comment #5) > I think it's a system update. The icon in the notification area just says > that an update is available, and looks similar to the one that I got for > previous system updates. The prompt confirming the download should list all the updates (system or apps or both).
(In reply to comment #6) > (In reply to Ehsan Akhgari [:ehsan] from comment #5) > > I think it's a system update. The icon in the notification area just says > > that an update is available, and looks similar to the one that I got for > > previous system updates. > > The prompt confirming the download should list all the updates (system or apps > or both). Hmm, what should that look like?
(In reply to Ehsan Akhgari [:ehsan] from comment #7) > (In reply to comment #6) > > (In reply to Ehsan Akhgari [:ehsan] from comment #5) > > > I think it's a system update. The icon in the notification area just says > > > that an update is available, and looks similar to the one that I got for > > > previous system updates. > > > > The prompt confirming the download should list all the updates (system or apps > > or both). > > Hmm, what should that look like? When you click the "X Updates available" notification you should be prompted with a confirm dialog listing the updates and size if available.
(In reply to comment #8) > (In reply to Ehsan Akhgari [:ehsan] from comment #7) > > (In reply to comment #6) > > > (In reply to Ehsan Akhgari [:ehsan] from comment #5) > > > > I think it's a system update. The icon in the notification area just says > > > > that an update is available, and looks similar to the one that I got for > > > > previous system updates. > > > > > > The prompt confirming the download should list all the updates (system or apps > > > or both). > > > > Hmm, what should that look like? > > When you click the "X Updates available" notification you should be prompted > with a confirm dialog listing the updates and size if available. Here's what I see: 1. "2 Updates available" (in the notification area). 2. I tap on that prompt. 3. "Download all updates". "Are you sure you want to download all updates?" 4. I tap on "Download". 5. The bug happens. The size information seems to be part of a newer update to gaia which I have not been able to get because I'm hitting this bug. Should I just send out the phone to a developer who focuses on the updater code?
Attached file Log —
OK, I tried doing this after rebooting the phone again while capturing the adb log, and this time the updater worked, and the phone rebooted and I got prompted again, and I confirmed, and this time the update process died in the middle of its work, with almost nothing useful in the log.
(In reply to Ehsan Akhgari [:ehsan] from comment #10) > Created attachment 683258 [details] > Log > > OK, I tried doing this after rebooting the phone again while capturing the > adb log, and this time the updater worked, and the phone rebooted and I got > prompted again, and I confirmed, and this time the update process died in > the middle of its work, with almost nothing useful in the log. From the logs it looks like the system updater worked and that you're now hitting an app update bug, probably bug 812931. Now when you get prompted for updates you see a list of the various updates right?
(In reply to comment #11) > (In reply to Ehsan Akhgari [:ehsan] from comment #10) > > Created attachment 683258 [details] > > Log > > > > OK, I tried doing this after rebooting the phone again while capturing the > > adb log, and this time the updater worked, and the phone rebooted and I got > > prompted again, and I confirmed, and this time the update process died in > > the middle of its work, with almost nothing useful in the log. > > From the logs it looks like the system updater worked and that you're now > hitting an app update bug, probably bug 812931. > > Now when you get prompted for updates you see a list of the various updates > right? The prompt currently tells me that there are two updates pending.
Component: Application Update → DOM: Apps
Product: Toolkit → Core
Version: unspecified → Trunk
I know I saw this bug before...or I think I did?
Whiteboard: DUPEME
blocking-basecamp: ? → +
Assignee: nobody → marshall
So this sounds like an app update bug at this point, or am I missing something?
(In reply to Marshall Culpepper [:marshall_law] from comment #14) > So this sounds like an app update bug at this point, or am I missing > something? My best guess is: it was, and it's fixed.
Keywords: qawanted
To the best of my understanding, the failed updates were Gecko updates, the ones applied by toolkit/mozapps/updates/updater.
Can I go ahead and reflash my phone so that I can continue testing the latest builds?
Maybe bug 813451?
(In reply to comment #18) > Maybe bug 813451? I am not experiencing a restart loop. Really, I think someone should just take my phone and debug this...`
Setting priority based on triage discussions. Feel free to decrease priority if you disagree.
Priority: -- → P1
Ehsan, it looks like you got updated to the last pre-FOTA update, and then your phone downloaded the FOTA update. E/GeckoConsole( 778): AUS:SVC Downloader:onProgress - progress: 10083029/10083029 E/GeckoConsole( 778): AUS:SVC Downloader:onStopRequest - original URI spec: http://update.boot2gecko.org/stable/unagi1/18.0a2/20121115094949/b2g_stable_update_2012-11-15_102959.mar, final URI spec: http://update.boot2gecko.org/stable/unagi1/18.0a2/20121115094949/b2g_stable_update_2012-11-15_102959.mar, status: 0 E/GeckoConsole( 778): AUS:SVC Downloader:onStopRequest - setting state to: pending E/GeckoConsole( 778): AUS:SVC gCanStageUpdates - able to stage updates because we'll use the service E/GeckoConsole( 778): AUS:SVC UpdateService:applyUpdateInBackground called with the following update: B2G 18.0a2 I/GonkAutoMounter( 960): Mounted /system partition as read-only E/GeckoConsole( 778): AUS:SVC readStatusFile - status: applying, path: /data/local/updates/0/update.status E/GeckoConsole( 778): AUS:SVC UpdateManager:refreshUpdateStatus - Notifying observers that the update was staged. state: applying, status: applying But nothing happens in the log after this. Did you see a dialog pop up asking you to restart? What happened when you restarted? Did you see a little android dude?
Flags: needinfo?(ehsan)
No, there was no dialog. I don't _think_ that I saw the Android dude there, since I remember seeing that a couple of days ago for the first time, but unfortunately I can't say this 100% for sure. It _could_ be that I was not looking closely enough, or that I'm misremembering.
Flags: needinfo?(ehsan)
Alright, I don't think there's a lot more we can do here. If your phone is at hand and you can find either me or "marshall_law" on IRC, we can check one more thing.
(In reply to comment #23) > Alright, I don't think there's a lot more we can do here. If your phone is at > hand and you can find either me or "marshall_law" on IRC, we can check one more > thing. My phone is sitting on my desk. But I'm going into an interview in 15 minutes... I can give it to Andrew too.
We found out that - your phone downloaded and successfully applied the FOTA update around Thu Nov 22 23:31:58 2012 - there's no new update being staged So this all fits: attachment 683258 [details] shows a successful download, and a few days later (next time you restarted?) the update was applied. Can you grab a new logcat after you force-check for an update and email it to cjones@mozilla.com?
(In reply to comment #25) > We found out that > - your phone downloaded and successfully applied the FOTA update around Thu > Nov 22 23:31:58 2012 > - there's no new update being staged > > So this all fits: attachment 683258 [details] shows a successful download, and a few days > later (next time you restarted?) the update was applied. > > Can you grab a new logcat after you force-check for an update and email it to > cjones@mozilla.com? Hmm, now I am facing another problem. Gaia isn't working for me any more, so my phone basically doesn't have a UI any more. (It just says "mozilla" on the bottom right side of the screen.) Can I force-check an update without using the Gaia settings app?
Ugh :(. The first update poll is done automatically after 5 minutes or an hour, I don't recall the default. So if you let your phone sit it should check. Emailing a logcat right now would be fantastic though. Getting the mozilla screen is obviously bad :(.
Attached file New log —
OK, this log captures turning the phone on, the mozilla logo appearing, and then the display going to sleep.
Mass Modify: All un-milestoned, unresolved blocking-basecamp+ bugs are being moved into the C3 milestone. Note that the target milestone does not mean that these bugs can't be resolved prior to 12/10, rather C2 bugs should be prioritized ahead of C3 bugs.
Target Milestone: --- → B2G C3 (12dec-1jan)
No update for >10 days. Ehsan, are you seeing the problem still? Marshall, have you had a chance to look? If you can't soon, can you unassign so we can give to someone else?
Ehsan is out until Wed, not sure where his phone is.
Assignee: marshall → nobody
I just spoke with Ehsan and he hasn't had a chance to get any more information here. He re-flashed his phone and has had at least one update since then. We may want to un-+ this since it seems unreproducible at this point. Putting back to nom for re-triage.
blocking-basecamp: + → ?
Triagers agreed with my suggestion to minus for now but please re-nom if you disagree.
blocking-basecamp: ? → -
I saw this happened in several builds before, issue also might be related to bug 829068 however it does nor repro on Build ID: 20130208070202 Kernel: Dec 5 Gecko http://hg.mozilla.org/releases/mozilla-b2g18/rev/4518b78583d0 Gaia 7e54ca673277b20b1d91d18477dc44d6ad226761
(In reply to Nick Dee from comment #34) > I saw this happened in several builds before, issue also might be related to > bug 829068 > > however it does nor repro on > > Build ID: 20130208070202 > Kernel: Dec 5 > Gecko http://hg.mozilla.org/releases/mozilla-b2g18/rev/4518b78583d0 > Gaia 7e54ca673277b20b1d91d18477dc44d6ad226761 I'd like to think that both this bug and bug 829068 have been fixed (by a variety of other bugs). There's been alot of improvements to the update code in this particular area (downloads getting stuck, etc) in late Jan.
There's been a ton of code churn as mentioned in comment 35, and I don't see how we could possibly reproduce the original environment. Removing qawanted, though we'll continue to keep an eye on updates.
Keywords: qawanted
I'm inclined to close this bug and open new ones for new issues we hit. Any objections?
Priority: P1 → --
Target Milestone: B2G C3 (12dec-1jan) → ---
Whiteboard: DUPEME → [closeme 3/4/2013]
Resolved per whiteboard
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 3/4/2013]
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: