-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Alacritty freezes Arch Linux, Wayland, Nvidia #7485
Comments
could you post the |
yeah, but I need the log and not the screenshot... |
And after it got frozen starting typing something like |
[2667358.602] [email protected](2276447, 114.84765625, 307.66406250) |
Cant do anything, SHIFT + H does nothing even the instance of alacritty that debugs gets freezes too even tho is in another worskpace, shift + h, prints H, I know because the terminal still works and can copy/paste its content, but still no renders changes in the front |
The log is truncated, could you please just run But you said that
So just start pressing like ten times and then close the window, it's more than enough. |
nice, yet another bug in compositor. If you look at the log you can see the
and
There's never a point when it changes back to to work around that you can try the patch from |
It worked thanks, does this has an impact on performance? I have been using alacritty for almost a year, I really don't wanna change it, version 0.12.3 worked just fine, thanks for all I really appreciate it |
No, but report this to hyprland please. |
Your issue got fixed upstream hyprwm/Hyprland#4287 |
System
OS: GNU/Linux
Version: alacritty 0.13.0 (78fa4d6)
Arch Linux: Wayland, Hyprland, Sway
No logs, after a while all instances of alacritty just freezes, can still type and do commands, but not visible, its like it just stops rendering the "GUI" part, If I continually use the instance of alacritty it won't freeze, its just If I leave it in a lonely workspace and don't use it, this never happened to me, I have just updated to 0.13 and just happened, using proprietary drivers btw
The text was updated successfully, but these errors were encountered: