package dante : socksify: error: dante client not built with preloading support

  • Done
  • quality assurance status badge
Details
3 participants
  • Benjamin
  • Nguy?n Gia Phong
  • Simon Tournier
Owner
unassigned
Submitted by
Benjamin
Severity
normal
B
B
Benjamin wrote on 3 May 2023 15:55
(address . bug-guix@gnu.org)
CSCON2VSU156.3J9X3VHN2OD93@robot.uvy.fr
Hello,

Dante package is not compiled with preloading support but it
could be

To reproduce :

guix shell dante w3m
echo "<hmtl><h1> Hello </h1> <p> World ! </p> </html>" | (
export SOCKS_SERVER="127.0.0.1:1"
exec socksify w3m -T text/html -dump
)

Following error is returned
error: dante client not built with preloading support.

Here is the result without socksify
```
echo "<hmtl><h1> Hello </h1> <p> World ! </p> </html>" | (w3m -T text/html -dump)
```

For additional information, I faced the problem when using the "html"
filter of aerc

cat /gnu/store/...aerc.../share/aerc/filters/html
```
#!/gnu/store/rib9g2ig1xf3kclyl076w28parmncg4k-bash-minimal-5.1.16/bin/sh
# aerc filter which runs w3m using socksify (from the dante package) to prevent
# any phoning home by rendered emails
export SOCKS_SERVER="127.0.0.1:1"
exec socksify w3m \
-I UTF-8 \
-T text/html \
-cols $(tput cols) \
-dump \
-o display_image?lse \
-o display_link_number=true
```

It seems that there was also these problem on the side of nixos :
N
N
Nguy?n Gia Phong wrote on 20 Dec 2023 08:18
(address . 63250@debbugs.gnu.org)
CXSZ7TYH49G6.2D6B5YNQM3FJS@guix
Could you take a look at https://issues.guix.gnu.org/67675
if it fixes it for you?
-----BEGIN PGP SIGNATURE-----

iQHIBAABCAAyFiEE6Q4RuASTNDthMuOUJxSLLAaiIksFAmWClWEUHG1jc2lueXhA
ZGlzcm9vdC5vcmcACgkQJxSLLAaiIkuQKAv9E14tVWHRCmBmW22QORZJNJuFm89C
3DCvlI9YLt8DwJWaJn4TxE2wJO1aud4SXkteLQgo9i5OcQCn3kV794+CSJGr4ynv
XexrI0A9ZD3TJwVlJYQkibajSYjv2AwXzVvpgW+f+Xai3QMOnuCIfIRNPNr8cf9l
BTzejDegrG8QPlZHapUwqeP5iIdHxhoeO6lytSJNoUS67dZtf70L/F1XmCsts9YT
KCQzCRCmc+DRpHVrNbepdQr+CZh6nj9KSs6fqd9nTxLHy7GCE9joHnK4zyv21t0K
girN8vL54/uVV3/eq2HYMqzHS1yRF2ehtN8Pgz2vO0NaVrKZY1otgtWfMEfGHrTU
nwmWJ2O7W2gY11j8BlUAKm51DpoDGYUBUFzaM7/9u2PKDbcvvrWWR0zIpEoIXhkC
t1cqqCcwfdlXD9+Xz3hAHmFFfe+1WfNxE2TgT5M/zV4kd1Totsc2OrqkWSr4T1vt
pHZJIfQs8s/ws70hKIP4Fxb42ZYBZgLJfdyK
=TJ5q
-----END PGP SIGNATURE-----


S
S
Simon Tournier wrote on 15 Feb 17:18 +0100
(name . Benjamin)(address . benjamin@uvy.fr)
875xyp7lbj.fsf@gmail.com
Hi,

On mer., 20 déc. 2023 at 16:18, Nguy?n Gia Phong via Bug reports for GNU Guix <bug-guix@gnu.org> wrote:

Toggle quote (3 lines)
> Could you take a look at https://issues.guix.gnu.org/67675
> if it fixes it for you?

