| Summary: | VBox Guest Additions / atomic mode false: Parts of the background are randomly painted on Wayland | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | postix <postix> |
| Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | normal | CC: | postix |
| Priority: | NOR | Keywords: | wayland-only |
| Version First Reported In: | 5.23.90 | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Screenrecording
kwin support information |
||
Created attachment 146191 [details]
kwin support information
I don't see this issue, when I log into the X11 session. Last time I tested the Wayland session was on Jan 31, so I guess - if this is a regression - it should have introduced between this day and today. OpenGL renderer string: llvmpipe (LLVM 12.0.0, 256 bits) OpenGL version string: 4.5 (Core Profile) Mesa 21.0.3 OpenGL platform interface: EGL it appears like you use llvmpipe, it might be a bug in llvmpipe. no kwin change comes to mind that could have introduced this regression. any ideas why kwin uses a software rasterizer? (In reply to Vlad Zahorodnii from comment #4) > any ideas why kwin uses a software rasterizer? I got a little bit further in investigating it: The issue did not come from any update from KWin (that's good!). However, it appeared since I have `correctly` installed the `guest additions`: First I have installed `gcc perl make`, which I had forgotten before, so before I actually had no additional Kernel module built / installed. Then via the VBox GUI I have mounted the guest addtions and ran `sudo /mnt/(...)/VBoxLinuxAddtions.sh` and finally rebooted. Now, before and after I did that, I saved the KWin support information and here's the diff: `diff kwin_supportInformation_without_linux_additions.txt kwin_supportInformation_with_linux_addtions.txt` ``` 63c63 < Atomic Mode Setting on GPU 0: true --- > Atomic Mode Setting on GPU 0: false 154c154 < Geometry: 0,0,1920x1080 --- > Geometry: 0,0,1280x800 156c156 < Refresh Rate: 59996 --- > Refresh Rate: 59987 ``` Apparently `Atomic Mode Setting on GPU 0` has changed due to the Linux guest addition installation, but I don't know how why it did that nor how I could control that and if that's the or a part of the root cause. Anything else I may check? Does this gives you a hint of what may be going wrong and why? 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! > any ideas why kwin uses a software rasterizer?
I think the question was answered in the sense, that it's related rather to AMS.
This bug was reported against an outdated version of KWin. We have made many changes since the. If the issue persists in newer versions can you reopen the bug report updating the version number. |
Created attachment 146190 [details] Screenrecording SUMMARY Since I made today's updates and rebooted, the screen of Plasma's Wayland desktop started to show weird graphical glitches, namely it draws parts of the background at random positions at random times. Please see the screen recording. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon Testing KDE Plasma Version: 5.23.90 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Wayland VirtualBox