Skip to content
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

Cannot click in the main window with v .209 #9775

Closed
Chrismarsh opened this issue Jul 10, 2024 · 9 comments
Closed

Cannot click in the main window with v .209 #9775

Chrismarsh opened this issue Jul 10, 2024 · 9 comments
Labels

Comments

@Chrismarsh
Copy link

Describe the problem:

I updated to 209 and now clicking in the window (to start a new connection, for example) does nothing.

I deleted the config, and I was able to click through the on-board preference setup. However, after that, click does nothing.

This is on Windows 11

To Reproduce:
Version: 1.0.209
Platform: Windows x64 10.0.22631
Plugins: none
Frontend: xterm-webgl

@Eugeny
Copy link
Owner

Eugeny commented Jul 10, 2024

Please capture DevTools console logs at the time of the issue: https://github.com/Eugeny/terminus/wiki/Debug-logs

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

@Chrismarsh
Copy link
Author

Beyond strange. As soon as I launched it with --inspect the problem has gone away and has stayed away. I note that I had to use --inspect as --debug was flagged as deprecated and wouldn't do launch the program.

@tomasz2048
Copy link

tomasz2048 commented Jul 11, 2024

This happens to me too on two different machines: in 1.0.209 I can't open new tab, profiles&connections or config.
I can switch between tabs that were saved from last session from before 208->209 update.
Starting with --inspect did not help. Can't get to DevTools.
Had to revert to 208.

@Chrismarsh Chrismarsh reopened this Jul 11, 2024
@Chrismarsh
Copy link
Author

Chrismarsh commented Jul 11, 2024

Reopened based on @tomasz2048. Does --inspect let you debug it as per @Eugeny 's suggestion? What you're describing is exactly the behaviour I saw that suddenly went away.

@tomasz2048
Copy link

tomasz2048 commented Jul 11, 2024

I'm getting inconsistent behavior, 2 different scenarios [2a and 2b is probably a matter of some random length timing...]:

  1. sometimes can open new tabs/profiles/settings all the time until I close the app
    2a. sometimes can open new tabs/profiles/settings only for a few seconds after app startup,
    2b. sometimes can't open tabs/profiles/settings at all from the start.

I don't see any errors in DevTools console after running with --inspect

I see some errors in CMD from where I run it with --inspect flag:
but those show up even in scenario when I can open new tabs permanently during app run

PS C:\dev> C:\Users\tomas\AppData\Local\Programs\Tabby\Tabby.exe --inspect
PS C:\dev>
Debugger listening on ws://127.0.0.1:9229/e3c36656-7834-4c7b-92e7-4ab050465ff4
For help, see: https://nodejs.org/en/docs/inspector
[Glasstron/DWM] Trying to load the native module...
[Glasstron/DWM] Native module loaded
(node:90280) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(Use Tabby --trace-deprecation ... to show where the warning was created)
Checking for update
Update for version 1.0.209 is not available (latest version: 1.0.209, downgrade is disallowed).
[88384:0711/153326.615:ERROR:jump_list.cc(300)] Failed to append custom category 'Recent' to Jump List due to system privacy settings.
[88384:0711/153326.647:ERROR:jump_list.cc(300)] Failed to append custom category 'Profiles' to Jump List due to system privacy settings.

Node.js® is a JavaScript runtime built on Chrome's V8 JavaScript engine.

@JamesDBartlett3
Copy link

I just upgraded to Tabby v1.0.209 today, and I started experiencing this same bug immediately after the upgrade.

If I launch Tabby with the --inspect argument, it will start up normally and open a new PowerShell tab, but only about ⅓ of the time. The other ⅔ of the time, it just hangs on this screen:
image
I can click on the buttons, and they do their little "I've been clicked!" animation, but nothing else happens. The only buttons that actually work are minimize, maximize, and close. I can also show/hide the window using the "Toggle terminal window" hotkey, but that's not very useful if the rest of the app is frozen. 😜

@GuangDai
Copy link

I just upgraded to Tabby v1.0.209 today, and I started experiencing this same bug immediately after the upgrade.

If I launch Tabby with the --inspect argument, it will start up normally and open a new PowerShell tab, but only about ⅓ of the time. The other ⅔ of the time, it just hangs on this screen:如果我用 --inspect 参数启动 Tabby,它将正常启动并打开一个新的 PowerShell 选项卡,但只有大约 ⅓ 的时间。其余 ⅔ 的时间,它只是在此屏幕上挂起: image I can click on the buttons, and they do their little "I've been clicked!" animation, but nothing else happens. The only buttons that actually work are minimize, maximize, and close. I can also show/hide the window using the "Toggle terminal window" hotkey, but that's not very useful if the rest of the app is frozen. 😜我可以点击按钮,它们会做它们的小"我被点击了!"动画,但没有其他事情发生。唯一真正有效的按钮是最小化、最大化和关闭。我也可以使用"切换终端窗口"热键来显示/隐藏窗口,但如果应用程序的其余部分都被冻结,这并不太有用。😜

Same. I am using Archlinux KDE. Maybe arch is too new?

@fgpetter
Copy link

Same problem here, it seems that process wont end when you close the window. When I tried to uninstall (windows), it shows a message that Tabby is active and I have to close before uninstall. I had to reboot and uninstal to rollback to 208.

@Eugeny
Copy link
Owner

Eugeny commented Jul 18, 2024

Duplicate of #9787

@Eugeny Eugeny marked this as a duplicate of #9787 Jul 18, 2024
@Eugeny Eugeny closed this as not planned Won't fix, can't repro, duplicate, stale Jul 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants