Re: [ANN] QjackCtl 0.3.0 (unstable-qt4) has been released!

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

As per you post use "bt"
(gdb) bt
#0  0xb780fba2 in QObject::parent (this=0x0)
    at ../../include/QtCore/../../src/corelib/kernel/qobject.h:213
#1  0xb781cc0d in QWidget::parentWidget (this=0x0)
    at ../../include/QtGui/../../src/gui/kernel/qwidget.h:949
#2  0xb7859ff1 in QWidget::window (this=0x0) at kernel/qwidget.cpp:3340
#3  0xb7850b65 in QWidget::topLevelWidget (this=0x0)
    at ../../include/QtGui/../../src/gui/kernel/qwidget.h:287
#4  0xb785066f in QToolTip::showText (pos=@0xbfb4cfe0, text=@0x81ab66c, w=0x0,
    rect=@0xbfb4cd34) at kernel/qtooltip.cpp:370
#5  0xb78507ad in QToolTip::showText (pos=@0xbfb4cfe0, text=@0x81ab66c, w=0x0)
    at kernel/qtooltip.cpp:397
#6  0x0805bc68 in qjackctlClientListView::eventFilter (this=0x81c94d0,
    pObject=0x81bbb88, pEvent=0xbfb4cfcc) at src/qjackctlConnect.cpp:818
#7  0xb78133c0 in QApplicationPrivate::notify_helper (this=0x812f198,
    receiver=0x81bbb88, e=0xbfb4cfcc) at kernel/qapplication.cpp:3530
#8  0xb7814d5c in QApplication::notify (this=0xbfb4db60, receiver=0x82f47d0,
    e=0xbfb4d1d0) at kernel/qapplication.cpp:3381
#9  0xb765955a in QCoreApplication::notifyInternal (this=0xbfb4db60,
    receiver=0x82f47d0, event=0xbfb4d1d0) at kernel/qcoreapplication.cpp:509
#10 0xb7810177 in QCoreApplication::sendEvent (receiver=0x82f47d0,
event=0xbfb4d1d0)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:186
#11 0xb78171ac in QApplication::event (this=0xbfb4db60, e=0xbfb4d664)
    at kernel/qapplication.cpp:2071
#12 0xb7813445 in QApplicationPrivate::notify_helper (this=0x812f198,
    receiver=0xbfb4db60, e=0xbfb4d664) at kernel/qapplication.cpp:3538
#13 0xb781375e in QApplication::notify (this=0xbfb4db60, receiver=0xbfb4db60,
    e=0xbfb4d664) at kernel/qapplication.cpp:3097
#14 0xb765955a in QCoreApplication::notifyInternal (this=0xbfb4db60,
    receiver=0xbfb4db60, event=0xbfb4d664) at kernel/qcoreapplication.cpp:509
#15 0xb765c923 in QCoreApplication::sendEvent (receiver=0xbfb4db60,
    event=0xbfb4d664)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:186
#16 0xb76858c9 in QTimerInfoList::activateTimers (this=0x8136fcc)
    at kernel/qeventdispatcher_unix.cpp:541
#17 0xb7682848 in timerSourceDispatch (source=0x8136f98)
    at kernel/qeventdispatcher_glib.cpp:142
#18 0xb715aa01 in g_main_context_dispatch () 
from /opt/kdedir/lib/libglib-2.0.so.0
#19 0xb715da76 in g_main_context_iterate () 
from /opt/kdedir/lib/libglib-2.0.so.0
#20 0xb715dff7 in g_main_context_iteration ()
from /opt/kdedir/lib/libglib-2.0.so.0
#21 0xb7682210 in QEventDispatcherGlib::processEvents (this=0x8133e48,
    flags=@0xbfb4d7d8) at kernel/qeventdispatcher_glib.cpp:327
#22 0xb78aa188 in QGuiEventDispatcherGlib::processEvents (this=0x8133e48,
    flags=@0xbfb4d80c) at kernel/qguieventdispatcher_glib.cpp:178
#23 0xb76564e2 in QEventLoop::processEvents (this=0xbfb4d880, 
flags=@0xbfb4d844)
    at kernel/qeventloop.cpp:126
#24 0xb7656664 in QEventLoop::exec (this=0xbfb4d880, flags=@0xbfb4d888)
    at kernel/qeventloop.cpp:168
#25 0xb7659ca7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:729
#26 0xb7812fc8 in QApplication::exec () at kernel/qapplication.cpp:3035
#27 0x08057c39 in main (arg   from /opt/kdedir/lib/libglib-2.0.so.0
#21 0xb7682210 in QEventDispatcherGlib::processEvents (this=0x8133e48,
    flags=@0xbfb4d7d8) at kernel/qeventdispatcher_glib.cpp:327
#22 0xb78aa188 in QGuiEventDispatcherGlib::processEvents (this=0x8133e48,
    flags=@0xbfb4d80c) at kernel/qguieventdispatcher_glib.cpp:178
#23 0xb76564e2 in QEventLoop::processEvents (this=0xbfb4d880, 
flags=@0xbfb4d844)
    at kernel/qeventloop.cpp:126
#24 0xb7656664 in QEventLoop::exec (this=0xbfb4d880, flags=@0xbfb4d888)
    at kernel/qeventloop.cpp:168
#25 0xb7659ca7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:729
#26 0xb7812fc8 in QApplication::exec () at kernel/qapplication.cpp:3035
#27 0x08057c39 in main (argc=Cannot access memory at address 0x0
) at src/main.cpp:89


_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user

[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux