Closed
Bug 672762
Opened 13 years ago
Closed 13 years ago
The application Nightly (process org.mozilla.fennec" has stopped unexpectedly at update 07/20
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 672809
People
(Reporter: anamaria.moldovan, Unassigned)
References
Details
Attachments
(2 files)
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.
Reporter | ||
Comment 1•13 years ago
|
||
Regression from bug 656609.
Comment 2•13 years ago
|
||
We need some logcat output
Reporter | ||
Comment 3•13 years ago
|
||
Comment 4•13 years ago
|
||
(In reply to comment #1) > Regression from bug 656609. What? This is a dupe of 672809
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 6•13 years ago
|
||
(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•13 years ago
|
||
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•13 years ago
|
||
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.
You need to log in
before you can comment on or make changes to this bug.
Description
•