646058 - OS level crash when updating Firefox kn 3.5.18->4.0 advertised

Status: RESOLVED DUPLICATE of bug 628829

(Toolkit :: Application Update, defect)

Description

[Teodosia Pop]

Attachment: screenshot

Build ID:  
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; mn; rv:1.9.1.18) Gecko/20110319 Firefox/3.5.18
and 
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; kn; rv:1.9.1.18) Gecko/20110319 Firefox/3.5.18

Mac 10.5.8

After the update from 3.5.18 to 4.0 is downloaded and FF is restarted, the update fails to install for kn and mn builds.

Steps to Reproduce:
1. Install 3.5.18 kn/mn FF build.
2. Set up FF for release test.
3. Restart FF and wait to be prompted for the update.
2. Download the update and restart FF.

Actual Results:
The update is downloaded, but after the restart, the update fails to install (see screenshot).

Expected Results:
The update should install without failures.

Comment 1

[u279076]

This is reproducible with Firefox 3.5.18 kn and ml on Mac OSX 10.6.

I've got copies of my OS crash logs which I will attach momentarily.

Comment 2

[u279076]

Attachment: Crash Log: After update

The following is a crash log which happens immediately following the update process (ie. after clicking Restart on the update dialog)

Comment 3

[u279076]

Attachment: Crash Log: After manual restart

The following is a crash log which now happens every time I try to start Firefox with this failed update.

Comment 4

[juan becerra [:juanb]]

I get: "The application Firefox Software Update quit unexpectedly", the crash log is similar to what Anthony posted.

Comment 5

[Robert Strong (they/them - no direct email)]

This is bug 628829 which hasn't made it into a release vehicle yet due to chemspills and in bug 629256 releng is supposed to have prevented updates for these locales on Mac.

Comment 6

[[e-mail] (:bhearsum)]

Did you change your update channel, by any chance?

Comment 7

[u279076]

(In reply to comment #6)
> Did you change your update channel, by any chance?

Update channel is releasetest.

Comment 8

[Henrik Skupin [:whimboo][⌚️UTC+2]]

When I have tested the updates from 3.5.18->4.0 last week I didn't got updates served on the release channel:

http://mozmill-archive.brasstacks.mozilla.com/#/update/report/b0c5cbbd24bf827d6dcfffc745d59808

Comment 9

[[e-mail] (:bhearsum)]

(In reply to comment #7)
> (In reply to comment #6)
> > Did you change your update channel, by any chance?
> 
> Update channel is releasetest.

Okay, if that's the case for Teodosia as well, then this is NOTABUG because we don't ship anything on that channel. Teodosia, do you know what your update channel is?

Comment 10

[u279076]

(In reply to comment #9)
> (In reply to comment #7)
> > (In reply to comment #6)
> > > Did you change your update channel, by any chance?
> > 
> > Update channel is releasetest.
> 
> Okay, if that's the case for Teodosia as well, then this is NOTABUG because we
> don't ship anything on that channel. Teodosia, do you know what your update
> channel is?

We instructed him to use releasetest -- I assume this was what he was testing on.  I'll let him comment if untrue.

Just for clarification, here is my STR:

1. Install Firefox 3.5.18 kn
2. Set update channel to releasetest
3. Set app.update.interval to 60 and app.update.timer to 600
4. Restart Firefox
5. Click notification when it appears
6. Install the update and click restart

Result: OS Level Crash

Comment 11

[[e-mail] (:bhearsum)]

So, if he was using releasetest, then this is fine to be a dupe of 628829, but it's not a real issue, since neither of the "real" channels (beta and release) are affected.

Comment 12

[Henrik Skupin [:whimboo][⌚️UTC+2]]

(In reply to comment #11)
> So, if he was using releasetest, then this is fine to be a dupe of 628829, but
> it's not a real issue, since neither of the "real" channels (beta and release)
> are affected.

Ben, but what I have mentioned earlier already on rd we really should keep release and releasetest in sync.

Comment 13

[[e-mail] (:bhearsum)]

(In reply to comment #12)
> (In reply to comment #11)
> > So, if he was using releasetest, then this is fine to be a dupe of 628829, but
> > it's not a real issue, since neither of the "real" channels (beta and release)
> > are affected.
> 
> Ben, but what I have mentioned earlier already on rd we really should keep
> release and releasetest in sync.

Yes, we should. It's been noted for the future.

Comment 14

[Nick Thomas [:nthomas] (UTC+12)]

I'll remove the test snippets for these broken locales over in bug 646136.