After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 84982 - "galeon -w" ignores $DISPLAY
"galeon -w" ignores $DISPLAY
Status: RESOLVED DUPLICATE of bug 84981
Product: galeon
Classification: Deprecated
Component: general
1.2.0
Other other
: Normal normal
: ---
Assigned To: galeon-maint
Yanko Kaneti
Depends on:
Blocks:
 
 
Reported: 2002-06-12 08:24 UTC by Michael Toomim
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Michael Toomim 2002-06-12 08:24:28 UTC
If I run galeon locally on machine/xserver (A), log in remotely from
machine/xserver (B), and try to open a new window on machine/xserver (B)
with "galeon -w", the window appears on machine/xserver (A) instead of (B),
ignoring the $DISPLAY variable and the --display cammand-line option.

This is what happens when I log in through an ssh connection to the remote
host acacia, which is already running a galeon instance:

acacia ~$ galeon -x -w --display=$DISPLAY
Message: Galeon already running, using existing process
acacia ~$ echo $DISPLAY
acacia.CS.Berkeley.EDU:10.0

Note that I can't get it to open a window on my xserver with any
combination of the --display option, the $DISPLAY environment variable, the
-x option and the -w option.  I've tried them all, even though I didn't
list the experiments here.

BTW, it also seems to me that I shouldn't get the message "Message: Galeon
already running, using existing process" if I explicitly TELL it to use an
existing process, but this is a minor quibble.
Comment 1 Yanko Kaneti 2002-06-12 13:11:19 UTC

*** This bug has been marked as a duplicate of 84981 ***