https://bugs.kde.org/show_bug.cgi?id=454547
Ahab Greybeard <ahab.greybe...@hotmail.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ahab.greybe...@hotmail.co.u
| |k
Status|REPORTED |CONFIRMED
Ever confirmed|0 |1
--- Comment #1 from Ahab Greybeard <ahab.greybe...@hotmail.co.uk> ---
I can Confirm this crash with the 5.0.6 appimage and the Jun 02 5.1.0-prealpha
(git 49171d80dc) appimages.
It seems to be caused by 'internal logic' not taking account of the situation.
The Filter Layer has opacity keyframes on it and the first one is not at
frame-0.
If you select a frame and change the opacity of the layer in the Layers docker
then the opacity keyframe value is changed for that layer, if it has an opacity
keyframe on it.
If it does not have an opacity keyframe on it then the previous opacity
keyframe value is changed.
For this layer, and similarly constructed layers, if you select a frame that is
before the first defined opacity keyframe then there is no previous opacity
keyframe and it crashes.
The same thing happens for a paint layer with opacity keyframes on it (and
probably other types of layers that can have opacity keyframes on them).
--
You are receiving this mail because:
You are watching all bug changes.
