https://bugs.kde.org/show_bug.cgi?id=405422

            Bug ID: 405422
           Summary: ksudoku live-git (commit 09814312d) small-game
                    generation fails with "Unable to generate a puzzle of
                    the chosen variant"
           Product: ksudoku
           Version: unspecified
          Platform: Gentoo Packages
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: iandw...@gmail.com
          Reporter: 1i5t5.dun...@cox.net
                CC: kde-games-b...@kde.org
  Target Milestone: ---

This just started happening a few days ago.  I like a quick 6x6 game so that's
my normal default, but games smaller than standard 9x9 seem to fail with
"Unable to generate a puzzle of the chosen variant", now.

However, given that ksudoku has had only a single GIT_SILENT commit since Jan
11, and it worked well after Jan 11, I suspect the trigger to be an update of
some dependency.

So what might trigger the above error on particularly smaller games?

(Note that I'm running live-git of nearly everything kde related, including all
frameworks and plasma packages, so if it's a kde-related dep it's likely
live-git, while other deps are reasonably recent, being gentoo/~amd64, aka
testing.  For toolchain, glibc-2.28-r5 updated on Mar 10, I /think/ after the
problem already appeared, and gcc-3.3.0 updated on Feb 24, I believe before the
problem altho I wouldn't have rebuilt kde packages until they had a commit, and
qt-5.12.1 on Feb 14 as parts of live-git plasma require qt-5.12 now...)

Also, out-of-routine I recently tried a big 25x25 which took me a couple of
days  to solve (BTW, the timer apparently wrapped at some point as it said only
a few hours, but that'd be a different bug I've not actually filed yet, is it
known or should I file a bug on it).  AFAIK the 6x6 games were working before
that, and broken very soon after, but I tried deleting (well, renaming) the
ksudokurc file and it didn't solve the problem, so if it's corrupted state it
must be elsewhere.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to