We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Issue migrated from trac ticket # 1885
component: client | priority: major | resolution: invalid
Hi all. Some Fedora users report this error (bugzilla ticket) by using xpra-2.3.1 (and with xpra-2.2.6 before): $ xpra start :100 --start-child=xterm xpra initialization error: invalid mode 'start' xpra is compiled with Python-3.6.5 with this configuration and available in the Fedora repositories if you can use it.
Hi all.
Some Fedora users report this error (bugzilla ticket) by using xpra-2.3.1 (and with xpra-2.2.6 before):
$ xpra start :100 --start-child=xterm xpra initialization error: invalid mode 'start'
xpra is compiled with Python-3.6.5 with this configuration and available in the Fedora repositories if you can use it.
The text was updated successfully, but these errors were encountered:
Sorry, something went wrong.
xpra does not fully support python3 yet (see #1568 and #853), you must use a python2 build to run the server for now. You should not provide a build that cannot be used to run a server.
xpra does not fully support python3 yet (see #1568 and #853), you must use a python2 build to run the server for now.
You should not provide a build that cannot be used to run a server.
No branches or pull requests
Issue migrated from trac ticket # 1885
component: client | priority: major | resolution: invalid
2018-06-23 14:27:41: sagitter created the issue
The text was updated successfully, but these errors were encountered: