Ubuntu
nvidia-graphics-drivers-375 package

Graphical artifacts after resuming from sleep mode with nvidia drivers

Bug #1668101 reported by Alan AZZERA on 2017-02-26

This bug report is a duplicate of: Bug #1667158: Regression: Borders of windows and desktop background are displayed badly after suspend/resume. Edit Remove

This bug affects 5 people

Affects		Status	Importance	Assigned to	Milestone
	nvidia-graphics-drivers-375 (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Since last nvidia drivers update, I experiment big and very annoying graphical artifacts. I have an Nvidia GeForce GTX 1070, with nvidia-375 (precise version : 375.39-0ubuntu0~gpu16.04.2). My version of Ubuntu is Ubuntu 16.04.2 LTS, completely up to date.

Revision history for this message

Alan AZZERA (azzera-alan) wrote on 2017-02-26:

Capture du 2017-02-26 21-37-18.png Edit (113.7 KiB, image/png)

affects:

kubuntu-meta (Ubuntu) → nvidia-graphics-drivers-375 (Ubuntu)

Revision history for this message

Jean (jeangab37) wrote on 2017-02-27:

I'm experiencing this issue too with an Nvidia Quadro K2100m on ArchLinux with nvidia-378.13-2. Did not have this problem until recently.

More specifically this seems to happen for me only with Chromium windows (did not try other opengl applications).

I know ubuntu can't fix my issue on ArchLinux but knowing that it might not be distro and nvidia 375.39 specific can help I guess. That is if my problem is the same.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2017-03-02:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nvidia-graphics-drivers-375 (Ubuntu):
status:	New → Confirmed

Revision history for this message

SunBear (sunbear-c22) wrote on 2017-03-02:

This bug is the same as https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1667158. I had reported this bug previously but so far the maintainer of this package has not assigned the issue to anyone to follow up. Is there a way to link your report to mine? You can also see some temporary workarounds discussed there.