GPU effects not working with Nvidia GPU in Wayland

What is your operating system?
Arch Linux

What is your Shotcut version (see Help > About Shotcut)?
Shotcut 25.01.25 installed from AUR

Can you repeat the problem? If so, what are the steps?
GPU effects doesn’t work in Wayland with RTX 3060 and latest nvidia-open drivers on Arch. It works in X11. Also tried Nvidia proprietary drivers but no difference.

The log shows the following error:
Shader compile log: 0(77) : error C7614: GLSL ES doesn’t allow use of reserved word sample

Not sure if this is a Shotcut issue, or a Wayland/Nvidia issue, but I thought I’d bring it to your attention. Thanks

Does the official AppImage or portable tar or Flatpak version have the same problem?

Please try the portable or AppImage files provided form the Shotcut Download site and report back

The AppImage doesn’t work either. With the system package I’m able to open Shotcut, but the moment I interact with the timeline it crashes. If I open it again, turn off GPU effects, and restart, then it works fine with the CPU.

However with the AppImage I’m not able to run the program at all. It freezes immediately upon opening and gives graphical artifacts until I close it.

Can you save the entire application log from the AppImage attempt and post it here? We might see some clues in there.

Other than a list of codecs, the only thing that stands out from the log is the following line:
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:79: TypeError: Cannot read property ‘status’ of null

I forgot to mention my DE is Plasma.

Edit: When running the system package it still gives that same line, but like I said the system package is able to open so I don’t think that line is relevant. There’s nothing else in the log.

Here’s the log for when the system package crashes. This is after I try to drag media into the timeline.
log.txt (22.0 KB)

This isn’t helpful for me because we do not build or support the AUR package. You should send that log to your package maintainer.

The best way for us to help you is if you run the Linux Portable package (that we build and support) and then post the application log from it here.
https://sourceforge.net/projects/shotcut/files/v25.01.25/shotcut-linux-x86_64-250125.txz/download

The log from the portable package is the same as the AppImage. All it shows is a list of formats and codecs.

Good to know. Can you share it here? Hopefully someone will see a hint.

Unfortunately, I don’t have a system with AUR and Nvidia to reproduce your setup. Can you post a screenshot to show what the graphical artifacts look like?

Here’s the log and a video showing the artifacts. The shotcut window is blank and artifacts the windows that are under it or above it.
log.txt (4 KB)

Wow! That’s really crazy. And when you disable GPU Effects it works normally?

That log file is not correct. The first line should be:

[Info ] Starting Shotcut version 25.01.25

Are you grabbing the file from here?
~/.local/share/Meltytech/Shotcut/shotcut-log.txt

Also, just to be clear, for “GPU effects”, you are referring to the “Settings → GPU Effects (unstable)” checkbox?

I suppose you can’t uncheck the box if the UI is in that broken state. In order to restore to defaults, you can delete/rename this file:
~/.config/Meltytech/Shotcut.conf
That will turn the GPU effects back off.

Sorry, here’s the correct log file after opening the portable package.
shotcut-log.txt (37.4 KB)
Yes the AUR system package works when I disable GPU Effects “Settings → GPU Effects (unstable)”

Thanks for working with me on this. From the log, I can see that Shotcut thinks everything is good. Otherwise, we would usually see some messages about graphics errors. So that’s a hint. Unfortunately, that doesn’t give us any hints about what is causing the problem.

I’m not sure how much energy you want to put into continued troubleshooting. It would be understandable if you just want to use Shotcut with the experimental GPU mode turned off.

Here are some other ideas to try if you want to keep troubleshooting:

I know we have other users using Shotcut with a 3060. But maybe there is something different about your setup.

No problem, thanks for addressing this. Here are a few things I tried:

  • I tried two older versions of Shotcut, same results
  • I tested a different PC with a fresh installation of Arch. Same result on Nvidia GPU, but AMD GPU works fine.
  • I didn’t install an older Nvidia driver because of dependency issues. I’m sure I could figure it out but didn’t have time today.

If I had to guess I’d say it’s an issue with the Nvidia driver and Wayland.