Application: nepomukservicestub (0.2) KDE Platform Version: 4.6.1 (4.6.1) Qt Version: 4.7.2 Operating System: Linux 2.6.38-1207-omap4 armv7l Distribution: Ubuntu Natty (development branch) -- Information about the crash: - What I was doing when the application crashed: Booting a fresh install on armel omap4 pandaboard running Kubuntu Natty Beta 1 The crash can be reproduced every time. -- Backtrace: Application: Nepomuk Service Stub (nepomukservicestub), signal: Segmentation fault [KCrash Handler] #6 0x44710578 in operator int (this=0x1270b08) at /usr/include/qt4/QtCore/qbasicatomic.h:85 #7 qt_metatype_id (this=0x1270b08) at ../../../backends/virtuoso/virtuosocontroller.cpp:43 #8 qt_metatype_id (this=0x1270b08) at /usr/include/qt4/QtCore/qmetatype.h:169 #9 qMetaTypeId<QProcess::ExitStatus> (this=0x1270b08) at /usr/include/qt4/QtCore/qmetatype.h:230 #10 qRegisterMetaType<QProcess::ExitStatus> (this=0x1270b08) at /usr/include/qt4/QtCore/qmetatype.h:243 #11 Soprano::VirtuosoController::VirtuosoController (this=0x1270b08) at ../../../backends/virtuoso/virtuosocontroller.cpp:83 #12 0x4470d578 in Soprano::Virtuoso::BackendPlugin::createModel (this=0x1267e08, settings=...) at ../../../backends/virtuoso/virtuosobackend.cpp:71 #13 0x42077370 in Nepomuk::Repository::open (this=0x126d880) at ../../../../nepomuk/services/storage/repository.cpp:158 #14 0x420784ec in Nepomuk::Repository::qt_metacall (this=0x126d880, _c=QMetaObject::InvokeMetaMethod, _id=-4, _a=0x12615d8) at ./repository.moc:83 #15 0x401d47a0 in QMetaObject::metacall (object=0x126d880, cl=<value optimized out>, idx=<value optimized out>, argv=<value optimized out>) at kernel/qmetaobject.cpp:237 #16 0x401ddeb8 in QObject::event (this=0x126d880, e=<value optimized out>) at kernel/qobject.cpp:1226 #17 0x40930170 in QApplicationPrivate::notify_helper (this=<value optimized out>, receiver=0x126d880, e=0x1267570) at kernel/qapplication.cpp:4462 #18 0x40933198 in QApplication::notify (this=0xbe9f07d8, receiver=0x126d880, e=0x1267570) at kernel/qapplication.cpp:4341 #19 0x40643218 in KApplication::notify (this=0xbe9f07d8, receiver=0x126d880, event=0x1267570) at ../../kdeui/kernel/kapplication.cpp:311 #20 0x401d0792 in QCoreApplication::notifyInternal (this=<value optimized out>, receiver=<value optimized out>, event=0x1267570) at kernel/qcoreapplication.cpp:731 #21 0x401d2cc4 in sendEvent (receiver=0x0, event_type=0, data=0x1187c78) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #22 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x1187c78) at kernel/qcoreapplication.cpp:1372 #23 0x401eda04 in sendPostedEvents (s=0x11ba578) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220 #24 postEventSourceDispatch (s=0x11ba578) at kernel/qeventdispatcher_glib.cpp:277 #25 0x410837f6 in g_main_context_dispatch () from /lib/arm-linux-gnueabi/libglib-2.0.so.0 #26 0x41083d40 in ?? () from /lib/arm-linux-gnueabi/libglib-2.0.so.0 #27 0x41083d40 in ?? () from /lib/arm-linux-gnueabi/libglib-2.0.so.0 Backtrace stopped: previous frame identical to this frame (corrupt stack?) Reported using DrKonqi
Can this be reproduced with a newer version of KDE? Say 4.6.4 or even 4.7.2?
Changing status to 'Waiting For Info'
This was fixed in Kubuntu Oneiric. Sorry, I didn't have time to help work on debugging this. My daily schedule was 110% consumed with Arm Server testing. Testing Kubuntu is something I have been doing as a courtesy for Scott Kitterman on the side. I will keep doing milestone testing until the KDE/Kubuntu community can purchase supported Arm hardware and take over full time.