https://bugs.kde.org/show_bug.cgi?id=359467
Bug ID: 359467
Summary: KWin might cause recursive QXcbEventReader::lock()'s
Product: kwin
Version: git master
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: core
Assignee: kwin-bugs-n...@kde.org
Reporter: thomas.luebk...@gmail.com
QXcbEventReader uses a non-recursive mutex (one might call this begging for
trouble, but well...) and KWin calls QX11Info::getTimestamp() when activating a
window after the active window closed (see backtrace)
This sucks a bit, we either need to defer activation to the end of the
eventloop (bad idea, since we're gonna loose the formerly active client until
then) or avoid fetching the X11 timestamp while we're in the eventloop.
Latter will inevitably collide w/ any solution reg. bug #348569 *AND* it's
pretty hard to assure we're not causing other access to the eventreader from
the eventfilter.
=> Maybe ask Qt to use a recursive mutex in 5.6?
Other ideas?
Reproducible: Always
--
You are receiving this mail because:
You are watching all bug changes.
