Bug 1358660

If adwaita-qt4 package is installed, Avidemux 2.6.12 Qt4 GUI (avidemux3_qt4) shows initially a blank window which fills with completely unresponsive controls a couple of minutes later while indefinitely consuming 100% of a CPU core, which renders this application unusable.

This problem was reported as a RPM Fusion bug https://bugzilla.rpmfusion.org/show_bug.cgi?id=4035 for Avidemux and F23 back in April, but it became only recently clear that the issue was related to adwaita-qt4. The bug equally affects Avidemux Qt4 builds from the current git trunk (despite Qt4 builds being declared obsolete upstream, the Qt5 GUI is not yet functional while the Qt4 one works unless hit by an issue like this one).


rpm -q avidemux-qt
avidemux-qt-2.6.12-3.fc24.x86_64

dnf info adwaita-qt4
Last metadata expiration check: 0:25:28 ago on Thu Jul 21 09:04:57 2016.
Available Packages
Name        : adwaita-qt4
Arch        : i686
Epoch       : 0
Version     : 0.4
Release     : 3.fc24
Size        : 53 k
Repo        : updates
Summary     : Adwaita Qt4 theme
URL         : https://github.com/MartinBriza/adwaita-qt
License     : LGPLv2+
Description : Adwaita theme variant for applications utilizing Qt4

Name        : adwaita-qt4
Arch        : x86_64
Epoch       : 0
Version     : 0.4
Release     : 3.fc24
Size        : 51 k
Repo        : updates
Summary     : Adwaita Qt4 theme
URL         : https://github.com/MartinBriza/adwaita-qt
License     : LGPLv2+
Description : Adwaita theme variant for applications utilizing Qt4


How reproducible:
Always.


Steps to Reproduce:
1. Install adwaita-qt4
2. Install avidemux-qt from rpmfusion.org or build it with a Qt4 GUI from source
3. Run the avidemux3_qt4 executable

Actual results: 
An unresponsive blank window opens, fills with unresponsive controls a few minutes later; Avidemux hangs indefinitely consuming 100% of a CPU core.

Expected results:
The Avidemux window is as fully functional as with adwaita-qt4 uninstalled.


The order of steps 1 and 2 doesn't matter, obviously. It also doesn't help to configure a different GTK+ and Qt theme, the mere presence of adwaita-qt4 is enough to trigger this bug.