Crashes when dragging a link in Librewolf (reproducible)

[askiiart]

Please fill out the following:

• Swayfx Version:

  • swayfx version 0.5 (based on sway 1.10.1)

• Debug Log:

  • https://gist.github.com/askiiart/28bd4936853842fb32bf1c185ca94700

• Configuration File:

  • Reproducible with just the default config

• Stack Trace:

  • This is only needed if sway crashes.
  • If you use systemd, you should be able to open the coredump of the most recent crash with gdb with
    coredumpctl gdb sway and then bt full to obtain the stack trace.
  • If the lines mentioning sway or wlroots have ?? for the location, your binaries were built without debug symbols. Please compile both sway and wlroots from source and try to reproduce.

• Description:

  • I opened Librewolf
  • I went to swayfx's GitHub
  • I dragged the "swayfx" repo link
  • swayfx crashed

---

It varies a bit in how soon it crashes after dragging the link, but it crashes fairly consistently (~90% of the time). Also, I'm not sure why, but the log entry in dmesg varies. Sometimes it says something like this:

[16884.690990] i915 0000:0b:00.0: [drm] *ERROR* Atomic update failure on pipe C (start=1243356 end=1243357) time 284 us, min 3058, max 3073, scanline start 3040, end 3083

And sometimes it's a segfault message instead:

[21736.913391] sway[44897]: segfault at 7f1bc3da3418 ip 00007f183da78da0 sp 00007ffdffb478e8 error 4 in libgallium-25.0.0.so[1a78da0,7f183c001000+1ab8000] likely on CPU 6 (core 0, socket 0)

[askiiart]

And it might be helpful to know that

1. This is using swayfx from the copr (https://copr.fedorainfracloud.org/coprs/swayfx/swayfx/)
2. This is on Fedora's 6.11.4-301.fc41.x86_64 kernel.
3. This is with an Intel Arc A750.

I just reinstalled and didn't think to update, I'll update and see if that fixes it.

[askiiart]

Yeah that fixed it :p

[WillPower3309]

Out of curiosity what update fixed it? Looks like you were already using the newest swayfx release - GPU side issue?

[askiiart]

Yeah, just Alchemist being buggy as always, updating the kernel fixed it - I'm on 6.13.5-200.fc41.x86_64 now.