Windows version not fully launching
h0kay opened this issue · comments
Bug report, debug log and your config file (FULL LOGS ARE MANDATORY)
Steps to reproduce
What is expected?
What is actually happening?
I installed the latest version of HyperHDR (HyperHDR-20.0.0.0beta1-Windows-AMD64.exe) on a Windows 10 machine that never had it installed, and it worked flawlessly. The next time I turned my computer back on, I attempted to launch it, and I noticed the system tray icon did not appear. Although the tray icon was not present, I saw it in my running processes, and noticed it turned my lights on.
I attempted to access the web interface, however, I got a blank screen on any menu item I clicked on, which prevents me from getting a log file:
I went through the uninstall process, restarted, reinstalled, and experienced the same exact issue. Even though I did an uninstall and verified the contents in C:\Program Files\ were removed, my previous settings were still being used because again, my lights turned on after launching, but the same issues persisted.
I looked around in my computer and noticed a folder called ".hyperion" under C:\Users\Username, which contained a database file. I made a copy of this folder and then removed it, and after launching Hyperion again, everything worked as it should. The task tray was visible, and the web interface worked once again. Of course my settings are no longer there, but because of this I'm wondering if the uninstaller should perhaps remove this settings database file as it appears it has the ability to become corrupt and prevent future instances being ran, even after a fresh reinstall.
System
Hi
I looked around in my computer and noticed a folder called ".hyperion" under C:\Users\Username, which contained a database file
we definitely do not use this folder. Maybe you tried to use the other software simultaneously? The conflict of resources is almost guaranteed.
In any case in the future: kill the process in the task bar and run hyperhdr.exe -c
without logs I cannot help
Hi
I looked around in my computer and noticed a folder called ".hyperion" under C:\Users\Username, which contained a database file
we definitely do not use this folder. Maybe you tried to use the other software simultaneously? The conflict of resources is almost guaranteed.
In any case in the future: kill the process in the task bar and run hyperhdr.exe -c
Good catch, one thing I forgot to mention is that I also have Hyperion installed, which causes the .hyperion folder to be created, but HyperHDR creates the .hyperhdr folder in the C:\Users\Username folder. I don't have both instances running however, and don't have either of them set to launch on startup. Since I can't get to the log files though I'm just reviewing the old database vs the new one in an online SQL viewer to see if there's anything that stands out, but so far nothing too odd looking.
Hi
I looked around in my computer and noticed a folder called ".hyperion" under C:\Users\Username, which contained a database file
we definitely do not use this folder. Maybe you tried to use the other software simultaneously? The conflict of resources is almost guaranteed.
In any case in the future: kill the process in the task bar and run hyperhdr.exe -c
Sorry I missed this message, here you go:
[logs]
These logs are taken after you tried to connect using web browser?
Could not start the SSDP server
that could be the problem, maybe it's something in your Windows configuration (custom firewall or conflict of resources?) or it's something else. Please attach your configuration file if it's possible then I take a look.
These logs are taken after you tried to connect using web browser?
Could not start the SSDP server
that could be the problem, maybe it's something in your Windows configuration (custom firewall or conflict of resources?) or it's something else. Please attach your configuration file if it's possible then I take a look.
The log was before accessing the web browser I believe, but, I went ahead and deleted the database file, which forced it to create a new one, and that results in HyperHDR working.
Looking at the logs on the web interface now, still appears to show the same error message about the SSDP server, even though things seem fine. Here's a copy of the bad database file:
[removed]
And below is the most recent log of the working instance, after wiping out the database and forcing it to create a new one:
[logs]
Thank you. Could you check if bad config behaves the same way if WLED device is powered off?
Same behavior from last time, I ran it normally the first time, then killed the process, and ran it with the -C command to generate the log shown below. The only thing I can think of that has changed since the last time it worked, was my local IP updated, not sure if that would cause an issue or not.
[logs]
I was able to achieve an identical effect in my environment with your configuration. The problem was the music effect set as the background. This is the most serious bug found in v20beta1 so far. I would like to ask you to test the installer from this build: https://github.com/awawa-dev/HyperHDR/actions/runs/7833456861
Tested this out with my original database, confirmed everything is working without issues now, thank you!