309117 - No updates found, if FF is installed in non-default directory

Status: RESOLVED WORKSFORME

(Toolkit :: Application Update, defect)

Description

[Sokraates]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b4) Gecko/20050918 Firefox/1.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b4) Gecko/20050918 Firefox/1.4

If Firefox is installed in any directory other than the default program
directory "C:\Program Files\Mozilla Firefox", checking for updates will always
result in no new updates being found.

Reproducible: Always

Steps to Reproduce:
1. Install Firefox in any non-default prgram directory (e.g. C:\Program
Files\firefox)
2. Click "Help" -> "Check for Updates"
3. Read the message telling you, that no updates were found. :)

Actual Results:  
No updates were found, even though there were more than enough.

Expected Results:  
Firefox should find and install updates, no mather where the program directory lies.

Comment 1

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

WFM from Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5)
Gecko/20050924 Firefox/1.4, installed into C:\Program Files\firefox, member of
Power Users group for Windows file permissions.

Do you have the LiveHTTPHeaders extension installed ? If so, then go Tools >
Live HTTP headers, Firefox window > Help > Check for updates, Finish. Copy the
URL retrieved from the LiveHTTPHeaders window and post it here (it will look
something like this http://aus2.mozilla.org/...../update.xml)

Comment 2

[Peter van der Woude [:Peter6]]

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b5) Gecko/20051003
Firefox/1.4.1 ID:2005100309

WFM

Comment 3

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

Reporter, please try to reproduce this bug with a build from 
 http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2005-10-04-18-mozilla1.8/

If you can still reproduce, please attach 
 <Firefox install dir>/updates/last-update.log
to this bug.

Comment 4

[Sokraates]

Only today I got around to give it another try.

Tried a updating 20051029 ZIP-build to 20051030 and it worked.

Strange ... maybe I accidently used an hourly build when first encountering this problem. 

Comment 5

[Axel Hecht]

resolving per reporters comments