-
Notifications
You must be signed in to change notification settings - Fork 29.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
Polkit is prompted but result in EACCES: permission denied #80516
Comments
@jorangreef have you seen this before? I am trying to figure out if this s a |
@bpasero is this for Electron 5.x? If so, this could be related to jorangreef/sudo-prompt#100 (comment) where Electron 5.x runs processes in a setuid sandbox (the Electron team are working on a fix). @arbaes to isolate, please would you try running:
|
@jorangreef this is still with Electron 4.x actually. Are you saying that with Electron 6 |
OH, this fix seems to have landed only in //cc @deepak1556 fyi this was a fix we needed for E6, but we need to verify it is good once we go with 6.0.8 |
@bpasero, yes, any Electron version which wanted to sandbox setuid, since there's no way we can do elevation without setuid. On an unrelated note, while we are talking, just a reminder about microsoft/terminal#2419, the bug behind jorangreef/sudo-prompt#97, which also affects VSCode. I see @bitcrazed assigned this 10 hours ago. |
@jorangreef did try with sudo-prompt 6.11.3, here's the output:
So I guess it's fine ? EDIT: |
@arbaes, thanks, yes I think that points again to Electron's setuid sandbox as the culprit. |
@arbaes can you post a screenshot of the about dialog of VSCode? |
I am still not convinced this issue is related to E6 because you see it with E4. |
If I can provide any more insights let me know |
I am getting this same error, but I have electron 6.1.1. I'm getting a similar error:
Is this the right place to report this? Thanks! |
When trying to save a file where I don't have write access, I can retry as sudo,
the polkit agent raise a prompt sucessfully, and then
Steps to Reproduce:
It worth to mention that a different message is raised when a wrong password is entered:
Does this issue occur when all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered: