https://bugs.kde.org/show_bug.cgi?id=312135
--- Comment #6 from Jan Ritzerfeld ---
(In reply to NSLW from comment #5)
> I loaded your .kmy and under buys there is -599.99 Euro which equals 7 x 75
> Euro + 1 x 74,99 Euro, so probably this issue was fi
https://bugs.kde.org/show_bug.cgi?id=361688
--- Comment #14 from Jan Ritzerfeld ---
(In reply to Sebastian Kügler from comment #13)
> Please don't just re-open bugreports, it makes my life managing kscreen bugs
> much harder.
Then, please fix the bug or mark it as wontfix! kscreen
https://bugs.kde.org/show_bug.cgi?id=361688
Jan Ritzerfeld changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=361688
--- Comment #12 from Jan Ritzerfeld ---
JFTR, I took a look at the source code from github:
* Since 1aa3eb98b22fbe5e690ca8f3096c6e3b712ac3d8, log.cpp calls
QLoggingCategory::setFilterRules("kscreen.*=true") unless KSCREEN_LOGGING is
set
https://bugs.kde.org/show_bug.cgi?id=361688
--- Comment #11 from Jan Ritzerfeld ---
(In reply to Sebastian Kügler from comment #10)
> [...]
> I can't just remove those messages, since we're actually using them to debug
> problems deep down in the stack, and they need to be
https://bugs.kde.org/show_bug.cgi?id=361688
Jan Ritzerfeld changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
