Closed Perlover closed 6 years ago
New, second dump Same behaviour:
I deleted Segwit wallet and restored Legacy wallet from seed as 'default_wallet' But i got Segmentation Fault again Here backtrace:
can you try to regenerate the icons file?
in the electrum source dir, please run 'pyrcc5 icons.qrc -o gui/qt/icons_rc.py'
bonjour, sorry i'm speeck french...comment je fait pour aller dans le répertoire source d'electrum, lancez 'pyrcc5 icons.qrc -o gui / qt / icons_rc.py'
Hello,
Thanks! I will try it later at evening because it bug I see in home computer.
Best regards, Perlover
8 янв. 2018 г. 11:36 пользователь "ThomasV" notifications@github.com написал:
in the electrum source dir, please run 'pyrcc5 icons.qrc -o gui/qt/icons_rc.py'
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/spesmilo/electrum/issues/3660#issuecomment-355931736, or mute the thread https://github.com/notifications/unsubscribe-auth/AAjDfSQcg7mi6WN7wja7RlnYZXuLAt6cks5tIe-cgaJpZM4RVVwd .
Hello!
I cloned git repo and checkout to '3.0.3' (i have this version and i know that this version is buggy now) I run this command and i got icons.qrc But this is now XML file and i don't know what should i do next with its? I installed the Electrum through command line 'sudo pip3 install...' The Electrum installed to '/usr/local/bin/electrum' Should i copy this icons.qrc file to some directory (?) in system and run electrum again?
P.S. And i found the file '/usr/local/lib/python3.5/dist-packages/electrum_gui/qt/icons_rc.py' in my system. May be this info will help...
Thanks for answer!
update the file icons_rc.py that you found in your system, with the one you generated
I have the same issue. But, when I use "pyrcc5 icons.qrc -o gui/qt/icons_rc.py" command, the error message is that:
pyrcc5: File does not exist 'icons.qrc'
Anyone could help me? I use the same system: Linux MInt 18.3 and have same the segmentation fault issue
Hi!
I did:
pyrcc5 icons.qrc -o gui/qt/icons_rc.py sudo cp gui/qt/icons_rc.py /usr/local/lib/python3.5/dist-packages/electrum_gui/qt/icons_rc.py
After i had run Electrum and got same error again Here is backtrace after rebuilding icons_rc.py an updating one.
I can try to update to 3.0.5 version (it's buggy 3.0.5) Or may be do you want to ask me to do some other tests for a catching this bug?
This bug only happen with Cinnamon. When I try to use Mate, this issue doesn't happen. I do not know much more than that and how do I fix it, but this hint of mate worked for me.
@Perlover the bug seems related to Mint, then. I think we should close the issue here, because I dont see how we can fix it on our side
May be. I have same Linux Mint 18.03 at work and there was Electrum 3.0.3 but i didn't have there problem. May be installed incorrectly cython-hidapi or hidapi library to python (i had problem when i installed at home). I close this ticket. I will try to reinstall Electrum and related libraries. If bug will not gone away i will reopen ticket.
Interesting noticeing
I updated Electrum 3.0.3 -> 3.0.5 The troubles were be continuing I reinstalled many modules (related with qt5 - python modules + deb packages) Troubles were there again
But when i copied ~/.electrum/wallet/* files and removed ~/.electrum (rm -rf ~/.electrum) and restored all wallets from copies (before i did again default_wallet in first start) - electrum works more stability (but i saw one crash)
So i think some file(s) in ~/.electrum caused Segmentation Fault
I have the same issue, and I noticed that if I enter the password and wait a few second before clicking next, it wont crash anymore.
Removing and recreating new ~/.electrum doesn't help :( May be problem was related with watch-only wallets for Bitcoin Trezor device. Now i have again - Electrum 3.0.5 crashed every time (not 100% cases but may be 90%) :(
Here new gdb backtrace: Can you see again to this problem? If you cannot understand the reason of this bug i will close ticket. But i did many reinstalling and problem occurs again and again :(
P.S. I can recompile or rebuild Electrum with options you will ask for getting more debugging info if you need. Only please write which options?
And i tested now not watch-only mode for Trezor Here native Segwit wallet for Electrum There crash again. But quickly sight to this shows that backtrace dump a little shorter
I found same problem with Qt5 & bitcoin wallet;
Issues: https://github.com/bitcoin/bitcoin/issues/11262 https://github.com/bitcoin/bitcoin/issues/9883 https://github.com/bitcoin/bitcoin/issues/9683
And Electrum issues: https://github.com/spesmilo/electrum/issues/3349 i see same syslog lines:
Jan 25 22:36:54 perlover-desktop kernel: [ 5063.039503] electrum[8938]: segfault at 40000068 ip 00007f8c9fd9c7b1 sp 00007fffddd37360 error 4 in libQt5Widgets.so.5.5.1[7f8c9f973000+659000]
I installed python3-all-dbg & python3-pyqt5-dbg packages And rerun again, i got new crash with debug info May be it will help?
, globals=, locals=locals@entry=0x0, args=, argcount=argcount@entry=1, kws=0x33764e0, kwcount=0, defs=0x0, defcount=0,
Python Exception Type does not have a target.:
Python Exception Type does not have a target.:
kwdefs=0x0, closure=0x0, name=, qualname=) at ../Python/ceval.c:4018
#25 0x000000000054a800 in fast_function (func=func@entry=, pp_stack=pp_stack@entry=0x7ffcf56a3c90, n=n@entry=1, na=na@entry=1, nk=nk@entry=0) at ../Python/ceval.c:4813
#26 0x000000000054ada5 in call_function (pp_stack=pp_stack@entry=0x7ffcf56a3c90, oparg=oparg@entry=0) at ../Python/ceval.c:4730
Python Exception Type does not have a target.:
#27 0x0000000000547f43 in PyEval_EvalFrameEx (f=f@entry=, throwflag=throwflag@entry=0) at ../Python/ceval.c:3236
#28 0x000000000054a74e in fast_function (func=func@entry=, pp_stack=pp_stack@entry=0x7ffcf56a3e30, n=n@entry=3, na=na@entry=3, nk=nk@entry=0) at ../Python/ceval.c:4803
#29 0x000000000054ada5 in call_function (pp_stack=pp_stack@entry=0x7ffcf56a3e30, oparg=oparg@entry=2) at ../Python/ceval.c:4730
Python Exception Type does not have a target.:
#30 0x0000000000547f43 in PyEval_EvalFrameEx (f=f@entry=, throwflag=throwflag@entry=0) at ../Python/ceval.c:3236
Python Exception Type does not have a target.:
Python Exception Type does not have a target.:
#31 0x000000000054a520 in _PyEval_EvalCodeWithName (_co=_co@entry=, globals=globals@entry=, locals=locals@entry=, args=args@entry=0x0, argcount=argcount@entry=0, kws=kws@entry=0x0, kwcount=0, defs=0x0,
defcount=0, kwdefs=0x0, closure=0x0, name=0x0, qualname=0x0) at ../Python/ceval.c:4018
Python Exception Type does not have a target.:
Python Exception Type does not have a target.:
#32 0x000000000054a610 in PyEval_EvalCodeEx (_co=_co@entry=, globals=globals@entry=, locals=locals@entry=, args=args@entry=0x0, argcount=argcount@entry=0, kws=kws@entry=0x0, kwcount=0, defs=0x0,
defcount=0, kwdefs=0x0, closure=0x0) at ../Python/ceval.c:4039
Python Exception Type does not have a target.:
Python Exception Type does not have a target.:
#33 0x000000000054a639 in PyEval_EvalCode (co=co@entry=, globals=globals@entry=, locals=locals@entry=) at ../Python/ceval.c:777
Python Exception Type does not have a target.:
Python Exception Type does not have a target.:
Python Exception Type does not have a target.:
#34 0x0000000000424ee8 in run_mod (mod=mod@entry=0x2b44878, filename=filename@entry=, globals=globals@entry=, locals=locals@entry=, flags=flags@entry=0x7ffcf56a4110, arena=arena@entry=0x2ab94d0) at ../Python/pythonrun.c:976
Python Exception Type does not have a target.:
Python Exception Type does not have a target.:
#35 0x000000000042797a in PyRun_FileExFlags (fp=fp@entry=0x2a7ad40, filename_str=filename_str@entry=0x7febb24ac890 "/usr/local/bin/electrum", start=start@entry=257, globals=globals@entry=, locals=locals@entry=, closeit=closeit@entry=1,
flags=0x7ffcf56a4110) at ../Python/pythonrun.c:929
#36 0x0000000000427d17 in PyRun_SimpleFileExFlags (fp=fp@entry=0x2a7ad40, filename=, filename@entry=0x7febb24ac890 "/usr/local/bin/electrum", closeit=closeit@entry=1, flags=flags@entry=0x7ffcf56a4110)
at ../Python/pythonrun.c:396
#37 0x0000000000427e7a in PyRun_AnyFileExFlags (fp=fp@entry=0x2a7ad40, filename=0x7febb24ac890 "/usr/local/bin/electrum", closeit=closeit@entry=1, flags=flags@entry=0x7ffcf56a4110) at ../Python/pythonrun.c:80
#38 0x00000000004370dc in run_file (fp=fp@entry=0x2a7ad40, filename=filename@entry=0x2a11250 L"/usr/local/bin/electrum", p_cf=p_cf@entry=0x7ffcf56a4110) at ../Modules/main.c:318
#39 0x0000000000437c0b in Py_Main (argc=argc@entry=2, argv=argv@entry=0x2a0f020) at ../Modules/main.c:768
#40 0x000000000041f319 in main (argc=2, argv=0x7ffcf56a4328) at ../Programs/python.c:65
(gdb)
```
I'm not sure what we can do to solve this. It seems like you're using a buggy Qt5 version, especially since the same issue occurs with other Qt applications.
I suggest you report this to your package maintainer.
Here my other Linux MInt 18.3 computer and Electrum 3.0.5 There were rarely crashes but they were Now i catched core file in my work computer. Here backtrace, may be it will help anybody I will close this ticket but i think dumps can be usefull for somebody
It turns out that the reality now is that Electrum can not be used in Linux Mint 18.3 :(
I created bug report here: https://bugreports.qt.io/browse/QTJIRA-325
I've downloaded Linux Mint 18.3 with Cinnamon and tried to reproduce this to no avail. Does this happen deterministically when doing something specific?
Hi, SomberNight!
Thanks for helping I have two computers: work & home. Both installed separately. But both had Mint 18.2 (Cinnamon) and after i upgraded successfully up to Mint 18.3 (Cinnamon). In both i installed by "sudo pip3 install" from "Download" section os Electrum site. First i had normal working Electrum at work and stability crashed at home. But in last time i see ofen crashed in work too. In both places i use Trezor watch-only wallets. But i saw that Electrum crashed in native wallets of Electrum too. I think it crashed when i use used wallets (which have a some transactions not empty). If i will notice some conditions for this bug i will let you know of cause here.
Can you reproduce the bug when running PyQt in valgrind? This should show you where the cause of the segmentation fault is actually happening.
I think i now reason of my problems
I installed now v3.1 and Electrum started without segmentation faults but it prints at start about trezor library version ("Your trezor library version is unknown but need 0.9.0") I tried to install again from https://github.com/trezor/python-trezor new v0.9.1 but after i got again and again this warning.
After i located in /usr/local/lib/python3.5/dist-packages these directories:
trezor-0.7.16.egg-info trezor-0.9.0-py3.5.egg trezorlib
I removed theirs by rm -rf ...
After i installed again python-trezor by "sudo -H pip3 install trezor" from source of python-trezor and now Electrum works. I didn't get SegFault but before it i got SegFault every time...
I think the problem was related with these libraries and may be by two versions of Trezor.
Ohh, no... After some sucessfully runs the Electrum 3.1 now terminated by Segmentation Fault again ,,,
Can you reproduce the bug when running PyQt in valgrind? This should show you where the cause of the segmentation fault is actually happening.
I will try
Here is "electrum -v" output before segmentation fault:
[SimpleConfig] electrum directory /home/user/.electrum
[get_server] [Errno 111] Connection refused
[Plugins] registering hardware digitalbitbox: ('hardware', 'digitalbitbox', 'Digital Bitbox wallet')
[Plugins] registering hardware keepkey: ('hardware', 'keepkey', 'KeepKey wallet')
[Plugins] registering hardware ledger: ('hardware', 'ledger', 'Ledger wallet')
[Plugins] registering hardware trezor: ('hardware', 'trezor', 'TREZOR wallet')
[Plugins] registering wallet type ('2fa', 'trustedcoin')
[profiler] __init__ 0.0024
[Network] blockchains dict_keys([0])
[Network] starting network
[Network] connecting to spv.48.org:50002:s as new interface
[FxThread] using exchange BitcoinAverage
[ruuxwv74pjxms3ws.onion] cannot resolve hostname
[de.hamster.science] connected
[spv.48.org] SSL certificate signed by CA
[spv.48.org] connected
[BitcoinAverage] getting fx quotes for USD
[Network] switching to spv.48.org:50002:s
[Network] sending subscriptions to spv.48.org:50002:s 0 0
[electrum.vom-stausee.de] connected
[Network] no height for main interface
[Network] switching to de.hamster.science:50002:s
[Network] sending subscriptions to de.hamster.science:50002:s 0 0
[cryptohead.de] connected
[WalletStorage] wallet path /home/user/.electrum/wallets/wallet
[Network] fee_histogram [[5, 105312], [2, 242986], [1, 26763504]]
[Network] fee_estimates[25] 3520
[Network] fee_estimates[10] 4250
[Network] fee_estimates[5] 10128
[Network] fee_histogram [[6, 100541], [2, 254967], [1, 26763504]]
[Network] fee_estimates[25] 3519
[Network] fee_estimates[10] 4250
[Network] fee_estimates[5] 10127
[Network] fee_estimates[2] 25703
[Network] relayfee 1000
[e.keff.org] SSL certificate signed by CA
[e.keff.org] connected
[Plugins] loaded trezor
[profiler] load_transactions 0.0002
[profiler] build_spent_outpoints 0.0000
[profiler] check_history 0.0000
[Network] fee_estimates[2] 25701
[profiler] get_full_history 0.0024
[profiler] on_update 0.0054
[profiler] write 0.0000
[profiler] save_transactions 0.0003
[ElectrumWindow/wallet] Notifying GUI
[btc.asis.io] connected
[profiler] load_wallet 0.1295
[DeviceMgr] getting client for keystore
[DeviceMgr] scanning devices...
[electrum.achow101.com] connected
[electrum.leblancnet.us] SSL certificate signed by CA
[electrum.leblancnet.us] connected
[E-X.not.fyi] connected
[btc.smsys.me] connected
[profiler] get_full_history 0.0100
[profiler] on_update 0.0271
[BitcoinAverage] received fx quotes
[profiler] get_full_history 0.0120
[profiler] on_update 0.0488
in the electrum source dir, please run 'pyrcc5 icons.qrc -o gui/qt/icons_rc.py'
When i do that, it returns Unable to open gui/qt/icons_rc.py for writing
For reference: https://github.com/bitcoin/bitcoin/pull/15203
Hi,
I restored wallet at new installation under name 'segwit_wallet' But i regulary i got "Segmentation fault" after start (i enter password for wallet, after i see lastunconfirmed transaction and after some seconds "Segmentation fault")
gdb
``` $ gdb $(which python3) GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later