Nulo
Yes, they do conflict, which is probably bad.
It looks to me that kcoreaddons is at the very least [being built with Qt6](https://github.com/KDE/kcoreaddons/search?p=1&q=qt6&type=commits) in their CI.
This happens to me constantly, and also when plugging/unplugging displays.
Don't take Alpine's (my) solution for granted; this makes the two packages (kcoreaddons and kcoreaddons-qt6) conflict, and is probably wrong.
This happens to me today in Pixel 7. TD1A.220804.031.2022102800
Same issue for me in Alpine w/ i915 driver. [sway.segfault.txt](https://github.com/swaywm/sway/files/9792515/sway.segfault.txt) Edit: got the same stacktrace when starting sway on boot with a monitor connected and kanshi on autostart.
This is still stuck on waiting-on-reporter but others have given debug logs already.
@rambip I have a similar problem with sticky keys; in Sway they are reliable, but in GNOME they are hit or miss.
Sorry for the shitty video, but here's a demo: [muestra2.webm](https://user-images.githubusercontent.com/86896666/200614734-c998129b-563d-4d19-83bf-9a1b5386d2ab.webm)
Even in GNOME, it doesn't happen under Qt apps. This also affects things like `&kp AT`, yielding 2 instead.