334568 - Renaming Camino.app creates non-functional application

Status: VERIFIED INVALID

(Camino Graveyard :: General, defect)

Description

[Andrew Reynhout]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20060413 Camino/1.0+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20060413 Camino/1.0+

Renaming Camino.app to, say, Camino-1.0+20060513.app, breaks the application.

I didn't notice this for a long time -- it seems that as long as there is an application named Camino.app, the bug isn't triggered (or at least the failure mode is invisible).

I renamed /Applications/Camino.app to /Applications/Camino-1.0.app and downloaded a nightly build.  I moved the nightly to the Apps dir, then renamed it to Camino-1.0+20060413.app, and launched it.

Camino popped up a "Where is Camino.app" dialog, with a modified file picker listing all of the apps under /Applications.  I chose "Camino-1.0+20060413.app", but the dialog popped right back up.  I selected Cancel, but the dialog popped right back up again.  Clicking Cancel four or five times in a row worked, but left me with Camino as the foreground app (About Camino revealed it to be the nightly I had launched, as expected), but no open browser window.  "New Window" got me a window, but Camino didn't seem to have loaded my profile (no bookmarks, etc).  Quit, renamed the nightly back to Camino.app, everything was back to normal.

Also, renaming the 1.0 binary back to Camino.app, then launching Camino-1.0+20060413.app works fine too (runs the nightly build).  Only when there's nothing named Camino.app does the bug occur.

My guess: somewhere, the application name is hardcoded.  When running a renamed version, it pulls something from the Camino.app directory structure (when possible) and continues along happily, or fails strangely (when not possible).


Reproducible: Always

Steps to Reproduce:
1. Rename all instances of "Camino.app" in the Finder launch path (possibly just within /Applications and /Users/yourname/Applications, but not sure)
2. Launch one of them
3. there is no step 3!

Actual Results:  
"Where is Camino.app" dialog, then (after several clicks) non-operable browser

Expected Results:  
Normal launch

Comment 1

[Stuart Morgan]

WFM with 2006032900.  Does it happen with Camino 1.0?  Do you have any third-party pref panes or the like for Camino installed?

Comment 2

[Andrew Reynhout]

(In reply to comment #1)
> Do you have any
> third-party pref panes or the like for Camino installed?

Yes: CamiTools and CamiScript.

I hadn't even considered third-party stuff, I apologize.

So I dug deeper, and it appears to be related to the contents of the Scripts directory.  When the directory exists but is empty (like in a fresh profile), Camino launches correctly regardless of the naming.  When Scripts is not empty, I get the behavior described.  The number of Cancel clicks required to get past the "Where is Camino.app" dialog is related to the number of scripts in the directory.

So this sounds like a CamiScript problem, right?

Thank you for your time and assistance!

Comment 3

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Invalid per comment 2.