-
Notifications
You must be signed in to change notification settings - Fork 44
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
New version xRDP & GCC error #17
Comments
Can you give me steps to reproduce your GCC issue? Purging and reinstalling - What do you specifically mean when you did this? "xRDP has stops with both the versions after a specific number of logins" - Can you provide steps to reproduce? I need more specific info to assist. None of these issues make sense or are things I have run into, using kWSL daily and extensively. |
Also need to confirm you selected a different port for xRDP when you installed a new instance. |
I actually uninstalled the last instance due to the xRDP error. The new instance connected to xRDP fine itself. The xRDP error can't be replicated in any way I know of. It just comes up after I have shutdown WSL too many times without running As for GCC in the new instance, you can probably replicate it (given it is a non defunct bug) by just trying to compile a C file, or with |
If you're seeing this xRDP error then Instead try Regarding your GCC issue, can you try rebuilding an Ubuntu/Neon package to verify your environment is ok? Sounds like you don't have the necessary development tools installed:
|
This might be a WSL2 issue as well. Can you try running the instance in WSL1 first and see if the issue persists? It shouldn't, because there's a logout script in KDE that shuts down WSL completely so new sessions are 'clean' |
The development tools installation worked. Not sure why I needed it, since I've always been able to compile right off the bat on previous versions and other distros.
What do you mean by a logout script? (When I said I shutdown without (Also, And finally, no matter what precautions exist- if i do face this problem again, how do I really solve it? Increasing the max sessions does not work, purging and reinstalling xrdp does not work either. |
When you click "Log Out" in KDE a script is kicked-off that ends the RDP session and terminates the WSL instance.
I have no idea what's wrong with your xRDP setup. You mentioned in your logs seeing |
So I did try logging out with that button as well as tried |
As well, in your install folder there's |
This worked. Now clicking the Log Out button on KDE does terminate the instance. I'm hoping it terminates the xrdp service before doing so, although only time will tell if I face the previous error again. Thank you for the assistance! |
Glad to hear your issue is sorted. What value for |
@DesktopECHO So in the beginning 15 worked out. The VMMEM process would terminate itself. But as time progresses, I've to keep increasing the time for the instance to even close ( |
Installed the new version, but its more unstable than the last version. the crashes still happen, but over that even gcc is not accessible? Error is get is:
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/Scrt1.o: in function _start': (.text+0x24): undefined reference to main
Looking for a way around that, adding it to path variables etc. Will try reinstalling as well.
The bigger issue is that xRDP has stops with both the versions after a specific number of logins. The error it gives is:
it is similar to this here, and some other problems, but none of the solutions worked. Purging and reinstalling doesn't work either. Any clue how to fix the login error?
The text was updated successfully, but these errors were encountered: