Closed Bug 750739 Opened 12 years ago Closed 12 years ago

Java UI up and running requests to load pages via the home screen or awesome bar fail to load , part 2

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Android
defect
Not set
normal

Tracking

(blocking-fennec1.0 -)

RESOLVED DUPLICATE of bug 750950
Tracking Status
blocking-fennec1.0 --- -

People

(Reporter: martijn.martijn, Unassigned)

Details

Attachments

(1 file)

Attached file Catlog
I'm basically still seeing bug 746444, except the "error building JSON arguments", I only see that when tapping on one of the entries  from "Your tabs from last time".

For the rest, I don't really see any useful error messages in the log, afaik.
I'm just unable to enter any url to follow or use any of the autocomplete entries to load that url.

This is with the HTC Desire HD, using today's Nightly build (downloaded it today from nightly.mozilla.org).

I got into this state after a long hang, where I just force stopped Fennec, because it didn't seem to go anywhere (I didn't get any UI, only saw a blue background).

When tapping on one of the Top sites thumbnails, at least the throbber starts spinning, but nothing happens afterwards.
Let me know, if you need more info from this phone or whatever to diagnose the problem.
There's nothing useful in the logs to know for sure if this is the same as bug 746444. You should be seeing a log message prefixed with "GeckoDBUtils" when exception that causes bug 746444 is thrown. I can't see it in your logcat...

Is it a permanent state? I mean, does restarting Fennec fix the problem? Do you need to reboot the phone?
Yes, it's a permanent state, restarting Fennec doesn't fix the problem.
A restart of the phone did help.

I guess that makes this bug worksforme then.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Except, that is not really a solution. A user shouldn't be expected to reboot his phone.
(In reply to Martijn Wargers [:mw22] (QA - IRC nick: mw22) from comment #4)
> Except, that is not really a solution. A user shouldn't be expected to
> reboot his phone.

Martijn, let's keep this bug open. If you get to reproduce this bug again, it would be useful if you attached the full list of running processes on the device too (adb shell ps). And the logcat output too.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Ok, thanks for the heads up. I'll keep on eye on it.
Btw, perhaps bug 750950 is a related bug?
Let's keep looking for this.
blocking-fennec1.0: ? → -
Keywords: qawanted
doesn't sound like this is affecting many people, but please renom if it becomes more prominent
This is the same as bug 750950. Dupping.
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → DUPLICATE
Clearing the qawanted flag since this was duplicated
Keywords: qawanted
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: