Author

Topic: Upgrade 1.9.8 to 2.5.3 issues (Read 496 times)

hero member
Activity: 619
Merit: 500
November 12, 2015, 12:36:38 PM
#4
It's always good practice to use sudo instead of the root account.

What distro did you use previously that did not require the sudoers file?
newbie
Activity: 19
Merit: 0
November 12, 2015, 10:26:47 AM
#3
Did you try
Code:
apt-get install libcanberra-gtk-module

No I never found that info.

I got it installed finally. Debian is a bit different, requires a "sudoers" file in addition to the sudo group. Once I got that I did the install from my normal users account but using sudo and it installed OK, replacing the launcher's 1.9.8 with 2.5.3. Didn't have any issues sending after that.

The python install/setup script apparently has enough smarts to do things that require root as well as the things that don't and does the right thing for both. That's why it didn't fully work trying to install using the root account but does with sudo (path differences etc). Of course the install totally fails with just a normal user account without sudo.

hero member
Activity: 619
Merit: 500
November 12, 2015, 09:48:40 AM
#2
Did you try
Code:
apt-get install libcanberra-gtk-module
newbie
Activity: 19
Merit: 0
November 12, 2015, 09:28:00 AM
#1
Having trouble with the upgrade. It partially works but seems to have permission issues, probably due to python.

I installed 1.9.8 with apt-get, but it's not available (unless from a PPA which I don't want to use for this) for Debian 8.2.

I downloaded from electrum site ( https://download.electrum.org/2.5.3/Electrum-2.5.3.tar.gz), but from there I am not clear the "right" way to proceed.

The instructions use pip to install Electrum. It will not install unless installed with a root account, which I did and it runs, I imported wallet, no issues.

UNTIL I went to send  a transaction. First one managed to get broadcast, but didn't show up in history. After a restart of Electrum it did, but merchant timed out waiting for it (I guess, that's how it appeared).

Tried to send a second time, similar issue. Here's what the console reported:

Code:
(process:4084): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Gtk-Message: Failed to load module "canberra-gtk-module"

This is rather frustrating. Any help would be greatly appreciated.

Thanks!


Jump to: