https://bugs.kde.org/show_bug.cgi?id=364850
supaiku <supa...@protonmail.ch> changed:
What|Removed |Added
CC||supa...@protonm
https://bugs.kde.org/show_bug.cgi?id=374562
--- Comment #12 from supaiku <supa...@protonmail.ch> ---
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 repe
https://bugs.kde.org/show_bug.cgi?id=371199
supaiku <supa...@protonmail.ch> changed:
What|Removed |Added
CC||supa...@protonm
https://bugs.kde.org/show_bug.cgi?id=374562
--- Comment #10 from supaiku <supa...@protonmail.ch> ---
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 <supa...@protonmail.ch> ---
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
https://bugs.kde.org/show_bug.cgi?id=374562
--- Comment #8 from supaiku <supa...@protonmail.ch> ---
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 ha
https://bugs.kde.org/show_bug.cgi?id=374562
--- Comment #7 from supaiku <supa...@protonmail.ch> ---
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 press
https://bugs.kde.org/show_bug.cgi?id=374562
--- Comment #5 from supaiku <supa...@protonmail.ch> ---
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 a
https://bugs.kde.org/show_bug.cgi?id=374562
--- Comment #1 from supaiku <supa...@protonmail.ch> ---
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
https://bugs.kde.org/show_bug.cgi?id=374562
Bug ID: 374562
Summary: Random crash when moving/transforming a layer
Product: krita
Version: 3.1.1
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity:
https://bugs.kde.org/show_bug.cgi?id=365678
supaiku <supa...@protonmail.ch> changed:
What|Removed |Added
CC||supa...@protonm
https://bugs.kde.org/show_bug.cgi?id=369492
--- Comment #2 from supaiku <supa...@protonmail.ch> ---
Don't know how to edit, but anyway.
Whenever the snap is updated, Krita loads from a new
~/snap/something/.local/share/krita directory.
It's not really user-friendly and quiet annoying t
https://bugs.kde.org/show_bug.cgi?id=369492
supaiku <supa...@protonmail.ch> changed:
What|Removed |Added
Version|unspecified |3.0.1
--- Comment #
https://bugs.kde.org/show_bug.cgi?id=369492
Bug ID: 369492
Summary: Krita config is lost on snap updates
Product: krita
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=369492
supaiku <supa...@protonmail.ch> changed:
What|Removed |Added
Summary|Krita config is lost on |Krita config i
https://bugs.kde.org/show_bug.cgi?id=367685
Bug ID: 367685
Summary: Toggle application launcher on meta key
Product: kwin
Version: git master
Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=364927
Bug ID: 364927
Summary: Add default shortcuts for window resizing
Product: kwin
Version: 5.6.95
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: wishlist
https://bugs.kde.org/show_bug.cgi?id=357110
Bug ID: 357110
Summary: krunner polutes log
Product: krunner
Version: 5.5.1
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
18 matches
Mail list logo
