Summary: | crash .kra | ||
---|---|---|---|
Product: | [Applications] krita | Reporter: | Nikolay <nemitko> |
Component: | General | Assignee: | Krita Bugs <krita-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | halla, portnov |
Priority: | NOR | Keywords: | drkonqi |
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/calligra/d9a7301b7e39435749db33455bc960980b231ad6 | Version Fixed In: | |
Sentry Crash Report: | |||
Attachments: |
s2.jpg
s1.jpg New crash information added by DrKonqi |
Description
Nikolay
2015-06-05 10:28:32 UTC
Hi, Can you attach the brush to the bug report? Created attachment 93032 [details] s2.jpg Hi, I do not know how to do it. Right click the mouse and the left led to a drop in the program. Before the latest update everything worked very stable. Link to brush "Cazu": http://www.pcazorla.com/2014/01/15/cazu-brush-collection-v2-for-krita/ Link to brush "David Revoy": http://www.davidrevoy.com/article248/krita-brushes-v6 Built-in brush to not cause damage. Other brushes did not put. Thank you. Screenshots: 2015-06-05 13:30 GMT+03:00 Boudewijn Rempt <boud@valdyas.org>: > https://bugs.kde.org/show_bug.cgi?id=348737 > > Boudewijn Rempt <boud@valdyas.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |boud@valdyas.org > > --- Comment #1 from Boudewijn Rempt <boud@valdyas.org> --- > Hi, > > Can you attach the brush to the bug report? > > -- > You are receiving this mail because: > You reported the bug. > Created attachment 93033 [details]
s1.jpg
Created attachment 93081 [details]
New crash information added by DrKonqi
krita (2.9.5) on KDE Platform 4.14.6 using Qt 4.8.6
- What I was doing when the application crashed:
Just painting with random brushes. Maybe it is important that brushes that I used were loaded from bundle.
-- Backtrace (Reduced):
#6 0x00007f7361693267 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55
#7 0x00007f7361694eca in __GI_abort () at abort.c:89
[...]
#11 0x00007f7346a8df8d in KisDynamicSensor::fromXML (this=this@entry=0x1052c340, e=...) at /build/krita-testing-13Ggmk/krita-testing-2+git20150603+r12/krita/plugins/paintops/libpaintop/kis_dynamic_sensor.cc:392
#12 0x00007f7346abae2b in KisDynamicSensorFade::fromXML (this=0x1052c330, e=...) at /build/krita-testing-13Ggmk/krita-testing-2+git20150603+r12/krita/plugins/paintops/libpaintop/sensors/kis_dynamic_sensor_fade.cpp:93
#13 0x00007f7346a8e373 in KisDynamicSensor::createFromXML (e=...) at /build/krita-testing-13Ggmk/krita-testing-2+git20150603+r12/krita/plugins/paintops/libpaintop/kis_dynamic_sensor.cc:287
It seems I figured out where is the bug, it looks like typo. The crash is because of QASSERT at kis_dynamic_sensor.cc:392: > Q_ASSERT(e.attribute("id", "") == id(sensorType())); The stack points out that sensor being processed is something called "fade" (kis_dynamic_sensor_fade.cpp:93). I assume that somewhere in the brush preset definition XML, I had a description of sensor with id="fade". So let's look at the definition of id() function (kis_dynamic_sensor.cc:337): > QString KisDynamicSensor::id(DynamicSensorType sensorType) > { > ... > case FADE: > return "speed"; > ... > } Stop, what!? :) It seems id() function returns wrong id, and then Q_ASSERTS() says about that. So I suggest to do > sed -i -e '343 s/speed/fade/' kis_dynamic_sensor.cc Git commit d9a7301b7e39435749db33455bc960980b231ad6 by Boudewijn Rempt. Committed on 13/06/2015 at 16:55. Pushed by rempt into branch 'calligra/2.9'. Thanks to Ilya Portnov for looking into this. CCMAIL:portnov@bk.ru M +1 -1 krita/plugins/paintops/libpaintop/kis_dynamic_sensor.cc http://commits.kde.org/calligra/d9a7301b7e39435749db33455bc960980b231ad6 |