Dear KDE developers, I seem to have found, what I would consider, a bug of plasma-pk-updates proxy handling: SUMMARY I recently moved a desktop computer from a network which requires a proxy to one which does not. For the proxy network, I set-up the proxy configuration using `kcmshell5 proxy` "use manually specified proxy configuration." This seems to write the proxy configuration to `.config/kioslaverc` setting 'ProxyType' to 1. After moving the computer to the 'proxy-less' network I updated the proxy configuration to "None" and 'ProxyType' was set to '0' but all other settings in this file were kept (specifically the URLs are still pointing to the proxy). Programs like chromium based browser and other applications using the proxy configuration seem to work fine: With 'ProxyType=1' they are using the proxy (and complain about the Internet/proxy not being reachable in the proxy-less network) and with 'ProxyType=0' they ignore the rest of the proxy settings and connect to the Internet directly. Not so `plasma-pk-updates` which always complains about the proxy not being reachable. > Download (curl) error for > https://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: proxy.domain.tld I also tried to logout and even reboot the computer which doesn't have any effects. STEPS TO REPRODUCE 1. Run `kcmshell proxy` to "use manually specified proxy configuration" (it doesn't matter if the proxy exists or not). 2. Run `kcmshell proxy` set proxy to "None" (make sure proxy URLs are still set in `config/kioslaverc`). 2a. maybe logout to be sure that `plasma-pk-updates` isn't using any 'outdated' proxy configuration. 3. run plasma-pk-updates OBSERVED RESULT Download (curl) error for 'https://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: proxy.domain.tld EXPECTED RESULT plasma-pk-updates ignoring the proxy configuration if `ProxyType=0`. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE with KDE installed from OBS KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 ADDITIONAL INFORMATION `plasma-pk-updates` works fine if the proxy URLs are 'blanked'/removed from `.config/kioslaverc` or if the files is removed completely.
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.