[winswitch] How to increment start timeout?

[Antoine Martin]

> 2020-12-17 09:52:04,760 cannot access python uinput module:
(..)
8 seconds to start the X11 server, slow.
You may want to switch to Xvfb and see if that starts faster for you.
See /etc/xpra/conf.d/55_server_x11.conf on the server.
> 2020-12-17 09:52:12,137 cannot create group socket '/run/xpra/11C82-0'
(..)
Then 4 more seconds for xpra itself - which isn't great but acceptable:
> 2020-12-17 09:52:16,001 xpra is ready.
(..)
> 2020-12-17 09:52:16,940 Handshake complete; enabling connection
(..)
> 2020-12-17 09:52:17,082 New unix-domain connection received
> 2020-12-17 09:52:17,082  on '/run/user/1000/xpra/11C82-0'
> 2020-12-17 09:52:17,398  uid=1000 (manganelll), gid=1000 (manganelll)
> 2020-12-17 09:52:17,398  running with pid 11622 on Linux Fedora 33
> ThirtyThree
Though it takes another 7 seconds before the client is ready.
Not quite sure what went on during that time - it could be related to
this bug:
https://xpra.org/trac/ticket/2978#comment:14
You may want to try the latest beta, apply the environment variable
workaround on the server, or use "--start-new-commands=no".
> 2020-12-17 09:52:24,559 Python/GTK3 Linux Neon 20.04 focal x11 client
> version 4.0.5-r27999 64-bit(..)

So that took 20 seconds from start to finish - which is on the slow
side, but this did not fail. (the timeout is longer than that IIRC)
Do you have a log of when it does fail and timeout?

FWIW: on my somewhat old system, it takes 6 seconds to get a window up:
$ xpra start ssh://localhost/ --start=xterm
2020-12-17 19:27:20,296 Xpra GTK3 client version 4.1-r28171M 64-bit
(..)
2020-12-17 19:27:26,177 Xpra GTK3 X11 server version 4.1-r28171 64-bit
2020-12-17 19:27:26,177  running on Linux Fedora 31 ThirtyOne

Cheers,
Antoine