Closed Bug 432327 Opened 12 years ago Closed 10 years ago

SeaMonkey Only Launches On Account That Installed It


(SeaMonkey :: General, defect)

SeaMonkey 1.1 Branch
Not set


(Not tracked)



(Reporter: dickie, Unassigned)




(1 file)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20080201 SeaMonkey/1.1.8
Build Identifier: 

SeaMonkey 1.1.9 will not lauch correctly and displays an initial browser window that is corrupt.  This text is scattered across the bottom of the browser window:

<key id=key_savePage"   key="&savePageCmd.commandkey;" command=Browser:SavePage" modifiers="accel"/>

Deleting SeaMonkey preferences and profiles on the account did not fix the problem.  SeaMonkey 1.1.9 was executed from the Mac OS X system-wide Applications folder where SeaMonkey was installed by an administrator account.  The problem is occurring on a normal user account, but SeaMonkey runs fine on the administrator account that installed it.

But launching SeaMonkey 1.1.9 directly from the downloaded .dmg file "fixes" the problem on this account. 

I have seen problems where accounts with multiple profiles have a similar problem and making all SeaMonkey application files read-only works around that problem.  I reported that problem in 389136.  But that work-around is not working for this problem.

This all started when the original system boot disk died and we booted from an exact system disk clone on an external drive. 

Reproducible: Always

Steps to Reproduce:
1.  Install SeaMonkey in to the mac OS X system-wide Applications folder using an administrator account 
2.  Launch SeaMonkey 1.1.9 from  a normal user account
3.  Note that the initial browser window is corrupt with extra text scattered along the bottom and parts of the menu are missing or not functional

Actual Results:  
The SeaMonkey browser window is corrupt and some menu items do not work.

Expected Results:  
SeaMonkey browser window should function.
Here is a screen shot of the corrupted browser window.
(In reply to comment #0)
> The problem is occurring on a normal user account, but SeaMonkey runs fine on
> the administrator account that installed it.

Please, ask the administrator to look for what could be (going) "wrong".

(In reply to comment #1)
> Created an attachment (id=319465) [details]

This looks like an XML error.
Isn't there an error in the Error Console (too) ?
Severity: critical → major
Version: unspecified → SeaMonkey 1.1 Branch
Well, this is my son's laptop, so I guess I am the administrator.  What specific information should we provide?

And why did you lower this to major from critical?  SeaMonkey will no longer launch and run under any circumstances from the standard system-wide Mac OS X Applications folder from any account other than the administrator account that installed it.

Dup of Bug 389783? Bug 389783 Comment #15 says problem still remains on Mac OS X.
Does anyone know if FireFox and Thunderbird have this same problem?  Is converting from SeaMonkey to Firefox and Thunderbird a way to permanently fix this problem?

(In reply to comment #3)
> What specific information should we provide?

I'm not too sure.
Did you check the two bugs WADA suggested ?

> And why did you lower this to major from critical?

Critical  	crashes, loss of data, severe memory leak
Major 	major loss of function
(In reply to comment #1)
> Screen Shot Of Corrupt Browser Window

Classic Theme. Does problem occur with Modern Theme too?
(In reply to comment #3)
> What specific information should we provide?

Because "file writing to program directory" related issue is suspected, at least followings are required for problem isolation, as done for MS Win case in Bug 389136.
(1) Check which files in program directory are added/modified with permitted user(installed user when this bug's case).
Because I don't have good tools for checking, I created small script of "matching merge of output of 'DIR /S' command of MS Win" in "Open Object REXX" when Bug 389136.
(2) Obtain file activity monitor log of Seamonkey for the files of (1) with restricted/usual user.
Filemon / "Process Monitor" for MS Win were used in analysis of MS Win case of Bug 389136.  
bug 390400 cites the same text, and solution there was " reinstalled with
the proper installation and now works as expected."
See Mac OS X installation instructions at

In particular, the CANNOT be run from inside the .dmg, it MUST first be drag-dropped to the Applications folder.

ISTR that it is best to run the newly installed build once as Administrator before trying to run it as an ordinary user, but I don't see that mentioned in these Installation Instructions.

As of this writing, the current "stable" version of SeaMonkey is 2.0.11, the current "beta" version is 2.1b1, and a new nightly build of 2.1b2pre is available approximately every 24 hours.
Closing as INCOMPLETE. Also it appears to be a user access rights issue and/or DMG problem.
Closed: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.