I use openSUSE tumbleweed, and I upgrade plasma to 6. When I using Pycharm and Webstorm (all two are jetbrains product and working fine in plasma 5), sometimes when I click on window, then other one respond, but not the top one window. And the top window kinda frozen. I can’t type in it, I can’t even click on it. e.g. opening one pycharm window and one webstorm window, when I click on pycharm one’s, webstorm window respond, but no elevation. the pycharm window don’t respond at all. Don’t know if this is a kwin issue or a jetbrains production QC problem.
1 Like
The issue of clicking into a window and the input being submitted to another window that is behind it, has been reported in this forum a few times already (here’s one and I remember that I’ve seen two more but I can’t locate them right now).
There are few bug tickets about this behavior but I think the best one to track is this: 478556 – With NVIDIA or AMD GPUs on X11, sometimes left or right clicking on IntelliJ IDE windows or a Plasma panel instead interacts with Plasma desktop
Also, its a good idea to check if you have the “slide back” Desktop Effect enabled - it is know to cause problem with the window stacking order (which is this bug).
I’m using wayland and not having “slide back” effect on. So I guess it’s not the same issue maybe?
Edit: After I look at the issue ticket you send to me. The problem is quiet the same, but on wayland and plasma 6. On plasma 5 I don’t have the same issue with X11 nor wayland.
Some folk have also raised this with jetbrains:
https://youtrack.jetbrains.com/issue/JBR-6921
I raised a jetbrains issues about pycharm and clion interfering with each other. It’s been marked as a duplicate of the above bug. I think JBR-621 describes two open projects interfering with each other - so I guess they have a common cause.
I’ve also been seeing this issue on Arch + KDE plasma 6 + Jetbrains 2024.1 (Webstorm, Rider, PyCharm).
Glad to see that my co-workers and I are not alone on this issue
I has the same issues. Intellij Idea 2024.01, when click button， and float a new sub window, and then I can not click the new sub window and can not click the new button in new sub window
Here is my verion detail:
Intellij Idea 2024.01
Operating System: Arch Linux
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.5-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 20 × 12th Gen Intel® Core™ i7-12700H
Memory: 62.5 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: LENOVO
Product Name: 82RF
System Version: Legion Y9000P IAH7H
I faced performance issues after upgrading to Plasma 6.
The issues happen only after I start up the IntlliJ.
I need to wait like half a second for context menu popup (e.g. right click) to appear.
The machine is idle of course. So it’s not like my computer is overtasked.
This is weird. I’d like my desktop environment to be proof against performance dorps caused by simply starting up an application.
1 Like
The stacking order issue (clicking on one window sends the input to another) has reportedly been fixed and will be available in the Plasma 6.0.5 bugfix release that is scheduled to later this week.
The performance issue (reported by @kade1 ) is not something I experienced on a completely idle machine, though running multiple Intellij instances (for example I often have two or three Android projects open in Android studio at once) can quickly make an otherwise idle system not so much idle - a single instance takes about 4GB of resident RAM (not VM size, actual pages in use) without doing anything interesting.
@kade1 - when you have performance issues, I suggest you look in the system monitor, and observe the “load average” graph on the overview page - the load average value should never be above the number of processors you have in your system, so if my system has 8 cores then a value of 8.0 means “the system is fully loaded”. This is a better measure of “system load” than “CPU usage” as it also takes into account I/O operations that are very often a bottleneck for modern applications. If - when you encounter performance issues - your load average is significantly higher than 1.0, then your system is very much not idle and performance degradation is expected.
1 Like
Thank you for your reply. I can certainly tell this is not caused by high load average. If that was the matter I’d simply ask my company to give me a better hardware. 
I am not sure what is the reason but I found a temporal workaround. The issue does not happen when I start IntelliJ with different JDK. I do it with an alias:
alias idea_alt='IDEA_JDK=/usr/lib/jvm/java-22-openjdk ~/APPS/IntelliJ-IDEA-U/bin/idea.sh'
And BTW - the issue is being discussed on JetBrains bugtracer:
youtrack.jetbrains.com/issue/JBR-6830/Poor-performance-with-KDE-Plasma-6-X11
The real question is - should this be fixed on their side? Or maybe the Plasma should be proofed against this issue in general (if it happens with IntelliJ then I assume it might happen with other applications as well).
So, to the question “should Plasma developers make sure that future unexpected bugs do not happen when users run any app”, I would say - yes, for sure, and while they’re doing that they should also make world peace and cure cancer, kthxbye.
All kidding aside, we can only solve problems when we see them, and sometimes you change one thing to make it better and that causes unexpected regressions in other places - and that is no reason not to make changes. Sometimes the problem is that software A relies on incorrect behaviours in software B and when someone fixes B - A stops working, but still B had to be fixed
1 Like
Sure thing. I can agree with all you said. 
Sometimes the problem is that software A relies on incorrect behaviours in software B and when someone fixes B - A stops working, but still B had to be fixed
And sometimes things get even more twisted up. I understand it very well. This is my daily bread.
Anyway, if you’re interested in any more feedback I can give it a test on different machine. But it’s likely going to be somewhere at the end of the week.
I think that the issue might occur while using X11 Server with nVidia proprietary drivers.
Thanks for the offer, but I have no insight into this problem and it doesn’t reproduce for me (using Android Studio).
The only thing I would note is that if the problem can be worked around by changing the JDK Intellij runs on - that is a good indication that the problem is indeed in Intellij (even though it may have been triggered by changes to kwin) and JetBrains developers are the best people to address it.
Sure.
IntelliJ developers will surely take care of this.
Another thing to note is that the whole Desktop Environment got affected by the issues (not just one window or application).
So if this can be reproduced with other applications, we will surely see it in the future. And maybe it will be easier to reproduce. 
So again, thank you for the response. Have a good day.
1 Like