Since patch#67675 is merged, is it fixed now?

Cheers,
simon
N
N
Nguy?n Gia Phong wrote on 18 Feb 09:33 +0100
(name . Benjamin)(address . benjamin@uvy.fr)
CZ82E559KHXS.ZCUB3RGBOAN6@guix
On 2024-02-15 at 17:18+01:00, Simon Tournier wrote:
Toggle quote (6 lines)
> On mer., 20 déc. 2023 at 16:18, Nguy?n Gia Phong wrote:
> > Could you take a look at https://issues.guix.gnu.org/67675
> > if it fixes it for you?
>
> Since patch#67675 is merged, is it fixed now?

FWIW it is fixed for me d-;
-----BEGIN PGP SIGNATURE-----

iQHIBAABCAAyFiEE6Q4RuASTNDthMuOUJxSLLAaiIksFAmXRwOoUHG1jc2lueXhA
ZGlzcm9vdC5vcmcACgkQJxSLLAaiIkspvgwAlqMTNdeSfkQFVJo3fsAjrugpXsZh
sYcsgRCualijKs5PFR3M9y2lSVnrbtU5BP1f6EW2ylMYp57/IA5gnSKDPZdGo28W
GUvRbPjp519BED0wf9DkwHUoD5KTmJ+NuSQToCFNfAeymmuT9WCc/OiznQN8eMye
/DaMvLmU+gzvMxo9HnwrMlU9ZbPGU43+9wy0kDgAGDE93jF2nF1ahktJ+xzll4xg
+7hu67cTU55xHXmt3w9CpsLbKG12m5UHT6Vj9hG6rNrVLpKAXvPXV9YxzTIAef0D
1MTWn9/gxET7ebya5pGrN5TeeOLrPILuiV9IaKN7uT2zsfz7tJkt7NmT6esl/yzp
IOCzbLytP9RwdLiGYnstJSbrlOLaenYRqey/ZvHvhQGGf7a4h6JJxg4cZr68tZgS
hJregIa/7FFCn/uTcyTyMBI6H7eSyXsEcXowGrSxUYHRynUaE0JnTfRLCFM/NtwI
SwUVs05GUqGqsp0Rm0LM82ZvNRxyiLoBeqxE
=5LaO
-----END PGP SIGNATURE-----


S
S
Simon Tournier wrote on 19 Feb 17:33 +0100
(name . Benjamin)(address . benjamin@uvy.fr)
87zfvw4dnr.fsf@gmail.com
Hi,

On dim., 18 févr. 2024 at 17:33, Nguy?n Gia Phong via Bug reports for GNU Guix <bug-guix@gnu.org> wrote:
Toggle quote (9 lines)
> On 2024-02-15 at 17:18+01:00, Simon Tournier wrote:
>> On mer., 20 déc. 2023 at 16:18, Nguy?n Gia Phong wrote:
>> > Could you take a look at https://issues.guix.gnu.org/67675
>> > if it fixes it for you?
>>
>> Since patch#67675 is merged, is it fixed now?
>
> FWIW it is fixed for me d-;

So closing.

Benjamin, if I am missing something, let me know.

Cheers,
simon
Closed
B
B
Benjamin wrote on 19 Feb 21:44 +0100
CZ9CJQISTC5V.1YLZ8O8WTFKM6@robot.uvy.fr
Hello,

This is fixed on my side too.

This bug can be closed

On Sun Feb 18, 2024 at 9:33 AM CET, Nguy?n Gia Phong wrote:
Toggle quote (8 lines)
> On 2024-02-15 at 17:18+01:00, Simon Tournier wrote:
> > On mer., 20 déc. 2023 at 16:18, Nguy?n Gia Phong wrote:
> > > Could you take a look at https://issues.guix.gnu.org/67675
> > > if it fixes it for you?
> >
> > Since patch#67675 is merged, is it fixed now?
>
> FWIW it is fixed for me d-;
?