Re: [winswitch] xpra launcher: connectionn fails with no message
On Thu, 2021-12-16 at 12:10 +0700, Antoine Martin via shifter-users wrote: > Are you also forcing 'ssh' with the launcher? I have put the following line in my xpra.conf, which I believe affects the launcher and CLI application: ssh=ssh -x > As you found out, the bug tracker is a much better place for getting > issues resolved than the mailing list. > > Please make sure to include all the details already requested: full > command lines, etc.. I understand. I thought I would try the mailing list first. I am not familiar with practices within this community, and customs vary about distinctions between seeking support and filing reports, and where to do one or the other. At this point, I am not sure what to put in a bug report. I have no information that seems relevant or procedure that seems reproducible. Frankly, I was hoping that some suggestions available from this inquiry might help me understand how to inspect the problem on my system well enough to have some information useful to report formally. ___ shifter-users mailing list shifter-users@lists.devloop.org.uk https://lists.devloop.org.uk/mailman/listinfo/shifter-users
Re: [winswitch] xpra launcher: connectionn fails with no message
On 15/12/2021 21:35, Eric Levy via shifter-users wrote: Thanks for the suggestions. See my comments, below, please. On Wed, 2021-12-15 at 20:15 +0700, Antoine Martin via shifter-users wrote: There have been a number of bugs reported recently with ssh connections: https://github.com/Xpra-org/xpra/issues/3383 https://github.com/Xpra-org/xpra/issues/3372 https://github.com/Xpra-org/xpra/issues/3330 https://github.com/Xpra-org/xpra/issues/3295 The original report for #3383 was given by me. Presently, I force use of the external command for SSH as a workaround. This solution resolves the problem, as evidenced by my success when invoking from the command line. The problem I am describing now seems to me not part of the issue reported in #3383. Are you also forcing 'ssh' with the launcher? Issue #3295 is in regard to an attempt to connect without a password, and as such, is also not closely related. I am using password authentication, and I have tried enough times that to be clear that a wrong password is not the problem. This is the kind of information that must be included in bug reports, otherwise we're just guessing. In my reply, I already had to guess that you were using ssh. Issue #3300 too seems a poor match. It was reported under Windows, and shows a dialog box with a message about failed authentication. It is also has been reported resolved in the version that I have tested, without success. Issue #3372 is reported a duplicate. As you found out, the bug tracker is a much better place for getting issues resolved than the mailing list. Please make sure to include all the details already requested: full command lines, etc.. Cheers, Antoine Try: xpra launcher --debug ssh The command output will include all ssh connection messages. (I assume that you're using ssh to connect - please include the command lines if that is not the case) The verbose output seems to show nothing rather helpful (see below). I checked the values for protocol, username, and password. As I indicated, of course, I have been successful using the same values in an invocation through command line. --- $ xpra_launcher --debug ssh Gtk-Message: 09:14:00.221: Failed to load module "appmenu-gtk-module" 2021-12-15 09:14:15,840 Xpra GTK3 client version 4.3-r30655 (g1e8a46dce) 64-bit Gtk-Message: 09:14:15.926: Failed to load module "appmenu-gtk-module" 2021-12-15 09:14:15,997 running on Linux Linuxmint 20.2 uma 2021-12-15 09:14:16,004 window manager is 'Mutter (Muffin)' Gtk-Message: 09:14:16.744: Failed to load module "appmenu-gtk-module" 2021-12-15 09:14:16,791 GStreamer version 1.16.2 for Python 3.8.10 64-bit 2021-12-15 09:14:16,871 created unix domain socket '/run/user/1000/xpra/clients/clientname-882690' 2021-12-15 09:14:16,930 No OpenGL_accelerate module loaded: No module named 'OpenGL_accelerate' 2021-12-15 09:14:17,077 Warning: vendor 'Intel' is greylisted, 2021-12-15 09:14:17,077 you may want to turn off OpenGL if you encounter bugs 2021-12-15 09:14:17,157 OpenGL enabled with Mesa Intel(R) Iris(R) Plus Graphics (ICL GT2) 2021-12-15 09:14:17,244 Warning: vendor 'Intel' is greylisted, 2021-12-15 09:14:17,244 you may want to turn off OpenGL if you encounter bugs 2021-12-15 09:14:17,245 OpenGL enabled with Mesa Intel(R) Iris(R) Plus Graphics (ICL GT2) xpra initialization error: cannot find any live servers to connect to 2021-12-15 09:14:17,500 Error: failed to receive anything, not an xpra server? 2021-12-15 09:14:17,501 could also be the wrong protocol, username, password or port 2021-12-15 09:14:17,501 or the session was not found 2021-12-15 09:14:17,513 removing unix domain socket '/run/user/1000/xpra/clients/clientname-882690' ___ shifter-users mailing list shifter-users@lists.devloop.org.uk https://lists.devloop.org.uk/mailman/listinfo/shifter-users
Re: [winswitch] xpra launcher: connectionn fails with no message
Thanks for the suggestions. See my comments, below, please. On Wed, 2021-12-15 at 20:15 +0700, Antoine Martin via shifter-users wrote: > There have been a number of bugs reported recently with ssh > connections: > https://github.com/Xpra-org/xpra/issues/3383 > https://github.com/Xpra-org/xpra/issues/3372 > https://github.com/Xpra-org/xpra/issues/3330 > https://github.com/Xpra-org/xpra/issues/3295 The original report for #3383 was given by me. Presently, I force use of the external command for SSH as a workaround. This solution resolves the problem, as evidenced by my success when invoking from the command line. The problem I am describing now seems to me not part of the issue reported in #3383. Issue #3295 is in regard to an attempt to connect without a password, and as such, is also not closely related. I am using password authentication, and I have tried enough times that to be clear that a wrong password is not the problem. Issue #3300 too seems a poor match. It was reported under Windows, and shows a dialog box with a message about failed authentication. It is also has been reported resolved in the version that I have tested, without success. Issue #3372 is reported a duplicate. > Try: > xpra launcher --debug ssh > The command output will include all ssh connection messages. > (I assume that you're using ssh to connect - please include the > command > lines if that is not the case) > The verbose output seems to show nothing rather helpful (see below). I checked the values for protocol, username, and password. As I indicated, of course, I have been successful using the same values in an invocation through command line. --- $ xpra_launcher --debug ssh Gtk-Message: 09:14:00.221: Failed to load module "appmenu-gtk-module" 2021-12-15 09:14:15,840 Xpra GTK3 client version 4.3-r30655 (g1e8a46dce) 64-bit Gtk-Message: 09:14:15.926: Failed to load module "appmenu-gtk-module" 2021-12-15 09:14:15,997 running on Linux Linuxmint 20.2 uma 2021-12-15 09:14:16,004 window manager is 'Mutter (Muffin)' Gtk-Message: 09:14:16.744: Failed to load module "appmenu-gtk-module" 2021-12-15 09:14:16,791 GStreamer version 1.16.2 for Python 3.8.10 64-bit 2021-12-15 09:14:16,871 created unix domain socket '/run/user/1000/xpra/clients/clientname-882690' 2021-12-15 09:14:16,930 No OpenGL_accelerate module loaded: No module named 'OpenGL_accelerate' 2021-12-15 09:14:17,077 Warning: vendor 'Intel' is greylisted, 2021-12-15 09:14:17,077 you may want to turn off OpenGL if you encounter bugs 2021-12-15 09:14:17,157 OpenGL enabled with Mesa Intel(R) Iris(R) Plus Graphics (ICL GT2) 2021-12-15 09:14:17,244 Warning: vendor 'Intel' is greylisted, 2021-12-15 09:14:17,244 you may want to turn off OpenGL if you encounter bugs 2021-12-15 09:14:17,245 OpenGL enabled with Mesa Intel(R) Iris(R) Plus Graphics (ICL GT2) xpra initialization error: cannot find any live servers to connect to 2021-12-15 09:14:17,500 Error: failed to receive anything, not an xpra server? 2021-12-15 09:14:17,501 could also be the wrong protocol, username, password or port 2021-12-15 09:14:17,501 or the session was not found 2021-12-15 09:14:17,513 removing unix domain socket '/run/user/1000/xpra/clients/clientname-882690' ___ shifter-users mailing list shifter-users@lists.devloop.org.uk https://lists.devloop.org.uk/mailman/listinfo/shifter-users
Re: [winswitch] xpra launcher: connectionn fails with no message
On 13/12/2021 19:10, Eric Levy via shifter-users wrote: Hello. I am running Linux Mint 20.2 on both a server and client system, with Xpra versions 4.2.3-r12 (server) and xpra v4.3-r30655 (g1e8a46dce) (client). I have also tried the 4.2.3 release on the client, with no noticeable difference respecting my problem. There have been a number of bugs reported recently with ssh connections: https://github.com/Xpra-org/xpra/issues/3383 https://github.com/Xpra-org/xpra/issues/3372 https://github.com/Xpra-org/xpra/issues/3330 https://github.com/Xpra-org/xpra/issues/3295 Perhaps it is one of those? I would have expected the 4.3-r30655 client to include this fix though. Until recently, I could connect either through the graphical launcher or the command-line client. However, presently, the laucher invariably fails to connect. No error dialog box appears, or other useful indication of a problem. The connection window simply drops at some point after the password prompt. From the command line, however, the issue does not present. Connection is successful, and I see no worrisome messages among the console output. Previously, both methods had worked. Recently, the server was restored from backup, to a different VM in the same hypervisor. The only difference might be certain unique identifiers, such as MAC address or disk partition UUIDs. I cannot find any log files that might help discover a problem reported by the graphical launcher client. I have looked in ~/.xpra and ~/.settings/xpra on both server and client. Try: xpra launcher --debug ssh The command output will include all ssh connection messages. (I assume that you're using ssh to connect - please include the command lines if that is not the case) Where might I look for an indication of the source of the problem? What suggestions might anyone offer to resolve? I would try the command line above whilst keeping an eye on your server's ssh log file. Cheers, Antoine Thank you for your help. ___ shifter-users mailing list shifter-users@lists.devloop.org.uk https://lists.devloop.org.uk/mailman/listinfo/shifter-users
