Manual proxy is partially cleared on 20.04 => 22.04 upgrade

[Sam]

We installed 20.04.4 on a wiped SSD using the live USB stick after entering the credentials for our WLAN. We set a manual proxy via Settings/Network before doing the installation.

After the system came up, we set up a second user account, and set a manual proxy via Settings/Network in that account also. We made no changes to /etc/apt/apt.conf.

We installed openssh-server as well as aptitude and updated the system, rebooted, then connected to the system over ssh, ran screen and do-release-upgrade.

The system upgraded normally to 22.04.1.

After we rebooted we noticed that the manual proxy setting had been cleared from both user accounts (was disabled in Settings/Network) which was not desirable.

However we noticed that aptitude was still making proxy requests, because /etc/apt/apt.conf contained a manual proxy setting:

     Acquire::http::Proxy "http://proxy.xxxxx.com:xxxxx/";

So this is inconsistent. Ideally the proxy settings should not have been cleared from both user accounts. But if that is to be the case, it should have also been removed from /etc/apt/apt.conf.

[Nick Rosbrook (enr0n)]

I don't believe this is related to any ubuntu-release-upgrader logic. I will re-assign the bug to gnome-control-center since it sounds like that's where you're configuring your proxy.

[Sam (i41bktobiu5q-launchpadnet)]

Thank you Nick. Yes Settings/Network is where we configured the [squid] proxy, in both accounts.

[Sam (i41bktobiu5q-launchpadnet)]

Possibly the 20.04.4 live system is also involved, because to my knowledge setting a proxy via Settings/Network does not normally make any changes to /etc/apt/apt.conf (i.e. you are not prompted for a sudo password after setting a manual proxy in Settings/Network).

So I'm guessing the 20.04.4 live system made the apt.conf change since apt requires it. (Note: some earlier versions of Ubuntu live systems did not make the apt.conf change automatically; we had to do it manually whenever we had to use proxies.)

In any case, whatever cleared the manual proxy setting from both user accounts ideally shouldn't do that.