Bug 292090 - Konquest crashes when I try start a new game
Summary: Konquest crashes when I try start a new game
Status: RESOLVED DUPLICATE of bug 296290
Alias: None
Product: konquest
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Chakra Linux
: NOR crash
Target Milestone: ---
Assignee: Pierre Ducroquet
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-21 03:57 UTC by André Marcelo Alvarenga
Modified: 2012-08-10 12:09 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (5.49 KB, text/plain)
2012-03-19 22:54 UTC, Antonin Blanc
Details
New crash information added by DrKonqi (5.22 KB, text/plain)
2012-08-10 12:09 UTC, Anthony Smitha
Details

Note You need to log in before you can comment on or make changes to this bug.
Description André Marcelo Alvarenga 2012-01-21 03:57:37 UTC
Application: konquest (2.1)
KDE Platform Version: 4.8.00 (4.8.0
Qt Version: 4.8.0
Operating System: Linux 3.1-CHAKRA i686
Distribution: "Chakra Linux"

-- Information about the crash:
- What I was doing when the application crashed:

- Run Konquest
- Click in "New"
- In Start New Game dialog, click in "OK"
- In Final Standings dialog, click in "OK"
- About 3 seconds later the game crashed.

The crash can be reproduced every time.

-- Backtrace:
Application: Konquest (konquest), signal: Segmentation fault
[KCrash Handler]
#7  MapScene::getSectorSize (this=0x9c61f98) at /chakra/desktop-unstable/kdegames/src/kdegames-4.8.0/konquest/map/mapscene.cc:192
#8  0x080633e8 in PlanetItem::boundingRect (this=0x9f76a38) at /chakra/desktop-unstable/kdegames/src/kdegames-4.8.0/konquest/map/mapitems.cc:77
#9  0xb6f17e1d in QGraphicsItemPrivate::effectiveBoundingRect(QGraphicsItem*) const () from /usr/lib/libQtGui.so.4
#10 0xb6f17fc2 in QGraphicsItemPrivate::sceneEffectiveBoundingRect() const () from /usr/lib/libQtGui.so.4
#11 0xb6f4f138 in ?? () from /usr/lib/libQtGui.so.4
#12 0xb6f4f3e8 in ?? () from /usr/lib/libQtGui.so.4
#13 0xb68b22f4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#14 0xb68b7723 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#15 0xb7544fa1 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#16 0xb62e623e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#17 0xb631aa30 in ?? () from /usr/lib/libQtCore.so.4
#18 0xb6318128 in ?? () from /usr/lib/libQtCore.so.4
#19 0xb6318162 in ?? () from /usr/lib/libQtCore.so.4
#20 0xb5671532 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#21 0xb5671d10 in ?? () from /usr/lib/libglib-2.0.so.0
#22 0xb5671fc4 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#23 0xb6318947 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#24 0xb696598a in ?? () from /usr/lib/libQtGui.so.4
#25 0xb62e4dcd in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#26 0xb62e5069 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#27 0xb62ea24a in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#28 0xb68b0154 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#29 0x080570ce in main (argc=) at /chakra/desktop-unstable/kdegames/src/kdegames-4.8.0/konquest/Konquest.cc:58

Reported using DrKonqi
Comment 1 Ron Bentley 2012-03-11 00:44:53 UTC
I could reproduce this on Konquest 2.1, KDE Platform Version 4.8.1, Qt version 4.8.0-1ubuntu9 (Kubuntu 12.04 beta).  It happened when both players were computers (weak), which seems to be the default.  When I changed player 0 to a human, I could then play the game -- although it would later crash when I closed Konquest (reported in a subsequent bug).
Comment 2 Antonin Blanc 2012-03-19 22:54:15 UTC
Created attachment 69743 [details]
New crash information added by DrKonqi

konquest (2.1) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0

exactly same problem here, it always crashs after i start new game :C

-- Backtrace (Reduced):
#6  0x000000000041d992 in MapScene::getSectorSize() ()
#7  0x000000000041e935 in PlanetItem::boundingRect() const ()
#8  0x00007f0b777548de in QGraphicsItemPrivate::effectiveBoundingRect(QGraphicsItem*) const () from /usr/lib64/qt4/libQtGui.so.4
#9  0x00007f0b77754a52 in QGraphicsItemPrivate::sceneEffectiveBoundingRect() const () from /usr/lib64/qt4/libQtGui.so.4
#10 0x00007f0b77793fec in QGraphicsSceneBspTreeIndexPrivate::_q_updateIndex() () from /usr/lib64/qt4/libQtGui.so.4
Comment 3 Jekyll Wu 2012-07-05 21:24:53 UTC

*** This bug has been marked as a duplicate of bug 296290 ***
Comment 4 Anthony Smitha 2012-08-10 12:09:21 UTC
Created attachment 73087 [details]
New crash information added by DrKonqi

konquest (2.1) on KDE Platform 4.8.4 (4.8.4) using Qt 4.8.1

I clicked on start new game, left Computer vs Computer as the only two players, and the game crashed.

-- Backtrace (Reduced):
#7  MapScene::getSectorSize (this=0xa1a52a8) at ../../konquest/map/mapscene.cc:192
#8  0x080621b8 in PlanetItem::boundingRect (this=0xa3734c0) at ../../konquest/map/mapitems.cc:77
#9  0xb6e8529d in QGraphicsItemPrivate::effectiveBoundingRect (this=0xa65f868, topMostEffectItem=0x0) at graphicsview/qgraphicsitem.cpp:2857
#10 0xb6e85442 in QGraphicsItemPrivate::sceneEffectiveBoundingRect (this=0xa65f868) at graphicsview/qgraphicsitem.cpp:2908
#11 0xb6ebc9e8 in _q_updateIndex (this=0xa1a54d8) at graphicsview/qgraphicsscenebsptreeindex.cpp:175