nix-channel error: opening pseudoterminal master: No such device

  • Open
  • quality assurance status badge
Details
7 participants
  • Zhu Zihao
  • Collin J. Doering
  • jgart
  • Nathan Dehnel
  • Haider
  • Jonas Schneider-Bensch
  • worldofgeese
Owner
unassigned
Submitted by
Nathan Dehnel
Severity
normal
Blocked by
N
N
Nathan Dehnel wrote on 17 May 2023 06:44
(name . bug-guix)(address . bug-guix@gnu.org)
CAEEhgEu0pROeYvYf8ZoGsaY=j-cPW+qmj4QUFvckWQfqFJehRw@mail.gmail.com
I recently started getting this error:

$ nix-channel --update
unpacking channels...
error: opening pseudoterminal master: No such device
error: program '/gnu/store/77sxsc9awh98pg4y1iab195adls6bbm8-nix-2.5.1/bin/nix-env'
failed with exit code 1

should I report this to nix instead?

tried running it in xfce-terminal and in a TTY
using the nix shepherd service
guix version c8e599b
H
H
Haider wrote on 4 Jun 2023 17:50
(address . 63546@debbugs.gnu.org)
CWXP123MB34945B2C7DBDEAFAC8BEDB60874CA@CWXP123MB3494.GBRP123.PROD.OUTLOOK.COM
Just here to state that I am also getting this error whilst using the
nix shepherd service. (I'm on an up-to-date guix system).
-----BEGIN PGP SIGNATURE-----

iQJPBAEBCAA5FiEElYQvYw0BTcD9RTvS66+xVw8ubSsFAmR8stQbHHBhcmFsbGUx
ZXBpcGVkQG91dGxvb2suY29tAAoJEOuvsVcPLm0rYEEP/28RJsP2D9hFOAS90kjc
aO0UPH36gNk1pqzK1D4xMcLA8qGeT7YOLP4Diz+HOSVG469Cxj/daNxP/cGTRWZN
mpWmTRtoIMGPRbVvr39EX8R7WqAEuO3XSa2KPwlcLhtzecrLGoZxQVU/LiiSsLV4
unbl6rc2bt+oxMrcFgI0oJ/JyzLTdl1DGbxeGl9SfU768N0sRkByNQ4ttAlfVobg
CtPYOt+81RdfDrmsLCMS1GE9JWVUtc0+4ypIDKS1zrbeVJEmZgWukgMS5P/jP1bk
ELHVQn4uHacXsvAQWxM65gJLlEf+GD2fkKQiWc21JMIxg7dMfXABHxacmAIvx6y5
rth3Ox8oepiHZfeSBf16NxeczykEDEyKzEuCoG13zbUkGtz+6SHj83h0EFHidTy2
ITtJ8qWs+ZlW/Fm0zIoZ13Tqfb5vEb7gH28hJw22iw3gZPRUq6Y4i//ISzVjpkFH
5xLX8OdnvC87GEcc5wR7uCSxLRMhrn8pvo9A2dZxfekNVOuNYOlQqmbE4l39yfxy
dN+mXJfUm6HQ7OTMPIerXx1098KFihhpjp6gMvnEJL9TcXwJUuG5touqAqpi7u7d
EJDYvRIrfzghiGMD8G6pxTqn35fwKuiBJFEtl1MfTmZPU6cev/kCDrZ4wBGqj82T
n/+87hj5mvINjbcaBTxplqho
=rrtU
-----END PGP SIGNATURE-----


Z
Z
Zhu Zihao wrote on 6 Jun 2023 18:09
(address . 63546@debbugs.gnu.org)
86mt1clgir.fsf@163.com
You can have a look at

which solves the problem.
--
Retrieve my PGP public key:

gpg --recv-keys B3EBC086AB0EBC0F45E0B4D433DB374BCEE4D9DC

Zihao
-----BEGIN PGP SIGNATURE-----

iIsEARYIADMWIQT4UAIrVkIEZilSHr2K2nJqP6LM8gUCZH9aHBUcYWxsX2J1dF9s
YXN0QDE2My5jb20ACgkQitpyaj+izPKyuAD/VmeiINEevhhk4dBrCZCPWPP2T+DP
92P676k82KVr6FMBAO9B18hKUuMZ+Z3+1Ar277sNC94FvdLUDc5nZ7E5GyoD
=cPVR
-----END PGP SIGNATURE-----

H
H
Haider wrote on 7 Jun 2023 22:03
Re: Nix-channel error
(address . 63546@debbugs.gnu.org)
CWXP123MB3494AD0389337742645B80B28753A@CWXP123MB3494.GBRP123.PROD.OUTLOOK.COM
Thank you Zihao, I did notice the patch at the time but I didn't assume
that it had fixed the issue.

I will stay patient for when it will be pushed upstream. Thank you for
your efforts.

Regards,
Haider Mirza
-----BEGIN PGP SIGNATURE-----

iQJPBAEBCAA5FiEElYQvYw0BTcD9RTvS66+xVw8ubSsFAmSA4o8bHHBhcmFsbGUx
ZXBpcGVkQG91dGxvb2suY29tAAoJEOuvsVcPLm0rKH0P/0LbB2hP9SiJVo3jzVGv
UQG62Xb5UuUcpbR1Y8RjJCGkMS4mItJWU0VNXZuWDgjlRX0NeAOFZe8jZ2vDbCfH
xfrhz6gvXLQ9SvyoAdZrFik48ywUvVgXcW92Ny0pPAdKmc338bPBTBUtzo/2jrLS
MkvOKmY+mS1sKUReWfHMlaKJU8rN87jbarzMxg7TL52d++TvwEq9qe1RVL2halLI
y7GQvlqSpjwahKtiMN3oNiMOxsAaHLPoXA7dek8FaZ/M2eFjwDh6NyB3BlNB/DyA
u5wcDWMvDo9ZEVGg2nk3x+KnBTatxRd+fbOmO1SCnkoJj0Bhv4pskIHLmeo9hBnL
iNMfB5nvFhFMv3YwRlNAJn+1fdooF9Ma80A3CIn+onFq2++YWJE8N0Zs4kOl4/AO
Fu/iKp9OVVqEKb8Rqf1/ra+5bC7OFQkUfSlEk3C+t3qF3+lhsO9+Mew45oFsCfxC
I9cq997/mUsR79vgJE80EgErEimHKYkttWfkYJaxs0HBrGycZm9R08qCDMO4VsSA
NmlLhnhSnnRDOIAOKzvkYLIOeo1E4JpbsPRucjOrwbLIwylOYdg9mSms6Xi4ENUI
NHtILc0ozQ1Q8zrD97+OKVqXn5IIKg9QXs8J/Dw0WsUJUA0DF8T4MliHjoKnsbqX
3KY4Uo+YhLVRrhMpbeDr2K3b
=QPUw
-----END PGP SIGNATURE-----


W
W
worldofgeese wrote on 23 Jun 2023 09:55
(No Subject)
(name . 63546@debbugs.gnu.org)(address . 63546@debbugs.gnu.org)
PZaQAiE8KDJVOmFexeaf6CJ2ItXUVvKFZYP_f2fa7Z7960SR9e6UzMi__kBlyzuyzMqunNI-SanjLNQliXYIxQHqaY-2t0a2GdTAD8qOGM8=@proton.me
I'm still receiving the same error. I tested a variant of Zhu's patch by defining my own custom Nix package that sticks very closely to Zhu's, just with manpages and docs generation disabled. I can confirm Nix is running latest: nix (Nix) 2.16.0.

This is the first time I've done any kind of Guix hacking so it's a bit rough. Here's my custom Nix package.

(define-public my-nix
(package
(inherit nix)
(name "nix")
(version "2.16.0")
(inputs (modify-inputs (package-inputs nix)
(append rapidcheck nlohmann-json)))
(source
(origin
(method git-fetch)
(uri (git-reference
(commit version)))
(file-name (git-file-name name version))
(sha256
(base32 "0jizpci4zspqpqqy3n780m4wh8dzhfywaiz953xv70c7in810dra"))))
(arguments
`(#:configure-flags '("--disable-doc-gen")
#:phases
(modify-phases %standard-phases
(replace 'check
(lambda args
;; Some tests expect environment variable NIX_STORE to be
;; "/nix/store"
(let ((original-NIX_STORE (getenv "NIX_STORE")))
(dynamic-wind
(lambda ()
(setenv "NIX_STORE" "/nix/store"))
(lambda ()
(apply (assoc-ref %standard-phases 'check) args))
(lambda ()
(setenv "NIX_STORE" original-NIX_STORE)))))))))))

Attempting to run devbox shell returns

Error: Command: /run/current-system/profile/bin/nix print-dev-env /home/worldofgeese/Downloads/projects/little_bits_of_buddha/.devbox/gen/flake/flake.nix --extra-experimental-features ca-derivations --option experimental-features nix-command flakes --json: exit status 1

[DEBUG] 2023/06/23 09:38:50 go.jetpack.io/devbox/internal/boxcli/midcobra/debug.go:72: Command stderr: path '/home/worldofgeese/Downloads/projects/little_bits_of_buddha/.devbox/gen/flake/flake.nix' does not contain a 'flake.nix', searching up
warning: Git tree '/home/worldofgeese/Downloads/projects/little_bits_of_buddha/.devbox/gen/flake' is dirty
error: opening pseudoterminal master: No such device.

Devbox is a Nix package available from the Nixpkgs repositories intended for local development using Nix flakes.
J
J
Jonas Schneider-Bensch wrote on 24 Jun 2023 08:54
nix-channel error: opening pseudoterminal master: No such device
(address . 63546@debbugs.gnu.org)
CAHA-Oa1ufKQak2AGCdfKQ=hBCyowEZe=ZfkEa=TTzVDSC=R-iA@mail.gmail.com
Perhaps this is a permissions issue with the nix shepherd service? I
haven't tried the patch linked above, but found that I could run

$ sudo nix-channel --update

without running into the issue. Then, I got the same error again when
trying to install any package with nix-env. Once again, I could run

$ sudo nix-env -i <some-package>

which would successfully install it to the root profile. After doing
this, however, I found that I now could run

$ nix-env -i <some-package>

to install the package to my user profile, presumably because the nix
store was populated by the run with sudo.
Attachment: file
J
Re: [PATCH v3 2/2] gnu: nix: Update to 2.16.1.
(address . control@debbugs.gnu.org)(address . control@debbugs.gnu.org)
5b326a51bbfee6d23f23689c92ae928a@dismail.de
block 63546 by 63893
C
C
Collin J. Doering wrote on 27 Jun 2023 17:00
nix-channel error: opening pseudoterminal master: No such device
(address . 63546@debbugs.gnu.org)
87edlxj6ek.fsf@rekahsoft.ca
For What Its Worth (fwiw): I found that restarting the nix-daemon shepherd service makes this issue go away for me.

Not sure what is the underlying cause, but thought I'd mention it for others.

Kind regards,

--
Collin J. Doering

-----BEGIN PGP SIGNATURE-----

iQFIBAEBCAAyFiEE+NVG868371PRtki+e03rkyErMCIFAmSa+dMUHGNvbGxpbkBy
ZWthaHNvZnQuY2EACgkQe03rkyErMCKD+ggAlnwRehUv2zyLIjkYbd80BJooerxw
X4BZZUiWCRarF+vwCR43MI7JSR02arE90NvvXPPGulARbZP1UQoF6QkJSkMT7BV/
YywF3Wl82ZWww1gLwOm0P0IO36bEyQ5px2jXqFhVNdqoLEKoTbJAKfXXOwtGpGjF
eRnaGpwUljJd3P7YdDAeI24YPi6TF+KJvpHLXNNnGiX4vzzqyUwAOm5cl6mnB5Jt
TcBjtG8D26btNsbV3hOIQmH9bG+LxJvoxMOebwQ3trct2pKUj3bKY5vl1k/Dd7aH
xRFs6NkAgD4Wb7FbaFbfj2aDy/Ai1ns1jb/vdX8ZxdtW9Ea2UF9kwdE0Pw==
=82J9
-----END PGP SIGNATURE-----

H
H
Haider wrote on 1 Jul 2023 11:54
/gnu/store/6wv8x4115jykg58fdgcjfka12vp2vms6-glibc-for-fhs-2.35/lib
(address . 63546@debbugs.gnu.org)
CWXP123MB34940F66EBC849A11CF8A092872BA@CWXP123MB3494.GBRP123.PROD.OUTLOOK.COM
Wow, thank you for the tempoary workaround.

It's quite obscure that it works though.
-----BEGIN PGP SIGNATURE-----

iQJPBAEBCAA5FiEElYQvYw0BTcD9RTvS66+xVw8ubSsFAmSf97gbHHBhcmFsbGUx
ZXBpcGVkQG91dGxvb2suY29tAAoJEOuvsVcPLm0rlqgP/AsJ2TwYfc+Ct/D0/lKJ
ittOg+IjrIbK5KvxUSIthMRhJixltqqnbjAy9etd0LX3J0I3FW+sxu78Z2YWnlO7
lekOQpulSaJylHZrD1VQCtIJubhpf+ApFDuvf6HJEJm7d3wvWHW89TkhQ8C1N701
OVJEkCN1sEfN3NW9lkxj3b9IMmwM3Dfzo2r14AajfNQd0M/Sj2rkpHUI6wDxhgPS
kywVgYVpHGW000uwy/plnXv4b5jTBEmsIRgrSfAew4JrT8hCYY60Ow8t+dAhfZvL
59CBvU7dCB0UCNqgJRKd/OybH5c5amsf1MjV1TDL5N3AEJ6GmJdtp7QFoxNndJTa
3BoxOAVTVCEC68xP2qARU6GGbCO89EFzh1jtTXog/xSj/e2xrTmMXBcdlU1LaI1a
HvurjrhfpyYisfCoV23rpeMALEU9YGeCbjk0lwThQaBGA3bld4i8zFlFHCE/FQiA
A2AeaiLCX6MQnUUZ6vUMR+0HTy+p9fPl4USIYp8zeT8HFj3FApzeGbM6pPyZzDdK
bw1g/+EBG9UzfSS5nA/e01t+ZZrVhVq8ZUlhiiRd5Jv+5zMNx4jSyO7kr3f4THbH
Au724ZoOlwd9cxHx6+7P8tk4j1jYiOSkt5BF6zXaMn5pPD2aOz2zH75tFX9lEit+
AiHpAY8qpao4Mql+euToLCK7
=qIDq
-----END PGP SIGNATURE-----


?
Your comment

Commenting via the web interface is currently disabled.

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

To respond to this issue using the mumi CLI, first switch to it
mumi current 63546
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