Can't run on Wayland (NVIDIA)

[raulcraveiro]

Hello! I'm trying to run ZapZap on Fedora Workstation 40, running on Wayland with the new NVIDIA driver 555.

When I try to run the app, I get the following error on terminal:

qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile
QPropertyAnimation: you're trying to animate the non-writable property width of your QObject
js: Error with Permissions-Policy header: Feature xr-spatial-tracking's parameters are ignored.
js: Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'attribution-reporting'.
js: Error with Permissions-Policy header: Unrecognized feature: 'battery'.
js: Error with Permissions-Policy header: Unrecognized feature: 'bluetooth'.
js: Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'compute-pressure'.
js: Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'interest-cohort'.
js: Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'shared-storage'.
js: Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'shared-storage-select-url'.
js: Error with Permissions-Policy header: Unrecognized feature: 'usb-unrestricted'.
The Wayland connection experienced a fatal error: Erro de protocolo

[natanael-b]

Please give a try:

flatpak run --env=QT_QPA_PLATFORM="wayland" com.rtosta.zapzap 

If this works @rafatosta shold consider add --env=QT_QPA_PLATFORM=wayland as finish-args

[rafatosta]

Por um momento nem acreditei que era você 🤣🤣
Curto e acompanho seus conteúdos e do Dio!!

Cara, parece que essa última atualização da nvidia tá quebrando mesmo no Wayland. Minha orientação é usar o X11 através do Flatseal.

Há uma limitação da minha parte por não ter nvidia. Mesmo mantenho os pacotes mais atualizados do Qt, recebo relatos sobre a quebra na NVidia.

Uso o Fedora Workstation e mantenho um Copr para o Zapzap. Os pacotes do Qt atualizam mais rapidamente no Fedora do que no Flatpak, então vale a pena fazer o teste se quiser usar em Wayland ao invés do X11.

Se testar via copr avisa se funcionou, por favor.
Obs: via copr é definido Wayland por padrão e só é possível mudar para x11 nas configurações do Zapzap. Então, se não abrir não há muito o que fazer.

Abraços

[rafatosta]

Please give a try:

flatpak run --env=QT_QPA_PLATFORM="wayland" com.rtosta.zapzap 

If this works @rafatosta shold consider add --env=QT_QPA_PLATFORM=wayland as finish-args

Have you worked around the problem with NVidia?

[kuroki100]

i'm having the same issue, after trying the command given this was the error:

flatpak run --env=QT_QPA_PLATFORM="wayland" com.rtosta.zapzap qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile QPropertyAnimation: you're trying to animate the non-writable property width of your QObject The Wayland connection experienced a fatal error: Protocol error

[Pryka]

Same issue, crash on Wayland.

[githubkuyaya]

I'm on Wayland aswell (Hyprland/arch) and it works without issue here, can't reproduce

[AxeldeWater]

I'm on Wayland aswell (Hyprland/arch) and it works without issue here, can't reproduce

@githubkuyaya you are not using the AUR version by any chance? Flatpak version right?

[githubkuyaya]

I'm on Wayland aswell (Hyprland/arch) and it works without issue here, can't reproduce

@githubkuyaya you are not using the AUR version by any chance? Flatpak version right?

Oh, no I'm using the AUR version. Sorry, didn't realize that this was about the Flatpak version.

[serhumanos]

when I used Wayland with mesa drivers, it works ok.. but now change to x11 and after install nvidia drivers zapzap crashes on start

EDIT: with wayland + nvidia, update flatpak to install flatpak-nvidia-drivers

[CazSaa]

I'm getting the same error with the AUR version on KDE Plasma + Wayland

[DarkGhostHunter]

There are two fixes for this, and both regards running ZapZap under X11 protocol.

If you're using the Flatpak version, you should either disable the Wayland socket (via Flatseal), or explicitly run with the x11 Socket. This way the QT engine automatically uses X11.

flatpak run --socket=x11 com.rtosta.zapzap

