Bug 468258 - PyCharm's code completion window is not usable on Wayland using dual screen setup with mixed scaling and primary on the right + kwin freezes
Summary: PyCharm's code completion window is not usable on Wayland using dual screen s...
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (other bugs)
Version First Reported In: 5.27.3
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: multiscreen, wayland-only
Depends on:
Blocks:
 
Reported: 2023-04-07 18:27 UTC by postix
Modified: 2025-06-28 03:47 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Screen recording (411.12 KB, video/x-matroska)
2023-04-07 18:27 UTC, postix
Details
kWin Support Info (6.95 KB, text/plain)
2023-04-07 18:28 UTC, postix
Details
Screenshot of the 2nd screen (3.18 MB, image/png)
2023-04-07 18:30 UTC, postix
Details
journalctl log (401.61 KB, text/x-log)
2023-04-07 18:31 UTC, postix
Details

Note You need to log in before you can comment on or make changes to this bug.
Description postix 2023-04-07 18:27:44 UTC
Created attachment 157932 [details]
Screen recording

SUMMARY

When entering some code in the IDE, the code completion window pops up. However, while typing this window flashes at random positions with random scaling and size and sometimes appears just as a black rectangle for fraction of a second.

Even worse, it can make the compositor completely freeze for a minute or so, where even keyboard or mouse input stops working. You can notice that the compositor first slows down while typing as there's a certain input lag until it becomes fully unresponsive.

Journalctl had logged the following (1085 times, i.e. 22 events per second):
> 19:19:22 kwin_wayland_wrapper[2179]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
as well as
> 19:19:22 kwin_wayland[2127]: kwin_core: XCB error: 3 (BadWindow), sequence: 52994, resource id: 18926880, major code: 129 (SHAPE), minor code: 3 (Combine)

When it finally had cooled down again, instead of an `else` I had `elllllllllllllllll(....)llllll` with roughly 1400 `l`s in the code input area. 

This seems to be a regression as I definitely could not observe these issues in 5.26 or prior. 


STEPS TO REPRODUCE
1) Dual screen: 2k@100% on the left, 4k@200% on the right + primary
I could not observe it with any other constellations so far. Unfortunately this is the setup I currently got to work with.
2) Please see the attached screen recording.  


SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20230404
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.9-1-default (64-bit)
Graphics Platform: Wayland
Processors: 24 ร— AMD Ryzen 9 5900X 12-Core Processor
Memory: 31.2 GiB of RAM
Graphics Processor: AMD Radeon RX 580 Series

PyCharm 2023.1 (Professional Edition)
Build #PY-231.8109.197, built on March 29, 2023
Runtime version: 17.0.6+10-b829.5 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Comment 1 postix 2023-04-07 18:28:07 UTC
Created attachment 157933 [details]
kWin Support Info
Comment 2 postix 2023-04-07 18:30:40 UTC
Created attachment 157934 [details]
Screenshot of the 2nd screen

This screenshot shows the `code completion window` how it appears at some point in time in the upper left corner of the left 2k@100% non-primary screen. It scales like 0.5.

This bug is also reproducible if `Scaling by the system` is set in kscreen.
Comment 3 postix 2023-04-07 18:31:20 UTC
Created attachment 157935 [details]
journalctl log
Comment 4 postix 2023-04-07 18:32:14 UTC
Last but not least, PyCharm runs under xwayland.
Comment 5 postix 2023-04-22 11:23:40 UTC
@Nate, since you now have a 100%|200% primary setup (bug #468770), would you like to try to reproduce this issue? :)
Comment 6 Vlad Zahorodnii 2025-05-29 10:05:59 UTC
I cannot reproduce the issue. Does it still happen in 6.3 or 6.4 beta?
Comment 7 David Edmundson 2025-05-29 10:45:36 UTC
marking as needs info pending #6
Comment 8 Bug Janitor Service 2025-06-13 03:48:07 UTC
๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Bug Janitor Service 2025-06-28 03:47:49 UTC
๐Ÿ›๐Ÿงน This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.