| Summary: | plasma-pk-update ignores proxyType=0 (in proxy configuration) | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Christian Quast <wildcart> |
| Component: | PK Updates widget | Assignee: | Jan Grulich <jgrulich> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | minor | CC: | jgrulich, kdedev, steve |
| Priority: | NOR | ||
| Version First Reported In: | 6.2.4 | ||
| Target Milestone: | 1.0 | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Christian Quast
2020-04-27 13:29:48 UTC
I'm also seeing this, using the pre-compiled openSUSE RPMs. I periodically get an 'Update Error' pop-up: ~~~ Download (curl) error for 'http://download.opensuse.org/repositories/KDE:/Applications/KDE_Frameworks5_openSUSE_Leap_15.1/repodata/repomd.xml': Error code: Connection failed Error message: Could not resolve proxy: HTTP_PROXY ~~~ The error can also be triggered by going to "Software Updates" (via the system tray) and clicking on the "Check for Updates" button. The same error can be seen when "Discover" is started. My user is set to not use a proxy; HTTP_PROXY is not set. The system default is also set to not use a proxy. Running the system update tool (in my case zypper) directly does not produce any such error. Versions: plasma5-pk-updates: 0.3.2 plasma5-workspace: 5.19.0 Thank you for the bug report. Unfortunately we were not able to get to it yet. If your system is still running Plasma 5, can we ask you to please check if this is still an issue with Plasma 5.27.12 (the current LTS version)? The PK Updates Widget has not been ported to Plasma 6, so if your system has updated to that, this report isn't relevant anymore. If you can still reproduce the bug, please change the Status to "CONFIRMED". Thanks. 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. |