Catastrophic failure in KSudoku

[Ian Wadham]

> On 19 Mar 2019, at 6:44 am, Jeremy Whiting <jpwhiting at kde.org> wrote:
> 
> Yep, same thing happens here. Aztec -> Generate A Puzzle shows a dialog box that says "
> Unable to generate a puzzle of the chosen variant; please try another." with a build I just did.
> 
The plot thickens! Albert Astals Cid got every variant to work, see build details at
 https://bugs.kde.org/show_bug.cgi?id=405422#c4

I have provisionally closed the bug with reason WORKSFORME (i.e. works for
Albert --- I cannot build and test KF5 and the latest KDE Games code on Apple).

Jeremy, are you still a KDE developer? If so, can you figure this out, maybe with
help from Albert. I am a little worried that this problem could escape into the next
release of KDE Apps, which is only a month away, but I am confident that Albert has
everything under control as usual.

Regardless of the release, what build-combination is this problem coming from?
Whatever it is needs to be stopped in its tracks before it gets any further.

Cheers,
Ian W.

> BR,
> Jeremy
> 
> On Thu, Mar 14, 2019 at 9:24 PM Ian Wadham <iandw.au at gmail.com> wrote:
> It appears that KSudoku is failing catastrophically. Only the most vanilla puzzle types can be selected
> (i.e.  Classic Sudoku nxn and Roxdoku nxnxn). All others fail to create their data-structures from XML
> files and so fail to generate a puzzle and display it (e.g. XSudoku, Killer Sudoku, Aztec, Samurai
> and many more).
> 
> For more details, please see https://bugs.kde.org/show_bug.cgi?id=405422, especially comment #3.
> 
> This was reported by Duncan, who builds KF5 and apps from live-git and has just noticed the problem
> appearing in the last week or two --- more recently than any changes in the KSudoku source.
> 
> Please can someone who has access to builds and executables of the latest development (HEAD)
> KSudoku code check if they can reproduce this error? You just need to run KSudoku, select Aztec
> puzzle-type (for example) and click on “Generate A Puzzle”.
> 
> Thanks in advance,
> Ian Wadham.
>