The other alternative is to run it with an environment variable. If you have Flatseal then the above should work (and it's more convenient), but you can also set the environment variable there. Either way, the environment value can work as part of the flatpack run command, or the CLI by appending the variable before executing ZapZap.

flatpak run --env=QT_QPA_PLATFORM="xcb" com.rtosta.zapzap

QT_QPA_PLATFORM=xcb zapzap

That is until Wayland woes are fixed, which much depend on NVIDIA side of things for hybrid graphics.

[Krauzer94]

I have both Arch and Debian installed, can confirm that this is more related to the NVIDIA driver version, because it works fine on both GNOME/Plasma and Xorg/Wayland under my Debian installation (Stable branch, driver 535 atm) but it only works on Xorg on GNOME/Plasma on my Arch installation

[taleroangel]

Having the same problem on Flatpak version

[2:2:1107/084552.818181:ERROR:interface_endpoint_client.cc(702)] Message 3 rejected by interface blink.mojom.Widget
The Wayland connection experienced a fatal error: Protocol error

OS: Fedora Linux 41
Kernel: Linux 6.11.5-300.fc41.x86_64
Graphics: Nvidia propietary driver 560.35.03

Fixed by disabling 'socket=wayland' on Flatseal

[rafatosta]

Having the same problem on Flatpak version

[2:2:1107/084552.818181:ERROR:interface_endpoint_client.cc(702)] Message 3 rejected by interface blink.mojom.Widget
The Wayland connection experienced a fatal error: Protocol error

OS: Fedora Linux 41
Kernel: Linux 6.11.5-300.fc41.x86_64
Graphics: Nvidia propietary driver 560.35.03

Fixed by disabling 'socket=wayland' on Flatseal

I'm using it with the 550 drive and it works perfectly. I'll investigate the reason.

[DarkGhostHunter]

This was a bug introduced on 555, so 550 would run fine, I believe.

[rafatosta]

This was a bug introduced on 555, so 550 would run fine, I believe.

Sorry, I made a mistake. I'm using 560.35.03

[rafatosta]

Are you facing the "invisible window" when opening in Wayland?

[DarkGhostHunter]

(To check if you have invisible window desease, open ZapZap via terminal and check if it runs or not).

[rafatosta]

(To check if you have invisible window desease, open ZapZap via terminal and check if it runs or not).

I don't know if this is the best way, but I solved it by adding the following environment variable:
DRI_PRIME=0

[AxeldeWater]

But that's not really solving the problem... That way you are just avoiding it. For the time being that might be sufficient to be able to use it but it's not ideal.

[rafatosta]

(To check if you have invisible window desease, open ZapZap via terminal and check if it runs or not).

I don't know if this is the best way, but I solved it by adding the following environment variable: DRI_PRIME=0

Even with that is not working anymore ...

[DarkGhostHunter]

Anyone running latest NVIDA drivers?

https://www.nvidia.com/en-us/drivers/details/230944/

[rafatosta]

Anyone running latest NVIDA drivers?

https://www.nvidia.com/en-us/drivers/details/230944/

No. I use the ones provided by default in Fedora.

[hideki2k02]

Allegedly the problem is fixed on NVIDIA 565, but from experience those drivers are far too unstable as of now.
EDIT: Here's the "definitive" workaround for now:

• Disabling thewayland Socket with FlatSeal whilst keeping the x11 and fallback-x11 sockets enabled (You can do that globally if its affecting multiple apps)
• Add GSK_RENDERER=gl to /etc/envirnoment also helps on some scenarios (You can also try ngl and vulkan)

[rafatosta]

Allegedly the problem is fixed on NVIDIA 565, but from experience those drivers are far too unstable as of now.
EDIT: Here's the "definitive" workaround for now:

• Disabling thewayland Socket with FlatSeal whilst keeping the x11 and fallback-x11 sockets enabled (You can do that globally if its affecting multiple apps)
• Add GSK_RENDERER=gl to /etc/envirnoment also helps on some scenarios (You can also try ngl and vulkan)

When I use X11, dragging and dropping files doesn't work. Does the same happen to you?

[hideki2k02]

When I use X11, dragging and dropping files doesn't work. Does the same happen to you?

Unfortunately it does. I think XWayland does not handle drag-and-drop properly, considering it was working file on X11.

[Tahinli]

Everything was working yesterday I updated to ZapZap and it's broken for me right now in wayland/hyprland. I'm using Flatpak version on Fedora 41 with 565.57.01 Nvidia Driver . I got this error.

Failed to create wl_display (No such file or directory)
qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vkkhrdisplay, vnc, wayland-egl, wayland, xcb.

I'm able to open ZapZap with "flatpak run --env=QT_QPA_PLATFORM="xcb" com.rtosta.zapzap" thanks to @DarkGhostHunter but I wanted to inform you about situation.

[rafatosta]

Everything was working yesterday I updated to ZapZap and it's broken for me right now in wayland/hyprland. I'm using Flatpak version on Fedora 41 with 565.57.01 Nvidia Driver . I got this error.

Failed to create wl_display (No such file or directory) qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vkkhrdisplay, vnc, wayland-egl, wayland, xcb.

I'm able to open ZapZap with "flatpak run --env=QT_QPA_PLATFORM="xcb" com.rtosta.zapzap" thanks to @DarkGhostHunter but I wanted to inform you about situation.

Restore all settings made by Flatseal and check if the error persists.

I also use the F41 on this same version of the drive and it works well.

[Tahinli]

Restore all settings made by Flatseal and check if the error persists.

I also use the F41 on this same version of the drive and it works well.

I pressed reset button on Flatseal and error persist. I can only run ZapZap with "flatpak run --env=QT_QPA_PLATFORM="xcb" com.rtosta.zapzap"

I can help you debug it, if you guide me.

[rafatosta]

Restore all settings made by Flatseal and check if the error persists.
I also use the F41 on this same version of the drive and it works well.

I pressed reset button on Flatseal and error persist. I can only run ZapZap with "flatpak run --env=QT_QPA_PLATFORM="xcb" com.rtosta.zapzap"

I can help you debug it, if you guide me.

I don't know what else is needed in your case. Here it is working perfectly well and already using "xcb" by default.

[Tahinli]

with xcb it's a bit clunky sometimes ZapZap can't scale well so I need to close and open it again. It doesn't work like before.

[rafatosta]

with xcb it's a bit clunky sometimes ZapZap can't scale well so I need to close and open it again. It doesn't work like before.

Just mark "Wayland" on Flatseal!

[Tahinli]

Just mark "Wayland" on Flatseal!

Thanks!