SUMMARY After upgrade to 5.18.1 I found that https://bugs.kde.org/show_bug.cgi?id=417444 is probably not fully patched because mouse pointer behaves erratically on areas around right and down corners. This problem makes firefox unusable on plasma wayland. STEPS TO REPRODUCE 1. Start plasma wayland session 2. Start firefox and open many tabs (at least so much, that fills tabbar) 3. Start thunderbird OBSERVED RESULT Try to click some tab with mouse, sometimes it switch tab, sometimes it switch to some other application window and clicks there (thunderbird). EXPECTED RESULT Clicks to firefox should stay here. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.18 KDE Plasma Version: 5.18.1 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 Kernel Version: 5.3.0-40-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-5300U CPU @ 2.30GHz Memory: 7,6 GiB of RAM ADDITIONAL INFORMATION I tested on 5.18.0 also with similar problems.
Hmm, I can't reproduce this bug. Just to be sure, did you reboot your computer after the upgrade?
Yes, reboot was done after upgrade.
What is strange, that in area about 70% of screen from top left corner at least clicks are OK. The resolution is Full-HD 1920x1080 and scaling is 100%.
Could you please post output of `qdbus org.kde.KWin /KWin supportInformation`?
Also when I switch firefox to CSD mode, then I cannot anymore with mouse switch back to no CSD mode, only via keyboard, because buttons at bottom don't work with mouse. Also if I try to open local menu on tabbar it is shown at left at some distance from mouse.
(In reply to Vlad Zahorodnii from comment #4) > Could you please post output of `qdbus org.kde.KWin /KWin > supportInformation`? Should I run it under plasma wayland ? Because of this problem I'm not running plasma wayland session, only when testing.
Created attachment 126188 [details] Output on X11 session
Created attachment 126189 [details] Output on wayland session
Attached both for X11 and wayland session the output of 'qdbus org.kde.KWin /KWin supportInformation'.
I tried to measure where context menu stops, then I got X=~1355px from 1920px (measured with physical ruler). So after X>~1355px mouse stops to behave correctly. Similar situation vertically, for example links on webpages stops work lower then Y>~871px of 1080px.
When I make firefox window smaller (not maximized), then it works OK on left top position, but when I move it to right down position, I cannot press anymore menubar (click goes to another object). There is another problem, that window title bar menu is not closing when I click outside of it.
I tried to lower resolution to 1600x900 and it works OK. But it is not native resolution.
I tried to restore resolution to FullHD/1920x1080 and it started to work OK. Sorry for this stream of comments. I'm trying to find the real/some cause of problems. I'd like sometimes to test with different settings.
Huh, I'm a little bit confused. We have a test that verifies that pointer events carry correct pointer coordinates... and it sort of passes... :| Are you able to reproduce this bug with other Xwayland applications?
I did logout/login test and now plasma wayland session starts in 1600x900, even if I change to FullHD before logout. So somewhere display settings don't stick in file. Of cause it is another problem, but could be related.
We received a similar bug report, but only for X11. It appears like it was caused by some config issue... Could you please verify that the issue is still present with clean home directory? https://bugs.kde.org/show_bug.cgi?id=417899#c5
Similar problem with Thunderbird on wayland session. I just have to push a button, but reaction was on another button.
I just tested on freshly created user and there is the same problems. What is strange if I change resolution to lower and back to normal - no more problems until logoff/logon.
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!
I already provided information about situation. The only last step is to reinstall from scratch to check if something in OS installation is wrong.
Requested information has been provided.
Okay, it seems like I'm able to reproduce this bug too.
but I can't reproduce it reliably.
So it happened to me only once. After that I haven't been able to reproduce the bug again.
Created attachment 132930 [details] A PDF with a little graphic and description of the bug and some affected Applications and not affected It seems that i have the same Bug, so i want to provide some Information how i get this Bug. I made already a File with Informations (saved as pdf with a little graphic). i have listet some Application which have the buggy behaviour an some that havn't in the pdf. Firefox, Thunderbird, Pidgin has the buggy behaviour and Dolphin and "radeon profile" for example are not affected. Basically as soon as i scale my Monitor down (native 3840x2160) to like 1080p and then back to scale factor 1 or 100% Then the Buggy behaviour occours. On a reboot the behaviour is gone again.
Created attachment 132931 [details] The Support Information of my System with the Wayland Session The Support Information of my System with the Wayland Session
One more Info. I am running Manjaro Linux, and i used the Firefox version out of the Repositorys. (I don't know how to see if it is native or not) I think it was a Version, that did not have enabled Wayland Support (as a native Wayland client), So i installed the fedora-firefox-wayland-bin package from the AUR. The firefox version which is patched to be a native Wayland client has not the problem. I could use all Functions and use all links and it show the correct behavior all over the whole Screen. While at the same time The standard repo Version of Thunderbird has the Issue. (I guess it is a not native wayland client - through xwayland) Maybe it is importand that for me it seems to be every time the same region which behaves false. it is always the top left quarter of the 4k screen which is good, the rest quarters are "bad". that screen that i every now and then change the scaling. but it does not matter if i scale it down to 1080p and back or down to 1440p and back to native (100%) - The affectet region stays the same while it is at 100%scale. - while i have it scales to 1440p there ist no "bad regeion" - while i have it scales to 1080p there ist no "bad regeion" There is another indication what might get wrong: - if i use the scale factor 1.01 (kscreen-doctor output.2.mode.0 output.2.scale.1.01) basically only 1% more pixels rendered and scaled to native Resolution then there is no "bad" regeion - if i use the scale factor 0.99 i again get the buggy region on the screen. but also with some luck? sometimes the bug disappersa. lets sy i change the scaling factor from 1.01 to 0.99 the bad region disappers in 0.99 factor. But i can trigger it immediately by scaling to factor 1.5 and back to 0.99 - then i have it again at 0.99 : it seems to be that only scaling factor's of 1 and lower (0.99↓) are affected? but to trigger it i need to scale somewhere above the factor 1.0 like 1.5 once and back to 1 or lower I used thunderbird to look for the bug by searching of the animation for links (the links schould get lines under them) just as indicator.
Created attachment 133028 [details] kscreen-doctor One more thing. to get rid of the bug now i once scale to 1.01 factor, then 1.02. then back to 1 for then the bug is gone. Maybe my Monitor Setup is a needed info for replicating the bug? left side 2560*1080@200Hz (i normaly do not scale that Monitor) right side 3840x2160@60Hz
Created attachment 133084 [details] New Kwin/Systeminformation I got Today Updates for the whole System, kde, Kernel and more at once. i have now Version ======= KWin version: 5.20.2 Qt Version: 5.15.1 Qt compile version: 5.15.1 XCB compile version: 1.14 So for me i couldn't reproduce the Bug after the updates. Thankyou :-)
Can you check whether the issue is still reproducible in 5.26?
Hi, i am currently running KDE Plasma Version: " kwin_wayland --v kwin 5.26.4 " And i followed my own instructions to trigger the Bug, i could NOT trigger The Bug. scaling is doing fine with the command Line Tool now and also the Display configuration menu of Plasma. TLDR: For me now everything is fine. Thankyou