After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 754056 - Provide a way to prevent background updates depending on network
Provide a way to prevent background updates depending on network
Status: RESOLVED DUPLICATE of bug 745747
Product: gnome-control-center
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-08-25 08:19 UTC by Luke Benstead
Modified: 2015-08-25 09:06 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Luke Benstead 2015-08-25 08:19:39 UTC 
Not sure this is the right component, I visualized it as a setting in control center but actually it might be network manager related...

I recently got bitten by the fact that GNOME downloads updates in the background by default when connected to WiFi. I hadn't used my laptop in a while and connected to my phone's 4G WiFi hotspot and then unknowingly wiped out my data quota for the month.

This can be rectified by running "gsettings set org.gnome.software download-updates false" but I don't really want to do that either. What I actually want is to prevent updates being downloaded when I'm connected to my WiFi hotspot only.

This isn't the first time I've wanted to restrict applications from using the Internet while connected to a hotspot (e.g. background syncing apps like Spideroak and Dropbox). A more general way to block applications depending on the Network you are connected to would be nice.
Comment 1 Bastien Nocera 2015-08-25 09:06:37 UTC 
Bug 745747 would be about tagging the connection as being metered, but separate bugs would need to be filed about various applications respecting this setting.

*** This bug has been marked as a duplicate of bug 745747 ***