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
$PATH is incorrect while using XRDP #1065
Comments
You can reset your PATH by editing |
Hi, I have edit the below line in startwm.sh but still i couldn't see PATH correctly. PATH="/usr/lib64/qt-3.3/bin:/opt/EE_LinXXX/bin/:/opt/APTOdevel/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/opt/bin:/opt/UsageModel" Please suggest me on this. |
Can you show me current your startwm.sh? |
Hi, I don't know why some letter are getting bold i have attached the file. |
One more information, RHEL7 XRDP is setting PATH correctly. |
Surround with ``` or ~~~ when you paste config or log. If massively long, attach is better. |
Yes, Can i give startwm.sh file again. |
Maybe xrdp on RHEL7 has different startwm.sh from RHEL6's. What about bring it from RHEL7? |
Yes, I guess you are right. I could see some difference in "/etc/X11/xinit/xinitrc-common" file of RHEL 6 and RHEL 7. RHEL 7 the file is like below:
|
RHEL 6 the same file is like below:
|
I couldn't see any startwm.sh file in RHEL 7.
|
In RHEL7, startwm.sh is placed somewhere in libexec directory, named startwm-bash.sh. |
Yes, its working thanks for all your help. I have another doubt can you clear that also. |
What? If your another issue is completely different from this topic, raise another github issue. |
Ok. Thanks for all your help. |
Issue has fixed by add the startwm.sh file of RHEL7. |
Hi,
We are using XRDP on Our RHEL6 machine.
Please find below details about our machine:
In PuTTY my $PATH is like below:
When Our user try to access the server using XRDP $PATH is different so we are facing some environment issue.
Please find below attachment for better understanding.
Can anyone help me it would be grateful.
The text was updated successfully, but these errors were encountered: