I've extracted Lorn's connectivity-api draft commit and made it self- compiling:
https://code.launchpad.net/~timo-jyrinki/+junk/connectivity-api-bearer You can either compile it yourself on the device or get this build for vivid/rc-proposed: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-059/+build/8313308/+files/libqt5network5-connectivityapibearer_0.0.1 %7Eunreleased-0ubuntu1%7Evivid1%7Etest1_armhf.deb It seems not to crash at least on device, but I don't know how to test it further. To test it: 1. Install the .deb 2. Remove/move the three other bearers from /usr/lib/arm-linux-gnueabihf/qt5/plugins/bearer away so that only libqubuntubearer.so is left 3. Reboot There'd now be also the new upstream method of QT_EXCLUDE_GENERIC_BEARER=1 that will be in Ubuntu's Qt 5.5 packages, but then I do not how it would be selected if NM or Ubuntu backend is used - if we get connectivity-api bearer working well enough, we should be able to specify it explicitly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
