Created attachment 120707 [details] image of the issue SUMMARY The blue splash of the hot corners are extremly large. They only activate if you go to the corner, but the splash activates in the middle of the screen, as if the resolution was wrong, but it isn't. This happened after installing nvidia drivers. (nvidia-drivers-418) STEPS TO REPRODUCE 1. install nvidia drivers on kubuntu 2. reboot 3. observe OBSERVED RESULT huge blue things on screen corners EXPECTED RESULT small, simple blue splashes that only show when i go into the corner of the screen. this might have been affected by an update, as well, as i was running a stable system a few weeks ago, and after a KDE update, this started happening. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.04, Plasma 5.15.4 (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION no additional info
Please check with the default breeze theme.
I'm relatively new to KDE, skipped the 4.x series completely (and do you blame me?) so I'm not exactly sure where to look here.
By the way, this happened in Kubuntu and openSuSE
(In reply to David Edmundson from comment #1) > Please check with the default breeze theme. I have switched themes around and the problem persists.
Yikes, that's weird. However I'm not clear on when this started happening. You said: > after a KDE update, this started happening And also: > This happened after installing nvidia drivers. (nvidia-drivers-418) Which is it? Also, does it go away if you change your Plasma theme to, say, Oxygen?
(In reply to Nate Graham from comment #5) > Yikes, that's weird. However I'm not clear on when this started happening. > You said: > > after a KDE update, this started happening > > And also: > > This happened after installing nvidia drivers. (nvidia-drivers-418) > > Which is it? Also, does it go away if you change your Plasma theme to, say, > Oxygen? It was hard to tell, because regardless, it kept doing it! But get this: this morning, I booted up my system, no updates at all the past day or two, and on a whim, I turn on the hot corner (expected it to be huge, change gfx driver, see if it persisted) and would you believe it, it's back to being small again!? I'm floored by this one. Basically, after all updates and chages I made, the problem was there. There were ZERO changes between it happening and this morning, but it has magically been fixed. Then I updated my system. I'll come back to this if I come about the issue again. This is stupidly strange.
Alrighty, started up the computer just now and the big splotch is back this morning. What the actual hell is going on?
So now that it's reproducing again, does it go away if you switch to the Oxygen plasma theme?
What desktop theme do you use?
(In reply to Vlad Zagorodniy from comment #9) > What desktop theme do you use? Breeze dark. I've tried other themes and the problem persists regardless of the theme.
(In reply to Nate Graham from comment #8) > So now that it's reproducing again, does it go away if you switch to the > Oxygen plasma theme? I have yet to try Oxygen. I'm running errands and will try when I get home
Could you post your kwinrc?
(In reply to Vlad Zagorodniy from comment #12) > Could you post your kwinrc? As soon as I get home I will do that, but I need to know how to do that please.
Use Dolphin to navigate to `~/.config/` and then attach the file named `kwinrc` to this ticket.
Created attachment 120800 [details] kwinrc file
Just for clarification, I changed back to the open source display driver and the problem was still there, so it's not too do with the Nvidia drivers.
Aaaand switching back to Nvidia driver it's normal again! What is going on here?! Is it only me having this problem? It can't be, not when it's done this on two different operating systems!
Does this bug occur if you switch to XRender render backend?
(In reply to Vlad Zagorodniy from comment #18) > Does this bug occur if you switch to XRender render backend? How can I check that? To be completely fair, KDE settings are so terribly organized, but in all my efforts I can't imagine a better way to do them lol
Open System Settings app and type "xrender" in the search field.
(In reply to Vlad Zagorodniy from comment #20) > Open System Settings app and type "xrender" in the search field. This morning's bootup: the problem is not there. To respond to you, it's set to OpenGL 2.0
Switch to the XRender rendering backnd and check whether you can reproduce this bug.
(In reply to Vlad Zagorodniy from comment #22) > Switch to the XRender rendering backnd and check whether you can reproduce > this bug. Switching to xrender, the corner icon got REALLLLLLY small almost couldn't see it.
I'm currently upgrading to 5.16, hopefully it's fixed already in this. 🤞
Well I've upgraded to 5.16 and the issue persists
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!
God damn bot.
Same issue: Garuda linux. Added more screenshots for verification. System informations: Monitor size: 1920x1080 Operating System: Garuda Linux KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.2-zen1-1-zen (64-bit) Graphics Platform: X11
Created attachment 145842 [details] Sizzling hot corners (Way too big)
Created attachment 145843 [details] From a fresh garuda install: Way too big! (bug)
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.
This one I can confirm is fixed now.