proxy issues following upgrade

[woodward2]

Hi,

I recently upgraded (Mint MATE) 19.3 --> 20 --> 20.1

I had three issues (and one annoyance that may be related) connected to proxy settings:

1. privoxy: I set the system and browser proxy settings to 127.0.0.1:8118 as usual, but firefox and chrome would not connect to it. "systemctl status" showed that it was loaded OK, but I had to un-install / re-install privoxy to get it to work (it worked immediately without changing any settings).

2. I use Amazon AWS CLI to backup photos to Amazon Glacier. This stopped working after the upgrade. To make it work I had to add the address of the Amazon server to the "Ignored Hosts" list (and the "no_proxy" env variable for good measure) - so it is clearly related to proxy settings. There is no reference to anything like the server name in the privoxy configuration files.

3. curl doesn't work at all; it just hangs immediately without downloading anything. To make it work I had to alias curl to 'curl --noproxy "*" ' - again, related to proxy settings

4. When running synaptic, if I click on "Get Screenshot" for a package it just hangs without downloading anything until it times out. "Get Changelog" works OK.

All of the above work OK out of the box in a fresh install of Mint MATE 20 --> 20.1 in a VM.

Code: Select all

System:    Kernel: 5.4.0-70-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: MATE 1.24.0 info: mate-panel 
           wm: marco 1.24.0 dm: LightDM 1.30.0 Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focal 
Machine:   Type: Desktop Mobo: FOXCONN model: A6GMV v: 0A serial: <filter> BIOS: American Megatrends v: 080014 
           date: 07/22/2010 
CPU:       Topology: Quad Core model: AMD Athlon II X4 640 bits: 64 type: MCP arch: K10 rev: 3 L2 cache: 2048 KiB 
           flags: lm nx pae sse sse2 sse3 sse4a svm bogomips: 24001 
           Speed: 800 MHz min/max: 800/3000 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 
Graphics:  Device-1: NVIDIA GF108 [GeForce GT 430] driver: nvidia v: 390.141 bus ID: 01:00.0 chip ID: 10de:0de1 
           Display: x11 server: X.Org 1.20.9 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa compositor: marco 
           v: 1.24.0 resolution: 1920x1080~60Hz 
           OpenGL: renderer: GeForce GT 430/PCIe/SSE2 v: 4.6.0 NVIDIA 390.141 direct render: Yes 
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] SBx00 Azalia vendor: Foxconn driver: snd_hda_intel v: kernel 
           bus ID: 00:14.2 chip ID: 1002:4383 
           Device-2: NVIDIA GF108 High Definition Audio driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0bea 
           Sound Server: ALSA v: k5.4.0-70-generic 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Foxconn driver: r8169 v: kernel port: e800 
           bus ID: 02:00.0 chip ID: 10ec:8168 
           IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 3.33 TiB used: 2.28 TiB (68.4%) 
           ID-1: /dev/sda vendor: Hitachi model: HDS721050CLA362 size: 465.76 GiB speed: 3.0 Gb/s rotation: 7200 rpm 
           serial: <filter> rev: A3MA scheme: MBR 
           ID-2: /dev/sdb vendor: Western Digital model: WD10EAVS-00M4B0 size: 931.51 GiB speed: 3.0 Gb/s serial: <filter> 
           rev: 0A01 scheme: GPT 
           ID-3: /dev/sdc vendor: Western Digital model: WD1600AAJS-00V4A0 size: 149.05 GiB speed: 3.0 Gb/s serial: <filter> 
           rev: 1D05 scheme: MBR 
           ID-4: /dev/sde type: USB vendor: Hitachi model: HDS722020ALA330 size: 1.82 TiB rotation: 7200 rpm serial: <filter> 
           scheme: MBR 
Partition: ID-1: / size: 31.83 GiB used: 24.71 GiB (77.6%) fs: ext4 dev: /dev/sda1 
           ID-2: /home size: 425.36 GiB used: 295.14 GiB (69.4%) fs: ext4 dev: /dev/sda5 
           ID-3: swap-1 size: 7.45 GiB used: 382.5 MiB (5.0%) fs: swap dev: /dev/sdc1 
Sensors:   System Temperatures: cpu: 31.0 C mobo: N/A gpu: nvidia temp: 56 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 36% 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/gezakovacs-ppa-focal.list 
           1: deb http://ppa.launchpad.net/gezakovacs/ppa/ubuntu focal main
           Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
           1: deb http://mirrors.evowise.com/linuxmint/packages ulyssa main upstream import backport
           2: deb http://mirror.freethought-internet.co.uk/ubuntu focal main restricted universe multiverse
           3: deb http://mirror.freethought-internet.co.uk/ubuntu focal-updates main restricted universe multiverse
           4: deb http://mirror.freethought-internet.co.uk/ubuntu focal-backports main restricted universe multiverse
           5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
           6: deb http://archive.canonical.com/ubuntu/ focal partner
           Active apt repos in: /etc/apt/sources.list.d/tarsnap.list 
           1: deb http://pkg.tarsnap.com/deb/ulyssa ./
Info:      Processes: 279 Uptime: 1d 16h 13m Memory: 7.77 GiB used: 2.77 GiB (35.7%) Init: systemd v: 245 runlevel: 5 
           Compilers: gcc: 9.3.0 alt: 7/9 Shell: bash v: 5.0.17 running in: mate-terminal inxi: 3.0.38 

I would like to understand especially the AWS and curl issues so I can get rid of the workarounds.

Any help appreciated.

[djph]

If it all works entirely as expected in a fresh 20.1 install (well, post some initial configuration, obviously); I would attribute it to things changing between the 19 and 20 bases.

Most likely some configuration parameters got renamed / deprecated / etc; but the upgrade from 19 would've kept the old config files around in either $HOME or /etc

[woodward2]

I guess it must be something like that, but it's hard to figure out what has changed without knowing where to look. When I get time, I'm currently concentrating on privoxy configs by diff-ing the changes between my old setup (backed up prior to the update) and the current privoxy config. I'm not fully convinced that is the issue, since a clean install works OK, and I made only a couple of minor additions to the privoxy user-config.

I'm also going through the apt logs from the upgrade to see if I can see anything.

I was hoping that someone may have experienced a similar issue and figured it out - after all, privoxy isn't a niche application - which is why I left the upgrade a good while, so that any bugs would be found and ironed out.

Oh well, back to the sleuthing...

[djph]

Yes - a clean install with clean configs that don't have any "old version" cruft like what you'd get with an in-place upgrade.