-
-
Notifications
You must be signed in to change notification settings - Fork 169
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
Update from xpra 3.1.3 to 3.1.4 breaks html5 on Centos 7 #3885
Comments
As per your log:
Please fix this system file and try again. Please also specify the exact version of the |
This Non-ASCII Character Syntax Error is only a side effect. I tried to install manually the missed xdg with pip2 install xdg. Vut this was not a help. A working installation with xpra 3.1.3 shows also this Syntax Error message:
|
There are many other worrying errors in your server log, which makes me think that this installation was not done correctly. |
I don't see any obvious html5 related fixes in the commit log, but I cannot reproduce this problem with the 3.1.5 beta from: https://xpra.org/beta/CentOS/7/ Please try this version first. |
the whole str==bytes fiasco makes it impossible for the receiver to correctly distinguish binary data from strings
Found the problem, not sure why I didn't see it before that. The commit above fixes that by not using |
This also uncovered some undesired behaviour in the html5 client:
That's improved in Xpra-org/xpra-html5@a67f925 |
Many Thanks! Many Thanks!
|
Describe the bug
After update from:
https://www.xpra.org/dists/CentOS/7/x86_64/xpra-3.1.3-10.0xpra1.el7.x86_64.rpm
to Version:
xpra-3.1.4-10.32985xpra1.el7.x86_64.rpm
orxpra-3.1.4-10.32985xpra1.el7.x86_64.rpm
the html5 funktion does not work anymore at Centos 7
To Reproduce
Steps to reproduce the behavior:
Browser
http://localhost:8888
5. specific action to trigger the bug
Websocket loading bar stops. No windows manager appears. No html5 Menu appears. Only an xterm appears without focus and without window decoration. No input possible.
Steps to Repair
System Information (please complete the following information):
Additional context
The issue is very well to reproduce with:
** log**
The text was updated successfully, but these errors were encountered: