Closed DandelionSprout closed 1 year ago
Although I acknowledge that the issue appears to not have occured to many people, I presume that limiting ElevenClock to one instance at a time would hopefully fix it.
This issue is caused due to the inability of the multiple instance handler to close other instances. This faillure is commonly caused by permissions on the .elevenclock folderplaced in your user directory, so please navigate there and delete any ElevenClockRunningXXXXXXXXX file.
P.D. The issues with the domain are happening because freenom has had issues with servers and they have lost lots of records, and won't allow registering new domains.I fixed this on v4.0, but, since the old domain is down, the updater does not work,so please update manually to version 4.0. v4.0 and newer depend on a .com domain registered with google, so there shouldn't be further issues
Please let me know if this fixes the issue
Strangely, the Microsoft Store page seems to install 3.9.3 on initial installation instead of anything newer, but I've installed 4.0.0 from GitHub now. I'll see if I can remember to let you know about any news after I've tested it for 1~4 days.
Yes, microsoft store is still reviewing version 4.0, and until they publish v4.0 3.9.3 will be the latest version available
I have upgraded elevenclock to version 4.0 but this issue still exists.
Hi, may I ask you how did you upgrade to version 4.0.X?
Okay, so it ended up taking me 3 weeks to test (ElevenClock would simply create new ElevenClockRunning files each day after I had deleted the previous one), as I could only test new approaches once a day, but I think (pressure on "think") that turning on "Enable silent updates" fixes it.
@marticliment https://github.com/marticliment/ElevenClock/releases
@DandelionSprout, it should not be related, but if it really fixes the issue, please let me know.
@oubeichen, have you ever ran ElevenClock or the installer with administrator rights?
Okay, so you were right that my "update check" theory was wrong, as not even turning off ElevenClock updates entirely could fix it.
My current theory is something related to when Windows enters sleep mode, with the area marked in orange below being files that were specifically changed by the OS circa around the time my PC last entered sleep mode this morning:
Could you please test this beta build?
https://github.com/marticliment/ElevenClock/releases/download/4.1.0-beta/ElevenClock.Installer.exe
Although I was a bit distracted in the past month, the problem seems to be gone/fixed as of 4.1.0 stable on my end.
Before submitting the issue
Describe the bug
For reasons I've struggled surprisingly much to figure out for some weeks, ElevenClock opens up a 2nd instance approx. once a day (Most likely after update checks), causing a flashing/lag effect on the clock, as can be seen in the animated screenshot below.
To Reproduce
Steps to reproduce the behaviour:
1) Install ElevenClock. 2) Set ElevenClock to start up on system boot. 3) Ensure that "Look for updates automatically" is turned on. 4) Ensure that the seconds counter is turned on. 5) Ensure that the ElevenClock language is set to Norwegian (BokmΓ₯l). 6) Wait up to 24 hours. 7) The clock's background will begin to flash, and sometimes have an odd lag effect for the seconds counter.
Expected behaviour
ElevenClock does not flash or lag.
Screenshots
https://user-images.githubusercontent.com/22780683/213908615-7aaba8e3-f3fd-4b32-8644-43ebed47da18.mp4
The Log
Additional context
Although I acknowledge that the issue appears to not have occured to many people, I presume that limiting ElevenClock to one instance at a time would hopefully fix it.
As an aside note, I notice in the log above that all references (if any) in ElevenClock's code to
somepythonthings.tk
should be removed as soon as feasible, since domains that start with numbers betweenww5.
andww50.
can be assumed to have elapsed and bought by SEO/malware spreaders (Even more so when using the .tk TLD), and a quick Google search forsomepythonthings.tk
seems to confirm my thoughts about it.