Bug 411316 (discover-proxy) - Discover continues to use proxy even after proxy has been disabled
Summary: Discover continues to use proxy even after proxy has been disabled
Status: RESOLVED WORKSFORME
Alias: discover-proxy
Product: Discover
Classification: Applications
Component: discover (show other bugs)
Version: 5.19.5
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Dan Leinir Turthra Jensen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-26 11:46 UTC by Deleted account
Modified: 2024-04-20 07:47 UTC (History)
9 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
The following error can be seen (59.08 KB, image/png)
2019-08-26 11:46 UTC, Deleted account
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Deleted account 2019-08-26 11:46:06 UTC
Created attachment 122367 [details]
The following error can be seen

SUMMARY
Discover tries to use proxy last set, even if disabled.

STEPS TO REPRODUCE
1. Set a proxy in Proxy settings, use manual proxy. Not tested with other proxy server options.
2. Start discover and check for updates
3. Then, disable the proxy again
4. Start discover to check again

OBSERVED RESULT
After a wait, an error message will pop up, stating "[repo name] is not available (could not connect to [proxy address]"

EXPECTED RESULT
Discover will check for updates and show what packages can be updated.

SOFTWARE/OS VERSIONS
Windows: N.A.
macOS: N.A.
Linux/KDE Plasma: Kubuntu 19.04
(available in About System)
KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.56.0
Qt Version: 5.12.2

ADDITIONAL INFORMATION
Comment 1 Deleted account 2019-08-28 19:20:04 UTC
The problem seems to have resolved with no additional action from my side. I would still consider this a bug.
Comment 2 Deleted account 2019-08-29 08:35:40 UTC
The next day, the problem reappeared. Installing packages is not possible today, but was for a short time (yesterday). Before yesterday, installing wasn't possible either.
Comment 3 Deleted account 2019-08-29 08:41:13 UTC
This is indeed a problem with Discover, as updating using Muon or running sudo apt update && sudo apt upgrade works fine.
Comment 4 Aleix Pol 2019-09-06 00:55:43 UTC
Yes, that makes sense. Thanks for reporting, will look into it.
Comment 5 Aleix Pol 2019-12-02 18:34:46 UTC

*** This bug has been marked as a duplicate of bug 410843 ***
Comment 6 Anton K 2020-09-28 12:03:52 UTC
I have the same error.

Operating System: KDE neon 5.19
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0
Qt Version: 5.15.0
Kernel Version: 5.4.0-48-generic
Comment 7 Martin Stolpe 2020-10-11 10:31:42 UTC
A solution to this problem has been posted here: https://forum.kde.org/viewtopic.php?f=309&t=161739#p430783
Comment 8 Eddie 2020-11-23 20:15:36 UTC
The work-around above is not a fix or a solution, it's a dirty workaround,

New KDE users would expect Discover to behave like other applications: act correctly on current KDE settings.

Discover should behave correctly: i.e. check KDE proxy settings, 
not "assume" old outdated incorrect disabled proxy details. My 2c opinion.
Comment 9 kde 2021-01-21 13:04:19 UTC
I see this bug, too.  It's somewhat of a pest because notifications show frequently on the desktop letting you know that connecting to the proxy failed.
Comment 10 laurentlepoittevin 2021-02-10 13:55:45 UTC
I've just switched to KDE.
This proxy problem is really annoying when you use your pc in a professional environment.
For my part I found that :
1 / the proxy settings in system configuration tools are not saved
2 / if I configure kioslaverc manually it works except for packagekit (except the first time),
3 / at the first configuration of kioslaverc (or apt.conf??) the proxy settings for packagekit are saved in transactions.db but, if you need to use another network without proxy, there is no way back. The only solution is to delete the transactions.db file (/var/lib/PackageKit/transactions.db).
This is a very annoying problem.
It is a concern especially the 1 exists under Neon and on kubuntu 20.04, so for this one it is certainly related to KDE and not to package kit.
Comment 11 Mikhail 2024-04-20 07:47:31 UTC
Hello!
I have th same problem:
SUMMARY
Discover is trying to use proxy, which was removed from the system

STEPS TO REPRODUCE
1. Launch Discover
2. Press Update all
3. 

OBSERVED RESULT
Не удалось загрузить пакет.:

E: http://ftp.linux.org.tr/ubuntu jammy-updates/main amd64 ubuntu-pro-client-l10n amd64 31.2.2~22.04 is not (yet) available (407 Proxy Authentication Required [IP: 176.222.59.2 59704]) E: http://ftp.linux.org.tr/ubuntu jammy-updates/main amd64 ubuntu-pro-client amd64 31.2.2~22.04 is not (yet) available (407 Proxy Authentication Required [IP: 176.222.59.2 59704]) E: http://ftp.linux.org.tr/ubuntu jammy-updates/main amd64 openssh-client amd64 1:8.9p1-3ubuntu0.7 is not (yet) available (407 Proxy Authentication Required [IP: 176.222.59.2 59704]) E: http://ftp.linux.org.tr/ubuntu jammy-updates/main amd64 ubuntu-advantage-tools all 31.2.2~22.04 is not (yet) available (407 Proxy Authentication Required [IP: 176.222.59.2 59704]) E: http://ftp.linux.org.tr/ubuntu jammy-updates/restricted amd64 firmware-sof-signed all 2.0-1ubuntu4.7 is not (yet) available (407 Proxy Authentication Required [IP: 176.222.59.2 59704]) E: https://dl.google.com/linux/chrome/deb stable/main amd64 google-chrome-stable amd64 124.0.6367.60-1 is not (yet) available (Invalid response from proxy: HTTP/1.0 407 Proxy Authentication Required Proxy-Authenticate: Basic realm="proxy" Connection: close Content-type: text/html; charset=utf-8 [IP: 176.222.59.2 59704]) 

EXPECTED RESULT
Sucsessfull update

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 5.24.7
(available in About /System)
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3