https://bugs.kde.org/show_bug.cgi?id=414576
Rebecca Breu <rebe...@rbreu.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rebe...@rbreu.de
--- Comment #46 from Rebecca Breu <rebe...@rbreu.de> ---
(In reply to Ahab Greybeard from comment #7)
> I seem to have fixed this for the appimages on my PC.
>
> In kritadisplayrc, I had the line OpenGLRenderer=none
>
> [I must have previously been turning Canvas Graphics Acceleration on and off
> to test another bug I'd been looking at. I assume I'd forgotten that a
> restart is needed to implement this.
> Note that the advisory statement "needs restart" looks like it only applies
> to the Preferred Renderer but it applies to any change in those settings.]
>
> Setting the kritadisplayrc line OpenGLRenderer to be 'auto' or 'desktop'
> clears the problem for me.
>
> Can you go to Settings -> Configure Krita -> Display , make sure Canvas
> Graphics Acceleration is ticked and then press OK then restart krita?
>
> This setting does not cause any zoom-lag problems for version 4.2.6 or
> 4.2.7.1 appimages. It affects 4.2.8 and the Dec09 4.3.0 prealpha appimages.
I just ran into this problem (Debian, appimage) — suddenly zooming was super
laggy on both 4.2.8 and 4.2.9 when it never had been before. Looking in
"Settings -> Configure Krita -> Display", it said the renderer was "Auto
(OpenGL)", but looking at my kritadisplayrc, OpenGLRenderer was set no none.
Editing the file as Ahab said fixed the problem.
I have no idea what caused the issue all of a sudden since I've never touched
the display settings. The only setting that I changed recently was to allow
several instances of Krita, and for the first time ever I was running two
intances of Krita at the same time, and that's when I noticed the issue. So
*maybe* accessing configs concurrently screwed something up, but I haven't been
able to reproduce it so far.
--
You are receiving this mail because:
You are watching all bug changes.
