Bug 322975

please attach output of:
qdbus org.kde.kwin /KWin supportInformation

Created attachment 81445 [details]
kwin information

i think it is the kwin problem because when i disable the animation.
the screen become normal.

You attached your BIOS.

Please attach the output of
   qdbus org.kde.kwin /KWin supportInformation

sorry for the wrong attach.
i update the wrong attach.
please delete it.

Created attachment 81448 [details]
kwin information

does it still happen when you disable the "fall apart" effect?

i think is not.
when i disable it.
the screen will turned to black.
the soulation is also to disable the animation.
and when i logout and login.
the error is gone.

the wrong screen render become two type,  all black or twisted screen.

i will upload a snapshot when the all black is happened again.

(In reply to comment #8)
> i think is not.
> when i disable it.
> the screen will turned to black.
> the soulation is also to disable the animation.
> and when i logout and login.
> the error is gone.

Can you please provide the output of "qdbus org.kde.kwin /KWin supportInformation" when the error is gone (to reflect the changes)
Thanks.

Created attachment 81457 [details]
kwin information with no error.

when my notebook back
i will upload that snapshot and kwin information.
that notebook is the most frequency that happened that problem.
every hibernate wake.
the screen will always black.

That's exactly the same output.
It soes not seem as if you had reconfigured something. (or you re-uploaded the old file ;-)

yeah, i just logout and login.
it return normal.
that why i did not know why it happened.

(In reply to comment #14)
> yeah, i just logout and login.
> it return normal.

;-)
To just clear the display, press "Shift+Alt+F12" twice.

On a clear screen, disable the fall apart effect and try to re-cause the issue.

(In reply to comment #15)
> (In reply to comment #14)
> > yeah, i just logout and login.
> > it return normal.
> 
> ;-)
> To just clear the display, press "Shift+Alt+F12" twice.
> 
> On a clear screen, disable the fall apart effect and try to re-cause the
> issue.


OK, i will try on the notebook.
that computer could test this.
it's hibernate always cause that problem

yes, still existed, even i disable the fall apart
just change the tty8 to tty9 and change back, the screen render is twisted.

this will happened when you never disable animation and re-enable.
if you disable to clear the screen.
this will not happened.
i need to use the kwin --replace& to re-occur this problem.

i will try to find which animation effect occur this problem

this is the another screen render error
http://i.imgur.com/MgB9oKl.png

this is the most frequent happened

i see an error output from kwin 
kwin(6151) KWin::checkGLError: GL error ( update texture ):  "0x506"

Created attachment 81479 [details]
output from my notebook.

according to my notebook test.
when i disable the fall apart.
the error is gone.
but when i enable.
it also has no such error.
so i think it is not that problem.

by the way, i use the opengl 3.1.

(In reply to comment #21)
> but when i enable it also has no such error.
> so i think it is not that problem.

You need a way to reproduce it - if it does never occur on that machine, there's not point in testing on it.

If you know how to reproduce it (hibernation), you'll have to see whether some particular setting causes this.

Eg. you set OpenGL to 2, then you hibernate, resume and see whether the issue still occurs. If yes, you try to disable the fall apart effect, hibernate and see whether the issue still occurs.

The issue will not suddenly appear just because you change some setting.
You will have to redo what initially caused it and see whether it still causes it to know whether the setup change had some impact.

for now, i have tested.
there are two way seems to reduce the happened that screen twist.
1. change the compositing to Xrandr.
2. disable fall apart(possible)

disabling fall apart will reduce the screen twist happened, but could not stop that happened

there are some error output on the terminal
kwin(23686) KWin::checkGLError: GL error ( update texture ):  "GL_INVALID_OPERATION" 
kwin(23686) KWin::checkGLError: GL error ( PostPaint ):  "GL_OUT_OF_MEMORY" 
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::end: Painter not active, aborted

according to my test today.
the fall apart could much reduce the screen twist happened.
but there are still a black screen will happened

simple question: did the scattered look of the first screenshot *ever* re-occur after turning off "fall apart" (and restarting the compositor)?

according to my tested for now.
scattered look seems just occur by fall apart.
after disable it, most of render error is all black.

Ok, but from what i understood so far, that happens exclusively after waking up from hibernation, while the scatter (also) occured after closing a window, correct?

That would be different bugs.

Is the screen locked (you get a login window) when you wake up form hibernation or is there even a screensaver?

wake from hibernate will be none lock screen.

this thing happen when the windows is closing, wake from hibernate or use the ctrl+alt+F1~F12 swtich to a new tty.

according today's closing windows test.
while closing minecraft window, the screen will flash for a short time.
the error is happened in that time.

(In reply to comment #29)
> wake from hibernate will be none lock screen.
> 
> this thing happen when the windows is closing
All windows or just "minecraft"?
Does minecraft run at a different resolution?

(Wake from STR and switch VT sounds like the GPU "just" forgets to repost memory, changing resolution could be bug #322970 resp. bug #322156)

no, it is windowed and not change resolution.
just close that game will cause this problem

for now, run application just minecraft will cause this problem.

and since kde update to 4.10.97.
it did not occur the problem again.
i will tested more for correcting this problem is solve or not.

now closing minecraft seems not cause that problem.
but switch to other tty still occur this problem

Can you try setting "tearing prevention" to "None"?

i will try later.
and without reason, since upgrade to 4.10.97.
this problem is occured not so frequently

tearing prevention is the same option of vsync?

(In reply to comment #37)
> tearing prevention is the same option of vsync?

Yes, "kcmshell4 kwincompositing", 3rd tab, first option in the OpenGL box.

that did not work.
still cause that problem

This might be one or two bugs.

The issues when resuming from startup or switching between VTs imply junked VRAM, this is usually just a driver issue.

This might be related to a bug that seems related to the fall apart effect on closing certain (OpenGL) clients and might be a shader pollution.

Does either issue occur
- with downgraded nvidia drivers?
- with OpenGL shaders DISabled?

I can confirm this. What i see is exactly the same as the reporter's.

But this just happen returning from suspend (sleep) , closing a opengl application doesn't trigger this.

The corrupted screen can be either twisted images or a black screen with a blurred box at the taskbar area.

At this time a re-toggling of compositing always resolves the problem. And suspend to RAM with composition turned off doesn't trigger this too.

I've tried Nvidia driver 319.32, 319.49 and 325.15 with kwin compositing type openGL 1.2, 2.0 and 3.1, also all the tearing prevention methods. The graphic card model is Quadro FX 1800M.

My system is KDE 4.11 on openSUSE 12.3 x64.

Here is my Kwin info: http://paste.kde.org/p09e87287/

I don't use fall apart effect.

*** Bug 324725 has been marked as a duplicate of this bug. ***

*** Bug 324725 has been marked as a duplicate of this bug. ***

FTR:
after a recent update to nvidia 325.15 the kernel hangs after resuming from STR - *regardless* of whether compositing or any OpenGL client was active.

-> That bug is *very* unlikely KWin related and a problem in the nvidia kernel module.

@l12436@yahoo.com.tw
Do you currently have issues when closing OpenGL clients in general or Mincraft in particular?

(In reply to comment #44)
This makes some sense.
With a recently purged profile and no change in default kwinrc , this problem seems disappeared after wake from suspend.
But if one change some settings in kwin module of system settings, this problem would likely to come back again. At least it is true to me.
So it looks like this problem is not directly related to kwin, but it is possbile somewhere in kwin may triggers this.

(In reply to comment #44)
> FTR:
> after a recent update to nvidia 325.15 the kernel hangs after resuming from
> STR - *regardless* of whether compositing or any OpenGL client was active.
> 
> -> That bug is *very* unlikely KWin related and a problem in the nvidia
> kernel module.
> 
> @l12436@yahoo.com.tw
> Do you currently have issues when closing OpenGL clients in general or
> Mincraft in particular?

it always happened.
and whenever i change 319.XX 325.XX 331.XX，it always happened

according to my test,
the fall apart is on of the effect that cause this problem

according to my test,
the fall apart is one of the effect that cause this problem

according to my test,
the fall apart is one of the effect that cause this problem

according to my test,
the fall apart is one of the effect that cause this problem

sorry for dup msg.....

Likely related to bug #344326 and in this case worked-around by http://commits.kde.org/kwin/9f13e9b26035984906896a56d64e85e11522c581 in KWin 5.4.0

I have saw that, the work around in kwin 5.4.0 seems nor work in kwin 4 due to the function did not exist in kwin 4

This bug report is quite old and has been reported to be fixed in 5.4. Can you still reproduce this issue with KDE 5.23?

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!