Bug 339503 - Changing difficulty warns about aborting current game, even when no current game exists
Summary: Changing difficulty warns about aborting current game, even when no current g...
Status: CONFIRMED
Alias: None
Product: bovo
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: Pelladi Gabor
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-29 12:16 UTC by heikki
Modified: 2020-11-23 08:21 UTC (History)
4 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 heikki 2014-09-29 12:16:51 UTC
After playing a game, I like to change the difficulty level one step up or down. Bovo gives me a warning that "Changing the difficulty level will end the current game", even though there is no current game, as indicated by the "GAME OVER. You won!" message on the status line.

Reproducible: Always

Steps to Reproduce:
1. Play a game to the end
2. Change the difficulty by selecting one in the pull-down menu on the status line


Actual Results:  
Alert "Changing the difficulty level will end the current game"

Expected Results:  
Diffculty change for the next game, with no warnings

This started to happen after a recent update on my Debian/Wheezy system
Comment 1 Andrew Crouthamel 2018-11-12 02:44:01 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 2 heikki 2018-11-12 09:26:19 UTC
The issue is still there in version 1.1.

Another way to see it is opening Bovo, and watching it autoplay. Change the difficulty level, and it pops up that warning about aborting the current game, even though there is no current game.

Not that this is a very serious issue, just a minor irritation.
Comment 3 Andrew Crouthamel 2018-11-12 16:24:14 UTC
Thanks for the update!
Comment 4 Justin Zobel 2020-11-23 08:21:41 UTC
Still an issue with 20.08.3