Pairs ready for wild explorers

Jeremy Whiting jpwhiting at kde.org
Thu Sep 29 22:05:14 UTC 2011


Built and tried to run it here and got this crash after entering my
name and choosing kde apps theme:

Application: pairs (pairs), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f8558711760 (LWP 24056))]

Thread 2 (Thread 0x7f853cd0e700 (LWP 24634)):
#0  0x00007f8553e93723 in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007f854f9619e4 in ?? () from /lib/libglib-2.0.so.0
#2  0x00007f854f961f1d in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3  0x00007f8554d204b6 in QEventDispatcherGlib::processEvents
(this=0x1c4a660, flags=...) at
/home/jeremy/devel/kde/src/qt-copy/src/corelib/kernel/qeventdispatcher_glib.cpp:426
#4  0x00007f8554ce1c1c in QEventLoop::processEvents
(this=0x7f853cd0ddb0, flags=...) at
/home/jeremy/devel/kde/src/qt-copy/src/corelib/kernel/qeventloop.cpp:149
#5  0x00007f8554ce1da6 in QEventLoop::exec (this=0x7f853cd0ddb0,
flags=...) at /home/jeremy/devel/kde/src/qt-copy/src/corelib/kernel/qeventloop.cpp:204
#6  0x00007f8554bb083b in QThread::exec (this=0x1c54c00) at
/home/jeremy/devel/kde/src/qt-copy/src/corelib/thread/qthread.cpp:501
#7  0x00007f8554bb09da in QThread::run (this=0x1c54c00) at
/home/jeremy/devel/kde/src/qt-copy/src/corelib/thread/qthread.cpp:568
#8  0x00007f8554bb3168 in QThreadPrivate::start (arg=0x1c54c00) at
/home/jeremy/devel/kde/src/qt-copy/src/corelib/thread/qthread_unix.cpp:298
#9  0x00007f85548f5b40 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#10 0x00007f8553e9e36d in clone () from /lib/x86_64-linux-gnu/libc.so.6
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f8558711760 (LWP 24056)):
[KCrash Handler]
#6  0x000000000041399d in CardItem::setType (this=0x1e05970,
type=CARD_SOUND, file=..., archive=...) at
/home/jeremy/devel/kde/src/pairs/src/carditem.cpp:88
#7  0x0000000000417b74 in PairsView::newGame (this=0x1628760,
theme=..., media=0x1679860) at
/home/jeremy/devel/kde/src/pairs/src/pairsview.cpp:117
#8  0x000000000041538d in Pairs::newGame (this=0x16228c0) at
/home/jeremy/devel/kde/src/pairs/src/pairs.cpp:116
#9  0x0000000000415b9a in Pairs::qt_static_metacall (_o=0x16228c0,
_c=QMetaObject::InvokeMetaMethod, _id=3, _a=0x16b0600) at
/home/jeremy/devel/kde/build/pairs/src/pairs.moc:56
#10 0x00007f8554cfbf57 in QMetaCallEvent::placeMetaCall
(this=0x167e550, object=0x16228c0) at
/home/jeremy/devel/kde/src/qt-copy/src/corelib/kernel/qobject.cpp:524
#11 0x00007f8554cfd1dd in QObject::event (this=0x16228c0, e=0x167e550)
at /home/jeremy/devel/kde/src/qt-copy/src/corelib/kernel/qobject.cpp:1194
#12 0x00007f85560e032d in QWidget::event (this=0x16228c0,
event=0x167e550) at
/home/jeremy/devel/kde/src/qt-copy/src/gui/kernel/qwidget.cpp:8809
#13 0x00007f85565cc714 in QMainWindow::event (this=0x16228c0,
event=0x167e550) at
/home/jeremy/devel/kde/src/qt-copy/src/gui/widgets/qmainwindow.cpp:1478
#14 0x00007f855820a7e8 in KXmlGuiWindow::event (this=0x16228c0,
ev=0x167e550) at
/home/jeremy/devel/kde/src/kdelibs/kdeui/xmlgui/kxmlguiwindow.cpp:126
#15 0x00007f855607a44e in QApplicationPrivate::notify_helper
(this=0x14d8250, receiver=0x16228c0, e=0x167e550) at
/home/jeremy/devel/kde/src/qt-copy/src/gui/kernel/qapplication.cpp:4518
#16 0x00007f855607a150 in QApplication::notify (this=0x7fff496f29d0,
receiver=0x16228c0, e=0x167e550) at
/home/jeremy/devel/kde/src/qt-copy/src/gui/kernel/qapplication.cpp:4483
#17 0x00007f855810f906 in KApplication::notify (this=0x7fff496f29d0,
receiver=0x16228c0, event=0x167e550) at
/home/jeremy/devel/kde/src/kdelibs/kdeui/kernel/kapplication.cpp:311
#18 0x00007f8554ce4352 in QCoreApplication::notifyInternal
(this=0x7fff496f29d0, receiver=0x16228c0, event=0x167e550) at
/home/jeremy/devel/kde/src/qt-copy/src/corelib/kernel/qcoreapplication.cpp:876
#19 0x00007f855606b0c1 in QCoreApplication::sendEvent
(receiver=0x16228c0, event=0x167e550) at
../../include/QtCore/../../../../src/qt-copy/src/corelib/kernel/qcoreapplication.h:231
#20 0x00007f8554ce5366 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x14a7250) at
/home/jeremy/devel/kde/src/qt-copy/src/corelib/kernel/qcoreapplication.cpp:1500
#21 0x00007f8554ce4f87 in QCoreApplication::sendPostedEvents
(receiver=0x0, event_type=0) at
/home/jeremy/devel/kde/src/qt-copy/src/corelib/kernel/qcoreapplication.cpp:1393
#22 0x00007f8556145081 in QCoreApplication::sendPostedEvents () at
../../include/QtCore/../../../../src/qt-copy/src/corelib/kernel/qcoreapplication.h:236
#23 0x00007f8554d1fbbc in postEventSourceDispatch (s=0x14cf5c0) at
/home/jeremy/devel/kde/src/qt-copy/src/corelib/kernel/qeventdispatcher_glib.cpp:279
#24 0x00007f854f9614a3 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#25 0x00007f854f961c80 in ?? () from /lib/libglib-2.0.so.0
#26 0x00007f854f961f1d in g_main_context_iteration () from /lib/libglib-2.0.so.0
#27 0x00007f8554d20493 in QEventDispatcherGlib::processEvents
(this=0x14a8b30, flags=...) at
/home/jeremy/devel/kde/src/qt-copy/src/corelib/kernel/qeventdispatcher_glib.cpp:424
#28 0x00007f855615126c in QGuiEventDispatcherGlib::processEvents
(this=0x14a8b30, flags=...) at
/home/jeremy/devel/kde/src/qt-copy/src/gui/kernel/qguieventdispatcher_glib.cpp:204
#29 0x00007f8554ce1c1c in QEventLoop::processEvents
(this=0x7fff496f2940, flags=...) at
/home/jeremy/devel/kde/src/qt-copy/src/corelib/kernel/qeventloop.cpp:149
#30 0x00007f8554ce1da6 in QEventLoop::exec (this=0x7fff496f2940,
flags=...) at /home/jeremy/devel/kde/src/qt-copy/src/corelib/kernel/qeventloop.cpp:204
#31 0x00007f8554ce49d2 in QCoreApplication::exec () at
/home/jeremy/devel/kde/src/qt-copy/src/corelib/kernel/qcoreapplication.cpp:1148
#32 0x00007f8556077674 in QApplication::exec () at
/home/jeremy/devel/kde/src/qt-copy/src/gui/kernel/qapplication.cpp:3779
#33 0x0000000000417121 in main (argc=1, argv=0x7fff496f2cf8) at
/home/jeremy/devel/kde/src/pairs/src/main.cpp:74

maybe I need to enter two player names?

Jeremy

On Thu, Sep 29, 2011 at 3:15 PM, Aleix Pol <aleixpol at kde.org> wrote:
> Hi!
> Some time ago we discussed in length various aspects of this application
> that eventually was called KMemory and it was hidden at the bottom of our
> git.kde.org repository and Marco rescued for all our pleasure and benefit.
> (big round of applause for Marco! :))
> The last two days we merged a couple of features that put the application in
> a testable state, it's still unpolished but most of the features we want for
> the application are there and we would like some of you to give us some
> feedback if you have the time.
> If you find any problem, feel free to reported to our fresh new bugs.kde.org
> account or to contact us here.
> We're looking forward to it, thanks in advance!
> Aleix
> Disclaimer: We're asking for ideas and collaboration, we know it's not ready
> _______________________________________________
> kde-edu mailing list
> kde-edu at mail.kde.org
> https://mail.kde.org/mailman/listinfo/kde-edu
>
>


More information about the kde-edu mailing list