8 Oct
2016
8 Oct
'16
2:45 p.m.
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 0x00007ffff75957e3 in XGetWindowProperty () from /usr/lib/libX11.so.6
#1 0x000000000041e6c4 in ?? ()
#2 0x00007ffff5aba21f in QAbstractEventDispatcher::filterNativeEvent(QByteArray
const&, void*, long*) () from /usr/lib/libQt5Core.so.5
#3 0x00007fffece0ec34 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () from
/usr/lib/libQt5XcbQpa.so.5
#4 0x00007fffece0f8c5 in QXcbConnection::processXcbEvents() () from
/usr/lib/libQt5XcbQpa.so.5
#5 0x00007ffff5ae9349 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5
#6 0x00007ffff6e67e3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#7 0x00007ffff6e6f5b1 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#8 0x00007ffff5abcc80 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from
/usr/lib/libQt5Core.so.5
#9 0x00007ffff5abf3fd in QCoreApplicationPrivate::sendPostedEvents(QObject*, int,
QThreadData*) () from /usr/lib/libQt5Core.so.5
#10 0x00007ffff5b11173 in ?? () from /usr/lib/libQt5Core.so.5
#11 0x00007ffff2724e67 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#12 0x00007ffff27250d0 in ?? () from /usr/lib/libglib-2.0.so.0
#13 0x00007ffff272517c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#14 0x00007ffff5b1157f in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/libQt5Core.so.5
#15 0x00007ffff5abb0da in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/libQt5Core.so.5
#16 0x00007ffff5ac35cc in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#17 0x000000000041df0a in ?? ()
#18 0x00007ffff4cfc291 in __libc_start_main () from /usr/lib/libc.so.6
#19 0x000000000041e519 in ?? ()
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
8 Oct
8 Oct
4:12 p.m.
On Sat, 8 Oct 2016 12:45:44 +0000
Fons Adriaensen <fons(a)linuxaudio.org> 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)
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
6:38 p.m.
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, using the Setup / Misc / "Start minimized to
system tray" option as from a previous v0.4.1 configuration ? also note
that this troubled option vanished on 0.4.2. however, due to many kind
requests, returned on 0.4.3 and is indeed guilty of the ill behavior
similar to the one you report.
as last resort, what happens when start on a blank configuration? hint:
remove or backup the ~/.config/rncbc.org/QjackCtl.conf file away, making
sure you can restore it back later, then launch qjackctl again.
cheers
--
rncbc aka. Rui Nuno Capela
7:06 p.m.
On Sat, Oct 08, 2016 at 04:38:25PM +0000, Rui Nuno Capela wrote:
On 10/08/2016 01:45 PM, Fons Adriaensen wrote:
Never used that option, and in 0.4.1 it's greyed out (apparently
since I don't enable the system tray icon).
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, using the Setup / Misc / "Start minimized to
system tray" option as from a previous v0.4.1 configuration ? also note
that this troubled option vanished on 0.4.2. however, due to many kind
requests, returned on 0.4.3 and is indeed guilty of the ill behavior
similar to the one you report. as last resort, what happens when start on a blank
configuration? hint:
remove or backup the ~/.config/rncbc.org/QjackCtl.conf file away, making
sure you can restore it back later, then launch qjackctl again.
With the config file removed 0.4.2 works. It segfaults again
when restarted with the 'Single application instance' option
disabled.
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
8:09 p.m.
On Sat, 8 Oct 2016 17:06:41 +0000
Fons Adriaensen <fons(a)linuxaudio.org> wrote:
On Sat, Oct 08, 2016 at 04:38:25PM +0000, Rui Nuno
Capela wrote:
Confirming the same thing here.
Manually setting 'Singleton=true' in QjackCtl.conf clears the fault.
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
On 10/08/2016 01:45 PM, Fons Adriaensen wrote:
Never used that option, and in 0.4.1 it's greyed out (apparently
since I don't enable the system tray icon).
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, using the Setup / Misc / "Start minimized to
system tray" option as from a previous v0.4.1 configuration ? also note
that this troubled option vanished on 0.4.2. however, due to many kind
requests, returned on 0.4.3 and is indeed guilty of the ill behavior
similar to the one you report. as last resort, what happens when start on a
blank configuration? hint:
remove or backup the ~/.config/rncbc.org/QjackCtl.conf file away, making
sure you can restore it back later, then launch qjackctl again.
With the config file removed 0.4.2 works. It segfaults again
when restarted with the 'Single application instance' option
disabled.
Ciao,
9:04 p.m.
On 10/08/2016 07:09 PM, Will Godfrey wrote:
On Sat, 8 Oct 2016 17:06:41 +0000
Fons Adriaensen <fons(a)linuxaudio.org> wrote:
> On Sat, Oct 08, 2016 at 04:38:25PM +0000, 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 ?
...
Confirming the same thing here.
Manually setting 'Singleton=true' in QjackCtl.conf clears the fault.
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.
byee
--
rncbc aka. Rui Nuno Capela
9:59 p.m.
On Sat, Oct 08, 2016 at 07:04:48PM +0000, 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 you'll probably say that it doesn't make sense to run
two Jack instances on the same machine. First, that isn't true,
and second that is not what I'm doing.
Simple fact is tht this 'single instance' thing is broken.
Even doing a ssh -X to another machine and running qjackctl
there counts as a second instance. In other words it checks
the wrong thing: the main window instead of the process.
Ciao,
-
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
10:55 p.m.
On 10/08/2016 08:59 PM, Fons Adriaensen wrote:
On Sat, Oct 08, 2016 at 07:04:48PM +0000, Rui Nuno
Capela wrote:
no i won't say anything like that because i know you can run several
jackd server instances on the same machine, provided you name them
differently. then probably it's Paul turn to say that is what is
fundamentally broken in jackd, not quite on qjackctl's fault.
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 you'll probably say that it doesn't make sense to run
two Jack instances on the same machine. First, that isn't true,
and second that is not what I'm doing.
byee Simple fact is tht this 'single instance'
thing is broken.
Even doing a ssh -X to another machine and running qjackctl
there counts as a second instance. In other words it checks
the wrong thing: the main window instead of the process.
yes it counts as a second instance but the uniqueness is preserved as
the main window is set with a local X server property string which
includes the hostname of the remote X client.
so you'll probably be ok with ssh -X even though the single application
instance is enabled.
hth.
byee
--
rncbc aka. Rui Nuno Capela
11:03 p.m.
On 10/08/2016 09:55 PM, Rui Nuno Capela wrote:
On 10/08/2016 08:59 PM, Fons Adriaensen 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 :)
cheers
--
rncbc aka. Rui Nuno Capela
On Sat, Oct 08, 2016 at 07:04:48PM +0000, 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
there counts as a second instance. In other words it checks
the wrong thing: the main window instead of the process.
yes it counts as a second instance but the uniqueness is preserved as
the main window is set with a local X server property string which
includes the hostname of the remote X client.
so you'll probably be ok with ssh -X even though the single application
instance is enabled.
11:30 p.m.
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 can grab the latest and greatest from git head master aka.
qjackctl 0.4.3.5, where the crash-bug is now fixed:
http://sourceforge.net/p/qjackctl/code/ci/67221d
https://github.com/rncbc/qjackctl/commit/67221df
https://gitlab.com/rncbc/qjackctl/commit/67221df
https://bitbucket.org/rncbc/qjackctl/commits/67221df
thanks
--
rncbc aka. Rui Nuno Capela
2770
days inactive
2770
days old
linux-audio-dev@lists.linuxaudio.org
9 comments
3 participants
participants (3)
-
Fons Adriaensen -
Rui Nuno Capela -
Will Godfrey