The silo 32 (https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-032/+packages) contains these fixes backported to Qt 5.4.1:
https://codereview.qt-project.org/#/c/122382/ https://codereview.qt-project.org/#/c/113478/ https://codereview.qt-project.org/#/c/121724/ https://codereview.qt-project.org/#/c/126219/ (with setting to skip generic plugin via ubuntu-touch-session package) With those this bug and accessibility property are fixed, but with the downside of NM bearer starting to somehow depend on more DBus calls that get blocked by apparmor (I meant "blocked by apparmor", not "blocking calls"), causing this same bug #1508945 as what happens with the PPA with Qt 5.5 packages (which have the one post-5.5.1 commit cherry- picked). If the apparmor rules are relaxed the same way as would be needed for fixing bug #1404188, the problems disappear, but alas we can't relax them for real. So unfortunately the fixes can't be apparently landed if not also switching to connectivity-api bearer or if there's a solution to NM bearer that fixes the bugs fixed in those first three commits without causing the new problem in our current apparmor setup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1470700 Title: QNetworkAccessManager hangs when in flight mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1470700/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
