https://bugs.kde.org/show_bug.cgi?id=457951
Bug ID: 457951
Summary: ksudoku commit 6e9d941ce with an existing theme config
results in a blank play-space and qpainter engine
errors
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: ---
On git-master (for frameworks/plasma/gear all three) using the gentoo/kde
project overlay live-git ebuilds. Current ksudoku HEAD 64ec262ee
For a couple months ksudoku would run, but attempting to actually play a game
resulted in a blank play-space, with the number-selector space blank as well.
Running from konsole gave me this pair of errors, twice at the select game
screen (which seemed to work), many many times when starting a game and getting
the blank play-space:
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::end: Painter not active, aborted
I finally had some time to bisect it tonight, with the culprit being (emails
masked):
commit 6e9d941ce
Author: Friedrich W. H. Kossebau <kossebau@>
AuthorDate: Sun Jun 19 19:40:16 2022 +0200
Commit: Friedrich W. H. Kossebau <kossebau@>
CommitDate: Sun Jun 19 19:40:16 2022 +0200
Port away from deprecated KGameTheme & KGameThemeSelector
Given that clue I rebuilt at HEAD, then tried reconfiguring my theme, and sure
enough, ksudoku gave me a proper play-space (and no qpainter errors in konsole)
once again. =:^)
So then I wondered what in the ksudokurc file it had been choking on. A diff
against a backup revealed this in the [Themes] section:
Old:
theme=themes/default.desktop
New:
theme=/usr/share/ksudoku/themes/default.desktop
So the code in the above commit does absolute paths while the old code
apparently saved the path relative to the system theme location, and the new
code doesn't know how to interpret that, resulting in a null theme, in turn
resulting in the null/0 qpainter engine error above.
--
You are receiving this mail because:
You are watching all bug changes.
