Permission Denied (os error 13) | Bevy | Page 1

fossil magnet Nov 28, 2023, 9:28 PM

#

I am doing 3 things and getting a permission denied error.
cargo new bevy-chess
cd bevy-chess
cargo run
This all works fine. It's only after I add bevy as a dependency that I start having problems.
cargo add bevy
cargo run

thread 'main' panicked at /home/ashensilverwolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/alsa-sys-0.3.1/build.rs:13:18:
  Failed to run command `PKG_CONFIG_ALLOW_SYSTEM_CFLAGS="1" PKG_CONFIG_ALLOW_SYSTEM_LIBS="1" "pkg-config" "--libs" "--cflags" "alsa"`, because: Permission denied (os error 13)
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...

Not sure what would be causing this, as I'm not using sudo commands at any point.
Any help would be appreciated.

#

rustup 1.26.0 (5af9b9484 2023-04-05)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active `rustc` version is `rustc 1.76.0-nightly (49b3924bd 2023-11-27)`

woeful token Nov 28, 2023, 9:45 PM

#

what does it say if you run

RUST_BACKTRACE=1 cargo run

fossil magnet Nov 28, 2023, 9:47 PM

#

  --- stderr
  thread 'main' panicked at /home/ashensilverwolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/libudev-sys-0.1.4/build.rs:38:41:
  called `Result::unwrap()` on an `Err` value: "Failed to run command `PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=\"1\" PKG_CONFIG_ALLOW_SYSTEM_LIBS=\"1\" \"pkg-config\" \"--libs\" \"--cflags\" \"libudev\"`, because: Permission denied (os error 13)"
  stack backtrace:
     0: rust_begin_unwind
               at /rustc/49b3924bd4a34d3cf9c37b74120fba78d9712ab8/library/std/src/panicking.rs:645:5
     1: core::panicking::panic_fmt
               at /rustc/49b3924bd4a34d3cf9c37b74120fba78d9712ab8/library/core/src/panicking.rs:72:14
     2: core::result::unwrap_failed
               at /rustc/49b3924bd4a34d3cf9c37b74120fba78d9712ab8/library/core/src/result.rs:1649:5
     3: core::result::Result<T,E>::unwrap
     4: build_script_build::main
     5: core::ops::function::FnOnce::call_once
  note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

#

and if you want full, here:

📎 message.txt

woeful token Nov 28, 2023, 9:52 PM

#

I'm not sure why this would happen when adding Bevy an a dependency since I never had to write

sudo cargo run

I wonder, are you using Windows with WSL2?

fossil magnet Nov 28, 2023, 9:55 PM

#

Correct

woeful token Nov 28, 2023, 9:56 PM

#

Might be that it is trying to install a dependency for Bevy and needs root access to do that. I say that based on a cursory scan of this article:
https://bevy-cheatbook.github.io/platforms/windows/wsl2.html

Working in WSL2 - Unofficial Bevy Cheat Book

fossil magnet Nov 28, 2023, 9:57 PM

#

Interesting

#

I'll try on another machine that's using native linux and see what happens

#

That breaks too.

#

It's running Linux Mint.
I followed the same order of operations that I did above.
It isn't a permission error, but is mentioning the same package; alsa.

fossil magnet Nov 28, 2023, 10:29 PM

#

Just spun up a VM using Kali, got the same problem.

#

alsa seems to be the common denominator here.

woeful token Nov 28, 2023, 11:20 PM

#

If you install alsa does it work?

fossil magnet Nov 28, 2023, 11:21 PM

#

Good question

#

I don't even know how I would install it

#

There's obviously the crate for alsa, but that's a library, not a tool or anything that can be "installed".

#

other resources are pointing to it being the "Advanced Linux Sound Architecture", which sounds like a driver

#

https://www.alsa-project.org/wiki/Main_Page

Main Page

woeful token Nov 28, 2023, 11:25 PM

#

I never heard of it before but it looks like its something that is part of the linux kernel so shouldn't need installation

#

https://wiki.archlinux.org/title/Advanced_Linux_Sound_Architecture

Advanced Linux Sound Architecture

fossil magnet Nov 28, 2023, 11:26 PM

#

I dunno if this is the problem though.
The "Permission Denied (os error 13)" was my original reason for posting here.
The alsa conspiracy only came up after testing on other platforms.

