-
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 process hang on close #7700
Comments
What makes you think Alacritty isn't closing? When opening Alacritty from a terminal, does it not return to the prompt immediately? This sounds like it's just a DE issue tbh. |
I just described why, but will do again, there is that spinning (loading indicator) that keeps rotating on the shortcut, indicating that the process has not yet closed (even though the window has closed), and also a bit after the spin is gone, I am still not able to open another Alacritty instance. It does nothing If I click on it to open. That is why. |
Do you see alacritty in the process tree? |
Please answer this question. |
Before when I did -v it opened a new instance of it, regardless if from normal terminal or alacritty itself. I didnt check just with the command itself. I had turned the laptop off, now I tried to turn it on, gave a grey screen on the login screen, seems related to nvidia gpu, trying to fix, so I am not able to check right now. |
I fixed the login issue. I just recorded a video showing the behavior. 2024-02-07.19-55-24.mp4Video format (HEVC) might not work here on the browser, but if you download, it should. When I type I just installed on my desktop, same OS, and the same thing happens. I also installed Wezterm, using together with all other shell tools, that does not happen, so that should indicate that those tools are not at fault. Same thing on Terminator. |
If you add [env]
LIBGL_ALWAYS_SOFTWARE = "1" in your config is it getting fixed? It seems like not our issue. It was also requested to try running from other terminal with |
It doesnt. But I see what you mean. Yeah, if I constantly exit and open a alacritty again through the terminal or keyboard shortcut, it goes instantly to a new window, without any delays.
It's PopOS 22.04, in the laptop the install was on this week. |
I suppose I have handed all the information you asked for, if you need anything else, let me know, I wont be opening I mostly use keyboards shorcuts which the problem doesnt happen. |
I believe I am experiencing the same issue. When I launch Alacritty through a terminal command, it functions as expected: I can open, close, and instantly reopen it without any problems. However, attempting to initiate Alacritty using a shortcut or by clicking its icon leads to a persistent spinning cursor, which remains even after closing Alacritty. Moreover, I'm unable to relaunch it (either via shortcut or icon) for a brief period, about 7 to 8 seconds. Based on what I've read in other issues here and after testing both Alacritty versions 0.13.1 and 0.14.0 (with and without the suggested patch), my understanding is that the problem might be related to GNOME itself. I was hopeful that the new GNOME version 45.4 would address this, but unfortunately, it has not. I genuinely miss using Alacritty. |
Even if it were related to gnome, why only on alacritty? |
I experienced the same issue for Alacritty and Brave. Changing Perhaps related to #868? |
I noticed that when I close Alacritty, through an exit for example, the window closes normally, but the shortcut icon progress bar keeps spinning and I am unable to open another instance till it stops, and even a bit more after it stops, only after.
I am using this ppa https://launchpad.net/~aslatter/+archive/ubuntu/ppa with the latest version, even though when installing it says
0.13.1
, when I do a-v
, it shows0.14.0-dev
.I use nushell, zellij and starship with it.
PopOS 22.04
Laptop with very good hardware. Certainly not the problem.
I was using Terminator as the terminal before and never had this kind of behavior, not a really bad thing, but sometimes it could be, that's why I opened the issue.
The text was updated successfully, but these errors were encountered: