- Debian: No such file or directory — а файл есть
- Try to run the following command
- fatal error: filesystem: No such file or directory #56
- Comments
- alan-cugler commented May 31, 2019
- My System
- [Errno 2] No such file or directory: ‘ffprobe’: ‘ffprobe’ #404
- Comments
- fantess commented Jul 12, 2019
- Steps to reproduce
- Expected behavior
- Actual behavior
- Your System configuration
- Is there an audio file you can include to help us reproduce?
- BlackLight commented Jul 23, 2019 •
- frozamilan1899 commented Aug 24, 2020
- BlackLight commented Aug 24, 2020 •
- frozamilan1899 commented Aug 25, 2020
- chroot: can’t execute ‘/bin/su’: No such file or directory #938
- Comments
- v-mos commented Apr 2, 2018
- darkt1981 commented Apr 8, 2018
- darkt1981 commented Apr 8, 2018
- v-mos commented Apr 14, 2018
- rarahim75 commented Jul 5, 2020
- istomyang commented Aug 23, 2020
- tarsonis123 commented Jan 11, 2021
- kh000 commented Jan 20, 2021 •
- bitsnaps commented May 13, 2021
Debian: No such file or directory — а файл есть
Здравствуйте, уважаемые. Скачал btsync (у меня arm, по ссылке Linux ARM тут), положил в /usr/bin и не могу запустить:
Как так и что с этим делать?
P.S. Тоже самое происходит, если переместить исполняемый файл, например, в домашний каталог.
P.S.S. Debian Jessie, вот такая железка.
chmod +x точно не поможет?
apparmor, selinux, noexec?
noexec на разделе
такое бывает когда исполняемый файл например предназначенный для 32 битной архитектуры пытаются запустить в 64-битной системе
А что покажет file btsync ? Необязательно на самой железке.
apparmor, selinux, chattr — это что? Что посмотреть?
В общем, похоже-таки несовместимость архитектур. Придётся пересобирать из исходников. Источник: http://otvety.google.ru/otvety/thread?tid=1e74bf1617bdb4b6
Try to run the following command
I had the same issue on Cubieboard.
Try to run the following command:
sudo ln -s /lib/arm-linux-gnueabihf/ld-linux.so.3 /lib/ld-linux.so.3
На Debian 7.6.0 (Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3 x86_64 GNU/Linux) столкнулся с той же проблемой. Для запуска 32-битного приложения может потребоваться пакет ia32-libs-i386. Дебиан по умолчанию не дает его установить из-за зависимостей. Решается таким образом:
sudo dpkg —add-architecture i386 sudo apt-get update sudo apt-get install ia32-libs-i386 (тянет за собой 60Мб зависимостей)
Источник
fatal error: filesystem: No such file or directory #56
Comments
alan-cugler commented May 31, 2019
Hi I am trying to build libloot (and eventually loot) natively on ubuntu 18.04.
I am primarily following this guys guide and have gotten all the dependencies installed.
I ran these commands to get it compiling and I make it past several dependencies before choking.
The Error is as follows:
compilation terminated. CMakeFiles/libloot_internals_tests.dir/build.make:86: recipe for target ‘CMakeFiles/libloot_internals_tests.dir/src/api/api.cpp.o’ failed make[2]: *** [CMakeFiles/libloot_internals_tests.dir/src/api/api.cpp.o] Error 1 CMakeFiles/Makefile2:223: recipe for target ‘CMakeFiles/libloot_internals_tests.dir/all’ failed make[1]: *** [CMakeFiles/libloot_internals_tests.dir/all] Error 2 Makefile:151: recipe for target ‘all’ failed make: *** [all] Error 2 «>
I did attempt to run through the entire repo and replace #include with #include . This did get past the half a dozen identical errors but eventually culminated in a final scroll fest of errors.
So is there a dependency or modification I need to make? Its been a couple years since I’ve done C++ code, but I don’t mind having to brush up for this to run native.
My System
- ubuntu 18.04
- i5 cpu/ 24 Gb RAM
- no errors from listed dependencies
The text was updated successfully, but these errors were encountered:
Источник
[Errno 2] No such file or directory: ‘ffprobe’: ‘ffprobe’ #404
Comments
fantess commented Jul 12, 2019
Steps to reproduce
linux o/s
installed my application under /Documents/
I don’t want to install ffmpeg as I need to upload application to the cloud using Cloud Foundry
I downloaded ffmpeg static binary and unpacked it under ./resources/ffmpeg
In the code, I configured
AudioSegment.converter = ‘./resources/ffmpeg/ffmpeg’
I tried including and excluding the executable
I also tried defining the absolute path to the file
Expected behavior
Then I run
audio = AudioSegment.from_mp3(filename)
Actual behavior
I get this error message:
[Errno 2] No such file or directory: ‘ffprobe’: ‘ffprobe’
It looks like it does not find the path to the executables
Your System configuration
- Python version: 3.7
- Pydub version: 0.23.1
- ffmpeg or avlib?: ffmpeg
- ffmpeg/avlib version: ffmpeg-4.1.4-i686-static.tar.xz
Is there an audio file you can include to help us reproduce?
You can include the audio file in this issue — just put it in a zip file and drag/drop the zip file into the github issue.
The text was updated successfully, but these errors were encountered:
BlackLight commented Jul 23, 2019 •
Are both the statically linked executables for ffmpeg and ffprobe present in your folder?
By default pydub builds the command for subprocess assuming that those executables are present in your PATH . If your executables are not in a PATH folder, then you’ll have to add your resources folder to the PATH environment variable before you launch your script. Overriding AudioSegment.converter in your code won’t probably work: there’s some code in pydub that relies on converter being exactly «ffmpeg» or «avconv». Additionally, a relative path like that won’t make it very robust if you launch your script from another folder.
frozamilan1899 commented Aug 24, 2020
did you solve this problem?
I met the same issue, and if you get any approach, would you please share it with me? Thank you.
BlackLight commented Aug 24, 2020 •
If you look at the logic to get the ffprobe executable you’ll notice that it simply relies on which .
IMHO there are more robust and portable ways to get if an executable is present in PATH (like for example exploring os.environ[‘PATH’] ), but this should be irrelevant for the actual functionality if you run pydub on Linux/MacOS.
Make sure that the ffprobe executable, which comes with ffmpeg , is present somewhere in your PATH . pydub will start working once it can find it.
frozamilan1899 commented Aug 25, 2020
If you look at the logic to get the ffprobe executable you’ll notice that it simply relies on which .
IMHO there are more robust and portable ways to get if an executable is present in PATH (like for example exploring os.environ[‘PATH’] ), but this should be irrelevant for the actual functionality if you run pydub on Linux/MacOS.
Make sure that the ffprobe` executable, which comes with ffmpeg , is present somewhere in your PATH`. pydub will start working once it can find it.
Thank you! It works for me, I fixed it with your approach.
Источник
chroot: can’t execute ‘/bin/su’: No such file or directory #938
Comments
v-mos commented Apr 2, 2018
i try to install kali or debian in my lenovo yoga book intel base device with no luck, i even restored my device for a clean install but i get stuck on that error, i read other similar issues but no one works for me
this is the ouput of the status
[12:41:22] >>> status
[12:41:22] Device: Lenovo YB1-X90F
[12:41:22] Android: 7.1.1
[12:41:22] Architecture: x86_64
[12:41:22] Kernel: 3.14.79-x86_64-g7f80a31
[12:41:22] Memory: 330/3849 MB
[12:41:22] Swap: 0/0 MB
[12:41:22] SELinux: yes
[12:41:22] Loop devices: yes
[12:41:22] Support binfmt_misc: yes
[12:41:22] Supported FS: exfat ext2 ext3 ext4 fuseblk msdos squashfs vfat
[12:41:22] Installed system: unknown
[12:41:22] Status of components:
[12:41:22] ## bootstrap/rootfs : do_status
[12:41:22] ## bootstrap/debian : do_status
[12:41:22] ## core/emulator : do_status
[12:41:22] ## core/motd : do_status
[12:41:22] ## core/hosts : do_status
[12:41:22] ## core/hostname : do_status
[12:41:22] ## core/mnt : do_status
[12:41:22] ## core/net : do_status
[12:41:22] ## core/timezone : do_status
[12:41:22] ## core/su : do_status
[12:41:22] ## core/locale : do_status
[12:41:22] ## core/profile : do_status
[12:41:22] ## core/aid : do_status
[12:41:22] ## core/sudo : do_status
[12:41:22] ## core/unchroot : do_status
[12:41:22] ## core : do_status
[12:41:22] ## bootstrap : do_status
[12:41:22] ## desktop/desktop-base : do_status
[12:41:22] ## extra : do_status
[12:41:22] ## desktop/dbus : do_status
[12:41:22] :: desktop/dbus . stopped
[12:41:22] ## desktop/lxde : do_status
[12:41:22] ## desktop : do_status
[12:41:22] ## extra/ssh : do_status
[12:41:22] :: extra/ssh . stopped
[12:41:22] ## graphics/vnc : do_status
[12:41:22] :: graphics/vnc . stopped
[12:41:22] ## graphics : do_status
[12:41:22] Mounted parts:
[12:41:22] * /
[12:41:22] * /proc
[12:41:22] * /sys
[12:41:22] * /sys/fs/selinux
[12:41:22] * /dev
[12:41:22] * /dev/shm
[12:41:22] * /dev/pts
[12:41:22] Available mount points:
[12:41:22] * /mnt/runtime/default/emulated 47.4/52.0 GB (fuse)
[12:41:22] * /mnt/runtime/read/emulated 47.4/52.0 GB (fuse)
[12:41:22] * /mnt/runtime/write/emulated 47.4/52.0 GB (fuse)
[12:41:22] * /mnt/media_rw/DE81-91D0 0.6/0.6 GB (vfat)
[12:41:22] * /mnt/runtime/default/DE81-91D0 0.6/0.6 GB (fuse)
[12:41:22] * /mnt/runtime/read/DE81-91D0 0.6/0.6 GB (fuse)
[12:41:22] * /mnt/runtime/write/DE81-91D0 0.6/0.6 GB (fuse)
[12:41:22] * /system 0.6/3.6 GB (ext4)
[12:41:22] * /country 0.4/1.0 GB (ext4)
[12:41:22] * /cache 0.2/0.2 GB (ext4)
[12:41:22] * /data 47.4/52.0 GB (ext4)
[12:41:22] * /oem_config 0.0/0.0 GB (ext4)
[12:41:22] * /factory 0.0/0.0 GB (ext4)
[12:41:22] * /sbin/.core/mirror/system 0.6/3.6 GB (ext4)
[12:41:22] * /sbin/.core/db-0/magisk.db 47.4/52.0 GB (ext4)
[12:41:22] * /storage/emulated 47.4/52.0 GB (fuse)
[12:41:22] * /storage/DE81-91D0 0.6/0.6 GB (fuse)
[12:41:22] Available partitions:
[12:41:22] * /dev/block/mmcblk1p1 578 MB (1183744 578M b Win95 FAT32)
[12:41:22] * /dev/block/mmcblk1p2 29 GB (61366272 29.2G 83 Linux)
[12:41:23] >> start
[12:46:06] Checking file system . skip
[12:46:06] Mounting the container:
[12:46:06] / . skip
[12:46:06] /proc . skip
[12:46:06] /sys . skip
[12:46:06] /sys/fs/selinux . skip
[12:46:06] /dev . skip
[12:46:06] /dev/shm . skip
[12:46:06] /dev/pts . skip
[12:46:06] ## bootstrap/rootfs : do_start
[12:46:06] ## bootstrap/debian : do_start
[12:46:06] ## core/emulator : do_start
[12:46:06] ## core/motd : do_start
[12:46:06] ## core/hosts : do_start
[12:46:06] ## core/hostname : do_start
[12:46:06] ## core/mnt : do_start
[12:46:06] :: Configuring core/mnt .
[12:46:06] /data/user/0/ru.meefik.linuxdeploy/bin/linuxdeploy: eval: line 1: can’t create /data/local/mnt/etc/mtab: nonexistent directory
[12:46:06] ## core/net : do_start
[12:46:06] :: Configuring core/net .
[12:46:06] /data/user/0/ru.meefik.linuxdeploy/bin/linuxdeploy: eval: line 1: can’t create /data/local/mnt/etc/resolv.conf: nonexistent directory
[12:46:06] /data/user/0/ru.meefik.linuxdeploy/bin/linuxdeploy: eval: line 1: can’t create /data/local/mnt/etc/resolv.conf: nonexistent directory
[12:46:06] ## core/timezone : do_start
[12:46:06] ## core/su : do_start
[12:46:06] ## core/locale : do_start
[12:46:06] ## core/profile : do_start
[12:46:06] ## core/aid : do_start
[12:46:06] ## core/sudo : do_start
[12:46:06] ## core/unchroot : do_start
[12:46:06] ## core : do_start
[12:46:06] ## bootstrap : do_start
[12:46:06] ## desktop/desktop-base : do_start
[12:46:06] ## extra : do_start
[12:46:06] ## desktop/dbus : do_start
[12:46:06] :: Starting desktop/dbus . chroot: can’t execute ‘/bin/su’: No such file or directory
[12:46:06] fail
[12:46:06] ## desktop/lxde : do_start
[12:46:06] ## desktop : do_start
[12:46:06] ## extra/ssh : do_start
[12:46:06] :: Starting extra/ssh . ls: /data/local/mnt/etc/ssh/: No such file or directory
[12:46:06] chroot: can’t execute ‘/bin/su’: No such file or directory
[12:46:06] chroot: can’t execute ‘/bin/su’: No such file or directory
[12:46:06] fail
[12:46:06] ## graphics/vnc : do_start
[12:46:06] :: Starting graphics/vnc . chroot: can’t execute ‘/bin/su’: No such file or directory
[12:46:06] fail
[12:46:06] ## graphics : do_start
[12:46:06]
The text was updated successfully, but these errors were encountered:
darkt1981 commented Apr 8, 2018
install busybox in /system/xbin
instead of /system/bin.
if that doesnt work change it to one of the other default locations busybox is giving.
that fixed it for me.
darkt1981 commented Apr 8, 2018
also bin/su might be your location seeing its looking there.
v-mos commented Apr 14, 2018
is all ready installed in /system/xbin and not luck
/bin/su doesnt exist, i try to create de directory and install in that directory but for some weard reason thats break the root of my device and now i not sure if i have to restore in order of get root again
is like linux deploy search the busy box in other folder or something like that if any can help me with this i realy apreciate
rarahim75 commented Jul 5, 2020
Hi.. i know this thread is kind of old.. but i am facing this same issue today.. did anyone discover a working solution?
istomyang commented Aug 23, 2020
I try, I fail, and I succeed. maybe the question of Source Path, Try using default path and download by proxy.
I just want to tell you, Repository in Linux deploy is a great place, you can download it and assign path with local storage.
Who say MUST Pay for it? If you have a job, pay for it !
tarsonis123 commented Jan 11, 2021
Any outcome of this? Stuck here since more than a day and nearly tried every combination of settings but still getting this error. There is no ‘bin/su’ on this lineage 14.1. Tried different busy box releases and offers and directories. no luck. Help would be greatly appreciate
kh000 commented Jan 20, 2021 •
I’m testing Linux Deploy on older device with android 4.4 and older version of Linux Deploy 2.0.3-227 .
What worked for me was using debian_arm Debian 10 Buster instead of stretch .
So to select it go to upper left corner menu -> repository -> refresh (upper right corner) and menu -> repository -> select debian_arm -> and import . After that use Image Configuration and set it to your liking. It should have new image called debian_arm selected.
Option 2 — I have not tried it and it might not work (and for obvious reasons it’s a bad advice to begin with :D):
This is coping buster static binary to stretch image on your device.
Another option is to download and copy static su binary and put it into your device to /data/local/mnt/bin (of course after mounting linux,iso )
hub.meefik.ru/rootfs/debian_arm.tgz -> debian_arm.tar\.\usr\bin\su
It might me easer to perform above actions if you select Installation type as directory instead of image. You will not have to mount it to paste su . In that case it probably will be installed to /data/data/ru.meefik.linuxdeploy/env/.
bitsnaps commented May 13, 2021
I got the same issue with a custom ROM BORETS, any workaround?
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Источник