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.
I've extracted Lorn's connectivity-api draft commit and made it self-compiling:
https:/ /code.launchpad .net/~timo- jyrinki/ +junk/connectiv ity-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- connectivityapi bearer_ 0.0.1%7Eunrelea sed-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: arm-linux- gnueabihf/ qt5/plugins/ bearer away so that only libqubuntubearer.so is left
1. Install the .deb
2. Remove/move the three other bearers from /usr/lib/
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.