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
Terminator display freeze #411
Comments
This is https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3369 and it affects far more than terminator unfortunately. It was originally brought up here in #284. The gnome-shell bug seems to be fixed now, but I don't know if Ubuntu has picked up those changes. Personally, when I went to ubuntu 20.10 I installed https://github.com/justinrdonnelly/wandering-pixel and that fixed the freezing problem. |
Will test workaround today. Thanks a lot for your reactivity on this, has been quite a pain those last days ! |
@mattrose In my situation, when the terminator in the following state, it will freeze as @0011001011 described above.
After the above steps, the terminator will freeze. To unfreeze it, you need to use the |
FYI, the reason it that I am using the Pixel Saver gnome extension. Now I am uninstall the Pixel Saver and try to use Unite. Everything works fine. |
terminator -g /dev/null
Describe the bug
During normal usage of terminator, the display completely freeze (even the cursor actually). It usually happens when using ALT+TAB or other CMD stuff, but not every time.
The terminal still works and accept inputs so you can sort of continue to use it in blind mode.
The only thing to do is either :
Using a htop or something constantly refreshing the terminal does not solve it.
To Reproduce
Every launch on my machine, which is a fresh ubuntu gorilla install. Tried with terminator from repo, and from the latest release on the mattrose/terminator repo.
Expected behavior
No freeze
Screenshots
NA
Desktop (please complete the following information):
Additional context
May be related to this
https://bbs.archlinux.org/viewtopic.php?id=259770
The text was updated successfully, but these errors were encountered: