<!-- See our full bug reporting guidelines at https://inkscape.org/contribute/report-bugs/ Writing a good bug report will ensure we'll be able to help efficiently. 🙂 --> #### Summary: <!-- Summarize the issue/suggestion concisely: --> The gradient tool produces a 'solid gradient' instead of fading into transparency. Introduced in https://gitlab.com/inkscape/inkscape/-/commit/87dff623b094a526f8cac371fa65a92514131cd7. Switching to a 'Gradient' using the Fill&Stroke dialog also has the same regression. #### Steps to reproduce: <!-- Describe what you did (step-by-step) so we can reproduce: --> - open Inkscape - Create an object with a fill - Add a gradient using the gradient tool #### What happened? Object has a gradient, but it isn't obvious #### What should have happened? Same behaviour as 1.4.2 - gradient fading into transparency. #### Version info <!-- Open 'Help > About' and click on the little bug icon in the bottom right corner that copies the debug information to your clipboard. For command line users, run 'inkscape --debug-info'. For Inkscape 1.0.2 and older, please manually add the Inkscape Version and Operating System Version. The Inkscape version is listed in the About dialog. For command line users, run 'inkscape -V' Paste the information in the empty space between the apostrophes below: --> ``` Inkscape 1.5-dev (b56c385615, 2025-09-26, custom) Compile (Run) GLib version: 2.84.4 GTK version: 4.18.6 (4.18.6) glibmm version: 2.83.1 gtkmm version: 4.18.0 libxml2 version: 2.12.10 libxslt version: 1.1.43 Cairo version: 1.18.2 (1.18.2) Pango version: 1.56.4 (1.56.4) HarfBuzz version: 10.4.0 (10.4.0) Poppler version: 25.02.0 OS version: Fedora Linux 42 (Workstation Edition) ``` <!-- ❤️ Thank you for filling in a new bug report, we appreciate the help! ❤️ Please be patient while we try to find the time to look into your issue. Remember that Inkscape is developed by volunteers in their spare time, we'll try our best to respond to all reports. --> <!-- Please be careful when/after writing # for example in logs, code, or versions of linux - use inline code span - single backticks (`) before and after it, like this - `#1618` - use multi-line code block - triple backticks (```) to fence/enclose console logs - attach long logs as a text file. -->