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 Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices Status in Canonical System Image: Confirmed Status in Unity 8: New Status in dbus-cpp package in Ubuntu: In Progress Status in indicator-network package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Incomplete Status in qtbase-opensource-src package in Ubuntu: Confirmed Status in buteo-syncfw package in Ubuntu RTM: New Status in location-service package in Ubuntu RTM: In Progress Status in maliit-framework package in Ubuntu RTM: New Status in network-manager package in Ubuntu RTM: Incomplete Status in sync-monitor package in Ubuntu RTM: New Bug description: Krillin, rc-proposed, r83 DESCRIPTION: I've been trying to track down the cause of the occasional UI freezes on my Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I get a burst of "PropertiesChanged" signals in dbus-monitor Here's a log of what's shown in dbus-monitor: http://pastebin.ubuntu.com/11992322/ I'd guess the problem is in the code that actually catches the signals and acts accordingly. HOW TO REPRODUCE: 1) Move to a place where many wifi hotspots are available 2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor" 3) Use the device while keeping an eye on dbus-monitor output To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
