Open glxnnteo opened 3 weeks ago
Hey @glxnnteo
Thanks for report! Can you try run it from the terminal with log enabled? If there's errors you can paste here
cmd.exe
(not PowerShell)taskkill /IM vibe.exe /F
set RUST_BACKTRACE=1
set RUST_LOG=vibe=debug,whisper_rs=debug
%localappdata%\vibe\vibe.exe
Having the same issue in Windows 11 Home.
cmd prompt doesn't work
Same issue. Microsoft Windows [Version 10.0.22631.4317] (c) Microsoft Corporation. All rights reserved.
C:\Windows\System32>cd ""C:\Program Files (x86)\Vibe"
C:\Program Files (x86)\Vibe>taskkill /IM vibe.exe /F SUCCESS: The process "vibe.exe" with PID 14188 has been terminated.
C:\Program Files (x86)\Vibe>set RUST_BACKTRACE=1
C:\Program Files (x86)\Vibe>set RUST_LOG=vibe=debug,whisper_rs=debug
C:\Program Files (x86)\Vibe>vibe.exe
C:\Program Files (x86)\Vibe>2024-10-28T08:14:11.779576Z DEBUG vibe::setup: Vibe App Running 2024-10-28T08:14:11.783509Z DEBUG vibe::custom_protocol: Protocol handler registered successfully. 2024-10-28T08:14:11.783591Z DEBUG vibe::setup: Cargo features: vulkan 2024-10-28T08:14:11.783655Z DEBUG vibe::setup: CPU Features {"avx":{"enabled":true,"support":true},"avx2":{"enabled":true,"support":true},"f16c":{"enabled":true,"support":true},"fma":{"enabled":true,"support":true}} 2024-10-28T08:14:11.783704Z DEBUG vibe::setup: Executable Architecture: x86_64 2024-10-28T08:14:11.783745Z DEBUG vibe::setup: APP VERSION: 2.6.3 2024-10-28T08:14:11.783782Z DEBUG vibe::setup: COMMIT HASH: d24ffccb0d05ea822ff1a3a6edb3b9871be9f368 2024-10-28T08:14:11.783829Z DEBUG vibe::setup: Non CLI mode
@thewh1teagle: I can reproduce my problem and solution! For the latter:
What happened?
Not too sure what's going on, I installed Vibe using the .exe setup and although it seems to be installed just fine, opening the shortcut doesn't do anything. I added an exclusion for Vibe on Windows Defender too and I do not have any other antivirus softwares, Any help?
Steps to reproduce
App was supposed to launch but never did. Tried multiple versions
What OS are you seeing the problem on?
Window
Relevant log output
No response