41991 - Logfile shows extra "./" in pathway for Linux installs

Status: RESOLVED INCOMPLETE

(Core Graveyard :: Installer: XPInstall Engine, defect, P2)

Description

[David Epstein]

build 2000-06-08-08-M16. Linux installed build only.
1. On Linux, go to http://jimbob/trigger3.html
2. Select any test case installing something, say a_addtestfile.
3. Trigger and OK.
4. Check logfile.
Result: Pathways for "Create Folder" and "Installing" contain and extra "./". 
This is where "package" folder is for extracted builds.

logfile examples:

-------------------------------------------------------------------------------
http://jimbob/jars/a_addtestfile.xpi  --  06/08/2000 17:37:51
-------------------------------------------------------------------------------

     Acceptance: a_addtestfile
     -------------------------

     [1/2]	Create Folder: /u/depstein/builds/M16/jun08/./testFolder
     [2/2]	Installing: 
/u/depstein/builds/M16/jun08/./testFolder/smrtupdt.txt

     Install completed successfully
     Finished Installation  06/08/2000 17:37:52

-------------------------------------------------------------------------------

-------------------------------------------------------------------------------
http://jimbob/jars/a_adddir_full_iver_ver.xpi  --  06/08/2000 14:38:38 
-------------------------------------------------------------------------------

     Acceptance: a_adddir_full_iver_ver
     ----------------------------------

     [1/3]	Create Folder: 
/u/depstein/builds/M16/jun08/./adddir_full_iver_ver
     [2/3]	Create Folder: 
/u/depstein/builds/M16/jun08/./adddir_full_iver_ver/subdir
     [3/3]	Installing: 
/u/depstein/builds/M16/jun08/./adddir_full_iver_ver/subdir/smrtupdt.txt

     Install completed successfully
     Finished Installation  06/08/2000 14:38:38

Comment 1

[Daniel Veditz [:dveditz] back January 5, 2026]

I'm not sure this is a problem, that is indeed the path to which we 
installed. Apparently XPCOM is giving us directory paths with that character in 
it, but it is accurate as far as it goes.

Maybe nsIFile should be squeezing out these characters? Reassigning to Samir 
for evaluation, with an eye toward closing it though.

Comment 2

[Samir Gehani]

Dep, 
Did you provide a relative path in the folder selection dialog in the installer?

Comment 3

[David Epstein]

no, I'm using an absolute path selected from the File Change dialog.

Comment 4

[David Epstein]

changed qa owner to depstein

Comment 5

[Daniel Veditz [:dveditz] back January 5, 2026]

How do you start mozilla? if it's something like ./mozilla that could be where 
XPCOM is getting the extra slash. In any case this is an XPCOM or nsIFile bug 
at best and most likely won't get fixed.

Comment 6

[David Epstein]

Yes, Mozilla is started with ./mozilla. But it's only happening in the installed 
build. In the extracted build, the file pathway correctly appears with the 
"package" folder (i.e. .../package/testFolder/file.txt) without the extra "./".
Yesterday's build was the first time I saw this occur.

Comment 7

[Daniel Veditz [:dveditz] back January 5, 2026]

*** Bug 42693 has been marked as a duplicate of this bug. ***

Comment 8

[Daniel Veditz [:dveditz] back January 5, 2026]

Resetting target field for missed milestones

Comment 9

[Jimmy Lee]

Updating QA Contact.

Comment 10

[Samir Gehani]

Over to Syd for installer bug triage

Comment 11

[R.K.Aa.]

Is this still an issue?