-
-
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
I can only connect via RDP if the user is in the sudo group #3016
Comments
Bad messages in
What do you get for |
Let me attack also the logs of .xsession-errors: /home/izi4me/.xsession-errors /home/raspi/.xsession-errors |
The group is render. I attach the new log from xordxrdp.10.txt |
For the browser issue see #2869 As for the rest of your issues, I've done a bit of poking about in past issues and found this comment on #1503 which describes your situation. I can't offer you a solution for the issue as reported as I don't have an rPI 4 to reproduce this. In the log you attach above for a working session, I notice the following:-
It looks like for the working session the device can't be opened, which is the other way round from what I'd expect. It does however give us a way forward which is to stop the xrdp session trying to use this device at all. See this comment for how to do that. |
First of all, thank you very much for your time and help. The problem with the browser was what you said. Using the --disable-gpu command works fine. Lets talk about the rdp connection. I have made the change you mention and reboot, but I still can't log in via RDP with "raspi" user. I cheked again the log xorgxrdp.11.log and even if the field is blank, it still gives an error when trying to use it:
I attach the xorgxrdp.11.log of the user "raspi" raspi_log(xorgxrdp.11.log).txt If you need anything else, tell me. Thank you. |
That log file looks fine. The session is not working for another reason. Check you're not logged in on the rPI console as the same user. If it's not that, paste your xrdp-sesman.log for the session times. |
I have checked the user who is logged in, and it's the user "izi4me". From this user I can connect via RDP, but I still can't connect with the "raspi" user. I have checked the xrdp-sesman.log and xrdp.log files, and I don't see anything strange. I attach the logs. |
Thanks. Have you get anything in |
I check it and there is not many information about the error, just "Failed to inhibit: Access denied" i attack the log. |
Let's try to get more logging out of the start session script. Try this logged in as
This might give you more in |
Its seems there is more information: |
I add a trace of debug into the xrdp-sesman.ini to get more info on the xrdp-sesman.log. Maybe can help you:
|
No, sadly none of that is useful, except to tell us that xrdp is trying to start the right desktop. Your desktop environment is failing - there's no problem with sesman. It may be related to this error, but I don't know enough about how the rPI desktop works to be sure.
Am I correct in thinking that |
xrdp version
0.9.21.1
Detailed xrdp version, build options
Operating system & version
Debian GNU/Linux 12 (bookworm)
Installation method
dnf / apt / zypper / pkg / etc
Which backend do you use?
xorg
What desktop environment do you use?
LXDE-pi
Environment xrdp running on
Raspberry PI (PCI bridge: Broadcom Inc. and subsidiaries BCM2711 PCIe Bridge)
What's your client?
Windows RDP client
Area(s) with issue?
Session manager (sesman)
Steps to reproduce
When I log in with the main user, there is no problem. When I try with any other user, the client closes automatically without any response message.
✔️ Expected Behavior
Log in with any user
❌ Actual Behavior
I can't log in with a different user than my main user
Anything else?
Logs
/var/log/xrdp.log
xrdp.log.txt
/var/log/xrdp-sesman.log
xrdp-sesman.log.txt
/home/izi4me/.xorgxrdp.10.log
xorgxrdp.10.log.txt
/home/raspi/.xorgxrdp.11.log
xorgxrdp.11.log..txt
When I add the raspi user to the sudo group, I can access correctly via RDP. I guess it must be a permissions problem but I can't identify the problem.
Thank you.
Regards.
The text was updated successfully, but these errors were encountered: