Bitvise SSH Client not able to open Remote Desktop

Asked by Peter Sotos

*hrumph*

Bitvise xterm SSH Client not able to open Remote Desktop. All that happens when I try to Remote Desktop connect is that I get a shell as I would when I normally use Bitvise in terminal mode. When I do an startx from the bitvise SSHed in terminal, it launches the Desktop on the linux box (I can see the monitor from my PC station). LOL

I tried this:
The problem is with debian default setup. It sets it up so that only root can log into X. In order to change this you need to edit the /etc/X11/Xwrapper.config file. For the syntax of that, check out the man page for 'Xwrapper.config'. All you need to add is the 'allowed_users=anybody' option.

I also tried this:

sudo stop lightdm (or kdm or gdm instead if you installed kubuntu or GNOME shell)
sudo Xorg -configure
sudo start lightdm (or kdm or gdm instead if you installed kubuntu or GNOME shell)

I have some more info:
I see these errors in the Bitvise command window:
02:28:57.906 Auto opening xterm terminal session.
02:28:57.906 Auto opening Remote Desktop session.
02:28:57.911 Listening for Remote Desktop client-2-server connection on 127.0.0.1:19593 succeeded.
02:28:57.914 Remote Desktop Connection launched successfully.
02:29:05.899 Accepted Remote Desktop client-2-server connection from 127.0.0.1:64857 to 127.0.0.1:3389.
02:29:05.901 Server rejected our attempt to open a Remote Desktop client-2-server connection - reason: SSH_OPEN_CONNECT_FAILED, description: Connection refused.
02:29:05.906 Closing Remote Desktop client-2-server connection from 127.0.0.1:64857 to 127.0.0.1:3389, sent: 0, received: 0.
02:29:34.864 Closing xterm terminal session.
--------------------------------------
I have made progress! I am able to login via XMing I get single windows but no Desktop client. I think I was successful with XMing because I specified Display "1" instead o "0". There is no such setting in bitvice. I would REALLY like to see the entire desktop. Anyway, I KNOW there is an X11 guru on here! Want to help me solve this challenge? I am close!

----------------

New update:
I am getting this from Bitvise:
Xming :0 -clipboard

XdmcpRegisterConnection: newAddress 10.0.x.xx
winCheckDisplayNumber - Xming is already running on display 0

Fatal server error:
InitOutput - Duplicate invocation on display number: 0. Exiting.

winDeinitMultiWindowWM - Noting shutdown in progress
-------------------------------
Another update:
Here is a view of my Xming widow. I am getting something just missing the rest of the desktop. I am launching a single program xterm, and then launching graphical apps from there but I am missing the whol desktop background and docking bar. I think I am close, please help! So tired! I have been working on this thing since yesterday.
http://fireballmm.com/X11_launching_problem.png
http://fireballmm.com/MissingFont.png

Again any help is much appreciated!

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Peter Sotos
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

Debian has root SSH connections allowed. You can configure it to not allow root SSH connections using /etc/ssh/sshd_config.conf

Why do you want the full desktop?
What are you planning to run in the remote desktop session?
Can you run individual applications in the SSH session?
Did you try PuTTY and enable the X forwarding feature (You seem to have Xming installed and running which is good)

Thanks

Revision history for this message
Peter Sotos (psotos) said :
#2

I am going to use the desktop to develop software. I want it to run my development environment.

I can run normal commands in the SSH session. I guess I don't exactly understand your question. When I use Bitvise I get a normal terminal and I can run regular command line thing in it. When I try to run GUI stuff it loads on the remote box and does not spawn any kind of XClient. When I use the XLauch, I can then run a terminal in the graphical mode and spam individual apps, but they are messed up with no real title bar. You can see from the screenshot how messed up it is.

I have not tried putty but Bitvise is supposed to support it so I suspect its not a tool problem but a settings problem. It's a perfectly valid SSH client. Bitvise also has an X FOrwarding feature and I have tried to enable that and its failed as well. Bitvise in no way works. Only the XLaunch works but again poorly.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#3

Install PuTTY and run it then allow X forwarding in PuTTY, Launch your GUI app from the terminal (Not the X server) and it will show on the client side.

On the server, what is the output of:

uname -a; cat /etc/issue

Thanks

Revision history for this message
Peter Sotos (psotos) said :
#4

Here is the responses that I got to the command and attempting to launch a graphical application (obviously I have scrubbed sensative information from the response):

Using username "xxxxxx".
xxxxxx@10.0.1.51's password:
Welcome to Ubuntu 12.04.3 LTS (GNU/Linux 3.8.0-29-generic x86_64)

 * Documentation: https://help.ubuntu.com/

  System information as of Sun Sep 1 23:56:09 MST 2013

  System load: 0.0 Processes: 201
  Usage of /: 0.5% of 908.92GB Users logged in: 1
  Memory usage: 6% IP address for eth0: 10.0.xx.xx
  Swap usage: 0%

  Graph this data and manage this system at https://landscape.canonical.com/

Last login: Sun Sep 1 12:43:23 2013 from xxxxxxxx.local
xxxxxx@xxxxxx:~$ uname -a; cat /etc/issue
Linux xxxxxx 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14 16:19:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Ubuntu 12.04.3 LTS \n \l

xxxxxx@xxxxxx:~$ Linux xxxxxx 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14 16:19:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
No command 'Linux' found, did you mean:
 Command 'linux' from package 'user-mode-linux' (universe)
Linux: command not found
xxxxxx@xxxxxx:~$ Ubuntu 12.04.3 LTS \n \l
Ubuntu: command not found
xxxxxx@xxxxxx:~$ ^C
xxxxxx@xxxxxx:~$ eclipse &
[1] 4250
xxxxxx@xxxxxx:~$ Eclipse: Cannot open display:

** (java:4251): WARNING **: Command line `dbus-launch --autolaunch=0b44f990cc49a5f5303fcdf800000497 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n
Eclipse: Cannot open display:
Eclipse:
An error has occurred. See the log file
/home/xxxxxx/.eclipse/org.eclipse.platform_4.3.0_1473617060_linux_gtk_x86_64/configuration/1378105052453.log.
^C
[1]+ Exit 13 eclipse
xxxxxx@xxxxxx:~$

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#5

archive.openflow.org/wk/images/5/5a/Putty_x11_fwding.PNG

Be sure that Xming is running before you connect.

Revision history for this message
Peter Sotos (psotos) said :
#6

Still failing.

BTW, thank you VERY MUCH for your help in this!

login as: xxxxxx
xxxxxx@10.0.xx.xx's password:
Welcome to Ubuntu 12.04.3 LTS (GNU/Linux 3.8.0-29-generic x86_64)

 * Documentation: https://help.ubuntu.com/

  System information as of Mon Sep 2 00:15:08 MST 2013

  System load: 0.0 Processes: 201
  Usage of /: 0.5% of 908.92GB Users logged in: 1
  Memory usage: 8% IP address for eth0: 10.0.1.51
  Swap usage: 0%

  Graph this data and manage this system at https://landscape.canonical.com/

Last login: Sun Sep 1 23:56:09 2013 from user-pc.local
xxxxxx@xxxxxx:~$ eclipse
Eclipse: Cannot open display:

** (java:4660): WARNING **: Command line `dbus-launch --autolaunch=0b44f990cc49a5f5303fcdf800000497 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n
Eclipse: Cannot open display:
Eclipse:
An error has occurred. See the log file
/home/xxxxxx/.eclipse/org.eclipse.platform_4.3.0_1473617060_linux_gtk_x86_64/configuration/1378106113916.log.
xxxxxx@xxxxxx:~$ xxxxxx@xxxxxx:~$ eclipse
xxxxxx@xxxxxx:~$: command not found
xxxxxx@xxxxxx:~$ Eclipse: Cannot open display:
Eclipse:: command not found
xxxxxx@xxxxxx:~$
xxxxxx@xxxxxx:~$ ** (java:4660): WARNING **: Command line `dbus-launch --autolaunch=0b44f990cc49a5f5303fcdf800000497 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n
-bash: syntax error near unexpected token `java:4660'
xxxxxx@xxxxxx:~$ Eclipse: Cannot open display:
Eclipse:: command not found
xxxxxx@xxxxxx:~$ Eclipse:
Eclipse:: command not found
xxxxxx@xxxxxx:~$ An error has occurred. See the log file
An: command not found
xxxxxx@xxxxxx:~$ /home/xxxxxx/.eclipse/org.eclipse.platform_4.3.0_1473617060_linux_gtk_x86_64/configuration/1378106113916.log.
-bash: /home/xxxxxx/.eclipse/org.eclipse.platform_4.3.0_1473617060_linux_gtk_x86_64/configuration/1378106113916.log.: No such file or directory
xxxxxx@xxxxxx:~$

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#7

Is Xming running when you launched PuTTY?

Revision history for this message
Peter Sotos (psotos) said :
#8

