> Just got a new machine, installed bitcoin-qt, ran it and got an > immediate segfault. Re-running get the same result. > > Backtrace from GDB: > > (gdb) r > Starting program: /home/erikd/Local/bin/bitcoin-qt
That's an odd location for the packaged binary? > [Thread debugging using libthread_db enabled] > Using host libthread_db library > "/lib/x86_64-linux-gnu/libthread_db.so.1". > [New Thread 0x7fffe9967700 (LWP 21490)] > [New Thread 0x7fffdcfa1700 (LWP 21491)] > [New Thread 0x7fffd7fff700 (LWP 21492)] > > Thread 1 "bitcoin-qt" received signal SIGSEGV, Segmentation fault. bitcoin-qt's working fine for me with the same versions of the libraries as you have, so I'll downgrade this report. Some things you might like to try if you haven't already: - try running /usr/lib/x86_64-linux-gnu/qt5/examples/gui/analogclock/analogclock from qtbase5-examples to see if simple qt programs fail? - running "bitcoin-qt -regtest" to eliminate downloading the blockchain and contacting peers while debugging - installing bitcoind, and trying it in headless mode to avoid qt and graphics related bugs - use "ssh -X" to get into your new desktop from somewhere else, and run bitcoin-qt from there, to perhaps eliminate any problems related to graphics drivers? > There doesn't seem to be any debug symbols available for libqt5gui5 so > I was not able to debug this futher. Have you tried installing the qtbase5-dbg and related packages? That seems to give me useful debug info. Cheers, aj