Skip to content

Permission denied panic when trying to install a node version #1412

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

Open
benbarbour opened this issue Apr 15, 2025 · 1 comment
Open

Permission denied panic when trying to install a node version #1412

benbarbour opened this issue Apr 15, 2025 · 1 comment

Comments

@benbarbour
Copy link

benbarbour commented Apr 15, 2025

Getting this error when I try to install.

❯ RUST_BACKTRACE=full fnm install 17.1.0
Installing Node v17.1.0 (x64)
thread 'main' panicked at /home/ben/.local/share/cargo/registry/src/index.crates.io-6f17d22bba15001f/reqwest-0.12.5/src/blocking/client.rs:973:38:
Client::new(): reqwest::Error { kind: Builder, source: Os { code: 13, kind: PermissionDenied, message: "Permission denied" } }
stack backtrace:
   0:     0x56041837f845 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hd736fd5964392270
   1:     0x5604183aa57b - core::fmt::write::hc6043626647b98ea
   2:     0x56041837c17f - std::io::Write::write_fmt::h0d24b3e0473045db
   3:     0x56041837f61e - std::sys_common::backtrace::print::h45eb8174d25a1e76
   4:     0x560418380b59 - std::panicking::default_hook::{{closure}}::haf3f0170eb4f3b53
   5:     0x5604183808fa - std::panicking::default_hook::hb5d3b27aa9f6dcda
   6:     0x560418380ff3 - std::panicking::rust_panic_with_hook::h6b49d59f86ee588c
   7:     0x560418380ed4 - std::panicking::begin_panic_handler::{{closure}}::hd4c2f7ed79b82b70
   8:     0x56041837fd09 - std::sys_common::backtrace::__rust_end_short_backtrace::h2946d6d32d7ea1ad
   9:     0x560418380c07 - rust_begin_unwind
  10:     0x560417fa54b3 - core::panicking::panic_fmt::ha02418e5cd774672
  11:     0x560417fa5946 - core::result::unwrap_failed::h55f86ada3ace5ed2
  12:     0x56041811d008 - reqwest::blocking::client::Client::new::h547e0fcfe16957dc
  13:     0x560417fb5678 - fnm::http::get::hfb692427c87eea45
  14:     0x56041800b603 - fnm::downloader::install_node_dist::hd4671542ba9e9ee3
  15:     0x560417fd4229 - <fnm::commands::install::Install as fnm::commands::command::Command>::apply::hdac1bb9e3f9e6860
  16:     0x560417fd3167 - fnm::commands::command::Command::call::h680747a56967bfdf
  17:     0x560417fc5ee0 - fnm::cli::SubCommand::call::h5842824d1bf0e76b
  18:     0x560417ff6ae9 - fnm::main::h663a8340c83a81f2
  19:     0x5604180100a3 - std::sys_common::backtrace::__rust_begin_short_backtrace::h395daf52855468e1
  20:     0x5604180100b9 - std::rt::lang_start::{{closure}}::h0b063c9adde4a752
  21:     0x56041837473d - std::rt::lang_start_internal::hcee5ed89fc25829a
  22:     0x560417ffc325 - main
  23:     0x7fdf540b21ca - <unknown>
  24:     0x7fdf540b228b - __libc_start_main
  25:     0x560417fa5d05 - _start
  26:                0x0 - <unknown>
@benbarbour
Copy link
Author

Wiping out fnm entirely and reinstalling seems to have resolved the issue.

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

1 participant