633237 - Firefox, 3.6.13, On the help menu, Apply Downloaded Update Now, Shows after restart

Status: RESOLVED INCOMPLETE

(Toolkit :: Application Update, defect)

Description

[tmax_us]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13 ( .NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13 ( .NET CLR 3.5.30729)

Firefox 3.6.13 - Shows on the help menu after restart. Have tried restart with no success. Keeps showing (Apply Downloaded Update Now).

Reproducible: Always

Steps to Reproduce:
1.Apply Downloaded Update Now
2.Apply Downloaded Update Now
3.Apply Downloaded Update Now
Actual Results:  
Same in help menu - Apply Downloaded Update Now

Expected Results:  
Should show no updates.

Updated or Should show no updates.

Comment 1

[Rob]

I am filing a _different_ (but similar) bug for Namoroka and spotted _this_ Bug when searching for Dupes.

I had this happen a moment ago. I checked for and applied Updates three times in a row and NOW when I check for Updates it seems to have 'ran out' and says I am up to date. 

It seems unlikely (but not impossible) that there would be so many Updates (even for Namoroka) in so short a period of time (three in less than ten minutes) and the first two did not 'seem to take' since the 'date version' (20110225033207) did not increment.

So I can _partially_ confirm this for a _different_ version of "Firefox" specifically "Namoroka". I say "partially" because I have a 'different' Browser and since the Reporter did not try FOUR times in a row  :(  .

Thanks,
Rob


Note:
"C:\Program Files\Mozilla Firefox\firefox.exe"		"Firefox"
"C:\Program Files\Namoroka\firefox.exe"			"Namoroka"


PS: I don't have enough 'Beans' to click on the Button to Confirm someone else's BR otherwise I would since it seems close enough to confirm (and avoid a Dupe).

Comment 2

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

Rob, for app update bugs it is better to file a bug and once the root cause is figured out it can be duped if necessary so please file a new bug

Comment 3

[Rob]

(In reply to comment #2)
> Rob, for app update bugs it is better to file a bug and once the root cause is
> figured out it can be duped if necessary so please file a new bug

I guess I spend too much time in the "other" Camps ;) (gcc, S/OS/illumos, etc.) where Dupes are to be avoided and 'cross-version confirmations' are desired.

I was just trying to CONFIRM for tmax_us .


I was fearful that my BR would languish and be WFM on the basis of: being hard to reproduce (esp. on FF-3.6.13 due to infrequent Updates, less so on Namoroka) AND being non-reproducible due to others not using TM+ and having 200+ Tabs open (so they 'dig in' to Windows VM (Swap File)) bringing restarts to a crawl (30 seconds to "really close" and 5 minutes to "finish" starting).


Will Bug 636916 fulfill the requirement to file a new BR ?

I can easily copy Bug 633237 Comment 1 and file a NEW Bug Report if you still desire.

Thanks,
Rob

Comment 4

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

Without knowing the root cause there is absolutely no way of knowing whether what you are experiencing is the same and in this specific instance there have been multiple root causes that lead to the same symptoms and each of which will need to be addressed separately.

The reason bug reports will often languish is I am one person trying to diagnose the root cause while I am also trying to fix bugs where the root cause is already understood and am also prioritizing my work so I fix the bugs where the largest number of users benefit.

As I stated in bug 636916 which you reported, I highly suspect that bug 636916 is either fixed for you on trunk. I would very much like to understand the root cause of what you are experiencing as I would like to understand all app update bugs so let's try to figure it out but please keep the discussion outside of this bug and in own bug 636916.

Comment 5

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

Reporter, is this still happening for you? If it is, please download / install the latest and at http://www.mozilla.com/en-US/firefox/new/ and report back when the next update is available as to whether you are still having this problem. Thanks

Comment 6

[Tim (fmdeveloper)]

Closing bug as Incomplete - if you are still experiencing this issue or have more information to provide feel free to post back here and we can re-open the bug. You can also get assistance by visiting the Firefox help site -> http://support.mozilla.com/en-US/kb/Ask+a+question