[LAD] qjackctl segfault

2016-10-08 Thread Fons Adriaensen
Qjackctl 0.4.2 segfaults immediately after startup on my (fully updated) Archlinux system (qt 5.7.0, fluxbox). 0.4.1 works OK. Anyone else seen this ? Backtrace: (gdb) where #0 0x775957e3 in XGetWindowProperty () from /usr/lib/libX11.so.6 #1 0x0041e6c4 in ?? () #2 0x75

Re: [LAD] qjackctl segfault

2016-10-08 Thread Will Godfrey
On Sat, 8 Oct 2016 12:45:44 + Fons Adriaensen wrote: > Qjackctl 0.4.2 segfaults immediately after startup on my > (fully updated) Archlinux system (qt 5.7.0, fluxbox). > 0.4.1 works OK. > > Anyone else seen this ? Not having any problem on debian testing qjackctl 0.4.2-2 (qt 5.6.1, openbox)

Re: [LAD] qjackctl segfault

2016-10-08 Thread Rui Nuno Capela
On 10/08/2016 01:45 PM, Fons Adriaensen wrote: > Qjackctl 0.4.2 segfaults immediately after startup on my > (fully updated) Archlinux system (qt 5.7.0, fluxbox). > 0.4.1 works OK. > > Anyone else seen this ? > first note that qjackctl v0.4.3 is the most recent release. are you, by any chance, usi

Re: [LAD] qjackctl segfault

2016-10-08 Thread Fons Adriaensen
On Sat, Oct 08, 2016 at 04:38:25PM +, Rui Nuno Capela wrote: > On 10/08/2016 01:45 PM, Fons Adriaensen wrote: > > Qjackctl 0.4.2 segfaults immediately after startup on my > > (fully updated) Archlinux system (qt 5.7.0, fluxbox). > > 0.4.1 works OK. > > > > Anyone else seen this ? > > > > first

Re: [LAD] qjackctl segfault

2016-10-08 Thread Will Godfrey
On Sat, 8 Oct 2016 17:06:41 + Fons Adriaensen wrote: > On Sat, Oct 08, 2016 at 04:38:25PM +, Rui Nuno Capela wrote: > > On 10/08/2016 01:45 PM, Fons Adriaensen wrote: > > > Qjackctl 0.4.2 segfaults immediately after startup on my > > > (fully updated) Archlinux system (qt 5.7.0, fluxbox

Re: [LAD] qjackctl segfault

2016-10-08 Thread Rui Nuno Capela
On 10/08/2016 07:09 PM, Will Godfrey wrote: > On Sat, 8 Oct 2016 17:06:41 + > Fons Adriaensen wrote: > >> On Sat, Oct 08, 2016 at 04:38:25PM +, Rui Nuno Capela wrote: >>> On 10/08/2016 01:45 PM, Fons Adriaensen wrote: Qjackctl 0.4.2 segfaults immediately after startup on my (full

Re: [LAD] qjackctl segfault

2016-10-08 Thread Fons Adriaensen
On Sat, Oct 08, 2016 at 07:04:48PM +, Rui Nuno Capela wrote: > spot on! confirmed here too on v0.4.3+ > > so, for the time being, do not ever set this Setup / Misc / "Single > application instance" option to anything else but true. The only problem is that I need it to be disabled. And now

Re: [LAD] qjackctl segfault

2016-10-08 Thread Rui Nuno Capela
On 10/08/2016 08:59 PM, Fons Adriaensen wrote: > On Sat, Oct 08, 2016 at 07:04:48PM +, Rui Nuno Capela wrote: > >> spot on! confirmed here too on v0.4.3+ >> >> so, for the time being, do not ever set this Setup / Misc / "Single >> application instance" option to anything else but true. > > The

Re: [LAD] qjackctl segfault

2016-10-08 Thread Rui Nuno Capela
On 10/08/2016 09:55 PM, Rui Nuno Capela wrote: > On 10/08/2016 08:59 PM, Fons Adriaensen wrote: >> On Sat, Oct 08, 2016 at 07:04:48PM +, Rui Nuno Capela wrote: >> > >> Simple fact is tht this 'single instance' thing is broken. >> Even doing a ssh -X to another machine and running qjackctl >> th

Re: [LAD] qjackctl segfault

2016-10-08 Thread Rui Nuno Capela
On 10/08/2016 10:03 PM, Rui Nuno Capela wrote: > > and if you really want to get rid of this qjackctl single instance > broken feature altogether just build it without: > >./configure --disable-xunique && make && sudo make install > > and then all your troubles will be gone, i hope :) > or you