Arch Linux

Description:
After upgrading lib32-qt4 to 4.8.7-6, I get a segmentation fault with the following stack trace when trying to start Skype :

#0 0x00000000 in ?? ()
#1 0xf6c69e89 in ?? () from /usr/lib32/libQtWebKit.so.4
#2 0xf6c6a707 in ?? () from /usr/lib32/libQtWebKit.so.4
#3 0xf6fee52c in ?? () from /usr/lib32/libQtWebKit.so.4
#4 0xf6fd6795 in ?? () from /usr/lib32/libQtWebKit.so.4
#5 0xf6fd60a2 in ?? () from /usr/lib32/libQtWebKit.so.4
#6 0xf6fd5e2b in ?? () from /usr/lib32/libQtWebKit.so.4
#7 0xf6fd5c69 in ?? () from /usr/lib32/libQtWebKit.so.4
#8 0xf6c17318 in QWebFrame::load(QNetworkRequest const&, QNetworkAccessManager::Operation, QByteArray const&) () from /usr/lib32/libQtWebKit.so.4
#9 0xf6c169c5 in QWebFrame::load(QUrl const&) () from /usr/lib32/libQtWebKit.so.4
#10 0xf6c37d64 in QWebView::load(QUrl const&) () from /usr/lib32/libQtWebKit.so.4
#11 0x5681d830 in ?? ()
#12 0x568503fb in ?? ()
#13 0x56b3d0ed in ?? ()
#14 0xf57d821a in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib32/libQtCore.so.4
#15 0xf57ecb24 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib32/libQtCore.so.4
#16 0xf57f2df1 in ?? () from /usr/lib32/libQtCore.so.4
#17 0xf57e82d3 in QObject::event(QEvent*) () from /usr/lib32/libQtCore.so.4
#18 0xf5bfb730 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib32/libQtGui.so.4
#19 0xf5bfcf6a in QApplication::notify(QObject*, QEvent*) () from /usr/lib32/libQtGui.so.4
#20 0xf57d23db in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib32/libQtCore.so.4
#21 0xf5808501 in ?? () from /usr/lib32/libQtCore.so.4
#22 0xf5805e29 in ?? () from /usr/lib32/libQtCore.so.4
#23 0xf50182b9 in g_main_context_dispatch () from /usr/lib32/libglib-2.0.so.0
#24 0xf5018559 in ?? () from /usr/lib32/libglib-2.0.so.0
#25 0xf5018624 in g_main_context_iteration () from /usr/lib32/libglib-2.0.so.0
#26 0xf5805583 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib32/libQtCore.so.4
#27 0xf5cb318a in ?? () from /usr/lib32/libQtGui.so.4
#28 0xf57cf08d in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib32/libQtCore.so.4
#29 0xf57d2a48 in QCoreApplication::exec() () from /usr/lib32/libQtCore.so.4
#30 0xf5bfcde5 in QApplication::exec() () from /usr/lib32/libQtGui.so.4
#31 0x5680387b in ?? ()
#32 0xf528b196 in __libc_start_main () from /usr/lib32/libc.so.6
#33 0x567f6739 in ?? ()

Replacing libQtWebKit.so.4.9.4 with the one found in 4.8.7-4 fixes the bug.