Arch Linux

Description:
I am suffering from an issue which is already reported upstream: https://bugreports.qt.io/browse/QTBUG-76657

Additional info:
a fix for this is queued in the 5.13 branch:
https://github.com/qt/qtwayland/commit/a4e6f88f50d1a1dd56df77ce8b07b98aceb20ddc.patch

to make that fix compile another backport is needed:
https://github.com/qt/qtwayland/commit/ec9057081f1094fbfeb11449bc533997731e4079.patch
(this seems to fix yet another QTBUG: https://bugreports.qt.io/browse/QTBUG-76397)

Steps to reproduce:
* (it doesn't always happen, but "most of the time" for me)
* start a plasma wayland session
* krunner:
** open krunner
** hide krunner
** (wait a while, do something else, ...)
** try to open krunner
** krunner does not show up anymore
* yakuake
** open yakuake
** hide yakuake
** (wait a while, do something else, ...)
** try to open yakuake again
** yakuake does not show up anymore
* (the next one I'm not sure about, it was "fixed" after I backported the two changes locally - but I'm not sure if that's some placebo effect...)
* plasma application launcher
** open the plasma application launcher
** close the plasma application launcher
** (watch as plasmashell restarts)

can you please backport qtwayland commits ec9057081f1094fbfeb11449bc533997731e4079 and a4e6f88f50d1a1dd56df77ce8b07b98aceb20ddc to the Arch Linux package?
upstream will include these with 5.13.1 which is going to be released in 6 weeks AFAIK.
I backported these two changes locally (updated PKGBUILD attached) and they fix the issues described above for me.