After updating archlinux to the latest version, a core dumped appears

[ystyle]

ystyle$ swaylock  --clock    --indicator     --indicator-radius 100          --indicator-thickness 7         --effect-blur 7x5
--effect-vignette 0.5:0.5       --ring-color bb00cc     --key-hl-color 880033   --line-color 00000000   --inside-color 00000088         --separator-color 00000000   --grace 2       --fade-in 0.2 --grace-no-mouse -i /home/ystyle/Pictures/056e547d70844900f3.jpg
[1]    3161 segmentation fault (core dumped)  swaylock --clock --indicator --indicator-radius 100 --indicator-thickness 7

[ystyle]

ystyle# neofetch
                   -`                    ystyle@Archlinux
                  .o+`                   ----------------
                 `ooo/                   OS: Arch Linux x86_64
                `+oooo:                  Host: XPS 13 7390
               `+oooooo:                 Kernel: 6.5.7-arch1-1
               -+oooooo+:                Uptime: 19 hours, 36 mins
             `/:-:++oooo+:               Packages: 2043 (pacman)
            `/++++/+++++++:              Shell: zsh 5.9
           `/++++++++++++++:             Resolution: 1920x1080
          `/+++ooooooooooooo/`           DE: Hyprland
         ./ooosssso++osssssso+`          WM: sway
        .oossssso-````/ossssss+`         Theme: Breeze [GTK2/3]
       -osssssso.      :ssssssso.        Icons: breeze-dark [GTK2/3]
      :osssssss/        osssso+++.       Terminal: WezTerm
     /ossssssss/        +ssssooo/-       CPU: Intel i7-10710U (12) @ 4.700GHz
   `/ossssso+/:-        -:/+osssso+-     GPU: Intel Comet Lake UHD Graphics
  `+sso+:-`                 `.-/+oso:    Memory: 12669MiB / 15688MiB
 `++:.                           `-/+/
 .`                                 `/

[WorkHardes]

Me too on Fedora 40

[seididieci]

Me too on Fedora 40 as well

[spiralman]

This also started happening to me when I upgraded to Fedora 40 (I was on 38; not sure if it happened in 39 or not).

I was able to narrow the issue down to the --fade-in option; if I remove it, it doesn't crash.

Interestingly, the --screenshot option doesn't cause a crash, so it seems like it's related to the fade effect, not the screen capture. I haven't had a chance to actually look at the core dump or step through the debugger to identify the issue, though.

Anyway, I thought others might find the workaround, of removing --fade-in, helpful.