Bugzilla – Bug 1116439
privoxy segfaults with 20181116
Last modified: 2019-08-11 11:37:26 UTC
Since the latest update privoxy is not usable any more. It segfaults. Backtrace is: # journalctl -xe (snip) Nov 17 14:25:50 silversurfer systemd[1]: Starting Privoxy Web Proxy With Advanced Filtering Capabilities... -- Subject: Unit privoxy.service has begun start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit privoxy.service has begun starting up. Nov 17 14:25:50 silversurfer kernel: privoxy[8638]: segfault at 10 ip 00007fc1fa66b9c7 sp 00007ffda370a5b0 error 6 in libc- 2.27.so[7fc1fa5e8> Nov 17 14:25:50 silversurfer kernel: Code: 24 88 08 00 00 0f 87 38 04 00 00 48 8b 50 18 48 83 e1 f8 49 81 fe ff 03 00 00 77 09 48 39 da 0f 8> Nov 17 14:25:51 silversurfer systemd[1]: privoxy.service: Control process exited, code=exited status=1 Nov 17 14:25:51 silversurfer systemd[1]: privoxy.service: Failed with result 'exit-code'. Nov 17 14:25:51 silversurfer systemd[1]: Failed to start Privoxy Web Proxy With Advanced Filtering Capabilities. -- Subject: Unit privoxy.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit privoxy.service has failed. -- -- The result is RESULT. # systemctl status privoxy.service ● privoxy.service - Privoxy Web Proxy With Advanced Filtering Capabilities Loaded: loaded (/usr/lib/systemd/system/privoxy.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sat 2018-11-17 14:25:51 CET; 16s ago Process: 8637 ExecStart=/usr/sbin/privoxy --chroot --pidfile /run/privoxy.pid --user privoxy /etc/config (code=exited, status=1/FAILURE) Process: 8636 ExecStartPre=/usr/bin/cp -upf /lib64/libresolv.so.2 /lib64/libnss_dns.so.2 /var/lib/privoxy/lib64/ (code=exited, status=0/SU> Process: 8635 ExecStartPre=/usr/bin/cp -upf /etc/resolv.conf /etc/host.conf /etc/hosts /etc/localtime /var/lib/privoxy/etc/ (code=exited, > Nov 17 14:25:50 silversurfer systemd[1]: Starting Privoxy Web Proxy With Advanced Filtering Capabilities... Nov 17 14:25:51 silversurfer systemd[1]: privoxy.service: Control process exited, code=exited status=1 Nov 17 14:25:51 silversurfer systemd[1]: privoxy.service: Failed with result 'exit-code'. Nov 17 14:25:51 silversurfer systemd[1]: Failed to start Privoxy Web Proxy With Advanced Filtering Capabilities.
from dmesg: [ 44.090408] privoxy[1897]: segfault at 10 ip 00007f7a4881b9c7 sp 00007fffc1e90660 error 6 in libc-2.27.so[7f7a48798000+1b6000] [ 44.090414] Code: 24 88 08 00 00 0f 87 38 04 00 00 48 8b 50 18 48 83 e1 f8 49 81 fe ff 03 00 00 77 09 48 39 da 0f 84 46 04 00 00 49 89 54 24 78 <48> 89 5a 10 49 39 ce 0f 84 84 01 00 00 48 81 f9 ff 03 00 00 0f 87 [ 44.203546] Bridge firewalling registered [ 44.511140] usblp0: removed [ 44.522016] usblp 9-2:1.0: usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x043D pid 0x011F [ 45.229070] nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based firewall rule not found. Use the iptables CT target to attach helpers instead. [ 69.072631] Bluetooth: RFCOMM TTY layer initialized [ 69.072637] Bluetooth: RFCOMM socket layer initialized [ 69.072642] Bluetooth: RFCOMM ver 1.11 [ 90.673162] fuse init (API version 7.27) [ 137.636676] privoxy[3942]: segfault at 10 ip 00007f3c74ffb9c7 sp 00007ffcaffcd7c0 error 6 in libc-2.27.so[7f3c74f78000+1b6000] [ 137.636687] Code: 24 88 08 00 00 0f 87 38 04 00 00 48 8b 50 18 48 83 e1 f8 49 81 fe ff 03 00 00 77 09 48 39 da 0f 84 46 04 00 00 49 89 54 24 78 <48> 89 5a 10 49 39 ce 0f 84 84 01 00 00 48 81 f9 ff 03 00 00 0f 87 [ 223.710242] privoxy[3965]: segfault at 10 ip 00007ff91f3e39c7 sp 00007fffce0d8ff0 error 6 in libc-2.27.so[7ff91f360000+1b6000] [ 223.710249] Code: 24 88 08 00 00 0f 87 38 04 00 00 48 8b 50 18 48 83 e1 f8 49 81 fe ff 03 00 00 77 09 48 39 da 0f 84 46 04 00 00 49 89 54 24 78 <48> 89 5a 10 49 39 ce 0f 84 84 01 00 00 48 81 f9 ff 03 00 00 0f 87 were the first instance is the system start. The two last are manually triggered.
I also had the same issue on two different workstation (one with Intel CPU and the other with AMD CPU, both with Tumbleweed). from dmesg: privoxy[19447]: segfault at 10 ip 00007fa4cf2ed9c7 sp 00007ffd1c831400 error 6 in libc-2.27.so[7fa4cf26a000+1b6000] Code: 24 88 08 00 00 0f 87 38 04 00 00 48 8b 50 18 48 83 e1 f8 49 81 fe ff 03 00 00 77 09 48 39 da 0f 84 46 04 00 00 49 89 54 24 78 <48> 89 5a 10 49 39 ce 0f 84 84 01 00 00 48 81 f9 ff 03 00 00 0f 87 On the AMD workstation I've solved adding this repository: http://download.opensuse.org/repositories/server:/proxy/openSUSE_Factory/
still valid for TW 20181126 44.165974] privoxy[1929]: segfault at 10 ip 00007fa199bc39c7 sp 00007ffe5ffaece0 error 6 in libc-2.27.so[7fa199b40000+1b6000] [ 44.165980] Code: 24 88 08 00 00 0f 87 38 04 00 00 48 8b 50 18 48 83 e1 f8 49 81 fe ff 03 00 00 77 09 48 39 da 0f 84 46 04 00 00 49 89 54 24 78 <48> 89 5a 10 49 39 ce 0f 84 84 01 00 00 48 81 f9 ff 03 00 00 0f 87
I encountered segmentation faults when starting privoxy after upgrading to 20181208 (from 201809xx). The version of privoxy at this point is 3.0.26-1.5 from repository openSUSE-Tumbleweed-Oss. I find this is related to two lines in the default configuration file /etc/privoxy/config: actionsfile default.action # Main actions file actionsfile user.action # User customizations With these two lines commented out, privoxy can start successfully. I also installed the source package of privoxy version 3.0.26-1.5 from repository openSUSE-Tumbleweed-Source and configured it to use a custom prefix and did a `make` and `make install`. This manually built privoxy can start without problems, using the same configuration files (without those two lines commented out) and command line options. I suspect there's something wrong when making the prebuilt package. Also noted the version suggested by Alessandro can start successfully, too.
I encountered segmentation faults when starting privoxy after upgrading to 20181208 and the issue is still present in 20181224. The current version of privoxy is 3.0.26-1.5 from repository openSUSE-Tumbleweed-OSS. Here's the error output: -- Unit privoxy.service has begun starting up. Jan 09 01:35:42 host kernel: privoxy[3507]: segfault at 10 ip 00007fc94c6a19c7 sp 00007ffcfcb3e6f0 error 6 in libc-2.27.so[7fc94c61e000+1b6000] Jan 09 01:35:42 host kernel: Code: 24 88 08 00 00 0f 87 38 04 00 00 48 8b 50 18 48 83 e1 f8 49 81 fe ff 03 00 00 77 09 48 39 da 0f 84 46 04 00 00 49 89 54 24 78 <48> 89 5a 10 49 39 ce 0f 84 84 01 00 00 48 81 f9 ff 03 00 00 0f 87 Jan 09 01:35:43 host systemd[1]: privoxy.service: Control process exited, code=exited status=1 Jan 09 01:35:43 host systemd[1]: privoxy.service: Failed with result 'exit-code'. Jan 09 01:35:43 host systemd[1]: Failed to start Privoxy Web Proxy With Advanced Filtering Capabilities. -- Subject: Unit privoxy.service has failed Seems like this is some interaction with newer version of libc and the configuration files.
I just upgrade to a newer openSUSE privoxy package. It has resumed working. Here's the package detail for those with this problem: Name : privoxy Version : 3.0.28 Release : 1.1 Architecture: x86_64 Install Date: Sat Jan 12 19:44:27 2019 Group : Productivity/Networking/Web/Proxy Size : 968762 License : GPL-2.0-or-later Signature : RSA/SHA256, Thu Jan 3 12:56:21 2019, Key ID b88b2fd43dbdc284 Source RPM : privoxy-3.0.28-1.1.src.rpm Build Date : Thu Jan 3 12:56:06 2019 Build Host : lamb55 Relocations : (not relocatable) Packager : https://bugs.opensuse.org Vendor : openSUSE
seems to be fixed in current version