-
-
Notifications
You must be signed in to change notification settings - Fork 171
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
Issue with starting a new session on xpra #3844
Comments
Your Xvfb is so old that it probably does not support
Where? Mailing list? Ticket?
Those are words, but I don't know what it means. Perhaps a screenshot would help.
What was the error?
Is this 7.9? Or an even more outdated version? |
Thank you for quick reply. I have changed back to the using and the output on running this command is as: Entering daemon mode; any further errors will be reported to:
And When I open this on the browser only the blue screen appears nothing else. For the xpra stop command.
this error appears. Log file for this session == >
Operating system == Linux CentOS Linux 7.9.2009 Core |
Please learn to use markdown, having to edit your tickets to be able to read them is time consuming.
Neither of these strings are valid.
Make sure that you have
Your browser is trying to use |
Thank you for quick reply.
Error: What about this error? |
The cause would be found in your server log |
I am able to resolve the above mentioned Pillow library of the python and closing of the Xpra session. But still facing some issues. Command to run xpra --> I have also created a proxy server, command for creating proxy server--> After running the first command, I am still having only the blue screen is appearing not the xterminal as expected. the log file is:
Please help me with this. Thank you |
You haven't explained all the errors that you've hit before or how you resolved them, which is making it more difficult to help you.
How is this relevant to your blue screen issue?
Is this a typo? Are you connecting using the html5 client? |
Thank you for quick reply. I used the proxy server because you have mentioned that
But even I have tried with the command --> the blue screen was still there no terminal was visible. Below mentioned are the version installed on my system.
As my os is Operating system == I am using one machine which is working for me as server as well as client. sorry but I don't know how to check html5 client or python client. Could you please guide me how to check these things. |
Then instead of using a proxy, configure your server to use SSL.
That won't do it since you are not defining any tcp or ssl sockets.
How did you connect then?
I mean connect with both of them.
Not answered. Does |
Thank you for quick reply.
I even tried for other format but still the same error occured.
No, this is not a type. The memory have something to do with xpra.
I am working on this. |
Well, a system with 376GB of memory is going to be unusual, when that happens there are going to be other things that are unusual.
This should have given you:
So my guess is that
I gave the wrong syntax, try:
|
Thank you for replying.
I tried opening the xterm through command line only without xpra, it is working. The terminal opened instantly.
Shouldn't the last and second last be same as the output you have shared. Question: Does Xpra uses cuda libraries for the GUI? Thank you. |
It depends on the version. 3.x does not. |
Describe the bug
I have just installed Xpra on linux machine. I was trying to start a session of xpra to check if it work and after the command an error showed up.
I have previous contacted you with some error and you have asked me to make changes to the file
/etc/xpra/conf.d/55_server_x11.conf
and remove the comment (#) in front ofxvfb = xvfb
and put comment in front ofxvfb = xdummy
.which is did but which created more issues for me as before changing this I was able to create new session but there was no display on blue background was there on the browser and also I was not able to stop the session with the command
xpra stop
Os details of the server
xpra version details:
xpra v3.1.4-r3M
As this is centos 7 so the xpra version installed on it is older version and I have used yum install xpra command for installation.
I am using the same machine as server and client so details for server and client are same.
To Reproduce
Steps to reproduce the behavior:
xpra start --bind-tcp=0.0.0.0:5905 --html=on --start=xterm
System Information (please complete the following information):
[NAME="CentOS Linux" VERSION="7 (Core)"]
[NAME="CentOS Linux" VERSION="7 (Core)"]
xpra v3.1.4-r3M
xpra v3.1.4-r3M
Additional context
Add any other context about the problem here.
Please see "reporting bugs" in the wiki section.
The text was updated successfully, but these errors were encountered: