Bug 321964 - KBreakOut traps mouse cursor
Summary: KBreakOut traps mouse cursor
Status: RESOLVED WORKSFORME
Alias: None
Product: kbreakout
Classification: Applications
Component: general (show other bugs)
Version: 1.1.0
Platform: Mint (Ubuntu based) Linux
: NOR grave
Target Milestone: ---
Assignee: Viranch Mehta
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-04 19:04 UTC by Alpheus
Modified: 2022-12-29 05:24 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alpheus 2013-07-04 19:04:35 UTC
There are two issues:

First, when playing the game, it isn't clear how you could get the mouse cursor.  I had to push several keys (starting with "P") to find out that I had to push "Esc" to pause the game.

Second, if the cursor somehow escapes the game, it traps the cursor between two invisible barriers, making it impossible to get to a left-hand side panel (my preference for panel location).  This is especially frustrating if you don't have any idea that the program is running!  And it's especially frustrating if you restart your computer, hoping that the problem will go away, but have it remain.  I was on the verge of re-installing my operating system....

I apologize for not replicating the bug.  I wasn't playing the game:  my daughter was.  I was fortunate that I was barely able to find the issue using Alt-Tab.

Reproducible: Always

Steps to Reproduce:
1.  I'm not sure, exactly.
2.
3.
Actual Results:  
Mouse cursor mysteriously trapped between two invisible vertical barriers that happen to correspond to where the "bouncing tray" can move, if you're lucky enough to find the game...

Expected Results:  
The mouse cursor should only disappear when the game is on-focus; if the came isn't in focus, the cursor should have free range of movement.  Also, it should be clear (perhaps a "note of explanation" somewhere on the screen is in order!  :-) to let players know how to restore cursor movement. 

I chose "Grave" as the severity option, because while there's a relatively easy workaround (find the program, use "Ctrl-Alt-Esc" to kill it--or just use "Esc" to pause it), if you aren't aware of what is happening, and the program re-loads even after a restart (which probably isn't a good behavior for a game!) someone can easily conclude that the only way to fix things is to re-install the entire operating system.

Of course, as much as I HATE restarting my computer, if the game were to be fixed so that it wouldn't re-start after logging out or after re-starting the computer, then that might be acceptable as well.
Comment 1 Thierry 2018-08-03 11:22:02 UTC
 The mouse cursor would be to repair.
The cairo-dock interferes with the mouse cursor. 
if the status bar is at the top, the  mouse cursor go out the game. 
It's really disturbing
Comment 2 Justin Zobel 2022-11-29 05:06:19 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 3 Bug Janitor Service 2022-12-14 05:12:34 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 2022-12-29 05:24:20 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!