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
On Wed, Oct 26, 2016 at 07:04:35PM +1100, Erik de Castro Lopo wrote:
> Anthony Towns wrote:
> > Maybe
> > /usr/lib/x86_64-linux-gnu/qt5/examples/widgets/desktop/systray/systray
> > might reproduce the crash?
> Indeed it does! Gdb backtrace follows.
Okay, that makes it a Qt/GL bug afaics then.
Anthony Towns wrote:
> Maybe
>
> /usr/lib/x86_64-linux-gnu/qt5/examples/widgets/desktop/systray/systray
>
> might reproduce the crash?
Indeed it does! Gdb backtrace follows.
Erik
> gdb --args
> /usr/lib/x86_64-linux-gnu/qt5/examples/widgets/desktop/systray/systray
GNU gdb (Debian 7.11.1-2)
On Tue, Oct 25, 2016 at 07:16:45PM +1100, Erik de Castro Lopo wrote:
> Thread 1 "bitcoin-qt" received signal SIGSEGV, Segmentation fault.
> qglx_findConfig (display=display@entry=0x56151080, screen=screen@entry=0,
> format=...,
> drawableBit=drawableBit@entry=1) at
Anthony Towns wrote:
> > Starting program: /home/erikd/Local/bin/bitcoin-qt
>
> That's an odd location for the packaged binary?
Yeah, gdb-ed the wrong binary. The correct binary does the same.
> bitcoin-qt's working fine for me with the same versions of the libraries
> as you have, so I'll
> 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
Package: bitcoin-qt
Version: 0.13.0-0.1
Severity: important
Dear Maintainer,
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
[Thread debugging
7 matches
Mail list logo
