Mist: Ethereum wallet fails to connect to geth with no accounts set in keystore

[winsvega]

Version: `0.9.0` OS & Version: linux Node type: `geth` Number of blocks synchronized: light

Error starting up node and/or syncing TypeError: Cannot read property 'timestamp' of undefined

[PatchRanger]

Confirming.
The blockchain looks synchronized - and it continues updating. While accounts are totally not working at all:

• My old accounts were not loaded into.
• I have the only Etherbase account with 0 ETH in it.
• There is no accounts to choose from at New Contract screen: the select is simply empty, no option at all.

[cryzed]

Same proplem here, I would also like to see this fixed, as Mist is currently unusable for me: the full synchronization takes too long and the light synchronization is broken. However, even updating Geth to 1.6.7, as planned in the referenced issue, doesn't seem to fix the problem: at some point the Mist client throws the described error and the synchronization in geth slows to a crawl (a single block header every few seconds, instead of hundreds).

[winsvega]

to resolve the error I described, you could just manually add a private key to the keystore folder.

[cryzed]

Oh, I do have an account there, and geth even lists it -- I still get the error when attempting to synchronize the block chain in light mode when using mist. Towards the very end of the process an error is raised and geth's synchronization has a count of 1 every so often.

[winsvega]

This error message Error starting up node and/or syncing TypeError: Cannot read property 'timestamp' of undefined comes from the Mist. so it is not the issue in synchronization of geth.
Try syncing geth standalone and then run Mist

[cryzed]

That seems to have worked, thank you.

[PatchRanger]

Thanks to the suggestions above, I was able to workaround the timestamp issue with this: I've replaced a comand under Myth icon from

"/opt/Mist/mist"

to

bash -c "geth --syncmode light --cache 512 --verbosity 4 & sleep 30 && /opt/Mist/mist"

Note that in one case single & is used while in the other - double (&&). Myth now starts successfully. But nevertheless the issue with accounts is still valid. I am going to somehow apply the @winsvega's workaround: to manually add a private key to the keystore folder.

[PatchRanger]

I've checked: keystore is not empty in my case.

Assuming that this concrete issue is dedicated to timestamp issue, I've created a new issue for my own case: #2938.

[HaleTom]

I noticed that geth was complaining with:

ERROR[09-29|13:00:24] Failed to retrieve current release       err="can't fetch trie key 5380c7b7ae81a58eb98d9c78de4a1fd7fd9535fc953ed2be602daaa41767312a: no suitable peers available" 

What worked for me was to:

1. Shutdown geth
2. geth removedb
3. Restart geth

This solved Mist's timestamp error for me.

[evertonfraga]

This is probably fixed, due to the combination of the huge refactor we did + several geth updates.
Please feel free to reopen should you still have some considerations about it.