If I create a new document, it is not visible. The title bar says new document, but the actual window still displays the Start screen.

If I disable canvas acceleration, then a new document is visible.

Is this a known problem? The driver version is 510, which is a lot newer than 470, so Xwayland hardware acceleration is supposed to work, right?

If you 3D acceleration work correctly, there is a very low chance the source of this problem come from the driver.

It seems that krita does not use the wayland Qt module, but anyway wayland should provide a compatility layer with X11 calls.

If you use wayland you could have see this when running krita :

""Krita does not support the Wayland platform. Use XWayland to run Krita on Wayland. Krita will close now.""

I dont know which distro you use but you can try install Xwayland >> apt install xwayland

If this does not work, give us you OS / GPU this can help

Saru wrote:If you 3D acceleration work correctly, there is a very low chance the source of this problem come from the driver.

It seems that krita does not use the wayland Qt module, but anyway wayland should provide a compatility layer with X11 calls.

If you use wayland you could have see this when running krita :

""Krita does not support the Wayland platform. Use XWayland to run Krita on Wayland. Krita will close now.""

I dont know which distro you use but you can try install Xwayland >> apt install xwayland

If this does not work, give us you OS / GPU this can help

So, the problem (new document is invisible) DOES NOT happen on other computers which have Wayland + Nvidia proprietary driver? In my case, I have tested two different Linux distributions, Ubuntu 22.04 daily build and Gnome Manjaro (stable), on the same computer, and the problem occurred on both distributions. I didn't manually install "Xwayland", but it gets installed by default, right? The GPU is RTX 2060 (not "Super").

I have the same problem on Fedora 36, coincidentally also with a regular RTX 2060 (proprietary driver 510.68.02). Is the only workaround running X?

I haven't tried using other drivers, but that wouldn't be the best solution either.