Bug 309025 - Crash while putting with advanced putting with keyboard
Summary: Crash while putting with advanced putting with keyboard
Status: RESOLVED WORKSFORME
Alias: None
Product: kolf
Classification: Applications
Component: general (show other bugs)
Version: 1.10
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Stefan Majewsky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-26 04:36 UTC by techsy730
Modified: 2018-11-29 09:42 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description techsy730 2012-10-26 04:36:28 UTC
Application: kolf (1.10)
KDE Platform Version: 4.8.5 (4.8.5)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-32-generic x86_64
Distribution: Ubuntu 12.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I was putting using the keyboard, with advanced putting turned on. I did have the mouse on top of it (which later tests showed can cause it to release the put earlier than I wanted if it was moving a bit, even mouse putting is turned off), and one time I got a crash.

If it helps any, it was the second game of that session (first one was two player, second was one player), and advanced putting was turned on in the first game (the two player one)

- Custom settings of the application:

- Advanced putting on
- Mouse putting off

The crash does not seem to be reproducible.

-- Backtrace:
Application: Kolf (kolf), signal: Floating point exception
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f34208ae780 (LWP 28522))]

Thread 3 (Thread 0x7f340ebcb700 (LWP 28525)):
#0  0x00007f341e16a303 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f341b3ac036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f341b3ac49a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f340ebd098b in ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
#4  0x00007f341b3cd9e5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f341b878e9a in start_thread (arg=0x7f340ebcb700) at pthread_create.c:308
#6  0x00007f341e175cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f340e3ca700 (LWP 28526)):
#0  0x00007f341e16a303 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f341b3ac036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f341b3ac49a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f3413417406 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x00007f341b3cd9e5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f341b878e9a in start_thread (arg=0x7f340e3ca700) at pthread_create.c:308
#6  0x00007f341e175cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f34208ae780 (LWP 28522)):
[KCrash Handler]
#6  0x00007f342045916b in putterTimeout (this=0x2cf0640) at ../../kolf/game.cpp:1208
#7  KolfGame::putterTimeout (this=0x2cf0640) at ../../kolf/game.cpp:1129
#8  0x00007f341e8d0281 in QMetaObject::activate (sender=0x29c00b0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547
#9  0x00007f341e8d5179 in QObject::event (this=0x29c00b0, e=<optimized out>) at kernel/qobject.cpp:1157
#10 0x00007f341f2b5894 in notify_helper (e=0x7ffffa4aa640, receiver=0x29c00b0, this=0x2168ce0) at kernel/qapplication.cpp:4559
#11 QApplicationPrivate::notify_helper (this=0x2168ce0, receiver=0x29c00b0, e=0x7ffffa4aa640) at kernel/qapplication.cpp:4531
#12 0x00007f341f2ba713 in QApplication::notify (this=0x7ffffa4aa940, receiver=0x29c00b0, e=0x7ffffa4aa640) at kernel/qapplication.cpp:4420
#13 0x00007f341ffef3f6 in KApplication::notify (this=0x7ffffa4aa940, receiver=0x29c00b0, event=0x7ffffa4aa640) at ../../kdeui/kernel/kapplication.cpp:311
#14 0x00007f341e8bbe9c in QCoreApplication::notifyInternal (this=0x7ffffa4aa940, receiver=0x29c00b0, event=0x7ffffa4aa640) at kernel/qcoreapplication.cpp:876
#15 0x00007f341e8ed1f2 in sendEvent (event=0x7ffffa4aa640, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#16 QTimerInfoList::activateTimers (this=0x216a560) at kernel/qeventdispatcher_unix.cpp:611
#17 0x00007f341e8eac0d in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:186
#18 timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:180
#19 0x00007f341e8eac31 in idleTimerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:233
#20 0x00007f341b3abd53 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f341b3ac0a0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007f341b3ac164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007f341e8eb3bf in QEventDispatcherGlib::processEvents (this=0x213dbe0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#24 0x00007f341f35dd5e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#25 0x00007f341e8bac82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#26 0x00007f341e8baed7 in QEventLoop::exec (this=0x7ffffa4aa8b0, flags=...) at kernel/qeventloop.cpp:204
#27 0x00007f341e8bff67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#28 0x000000000040279b in main (argc=1, argv=0x7ffffa4aaf38) at ../../kolf/main.cpp:106

Reported using DrKonqi
Comment 1 techsy730 2012-10-26 04:38:03 UTC
Oh, forgot to mention, I was not able to get this crash to occur a second time when I tried to delibratley trigger it.
Comment 2 Andrew Crouthamel 2018-10-29 22:43:26 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2018-11-13 14:40:19 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2018-11-29 09:42:36 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!