https://bugs.kde.org/show_bug.cgi?id=522735
--- Comment #7 from [email protected] --- (In reply to Zamundaaa from comment #5) > The problem seems to be that KWin can't get a functioning framebuffer: > > GL_INVALID_OPERATION error generated. <image> and <target> are incompatible > > Do you have any environment variables set that are related to KWin? > > Also, does either one of these make a difference? > > KWIN_DRM_DEVICES=/dev/dri/card2 > > KWIN_DISABLE_VULKAN=1 No, I don't have any KWin-related environment variables set. That report and the earlier clean log were on a stock session with nothing overridden, and I double-checked there's no systemd drop-in or anything setting KWIN_* for the compositor. I tried KWIN_DISABLE_VULKAN=1 on its own and it makes no difference. The session still comes up with no signal on the monitor (which is the only display, plugged into the NVIDIA), degrades to a placeholder screen, and the journal has the same GL_INVALID_OPERATION "<image> and <target> are incompatible" plus GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT flood as before, this time about 288 of them across several output reconfigs. I'm attaching that boot's plasma-kwin_wayland log. I also tried KWIN_DRM_DEVICES pointed at the NVIDIA and it made no difference either, same errors and no image. One thing worth flagging: the DRM card numbering isn't stable between boots on this machine, the NVIDIA has come up as both card0 and card2 on different boots, so /dev/dri/card2 isn't reliably the NVIDIA here. To be sure I was pinning the right node I used a udev symlink tied to the NVIDIA's PCI address (0000:01:00.0) instead of a literal cardN, and it still failed the same way -- You are receiving this mail because: You are watching all bug changes.
