-
-
Notifications
You must be signed in to change notification settings - Fork 815
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
Panic launching wezterm-gui.exe
on Windows
#1245
Comments
Just confirming, exactly the same for me. Fine from command line, handle assertion panic from shortcut / start menu. |
I can confirm
Tracing this through the deps: rust-cli/env_logger#214 leads to this Rust issue: |
Awesome, thank you. Will follow that issue... hopefully a backport! |
Skip initializing pretty logger when running in the windows subsystem. refs: #1245 refs: rust-lang/rust#88576
I just pushed a commit that seems to resolve this for me; it'll take ~30 minutes to build out and show up in the nightly downloads. |
Amazing. Works great! Thanks for taking care of this so quickly. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
What Operating System(s) are you seeing this problem on?
Windows
WezTerm version
20211021-185611-04768fd1
Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?
Yes, and I updated the version box above to show the version of the nightly that I tried
Describe the bug
Launching
wezterm.exe
successfully opens a command prompt, which then opens the WezTerm window. Launching from thewezterm-gui.exe
executable produces the following panic:However, running
does launch it successfully.
To Reproduce
No response
Configuration
I don't know if any of my config is relevant to the issue. But I can provide it if needed.
Expected Behavior
No response
Logs
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: