When input, characters are not displayed

[L-Super]

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]

• open teminal
• typing

[Freenex1911]

I can confirm, having the same issue with 1.0.200.

[oddpixel]

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.

[TheBlueKnight42]

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.

[YouthInThinking]

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.

[Eugeny]

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).

[oddpixel]

@Eugeny just did some testing and the issue goes away when I uncheck "Disable GPU acceleration" in settings.

Version: 1.0.200
Platform: Windows x64 10.0.19045
Plugins: none
Frontend: xterm-webgl

[YouthInThinking]

@Eugeny just did some testing and the issue goes away when I uncheck "Disable GPU acceleration" in settings.

Version: 1.0.200 Platform: Windows x64 10.0.19045 Plugins: none Frontend: xterm-webgl

I'd like to wait for a complete official fix for this bug before upgrading.

[Eugeny]

"Disable GPU" is off by default - is there a reason why you've enabled it?

[L-Super]

"Disable GPU" is off by default - is there a reason why you've enabled it?

I tried to off or on Disable GPU, but the phenomenon still exists.
version: 1.0.200

[momodezhou]

I can confirm, having the same issue with 1.0.200.

[Plasmagun86]

I have the same issue on 1.0.200 but It seems that it occurs only on the first tab.
I often use 2 or 3 tab in tabby and the issue seems to occur only on the first one, if i close it, the issue seem to be gone.
I hope it will help.

[L-Super]

I have the same issue on 1.0.200 but It seems that it occurs only on the first tab.
I often use 2 or 3 tab in tabby and the issue seems to occur only on the first one, if i close it, the issue seem to be gone.
I hope it will help.

I'm not. Each of my tabs has this problem.

[YouthInThinking]

I have the same issue on 1.0.200 but It seems that it occurs only on the first tab.
I often use 2 or 3 tab in tabby and the issue seems to occur only on the first one, if i close it, the issue seem to be gone.
I hope it will help.

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.

[TheBlueKnight42]

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
Possible Workaround

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.
-- Blue

GitHub

GitHub - Eugeny/tabby: A terminal for a more modern age

A terminal for a more modern age. Contribute to Eugeny/tabby development by creating an account on GitHub.

[momodezhou]

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 Possible Workaround

After some testing I have consistent results for you to try.

I used Oracle VirtualBox 7 (7.0.10-158379Ubuntujammy) 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. -- Blue

GitHub**GitHub - Eugeny/tabby: A terminal for a more modern age**A terminal for a more modern age. Contribute to Eugeny/tabby development by creating an account on GitHub.

it still has the problem when i jump to remote machine by ssh.
my machine info:
Linux xuan 6.2.0-26-generic #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Jul 13 16:27:29 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

GitHub

GitHub - Eugeny/tabby: A terminal for a more modern age

A terminal for a more modern age. Contribute to Eugeny/tabby development by creating an account on GitHub.

[momodezhou]

I can confirm, having the same issue with 1.0.200.

it still has the problem when i jump to remote machine by ssh.
my machine info:
Linux xuan 6.2.0-26-generic #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Jul 13 16:27:29 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

[arakis]

I also made this observation in some situations even in 1.0.197, but also:

• When connecting to SSH (from Windows/Powershell to Linux/zsh) and then returning, then calling Terraform on Windows, I can't even see the characters (to confirm "y-e-s" in Terraform). It doesn't even react anymore, not even to CTRL+C. This means I need to kill the terraform.exe process from Task Manager. This always happens only if I connected via SSH before.

It seems to be a different issue, but might have a relation to this one.

[hangingman]

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.

[pilotcy]

I can confirm, having the same issue with 1.0.200.

[yigeyanse]

I also have the same issue with 1.0.200 version , please fix it.

[Clem-Fern]

Hey, I encoutered this issue too.

Errors seen in debug console at the time of the issue :

[23917:0920/204639.014464:ERROR:gl_utils.cc(402)] [.WebGL-0x1c5806ae9500]GL Driver Message (OpenGL, Performance, GL_CLOSE_PATH_NV, High): GPU stall due to ReadPixels
[23917:0920/204639.095657:ERROR:gl_utils.cc(402)] [.WebGL-0x1c5806ae9500]GL Driver Message (OpenGL, Performance, GL_CLOSE_PATH_NV, High): GPU stall due to ReadPixels
[23917:0920/204639.192432:ERROR:gl_utils.cc(402)] [.WebGL-0x1c5806ae9500]GL Driver Message (OpenGL, Performance, GL_CLOSE_PATH_NV, High): GPU stall due to ReadPixels
[23917:0920/204640.121306:ERROR:gl_utils.cc(402)] [.WebGL-0x1c5806ae9500]GL Driver Message (OpenGL, Performance, GL_CLOSE_PATH_NV, High): GPU stall due to ReadPixels (this message will no longer repeat)

It seems to be a bug with WebGL and chromium. Switching to xterm (canvas) in Settings > Terminal > Rendering > Frontend like suggested by @momodezhou is definitely the good workaround.

@Eugeny, it's a bit out of my league and I didn't get the time to look into it more deeply but here's what I found:
webgl regression: may not render as typing xtermjs/xterm.js#4665
Text is not rendering when typing in terminal microsoft/vscode#190195
tracking Chromium bug (https://bugs.chromium.org/p/chromium/issues/detail?id=1476475)

From what I understood, VSCode temporarily fixed this by conditionally switching from webgl to canvas (microsoft/vscode#191795)

1476475 -

chromium -

An open-source project to help move the web forward. -

Monorail

[Dgiannot]

I also am having the same issue. Rolled back to 1.1.197 as workaround

[robpomeroy]

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.

[arakis]

To be honest, i'm also using tabby (only) on VM/RDP, because Windows 2022 (cloud) installations can't install Windows Terminal.

[gitthangbaby]

Thanks for suggestions. My consoles broke after some time: 1) cursor disappeared 2) mouse produced letters 3) typed text invisible.

[andylau004]

I rolled back to 1.0.197

big trouble ---> 1.0.200

[Issues-translate-bot]

The translator bot has detected that this issue body's language is not English, and has translated it automatically.

---

I rolled back to 1.0.197

big trouble ---> 1.0.200

[Eugeny]

It's fixed in v201

[gitthangbaby]

thanks. I have the same problems in (canvas) mode and in v201:
today i click on some panes and it interprets mouse click and mouse scroll like this, and cursor gone:
$ 0;37;36M0;37;36m0;51;35M0;51;35m0;51;35M0;51;35m0;51;35M0;51;35m0;53;35M0;53;35mjjkl0;72;0;
This behavior is way more frequent than missing text. So it's another issue then.
Found quick steps to reproduce:
Just run any interactive app per #7058 and CtrlShiftR. The pane cannot be fixed other than by closing it.

update: i'm still getting the variation of this issue in v201-v205. it's a tripple frustration at the moment:
① the cursor is there and it doesn't move when typing. the characters are not visible, but they are added to hidden command line. #8884
② another issue from #7058, is where cursor disappears, but i can type characters which are visible. but i don't know where i'm in the command line, editing is also horrible. mouse drops weird characters.
③ not able to copy from midnight commander in a simple shell is a very tough situation #7273 #9215.
④ find dialog inserting keyword to the clipboard #9196 and overlaps with the minimize/maximize/close buttons

[gitthangbaby]

I rolled back to 1.0.197

big trouble ---> 1.0.200

^ this is the resolution. i've copied 197 tab-terminal and tab-ssh folders to the 205 version to mitigate this. All other issues above remain in 205 gl/canvas.