I found another.  Should I post this in a different area?  Or is this ok
here?

Core was generated by `./rosegarden'.
Program terminated with signal 6, Aborted.
#0  0x00007f7148d57425 in __GI_raise (sig=<optimized out>)
    at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
64      ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  0x00007f7148d57425 in __GI_raise (sig=<optimized out>)
    at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1  0x00007f7148d5ab8b in __GI_abort () at abort.c:91
#2  0x00007f714b77b5db in qt_message_output (msgType=<optimized out>,
    buf=0x27a0648 "ASSERT failure in : \"Got an update for an invalid
inteface. Investigate this.\", file atspiadaptor.cpp, line 899") at
global/qglobal.cpp:2284
#3  0x00007f714b77b98f in qt_message(QtMsgType, const char *, typedef
__va_list_tag __va_list_tag *) (msgType=QtFatalMsg,
    msg=0x7f714b8e8fb8 "ASSERT failure in %s: \"%s\", file %s, line %d",
ap=0x7fff7627dec8)
    at global/qglobal.cpp:2330
#4  0x00007f714b77bb34 in qFatal (msg=<optimized out>) at
global/qglobal.cpp:2513
#5  0x00007f7138b1b24f in AtSpiAdaptor::notify(int, QAccessibleInterface*,
int) ()
   from
/usr/lib/x86_64-linux-gnu/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so
#6  0x00007f714c859bc1 in QAccessible::updateAccessibility (o=<optimized
out>, who=0,
    reason=QAccessible::Focus) at accessible/qaccessible_unix.cpp:118
#7  0x00007f714c885ee8 in QListView::currentChanged (this=0x2629460,
current=...,
    previous=...) at itemviews/qlistview.cpp:3172
#8  0x00007f714b899781 in QMetaObject::activate (sender=0x268e100,
m=<optimized out>,
    local_signal_index=<optimized out>, argv=0x7fff7627e750) at
kernel/qobject.cpp:3547
#9  0x00007f714c8b60aa in QItemSelectionModel::currentChanged
(this=<optimized out>,
    _t1=..., _t2=...) at .moc/release-shared/moc_qitemselectionmodel.cpp:173
#10 0x00007f714c8b61a0 in QItemSelectionModel::setCurrentIndex
(this=0x268e100, index=...,
    command=...) at itemviews/qitemselectionmodel.cpp:1175
---Type <return> to continue, or q <return> to quit---
#11 0x00007f714c8646d4 in QAbstractItemView::mousePressEvent
(this=0x2629460,
    event=<optimized out>) at itemviews/qabstractitemview.cpp:1682
#12 0x00007f714c389299 in QWidget::event (this=0x2629460,
event=0x7fff7627f5a0)
    at kernel/qwidget.cpp:8367
#13 0x00007f714c749836 in QFrame::event (this=0x2629460, e=0x7fff7627f5a0)
    at widgets/qframe.cpp:557
#14 0x00007f714c85deeb in QAbstractItemView::viewportEvent (this=0x2629460,
    event=0x7fff7627f5a0) at itemviews/qabstractitemview.cpp:1644
#15 0x00007f714b8854b8 in
QCoreApplicationPrivate::sendThroughObjectEventFilters (
    this=<optimized out>, receiver=0x24eb6d0, event=0x7fff7627f5a0)
    at kernel/qcoreapplication.cpp:1025
#16 0x00007f714c33877f in notify_helper (e=0x7fff7627f5a0,
receiver=0x24eb6d0,
    this=0x22c8b30) at kernel/qapplication.cpp:4552
#17 QApplicationPrivate::notify_helper (this=0x22c8b30, receiver=0x24eb6d0,
    e=0x7fff7627f5a0) at kernel/qapplication.cpp:4528
#18 0x00007f714c33df2f in QApplication::notify (this=<optimized out>,
receiver=0x24eb6d0,
    e=0x7fff7627f5a0) at kernel/qapplication.cpp:4099
#19 0x00007f714b88532c in QCoreApplication::notifyInternal
(this=0x7fff76282060,
    receiver=0x24eb6d0, event=0x7fff7627f5a0) at
kernel/qcoreapplication.cpp:915
#20 0x00007f714c339782 in sendEvent (event=<optimized out>,
receiver=<optimized out>)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#21 QApplicationPrivate::sendMouseEvent (receiver=0x24eb6d0,
event=0x7fff7627f5a0,
    alienWidget=0x24eb6d0, nativeWidget=0x7fff76280290,
buttonDown=0x24eb6d0,
---Type <return> to continue, or q <return> to quit---
    lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3167
#22 0x00007f714c3b8b15 in QETWidget::translateMouseEvent
(this=0x7fff76280290,
    event=<optimized out>) at kernel/qapplication_x11.cpp:4617
#23 0x00007f714c3b7ace in QApplication::x11ProcessEvent
(this=0x7fff76282060,
    event=0x7fff7627fe70) at kernel/qapplication_x11.cpp:3732
#24 0x00007f714c3e1052 in x11EventSourceDispatch (s=0x22c9670, callback=0,
user_data=0x0)
    at kernel/qguieventdispatcher_glib.cpp:146
#25 0x00007f71485f8173 in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x00007f71485f84c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x00007f71485f8584 in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x00007f714b8b48bf in QEventDispatcherGlib::processEvents
(this=0x22ce490, flags=...)
    at kernel/qeventdispatcher_glib.cpp:424
#29 0x00007f714c3e0cde in QGuiEventDispatcherGlib::processEvents
(this=<optimized out>,
    flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#30 0x00007f714b883e62 in QEventLoop::processEvents (this=<optimized out>,
flags=...)
    at kernel/qeventloop.cpp:149
#31 0x00007f714b8840b7 in QEventLoop::exec (this=0x7fff76280210, flags=...)
    at kernel/qeventloop.cpp:204
#32 0x00007f714c808f86 in QDialog::exec (this=0x7fff76280290) at
dialogs/qdialog.cpp:554
#33 0x00000000007cb942 in Rosegarden::FileDialog::getOpenFileName(QWidget*,
QString const&, QString const&, QString const&, QString*,
QFlags<QFileDialog::Option>) ()
---Type <return> to continue, or q <return> to quit---
#34 0x0000000000657378 in
Rosegarden::RosegardenMainWindow::slotImportMIDI() ()
#35 0x000000000065b42a in
Rosegarden::RosegardenMainWindow::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) ()
#36 0x00007f714b899781 in QMetaObject::activate (sender=0x235b9c0,
m=<optimized out>,
    local_signal_index=<optimized out>, argv=0x7fff762808f0) at
kernel/qobject.cpp:3547
#37 0x00007f714c332072 in QAction::triggered (this=<optimized out>,
_t1=false)
    at .moc/release-shared/moc_qaction.cpp:277
#38 0x00007f714c33225f in QAction::activate (this=0x235b9c0,
event=<optimized out>)
    at kernel/qaction.cpp:1257
#39 0x00007f714c7845e9 in QMenuPrivate::activateCausedStack
(this=0x2364a80,
    causedStack=..., action=0x235b9c0, action_e=QAction::Trigger, self=true)
    at widgets/qmenu.cpp:1028
#40 0x00007f714c78a742 in QMenuPrivate::activateAction (this=0x2364a80,
action=0x235b9c0,
    action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1120
#41 0x00007f714c388fb4 in QWidget::event (this=0x3372f40,
event=0x7fff762812c0)
    at kernel/qwidget.cpp:8371
#42 0x00007f714c78bcdb in QMenu::event (this=0x3372f40, e=0x7fff762812c0)
    at widgets/qmenu.cpp:2469
#43 0x00007f714c3387b4 in notify_helper (e=0x7fff762812c0,
receiver=0x3372f40,
    this=0x22c8b30) at kernel/qapplication.cpp:4556
#44 QApplicationPrivate::notify_helper (this=0x22c8b30, receiver=0x3372f40,
    e=0x7fff762812c0) at kernel/qapplication.cpp:4528
#45 0x00007f714c33df2f in QApplication::notify (this=<optimized out>,
receiver=0x3372f40,
---Type <return> to continue, or q <return> to quit---
    e=0x7fff762812c0) at kernel/qapplication.cpp:4099
#46 0x00007f714b88532c in QCoreApplication::notifyInternal
(this=0x7fff76282060,
    receiver=0x3372f40, event=0x7fff762812c0) at
kernel/qcoreapplication.cpp:915
#47 0x00007f714c339782 in sendEvent (event=<optimized out>,
receiver=<optimized out>)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#48 QApplicationPrivate::sendMouseEvent (receiver=0x3372f40,
event=0x7fff762812c0,
    alienWidget=0x0, nativeWidget=0x3372f40, buttonDown=0x0,
lastMouseReceiver=...,
    spontaneous=true) at kernel/qapplication.cpp:3167
#49 0x00007f714c3b91e1 in QETWidget::translateMouseEvent (this=0x3372f40,
    event=<optimized out>) at kernel/qapplication_x11.cpp:4551
#50 0x00007f714c3b7ace in QApplication::x11ProcessEvent
(this=0x7fff76282060,
    event=0x7fff76281b90) at kernel/qapplication_x11.cpp:3732
#51 0x00007f714c3e1052 in x11EventSourceDispatch (s=0x22c9670, callback=0,
user_data=0x0)
    at kernel/qguieventdispatcher_glib.cpp:146
#52 0x00007f71485f8173 in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#53 0x00007f71485f84c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#54 0x00007f71485f8584 in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#55 0x00007f714b8b48bf in QEventDispatcherGlib::processEvents
(this=0x22ce490, flags=...)
    at kernel/qeventdispatcher_glib.cpp:424
#56 0x00007f714c3e0cde in QGuiEventDispatcherGlib::processEvents
(this=<optimized out>,
    flags=...) at kernel/qguieventdispatcher_glib.cpp:204
---Type <return> to continue, or q <return> to quit---
#57 0x00007f714b883e62 in QEventLoop::processEvents (this=<optimized out>,
flags=...)
    at kernel/qeventloop.cpp:149
#58 0x00007f714b8840b7 in QEventLoop::exec (this=0x7fff76281f30, flags=...)
    at kernel/qeventloop.cpp:204
#59 0x00007f714b889407 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1187
#60 0x00000000004499ba in main ()

I was so happy to have it working that I didnt yet uninstall "qt-at-spi".
I am now going to uninstall that and reconfigure and compile in case that
is what is causing this bug.


On Tue, Oct 22, 2013 at 8:25 AM, Brian Clem <mrbrianc...@gmail.com> wrote:

> You were correct.  I checked my config settings and I had --enable-debug
> at the end.
>
> Went back and reconfigured w/o debug option, built and it runs without
> crashing.
>
> Egg removed from face.  Thank you!
>
>
> On Tue, Oct 22, 2013 at 8:01 AM, D. Michael McIntyre <
> rosegarden.trumpe...@gmail.com> wrote:
>
>> On 10/22/2013 07:22 AM, Brian Clem wrote:
>>
>> > QSpiAccessible::accessibleEvent not handled:  \"6\"
>>
>> There are lots of applications crashing with exactly the same kind of
>> trace.  I think that is coming from auto-generated code over which we
>> have no control; code generated by the meta-object compiler in Qt.
>> There are wide suggestions to work around this problem by removing the
>> 'qt-at-spi' package from your system.
>>
>> I guess the most important question is how you built Rosegarden.  If
>> that is a debug build (./configure --enable-debug) then you probably
>> shouldn't be experiencing a crash in spite of the problem there.  We
>> have a Qt option enabled that causes it to crash on warnings such as
>> these, for debugging purposes, and that option is NOT supposed to be
>> enabled in a production build. However, I suspect it actually is enabled
>> in production builds anyway.  I keep meaning to test that intentionally,
>> and haven't gotten around to it.
>>
>> Anyway, I don't see a solution for the QSpiAccessible::accessibleEvent
>> nonsense other than the listed workaround.  It's not something we're
>> doing directly.  I suppose it's possible you have some weird
>> accessibility stuff enabled on your system; maybe for kids with
>> disabilities or something.  If so, yours makes for an interesting test
>> environment.  If not, we'll just try having you remove the 'qt-at-spi'
>> package and move on.  I don't actually see what use that thing is
>> supposed to be anyway.
>>
>> --
>> D. Michael McIntyre
>>
>>
>> ------------------------------------------------------------------------------
>> October Webinars: Code for Performance
>> Free Intel webinars can help you accelerate application performance.
>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
>> from
>> the latest Intel processors and coprocessors. See abstracts and register >
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Rosegarden-user mailing list
>> Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
>> https://lists.sourceforge.net/lists/listinfo/rosegarden-user
>>
>
>
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
_______________________________________________
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user

Reply via email to