https://bugs.kde.org/show_bug.cgi?id=512511
Zamundaaa <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] Status|REPORTED |CONFIRMED Ever confirmed|0 |1 --- Comment #3 from Zamundaaa <[email protected]> --- The "permission denied" warnings almost certainly come from the VT switch. This bit is more interesting though: > Nov 22 23:23:32 engine kwin_wayland[1978]: Failed to create framebuffer: > Invalid argument > Nov 22 23:23:32 engine kwin_wayland[1978]: src QRectF(0,0 256x256) -> dst > QRect(1046,1104 256x256) > Nov 22 23 23:23:54 engine kwin_wayland[39355]: atomic commit failed: Device > or resource busy > Nov 22 23:23:46 engine kwin_wayland[39355]: atomic commit failed: Device or > resource busy > Nov 22 23:23:46 engine kwin_wayland[39355]: atomic commit failed: Device or > resource busy and matches something I saw yesterday as well. I can't yet explain though why the kernel would disallow creating the framebuffer object... Or what changes in KWin could be related, drm_buffer.cpp had its last change 6 months ago. I'll try bisecting. -- You are receiving this mail because: You are watching all bug changes.
