https://bugs.kde.org/show_bug.cgi?id=518732
Zamundaaa <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WAITINGFORINFO CC| |[email protected] Status|CONFIRMED |NEEDSINFO --- Comment #9 from Zamundaaa <[email protected]> --- > With sessions unfrozen, KWin attempts to reacquire DRM master before the DRM > subsystem is fully reinitialized That's nonsense, KWin neither acquires or un-acquires drm master (logind does that), nor does the drm subsystem get "reinitialized" after suspend. Please don't dump LLM output into our bugtracker, it's less than useless. There's two actual problems here: - the fallback for output configurations failing to be applied is rather limited. It prevents KWin from crashing, but it can lose output settings when this happens - suspend on Nvidia is weird. Instead of handling suspend in the kernel (like every other driver), it switches to a different VT before suspend, and back to the original one after wakeup. Systemd however notifies KWin of those events, and outputs are only updated after it switched back, but maybe something's broken in your driver setup that prevents this Please follow https://invent.kde.org/plasma/kwin/-/wikis/Debugging/Debugging-DRM-issues to get a drm debug log of a suspend + wakeup where the problem happens. -- You are receiving this mail because: You are watching all bug changes.
