Skip to content
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

Windows shell admin error #48

Open
Inokenty90 opened this issue Jan 13, 2021 · 12 comments
Open

Windows shell admin error #48

Inokenty90 opened this issue Jan 13, 2021 · 12 comments
Assignees
Labels
bug Something isn't working

Comments

@Inokenty90
Copy link

with admin privileges
изображение
without
изображение
Error from gsudo when interrupt program with Ctrl+c

@kingToolbox
Copy link
Owner

Exit Code 0xC000013A means that gsudo has been terminated by ctrl+c. From the picture, it should be the ctrl+c that caused the gsudo to exit. And I think gsudo did not handle ctrl+c correctly.

I just released a new version 2.0.0_Prerelease_1, which also contains the updated gsudo v0.7.3, please download and see if the same problem still exists, thank you.

@Inokenty90
Copy link
Author

same error
изображение

@Inokenty90
Copy link
Author

gerardog/gsudo#53 strange but in issue said that in 0.7.2 this error already fixed

@kingToolbox
Copy link
Owner

kingToolbox commented Jan 14, 2021

Yes, I have seen that issue, so one possibility is that it has not been fixed completely.

When I tried to reproduce your problem, I found only pressing ctrl+c at the beginning of the session may cause gsudo to be stopped. I guess it is because the powershell process has not started yet. Once I saw the command prompt, I can no longer stop it by pressing ctrl+c. I have tried several environments with such results. So maybe this question should be submitted to gsudo. Unfortunately, I am afraid there is nothing I can do.

@Inokenty90
Copy link
Author

Tried to reproduce gsudo error without WindTerm and failed. Tried to start powershell from cmd, cmd from powershell, start cmd from Task Manager.

@kingToolbox
Copy link
Owner

Thank you for your hard work. Although not reproducing the problem elsewhere does not mean that it is only related to WindTerm, but this month I will continue to analyze this problem. Whether it can be resolved or not, I will tell you.

@kingToolbox kingToolbox added the bug Something isn't working label Jan 15, 2021
@kingToolbox kingToolbox self-assigned this Jan 15, 2021
@Inokenty90
Copy link
Author

Repeated error on virtual machine with windows 10x64. Need to disable UAC and login as built-in Administrator account.

@kingToolbox
Copy link
Owner

When I saw "repeated", I was optimistic. Such problems can usually be solved well. I will create a vm as you said and try it.

I read the introduction of gsudo, it should be allowed to run under such preset conditions, but I don't know what role gsudo can play in this way, because its purpose is to run commands with elevated permission.

@Error996
Copy link

Fix in gsudo v1.0.2 Latest

Fixed 'gsudo cache' auto-elevation on PowerShell when path has spaces.
Fixed Cache auto not working with sudo alias or msys (#98)
gsudo failing in PowerShell with ExecutionPolicy=Restricted. (#101)
Fixed Ctrl-C Handling on de-elevation (#103)

@gerardog
Copy link

Hi. Let me know if this issue persists. BTW, latest gsudo is v1.2 😊

@kingToolbox
Copy link
Owner

@Error996 @gerardog
The gsudo currently used is v1.0.2, and will be upgraded to the 1.2.0 version soon. So this bug should be fixed, but I don't have an environment to test it.

@kingToolbox
Copy link
Owner

@Error996 @gerardog
I am happy to inform you that WindTerm_2.4.0_Prerelease_2 has been released and gsudo 1.2.0 has been packaged. Please download and check it, thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants