Application: konquest (2.1) KDE Platform Version: 4.8.1 (4.8.1) Qt Version: 4.8.0 Operating System: Linux 3.2.0-18-generic-pae i686 Distribution: Ubuntu precise (development branch) -- Information about the crash: - What I was doing when the application crashed: I had just completed one game, and had started another one. The crash happened (and often happens) at the exact moment I first mouse over a planet in the fresh game, in order to see its details as a tooltip. This is on a beta release of Ubuntu 12.04 (Precise Pangolin) for i386, running a Unity 2D desktop. It's been happening for some time now. The crash can be reproduced some of the time. -- Backtrace: Application: Konquest (konquest), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xb4ca7980 (LWP 6217))] Thread 2 (Thread 0xb1bffb40 (LWP 6221)): #0 0xb7716424 in __kernel_vsyscall () #1 0xb5ef1020 in __GI___poll (fds=0xb12023b0, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0xb550db7b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb550011e in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb55005db in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb344598a in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 #6 0xb5523483 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #7 0xb55d1d4c in start_thread (arg=0xb1bffb40) at pthread_create.c:308 #8 0xb5eff76e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 1 (Thread 0xb4ca7980 (LWP 6217)): [KCrash Handler] #7 MapScene::getSectorSize (this=0x8da4198) at ../../konquest/map/mapscene.cc:192 #8 0x080621b8 in PlanetItem::boundingRect (this=0x8fa8cc0) at ../../konquest/map/mapitems.cc:77 #9 0xb6e9633d in QGraphicsItemPrivate::effectiveBoundingRect (this=0x8c1af78, topMostEffectItem=0x0) at graphicsview/qgraphicsitem.cpp:2857 #10 0xb6e964e2 in QGraphicsItemPrivate::sceneEffectiveBoundingRect (this=0x8c1af78) at graphicsview/qgraphicsitem.cpp:2908 #11 0xb6ecd868 in _q_updateIndex (this=0x8da43c8) at graphicsview/qgraphicsscenebsptreeindex.cpp:175 #12 QGraphicsSceneBspTreeIndexPrivate::_q_updateIndex (this=0x8da43c8) at graphicsview/qgraphicsscenebsptreeindex.cpp:120 #13 0xb6ecdb18 in QGraphicsSceneBspTreeIndex::event (this=0x8c0bba0, event=0xbfd8d28c) at graphicsview/qgraphicsscenebsptreeindex.cpp:704 #14 0xb6805d24 in notify_helper (e=0xbfd8d28c, receiver=0x8c0bba0, this=0x886ccc8) at kernel/qapplication.cpp:4555 #15 QApplicationPrivate::notify_helper (this=0x886ccc8, receiver=0x8c0bba0, e=0xbfd8d28c) at kernel/qapplication.cpp:4527 #16 0xb680b15d in QApplication::notify (this=0xbfd8d28c, receiver=0x8c0bba0, e=0xbfd8d28c) at kernel/qapplication.cpp:4284 #17 0xb74a0801 in KApplication::notify (this=0xbfd8d594, receiver=0x8c0bba0, event=0xbfd8d28c) at ../../kdeui/kernel/kapplication.cpp:311 #18 0xb62480ae in QCoreApplication::notifyInternal (this=0xbfd8d594, receiver=0x8c0bba0, event=0xbfd8d28c) at kernel/qcoreapplication.cpp:876 #19 0xb627d0c0 in sendEvent (event=0xbfd8d28c, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #20 QTimerInfoList::activateTimers (this=0x886b514) at kernel/qeventdispatcher_unix.cpp:611 #21 0xb627a828 in timerSourceDispatch (source=0x886b4e0) at kernel/qeventdispatcher_glib.cpp:186 #22 timerSourceDispatch (source=0x886b4e0) at kernel/qeventdispatcher_glib.cpp:180 #23 0xb54ffd8a in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 #24 0xb5500195 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #25 0xb5500271 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #26 0xb627afb7 in QEventDispatcherGlib::processEvents (this=0x886b958, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #27 0xb68be80a in QGuiEventDispatcherGlib::processEvents (this=0x886b958, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #28 0xb6246c3d in QEventLoop::processEvents (this=0xbfd8d4f4, flags=...) at kernel/qeventloop.cpp:149 #29 0xb6246ed9 in QEventLoop::exec (this=0xbfd8d4f4, flags=...) at kernel/qeventloop.cpp:204 #30 0xb624c5ea in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148 #31 0xb68038c4 in QApplication::exec () at kernel/qapplication.cpp:3816 #32 0x08055e9e in main (argc=0, argv=0x0) at ../../konquest/Konquest.cc:58 This bug may be a duplicate of or related to bug 292090. Possible duplicates by query: bug 295729, bug 292090. Reported using DrKonqi
Created attachment 70285 [details] New crash information added by DrKonqi konquest (2.1) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.0 - What I was doing when the application crashed: Finished one game and start another one. At this moment it crashes immediately. -- Backtrace (Reduced): #7 MapScene::getSectorSize (this=0x9fe1008) at ../../konquest/map/mapscene.cc:192 #8 0x08061f68 in PlanetItem::boundingRect (this=0xa3994d0) at ../../konquest/map/mapitems.cc:77 #9 0x017690ad in QGraphicsItemPrivate::effectiveBoundingRect (this=0xa28a708, topMostEffectItem=0x0) at graphicsview/qgraphicsitem.cpp:2857 #10 0x01769252 in QGraphicsItemPrivate::sceneEffectiveBoundingRect (this=0xa28a708) at graphicsview/qgraphicsitem.cpp:2908 #11 0x017a05c8 in _q_updateIndex (this=0x9fe1238) at graphicsview/qgraphicsscenebsptreeindex.cpp:175
Created attachment 70793 [details] New crash information added by DrKonqi konquest (2.1) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1 - What I was doing when the application crashed: Startin a new game after winning another one and moving the mouse. -- Backtrace (Reduced): #7 MapScene::getSectorSize (this=0x9799c20) at ../../konquest/map/mapscene.cc:192 #8 0x080621b8 in PlanetItem::boundingRect (this=0x99c2e30) at ../../konquest/map/mapitems.cc:77 #9 0xb6f5428d in QGraphicsItemPrivate::effectiveBoundingRect (this=0x98f1458, topMostEffectItem=0x0) at graphicsview/qgraphicsitem.cpp:2857 #10 0xb6f54432 in QGraphicsItemPrivate::sceneEffectiveBoundingRect (this=0x98f1458) at graphicsview/qgraphicsitem.cpp:2908 #11 0xb6f8b9d8 in _q_updateIndex (this=0x97a2928) at graphicsview/qgraphicsscenebsptreeindex.cpp:175
Created attachment 70879 [details] New crash information added by DrKonqi konquest (2.1) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1 - What I was doing when the application crashed: Just finished a game, started a new one. The game crashes instantly. - Custom settings of the application: I usually start the games that crash with Ctrl+N. -- Backtrace (Reduced): #6 MapScene::getSectorSize (this=0x1c1cda0) at ../../konquest/map/mapscene.cc:192 #7 0x000000000041ce25 in PlanetItem::boundingRect (this=0x1a1e5c0) at ../../konquest/map/mapitems.cc:77 #8 0x00007fcac3118c7b in QGraphicsItemPrivate::effectiveBoundingRect (this=0x22fb3c0, topMostEffectItem=0x0) at graphicsview/qgraphicsitem.cpp:2857 #9 0x00007fcac3118dd2 in QGraphicsItemPrivate::sceneEffectiveBoundingRect (this=<optimized out>) at graphicsview/qgraphicsitem.cpp:2908 #10 0x00007fcac314d128 in _q_updateIndex (this=0x1f6aea0) at graphicsview/qgraphicsscenebsptreeindex.cpp:175
Created attachment 71653 [details] New crash information added by DrKonqi konquest (2.1) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1 I won a game and started the next. When in the start up menu as soon as I move the mouse the game crashes. It happens 9/10 times. -- Backtrace (Reduced): #7 MapScene::getSectorSize (this=0x94eb100) at ../../konquest/map/mapscene.cc:192 #8 0x080621b8 in PlanetItem::boundingRect (this=0x95ccdb8) at ../../konquest/map/mapitems.cc:77 #9 0x0165e28d in QGraphicsItemPrivate::effectiveBoundingRect (this=0x9a656f8, topMostEffectItem=0x0) at graphicsview/qgraphicsitem.cpp:2857 #10 0x0165e432 in QGraphicsItemPrivate::sceneEffectiveBoundingRect (this=0x9a656f8) at graphicsview/qgraphicsitem.cpp:2908 #11 0x016959d8 in _q_updateIndex (this=0x94eb138) at graphicsview/qgraphicsscenebsptreeindex.cpp:175
*** Bug 292090 has been marked as a duplicate of this bug. ***
*** Bug 295729 has been marked as a duplicate of this bug. ***
*** Bug 301090 has been marked as a duplicate of this bug. ***
*** Bug 299856 has been marked as a duplicate of this bug. ***
*** Bug 302144 has been marked as a duplicate of this bug. ***
*** Bug 298171 has been marked as a duplicate of this bug. ***
*** Bug 298004 has been marked as a duplicate of this bug. ***
*** Bug 299791 has been marked as a duplicate of this bug. ***
*** Bug 296514 has been marked as a duplicate of this bug. ***
Created attachment 72801 [details] New crash information added by DrKonqi konquest (2.1) on KDE Platform 4.8.4 (4.8.4) using Qt 4.8.2 - What I was doing when the application crashed: Finished one game. Started a second game. It crashes frequently at this point. I think it crashes just after asking the number of planets, and while drawing the new game. I have a couple of "custom" settings. I run a dual screen, NVidia Left screen is larger than the right, but I usually play Konquest on right screen. When I maximize the window, I usually push the bottom of the window down below the bottom of the current screen, so I don't see all the comments, then maximize to the top. -- Backtrace (Reduced): #6 MapScene::getSectorSize (this=0x2843160) at /usr/src/debug/kdegames-4.8.4/konquest/map/mapscene.cc:192 #7 0x000000000041ce35 in PlanetItem::boundingRect (this=0x2f09290) at /usr/src/debug/kdegames-4.8.4/konquest/map/mapitems.cc:77 #8 0x0000003f3abb192b in QGraphicsItemPrivate::effectiveBoundingRect (this=0x2fa2000, topMostEffectItem=0x0) at graphicsview/qgraphicsitem.cpp:2857 #9 0x0000003f3abb1a82 in QGraphicsItemPrivate::sceneEffectiveBoundingRect (this=<optimized out>) at graphicsview/qgraphicsitem.cpp:2908 #10 0x0000003f3abe5da8 in _q_updateIndex (this=0x28434c0) at graphicsview/qgraphicsscenebsptreeindex.cpp:175
SVN commit 1310665 by aacid: Remove the graphic items from the scene on game end otherwise they try to access the map but we already killed it because the game ended FIXED-IN: 4.9.1 M +1 -0 gameview.cc M +9 -4 map/mapscene.cc M +1 -0 map/mapscene.h WebSVN link: http://websvn.kde.org/?view=rev&revision=1310665
SVN commit 1310667 by aacid: Forward-port aacid * r1310665 branches/KDE/4.9/kdegames/konquest/ (gameview.cc map/mapscene.cc map/mapscene.h) Remove the graphic items from the scene on game end otherwise they try to access the map but we already killed it because the game ended FIXED-IN: 4.9.1 M +1 -0 gameview.cc M +9 -4 map/mapscene.cc M +1 -0 map/mapscene.h WebSVN link: http://websvn.kde.org/?view=rev&revision=1310667
*** Bug 307770 has been marked as a duplicate of this bug. ***
Created attachment 75055 [details] New crash information added by DrKonqi konquest (2.1) on KDE Platform 4.8.5 (4.8.5) using Qt 4.8.1 - What I was doing when the application crashed: the crash happend when i try to change size of map while starting new game -- Backtrace (Reduced): #7 MapScene::getSectorSize (this=0xa150fa0) at ../../konquest/map/mapscene.cc:192 #8 0x08062188 in PlanetItem::boundingRect (this=0xa4879c8) at ../../konquest/map/mapitems.cc:77 #9 0xb6ee829d in QGraphicsItemPrivate::effectiveBoundingRect (this=0x9dd9f58, topMostEffectItem=0x0) at graphicsview/qgraphicsitem.cpp:2857 #10 0xb6ee8442 in QGraphicsItemPrivate::sceneEffectiveBoundingRect (this=0x9dd9f58) at graphicsview/qgraphicsitem.cpp:2908 #11 0xb6f1f9e8 in _q_updateIndex (this=0xa1511d0) at graphicsview/qgraphicsscenebsptreeindex.cpp:175
Created attachment 75830 [details] New crash information added by DrKonqi konquest (2.1) on KDE Platform 4.8.5 (4.8.5) using Qt 4.8.1 - What I was doing when the application crashed: creating a new game after finishing the first -- Backtrace (Reduced): #7 MapScene::getSectorSize (this=0xa26d670) at ../../konquest/map/mapscene.cc:192 #8 0x08062188 in PlanetItem::boundingRect (this=0x9b64060) at ../../konquest/map/mapitems.cc:77 #9 0xb6f1b29d in QGraphicsItemPrivate::effectiveBoundingRect (this=0xa5d93a8, topMostEffectItem=0x0) at graphicsview/qgraphicsitem.cpp:2857 #10 0xb6f1b442 in QGraphicsItemPrivate::sceneEffectiveBoundingRect (this=0xa5d93a8) at graphicsview/qgraphicsitem.cpp:2908 #11 0xb6f529e8 in _q_updateIndex (this=0xa1f8710) at graphicsview/qgraphicsscenebsptreeindex.cpp:175
*** Bug 316064 has been marked as a duplicate of this bug. ***
*** Bug 320209 has been marked as a duplicate of this bug. ***
*** Bug 328204 has been marked as a duplicate of this bug. ***
*** Bug 328225 has been marked as a duplicate of this bug. ***
*** Bug 328226 has been marked as a duplicate of this bug. ***