| Summary: | Screen corruption with intel hd4000 and Opengl 3.1 [project neon] | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | vebveb |
| Component: | scene-opengl | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | justin.zobel |
| Priority: | NOR | ||
| Version First Reported In: | 4.11.11 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
glitch with Opengl 3.1
output of qdbus org.kde.KWin /KWin supportInformation |
||
> I'm using Opengl 3.1 for compositing with standard Ubuntu 14.04 Unlikely. The driver version most likely doesn't support it and falls back to GL2. You're "lucky" if it doesn't crash, see bug #327310 However. a) Please attach the outputs of "glxinfo" and "qdbus org.kde.KWin /KWin supportInformation" on either system. b) I assume you're referring to the single artifact column in the screenshot? -> Does it clear when you damage the area (move a window around or similar)? -> Does it happen with the oxygen decoration? -> Does it happen with disabled blurring? -> Is it related to some particular action? (Animtated window on-screen mapping, window activation or similar) Created attachment 87577 [details]
output of qdbus org.kde.KWin /KWin supportInformation
Very strangely, I don't manage to reproduce it.
Thus it was triggered with the combination of something else I haven't managed to find.
a) Ok, I attach it here, but it says Opengl 3.3 is fine (on both systems)
b) yes, this one. When moving the window or even selecting a menu of this window or another window, there was artifacts like parts of all the opened windows painted at wrong (but near from the original) locations. moving back to Opengl 2 solved that, and going back to Opengl 3.1 was triggering all that again.
the supportInformation are not from the project5 neon iso - thus are pretty worthless unless you've the very same issues with the system in use when obtaining the informations. I don't have the same hardware to test this. Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I'm setting status to "needsinfo" pending your response, please change back to "resolved" or "reported" when you respond, thanks. 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! |
Created attachment 87564 [details] glitch with Opengl 3.1 I've been testing last project neon iso, and found by enabling GLX/Opengl 3.1, there is a lot of screen corruption issues. There was none with Opengl 2. The corruption is easy to trigger, for example dragging the window to the top of the screen to maximize it triggers them. This on a laptop with an intel hd4000. I'm using Opengl 3.1 for compositing with standard Ubuntu 14.04 and it's working well. It was very difficult to take a screenshot of this, and I managed to catch a very small glitch on the screenshot I include there.