Created attachment 166321 [details] This is how the wayland session looks like for a new user in first time login SUMMARY *** In my system with dual nvidia GPUs (RTX A2000 and RTX A5000) wayland is unusable. If I removing one of the GPUs then everything works as expected. STEPS TO REPRODUCE 1. Have a system with dual nvidia GPUs 2. 3. OBSERVED RESULT screen is corrupted and flickers as seen on the attached EXPECTED RESULT should work as it works with dual GPUs in X11, or with single GPU in wayland SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-21-generic (64-bit) Graphics Platform: Wayland Processors: 20 × Intel® Xeon® W-2255 CPU @ 3.70GHz Memory: 62.5 GiB of RAM Graphics Processor: NVIDIA RTX A5000/PCIe/SSE2 ADDITIONAL INFORMATION Please let me know if and how I can help. I'm willing to spend some time in fixing this issue but it seems so low level for my so I may need a lot of guidance. Thanks!
That's odd, to say the least. Are there any warnings in KWin's log when this happens? You can access it with > journalctl --user-unit plasma-kwin_wayland --boot 0
Created attachment 166406 [details] journal log see attached the journal logs. I'm not sure what I'm supposed to look for :\
Just in case: Seems like the following line doesn't appear on my yesterday's journal logs (the ones with a single gpu in which wayland was working) kwin_wayland[1368]: qt.dbus.integration: QDBusConnection: couldn't handle call to Teardown, no slot matched The error line below appears in either case kwin_wayland_wrapper[1368]: src/gbm_drv_common.c:130: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 875708754 Hope it helps.
The gbm error is a minor driver bug, but it's unrelated. The dbus one is also unrelated. Judging by the lack of errors in KWin + the image, the problem might be on the app side - maybe the apps are using the wrong GPU. I don't know if anything about that would be logged, but if so, please attach the output of > journalctl --user-unit plasma-plasmashell --boot 0 As some additional things you could check, can you start apps that don't use the GPU at all, like Konsole? Also, if you set the > KWIN_DRM_DEVICES=/dev/dri/card1:/dev/dri/card0 environment variable to force KWin to use the other GPU, does that change anything?
> As some additional things you could check, can you start apps that don't use the GPU at all, like Konsole? Sorry I missed to mention that. If I press Alt+F2 and then type knosole it runs as expected. It just leaves the window traces (like it is shown in the screenshot I attached) if I move it around. With the konsole open I can then run kate and even firefox. It seems like the applications that are corrupted are the ones that are based on qml (or kirigami?) like (the ones I tried) systemsettings, discover, eliza and spectacle. I'll test the other suggestions soon.....
Created attachment 166407 [details] plasmashell journal logs please see attached the plasmashell journal log. setting KWIN_DRM_DEVICES=/dev/dri/card1:/dev/dri/card0 didn't change anything
Created attachment 166408 [details] wayland session Just in case here is a wayland session with konsole and firefox running
Okay, qml apps not working definitely points in the direction of the OpenGL driver. Does a simpler egl app like weston-simple-egl work?
As one more thing, does > KWIN_DRM_DEVICES=/dev/dri/card0:/dev/dri/card1 (card numbers reversed) change anything? It would be weird if the other order would be used as default, but it's not impossible
>does > KWIN_DRM_DEVICES=/dev/dri/card0:/dev/dri/card1 > (card numbers reversed) change anything? Tried that already and it seems like my computer used LSD :) I'll check weston-simple-egl soon...
Created attachment 166452 [details] weston-simple-egl weston-simple-egl doesn't work as well. Similar issue with qml apps (see attached). So I guess it's not really a plasma issue. Right?
Yeah, this is definitely a NVidia driver bug. I think the correct place to report them is in the NVidia forums.
Thank so much for your effort!