-
-
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
Failure to launch authentication prompt on Ubuntu 24.04 LTS #3248
Comments
It may also be noteworthy that GNOME Remote Desktop (the default RDP server in Ubuntu, the one that appears in Ubuntu settings) does not have this problem. By default, for GNOME Remote Desktop, authentication prompts appear when a superuser GUI action is performed (e.g., adding a new user). Thus, although I mentioned that this could be a GNOME or polkit problem, it is mediated by an interaction with xrdp in a manner not replicated with GNOME Remote Desktop. |
Thanks for the high quality issue report @ToeKneeFan. I'm a bit snowed under to look at this in a lot of detail currently, but I think what you're saying is, the link between the polkit daemon the polkit authentication agent for GNOME appears to be not working. Is that correct? |
Also, can you pick a scenario you'd like to look at and we'll step through it. |
FWIW, on my machine I get an authentication prompt in a GNOME xrdp session with this command as an unprivileged user:-
|
Thank you for your kind words, @matt335672! It appears to be an issue with the polkit daemon and polkit authentication agent, although it occurs when remotely accessing via xrdp and does not occur for GNOME Remote Desktop; perhaps it is due to a difference in the way xrdp-initiated GNOME sessions are treated. I realize GNOME Remote Desktop is just accessing a more local session (is visible from the machine's local screen), so there are likely fundamental differences in the characteristics of the respective GNOME sessions. |
|
Thanks - I can see that too. I've got a VM with a privileged user and a non-privileged user. If I use the non-privileged user I get prompted for privileged user credentials on the console, but not in an xrdp session. I'll figure out what the differences are in both modes and document it here. |
I've enabled logging for polkit by using the instructions on the Arch wiki, i.e.:-
Logging in on the console, I get the following logged when I enter the users panel:-
When I hit the
I now run the Logging on on xrdp, I get the following logged when I enter the
When I hit the HOWEVER, I do appear to be having some problems switching between the same user over xrdp and the console:-
This is perhaps muddying the waters here. @ToeKneeFan - can you try to reproduce the above with the logging. Please use a different user between console and xrdp session, and make sure after running the script that your user is added to the |
@matt335672 Sorry to take so long to get back to you! I created
When navigating to the Users panel, the "Unlock" button has disappeared entirely. It is replaced with the banner:
There are no messages in logging upon navigating to the Users panel on my end. However, there are some messages upon initial xrdp login, such as the following
I tried this both with and without the additional Removing I am using the current version of xrdp on the apt repository (0.9.24); I assume you may be on a later development version, which may explain some differences in behavior. I can test on a later version/branch if desired. |
Sorry - I meant Also, this is not related to the xrdp version at all - this is pure polkit. There's probably a difference in the way we're running polkitd. I've realised I'm using a completely separate user. Can you try the following:-
Thanks. |
Thank you, I have run these steps as advised (adding At the moment, my only polkit rule in If it would be helpful, I can try to reproduce on a clean VM. |
There's something going on here I don't understand, that's for sure. If you're able to start from a clean VM built from an iso, that could be useful. I can then try to reproduce here from the same iso. |
@ToeKneeFan - did you manage to get anywhere with a clean VM? |
xrdp version
0.9.24
Detailed xrdp version, build options
Operating system & version
Ubuntu 24.04.1 LTS
Installation method
dnf / apt / zypper / pkg / etc
Which backend do you use?
xorgxrdp
What desktop environment do you use?
GNOME
Environment xrdp running on
Physical machine with Intel HD Graphics 630
What's your client?
Microsoft Remote Desktop on Microsoft Windows 11
Area(s) with issue?
Authentication
Steps to reproduce
✔️ Expected Behavior
We expect for an authentication prompt to appear and ask for a password.
❌ Actual Behavior
Nothing happens. Actions requiring sudo privileges are ignored.
Anything else?
OS release relationship
This problem appears to be new to Ubuntu 24.04 LTS and was not present on the prior LTS version (22.04 LTS). That is, the expected authentication prompts appeared when GUI actions required it. It may not necessarily be related to xrdp; this could be a polkit or GNOME issue.
Previous reports
This problem has been noted by a different user on StackOverflow. This was also noted on the c-nergy blog, which describes that expected polkit AUTH_ADMIN rules do not work:
Unrelated issues/solutions
My
.xsessionrc
file consists of the following:That is, I have already configured xrdp to use the Ubuntu GNOME environment, rather than the default GNOME one. The problem reported on "Running GNOME on Ubuntu 24.04 LTS" is unrelated.
The solution proposed in "Why can't I perform some privileged GUI actions?" and @matt335672's pk-local is very helpful but is not applicable in this scenario, as pk-local adds polkit rules, including AUTH_ADMIN rules, but those rules cannot call the authentication prompt (as noted above).
This problem appears unrelated to #3053, which reports a different issue with Ubuntu 24.04 LTS. The error in this report is actually more similar to the problem described in #2926, which details a similar authentication-prompt issue on Xfce (may be the exact same problem, except on a different OS); that issue appears to have been closed prematurely due to nonresponse by the OP, so I am opening this one (especially as it is unclear if it is the same problem).
The text was updated successfully, but these errors were encountered: