Closed djust-uzh closed 1 year ago
xpra initialization error: mode 'seamless' not found in command line arguments
That's a re-connection bug. Will fix.
.. but I cannot produce a log output on Windows (-d all does not output to cmd)
Use Xpra_cmd.exe
to see the command output.
Or locate the client log file in %APPDATA%
.
Thank you very much!
If it helps, here are the ends of a couple of client logs.
2023-08-25 10:39:44,232 running
2023-08-25 10:42:42,599 Connection lost
CONNECTION_LOST, reconnecting
2023-08-25 10:42:43,307 xpra initialization error:
mode 'seamless' not found in command line arguments
In the following log, a new session was started soon after the previous session was successfully shut down, and it crashed without the seamless
error. Re-attaching was successful.
2023-08-25 10:44:43,043 running
2023-08-25 10:44:51,270 UI thread is now blocked
UI thread is now blocked
Depending on how long this lasts, this can be the source of the problem. It means that xpra's main thread doesn't get a chance to run - for whatever reason, this can eventually cause the connection to drop if the server decides that the client is unresponsive.
@djust-uzh the commit above should fix this (untested but looks correct). There are updated MS Windows builds here: https://xpra.org/beta/windows/
Unfortunately, the fix did not succeed. I still get the error with the beta version on the client (Xpra-x86_64_6.0-r34116).
2023-08-25 16:02:52,161 running
2023-08-25 16:11:23,306 Connection lost
CONNECTION_LOST, reconnecting
2023-08-25 16:11:23,986 xpra initialization error:
mode 'seamless' not found in command line arguments
I assume I don't have to update the server also. Let me know, if I can be of further help.
Sorry about that, I fat fingered the fix. Please try again with r34119 or later. Only the client needs updating.
I'm sorry to bother you again, but now I get
2023-08-25 16:48:25,352 running
2023-08-25 16:50:45,039 Connection lost
CONNECTION_LOST, reconnecting
2023-08-25 16:50:45,709 xpra initialization error:
mode 'seamless' not found in command line arguments ['xpra_cmd', 'start', 'ssl://[user]@[host]:[port]', '--ssl-server-verify-mode=none', '--no-microphone', '--no-speaker', '--no-webcam', '--no-printing', '--pulseaudio=no', '--start-child=rstudio']
with r34119. Re-attaching works.
Sorry about that. It was sloppy, I should really have tested this code before pushing it.
Now done more correctly in b2af51582f8c4c45947b686b634f75dc972b3fc2. This commit includes a unit test that re-uses the arguments you supplied. So it should also work for you and we will notice if it breaks in the future. Try r34120 or later. This will be included in the 5.0.1 release.
Describe the bug I have a xpra proxy server running as a daemon on Ubuntu Jammy accepting connections over ssl. I can successfully connect to the server with various clients (Windows, macOS) and run programs. At some point the client crashes with the error dialog
xpra initialization error: mode 'seamless' not found in command line arguments
. The time frame of the crash varies. I've had sessions run as short as 30 seconds and as long as 30 minutes. The session on the server remains active and can be attached to successfully after the client crash.The disconnects did not happen with older versions on the server, probably 4.4.3 but not sure which version.
To Reproduce Steps to reproduce the behavior:
xpra.service
(port has been replaced with [port]):xpra start ssl://[user]@[server]:[port] --ssl-server-verify-mode=none --microphone=no --speaker=no --webcam=no --printing=no
System Information (please complete the following information):
Additional context
This is probably a problem on the client side, but I cannot produce a log output on Windows (
-d all
does not output to cmd).server.log
[sanitized]