Cbh31 at 21:05, 4 August 2020

2020-08-04T21:05:41Z

← Older revision		Revision as of 21:05, 4 August 2020
Line 38:		Line 38:

	<pre>		<pre>
	xpra attach ssh:myworkstation.ch.private.cam.ac.uk:1		xpra attach ssh:myworkstation.ch.private.cam.ac.uk:1 --ssh="ssh -l <username>"
	</pre>		</pre>

Ajwt3: Created page with "Notes from the COS Have you encountered xpra? It is basically "screen for X". I'd strongly advise using it since you'd be able to attach/detach your vmd window from anywhere:..."

2018-03-14T10:55:19Z

Created page with "Notes from the COS Have you encountered xpra? It is basically "screen for X". I'd strongly advise using it since you'd be able to attach/detach your vmd window from anywhere:..."

New page

Notes from the COS

Have you encountered xpra? It is basically "screen for X". I'd strongly advise using it since you'd be able to attach/detach your vmd window from anywhere:

You need it on both your client machine and the server. It should "just work" if your machine isn't using the nvidia GL libraries.

xpra start ssh:$REMOTEHOSTNAME:100 --start-child=/usr/local/shared/vmd/1.9.2/64/bin/vmd

More info here:

http://xpra.org/trac/wiki/Usage

Obsidian has the nvidia GL libraries, and you can't easily seem to use these to render on xdummy or xvfb. Also, nvidia brings in the xserver-xorg-legacy package, which provides a wrapper around Xorg, which in turn breaks other things. ( https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-dummy/+bug/1589447 ) xpra seems to want to use Xorg instead of Xvfb for some reason as well.

OK... so basically, you want to run vmd over ssh somewhere else that is running with nvidia libgl stuff. So, if this works, you can probably write a short shell script or some such to launch the "xpra daemon":

On your workstation:
<pre>
sudo apt-get install xvfb xpra
</pre>

This should start things with the mesa libraries instead of the nvidia ones.

<pre>
xpra start --xvfb 'env LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/mesa: Xvfb +extension GLX -screen 0 3840x2560x24+32 -nolisten tcp -noreset'
</pre>

This should say something like Actual log file name is now: /home/$USER/.xpra/:1.log . It should be listening on :1 then (if not, substitute). You can attach, detach, whatever... kind of like screen (RTM).

You can now do things in your ssh session on your workstation like:

<pre>
export DISPLAY=:1
LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/mesa: vmd
</pre>

Which should launch vmd on :1. You can attach the session from your client computer:

<pre>
xpra attach ssh:myworkstation.ch.private.cam.ac.uk:1
</pre>

then you should magically see vmd spring into life. Other things you may find useful are:

<pre>
xpra list
xpra stop :1
</pre>

Xpra - Revision history

Cbh31 at 21:05, 4 August 2020

Ajwt3: Created page with "Notes from the COS Have you encountered xpra? It is basically "screen for X". I'd strongly advise using it since you'd be able to attach/detach your vmd window from anywhere:..."