Bug 355976

Summary:	Brush stroke signal lost with krita-lod-unstable
Product:	[Applications] krita	Reporter:	Tyson Tan <tysontanx>
Component:	Brush engines	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED FIXED
Severity:	major	CC:	dimula73, halla
Priority:	NOR
Version First Reported In:	2.9.9
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Tyson Tan 2015-11-27 08:23:49 UTC

When using Krita lod-unstable build from Dmitry's PPA, I found that the current build does not update brush strokes as active as krita-testing build. Very oftenly after I applied multiple brush strokes and saw the cursor moved, nothing would appear on the canvas. Continue drawing sometimes could "push through" a few strokes, but the strokes before that were lost and the screen update was slow -- more than 500ms after the last stroke did I see things starting to come up. 

I tested this is on a RGB 8 bit, 12000x7000px 2 layers kra files. Ubuntu Gnome 15.04. krita-lod-unstableK2+git20151117+r12-61~ubuntu15.04.1. Very obvious when using Fill_circle brush preset, Krita simply became unusable after a few strokes like that. I tried turning off OpenGL and autosave. But they did not help at all.

Now I'm using krita-testing 2+git20151117+r41-61~ubuntu15.04.1, the problem never happened.

Reproducible: Always

Comment 1 Halla Rempt 2015-11-27 09:54:22 UTC

Dmitry will take a look on Monday.

Comment 2 Dmitry Kazakov 2015-12-15 10:33:35 UTC

Hi, Tyson!

I still have a trouble with reproducing your bug :( I've seen it a couple of times, but I cannot reproduce it in development environment. I will keep hunting the bug further :(

Comment 3 Halla Rempt 2016-04-13 13:42:49 UTC

I suspect that this is related to https://bugs.kde.org/show_bug.cgi?id=361619, actually.

Comment 4 Halla Rempt 2016-04-16 13:09:20 UTC

See https://phabricator.kde.org/T2077

Comment 5 Dmitry Kazakov 2016-08-15 12:22:54 UTC

Hi, Tyson! I didn't see this bug for ages... is this bug still actual? I have a feeling it has been fixed since then.

Comment 6 Tyson Tan 2016-08-15 14:01:14 UTC

Hi Dmitry, I don't see this bug anymore for a very long time. 9 out of 10 it was a Ubuntu 15.04 specific bug -- it had very old Qt packages. I think you've fixed it in the recent builds. Thank you!