> Thanks, I've updated the man page:
> https://www.xpra.org/trac/changeset/1995
>
Thank you.
> > At the moment one can tell that remote Xpra session do not exist only
> > from prior experience (which I'm lacking as well because I usually
> > connect to session that is running). As you can see the attempt to
> > connect to non-
> >
> > existent session gives two errors:
> > bash: .xpra/run-xpra: No such file or directory
> >
> > cannot write using ['ssh', '-T', 'HOST']:
> > the SSH process has terminated with exit code=127
> >
> > neither of which is clear about the real issue (cause).
>
> I will try to do something about that.
>
That would a valuable improvement, thank you.
Simplest thing to do might be just to print an additional message
"Hint: session is not running?"
or
"Can't attach to running session."
or similar after in order to provide a clue/suggestion where the problem might
be.
Regards,
Dmitry.
_______________________________________________
shifter-users mailing list
[email protected]
http://lists.devloop.org.uk/mailman/listinfo/shifter-users
