Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node not installing on fresh Ubuntu (18.04) install in kvm #48044

Closed
cstpraveen opened this issue May 17, 2023 · 1 comment
Closed

Node not installing on fresh Ubuntu (18.04) install in kvm #48044

cstpraveen opened this issue May 17, 2023 · 1 comment

Comments

@cstpraveen
Copy link

cstpraveen commented May 17, 2023

Version

v16.20.0

Platform

Linux user 4.15.0-210-generic 221-Ubuntu SMP Tue Apr 18 08:32:52 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Subsystem

No response

What steps will reproduce the bug?

Executed below command

$ curl -sL https://deb.nodesource.com/setup_16.x | sudo -E bash -
$ sudo apt-get install -y nodejs

How often does it reproduce? Is there a required condition?

No response

What is the expected behavior? Why is that the expected behavior?

Expected behaviour is to see the npm version, but instead facing error.

What do you see instead?

$ node -v
v16.20.0

$ npm -v
node:buffer:599
    slice: (buf, start, end) => buf.utf8Slice(start, end),
                                    ^

RangeError: Index out of range
    at Object.slice (node:buffer:599:37)
    at Buffer.toString (node:buffer:819:14)
    at Object.readFileSync (node:fs:502:41)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1213:18)
    at Module.load (node:internal/modules/cjs/loader:1074:32)
    at Function.Module._load (node:internal/modules/cjs/loader:909:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:22:47 {
  code: 'ERR_OUT_OF_RANGE'
}

Additional information

No response

@bnoordhuis
Copy link
Member

Duplicate of #33503, #34709, #42215 and possibly more. You're hitting a kvm/qemu bug, not a node bug.

@bnoordhuis bnoordhuis closed this as not planned Won't fix, can't repro, duplicate, stale May 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants