Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Freeze followed by crash when clicking on the red network icon #1060

Closed
goetzc opened this issue Mar 5, 2015 · 9 comments
Closed

Freeze followed by crash when clicking on the red network icon #1060

goetzc opened this issue Mar 5, 2015 · 9 comments

Comments

@goetzc
Copy link

goetzc commented Mar 5, 2015

Since the update to version 2.0, I get the message "Not connected" on the bottom-left corner. When clicking on the red Network icon (or from menu Tools), Electrum main window disappears, but the tray icon stays there, sometimes after a dozen seconds the tray icon disappears, with no more electrum process.

This is in Arch Linux, Python 2.7.9-1, python2-pyqt4 4.11.3-3

$ electrum
Connected to daemon on port 8001
libpng warning: iCCP: known incorrect sRGB profile
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
python2: xcb_io.c:274: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.

[2]-  Terminated              electrum
[3]+  Aborted                 (core dumped) electrum

The dumped core could not be saved. This was in dmesg:

electrum[20028]: segfault at 4 ip b4f081a4 sp bfc7e58c error 4 in libQtCore.so.4.8.6[b4d74000+2fb000]

One other occasion:

$ electrum -v
electrum directory /home/test/.electrum
CA bundle: /etc/ssl/certs/ca-certificates.crt found
Audio MODEM is not found.
[OA] Initialiasing OpenAlias plugin, OA_READY is True
Connected to daemon on port 8001
wallet path /home/test/.electrum/wallets/default_wallet
libpng warning: iCCP: known incorrect sRGB profile
(then, when clicking on Network)
NetworkProxy: terminating

The crash is reproducible every time, just the output differed, which I don't know why.

@ecdsa
Copy link
Member

ecdsa commented Mar 5, 2015

you have the electrum daemon running.
what is the output of "electrum daemon status" ?
does the crash occur too if you are not running a daemon?
(you can stop it with "electrum daemon stop")

@goetzc
Copy link
Author

goetzc commented Mar 5, 2015

If there is no electrum process running:

$ electrum -v daemon stop
electrum directory /home/test/.electrum
CA bundle: /etc/ssl/certs/ca-certificates.crt found
Connected to daemon on port 8001
Daemon stopped
NetworkProxy: terminating

If there is again no electrum process running:

$ electrum -v daemon status
electrum directory /home/test/.electrum
CA bundle: /etc/ssl/certs/ca-certificates.crt found
Connected to daemon on port 8001
NetworkProxy: terminating

Which starts an electrum process, if the same command is invoked again, a new process (with different PID and so) is started. Nothing more is printed on screen.
Then calling "electrum daemon stop" just starts another electrum process, which stops after a couple of seconds. The other processes don't seem to be affected.

@ecdsa
Copy link
Member

ecdsa commented Mar 5, 2015

what's in the daemon.log file?
(in your .electrum directory)

@ecdsa
Copy link
Member

ecdsa commented Mar 5, 2015

hmm, I see, you never started the daemon, but it thinks there is an active daemon because some application is using port 8001.
do this: "electrum setconfig daemon_port 8123"
(assuming that port number 8123 is free, otherwise pick another one yourself)

@goetzc
Copy link
Author

goetzc commented Mar 5, 2015

There is no such file. find ~/.electrum/ -name daemon.log gives nothing.

But changing the port fixed everything! :)

@ecdsa
Copy link
Member

ecdsa commented Mar 5, 2015

ok I made the daemon use a file socket: 59c76f5
this will prevent similar problems
I still do not understand how this could cause a crash. that should be investigated

@ecdsa
Copy link
Member

ecdsa commented Mar 6, 2015

I also added a short timeout to get_parameters in 33b1142

@ecdsa
Copy link
Member

ecdsa commented Mar 6, 2015

I made a bugfix release, version 2.0.1
I hope we will have binaries soon.

@ecdsa ecdsa closed this as completed Mar 6, 2015
@goetzc
Copy link
Author

goetzc commented Mar 7, 2015

2.0.1 fixes the problem. Thank you!

protonn pushed a commit to argentumproject/electrum-arg that referenced this issue Feb 15, 2019
* Fix FloatingActionButton positioning on API levels before 21

* Use pkgutil to load data files, so `electroncash` package doesn't need to be extracted on Android:
Closes spesmilo#1062, which I assume was caused by the cache directory being cleared while the app was running.

* Update to Chaquopy 5.0.7 (closes spesmilo#1060)

* Use new Chaquopy primitive conversion methods

* Use new Chaquopy container view methods

* Update to Chaquopy 5.1.0  /  Pin version of pycryptodomex

* Use correct container interface when calling get_blockchains

* Add missing lock (closes spesmilo#1109)

* Don't restore UI state if process has been restarted (closes spesmilo#1057, closes spesmilo#1093, closes spesmilo#1095)

* Fix "Can not perform this action after onSaveInstanceState" errors (closes spesmilo#1083, closes spesmilo#1091, closes spesmilo#1103)

* Trigger onShowDialog from DialogFragment.onStart rather than Dialog.setOnShowListener (closes spesmilo#1108, and see also spesmilo#1046)

* Don't show temporary files in wallet list (closes spesmilo#1102)

* ImageView size is now unavailable in onShowDialog, so get QR resolution from resource instead

* Catch network exceptions at top level of Connection thread (closes spesmilo#1096)

* Add missing locks

* Fix unit tests

* Update Android license agreement hash
Toporin pushed a commit to Toporin/electrum-satochip that referenced this issue Feb 16, 2021
* Fix FloatingActionButton positioning on API levels before 21

* Use pkgutil to load data files, so `electroncash` package doesn't need to be extracted on Android:
Closes spesmilo#1062, which I assume was caused by the cache directory being cleared while the app was running.

* Update to Chaquopy 5.0.7 (closes spesmilo#1060)

* Use new Chaquopy primitive conversion methods

* Use new Chaquopy container view methods

* Update to Chaquopy 5.1.0  /  Pin version of pycryptodomex

* Use correct container interface when calling get_blockchains

* Add missing lock (closes spesmilo#1109)

* Don't restore UI state if process has been restarted (closes spesmilo#1057, closes spesmilo#1093, closes spesmilo#1095)

* Fix "Can not perform this action after onSaveInstanceState" errors (closes spesmilo#1083, closes spesmilo#1091, closes spesmilo#1103)

* Trigger onShowDialog from DialogFragment.onStart rather than Dialog.setOnShowListener (closes spesmilo#1108, and see also spesmilo#1046)

* Don't show temporary files in wallet list (closes spesmilo#1102)

* ImageView size is now unavailable in onShowDialog, so get QR resolution from resource instead

* Catch network exceptions at top level of Connection thread (closes spesmilo#1096)

* Add missing locks

* Fix unit tests

* Update Android license agreement hash
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants