If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Local and remote browsers conflict

VERIFIED INVALID

Status

SeaMonkey
General
VERIFIED INVALID
16 years ago
12 years ago

People

(Reporter: brian, Assigned: blizzard)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
1) Open a browser on the local machine.
2) SSH (with X11 forwarding) to a remote machine and open up a remote browser.

Instead of starting a new remote browser, another window in the local browser is
opened.

This also happens in the reverse - opening a remote browser, then a local
browser, just opens another window on the remote machine.

I am using the 20020414 build.
I assume you're using the linux rpm distribution? If so, that's the design
behavior...
Assignee: Matti → blizzard
Status: UNCONFIRMED → NEW
Ever confirmed: true
(Reporter)

Comment 2

16 years ago
No, I am using a Debian package "mozilla-snapshot", actually.  If this is the
design behavior for RPM, does that imply there is a way to turn this 'feature' off?

The main problem is running Mozilla locally (especially for mail).  If I then
want to open a remote browser (mostly for remote file browsing (ie
file:///foo.html - for testing in-development web sites on our development box),
I must close all local windows locally before using a remote setup.  This is
*VERY* annoying :)
> does that imply there is a way to turn this 'feature' off?

Yes.  Edit the shell script that starts mozilla (not sure whether this is
'mozilla' or 'run-mozilla.sh' that you'd want to edit) to not use -remote to
open new windows instead of starting the browser...

You can also start the remote browser by running it with -Pprofilemanager, iirc.
(Reporter)

Comment 4

16 years ago
Excellent.  Actually, as long as there is *any* option specified it does not use
-remote.  A '-noremote' option would be nice for this if it is going to be the
default to use -remote, though.

Thanks,
-Brian
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → INVALID

Comment 5

16 years ago
is this really invalid?

bz?
Yes. It's a "bug" or "feature" in Debian's startup script, which has nothing to
do with mozilla.org
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.