https://bugs.kde.org/show_bug.cgi?id=374562
Andrew Crouthamel changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=374562
Andrew Crouthamel changed:
What|Removed |Added
Keywords||triaged
--- Comment #13 from Andrew Croutha
https://bugs.kde.org/show_bug.cgi?id=374562
--- Comment #12 from supaiku ---
Hello Dmitry!
I tried it with your the new AppImage and it has gotten a lot harder to provoke
the crash... I'm not even sure if it's the same crash, but I could still crash
Krita by repeatedly pressing STRG+T and moving
https://bugs.kde.org/show_bug.cgi?id=374562
Dmitry Kazakov changed:
What|Removed |Added
CC||dimul...@gmail.com
--- Comment #11 from Dmitry
https://bugs.kde.org/show_bug.cgi?id=374562
--- Comment #10 from supaiku ---
May be noteworthy, that it (subjectively) only happens when I'm transforming a
Layer inside a Group Layer.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=374562
--- Comment #9 from supaiku ---
Hey,
I located another crash with a different stacktrace and I'm sure that's a
completely different issue, but it's also related to Layer Transform.
Whenever it happened, I was about to apply the transform by hitting en
https://bugs.kde.org/show_bug.cgi?id=374562
--- Comment #8 from supaiku ---
I forgot to add, that I got a lot of prints of:
krita.general: Unexpected tool event has come to continuePrimaryAction while
being mode 0 !
krita.general: Unexpected tool event has come to continuePrimaryAction while
bei
https://bugs.kde.org/show_bug.cgi?id=374562
--- Comment #7 from supaiku ---
I found a reliable way to provoke a crash. Today it happened again on the
client mentioned above, while using the transform tool, BUT this time someone
could tell me exactly what was pressed. He was using the transform to
https://bugs.kde.org/show_bug.cgi?id=374562
--- Comment #6 from Boudewijn Rempt ---
Hm... I'm not making the ppa builds myself. Maybe they aren't even stripped
then? I need to ask Dmitry when he comes back from his vacation.
--
You are receiving this mail because:
You are watching all bug chang
https://bugs.kde.org/show_bug.cgi?id=374562
--- Comment #5 from supaiku ---
Hi Boudewijn Rempt,
I already ditched 16.04 in favor of 16.10 and the lime ppa. It is -
subjectively - much more stable. Though some occasional crashes are still
there.
Same question as z-uo: Where are the debug symbols
https://bugs.kde.org/show_bug.cgi?id=374562
--- Comment #4 from z-uo ---
(In reply to Boudewijn Rempt from comment #3)
> Hi Supaiku,
>
> Could you also check with the appimage? If that also crashes for you, then
> we might have to make a special version with debug symbols for you, since
> these
https://bugs.kde.org/show_bug.cgi?id=374562
Boudewijn Rempt changed:
What|Removed |Added
Status|UNCONFIRMED |NEEDSINFO
Platform|Other
https://bugs.kde.org/show_bug.cgi?id=374562
z-uo changed:
What|Removed |Added
CC||nicolas.boug...@z-uo.com
--- Comment #2 from z-uo ---
I
https://bugs.kde.org/show_bug.cgi?id=374562
--- Comment #1 from supaiku ---
I forgot to mention that the typical workspace has 100+ layers and uses up to
1GB+ memory.
The memory of the workstation is (according to memtest) not faulty. The
graphics card in use is a Radeon R7 using the open source
14 matches
Mail list logo
