Your message dated Tue, 03 Nov 2015 18:50:54 +0000 with message-id <camckhmr2djj7z0tyc_dwykmuvwop0qccqxegz8c0qri1rgn...@mail.gmail.com> and subject line Re: Bug#803949: electrum: Electrum unable to start; Cannot read config file has caused the Debian Bug report #803949, regarding electrum: Electrum unable to start; Cannot read config file to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 803949: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803949 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: electrum Version: 1.9.8-4 Severity: grave Justification: renders package unusable Dear Maintainer, I've never had this problem before, but after recently re-installing Debian, I am unable to start Electrum. When I try from the command line, I get the following: Traceback (most recent call last): File "/usr/bin/electrum", line 174, in <module> config = SimpleConfig(config_options) File "/usr/lib/python2.7/dist-packages/electrum/simple_config.py", line 33, in __init__ self.read_user_config() File "/usr/lib/python2.7/dist-packages/electrum/simple_config.py", line 157, in read_user_config raise IOError("Cannot read config file.") IOError: Cannot read config file. -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages electrum depends on: ii python 2.7.9-1 ii python-electrum 1.9.8-4 electrum recommends no packages. electrum suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---On Tue, 3 Nov 2015 at 19:17 Zachary Peterson <zap5...@psu.edu> wrote: > 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 > > That seems a likely cause. I was running Testing for a while before > reverting to Stable due to some issues with other packages. > This error looks like what you would get trying to load a config file that has been upgraded to the new JSON format, so that's probably what happened. Unfortunately there isn't any way to go back unless you have a backup of your files; while the config file isn't too important (you could probably just delete it and set up your configuration again), your wallet file won't open with an older version anymore if it was upgraded to a newer version. On the other hand, I think Electrum 1.9.8 isn't even usable to generate transactions anymore due to changes in transaction signing. I do intend to upload Electrum 2.5.2 (and probably 2.5.3 thereafter) to jessie-backports once it migrates to testing (~2 days), so installing this from backports once it makes it there is likely your best option. I'm closing this bug as not being able to load a newer format config file isn't really a bug (the forwards incompatibility is intentional).
--- End Message ---
