Bug 87705 - kpat crashes when choosing unknown game type
Summary: kpat crashes when choosing unknown game type
Status: RESOLVED DUPLICATE of bug 87451
Alias: None
Product: kpat
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Stephan Kulow
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-21 21:50 UTC by Anders Lindén
Modified: 2004-08-22 17:02 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Anders Lindén 2004-08-21 21:50:54 UTC
Version:           2.2 (using KDE 3.3.0, compiled sources)
Compiler:          gcc version 3.4.1 20040803 (Gentoo Linux 3.4.1-r2, ssp-3.4-2, pie-8.7.6.5)
OS:                Linux (i686) release 2.6.8

Started KPatience in my newly compiled KDE 3.3.0, and when choosing game type I found the option "unknown" in the list. Choosing that game type causes kpat to crash and give this backtrace:

Using host libthread_db library "/lib/libthread_db.so.1".
[KCrash handler]
#5  0x0805a93c in Dealer::setAutoDropEnabled (this=0x0) at dealer.cpp:987
#6  0x0806886b in pWidget::newGameType (this=0x818f030) at pwidget.cpp:336
#7  0x0806a314 in pWidget::qt_invoke (this=0x818f030, _id=75, _o=0xbfffe830)
    at pwidget.moc:136
#8  0x40d50b94 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#9  0x40d5132c in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#10 0x405b0499 in KAction::activated (this=0x1) at qmetaobject.h:261
#11 0x405b04bd in KAction::slotActivated (this=0x1) at kaction.cpp:1057
#12 0x405c75eb in KSelectAction::slotActivated (this=0x819b568)
    at kactionclasses.cpp:781
#13 0x405c7a2e in KSelectAction::qt_invoke (this=0x819b568, _id=22,
    _o=0xbfffe9e0) at kactionclasses.moc:357
#14 0x40d50b94 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#15 0x410ab51d in QSignal::signal () from /usr/qt/3/lib/libqt-mt.so.3
#16 0x40d6b6c1 in QSignal::activate () from /usr/qt/3/lib/libqt-mt.so.3
#17 0x40d730c3 in QSingleShotTimer::event () from /usr/qt/3/lib/libqt-mt.so.3
#18 0x40cecbef in QApplication::internalNotify ()
   from /usr/qt/3/lib/libqt-mt.so.3
#19 0x40cecd8c in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3
#20 0x4084d4c5 in KApplication::notify (this=0xbffff130, receiver=0x81bca00,
    event=0xbfffee70) at kapplication.cpp:495
#21 0x40ce019c in QEventLoop::activateTimers ()
   from /usr/qt/3/lib/libqt-mt.so.3
#22 0x40c990b1 in QEventLoop::processEvents () from /usr/qt/3/lib/libqt-mt.so.3
#23 0x40d034f1 in QEventLoop::enterLoop () from /usr/qt/3/lib/libqt-mt.so.3
#24 0x40d03446 in QEventLoop::exec () from /usr/qt/3/lib/libqt-mt.so.3
#25 0x40cebd4f in QApplication::exec () from /usr/qt/3/lib/libqt-mt.so.3
#26 0x08056856 in main (argc=1, argv=0x1) at main.cpp:71
Comment 1 Stephan Kulow 2004-08-22 17:02:52 UTC

*** This bug has been marked as a duplicate of 87451 ***