https://bugs.kde.org/show_bug.cgi?id=521837
Zamundaaa <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REPORTED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #14 from Zamundaaa <[email protected]> --- Alright, there are some interesting parts in there. DRM_IOCTL_SET_MASTER fails with EBUSY, so some other file descriptor already has drm master (in KWin or outside). This part means KWin in some way opened 0xe200, got drm master (auth=1), and dropped it again: > [42799.687225] nouveau 0000:06:00.0: [drm:drm_open_helper] > comm="kwin_wayland", pid=184295, minor=0 > [42799.687384] nouveau 0000:06:00.0: [drm:drm_ioctl] comm="kwin_wayland" > pid=184295, dev=0xe200, auth=1, DRM_IOCTL_AUTH_MAGIC > [42799.687392] nouveau 0000:06:00.0: [drm:drm_authmagic] 0 > [42799.687399] nouveau 0000:06:00.0: [drm:drm_ioctl] comm="kwin_wayland", > pid=184295, ret=-22 > [42799.687405] nouveau 0000:06:00.0: [drm:drm_ioctl] comm="kwin_wayland" > pid=184295, dev=0xe200, auth=1, DRM_IOCTL_SET_CLIENT_CAP > [42799.687411] nouveau 0000:06:00.0: [drm:drm_ioctl] comm="kwin_wayland", > pid=184295, ret=-95 > [42799.687417] nouveau 0000:06:00.0: [drm:drm_ioctl] comm="kwin_wayland" > pid=184295, dev=0xe200, auth=1, DRM_IOCTL_DROP_MASTER I tracked this down to be in Mesa, specifically Vulkan. While it does drop drm master, for some reason the return value is missing from the log... More importantly, there's also > [42799.698938] nouveau 0000:06:00.0: [drm:drm_open_helper] > comm="kwin_wayland", pid=184295, minor=0 > [42799.699030] nouveau 0000:06:00.0: [drm:drm_ioctl] comm="kwin_wayland" > pid=184295, dev=0xe200, auth=1, DRM_IOCTL_AUTH_MAGIC > [42799.699048] nouveau 0000:06:00.0: [drm:drm_authmagic] 0 > [42799.699054] nouveau 0000:06:00.0: [drm:drm_ioctl] comm="kwin_wayland", > pid=184295, ret=-22 which does not drop drm master and almost certainly causes the problem. I couldn't find any code path in Mesa that would do this, but perhaps I'm mistaken. Try adding KWIN_DISABLE_VULKAN=1 in /etc/environment and reboot afterwards. Does that make things work again? If yes, do you have any Nvidia Vulkan drivers still installed that might be interfering? -- You are receiving this mail because: You are watching all bug changes.
