Now that Qt 4.8.3 (the first upstream Qt version to include this patch) is in Arch Linux, the problem occurs there too. For me, it caused both plasma-desktop and kwin to segfault on startup, thus making KDE almost unusable. (As a temporary measure to prevent these from crashing, I reverted to Qt 4.8.2.) https://bugs.archlinux.org/task/31654
Now that Qt 4.8.3 (the first upstream Qt version to include this patch) is in Arch Linux, the problem occurs there too. For me, it caused both plasma-desktop and kwin to segfault on startup, thus making KDE almost unusable. (As a temporary measure to prevent these from crashing, I reverted to Qt 4.8.2.) /bugs.archlinux .org/task/ 31654
https:/
There's also an Ubuntu bug report which looks it it might be caused by this patch: /bugs.launchpad .net/ubuntu/ +source/ qt4-x11/ +bug/1045755
https:/
This patch actually appears to have originated 2 years ago in the upstream WebKit SVN repository: trac.webkit. org/changeset/ 62799 /bugs.webkit. org/show_ bug.cgi? id=41641 qt.gitorious. org/qt/ qtscript/ commit/ 79ebd39d0d4846c b911ae122d2059e 5add568d7e qt.gitorious. org/qt/ qt/commit/ ada98493bbfbd9a f0d0b593017e29d 39bcd3495e /bugreports. qt-project. org/browse/ QTBUG-23871
http://
https:/
But it wasn't until August this year that it migrated from WebKit's JavaScriptCore to the copy of JavaScriptCore in the QtScript module of Qt:
http://
http://
https:/
Maybe it would be worth reporting the problem to the upstream WebKit developers?