Electrum GUI does not start update update 2.8.2 -> 2.8.3 on Ubuntu Linux

[arberg]

Hi,

I ran

sudo pip2 install https://download.electrum.org/2.8.3/Electrum-2.8.3.tar.gz

I could see from its messages that it uninstalled my 2.8.2 version and then installed 2.8.3.

After updating and running electrum command, the electrum GUI was not shown, the command just hung. If I C-c it says

Traceback (most recent call last):
  File "/usr/local/bin/electrum", line 374, in <module>
    fd, server = daemon.get_fd_or_server(config)
  File "/usr/local/lib/python2.7/dist-packages/electrum/daemon.py", line 63, in get_fd_or_server
    server = get_server(config)
  File "/usr/local/lib/python2.7/dist-packages/electrum/daemon.py", line 85, in get_server
    time.sleep(1.0)
KeyboardInterrupt


If I move .electrum away and start it up immediatly, it looks good, but of cause no wallet data. I copied .electrum/config and .electrum/wallets from old and then it started up immediately. Initially it showed my transactions as unverified, then after a few minutes it looked good.

Is this a bug I should report on the GitHub tracker?

Regarding the install:
It complained about some missing /home/user/.cache/pip/http so I can it again several times, then ended up reading what it said and running sudo with -H. I think this just means it didn´t cache the download in /root/.cache/pip, but anyway I wanted to mention it.

Best Alex

sudo -H pip2 install https://download.electrum.org/2.8.3/Electrum-2.8.3.tar.gz

Not that

[Abdussamad]

Yes this is a bug. Sometimes the blockchain_headers file gets corrupted. If you want to pursue the matter you can post a bug report about it on github. But first see if you can reproduce it by replacing the blockchain_headers file with the corrupt one and running electrum.

[pooya87]

i had this problem a couple of times so far, the first one was the blockchain_headers file but it was a long time ago with an old version.
the newer problem was with the config file. i never figured out where the problem was coming from, but i think it was the "gui_last_wallet" or "recently_open" variables in it.

if you want to reproduce it make sure you have replaced the newly generated config file with your old one and see if the problem persists.