@Timo Thanks for the update. I commented on bug #1404188 regarding this bug. I agree with you that moving to a new backend for the vivid-overlay PPA is risky. That said, if we keep the networkmanager bug backend, this bug really needs to be fixed.
What you say about the networkmanager backend is true, as NM is the controller of our networking, so querying it makes sense if you want to know whether we're on 3g or WiFi. That said, the connectivity API was originally designed to do the same thing, although it was never actually "published" as an API that could be used by the rest of the system. It was designed for this, however the team never finished the work, so AFAIK to date, it's only been used by indicator-network. In *theory*, it should be possible to query the same exact information from a connectivity-API based backend. It would give far less control however actually permitting changes to the network configuration and/or what interface was activated. I think that's OK, as we delegate all of that to indicator-network. We have no concept of a network-admin capability that can be granted to apps ( again AFAIK ). -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
