672762 - The application Nightly (process org.mozilla.fennec" has stopped unexpectedly at update 07/20

Status: RESOLVED DUPLICATE of bug 672809

(Firefox for Android Graveyard :: General, defect)

Description

[Anna (Waverley)]

Attachment: The error message.

Build Id : 
Mozilla /5.0 (Android;Linux armv7l;rv:8.0a1) Gecko/20110720 Firefox/8.0a1 Fennec/8.0a1 
Device: HTC Desire Z (Android 2.2), Google Nexus S (Android 2.3) and LG Optimus 2x P990 (Android 2.2)


Steps to reproduce:
1. Mozilla /5.0 (Android;Linux armv7l;rv:8.0a1) Gecko/20110719 Firefox/8.0a1 Fennec/8.0a1  installed
2. Go to about:fennec
3. Check for updates
4. Install update -> replace application yes
5. Open application

Expected result:
The application should open with Mozilla /5.0 (Android;Linux armv7l;rv:8.0a1) Gecko/20110720 Firefox/8.0a1 Fennec/8.0a1 installed

Actual result:
The application crashes at startup, giving the error: "The application Nightly (process org.mozilla.fennec" has stopped unexpectedly. Please try again." Please see the screenshot.

Note: One has to uninstall the application and install it directly from the ftp in order to launch it. Clearing data from Applications -> Manage Applications -> Nightly doesn't solve the problem.

Comment 1

[Anna (Waverley)]

Regression from bug 656609.

Comment 2

[Mark Finkle (:mfinkle) (use needinfo?)]

We need some logcat output

Comment 3

[Anna (Waverley)]

Attachment: the logcat

Comment 4

[Aaron Train [:aaronmt]]

(In reply to comment #1)
> Regression from bug 656609.

What? This is a dupe of 672809

Comment 6

[Anna (Waverley)]

(In reply to comment #4)
> (In reply to comment #1)
> > Regression from bug 656609.
> 
> What? This is a dupe of 672809
> 
> *** This bug has been marked as a duplicate of bug 672809 ***

I thought bug 672809 is a dupe of this bug, since it's newer. No?

Comment 7

[Mark Finkle (:mfinkle) (use needinfo?)]

bug 672809 has a patch, so in this case we dupe the bug without the patch. Usually we would dupe the newer bug. Sometimes it doesn't work out that way.

Comment 8

[Brad Lassey [:blassey] (use needinfo?)]

As I see it, the rule of thumb is to dupe to the bug with more activity (and a patch represents a lot of activity). If neither bug has a lot of activity, then newness can be the tie breaker.