Surely if this patch fixes the issue, it should be possible to backport the same fix also to the Qt 5.0.1 in raring (unless there is something blocking the patch to work with 5.0.1 vs. 5.0.2 in saucy). The policy is to first have the fix tested in a development release, so let's have that first.
Surely if this patch fixes the issue, it should be possible to backport the same fix also to the Qt 5.0.1 in raring (unless there is something blocking the patch to work with 5.0.1 vs. 5.0.2 in saucy). The policy is to first have the fix tested in a development release, so let's have that first.