On certain settings, Boncy Ball bounces in such high speed and unpredictable patter that it requires superhuman abilities to catch it, put in safe place, hover mouse pointer to wait for plasma configuration to show up and remove it or configure to sane settings. See steps to reproduce below. Reproducible: Always Steps to Reproduce: 1. Put Bouncy Ball to desktop 2. Enable autobouncing. Enhance autobouncing strength to at least half of possible range. Lower gravity settings to 1/4 of possible range or less. 3. Close configuration dialog saving changes. Actual Results: Bouncy ball starts to bounce like mad. It moves so fast, it is virtually impossible to catch it and configure/delete. Expected Results: There should be some way to bring bouncy ball to order no matter how silly it is configured. I think that under certain circumstances, bouncy ball should just stop moving. These circumstances could be: 1. "Unlock widgets" plasma state (some users prefer to have widgets unlocked all the time, so they may report Bouncy Ball not working) 2. "Add widget" panel activated. 3. "Cashew" icon clicked The idea is: if desktop is in configurable state, then user should be able to configure each widget without problems. This could also be solved by KCModule that lists all widgets and gives option to open their configure dialog box, but it seems like too much work right now. There is thread on KDE forums of user who was playing with widgets and managed to configure Bouncy Ball in a way he is not able to reconfigure/remove it: http://forum.kde.org/viewtopic.php?f=67&t=106939
Hello! This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5. Accordingly, we hope you understand why we must close this bug report. If the issue described here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging Thanks for your understanding! Nate Graham