| Summary: | Excessive amount of _NET_DESKTOP_GEOMETRY PropertyChange slow down the entire Xorg | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Maxim <maxim.kartashev> |
| Component: | platform-x11-standalone | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | atrujillo92work, benji.weber, bizyaev, debroechi, dener.kup, hp1656173638, kde, kde, kde, sam, tobias |
| Priority: | NOR | ||
| Version First Reported In: | git-stable-Plasma/6.1 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | A C program that illustrates the bug | ||
|
Description
Maxim
2024-06-26 12:43:23 UTC
I've built the attached C program but I cannot reproduce the issue when dragging a file from Dolphin or nautilus This test program does produce the problem on my original system, a KDE Neon 5 install that underwent updates and received the Plasma 6 (and of course KDE Neon 6) release. I switched to using Kubuntu for some time to avoid it as I assumed it was an issue with Plasma 6. However, downloading and installing the latest release of KDE Neon today on the same hardware does not produce the bug. Could it be possibly related to the upgrade process? Hi there. I'm using IntelliJ Ultimate for my daily business on Manjaro. After updating Plasma 5 to version 6, IntelliJ became unusable in my multi display setup. Unplugging all external displays solved the issue, but that's not an option to me. A couple a days ago I set up a new machine. Since I set up IntelliJ with an OpenJDK instead of the JBR, I did not run into that issue so far. But I read the comment wondering about if it may be an issue of the Plasma update process. On this new machine I started with Plasma 6, so I just gave that idea a try and started IntelliJ without all the workarounds. As a result I got an IDE that was quite usable, but still had issues especially with animations fading in and out the menu bar menus or dialogs. I configured only a couple of Manjaro settings, animation settings have not been changed by me. It's still a recognizable improvement running the IDE with that custom IDE setting (-Dwatch.desktop.geometry=false) and the custom JBR provided in that JetBrains issue linked with this KDE issue. (In reply to Vlad Zahorodnii from comment #1) > I've built the attached C program but I cannot reproduce the issue when > dragging a file from Dolphin or nautilus FYI: I tried this with both Wayland and X11. It's only an issue with X11 on my system. (In reply to Reg from comment #4) > (In reply to Vlad Zahorodnii from comment #1) > > I've built the attached C program but I cannot reproduce the issue when > > dragging a file from Dolphin or nautilus > > FYI: I tried this with both Wayland and X11. It's only an issue with X11 on > my system. I've tested it in Plasma X11 session as well. > I've tested it in Plasma X11 session as well.
I don't know if it would make a difference but I have all the fancy wobbly windows and such turned on on my system. I also have multiple screens, 6 in 2x3 grid and one off to the side. Perhaps two or more monitors would make a difference.
I meet the issue and solve the temporarily solve it by using the hack provided by jetbrains. This is still an ongoing bug, and I hope to see a better solution. For some reason kwin is bombarded with XCB_RANDR_NOTIFY_OUTPUT_CHANGE events. No screen changes are made. kwin is spammed with XCB_RANDR_NOTIFY_OUTPUT_CHANGE when opening new windows, but it's flooded with nonsensical RandR events more frequently when the dnd moves. Just to be sure, I've disabled kscreen and kwin_x11 is still bombarded with XCB_RANDR_NOTIFY_OUTPUT_CHANGE events. kwin itself has no code to trigger randr output changes. Restarting kwin_x11 fixes it getting spammed with XCB_RANDR_NOTIFY_OUTPUT_CHANGE events. ... and the events resume coming in after changing the display layout in system settings The XCB_RANDR_NOTIFY_OUTPUT_CHANGE events come directly from Xorg, it doesn't appear like Qt or KWin do something wrong with the events. I suspect that it might be a Xorg bug. *** This bug has been marked as a duplicate of bug 484323 *** |