Bug 1416396
Summary: | PackageKit still using proxy removed from gnome-settings | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Lorenzo Dalrio <lorenzo.dalrio> |
Component: | PackageKit | Assignee: | Richard Hughes <rhughes> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 25 | CC: | igitur, jonathan, klember, rdieter, rhughes, smparrish, tomek, wanwizard |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-12-12 10:45:54 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Lorenzo Dalrio
2017-01-25 12:19:15 UTC
I can't reproduce this anymore, now it is working as expected. I can reproduce it. { ~ } ยป pkcon refresh force /etc/yum.repos.d Refreshing cache [=========================] Loading cache [=========================] Finished [=========================] Fatal error: cannot update repo 'updates': Cannot prepare internal mirrorlist: Curl error (7): Couldn't connect to server for https://mirrors.fedoraproject.org/metalink?repo=updates-released-f25&arch=x86_64 [Failed to connect to 127.0.0.1 port 8080: Connection refused] Also PackageKit-1.1.5-1.fc25.x86_64 and no proxy defined in environment variables. Reopening, after modifying the proxy settings the problem happens again. Mar 01 08:42:43 gollum packagekitd[1750]: Skipping refresh of rpmfusion-free: cannot update repo 'rpmfusion-free': Cannot prepare internal mirrorlist: Curl error (5): Couldn't resolve proxy name for https://mirrors.rpmfusion.org/metalink?repo=free-fedora-25&arch=x86_64 [Could not resolve proxy: proxy.eng.it] I also have this problem (on F25, after updating also on F26). I have removed the proxy configuration months ago, and have been plagued by this issue ever since. I have found that altough the settings are changed in the gnome panel, they aren't updated in /var/lib/PackageKit/transactions.db (in the proxy table). I can confirm this in F27 - PackageKit-1.1.6-7.fc27.x86_64 This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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. |