mirror of
https://github.com/LGUG2Z/komorebi.git
synced 2026-01-11 14:40:25 +01:00
Error: No connection could be made because the target machine actively refused it. (os error 10061) #67
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ghost on GitHub (Dec 30, 2021).
I get this error anytime I run a command, it starts normal but when I run komorebi status for example. I get the error. Please help
@pigmej commented on GitHub (Dec 30, 2021):
Did you started komorebi earlier via
komorebic start?@ghost commented on GitHub (Dec 30, 2021):
Yes I did
@ghost commented on GitHub (Dec 30, 2021):
https://user-images.githubusercontent.com/93096206/147785338-9ec6adcb-c5c8-45f3-8cae-915b721723d6.mp4
@ghost commented on GitHub (Dec 30, 2021):
oops my bad
@LGUG2Z commented on GitHub (Dec 31, 2021):
This happens from time to time when using the komorebic wrapper to start the komorebi process from Powershell. When it happens to me, I do one of the following:
komorebic startthere, though this still may failkomorebic startfrom a cmd terminal; I've never had this failStart-Process komorebi.exe -WindowStyle hiddenI don't know enough about calling Powershell from Rust to know why this failure occurs sometimes, but I'm happy to keep this ticket open as a bug for someone who is interested enough to look into it.
@ghost commented on GitHub (Dec 31, 2021):
Yeah none of those worked
@ghost commented on GitHub (Dec 31, 2021):
nvm it worked, ty
@nivpgir commented on GitHub (Mar 7, 2022):
Hey, I just wanted to say that the same thing happened to me and the workarounds offered here did not help, the best results I managed to get were by changing the code
komorebic startis running to:and adding:
to the top of komorebics
main.rsthere's some more testing to be done to be more sure but this is more promising than anything else I've tried,
I don't know much about windows' api but this feels like a much more native/stable way to start komorebi than with powershell (although I wasn't able to get rid of the
cmdpart of the command).I'll report back after more testing.