Package: privoxy
Version: 3.0.34-3+b2
Severity: important

Usually the first thing I do after booting is starting firefox. Here I have to start until
privoxy starts which takes aroun two mins.

I purged the package, reinstalled. No change.


-- System Information:
Debian Release: trixie/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.6.22 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages privoxy depends on:
ii adduser 3.137
ii debconf [debconf-2.0] 1.5.86
ii init-system-helpers 1.66
ii libbrotli1 1.1.0-2+b3
ii libc6 2.38-6
ii libmbedcrypto7t64 2.28.7-1.1
ii libmbedtls14t64 2.28.7-1.1
ii libmbedx509-1t64 2.28.7-1.1
ii libpcre2-8-0 10.42-4+b1
ii logrotate 3.21.0-2
ii ucf 3.0043+nmu1
ii zlib1g 1:1.3.dfsg-3.1

Versions of packages privoxy recommends:
it doc-base 0.11.2

Versions of packages privoxy suggests:
ii apparmor 3.0.12-1+b2

-- debconf information:
privoxy/listen-address: 127.0.0.1:8118 [::1]:8118

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Eric!

Thank you for your bug report.

On So, 24 Mär 2024, Eric Valette wrote:

Package: privoxy
Version: 3.0.34-3+b2
Severity: important

Usually the first thing I do after booting is starting firefox. Here
I have to start until privoxy starts which takes aroun two mins.

I purged the package, reinstalled. No change.

I didn't notice a problem with privoxy startup time, so let's try to
track down what's the root cause of your problem is.

privoxy waits for network-online.target before it starts.
Maybe you could check, whether network-online or privoxy is delaying
here.

What do you see in the output of
systemctl status network-online.target privoxy.service
On my system provoxy starts a the moment when network-online is active
and takes 1 second to start.
Can you see, when network-online is active on your system? Is it just
after booting or does it also take these two minutes?

If the former, this isn't a privoxy issue, since privoxy has to wait
for a working network, otherwise it isn't able to bind the interfaces
(this was a problem in https://bugs.launchpad.net/ubuntu/+source/privoxy/+bug/1870101).

If it's a problem in privoxy, that it is really starting up delayed,
what do you see
journalctl -u privoxy
or in /varl/log/privoxy/logfile?
Maybe you should (temporarily) increase debug level in
/etc/provoxy/config (maybe debug 4096 could be helpful, maybe others,
too).

Does your problem only happen on system startup or can you reproduce
it via
systemctl stop privoxy; systemctl start privoxy

Greetings
Roland

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)