-
-
Notifications
You must be signed in to change notification settings - Fork 68
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
vNext v0.8.0 win x64 only shows spinner #268
Comments
Thanks for reporting. Do you see the same issue if you use the installer (.exe) instead of the zip file? |
MSI: requires elevation to admin privileges, so sorry, cannot test that. |
Same here via the win64 MSI installer. The spinner does eventually timeout with the message:
Looking in the event log I saw I was missing a runtime dependency:
I uninstalled Netpad & installed the missing framework but I still get stuck on the spinner => timeout message. |
The .exe installer actually runs in user mode and is configured to only do user installs. So if you haven't already tried it, give it a shot. Besides that, here are some things to try:
|
@AlexKeene thank you for reporting. I'll check this out. |
Same thing here with the .deb package on Linux Mint 21.3; after a while it times out with:
Regular v0.8.0 package installs / runs normally. System: |
@sjsepan3 can you try installing .NET 6 runtime or sdk and see if that fixes the issue for you? |
6.0 SDK is already on my system. Also, just decided to follow your advice to @AlenKeene and run from terminal, and got output below, followed by app starting OK (that is after failing 3 times starting from menu.). Starting from menu again still times out...but starting from terminal again still works.
|
Output from 3rd run from terminal ( Note: the & is so I get back control at the terminal, but the previous runs from the terminal, which also worked, were without the &, so that doesn't affect it. I cannot tell why running from the menu entry ( @tareqimbasher UPDATE: the linux menu editor has an option to "Launch in Terminal", but when checked (it is not by default) it still times out. So, still somehow different than manually running in terminal (bash). sjsepan ~ v20.15.0 06:16 [2024-10-02][10:16:39][app_lib::dotnet_server_manager][INFO] Starting .NET server backend at path: '/usr/lib/NetPad vNext/resources/netpad-server/NetPad.Apps.App' with working dir: '/usr/lib/NetPad vNext/resources/netpad-server'
|
Thank you for the details. I'll take a look and see what's going on. @sjsepan3 is the AppImage giving you the same experience? |
I will try it out tomorrow and let you know ... @tareqimbasher OK, so the same vnext AppImage exhibits that dual behavior: when run from the desktop launcher in the menu( UPDATE: so I can start the app from the terminal at ~ (home/username) with |
Thanks @sjsepan3 for the update. It must be having a problem getting the path where it's located. |
I double-click the executable after extraction from the x64 zip archive (unblocked first). The window launches full-screen, I get to see a spinner in the middle and that's it.
Windows 10 with latest patches. "Normal" 0.8.0 starts just fine.
The text was updated successfully, but these errors were encountered: