On Wednesday 11 July 2007, David Baron wrote:
> On Wednesday 11 July 2007, Rui Nuno Capela wrote:
> > David Baron wrote:
> > > More very minor things:
> > >
> > > 1. Jack is always started with qjackctl. I have that option not
> > > checked.
> >
> > Does the main top-left display says 'Started' or 'Active' (in bright
> > yellow over black) when you launch qjackctl?
>
> Yes.
"Active"
Now this touches the icons as well!
The first run I tried this, icons were what was exected. The server did not
come up by itself and I had the red box. Hit start, got "starting" which
takes time. After I got rid of the -X command by having no "MIDI driver"
succeded in getting to "started" with the green arrow!
Runs after that, regardless of the "MIDI driver" setting, come up active with
the errant icons!! Stop yields blank white circle. Start returns immediately
to "active" with red arrow icon!
If I close the app.
killall jackd
rerun the app.
Comes up "stopped", red box.
Start --> "starting" --> "started" green arrow
Stop --> blanks black displa pane, blank white circle.
Start --> "active", red arrow.
If I check the "execute script after shutdown" as killall jackd, then stopping
and starting works the way I would expect with the correct icons.
Then I am be asked whether to terminate jackd on quitting.
If I leave and restart, then I get "active" with red arrow.
Stop goes to blank white circle.
Start goes to "starting" --> "started" green arrow ...
This should be useful information.
(Thanks for not killing the app on upper-right [x]. This was not correct
behavior for a "tray" app.)
> > > 2. I have had the program crash out working the connections (all-alsa)
> > > pane. Happens when I touch the midi-through item.
> >
> > This deserves some debugging. Are willing to help?
> > 1) rebuild with ./configure --enable-debug && make
> > 2) ulimit -c unlimited
> > 3) ./qjackctl
> > 4) *make-it-crash* (core dumped)
> > 5) gdb ./qjackctl core
> >
> > Tell me what you find.
>
> May try tomorrow. See what happens.
Was able to crash it but no "core" file was produced.
Ran from within the debugger. Was not able to crash it after many tries.
As per a reply to another poster, here is the coredump from 5) core.8983
Program terminated with signal 11, Segmentation fault.
#0 0xb780fba2 in QObject::parent (this=0x0)
at ../../include/QtCore/../../src/corelib/kernel/qobject.h:213
213 ../../include/QtCore/../../src/corelib/kernel/qobject.h: No such file
or directory.
in ../../include/QtCore/../../src/corelib/kernel/qobject.h
If this were really not available, then it would not have compiled. However,
this is what I got.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@email-addr-hidden
http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user
Received on Thu Jul 12 16:15:02 2007
This archive was generated by hypermail 2.1.8 : Thu Jul 12 2007 - 16:15:02 EEST