Closed Bug 100205 Opened 23 years ago Closed 23 years ago

mozilla startup script starts up a netscape window if netscape is running

Categories

(Core Graveyard :: Cmd-line Features, defect)

Product:
Core Graveyard
Component:
Cmd-line Features
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME

People

(Reporter: kiltedknight, Assigned: blizzard)

Details

(Whiteboard: [xremote])

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3) Gecko/20010808 BuildID: When running the 0.9.3-1 build, mozilla did not find running Netscape 4.7 processes and connect to them as if they were the same. The 0.9.4-2 build does. Reproducible: Always Steps to Reproduce: 1.Start Netscape 4.77 (that's what I'm running, anyway) 2.Run Mozilla 0.9.4-2 Actual Results: It opened a new Netscape 4.77 window instead of a Mozilla window. Expected Results: Started the Mozilla 0.9.4-2 build browser.
joe, what was the command you entered to run mozilla while netscape 4.77 was running? was it mozilla-bin -remote 'ping()'? blizzard, feel free to reassign, if needed.
Assignee: pchen → blizzard
Component: XP Apps → XP Apps: Cmd-line Features
I ran /usr/bin/mozilla. When I saw it pop up a new window from my existing Netscape 4.77 process, I went through the shell script, then tried running the commands manually (see the function "check_running()"). After running, I did "echo $?" and it came back with a value of 1.
Updating summary. ping() returns '1' like it should if there's a parse error. '2' means there was no window running.
Summary: "mozilla-bin -remote 'ping()'" shows true if Netscape 4.x is running → mozilla startup script starts up a netscape window if netscape is running
Whiteboard: [xremote]
If it's returning a parse error, then as far as the shell script is concerned, no other copy of mozilla is running. So does that make this a shell script error?
Marking these all WORKSFORME sorry about lack of response but were very overloaded here. Only reopen the bug if you can reproduce with the following steps: 1) Download the latest nightly (or 0.9.6 which should be out RSN) 2) Create a new profile 3) test the bug again If it still occurs go ahead and reopen the bug. Again sorry about no response were quite overloaded here and understaffed.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
It already worked under 0.9.5 :)
Verified WFM, then. :)
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.