https://bugs.kde.org/show_bug.cgi?id=453280
--- Comment #16 from Stefan Becker <chemob...@gmail.com> --- Created attachment 149318 --> https://bugs.kde.org/attachment.cgi?id=149318&action=edit kscreen: fix XCB connection resource leak After digging through the source code and running kded5 under ltrace $ ltrace -e xcb_connect+xcb_connect_to_display_with_auth_info+xcb_connect_to_fd+xcb_disconne...@libxcb.so.1 kded5 I was able to track down the resource leak. This error is mis-attributed to "kded", the culprit is "kscreen". More specifically the problem was introduced by this git commit: commit 09b988e6628093e7d4c8b92cd8a0a1fe2da2f77e Author: Marco Martin <notm...@gmail.com> Date: Fri Mar 4 09:05:19 2022 +0000 X11: align touchscreen to internal display On Wayland is the compositor itself that keeps the touchscreen coordinates mapped to the size and position of the internal screen, also keeping rotation into account. on X11, needs to be done via XInput, do it when KScreen actually applies a configuration. BUG: 415683 XOpenDisplay() internally calls xcb_connect(), which allocates a new XCB connection. Therefore you need to call XCloseDisplay() again to release the connection. This is what the attached patch does. With it the problem can no longer be reproduced. There may be other or better ways to fix this, e.g. * determine X Display from the XCB connection retrieved from QX11Info * use XCB calls with XCB connection instead of X calls that require X Display but I was unable to determine that based on API documentation. -- You are receiving this mail because: You are watching all bug changes.
