https://bugs.kde.org/show_bug.cgi?id=454086
--- Comment #29 from Andrew Ammerlaan <andrewammerl...@gentoo.org> --- (In reply to Zamundaaa from comment #13) > So (In reply to VesperLlama from comment #10) > > New dmesg-drm-debug.log > now contains messages about commits failing with EINVAL (-22), but still > nothing about the reason for it, or the expected messages about it. > > (In reply to Tony Stipanic from comment #11) > I will try to get useful logs and attach it asap. > Please do! I don't know how much logging NVidia does, but it may yield > useful information either way. > > @Andrew Ammerlaan if you also run the script from comment #3 that might help > as well. > > Some general things you could all try is using the environment variables > (one by one) > KWIN_DRM_USE_MODIFIERS=0 > KWIN_DRM_PREFER_COLOR_DEPTH=24 > KWIN_DRM_NO_AMS=1 I uploaded the logs from the debug script, plus the same logs with the environment variables you suggested. For some reason my computer is acting very 'weird' after running this script and rebooting. It's very slow to start up now, and the system POST is no longer displayed on the screen. -- You are receiving this mail because: You are watching all bug changes.
