Closed Bug 68812 Opened 25 years ago Closed 25 years ago

Mozilla hangs when starting on OpenVMS V7.2-1 system

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Platform:
DEC
OpenVMS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: john.reagan, Assigned: colin)

Details

I installed the latest OpenVMS version of Mozilla from http://www.openvms.compaq.com/openvms/products/ips/MOZILLA-OPENVMS-ALPHA- M07.SFX_AXPEXE to my V7.2-1 system. I installed it into the default area. When I try to run it, it only prints $ @SYS$COMMON:[MOZILLA]MOZILLA Starting mozilla-bin... Registering plugin 0 for: "*","All types",".*" and then hangs. Nothing else... I'm running V7.2-1 plus VMS721_ACRTL V2.0 VMS721_UPDATE V1.0 I'm planning on installing the next V7.2-1 update (its available) plus a newer ACRTL. I have Java V1.3-1 installed, but that should have gone into a different directory tree and not affected the default Java files yes?
Reporter, does the user running mozilla have write access to the directory Mozilla is installed in? See bug 41057.
No, I don't have write access (by default) to SYS$COMMON:[MOZILLA] from my own account. I set the directory to world:write access and retried. No change.
Well, after the first attempt one often has corrupted files to contend with... Could you please do the following? 1) do a clean install of Mozilla 2) make sure the mozilla install directory is writable by you 3) make sure you are using a clean profile (run mozilla -profilemanager or just delete your currently existing profile) 4) run mozilla Does it still hang at startup after that? If so, this is unrelated to bug 41057.
I reinstalled Mozilla M0.7. I deleted my existing profile. I made sure that the install directory was world-writable Same thing... $@sys$common:[mozilla]mozilla Starting mozilla-bin... ProfileManager : CreateNewProfile Profile Name: default Profile Dir: /hiyall$/reagan/.mozilla Registering plugin 0 for: "*","All types",".*" and there it hangs. John
ccing colin, since he's the person who knows stuff about the VMS port
Make sure that all the files in the [MOZILLA...] tree are WORLD:RE.
Assignee: asa → colin
John, just to clarify, you sholdn't need any of these 7.2-1 updates. But I'm sure they won't do any harm either. Mozilla doesn't use Java yet (can't until 1.3.0_01 is released on OpenVMS), so any Java installed is irrelevant here. I assume you're running TCP/IP Services for OpenVMS; is that right?
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
All files in sys$common:[mozilla...] are indeed w:re Yes, I'm running TCP/IP (aka UCX) V5.0A ECO2 (just installed). I was running ECO1 the other day and thought that perhaps ECO2 might help. It didn't...
Can you define this logical, start Mozilla, and then send me the output: $ DEFINE VMS_TRACE_FILENAMES 1 Either post the trace here as an attachment or mail it directly to me at colin@theblakes.com (or STAR::BLAKE).
Trace mailed directly to Colin at STAR::BLAKE
With help from Colin, I have it working now. As guessed by previous folks, I didn't have full write-access to the entire bin tree for M0.7 to write into. With the correct access, it now starts up just fine. This can be closed now.
Closing.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.