[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Tsu Jan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

--- Comment #113 from Tsu Jan  ---
Shouldn't the title be changed to "Black or corrupted screen on resume from
suspend with nVidia"? I had this issue with nVidia but never with Intel.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Alonso Murillo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

--- Comment #112 from Alonso Murillo  ---
Hi I am using;
Linux Mint 17.3 KDE 64bits
Kernel 3.13.0-87-generic 
NVidia 340.96 (and have try other versions of it too)
Xorg 11.0

And sometimes when put computer on standby when wakes up every things looks
fine except blinks a lot and it is very annoying, so have log off or kill
xserver in order to stop the blinking.

Regards,
   Alonso Murillo.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[JS Gibson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

--- Comment #111 from JS Gibson  ---
Cool. Makes me look forward to the next nVidia driver.

JSG

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

--- Comment #110 from Thomas Lübking  ---
It's probably the same issue but here affects the GL context in plasmashell
(the desktop process)
Anything you do on kwin (incl. restarting the compositor) has thus no effect.

=> You'll have to restart plasmashell ("pkill plasmashell; sleep 1; plasmashell
&") to get rid of that, though there's suggestion that the most recent™ nvidia
drivers do no longer expose this behavior.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[JS Gibson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

--- Comment #109 from JS Gibson  ---
Comment on attachment 99461
  --> https://bugs.kde.org/attachment.cgi?id=99461
Labels of desktop items in Folder View are replaced with colorful noise.

Replying to this from a email I received re: Bug 344326. I get this as well,
and while he mentioned the missing text on the lock screen, I also sometimes
get missing text on the clock widget on my toolbar. I'll have 7:4 instead of
7:42 or whatever, and I have yet to figure out a way to get it to come back
short of logging out. (Ctrl+Shift+F12, no dice.) I get the scrambled much less
frequently now. Usually only when changing screen modes for a game/whatever
instead of when resuming from sleep/suspend.

JSG

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Chris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

Chris  changed:

   What|Removed |Added

 CC||emailofch...@gmail.com

--- Comment #108 from Chris  ---
Created attachment 99461
  --> https://bugs.kde.org/attachment.cgi?id=99461=edit
Labels of desktop items in Folder View are replaced with colorful noise.

This is one of only two effects I've noticed on my system, labels of desktop
files replaced with noise. This, and text has at least once been missing on the
lock screen after coming back from standby mode.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Ben Cooksley via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

Ben Cooksley  changed:

   What|Removed |Added

 CC|rajind...@hotmail.com   |

--- Comment #107 from Ben Cooksley  ---
Removing person from CC list per abuse reports from Microsoft.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

--- Comment #106 from Thomas Lübking  ---
Once we reliably get aware of it, its time to wipe fbo & vbo - it's what
already happens for vbo's atm, just based on a hack interpreting a GL error
(ie. when it's actually too late)

As long as we don't map the textures, that should be fine. The driver should™
be able to fix the texture ids on its own.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Martin Gräßlin via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

--- Comment #105 from Martin Gräßlin  ---
> Unfortunately it's not even (yet) linked in 
> https://developer.nvidia.com/nvidia-opengl-specs so far (bleeding edge beta 
> feature)

I got contacted by an NVIDIA dev and have a copy of the spec.

So yes, most likely the new extension will help, but I don't know yet how we
can best make use of it. Probably just restarting the compositor should do the
trick (it's overkill, but better safe than sorry).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[deadite66 via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

deadite66  changed:

   What|Removed |Added

 CC||lee295...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Rafael via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

--- Comment #104 from Rafael  ---
Actually, I have not "broken glass effect" (as my screencast showed) but
however I still have "noise" in all windows till I resize them.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

--- Comment #103 from Thomas Lübking  ---
Probably. There're mentions it'd only fire on FBOs, but since those would
likely go alongside.
Unfortunately it's not even (yet) linked in
https://developer.nvidia.com/nvidia-opengl-specs so far (bleeding edge beta
feature)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Nick Guletskii via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

--- Comment #102 from Nick Guletskii  ---
Could the new NV_robustness_video_memory_purge extension be used to detect when
to trigger an update?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[JS Gibson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

JS Gibson  changed:

   What|Removed |Added

 CC||jgibson...@gmail.com

--- Comment #101 from JS Gibson  ---
(In reply to Ruslan Kabatsayev from comment #0)
> Often after I suspend my machine, wait some time and resume back, I see
> sometimes black, other times corrupted screen with blinking triangles of
> distorted windows content. This happens on at least two machines I'm working
> on, both with nvidia video cards (one Quadro (can't tell details yet),
> another GeForce GTX 750 Ti with binary driver 340.46), both machines running
> 64 bit kernel.
> 
> This is a regression, and I've run git-bisect to find that the bad commit is
> commit 1f0bb6d36075b0b14c927b91d5c3df6720826afd
> Author: Fredrik Höglund 
> Date:   Thu Mar 21 23:52:03 2013 +0100
> 
> kwin: Use the new API for rendering quads
> 
> This bug sometimes doesn't reproduce, so I can only be _almost_ sure that
> previous versions don't have it. But I've tested kwin version right before
> this commit, at f709af7c7e23010293c8eb9fa67871adfdb75207, and haven't seen
> any problems for several days, so I think the above bad commit should be the
> right one.
> 
> Reproducible: Sometimes
> 
> Steps to Reproduce:
> 1. Run kwin with OpenGL compositing on an nvidia card with binary driver
> 2. Suspend to RAM
> 3. Wait several minutes (sometimes needs hours, don't know what triggers it)
> 4. Resume
> 
> Actual Results:  
> Screen is garbled with flickering triangles textured with parts of desktop
> content, or sometimes screen is just black
> 
> Expected Results:  
> Desktop should render normally
> 
> Toggling compositing off and on by double pressing Alt+Shift+F12 fixes the
> screen and lets me work normally until next suspend/resume cycle.

The same thing also happens whenever I change resolutions. If I have a game
start up in a lower res, and then change it, it also happens. I was wondering
if you have multiple monitors. I have a laptop set up with an external monitor
that I run with the lid closed. The machine always goes to  the laptop monitor
(1920x1080) when KDE starts (gonna be researching this bug next). After
entering the password (have to do it blind) it will change over to the external
(1920x1200) monitor. I was thinking it was the resolution change as it doesn't
happen when I boot up without the external monitor.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Blucode via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

--- Comment #99 from Blucode  ---
Bad news:
Driver Version 361.28 still has the bug with KWin : 4.11.11.
No more crazy triangles but X hang and STR  or simple system shutdown may hang.
I'll have to upgrade distro for next KWin...

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Blucode via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

--- Comment #98 from Blucode  ---
I've found this talk mentioning a new nvidia driver that no longer has the
suspend-to-RAM broken :
https://devtalk.nvidia.com/default/topic/791786/linux/dpms-not-working-on-gtx980-with-displayport-connection/3
It's mainly about DPMS not working but STR as well in comments page 3.
352.63 (2015.11.16) : bug (I have this one)
358.16 (2015.11.20) : fixed (but no mention in changelog)

I'll add a feedback here if I manage to get this version working for my distro:
This would mean that the workaround can be removed from the KWin code to keep
it clean and tidy.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Blucode via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

--- Comment #94 from Blucode  ---
Created attachment 97061
  --> https://bugs.kde.org/attachment.cgi?id=97061=edit
Disable KDE compositor uppon lock screen (and restore state after)

Using Linux Mint 17.3 KDE Edition, I'm affected by this 1 year old bug on this
brand new distro installation :(
I not sure to be willing to patch and compile the whole KWin myself, next Mint
is 6 months away with the right KWin version I hope...

My main concern was to be locked out by the screensaver with a crazy screen and
not being able to type in the password and get back to the session for a
alt-shift-F12 ...

So I took a few hours to make those python lines in attachment:

It stops compositing uppon screen lock (kde) and put it back as it was uppon
unlock.

(I've just registered here to share this small script)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

--- Comment #97 from Thomas Lübking  ---
As mentioned, there's a workaround in KWin 5.4 and up.
4.x won't see any upstream updates and the patch isn't easy to backport.

The bug is (likely) in the nvidia driver when moving VBOs between system and
video RAM. I have frankly not the least idea how or why that should happen when
locking the screen (except when it's rather "when suspending the screen,
causing a randr event, and the screenlocker is just randomly invoked as well")

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

--- Comment #95 from Thomas Lübking  ---
This bug is about resuming from STR (and nvidia), not about screen locking.
Also it's worked around in 5.4 (though kwin can still crash in the driver)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Blucode via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

Blucode  changed:

   What|Removed |Added

 CC||bluflonal...@gmail.com

--- Comment #96 from Blucode  ---
Thanks for keeping an eye on this bug.

What I have in common about the bug in description and comments 1-93 :
- "I see sometimes black, other times corrupted screen with blinking triangles
of distorted windows content"
- "running 64 bit kernel"
- "nvidia video cards" "GeForce GTX" (mine is 970)
- "kwin with OpenGL compositing on an nvidia card with binary driver"
- "Magic Lamp effect indeed boosts reproducibility of this bug"
- "this is also triggered by screen configuration change" (I do xrandr to dim
screen)
- "workaround disabling and enabling compositing always works"
- "disabling/re-enabling compositing does indeed fix it"
- ...

So I do have this very bug (even if I don't STR - suspend to RAM)

Also: Andrew de Quincey says (32) "My problem previously was that you can't
toggle compositing from the lockscreen"
Me too.

I have Mint 17.3 with
Linux 3.19.0 x86_64, KDE : 4.14.2 , KWin : 4.11.11
NVidia Driver Version: 352.63

(BTW if my comment isn't relevant for some reason I'd be glad to know why and
how I could make a quick fix before getting the next distrib release)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Sean Mackedie via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

Sean Mackedie  changed:

   What|Removed |Added

 CC|colonelpani...@gmail.com|

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Stuart Citrin via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

Stuart Citrin  changed:

   What|Removed |Added

 CC||ctrn...@gmail.com

--- Comment #92 from Stuart Citrin  ---
reference bug 323686, comments 55, 58 etc.

The bug is still reproducible on Linux Mint 17.3 with nvidia 340.96, kwin
4.4.11, linux 3.13.0.24.

On Arch with nvidia 340.96, kwin/plasma 5.5.3, , linux 4.3.3, the bug is no
longer reproducible.  

That is,  on Arch running 5.5 you can:

1. enable effects and  magic lamp. 
2. Minimize and restore a few windows
3. navigate to a tty VT 
4. navigate back to the graphics VT running kde  

and the screen will properly render. 

On Mint running 4.4 you still get the black screen with only the cursor drawn.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

--- Comment #93 from Thomas Lübking  ---
Yes, it's supposed to be work-a-rounded by the patch in comment #53 (applies to
5.4 and up)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Rafael via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

Rafael  changed:

   What|Removed |Added

  Attachment #95851|Some letters are hidden |Some letters are hidden.
description||Below the time "martes, 1
   ||de diciembre de 2015" and
   ||"Desbloquear" in the
   ||button.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Rafael via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

--- Comment #89 from Rafael  ---
Created attachment 95851
  --> https://bugs.kde.org/attachment.cgi?id=95851=edit
Some letters are hidden

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

--- Comment #87 from Thomas Lübking  ---
Suspend To Ram ;-)

Can you interact with the login screen with the bricky text?
(Either the particular greeter GL context - *in* the client - has trouble with
its glyph cache or the greeter isn't shown at all and you see a superimposition
of various paints onto the root window)

I assume your problems are related to the lockscreen greeter. Can you disable
screen locking (across STR) and see whether you still have problems?
(The greeter is written in QtQuick, which is an OpenGL scene and will likely
suffer from the same issues KWin faced before the workaround)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Rafael via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

--- Comment #88 from Rafael  ---
Ok with STR.  I must say that I ONLY have "bricky text" on the screen lock form
window. Just some hours ago I had a similar issue (see the next screenshot) but
this time I even can only enter my password in one of my monitors, exactly the
other one that have not that issue. Apparently, this problem always happen in
my DVI monitor, not in the VGA monitor (if it can help someway). 

But disable screenlock will not do nothing about the "bricked text", cause it
only appears on the screenlock window.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Rafael via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

--- Comment #84 from Rafael  ---
Hi again. 

Thomas Lübking , I don't know what's the meaning of STR. If you ask me if I
suspended my desktop PC on the locked screen, I should say "maybe", cause I
have a delay of 1 hour to sleep my system when afk.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Rafael via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

--- Comment #85 from Rafael  ---
Created attachment 95835
  --> https://bugs.kde.org/attachment.cgi?id=95835=edit
"Doubled view" on one of my two monitors in the lock out screen

I have TWO monitors, and only the default monitor showed the "doubled" text in
the screen lock.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Bas van Schaik via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

Bas van Schaik  changed:

   What|Removed |Added

 CC|b...@tuxes.nl|

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Ruslan Kabatsayev via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

--- Comment #81 from Ruslan Kabatsayev  ---
(In reply to Rafael from comment #79)
> Another atypical issue I saw some time in the unlock screen is "crossed
> text", that's to say, the text  (and only the text) appeared  like if you
> put your eyes "crossed". I have some screenshot of this and will send here.

It might be bug 307003.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Rafael via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344326

--- Comment #82 from Rafael  ---
Thank you Ruslan Kabatsayev , but it's not the same issue.  Mine only had
happened if login after wake up.  The 307003 bug seems to be subpixel rendering
related.
; )

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[anselmolsm]

https://bugs.kde.org/show_bug.cgi?id=344326

Anselmo L. S. Melo (anselmolsm)  changed:

   What|Removed |Added

 CC|anselmo...@gmail.com|

-- 
You are receiving this mail because:
You are watching all bug changes.