For the past couple of months or so, I’ve been experiencing a problems with my waking up my acer Spin 5 from sleep mode. I’ve noticed that when I let it go to sleep mode (or hibernate), sometimes it would not manage to boot up again.
I’ve managed to track the issue when syncthing is up and running.
Syncthing version: 1.12 operating system: Windows 10 home (fully patched)
When I start syncthing and I leave it running, if the computer goes into sleep mode/hibernation then it is not possible to wake it up. What happens is that the keyboard lights up (as it should), but there is no other response from the system.
The only way to get the computer operational again, is to press the power button for a few minutes (hard reset) and then restart it.
That behavior only happens when I have syncthing running. I’ve tried that (see below).
More details on how I came to the conclusion
Initially, I thought it was some sort of corruption through the updates of windows. I’ve had the Acer Sping 5 for 3 years, and it worked with syncthing without a problem all this time. I need to note that because the Spin5 is my carry around laptop, to save some time during boot, i’ve had syncthing disabled at boot, and occasionally I start it up. However, I never had a problem before (I use syncthing to sync between at least 5 pc’s and various operating systems without a problem). That is the reason, why I didn’t suspect syncthing earlier.
At some point about a couple of weeks ago, I decided to refresh the Windows 10 installation to see if that fixed things. I did the full refresh, and I slowly started to add things. Then last week the same problem happened (I would try to boot windows from sleep mode, but nothing happened apart from the keyboard lighting up). For the past week, I’ve avoided using syncthing, and the behaviour was as expected. Then yesterday, I rebooted the computer, started syncthing, and then let it go to sleep mode, and I couldn’t start it again (as I’ve mentioned above I have to use the power button to power down the pc and then restart it).
The only workaround I’ve found so far is to shutdown syncthing whenever I don’t use the computer.
Does anyone have a similar problem?
Can anyone help, with verifying/understanding/pinpointing what the problem is from the logs on Windows/syncthing, so that I can post a proper bug issue.