Bug 366685

Summary: All dots have been eaten but next level does not begin. Stuck
Product: [Applications] kapman Reporter: veralee <doug>
Component: generalAssignee: Thomas Gallinari <tg8187>
Status: RESOLVED WORKSFORME    
Severity: major CC: kde-games-bugs-null
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Mint (Ubuntu based)   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: A screenshot showing the game without any dots... a problem.

Description veralee 2016-08-11 22:53:29 UTC
It's really quite simple.
I've run through the maze and have eaten all of the dots.
The game continues with an empty maze, the ghosts eventually get me and it restarts if I have spare lives, but again, same level, no dots.

Reproducible: Sometimes

Steps to Reproduce:
1. Play game
2. Eat All Dots
3.

Actual Results:  
All dots are gone, no new level

Expected Results:  
New level spawns as soon as last dot is eaten
Comment 1 veralee 2016-08-11 22:55:05 UTC
Version is 1.1.0 which is not one of the options in the pull-down menu here.
Comment 2 veralee 2016-08-11 22:58:55 UTC
Created attachment 100557 [details]
A screenshot showing the game without any dots... a problem.
Comment 3 veralee 2016-09-03 22:50:43 UTC
I'd classify this as a UI bug.  
I later found that the color of the dots and the background are so close in one area of gameplay (lower left) that it is very difficult to determine if dots are present.  

I see from my attachment that the dots are there but I did not see them.
Comment 4 veralee 2016-09-04 00:57:00 UTC
(In reply to veralee from comment #3)
> I'd classify this as a UI bug.  
> I later found that the color of the dots and the background are so close in
> one area of gameplay (lower left) that it is very difficult to determine if
> dots are present.  
> 
> I see from my attachment that the dots are there but I did not see them.

Update:  I recreated the bug... it's not a UI issue.  It really does get stuck with no dots left.
Comment 5 Justin Zobel 2022-10-24 00:46:33 UTC
Thank you for reporting this bug 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 6 Bug Janitor Service 2022-11-08 05:10:23 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 7 Bug Janitor Service 2022-11-23 05:16:49 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!