-
-
Notifications
You must be signed in to change notification settings - Fork 3.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
When input, characters are not displayed #8884
Comments
I can confirm, having the same issue with |
I can also confirm since I updated a few days ago to 1.0.199. Updated to 1.0.200 and still see this issue. |
I rolled back from 1.0.200 > 1.0.199 > 1.0.198 > 1.0.197 checking each along the way. The problem resolved when I got to 197. |
Yeah, I'm having this problem too, in v1.0.200, v1.0.199, and v1.0.198. It's a serious problem, having to rely on the space bar and line feeds to see the contents of the input message, making it difficult to verify that the input is correct when I'm outputting characters. I ended up going back to v1.0.197 to avoid this problem, which is a shame. |
Could you please include more info about your setup? So far I couldn't reproduce it on 6 computers I test with (all 3 OSes included). |
@Eugeny just did some testing and the issue goes away when I uncheck "Disable GPU acceleration" in settings. Version: 1.0.200 |
I'd like to wait for a complete official fix for this bug before upgrading. |
"Disable GPU" is off by default - is there a reason why you've enabled it? |
I tried to off or on |
I can confirm, having the same issue with 1.0.200. |
I have the same issue on 1.0.200 but It seems that it occurs only on the first tab. |
I'm not. Each of my tabs has this problem. |
Either way, it shows that the problem does exist, and I look forward to an official fix for this bug soon, thanks. |
@Eugeny After some testing I have consistent results for you to try. I used Oracle VirtualBox 7 (7.0.10-158379~Ubuntu~jammy) and booted off the ubuntu-23.04-desktop-amd64.iso and hit "try" to load in to the live iso. I opened firefox and got past the initial tabs. I went directly to https://github.com/Eugeny/tabby, downloaded the tabby-1.0.200-linux-x68.deb, and installed it. After opening a terminal session, the typing problem persists there for me. I type 12 they show, but after that 345678 and the numbers did not show until 8. It seems like every 6 characters sent to the window prompts a display, and this included the prompt itself. I started playing with the settings and discovered that if I switch frontend to "xterm (canvas)" and open a new terminal, the problem went away. Switching back to "xterm (WebGL)" and opening a new terminal causes the problem to return. Back in my desktop (kubuntu-23.04-amd64, tabby-1.0.200) I tried switching to "xterm (canvas)" and opening a new terminal. The problem is gone. For me, I have a viable work around. I hope this helps others and proves a consistent solution.
|
it still has the problem when i jump to remote machine by ssh.
|
it still has the problem when i jump to remote machine by ssh. |
I also made this observation in some situations even in
It seems to be a different issue, but might have a relation to this one. |
Thanks #8884 (comment) I switched terminal front-end "xterm (canvas)" , and restart tabby, then problem resolved. But, inputting is a bit slower than previous tabby. |
I can confirm, having the same issue with 1.0.200. |
I also have the same issue with 1.0.200 version , please fix it. |
Hey, I encoutered this issue too. Errors seen in debug console at the time of the issue :
It seems to be a bug with WebGL and chromium. Switching to
|
I also am having the same issue. Rolled back to 1.1.197 as workaround |
Confirmed switching to xterm (canvas) (thanks @Clem-Fern!) resolves for me. I only see the issue when using Tabby on a VM at the other end of an RDP connection, incidentally. |
To be honest, i'm also using tabby (only) on VM/RDP, because Windows 2022 (cloud) installations can't install Windows Terminal. |
Thanks for suggestions. My consoles broke after some time: 1) cursor disappeared 2) mouse produced letters 3) typed text invisible. |
I rolled back to 1.0.197 big trouble ---> 1.0.200 |
I rolled back to 1.0.197 big trouble ---> 1.0.200 |
It's fixed in v201 |
thanks. I have the same problems in (canvas) mode and in v201: update: i'm still getting the variation of this issue in v201-v205. it's a tripple frustration at the moment: |
^ this is the resolution. i've copied 197 tab-terminal and tab-ssh folders to the 207 version to mitigate this. All other issues above remain in 207 gl/canvas. |
Describe the problem:
[A clear and concise description of what the bug is.]
When I updated to the latest version, there was a bug. When I input a command in the terminal, the characters are not displayed or are not updated in a timely manner. Only the cursor is moving, but no characters are displayed. It will make it difficult for me to know what I am typing.
version:1.0.198
To Reproduce:
[Steps to reproduce the behavior]
The text was updated successfully, but these errors were encountered: