guix pull command fails on a torified bash shell

  • Open
  • quality assurance status badge
Details
2 participants
  • Girish
  • Maxime Devos
Owner
unassigned
Submitted by
Girish
Severity
normal
G
G
Girish wrote on 19 Jan 2022 16:47
(address . bug-guix@gnu.org)
5c1158fb-305d-a5ff-4d16-8d03e9e18eba@posteo.net
When I run `guix pull` command the following error is generated:

In procedure scm_lreadr: #<unknown port>:16:144: Unknown # object: #\<

Further invocations to `guix <option>` produces Segmentation fault.

However, the following command still works:

`/run/current-system/profile/bin/guix <option>`
M
M
Maxime Devos wrote on 20 Jan 2022 11:04
eea482bab1257fc83b8426eb3488672b6f49dcd0.camel@telenet.be
Girish schreef op wo 19-01-2022 om 15:47 [+0000]:
Toggle quote (4 lines)
> When I run `guix pull` command the following error is generated:
>
> In procedure scm_lreadr: #<unknown port>:16:144: Unknown # object: #\<

Does it only print that, or is there also some backtrace?
To investigate the issue, the backtrace would be useful.

Greetings
Maxime.
-----BEGIN PGP SIGNATURE-----

iI0EABYKADUWIQTB8z7iDFKP233XAR9J4+4iGRcl7gUCYekzuBccbWF4aW1lZGV2
b3NAdGVsZW5ldC5iZQAKCRBJ4+4iGRcl7gRxAQCFnCQShB4CZkKmtMYWK7+GM1po
B7b9uLN1OOKIoXVetAD/Uom2xH5PNuQX0DWgv3D8AfxyTX/6FJEYwrUIK6jD6w8=
=HnMj
-----END PGP SIGNATURE-----


M
M
Maxime Devos wrote on 21 Jan 2022 10:49
(name . Girish)(address . girishm@posteo.net)(address . 53369@debbugs.gnu.org)
9c5f0f9eea5f2adb56c16ed0f86d98816fd1e563.camel@telenet.be
[Please keep debbugs in CC or To]

Toggle quote (2 lines)
>  guix pull command fails on a torified bash shell

Does it also happen outside a torified shell?
torify sets LD_PRELOAD, which is rather fragile ...
E.g., if torify comes from a foreign distro and guix comes from guix,
then quite possibly there's some kind of binary incompatibility in-
between.

Anyway, torify probably doesn't do what you want it to do, because the
substitutes and most source code is downloaded through the guix daemon,
which is probably not torified. I recommend setting the 'http_proxy'
and 'https_proxy' environment variables instead (for the daemon and
user), although there might be some situations in which they are not
respected.

Girish schreef op vr 21-01-2022 om 08:54 [+0000]:
Toggle quote (1 lines)
> Actually, it prints 'Segmentation fault' when I run `guix pull`.
Maybe look in 'dmesg' to see if there was an out-of-memory situation.

Toggle quote (7 lines)
> When I run `/run/current-system/profile/bin/guix pull` it runs fine
> but ends with following exception:
> ice-9/boot-9.scm:1669:16: In procedure raise-exception:
> In procedure scm_lreadr: #<unknown port>:16:144: Unknown # object #\<
> I'm not sure whether the above details are enough.
> How can I view the complete backtrace for `guix`?

Normally, the backtrace is printed automatically, looking like
something along these lines:

Toggle quote (18 lines)
> Backtrace:
> In ice-9/boot-9.scm:
> 1752:10 6 (with-exception-handler _ _ #:unwind? _ # _)
> In unknown file:
> 5 (apply-smob/0 #<thunk 7f1cc976d080>)
> In ice-9/boot-9.scm:
> 724:2 4 (call-with-prompt _ _ #<procedure default-prompt-
> handle…>)
> In ice-9/eval.scm:
> 619:8 3 (_ #(#(#<directory (guile-user) 7f1cc9773c80>)))
> In ice-9/boot-9.scm:
> 2835:4 2 (save-module-excursion _)
> 4380:12 1 (_)
> In $HOME/source-code/rw/guix/q.scm:
> 1:1 0 (_)
>
> $HOME/source-code/rw/guix/q.scm:1:1: Unbound variable: foo

Basically, the backtrace starts at the 'Backtrace:' line.
But it seems like it was not printed in your case ...

Greetings
Maxime.
-----BEGIN PGP SIGNATURE-----

iI0EABYKADUWIQTB8z7iDFKP233XAR9J4+4iGRcl7gUCYeqBjxccbWF4aW1lZGV2
b3NAdGVsZW5ldC5iZQAKCRBJ4+4iGRcl7kh7AQCUyU1oTVixG7nESArnEriR/pLK
LyeOEcW/68gDOfMzoQEAlnadg2X5MaoGmQuVkDpZI5+pN/gYlN5wT92R9KtfkQs=
=fh73
-----END PGP SIGNATURE-----


?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 53369@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 53369
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch