X11 Forwarding

[ray73864]

Having an issue with X11 Forwarding.

I have X11 Forwarding turned on as default for all SSH connections, I also have X11 Forwarding enabled for my 2 SSH profiles.

However, when I try and run the command system-config-printer on our RHEL servers at work (makes no difference if I use the profile or open a fresh new SSH connection), I get the following output back:

system-config-printer
 SSH   X  Could not connect to the X server: Error: connect ECONNREFUSED 127.0.0.1:6000
 SSH      Tabby tried to connect to {"host":"localhost","port":6000} based on the DISPLAY environment var (localhost:0)
 SSH      To use X forwarding, you need a local X server, e.g.:
 SSH      * VcXsrv: https://sourceforge.net/projects/vcxsrv/
 SSH      * Xming: https://sourceforge.net/projects/xming/
The application 'system-config-printer.py' lost its connection to the display localhost:11.0;
most likely the X server was shut down or you killed/destroyed
the application.

This was working fine in Tabby Portable 1.0.189-x64, the issue only started happening when I upgraded to Tabby Portable 1.0.197-x64.

If I run the export command on the server, I get declare -x DISPLAY="localhost:11.0"

[ray73864]

[nabaco]

What system are you running on? If on Windows, do you have an X server running, like suggested in the help message?

[ray73864]

What system are you running on? If on Windows, do you have an X server running, like suggested in the help message?

Running on Windows.

I wonder, I looked back at what I was using earlier.

When I was using alpha-189, I was using the portable version, with this version, X11-Forwarding works 100%, when I type 'system-config-printer', the dialog opens 100%.

However now I am using an installed version of Tabby, X11-Forwarding is no longer working.

Would much rather not have to install anything extra, if portable comes with the necessary stuff, I feel the install version should come with it too.

Looks like in my OP, I stupidly believed I was still using the portable version, but I'm not.

[pansila]

Did you open MobaXterm or similar X server enabled terminal clients? Tabby works with X11 forwarding when these softwares run, otherwise it fails.

[ray73864]

Did you open MobaXterm or similar X server enabled terminal clients? Tabby works with X11 forwarding when these softwares run, otherwise it fails.

When I was using the portable version, I never had anything else open.

However it looks like if I open MobaXterm first, then the non-portable version works fine.

Would rather not have to have MobaXterm open or another X server running on my PC, otherwise I might as well just give up on Tabby and continue with MobaXterm.

I love Tabby, it's really nice to use, but I need this particular feature, and would prefer it was all in 1 package like it is with MobaXterm.

[overclockato]

I have the same ray73864 issue, using Putty the X11 forwarding works fine.

[zouxf]

In my opinion, this is probably the only place where tabby loses out to mobaxterm

[jdrch]

In my opinion, this is probably the only place where tabby loses out to mobaxterm

Agreed. On the flip side, good luck getting MobaXterm to work with a local PowerShell 7.x.

[SaschaSchiwy]

Enter: 127.0.0.1:0.0 to Override X11 display

[jdrch]

Enter: 127.0.0.1:0.0 to Override X11 display

@SaschaSchiwy Where in the Settings should this be done?

[SaschaSchiwy]

using xming

[jdrch]

using xming

Thanks! On 1 hand I like MobaXterm on Windows as at least with it I have only 1 app to maintain - since I run Windows Terminal Preview anyway. With Tabby I have 2 (Tabby + the X server). OTOH Tabby might replace Asbru Connection Manager on my Linux machines.

[IoSonoPiero]

Hello, I'm using Tuxedo OS (Ubuntu 22.04), and if I use my terminal to connect to a Ubuntu VM with: ssh -X osboxes@192.168.1.50 when I launch xclock I got this:

When I try to connect with Tabby, I get this:

Using localhost:10.0 in X11 override, I get this:

Any help, please?