-
-
Notifications
You must be signed in to change notification settings - Fork 143
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
Issue: Running gsudo from a desktop shortcut flashes a console window quickly #327
Comments
Also There's a weired API behavior of OBS started by gsudo(normal or cache). |
Hi @eebssk1, Windows spawns the console before actually starting gsudo, hence Another workaround is to set the shortcut to show minimized, which reduces the flashing to just a minimum on to the taskbar: The idea of having a different Regarding the OBS issue, that's an interesting one that can get more attention. We can repurpose this issue in that direction if you want instead of creating another one. Do you have a stacktrace or additional debug info, logs, repro steps on obs, etc? Thank you. |
Hi @gerardog . Then let's focusing on the OBS one and repurpose the issue. OBS log is here though there's no much useful infomation > https://catbin.sh/b/c17c3e15 It's rather easy to reproduce. You just start obs with gsudo and then add monitor capture source, then it fails. There's a pretty weired workaround. You tick the "Run as admin" for this user compatibility flag of obs64.exe and then start with gsudo and it the works without problem. PS:Looks like only monitor capture api has such problem so maybe some windows internal related. |
Just found another weired point. The way in workaround always start OBS in minimized. |
Hmm I reinstalled windows in this lunar new year and then the issue is gone... |
run-hidden could be used for this. |
@gerardog Hi. Thanks for the new release. |
Description
I'm using gsudo prepended on a shortcut to start a GUI program as admin.(gsudo cache auto spawned via taskscheduler)
Everytime I open the shotcut it flashes a cmd windows quickly and then start the target application.
This is a bit annoying to me.
Proposed technical details
I found a workaround, by prepending "conhost.exe --headless" which precreate a invisible console that gsudo will take over.
It's better if there is something like gsudow which supports this natively.
The text was updated successfully, but these errors were encountered: