feComposite and feGaussianBlur filter effect incompatibility

Bug #300182 reported by Quartz
This bug report is a duplicate of:  Bug #186281: crash with filter effect + blur. Edit Remove
4
Affects Status Importance Assigned to Milestone
Inkscape
New
Undecided
Unassigned

Bug Description

Steps to reproduce:

 1. Create new Inkscape document.
 2. Use the Layers window to create a new filter effect by setting the default layer's blend mode.
 3. Delete the layer.
 4. Open the Filter Editing window and add a new feComposite filter effect to the filter created in step #2.
 5. Delete the feBlend filter effect in the filter.
 6. Set in2 to "BackgroundImage" on the feComposite filter effect.
 7. Set k2 to "1.00" and k3 to "1.00".
 8. Note the filter name - something like "filter3153".
 9. Create a solid, opaque black rectangle for a background, and create some objects over it (not black).
10. Open the XML editor.
11. Select the non-black object you created in step #9 and append the filter effect noted in step #8 to the end of the style attribute. (Something like "filter:url(#filter3153)", separated from the previous thing with a ';' semicolon.)
12. Open the Style window and try to add gaussian blur.
13. Inkscape will instantly encounter a fatal error when you touch the Blur slider.

Attached is info from Fedora 9's "Bug Buddy". If this is not helpful, I can provide a backtrace.

Revision history for this message
Quartz (quartz) wrote :
Revision history for this message
Niko Kiirala (kiirala) wrote :

Is this per chance with 0.46 release version?

This seems like a bug that's already fixed, which can be triggered with three steps:
* create an object
* assign any filter to that object, except single Gaussian blur
* use the blur slider on that object

Revision history for this message
Quartz (quartz) wrote :

Ah. Yes, 0.46. :-P Sorry about that! Thanks a lot!

I think I shall continue to wait contentedly for newer releases to come
floating down from the sky as RPM updates.

In the meantime, do I need to look through release notes before I report
any more bugs in v0.46?

(And just in case any of the developers are getting a duplicate of this, I bet it was because I experimentally sent an email to the reply-to address on the notification email I got - <email address hidden>. Sorry about that. ;) I'm still trying to learn the ropes here in user-level bug reporting.)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.