[Pkg-bitcoin-devel] Bug#803949: Bug#803949: electrum: Electrum unable to start; Cannot read config file

[s7r]

Hello,

That is right. You should use 2.5.2 or newer - 1.9.8, aside the fact
that it uses only old version seeds, it won't be able to sign a
transaction and broadcast it to the network because it doesn't contain
the low-S enforcement in ECDSA signatures update. So you will have a
hard time spending coins with electrum 1.9.8.

2.5.2 is in unstable, but it still has a bug in install wizard which
affects Debian. I reported it and it was fixed in 2.5.3 which will be
released very soon. Make sure you update to 2.5.3 when it's in sid or
from unstable if you are ok with that.

On 11/3/2015 7:16 PM, Zachary Peterson wrote:
>>>>>> Tristan Seligmann <mithrandi at mithrandi.net> writes:
> 
>> The following command should reproduce the process used by Electrum
>> 1.9.8 to load the config file:
> 
>> python -c 'import ast, os; print
>> ast.literal_eval(open(os.path.expanduser("~/.electrum/config")))'
> 
>> This should fail with a Python exception; could you reply to this bug
>> with the output?
> 
> Traceback (most recent call last):
>   File "<string>", line 1, in <module>
>   File "/usr/lib/python2.7/ast.py", line 80, in literal_eval
>     return _convert(node_or_string)
>   File "/usr/lib/python2.7/ast.py", line 79, in _convert
>     raise ValueError('malformed string')
> ValueError: malformed string
> 
>> (The problem could be that your configuration is corrupt somehow, or
>> the file is unreadable for some reason. Another possibility is that
>> you have run a newer version of Electrum somehow; newer versions use a
>> different format for the configuration and wallet files, and will
>> upgrade it automatically, making older versions unable to read the
>> files.)
> That seems a likely cause. I was running Testing for a while before
> reverting to Stable due to some issues with other packages.
>