Hide Forgot
Description of problem: I've observed that my laptop establishes connection to geoip.fedoraproject.org multiple times per second. It doesn't matter if it's idle or used. Constant use increases power consumption and can increase cost of metered internet access. # strace -p 1903 -etrace=connect -tt Process 1903 attached 11:28:00.673358 connect(11, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("140.211.169.197")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:04.805051 connect(12, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("140.211.169.197")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:06.562463 connect(11, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("152.19.134.146")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:07.218616 connect(12, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("66.135.62.201")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:08.223273 connect(10, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("66.135.62.201")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:09.487041 connect(12, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("85.236.55.6")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:09.692291 connect(11, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("67.203.2.67")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:09.816693 connect(11, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("152.19.134.146")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:10.820292 connect(10, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("66.135.62.201")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:10.908265 connect(10, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("85.236.55.6")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:11.682167 connect(11, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("66.135.62.201")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:11.807530 connect(11, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("152.19.134.146")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:12.067737 connect(12, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("213.175.193.206")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:13.219099 connect(11, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("67.203.2.67")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:13.621159 connect(10, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("80.239.156.215")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:14.421046 connect(10, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("209.132.181.16")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:15.461515 connect(12, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("66.35.62.166")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:15.697904 connect(10, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("80.239.156.215")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:15.796575 connect(11, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("67.203.2.67")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:15.888418 connect(11, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("67.203.2.67")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:15.989857 connect(11, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("66.35.62.166")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:16.095503 connect(11, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("67.203.2.67")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:16.498000 connect(10, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("67.203.2.67")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:16.727535 connect(10, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("213.175.193.206")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:18.979209 connect(12, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("85.236.55.6")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:21.397702 connect(11, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("80.239.156.215")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:21.657261 connect(12, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("85.236.55.6")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:21.774308 connect(11, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("80.239.156.215")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:23.080861 connect(10, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("66.135.62.201")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:23.435242 connect(11, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("66.135.62.201")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:24.227235 connect(11, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("66.35.62.166")}, 16) = -1 EINPROGRESS (Operation now in progress) 11:28:24.576246 connect(10, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("80.239.156.215")}, 16) = -1 EINPROGRESS (Operation now in progress) PID 1903 is: # systemctl status 1903 dbus.service - D-Bus System Message Bus Loaded: loaded (/usr/lib/systemd/system/dbus.service; static) Active: active (running) since Sun 2013-12-08 16:54:04 CET; 1 weeks 1 days ago Main PID: 652 (dbus-daemon) CGroup: /system.slice/dbus.service ├─ 652 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation └─1903 /usr/libexec/geoclue -t 5 Tcpdump confirms that majority (per number) of requests are to geoip.fedoraproject.org/city Version-Release number of selected component (if applicable): geoclue-0.12.99-5.fc20.x86_64 How reproducible: Always. Steps to Reproduce: 1. Run Fedora 20
Wrong component: $ rpm -qf /usr/libexec/geoclue geoclue2-2.0.0-1.fc20.x86_64
I have pushed some changes to latest release/git master that should fix this.
Zeeshan: has this been pushed to a stable release?
(In reply to Peter Robinson from comment #3) > Zeeshan: has this been pushed to a stable release? Nope.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.