Palapeli crashes if you try to move pieces while they are snapping. When you drop a piece into place there is a animation and both the dropped piece and all fitted pieces moves into place. If you happen to move some of the theese pieces while this animation is playing, palapeli will crash. My guess is that there is a conflict in the piece positioning code, where the animation commands one position and the mouse drag/drop action suggests another position. If this is the case, I suggest either abort the animation when the user clicks and instantly snap the pieces together or let the animation continue but make it's position relative to the mouse position, or (not prefered, but better than crashing) hinder the user from clicking until the animation is complete. Reproducable: Always Steps to reproduce/brute force solving: 1. Move all the pieces into a small area a. mark half of the pieces b. move them onto the other half c. repeat until you have a small enough pile 2. Make them snap and move them directly a. Mark half of the pieces again b. Move the marked pieces onto the other half, there is a good change some of them will fit c. Pick them up again while the snapping animation plays, you have to be quite fast (just pressing the mouse button like crazy while moving the mouse will do the trick) d. Repeat until it crashes, it may take a couple of tries to get the timeing right.
Still here in version 2.0 / KDE 4.14.5. Segmentation fault. I'm sorry for the lack of a stack trace, but it should be easily reproducible,
Thanks for the reminder. I did a major update about a year ago to produce v 2.0 (features to help with large puzzles), but back then I could not see what was causing the sporadic crashes when moving pieces. Since then there has been https://bugs.kde.org/show_bug.cgi?id=336075 which gives an additional way to reproduce a crash. I just need some time to work on it now... :-)
Thank you for the report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
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!
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!