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 149929 - Cannot run on a remote display when already running on local display
Cannot run on a remote display when already running on local display
Status: RESOLVED DUPLICATE of bug 69260
Product: galeon
Classification: Deprecated
Component: general
1.3.17
Other Linux
: Normal normal
: ---
Assigned To: galeon-maint
galeon-maint
Depends on:
Blocks:
 
 
Reported: 2004-08-11 18:15 UTC by madcap
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description madcap 2004-08-11 18:15:27 UTC
1. On box 1, run galeon on the local display.
2. On box 2, log into box 1 and set your display to box 2's (export DISPLAY=box2:0)
3. Attempt to run galeon to box 2's display.

Actual Results:
A new galeon window appears on box 1's display. This is part of the same session
started in step 1.

Expected Results:
A new galeon window appears on box 2's display. This window is part of a
seperate session than in step 1 (if you quit box 2's galeon, it doesn't quit box
1). Any saved sessions are per-display (so if I save box 2's session, it will
restore it only when running to box 2's display- or maybe you want to ask at
save time, gconf setting, etc. it's not that important to me). 

This is written for 1.3.17 since that's what I'm using right now, but this has
existed in galeon versions dating far back.
Comment 1 Tommi Komulainen 2004-08-11 18:37:52 UTC

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