tryphotino / photino.Blazor

https://tryphotino.io
Apache License 2.0
347 stars 63 forks source link

Does not work on wayland #138

Open M0n7y5 opened 1 month ago

M0n7y5 commented 1 month ago

I tried all samples and i get this error every time:

/home/___/RiderProjects/photino.Blazor/Samples/Photino.Blazor.NativeAOT/bin/Debug/net8.0/Photino.Blazor.NativeAOT
Photino.NET: "Photino".SetTitle(Photino.Blazor App)
Photino.NET: "Photino.Blazor App".SetUseOsDefaultSize(False)
Photino.NET: "Photino.Blazor App".SetUseOsDefaultLocation(False)
Photino.NET: "Photino.Blazor App".SetWidth(1000)
Photino.NET: "Photino.Blazor App".SetHeight(900)
Photino.NET: "Photino.Blazor App".SetLeft(0)
Photino.NET: "Photino.Blazor App".SetTop(100)
Photino.NET: "Photino.Blazor App".SetIconFile(favicon.ico)
Photino.NET: "Photino.Blazor App".SetTitle(Photino Blazor Sample)
Photino.NET: "Photino Blazor Sample".Load(/)
Photino.NET: "Photino Blazor Sample" ** File "/" could not be found.
Photino.NET: "Photino Blazor Sample".Load(app://localhost/)
Gdk-Message: 02:27:30.753: Error 71 (Protocol error) dispatching to Wayland display.

Process finished with exit code 1.
M0n7y5 commented 1 month ago

After some more research it looks like its a nvidia issue: Temp workaround is described here: https://github.com/tauri-apps/tauri/issues/10702

CalvinPVIII commented 1 month ago

Also having the same issue, using KDE/Wayland, and the latest NVIDIA Driver. The workaround I've been using for now has been to launch the app using the command WEBKIT_DISABLE_DMABUF_RENDERER=1 dotnet watch run

Xyncgas commented 1 month ago

git checkout a95415a6e358085c30c64cd8a7167c43714c076e on the repository seems like a quick temporary solution for those needing it

https://github.com/tryphotino/photino.Blazor/commit/a95415a6e358085c30c64cd8a7167c43714c076e

WEBKIT_DISABLE_DMABUF_RENDERER=1 was not working for me

I ranWEBKIT_DISABLE_DMABUF_RENDERER=1 dotnet run on the project which used photino.blazor and I cloned the repository to 404a3ea9a5552a127b47af5b0f6b27f0a203c467 before doing it

philippjbauer commented 1 month ago

Thank you for reporting this. We pinned the issue, but since this is an upstream bug in the Nvidia driver, we can't do anything about it.