-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
blue screen with xrdp #962
Comments
Show us the log as well as #952. |
I have the same problem. i get blue screen for some time and get the same error, when i try to connect via microsoft remote desktop.
Here is the xrdp.log file when i try to login. [20171211-10:09:45] [INFO ] starting xrdp with pid 6175 |
@ErencanOzkan Did you see #952? |
@metalefty Yes i see #952 |
Okay, then, can you show me xrdp-sesman.log as well as #952? |
No feed back from the reporter more than 1 month, closing. I'll reopen this when you're back. |
Exactly the same blue screen for me, I am installing from source - branch: devel, commit ae1514c. Follow the instruction from https://github.com/neutrinolabs/xrdp/wiki/Building-on-Debian-8. Attached logs |
as it is already deprecated. x11rdp is complicated to build and very few people using it actually. However, some people still select "X11rdp" session and get stuck despite not installing x11rdp. neutrinolabs#962 (comment) People who really want to use x11rdp should revert this commit.
as it is already deprecated. x11rdp is complicated to build and very few people using it actually. However, some people still select "X11rdp" session and get stuck despite not installing x11rdp. neutrinolabs#962 (comment) People who really want to use x11rdp should revert this commit.
Sorry for necrobumping this old thread, but I'm facing the very same issue on manjaro, tried even with the very latest version of xrdp and xorgxrdp as for today (0.9.13).
xrdp-sesman.log
|
did you find a solution for that ? |
after installing, with all files in right locations, xrdp comes up with a solid blue screen with a window claiming it starts to connect, then it fails and just says, "connection problem, giving up, some problem"
The text was updated successfully, but these errors were encountered: