| Summary: | Background contrast effect causes panel flickering and composition restarts while browsing through mails in KMail | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Matthias Dahl <ua_bugz_kde> |
| Component: | effects-various | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | kde.org |
| Priority: | NOR | ||
| Version First Reported In: | 5.7.3 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Matthias Dahl
2016-09-02 18:29:37 UTC
Could you please add the output of: qdbus org.kde.KWin /KWin supportInformation and could you also run kwin_x11 from a konsole and watch for Opengl debug output errors when it happens? Unfortunately, kwin_x11 reports nothing except for the system info when it restarts. The one thing that does get logged though (and I just noticed this now) is: kernel: NVRM: Xid (PCI:0000:01:00): 31, Ch 00000020, engmask 00000101, intr 10000000 It is hard to say if this happens immediately before the rest or after. It is at least logged after the rest is noticeable on the screen. It makes no difference btw, if OpenGL 3.1 or 2.0 is used. Except for that, there is only the usual "Desktop effects were restarted due to a graphics reset" and that it was requested. Here the support info: https://paste.kde.org/pdp5kzzws Once the desktop effects restarted, the output is different though: -glPreferBufferSwap: 0 +glPreferBufferSwap: 99 Meaning, VSYNC is off and one has to manually enable it again. Is there anything else I can do? > Except for that, there is only the usual "Desktop effects were restarted due to a graphics reset" and that it was requested.
Oh that's good to know. So there is some GL error which is then sent to us. I fear there is not much we can do. From our perspective we are handling this in the correct way.
> So there is some GL error which is then sent to us.
Wouldn't it be beneficial to track down what is causing that error in the first place? I have seen this both with my old system (Fermi) and my new one (Pascal) across several driver major versions.
Also, it seems like this desktop effect is a common offender and causing trouble, judging from what I was able to read up on it.
Besides all that, I bet there is something terrible wrong here. Going from msg to msg shouldn't flicker the desktop panel, nor should it cause to restart the desktop effects eventually. To me, it seems a bit like there is timing involved somewhere. While I was using the akonadiconsole and did a restart of akonadi, akonakiconsole was obviously "busy"/"sluggish" while I moved the window to another desktop... and the desktop effects were restarted. Again, with the effect naturally on.
I mean, I have no problem turning it off... and I see no advantage of having it on. But others will as well run into this problem -- and it is an annoying bug. And not everyone will have the time and patience to track it down or will report it here. It is, imho, bad press for KDE when in its default configuration, such a bug exists.
Just my two cents, and I absolutely mean no disrespect here. Just trying to draw a wider picture...
Interesting, I found one more way to easily trigger the restart w/ and w/o the contrast effect enabled: Slide the KWin window a bit under the panel and start browsing through the msgs, and the effects will restart over and over again. This also happens if you make the window maximized, I guess due to the shadow effect or whatnot. If you move the window out of the way of the panel, things are fine -- as long as the contrast effect is not active. This issue report is quite old. Can you please confirm, that it still persists 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! |