I've never filed a bug report, I'm just a guy trying to learn linux and programming in general. I'm going to describe this as simply as possible. If you right click on the desktop, you get a menu, right? As you move the mouse within this menu, a blue box highlights whatever menu item your cursor is currently hovering over. I'm going to refer to the "blue box" as "current menu selection highlight". The bug is in whatever process controls "current menu selection highlight". The "current menu selection highlight" starts "bleeding" the blue "highlight" over other menu items in a blocky, pixelated, flashing manner. Two additional aspects of this bug, 1) it is not limited to that menu. It also happens on application toolbars, and dropdowns with varying degrees of severity. It does not happen on the main KDE application selection menu. 2) It does not happen at all if I have a video playing in-browser (simply playing something on youtube). Yes. I can right click desktop, etc, and "current menu selection highlight" does not have any graphical abnormalities so long as there is a video playing in a tab in an open browser window, even if that tab is NOT currently the selected (displayed) tab. I thought it was my graphics card. As best I can tell at this point - it is not. My Computer and Platform info Dell T1500, Nvidia 1050 card. HITACHI HDD (WINDOWS 10); PNY SSD (PARROT) Parrot Security OS 3.10 Full; NOT installed, the ISO is on the SSD, along with a "persistence" partition. (For some reason I have not been able to install *linux* to the SSD no matter what linux disto or method of installation I attempt.) The PARROT 3.10 ISO comes with MATE - LIGHTDM. ("current menu selection highlight" works fine in MATE, NO graphical abnormalities, nor any graphics issues in WINDOWS 10 on the HDD.) I then download the PARROT-KDE package. During install I am prompted to choose between LIGHTDM or SDDM. I've tried both with the same problem. *NOTE: Installing the PARROT-KDE package on my Lenovo Thinkpad with a "persistence" partition on the internal HDD (that has WINDOWS 10) results in a perfect PARROT-OS KDE-PLASMA 5 desktop, using LIGHTDM or SDDM. I have also installed (PARROT OS 3.10 FULL / KDE PLASMA 5 thing) on an old 32-bit Velocity Micro desktop using a TOSHIBA HDD (ISO/persistence type install again) that was pulled out of a PS3, and even that works great. If this is some crazy freak of nature that will consume your life to track it down, don't bother, I'll use Mate on the Dell, but if you can fix it fairly easily, or point me in the right direction, go for it.
Thanks for the bug report! This is the kind of issue where attaching a screenshot or a screen recording would really help us out. Would you mind doing that? For a screenshot, open Spectacle, set it to take a screenshot after 5 seconds, and then use that time to open the menu and reproduce the issue. Attach the screenshot here. For a screen recording, I recommend SimpleScreenRecorder, and saving it in the .webm format. You may need to use a low bitrate to keep the resulting file under the 4MB attachment limit. Thanks!
Also, what version of KDE Plasma are you using, and in what distro?
Created attachment 109715 [details] image
Created attachment 109716 [details] image
Looks like graphical corruption, and you've got an NVIDIA GPU. Are you by any chance using the proprietary NVIDIA driver?
Created attachment 109717 [details] attachment-334-0.html No, the last time I tried to download one using apt-get, and getting what I thought was the correct driver, it killed everything, I just had to make a totally new persistence partition. That was before I tried using the parrot-kde package at all. It does seem like it's in the card though, especially with it smoothing out when a video is playing. On Sat, Jan 6, 2018 at 6:44 PM, Nate Graham <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=388630 > > Nate Graham <pointedstick@zoho.com> changed: > > What |Removed |Added > ------------------------------------------------------------ > ---------------- > Component|general |Folder > Assignee|kde@davidedmundson.co.uk |hein@kde.org > > --- Comment #5 from Nate Graham <pointedstick@zoho.com> --- > Looks like graphical corruption, and you've got an NVIDIA GPU. Are you by > any > chance using the proprietary NVIDIA driver? > > -- > You are receiving this mail because: > You reported the bug. >
Yeah, at this point I'll let the Plasma maintainers continue to triage the bug.
Are you still able to reproduce this in Plasma 5.17 or the 5.18 beta?
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!
Can you reproduce this bug if compositing is disabled? (press Shift+Alt+F12 to toggle compositing)
Setting back to WAITINGFORINFO.
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!