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

Windows version Tabby 1.0.216 stuck on startup #10141

Closed
feym78 opened this issue Dec 31, 2024 · 10 comments
Closed

Windows version Tabby 1.0.216 stuck on startup #10141

feym78 opened this issue Dec 31, 2024 · 10 comments
Labels

Comments

@feym78
Copy link

feym78 commented Dec 31, 2024

Describe the problem:
Cannot run Tabby 1.0.216 on fresh install windows 11, it just stucks on load screen. Saw same issues with mac version and it looks like it was fixed, but still cant run it on windows 11 with Ryzen HX 370.
Tried to install previos version 1.0.215 and it starting fine, but fresh install of 1.0.216 or upgrade to 1.0.216 doesn't work.

To Reproduce:
Install Tabby 1.0.216 on windows 11.

@feym78 feym78 added the T: Bug label Dec 31, 2024
@Eugeny
Copy link
Owner

Eugeny commented Jan 1, 2025

Please reinstall it from the Releases page here. I've already swapped the installer for a fixed one a few days ago.

@Eugeny Eugeny closed this as completed Jan 1, 2025
@feym78
Copy link
Author

feym78 commented Jan 1, 2025

@Eugeny Happy New Year :)
Looks like it is not working, just downloaded installer from release page before submitting this issue, so it should be actual but still doesn't work.
Used file tabby-1.0.216-setup-x64.exe, installed in user space.

@Eugeny Eugeny reopened this Jan 1, 2025
@Eugeny
Copy link
Owner

Eugeny commented Jan 1, 2025

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.

@Ray-D-Song
Copy link

The same problem, stuck here, and I can't open devtools with the shortcut key.
On Windows, .\tabby --debug is also invalid.
image

@Ray-D-Song
Copy link

I tried downloading version 1.0.215 and it successfully started.

@nagastone
Copy link

And i stuck on startup in Windwos Server 2012

@vecinohk
Copy link

vecinohk commented Jan 3, 2025

@Ray-D-Song @nagastone + all:

You need to install the last one Microsoft Visual C++ Redistributable Version .

You only need the x64 version, but you can't go wrong with an x86 installation.

x64 - https://aka.ms/vs/17/release/vc_redist.x64.exe
x86 - https://aka.ms/vs/17/release/vc_redist.x86.exe

Then Tabby works in version 216. I had this problem too, but I understood that I was missing Visual C++ Redistributable. Previous versions did not require it.

@Invisi
Copy link

Invisi commented Jan 4, 2025

Running 1.0.216-portable-x64 on Windows 11 22631.4602, was able to get a debug log via --inspect:

[Glasstron/DWM] Trying to load the native module...
[Glasstron/DWM] Native module loaded
(node:61308) [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
thread 'tokio-runtime-worker' panicked at C:\Users\runneradmin/.cargo\registry\src\index.crates.io-6f17d22bba15001f\pageant-0.0.1-beta.3\src\pageant_impl.rs:64:75:
called `Result::unwrap()` on an `Err` value: WindowsError(Error { code: HRESULT(0x800703E6), message: "Invalid access to memory location." })
stack backtrace:
   0:     0x7ffaece9855b - napi_register_module_v1
   1:     0x7ffaecd3eee9 - napi_register_module_v1
   2:     0x7ffaece81c41 - napi_register_module_v1
   3:     0x7ffaece9a9a6 - napi_register_module_v1
   4:     0x7ffaece9a278 - napi_register_module_v1
   5:     0x7ffaece9b32f - napi_register_module_v1
   6:     0x7ffaece9abf7 - napi_register_module_v1
   7:     0x7ffaece9ab3f - napi_register_module_v1
   8:     0x7ffaece9ab28 - napi_register_module_v1
   9:     0x7ffaeceba4b4 - napi_register_module_v1
  10:     0x7ffaeceba970 - napi_register_module_v1
  11:     0x7ffaecdace49 - napi_register_module_v1
  12:     0x7ffaecdaa76d - napi_register_module_v1
  13:     0x7ffaecea88ed - napi_register_module_v1
  14:     0x7ffaecead40b - napi_register_module_v1
  15:     0x7ffaece9ee4f - napi_register_module_v1
  16:     0x7ffaece9ec56 - napi_register_module_v1
  17:     0x7ffaece95add - napi_register_module_v1
  18:     0x7ffbb60a259d - BaseThreadInitThunk
  19:     0x7ffbb700af38 - RtlUserThreadStart
Error: Error: Cannot find latest.yml in the latest release artifacts (https://github.com/Eugeny/tabby/releases/download/v1.0.216/latest.yml): HttpError: 404
"method: GET url: https://github.com/Eugeny/tabby/releases/download/v1.0.216/latest.yml\n\nPlease double check that your authentication token is correct. Due to security reasons, actual status maybe not reported, but 404.\n"
[snip]

Killing gpg-agent results in a different error:

WindowsError(Error { code: HRESULT(0x80072733), message: "A non-blocking socket operation could not be completed immediately." })

Notable differences from default setups:

  • there are some old sessions in Tabby that automatically reconnect on launch
  • I'm running gpg-agent instead of ssh-agent, though that shouldn't make a big difference as it's the same pipe: \\\\.\\pipe\\openssh-ssh-agent

@feym78
Copy link
Author

feym78 commented Jan 4, 2025

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

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

Hi.
Today I tried to update version from 215 to 216 to check dev logs but after upgrade it worked... I don't know why, nothing changed in my end.
BUT now when I close tabby I'm getting VC++ error:
image
Thing is that I don't have disk D mentioned in the error.
I tried to update VC++ redist as @vecinohk mentioned but it didn't help - same error after closing the app.

In message above there is also some strange text about runner in the error.
I think may be there was some error with building exe files for 216 version.

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

@Eugeny
Copy link
Owner

Eugeny commented Jan 6, 2025

The startup issue is now fixed in the nightly - the assertion error will be tracked in #10134

@Eugeny Eugeny closed this as completed Jan 6, 2025
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