Bug#841951: bitcoin-qt segfaults on startup
Anthony Towns wrote:
> Okay, that makes it a Qt/GL bug afaics then. Might be worth trying the
> attached. I get:
>
> $ g++ -o test test.cpp -lX11 -lGL -Wall -W
> $ ./test
> config 0 alphaSize 0
> config 1 alphaSize 0
> config 2 alphaSize 0
> ...
> config 36 alphaSize 0
> config 37 alphaSize 0
> config 38 alphaSize 8
> config 39 alphaSize 8
>
> I'm guessing you'll get some visual==NULL!! warnings
Indeed. I get single `visual==NULL` at:
config 0 alphaSize 0
config 1 alphaSize 0
config 2 alphaSize 0
config 3 alphaSize 0
config 4 alphaSize 0
config 5 alphaSize 0
config 6 alphaSize 0
config 7 alphaSize 0
config 8 alphaSize 0
config 9 alphaSize 0
config 10 alphaSize 0
config 11 alphaSize 0
config 12 alphaSize 0
config 13 alphaSize 0
config 14 alphaSize 0
config 15 alphaSize 0
config 16 alphaSize 0
config 17 alphaSize 0
config 18 alphaSize 8
config 19 alphaSize 8
config 20 alphaSize 8
config 21 alphaSize 8
config 22 alphaSize 8
config 23 alphaSize 8
config 24 alphaSize 8
config 25 alphaSize 8
config 25 visual==NULL!!
config 26 alphaSize 8
config 27 alphaSize 8
config 28 alphaSize 8
config 29 alphaSize 8
config 30 alphaSize 8
config 31 alphaSize 8
config 32 alphaSize 8
config 33 alphaSize 8
config 34 alphaSize 8
config 35 alphaSize 8
config 36 alphaSize 0
config 37 alphaSize 0
config 38 alphaSize 8
config 39 alphaSize 8
every time I run the program.
> as well at which
> point you might be able to work out what's going on?
Well I suspect that must be the one config that bitcoin-qt is
trying to use. Should this debian bug be moved to another package?
If so, which one?
Erik
--
----------------------------------------------------------------------
Erik de Castro Lopo
http://www.mega-nerd.com/
Reply to: