Hi,
> I now have his PC with me on my local network, and commands executed
> through ssh -X still display on his screen instead of mine.
>
> From his gnome-terminal on my PC:
> [gary@fedora ~]$ echo $DISPLAY
> localhost:10.0
>
> How do I set the display for commands executed remotely to appear on my
> screen?
It might be the program ignoring the DISPLAY because it's using wayland
or because it already is running locally and just starts a new window.
Try running something like "xdpyinfo" or "xrandr" to see if you can tell
which display it's using.
That's a great thought. it does appear when running xrandr that it is the local display (my desktop) when running xrandr over ssh on the remote system. My display size is 3440x1440, and reports the same when running locally.
[gary@garypc ~]$ echo $DISPLAY
localhost:10.0
localhost:10.0
[gary@garypc ~]$ xrandr
Screen 0: minimum 320 x 200, current 3440 x 1440, maximum 16384 x 16384
Screen 0: minimum 320 x 200, current 3440 x 1440, maximum 16384 x 16384
When running on the garypc system, it reports 1920x1080, which is also correct.
However, even when launching gnome-terminal when none is currently running, it still launches on the remote system, not my desktop.
You can try running "export GDK_BACKEND=x11" before running evolution.
Setting that env variable causes evolution to not run at all:
[gary@garypc ~]$ export GDK_BACKEND=x11
[gary@garypc ~]$ evolution
libEGL warning: DRI3: failed to query the version
libEGL warning: DRI2: failed to authenticate
(evolution:985885): Gdk-WARNING **: 14:47:55.252: The program 'evolution' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
(Details: serial 174 error_code 1 request_code 155 (unknown) minor_code 1)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
[gary@garypc ~]$ evolution
libEGL warning: DRI3: failed to query the version
libEGL warning: DRI2: failed to authenticate
(evolution:985885): Gdk-WARNING **: 14:47:55.252: The program 'evolution' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
(Details: serial 174 error_code 1 request_code 155 (unknown) minor_code 1)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
One difference is that his PC is Wayland while mine is X11, but that shouldn't have anything to do with *where* a program is displayed.
-- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