woeful token Nov 28, 2023, 11:27 PM

#

what if you run the original command with sudo

fossil magnet Nov 28, 2023, 11:27 PM

#

I suppose I could try it

#

sudo cargo run

woeful token Nov 28, 2023, 11:27 PM

#

yeah

fossil magnet Nov 28, 2023, 11:27 PM

#

I'll let you know how it goes, it's gonna take a while

#

fetching is already gonna be a minute or two

#

well this is funky

woeful token Nov 28, 2023, 11:31 PM

#

aha

fossil magnet Nov 28, 2023, 11:31 PM

#

i've got nothing for this

woeful token Nov 28, 2023, 11:31 PM

#

update rustc

fossil magnet Nov 28, 2023, 11:31 PM

#

it's on 1.76 nightly

woeful token Nov 28, 2023, 11:32 PM

#

oh yeah I see

fossil magnet Nov 28, 2023, 11:32 PM

#

hence why I'm confused lol

woeful token Nov 28, 2023, 11:32 PM

#

maybe delete lock file

#

shot in the dark

fossil magnet Nov 28, 2023, 11:33 PM

#

negative, chief

woeful token Nov 28, 2023, 11:33 PM

#

maybe there is the rustc version for windows and the rustc version for WSL2 and its using the wrong one

fossil magnet Nov 28, 2023, 11:34 PM

#

wait...

#

lemme wipe previous rustup installs, I might've borked something earlier

#

weirder problem

#

I uninstalled rust via rustup self uninstall, as instructed

#

now i'm reinstalling

#

#

i hate when problems become more problematic

woeful token Nov 28, 2023, 11:37 PM

#

what happens if you check the rust version in powershell?

fossil magnet Nov 28, 2023, 11:38 PM

#

doesn't exist

#

rustc : The term 'rustc' is not recognized as the name of a cmdlet, function, script file, or operable program.

#

rustc -V

woeful token Nov 28, 2023, 11:39 PM

#

is there anything in the folder ~/.cargo/bin

#

in wsl

fossil magnet Nov 28, 2023, 11:40 PM

#

.cargo/ does not exist as a directory within my user directory

woeful token Nov 28, 2023, 11:40 PM

#

the page also mentions "During installation rustup will attempt to configure the PATH. Because of differences between platforms, command shells, and bugs in rustup, the modifications to PATH may not take effect until the console is restarted, or the user is logged out, or it may not succeed at all.

If, after installation, running rustc --version in the console fails, this is the most likely reason."

fossil magnet Nov 28, 2023, 11:41 PM

#

that...

woeful token Nov 28, 2023, 11:41 PM

#

I wonder if uninstalling also would require a restart

fossil magnet Nov 28, 2023, 11:41 PM

#

good question

#

nope, still complaining

#

still a fair question

woeful token Nov 28, 2023, 11:43 PM

#

what is inside /usr/bin since that is where the error message says the existing installation of Rust is

#

Also found this thread, if you scroll down a bit theres a post with 30 upvotes that might have a solution

#

https://github.com/rust-lang/rustup/issues/953

GitHub

Can't install rustup because of existing rust that I can't remove ·...

We have a copy of rustc version 1.14.0 installed on my school's server. I want to set up the latest version of rust (currently 1.15.1) in my home directory, ideally using rustup. But because of...

fossil magnet Nov 28, 2023, 11:45 PM

#

rust-clang, rust-lld, rust-llvm-dwp, rustc*, and cargo*

woeful token Nov 28, 2023, 11:45 PM

#

if the github thread post doesn't fix it maybe delete all those folders

fossil magnet Nov 28, 2023, 11:48 PM

#

pretty sure that issue was just to add the warning

#

