jramboz / tintalle

Python/Qt-based application for managing OpenCore-based lightsabers
5 stars 1 forks source link

Blank screen after install on Windows #18

Open jramboz opened 2 weeks ago

jramboz commented 2 weeks ago

From Discord:

Monster (Tom) — Today at 9:21 AM Hey Jason Running into some fun issues trying to get the program to load.

Installed it in 3 locations: Home desktop (Win 10) Private laptop (Win 11) Work laptop 🤫 (Win 10)

It runs correctly after launching on my home desktop (unfortunately don't have access to that right now for checks). The other two will launch it, and then the program hangs (non-responsive), and will not progress past the first screen.

I've done a clean installation (as an admin) on both laptops, restarted each devices, uninstalled the file, restarted again, done another clean install, but I get the same results.

Are there any known issues around file pathways causing the program not to run? I've tried program files, as well as program files (x86) and program data. It doesn't make a difference.

image

Another user - Kaiser (Franz) - reported the same issue, on Windows 11.

jramboz commented 2 weeks ago

Possibly relevant: https://stackoverflow.com/questions/44333839/application-does-not-work-when-installed-with-inno-setup

jramboz commented 2 weeks ago

I had Tom try to run the app as Administrator -- he said the same thing happened. I've sent him and Franz a Windows build of 0.5.2 in a zip file (i.e., without installer) to see if that runs. That should help me narrow down whether it's an installer problem or not.

jramboz commented 1 week ago

Tom said that the non-installer build had the same problem. So it seems unlikely to be an installer issue.

My next theory is that it's a problem with the pyinstaller packaging. Some googling in this direction points to upx as a possible culprit. I've disabled upx in the windows .spec file, re-built, and sent to Tom for testing.

jramboz commented 1 week ago

No luck. There also didn't seem to be any noticeable different in the file size generated without upx. Tom is willing to try installing Python and running the app from the source. So that will be the next step. If that works, then it's a pyinstaller issue.

jramboz commented 1 week ago

Tom reported that running direct from code had the same issue. However, per the screenshot, it seems that it is initializing and running -- just that the UI is not responding. image

jramboz commented 1 week ago

I wrote a minimal UI and sent that to Tom to test. That worked on his machine just fine. So I don't think it's a basic problem with PySide/Qt.

My guess is it has something to do with how I'm doing multi-threading/asyncio. Admittedly, this is a mess right now--I was learning a lot as I was going, and I don't think PySide6 even had inbuilt support for asyncio when I started. I'm going to explore re-writing everything to use PySide6.QtAsyncio--which will probably also require some changes to py2saber as well.