Bug 472450 - kwin_core: XCB error: 152 (BadDamage)
Summary: kwin_core: XCB error: 152 (BadDamage)
Status: RESOLVED NOT A BUG
Alias: None
Product: kwin
Classification: Plasma
Component: core (other bugs)
Version First Reported In: 5.27.6
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: needs_verification
Depends on:
Blocks:
 
Reported: 2023-07-21 02:34 UTC by nekonexus
Modified: 2023-07-25 13:01 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nekonexus 2023-07-21 02:34:24 UTC
SUMMARY
I'm not familiar with the nature of this error but I tried looking into it:
(https://www.phind.com/search?cache=29983abd-db3c-4ebb-bf46-682f4dffd59c)

and it appears the error might be related to a race condition?

I'm under the impression that race conditions are difficult to pin down and that I don't know if this issue will be solved because of it, but I figured it's worth mentioning) since I don't know if the KDE Plasma telemetry setting reports it.

STEPS TO REPRODUCE
1. Boot into KDE Plasma from SDDM
2. Enable "session restore" from last logout in System Settings
3. Open some windows if none are open already
4. Reboot
5. Login via SDDM again
6. Check journalctl

OBSERVED RESULT
This error in journalctl:

kwin_x11[2835]: kwin_core: XCB error: 152 (BadDamage), sequence: 25996, resource id: 16778541, major code: 143 (DAMAGE), minor code: 3 (Subtract)

EXPECTED RESULT
No "kwin_core" x11/XCB errors in journalctl.

SOFTWARE/OS VERSIONS
Linux: Arch Linux - Kernel 6.3.8-273-tkg-pds (https://github.com/frogging-family/linux-tkg)
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10
GPU: NVIDIA GeForce RTX 2080 Ti
GPU Driver Version: 535.86.05


ADDITIONAL INFORMATION
N/A
Comment 1 David Edmundson 2023-07-25 13:01:33 UTC
Thanks, it's a perfectly harmless warning, from a stack below us. Telling us that we couldn't get a response to a query to a window because the client closed, something valid to do and handled fine.

The warnings were turned off in Qt6