https://bugs.kde.org/show_bug.cgi?id=419421
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Ever confirmed|1 |0
Status|RESOLVED |REPORTED
--- Comment #35 from Nate Graham <n...@kde.org> ---
RESOLVED WAITINGFORINFO isn't a status that makes sense; re-opening. :)
It seems like a workaround has been found, which hopefully helps to isolate the
problem itself. It seems like the automatic or multi-threaded render loop
settings are provoking this issue?
--
You are receiving this mail because:
You are watching all bug changes.
