Originally created by @Lap1n on GitHub (Jan 8, 2022).
I installed komorebi on Windows 10 withScoop.
When I start the application with komorebic start
I get the following output which seems normal: Start-Process komorebi.exe -WindowStyle hidden
However, I do not observe any automatic tiling
When I execute the commands komorebic state and komorebic stop, I get the same following output:
Error: No connection could be made because the target machine actively refused it. (os error 10061)
Location:
/rustc/c8dfcfe046a7680554bf4eb612bad840e7631c4b\library\core\src\result.rs:1897:27
Is there something that I missed in the installation process?
Thank you for this great project!
Originally created by @Lap1n on GitHub (Jan 8, 2022).
I installed komorebi on Windows 10 withScoop.
When I start the application with
`komorebic start`
I get the following output which seems normal:
`Start-Process komorebi.exe -WindowStyle hidden`
However, I do not observe any automatic tiling
When I execute the commands `komorebic state` and `komorebic stop`, I get the same following output:
```
Error: No connection could be made because the target machine actively refused it. (os error 10061)
Location:
/rustc/c8dfcfe046a7680554bf4eb612bad840e7631c4b\library\core\src\result.rs:1897:27
```
Is there something that I missed in the installation process?
Thank you for this great project!
Try the workarounds in that post, this is known to happen intermittently
@LGUG2Z commented on GitHub (Jan 8, 2022):
This sounds like the same issue described here: https://github.com/LGUG2Z/komorebi/issues/89#issuecomment-1003216079
Try the workarounds in that post, this is known to happen intermittently
I've tried it (trying to launch it alternately with powershell and command prompt) and still having the same issue.
@Lap1n commented on GitHub (Jan 8, 2022):
I've tried it (trying to launch it alternately with powershell and command prompt) and still having the same issue.
Does the process launch when launching from the komorebi binary directly?
❯ komorebi --help
komorebi 0.1.6
Jade Iqbal <jadeiqbal@fastmail.com>
A tiling window manager for Windows
USAGE:
komorebi.exe [OPTIONS]
OPTIONS:
--ffm Allow the use of komorebi's custom focus-follows-mouse implementation
-h, --help Print help information
-V, --version Print version information
❯ komorebi
2022-01-09T02:35:51.305115Z INFO init: komorebi::window_manager: initialising
2022-01-09T02:35:51.354269Z INFO init:update_focused_workspace{follow_focus=false}: komorebi::window_manager: updating
2022-01-09T02:35:51.359007Z INFO komorebi::process_command: listening
2022-01-09T02:35:51.359092Z INFO komorebi::process_event: listening
...
@LGUG2Z commented on GitHub (Jan 9, 2022):
Does the process launch when launching from the `komorebi` binary directly?
```
❯ komorebi --help
komorebi 0.1.6
Jade Iqbal <jadeiqbal@fastmail.com>
A tiling window manager for Windows
USAGE:
komorebi.exe [OPTIONS]
OPTIONS:
--ffm Allow the use of komorebi's custom focus-follows-mouse implementation
-h, --help Print help information
-V, --version Print version information
```
```
❯ komorebi
2022-01-09T02:35:51.305115Z INFO init: komorebi::window_manager: initialising
2022-01-09T02:35:51.354269Z INFO init:update_focused_workspace{follow_focus=false}: komorebi::window_manager: updating
2022-01-09T02:35:51.359007Z INFO komorebi::process_command: listening
2022-01-09T02:35:51.359092Z INFO komorebi::process_event: listening
...
```
When I run komorebi --help, I get the same output as you (same version also).
However, when I run komorebi, I do not get any output.
@Lap1n commented on GitHub (Jan 9, 2022):
When I run `komorebi --help`, I get the same output as you (same version also).
However, when I run `komorebi`, I do not get any output.
If you try running komorebi directly with $env:RUST_LOG = 'trace'; $env:RUST_BACKTRACE = 'full'; komorebi, do you still not have any output?
Can you download the latest build artifact from here, try running komorebi from that zip file and see if the behaviour is the same?
@LGUG2Z commented on GitHub (Jan 10, 2022):
If you try running `komorebi` directly with ` $env:RUST_LOG = 'trace'; $env:RUST_BACKTRACE = 'full'; komorebi`, do you still not have any output?
Can you download the latest build artifact from [here](https://github.com/LGUG2Z/komorebi/actions/runs/1668460412), try running `komorebi` from that zip file and see if the behaviour is the same?
I can confirm this behavior. By downloading the zip file and unpacking the binaries to a folder in PATH everything works fine. It looks like it's related to how the app is installed via scoop.
@JSamir commented on GitHub (Jan 10, 2022):
I can confirm this behavior. By downloading the zip file and unpacking the binaries to a folder in PATH everything works fine. It looks like it's related to how the app is installed via scoop.
This is the output, I tried multiple times, no luck. How long should it stay at updating? Also I had to download latest build artifact. I am on Windows 11. Another interesting thing is that it needs to be run in Powershell, not Powershell 7, otherwise I get no output, even with latest artifact.
PS C:\Users\pegak> komorebi
2022-01-12T11:02:58.711783Z INFO init: komorebi::window_manager: initialising
2022-01-12T11:02:58.711783Z INFO init: komorebi::window_manager: initialisi
PS C:\Users\pegak> komorebi
2022-01-12T11:03:51.644580Z INFO init: komorebi::window_manager: initialising
2022-01-12T11:03:51.656951Z INFO init:update_focused_workspace{follow_focus=false}: komorebi::window_manager: updating
PS C:\Users\pegak> komorebi --ffm
2022-01-12T11:04:30.049512Z INFO init: komorebi::window_manager: initialising
2022-01-12T11:04:30.061256Z INFO init:update_focused_workspace{follow_focus=false}: komorebi::window_manager: updating
EDIT: Restarting computer helped. :) Now I have to figure out, how to not manage quake-like terminal window. :)
EDIT2: I had some troubles with it, so I had to close komorebi and now it doesn't work again. I will try to restart PC again, but I think it shouldn't happen to be stuck at loading.
@BleedingDev commented on GitHub (Jan 12, 2022):
This is the output, I tried multiple times, no luck. How long should it stay at updating? Also I had to download latest build artifact. I am on Windows 11. Another interesting thing is that it needs to be run in Powershell, not Powershell 7, otherwise I get no output, even with latest artifact.
```
PS C:\Users\pegak> komorebi
2022-01-12T11:02:58.711783Z INFO init: komorebi::window_manager: initialising
2022-01-12T11:02:58.711783Z INFO init: komorebi::window_manager: initialisi
PS C:\Users\pegak> komorebi
2022-01-12T11:03:51.644580Z INFO init: komorebi::window_manager: initialising
2022-01-12T11:03:51.656951Z INFO init:update_focused_workspace{follow_focus=false}: komorebi::window_manager: updating
PS C:\Users\pegak> komorebi --ffm
2022-01-12T11:04:30.049512Z INFO init: komorebi::window_manager: initialising
2022-01-12T11:04:30.061256Z INFO init:update_focused_workspace{follow_focus=false}: komorebi::window_manager: updating
```
EDIT: Restarting computer helped. :) Now I have to figure out, how to not manage quake-like terminal window. :)
EDIT2: I had some troubles with it, so I had to close komorebi and now it doesn't work again. I will try to restart PC again, but I think it shouldn't happen to be stuck at loading.
Again, started working after restart, then i opened File Explorer via Win + E and it stopped. Not even events are logged.
@BleedingDev commented on GitHub (Jan 12, 2022):
Again, started working after restart, then i opened File Explorer via Win + E and it stopped. Not even events are logged.
@pegak The point at which the logs hang for you is when komorebi is trying to find information about the connected monitors. Can you try running the same binaries in a Hyper-V Windows Dev VM? (should be able to drag and drop them over).
@LGUG2Z commented on GitHub (Jan 13, 2022):
@pegak The point at which the logs hang for you is when `komorebi` is trying [to find information about the connected monitors](https://github.com/LGUG2Z/komorebi/blob/master/komorebi/src/window_manager.rs#L176). Can you try running the same binaries in a Hyper-V Windows Dev VM? (should be able to drag and drop them over).
@LGUG2Z commented on GitHub (Jan 13, 2022):
@1014404193 https://github.com/LGUG2Z/komorebi/issues/89#issuecomment-1003216079 try the alternatives in this comment, you can also try running `Start-Process komorebi.exe -WindowStyle hidden` directly in PowerShell.
@1014404193 #89 (comment) try the alternatives in this comment, you can also try running Start-Process komorebi.exe -WindowStyle hidden directly in PowerShell.
Start-Process komorebi.exe -WindowStyle hidden can use,ty
@vvspWsvzz1z7 commented on GitHub (Jan 14, 2022):
> @1014404193 [#89 (comment)](https://github.com/LGUG2Z/komorebi/issues/89#issuecomment-1003216079) try the alternatives in this comment, you can also try running `Start-Process komorebi.exe -WindowStyle hidden` directly in PowerShell.
`Start-Process komorebi.exe -WindowStyle hidden` can use,ty
@pegak The point at which the logs hang for you is when komorebi is trying to find information about the connected monitors. Can you try running the same binaries in a Hyper-V Windows Dev VM? (should be able to drag and drop them over).
I can try, just have to find time for that. Will report here. :)
@BleedingDev commented on GitHub (Jan 14, 2022):
> @pegak The point at which the logs hang for you is when `komorebi` is trying [to find information about the connected monitors](https://github.com/LGUG2Z/komorebi/blob/master/komorebi/src/window_manager.rs#L176). Can you try running the same binaries in a Hyper-V Windows Dev VM? (should be able to drag and drop them over).
I can try, just have to find time for that. Will report here. :)
After I updated komorebi installed by scoop from 0.1.6 to 0.1.7, I ran into the above problem, but I solved it by the following workaround.
I noticed that the binaries of komorebi.exe and komorebic.exe under scoop/shims were not updated, so I replaced them with the latest version in scoop/apps/komorebi/current manually, and it works fine.
I don't know if this is the safe and correct way, but for your information.
@annenpolka commented on GitHub (Jan 27, 2022):
After I updated komorebi installed by scoop from 0.1.6 to 0.1.7, I ran into the above problem, but I solved it by the following workaround.
I noticed that the binaries of `komorebi.exe` and `komorebic.exe` under `scoop/shims` were not updated, so I replaced them with the latest version in `scoop/apps/komorebi/current` manually, and it works fine.
I don't know if this is the safe and correct way, but for your information.
@sitiom commented on GitHub (Jan 27, 2022):
Created a PR of komorebi in the Extras bucket, maybe someone there can help (https://github.com/ScoopInstaller/Extras/pull/7840).
@LGUG2Z I want to contribute to the upstream manifest, but it seems like goreleaser doesn't support the notes and suggest properties.
@sitiom commented on GitHub (Jan 28, 2022):
@LGUG2Z I want to contribute to the upstream manifest, but it seems like goreleaser doesn't support the `notes` and `suggest` properties.
@sitiom I'm happy to deprecate the custom bucket published by GoReleaser if we can get a manifest merged to the scoop/extra's bucket. 🙏
@LGUG2Z commented on GitHub (Jan 28, 2022):
@sitiom I'm happy to deprecate the custom bucket published by GoReleaser if we can get a manifest merged to the scoop/extra's bucket. 🙏
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Lap1n on GitHub (Jan 8, 2022).
I installed komorebi on Windows 10 withScoop.
When I start the application with
komorebic startI get the following output which seems normal:
Start-Process komorebi.exe -WindowStyle hiddenHowever, I do not observe any automatic tiling
When I execute the commands
komorebic stateandkomorebic stop, I get the same following output:Is there something that I missed in the installation process?
Thank you for this great project!
@LGUG2Z commented on GitHub (Jan 8, 2022):
This sounds like the same issue described here: https://github.com/LGUG2Z/komorebi/issues/89#issuecomment-1003216079
Try the workarounds in that post, this is known to happen intermittently
@Lap1n commented on GitHub (Jan 8, 2022):
I've tried it (trying to launch it alternately with powershell and command prompt) and still having the same issue.
@LGUG2Z commented on GitHub (Jan 9, 2022):
Does the process launch when launching from the
komorebibinary directly?@Lap1n commented on GitHub (Jan 9, 2022):
When I run
komorebi --help, I get the same output as you (same version also).However, when I run
komorebi, I do not get any output.@LGUG2Z commented on GitHub (Jan 10, 2022):
If you try running
komorebidirectly with$env:RUST_LOG = 'trace'; $env:RUST_BACKTRACE = 'full'; komorebi, do you still not have any output?Can you download the latest build artifact from here, try running
komorebifrom that zip file and see if the behaviour is the same?@JSamir commented on GitHub (Jan 10, 2022):
I can confirm this behavior. By downloading the zip file and unpacking the binaries to a folder in PATH everything works fine. It looks like it's related to how the app is installed via scoop.
@BleedingDev commented on GitHub (Jan 12, 2022):
Same issue here, gonna try release bin and will report.
@BleedingDev commented on GitHub (Jan 12, 2022):
This is the output, I tried multiple times, no luck. How long should it stay at updating? Also I had to download latest build artifact. I am on Windows 11. Another interesting thing is that it needs to be run in Powershell, not Powershell 7, otherwise I get no output, even with latest artifact.
EDIT: Restarting computer helped. :) Now I have to figure out, how to not manage quake-like terminal window. :)
EDIT2: I had some troubles with it, so I had to close komorebi and now it doesn't work again. I will try to restart PC again, but I think it shouldn't happen to be stuck at loading.
@BleedingDev commented on GitHub (Jan 12, 2022):
Again, started working after restart, then i opened File Explorer via Win + E and it stopped. Not even events are logged.
@vvspWsvzz1z7 commented on GitHub (Jan 13, 2022):
i install from scoop,stop and exit powershell,when i try star again start appear 10061
@LGUG2Z commented on GitHub (Jan 13, 2022):
@pegak The point at which the logs hang for you is when
komorebiis trying to find information about the connected monitors. Can you try running the same binaries in a Hyper-V Windows Dev VM? (should be able to drag and drop them over).@LGUG2Z commented on GitHub (Jan 13, 2022):
@1014404193 https://github.com/LGUG2Z/komorebi/issues/89#issuecomment-1003216079 try the alternatives in this comment, you can also try running
Start-Process komorebi.exe -WindowStyle hiddendirectly in PowerShell.@vvspWsvzz1z7 commented on GitHub (Jan 14, 2022):
Start-Process komorebi.exe -WindowStyle hiddencan use,ty@BleedingDev commented on GitHub (Jan 14, 2022):
I can try, just have to find time for that. Will report here. :)
@younger-1 commented on GitHub (Jan 18, 2022):
Some problems, don't work with above workarounds
@annenpolka commented on GitHub (Jan 27, 2022):
After I updated komorebi installed by scoop from 0.1.6 to 0.1.7, I ran into the above problem, but I solved it by the following workaround.
I noticed that the binaries of
komorebi.exeandkomorebic.exeunderscoop/shimswere not updated, so I replaced them with the latest version inscoop/apps/komorebi/currentmanually, and it works fine.I don't know if this is the safe and correct way, but for your information.
@sitiom commented on GitHub (Jan 27, 2022):
Created a PR of komorebi in the Extras bucket, maybe someone there can help (https://github.com/ScoopInstaller/Extras/pull/7840).
@sitiom commented on GitHub (Jan 28, 2022):
@LGUG2Z I want to contribute to the upstream manifest, but it seems like goreleaser doesn't support the
notesandsuggestproperties.@LGUG2Z commented on GitHub (Jan 28, 2022):
@sitiom I'm happy to deprecate the custom bucket published by GoReleaser if we can get a manifest merged to the scoop/extra's bucket. 🙏
@sitiom commented on GitHub (Jan 28, 2022):
Merged now!
@LGUG2Z commented on GitHub (Jan 28, 2022):
Readme has been updated to point people to the extras bucket. 🚀