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 737694 - gnome-terminal-server can't XOpenDisplay() when run from "ssh -X localhost"
gnome-terminal-server can't XOpenDisplay() when run from "ssh -X localhost"
Status: RESOLVED OBSOLETE
Product: gnome-terminal
Classification: Core
Component: general
3.10.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-10-01 00:18 UTC by Federico Mena Quintero
Modified: 2021-06-10 20:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Federico Mena Quintero 2014-10-01 00:18:10 UTC 
1. Log into your machine as usual.

2. Open a terminal (any terminal, either gnome-terminal or an xterm)

3. ssh -X localhost

4. run "gnome-terminal" by hand from the ssh session

You get this:

  X11 connection rejected because of wrong authentication.
  Error creating terminal: No screen 0 on display "localhost:10.0"

This is because:

a. In your ssh session, you run gnome-terminal, which does a DBus call to gnome-terminal-server.

b. Your session DBus from (1) above launches gnome-terminal-server with DISPLAY=:0.  Or, if gnome-terminal-server was already running from (2), it of course has that same DISPLAY.

c. gnome-terminal-server gets to terminal_util_get_screen_by_display_name(display="localhost:10.0").  It can't find "localhost:10" in GdkDisplayManager's list of displays, since g-t-s was only launched for :0.  However, then it calls gdk_display_open("localhost:10.0") and fails.

How can we pass the X authorization via DBus?
Comment 1 GNOME Infrastructure Team 2021-06-10 20:52:01 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/7505.