Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

xpra ssh mode cannot connect from mac gui launcher #1281

Closed
totaam opened this issue Aug 10, 2016 · 34 comments
Closed

xpra ssh mode cannot connect from mac gui launcher #1281

totaam opened this issue Aug 10, 2016 · 34 comments

Comments

@totaam
Copy link
Collaborator

totaam commented Aug 10, 2016

Issue migrated from trac ticket # 1281

component: client | priority: major | resolution: worksforme

2016-08-10 10:04:58: davide created the issue


I have a Ubuntu server running a session on Display :30

I can connect/disconnect from it remotely and even locally on my mac through ssh -X (which defeats the point).

However, whenever I try the xpra launcher with all the right settings, I just get the red 'Connection lost' with no explanation. Also, there is no documentation.

Maybe if I had the command-line version of xpra I could try
attach but I can't find it for MAC. This could be really good, but as is, it is unusable. Such a shame...

@totaam
Copy link
Collaborator Author

totaam commented Aug 10, 2016

2016-08-10 11:00:33: antoine changed owner from antoine to davide

@totaam
Copy link
Collaborator Author

totaam commented Aug 10, 2016

2016-08-10 11:00:33: antoine commented


What version are you using?
What mode are you using to try to connect?
What commands lines are you using to start xpra? Does it work if you connect from Ubuntu?
etc.. for more guidelines, see ReportingBugs.

Xpra is used every day on macs.

The Xpra executable will be on your path if you use the PKG installer, otherwise it will be found in Xpra.app/Contents/Helpers/Xpra

Finally, there is tons of documentation, here on this wiki and via the xpra man page.

@totaam
Copy link
Collaborator Author

totaam commented Aug 10, 2016

2016-08-10 11:10:27: davide uploaded file Screen Shot 2016-08-10 at 11.02.16.png (771.1 KiB)

Screen Shot 2016-08-10 at 11.02.16.png

@totaam
Copy link
Collaborator Author

totaam commented Aug 10, 2016

2016-08-10 11:14:14: antoine changed status from new to closed

@totaam
Copy link
Collaborator Author

totaam commented Aug 10, 2016

2016-08-10 11:14:14: antoine set resolution to duplicate

@totaam
Copy link
Collaborator Author

totaam commented Aug 10, 2016

2016-08-10 11:14:14: antoine commented


So you're using SSH mode, you may want to try the latest beta osx builds which include a fix for ssh mode.
Or use ssh keys.

See #1240

@totaam
Copy link
Collaborator Author

totaam commented Aug 10, 2016

2016-08-10 11:18:00: antoine changed title from xpra doesn't work on mac to xpra ssh mode cannot connect from mac gui launcher

@totaam
Copy link
Collaborator Author

totaam commented Aug 10, 2016

2016-08-10 11:37:48: antoine commented


See #1240#comment:7

@totaam
Copy link
Collaborator Author

totaam commented Aug 10, 2016

2016-08-10 12:22:41: davide changed status from closed to reopened

@totaam
Copy link
Collaborator Author

totaam commented Aug 10, 2016

2016-08-10 12:22:41: davide removed resolution (was duplicate)

@totaam
Copy link
Collaborator Author

totaam commented Aug 10, 2016

2016-08-10 12:22:41: davide commented


The Beta version still doesn't work with my El Capitan.

I tried at commandline

./Xpra ssh:username@ipaddress:display

and got the error

xpra: error: invalid mode 'initenv'

@totaam
Copy link
Collaborator Author

totaam commented Aug 10, 2016

2016-08-10 12:25:08: antoine changed status from reopened to closed

@totaam
Copy link
Collaborator Author

totaam commented Aug 10, 2016

2016-08-10 12:25:08: antoine set resolution to invalid

@totaam
Copy link
Collaborator Author

totaam commented Aug 10, 2016

2016-08-10 12:25:08: antoine commented


Had you replied to my questions in comment:1, which I have now repeated numerous times, we would all have saved a lot of time.
Your xpra version on the server is too old. More details here: Versions


Also, please always include the exact command you typed (cut&pasting them), the ones from comment:5 are made up, and wrong.

@totaam
Copy link
Collaborator Author

totaam commented Aug 10, 2016

2016-08-10 13:47:53: davide changed status from closed to reopened

@totaam
Copy link
Collaborator Author

totaam commented Aug 10, 2016

2016-08-10 13:47:53: davide removed resolution (was invalid)

@totaam
Copy link
Collaborator Author

totaam commented Aug 10, 2016

2016-08-10 13:47:53: davide commented


It is true the previous server was old.

However I just tried the beta version with an xpra session on a
brand new server and got the error

'server requested disconnect: login timeout

[El Capitan trying to connect to current Ubuntu]

@totaam
Copy link
Collaborator Author

totaam commented Aug 10, 2016

2016-08-10 14:00:31: davide commented


I tried connecting through ssh -X on this server and got lots of libGL errors

libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
The program 'Xpra' received an X Window System error.
This probably reflects a bug in the program.
The error was 'GLXBadContext'.
  (Details: serial 261 error_code 160 request_code 150 minor_code 6)
  (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 --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

@totaam
Copy link
Collaborator Author

totaam commented Aug 11, 2016

2016-08-11 13:22:43: antoine changed status from reopened to new

@totaam
Copy link
Collaborator Author

totaam commented Aug 11, 2016

2016-08-11 13:22:43: antoine commented


opengl has nothing to do with your problem, no idea what "I tried connecting through ssh -X" means since you're still not including the actual commands you used.

Try with the latest beta, which will allow you to disable ssh host key checking. Maybe you never connected to that SSH server before and SSH strict host key checking is enabled but without support for GUI confirmation.


Here's what a proper debugging information looks like:

  • server
$ echo $USER
test
$ rpm -qa xpra
xpra-1.0-0.20160811r13304.fc24.x86_64
$ xpra start --start=xterm --bind-tcp=0.0.0.0:10000 :100

(and keep an eye on your server log)

  • osx client from GUI:
open Desktop/Xpra-1.0-[r13304](../commit/85b1c6e26feb7276243ccaf0ac3184da3970a079).dmg
open /Volumes/Xpra/Xpra.app
  • osx client from command line:
open Desktop/Xpra-1.0-[r13304](../commit/85b1c6e26feb7276243ccaf0ac3184da3970a079).dmg
/Volumes/Xpra/Xpra.app/Contents/Helpers/Xpra attach ssh/test:testpassword@HOST/100

(you can omit the display part if you have a single server session running)

Unless you can provide similar details showing your exact problem, in particular any output or error messages, I will close this bug.

@totaam
Copy link
Collaborator Author

totaam commented Aug 14, 2016

2016-08-14 00:38:29: davide commented


OK I will try tomorrow

@totaam
Copy link
Collaborator Author

totaam commented Aug 14, 2016

2016-08-14 18:38:15: davide uploaded file xpra_bug_report_20160814.zip (521.2 KiB)

@totaam
Copy link
Collaborator Author

totaam commented Aug 15, 2016

2016-08-15 04:45:50: antoine commented


Info still missing. How many times can I ask for the same thing? This will be the last.
See comment:1 and #1240#comment:9, comment:9 right above for an example.

@totaam
Copy link
Collaborator Author

totaam commented Aug 15, 2016

2016-08-15 09:08:06: davide uploaded file Screen Shot 2016-08-15 at 09.06.39.png (821.4 KiB)

Attempt from Ubuntu to Ubuntu
Screen Shot 2016-08-15 at 09.06.39.png

@totaam
Copy link
Collaborator Author

totaam commented Aug 15, 2016

2016-08-15 09:14:25: davide commented


OK - I tried your suggestion to test whether Ubuntu would connect,
and the answer was 'no' for the new server. [see attachment 3]

I had tested the old server [Ubuntu 10.2] for the same thing and it had worked. I hadn't checked the new one for this
but it appears this could be the issue - that the current version of Xpra
is not compatible with Ubuntu 16 without further tweaking.

@totaam
Copy link
Collaborator Author

totaam commented Aug 15, 2016

2016-08-15 10:23:13: antoine changed status from new to closed

@totaam
Copy link
Collaborator Author

totaam commented Aug 15, 2016

2016-08-15 10:23:13: antoine set resolution to needinfo

@totaam
Copy link
Collaborator Author

totaam commented Aug 15, 2016

2016-08-15 10:23:13: antoine commented


The current version of xpra for Ubuntu xenial is 0.17.4, more details here: Versions - same as comment:6.
Details as per comment:9 are still missing too, so I'm done.

@totaam
Copy link
Collaborator Author

totaam commented Mar 1, 2017

2017-03-01 20:56:25: ackalker commented


Dear Antoine,

Please, could you drop the condescending tone, get some sleep, whatever. Not all users of Xpra are professional bug reporters, or even have any experience in reporting problems.

I think I'm having a similar problem to DavidE: I'm unable connect to a Linux server using the GUI part of Xpra for Mac OS.

I'm attaching a zip file which was saved after clicking the "Bug Report" icon in the Xpra GUI.

@totaam
Copy link
Collaborator Author

totaam commented Mar 1, 2017

2017-03-01 20:57:08: ackalker changed status from closed to reopened

@totaam
Copy link
Collaborator Author

totaam commented Mar 1, 2017

2017-03-01 20:57:08: ackalker removed resolution (was needinfo)

@totaam
Copy link
Collaborator Author

totaam commented Mar 1, 2017

2017-03-01 21:40:40: ackalker commented


Tried to repro just to be absolutely sure but I was unable to. There was a problem with the connection between the Mac client and Linux server, unrelated to Xpra.
After fixing this, both commandline xpra attach and the GUI worked well.

It would have been nice if the error message reported by the GUI had been more indicative of the root cause of the problem.

@totaam
Copy link
Collaborator Author

totaam commented Mar 1, 2017

2017-03-01 21:42:20: ackalker changed status from reopened to closed

@totaam
Copy link
Collaborator Author

totaam commented Mar 1, 2017

2017-03-01 21:42:20: ackalker set resolution to worksforme

@totaam totaam closed this as completed Mar 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant