https://bugs.kde.org/show_bug.cgi?id=448866
--- Comment #18 from fanzhuyi...@gmail.com --- (In reply to Dick Tracey from comment #17) > (In reply to fanzhuyifan from comment #16) > > Does anyone still experience this issue after configuring nvidia to preserve > > video memory after suspend? > > (https://wiki.archlinux.org/title/NVIDIA/Tips_and_tricks) I also had similar > > problems, which disappeared after enabling this. > > > > If not, should this be closed as RESOLVED-DOWNSTREAM (since we are expecting > > distributions to have the correct configurations)? > > Why does this mean there is no issue with kwin? I am not saying that there is no issue with kwin. I honestly don't know. That's why I am asking a question -- if this doesn't happen when nvidia is configured to preserve video memory after suspend, what would be the correct way to proceed? Does this means that distributions should always enable this option? Or should kwin handle this somehow? If so, how should kwin handle this? I don't know what the answer is. Someone more knowledgeable about these matters should comment. > And why do you call an experimental workaround "the correct configuration"? True, this feature is documented as experimental in the official nvidia documentation[1]. But it seems to be the only way provided by nvidia to save and restore all video memory allocations. Again, I am happy to hear your constructive feedback on this. [1] http://download.nvidia.com/XFree86/Linux-x86_64/545.29.06/README/powermanagement.html -- You are receiving this mail because: You are watching all bug changes.