Yes Sir!

I see a little X in my taskbar.

Welcome to the Xming X Server
Vendor: Colin Harrison
Release: 6.9.0.31
FreeType2: 2.3.4
Contact: http://sourceforge.net/forum/?group_id=156984

C:\Program Files (x86)\Xming\Xming.exe :0 -clipboard
 -multiwindow

XdmcpRegisterConnection: newAddress 10.0.1.52
winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel
winAllocateFBShadowGDI - Creating DIB with width: 3840 height: 1200 depth: 32
winAllocateFBShadowGDI - Requested DIB (bitmap) will be larger than 16 MB. The surface may fail to be allocated on Windows 95, 98, or Me, due to a 16 MB limit in DIB size. This limit does not apply to Windows NT/2000, and this message may be ignored on those platforms.
winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32
glWinInitVisuals:1596: glWinInitVisuals
glWinInitVisualConfigs:1503: glWinInitVisualConfigs glWinSetVisualConfigs:1581: glWinSetVisualConfigs
init_visuals:1055: init_visuals
null screen fn ReparentWindow
null screen fn RestackWindow
InitQueue - Calling pthread_mutex_init
InitQueue - pthread_mutex_init returned
InitQueue - Calling pthread_cond_init
InitQueue - pthread_cond_init returned
winInitMultiWindowWM - Hello
winInitMultiWindowWM - Calling pthread_mutex_lock ()
winMultiWindowXMsgProc - Hello
winMultiWindowXMsgProc - Calling pthread_mutex_lock ()
glWinScreenProbe:1390: glWinScreenProbe
fixup_visuals:1303: fixup_visuals
init_screen_visuals:1336: init_screen_visuals
(--) 16 mouse buttons found
(--) Setting autorepeat to delay=500, rate=31
(--) winConfigKeyboard - Layout: "00000409" (00000409)
(--) Using preset keyboard for "English (USA)" (409), type "4"
(WW) Couldn't load XKB keymap, falling back to pre-XKB keymap
Could not init font path element C:\Program Files (x86)\Xming/fonts/misc/, removing from list!
Could not init font path element C:\Program Files (x86)\Xming/fonts/TTF/, removing from list!
Could not init font path element C:\Program Files (x86)\Xming/fonts/Type1/, removing from list!
Could not init font path element C:\Program Files (x86)\Xming/fonts/75dpi/, removing from list!
Could not init font path element C:\Program Files (x86)\Xming/fonts/100dpi/, removing from list!
Could not init font path element C:\Program Files\Xming\fonts\dejavu, removing from list!
Could not init font path element C:\Program Files\Xming\fonts\cyrillic, removing from list!
Could not init font path element C:\WINDOWS\Fonts, removing from list!
winInitMultiWindowWM - pthread_mutex_lock () returned.
winInitMultiWindowWM - pthread_mutex_unlock () returned.
winMultiWindowXMsgProc - pthread_mutex_lock () returned.
winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0
winMultiWindowXMsgProc - pthread_mutex_unlock () returned.
winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0
winProcEstablishConnection - Hello
winInitClipboard ()
winProcEstablishConnection - winInitClipboard returned.
winClipboardProc - Hello
DetectUnicodeSupport - Windows Vista
winClipboardProc - DISPLAY=127.0.0.1:0.0
winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display.
winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display.
winClipboardProc - XOpenDisplay () returned and successfully opened the display.

Revision history for this message
Peter Sotos (psotos) said :
#9

Tried launching gedit too

xxxxx@xxxxxx:~$ gedit

** (gedit:4739): WARNING **: Command line `dbus-launch --autolaunch=0b44f990cc49a5f5303fcdf800000497 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n
Cannot open display:
Run 'gedit --help' to see a full list of available command line options.

Revision history for this message
Peter Sotos (psotos) said :
#10

Ahha!

I was putting 127.0.0.1 instead of 127.0.0.1:0.0

DOH!

Though I DID do that for bitvise and it still failed. So hey next question how do I get the thing to show me a window with a desktop? :D

Peter

Revision history for this message
Peter Sotos (psotos) said :
#11

Thanks for your help Andrew! Most appreciated!

- Peter

Revision history for this message
Alif M. Ahmad (alivema4ever) said :
#12

@Peter: Don't forget to enable X11 forwarding on Bitvise SSH option
Under Terminal tab, find X11 forwarding. Check at the box. Re-login to test the result.

Be sure to start Xming before logging in and add Xming as allowed program on Windows Firewall for both incoming & outgoing connection.