mirror of
https://github.com/LGUG2Z/komorebi.git
synced 2026-01-11 14:40:25 +01:00
Komorebi is not launching #70
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 @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. 🚀