Comment 5 for bug 1341548

Thanks for the additional info on this.

Just to be sure I understand this correctly, confined apps in effect cannot manipulate the network session using a combo of QNetworkConfigurationManager and QNetworkSession to watch for changes in the network configuration, which i believe is where these dbus denials are coming from as it's using the bearer management api.

Dekko isn't doing anything major here regarding network session manipulation see http://bazaar.launchpad.net/~dpniel/dekko/trunk-1/view/head:/src/Imap/Model/SystemNetworkWatcher.cpp, but I can see why this isn't aloud in a confined app.

Looking at the available security profiles i see there is a 'connectivity' policy. Ideally it would be awesome to be able to determine offline, 3g/mobiledata and wifi and give the user options for setting bandwidth saving mode for mobile data connections on the fly etc...
I see there is some comments in that profile regarding the bug you mentioned previously, ( bug #1226844 ). Am I able to use this to determine the current connection/network state? Or do you know of any other way I can watch for network change events?