Describe the issue:
Bitcoin-Qt freezes on start-up, giving two transparent windows. I suspect it’s related to my system clock changing (more details below). This means the issue is not caused by the Bitcoin Core software but, I’m submitting it anyway because the error could maybe be catched and handled more graciously. Even crashing in a secure way would be better: when this happens I’m kinda scared to kill the process and mess the blockchain.
What behaviour did you expect?
Bitcoin-Qt should start normally.
What was the actual behavior (provide screenshots if the issue is GUI-related)?
The program freezes giving a transparent Bitcoin Core window and another transparent Bitcoin - Warning window. Screenshot for reference:
How reliably can you reproduce the issue, what are the steps to do so?
When I start my computer on linux after I’ve been using windows (it’s dual boot), the OS changes the system clock seconds after entering the desktop, syncing with some internet time server. Around 30% of the times, this produces the issue. I suspect the time change in the middle of the initialization makes the software freak out.
It should also occur with any other kind of use that makes the system clock change inmediatly after boot but I mention this details because I think it’s a very common use case. I think I could try to manually reproduce the error consistently by changing the system clock on the BIOS if needed.
What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)?
I believe I installed it from my package manager. It was either that or downloaded from website.
What type of machine are you observing the error on (OS/CPU and disk type)?
uname -a says: Linux [removed host name] .0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
For the GUI-related issue on Linux provide names and versions of a distro, a desktop environment and a graphical shell (if relevant).
Linux Mint 19 Mate 64-bit
Any extra information that might be useful in the debugging process.
Logs confirm it’s clock related: https://pastebin.com/ni7bWgL9
I understand that this issue occurs in very very specific circunstances and it’s ok if fixing it is not a priority. If you consider this to be important and it could use a fix, I would be happy to try to investigate it further and submit a PR.
Thanks for reading and for the hard work mantaining this.