Problem with latest Nvidia drivers 375.39 and 378.13 [duplicate]
My system updated the long lived branch Nvidia drivers to 375.39 yesterday. The problem is that now, when the computer goes to sleep, then wakes up, some windows are buggy:
The same happens with terminal windows. I tried the short lived branch latest drivers, the 378.13, it is the same problem. What can I do ?
Update: Now the drivers 375.39 are the official Nvidia drivers available from the Ubuntu repository, yet the bug evoked above is still there.
I have also reported the same issue to Ubuntu nvidia-graphics-drivers-375 package in launchpad. The workaround I found was to click an effect button in CompizConfig Setting Manager --> Effects.
I also described another issue for this driver and a temporary work around here.
For those affected, please help to add your voice to the launchpad bug report.
Update: I have shared a better temporary solution in that bug report that removes the bad window borders every time the computer wakes from suspend mode. See comment 13. Pending NVidia to provide a more permanent fix.
Update2: Pls also see comment 44. This workaround is suitable if you are using Ubuntu 16.04.2 LTS with kernel 4.8.0-xx instead of kernel 4.4.0.xx.
Update3 (8th Apr 2017): The new 381.09 beta driver with the bug fix is now available. Use 381.09 driver instead of 375.39 or 378.13. See comments #54 & #55.
Update4 (1st June 2017): The new 375.66 driver was released on 4th May 2017 with fixes to resolve many of the bugs related to 375.39. I have used it since it was made available by "Graphics Driver" team ppa and I have not encountered any issues, works great with 16.04.2. Use driver 375.66 as it is the latest long-lived branch release, else use driver 381.22(which takes over 381.09).
Not really a perfect fix as it doesn't solve the issue but, to recover after the driver glitches upon waking from sleep you can open a new terminal and just relaunch unity via...
blahblah@Computer:~$unity
Some programs don't always recover nicely (eg: chrome will have to be relaunched), but its a bit faster than restarting or logging out / in.