warning: it looks like you have an existing installation of Rust at:
warning: /usr/bin
warning: It is recommended that rustup be the primary Rust installation.
warning: Otherwise you may have confusion unless you are careful with your PATH
warning: If you are sure that you want both rustup and your already installed Rust
warning: then please reply `y' or `yes' or set RUSTUP_INIT_SKIP_PATH_CHECK to yes
warning: or pass `-y' to ignore all ignorable checks.
error: cannot install while Rust is installed

#

cleared the files/folders in question

#

not complaining

woeful token Nov 28, 2023, 11:51 PM

#

nice

fossil magnet Nov 28, 2023, 11:51 PM

#

cargo run still complaining about permissions

#

trying sudo

#

  --- stderr
  thread 'main' panicked at 'Could not run `PKG_CONFIG_ALLOW_SYSTEM_CFLAGS="1" PKG_CONFIG_ALLOW_SYSTEM_LIBS="1" "pkg-config" "--libs" "--cflags" "alsa"`
  The pkg-config command could not be found.

  Most likely, you need to install a pkg-config package for your OS.
  Try `apt install pkg-config`, or `yum install pkg-config`,
  or `pkg install pkg-config`, or `apk add pkgconfig` depending on your distribution.

  If you've already installed it, ensure the pkg-config command is one of the
  directories in the PATH environment variable.

  If you did not expect this build to link to a pre-installed system library,
  then check documentation of the alsa-sys crate for an option to
  build the library from source, or disable features or dependencies
  that require pkg-config.', /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/alsa-sys-0.3.1/build.rs:13:18
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

#

back to alsa

#

this is now the same problem I had on Mint and Kali native systems

woeful token Nov 28, 2023, 11:53 PM

#

apt install pkg-config

#

assuming thats ubuntu

#

from the color of the terminal

fossil magnet Nov 28, 2023, 11:53 PM

#

correct

#


  --- stderr
  thread 'main' panicked at '`PKG_CONFIG_ALLOW_SYSTEM_CFLAGS="1" PKG_CONFIG_ALLOW_SYSTEM_LIBS="1" "pkg-config" "--libs" "--cflags" "alsa"` did not exit successfully: exit status: 1
  error: could not find system library 'alsa' required by the 'alsa-sys' crate

  --- stderr
  Package alsa was not found in the pkg-config search path.
  Perhaps you should add the directory containing `alsa.pc'
  to the PKG_CONFIG_PATH environment variable
  No package 'alsa' found
  ', /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/alsa-sys-0.3.1/build.rs:13:18
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

#

and we're back to square one

woeful token Nov 28, 2023, 11:55 PM

#

maybe this one: https://askubuntu.com/questions/1396181/package-alsa-was-not-found-in-the-pkg-config-search-path-perhaps-you-should-add

Ask Ubuntu

Package alsa was not found in the pkg-config search path. Perhaps y...

im having problems with bevy framework.
sorry im new at this site and idk how to make my question more "readable"
Full exit code when i try to run:cargo run --example hello_world

I tried

fossil magnet Nov 28, 2023, 11:57 PM

#

pray for me

#

it worked

#

still refuses to cooperate when running w/o sudo

#

but it's something

woeful token Nov 28, 2023, 11:59 PM

#

did it compile?

fossil magnet Nov 28, 2023, 11:59 PM

#

yes

#

still need to address the original issue, which is permission

#

but thanks for helping me get this far in the first place

woeful token Nov 29, 2023, 12:00 AM

#

no worries

fossil magnet Nov 29, 2023, 12:01 AM

#

anything you have for the perms?

woeful token Nov 29, 2023, 12:01 AM

#

I'm not really sure why it wants permissions, was the permissions a problem on Kali or Mint or just the alsa thing?

fossil magnet Nov 29, 2023, 12:02 AM

#

permissions (so far) has only been a WSL thing

woeful token Nov 29, 2023, 12:04 AM

#

guessing this one might be relevant: https://stackoverflow.com/questions/50586535/make-rustc-cargo-rustup-rustdoc-commands-work-without-sudo-inside-the-windows

Stack Overflow

Make rustc, cargo, rustup, rustdoc commands work without sudo insid...

I'm running a WSL Debian distro because I wanted to follow along with the InterMezzOS tutorials. I followed the installation instructions for Rust and ran curl https://sh.rustup.rs -sSf | sh, but I...

fossil magnet Nov 29, 2023, 12:05 AM

#

fossil magnet permissions (so far) has only been a WSL thing

confirmed, it's only a WSL thing. Kali worked fine with the previous steps to account for alsa.

fossil magnet Nov 29, 2023, 12:08 AM

#

woeful token guessing this one might be relevant: https://stackoverflow.com/questions/5058653...

I don't know why it worked, but it did

#Permission Denied (os error 13)