Bug 392886

Summary:	Rendering issues after suspend wake
Product:	[I don't know] kde	Reporter:	Rajinder Yadav <devguy.ca>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Rendering bug in application. Desktop will not rerender, ugly vertical lines after sleep.

Description Rajinder Yadav 2018-04-08 18:38:32 UTC

Created attachment 111905 [details]
Rendering bug in application.

I am using Kubuntu 16.04 LTS with the NVidia binary driver v 384.111.

I have visual code insider install which seem to be the only application for now that had rendering issues after I come out of suspend mode.

This is a fresh install KDE linux system.
The bug is reproducible for me.

Step

1. Install vscode insider: https://code.visualstudio.com/insiders/
2. Open KDE driver manager and select "Using NVIDIA binary driver - version 384.111"
3. Reboot system.
4. Open Visual Studio insider app (vscode)
5. Click on vscode, then press CTRL+`  to open the terminal.
6. Put system into suspend.
7. Wake system up, login.
8. Terminal window rendering is messed up, has vertical line that will not go away.

Comment 1 Rajinder Yadav 2018-04-08 19:03:21 UTC

I also test switching the video driver to, "Using X.Org X server -- Nouveau display driver", which was the default after a fresh install on my Linux system.

No my system hangs with a black screen coming out of suspend, all I see is the mouse point that can be moved around.

I never get to the login screen.

Comment 2 Rajinder Yadav 2018-04-08 19:24:59 UTC

I switched back to use the NVidia driver and I also see Dolphin app having rendering issues along the title-bar, all vertical lines.

Comment 3 Rajinder Yadav 2018-04-14 23:32:59 UTC

Created attachment 112031 [details]
Desktop will not rerender, ugly vertical lines after sleep.

Comment 4 Christoph Feck 2018-04-15 03:02:39 UTC


*** This bug has been marked as a duplicate of bug 364766 ***