I'm using a Python application that accesses a USB device (pipsta printer) and executes a routine. It's running fine outside the container, but when it comes to the container it returns a error like this:
(File "usr/local/lib/python2.7/dist-packages/usb/backend/libusb0.py", line 386, in _check:
raise USBError(errmsg, ret)
USB.core.USBError: [Errno None] couldn't opendir(): No such a file or directory)
In my dockerfile, I've included all the packages relevant to Python and USB, and I also moved the relevant files to /etc/udev/rules.d and restarted udev.
Make sure you:
followed every step from assembly instruction and https://bitbucket.org/ablesystems/pipsta/wiki/Pipsta%20First-Time%20Setup
printer is connected to the power
printer is connected via usb to raspberry
printer's led doesn't blink (should be green constantly)
proper usb library is installed (or try to install different version of the usb library). What version are you using? python: print(usb.__version__) , it works fine for me with version 1.0.0rc1
is printer visible to the os? command: ls /dev/ap1400
I know this is an old question (I've only just encountered it). The following is a paraphrasing of the FAQ. The following steps should help diagnose the problem.
Download the latest set of Pipsta examples..
Extract the contents of the zip file.
Change directory to where the files were extracted
Change directory to the Examples folder.
Using a terminal run the command python verify_pipsta_install.py. This will try and help diagnose problems.
The following will should fix the python usb library error.
If your Pipsta printer firmware is V9.2.03 please upgrade the firmware to V9.2.08 using the fpu (both can be found in the downloads section of bit bucket.
Install the latest version of the Pipsta examples (download from bitbucket).
Copy the new pipsta/Examples/system_scripts/ to /etc/udev/rules.d/60-ablesystems-pyusb.rules
Restart the Raspberry Pi
If the printer still fails to be discovered then -
The following workaround may work.
1. Unplug the printer from the USB port
1. Enter the command sudo lsusb
1. Reconnect the printer
1. Enter the command sudo lsusb
If the printer has been detected by the Linux environment then either /dev/ap1400 or /dev/pipsta should exist in the filesystem.
NOTE The Pipsta now has Debian packages to help with installation. I have a link limit on my account but search for pipsta-printer-utilities-1.1.1-Linux.deb and pipsta-cups-driver-0.3.0-armhf.deb for more information.
Related
im trying to make v4l2loopback work on my desktop PC (no hardware camera) with mint 19.3, kernel 5.4.0-42-generic x86_64.
I followed the official instructions and compiled from git the v4l2loopback module and everything seem to run correctly, as no error prompted while running the instructions, but when i do ll /dev/v* there's no /dev/videoN entry.
I also tried with the flags exclusive_caps=1 and devices=2 but to no avail.
Any idea what i might be missing or doing wrong?
you need to load the module (e.g. using modprobe) before you can use it.
see also https://github.com/umlaeute/v4l2loopback#run
I hope someone out there can help me!
I'm working on a Toshiba SATELLITE-L50-A-1DN, and I am having problems connecting a camera to the USB ports, as well as the integrated webcam not being recognised.
I am using Ubuntu 16.04 with kernel 4.13.0-45-generic
After plugging in an external webcam, lsusb does not change, indicating no device has been recognised.
ls -ltrh /dev/video* returns the error: ls: cannot access '/dev/video*': No such file or directory
I have tried installing uvcvideo, but the most up to date version is already installed. Related to this, I cannot access the Video4Linux module required to use one of the two cameras I am trying to use.
I am aware of the same question being posted here: cannot access /dev/video*: No such file or directory but I can't seem to make that solution work for me.
In dev is there root direct:
my#my-u18gv:~$ cd /dev/video0
If the bellow msg come:
No such file or directory
Then there may be two cases if i found and try to fix:
*
1.) The ubuntu machine or linux machine.
*
There may be various scenario or dependencies which may be causing
this but this what i check on both condition. The the packages and
retart the system
sudo apt-get update
To check the webcamp you can use cheese or any other it depends on
you:
sudo apt-get install cheese
cheese
*
2.) Ubuntu in Virtual Machine running on windows.
*
I'm using ubuntu 18.04, virtual machine 5.2.14 on windows 10 64bit.
Steps:
Open the VM Virtual Box and select the snapshot you are using.
Select the Settings
Select the USB menu at the left
Enable the usb controller and select the USB 2.0 (EHCI) cintroller
Click from USB Device_filter there is a usb cable icon with '+' sign at the right side.
Select your device from the list. In my list it was realtek semiconductor corp.
Here you may face one issue:
while selecting and USB 2.0 and when you start then if you get below error.
failed to install extension pack VERR_SYMBOL_NOT_FOUND ..
Then you need to install VM VirtualBox Extension Pack.
Note: take care that the version of the VM virtualbox and extension package should be same or it might give you error.
Steps: For installing VM VirtualBox Extension Pack
link:https://www.virtualbox.org/wiki/Download_Old_Builds_5_2
For every version you will find the extension package you need in above link.
Open the VM Virtual Box and click on File --> Preferences --> Extensions
Click on Plus icon and Add the extension which you downloaded.
Execute the command:
enter image description here
system error:
[ERROR] [1575905480.653251919]: Unable to identify '/dev/video0': 2, No such file or directory
enter image description here
Answers:
First of all, try your own laptop camera good or bad (do a QQ search, etc...); no problem found
Then review the virtual machine settings. The blue circle has not been opened before and the virtual machine must be turned off for it to be marked;
enter image description here
Reboot, the camera device can now be found in the virtual machine and check "Connect (disconnect from host)".
enter image description here
Re-run the command, the camera can open correctly
enter image description here
I hope it works
I need to install Concourse(CI/CD) on my Local windows machine
Below process I followed :
Install Bosh on local system.
It was successfully install and while executing command at command prompt
then it show version all "bosh" -- "version 3.0.1-712bfd7-2018-03-13T23:26:43Z".
Try Download the concourse-lite deployment manifest file but it fails it shows below error.
Follow the below link to install Concourse :
https://concoursetutorial.com/ --- section For Windows:
I don't reccomend doing this at all because you'll be swimming so far out of the main stream that you'll find tons of issues and no one is going to care enough to want to fix them.
Even if you didn't find any issues, resources require a linux worker for anything to work so your going to need linux anyways.
I recommend running your db, web and linux worker on linux and then running windows workers as needed.
Trying to install swift on my Ubuntu 14.04.3 server. Followed the guide on Swift.org.
download the install package
fetched the gpg keys
verified the .sig file
extracted the file and added the usr/bin subdir to my PATH
However when I try running swift I get "No such file or directory"
Swift seems to be found:
icanzilb#underplot:~/public$ which swift
/home/icanzilb/swift-DEVELOPMENT-SNAPSHOT-2016-01-25-a-ubuntu14.04/usr/bin/swift
Path is correct:
icanzilb#underplot:~/swift-DEVELOPMENT-SNAPSHOT-2016-01-25-a-ubuntu14.04/usr/bin$ echo $PATH
/home/icanzilb/swift-DEVELOPMENT-SNAPSHOT-2016-01-25-a-ubuntu14.04/usr/bin:...
But can't run it:
icanzilb#underplot:~/swift-DEVELOPMENT-SNAPSHOT-2016-01-25-a-ubuntu14.04/usr/bin$ swift
-bash: /home/icanzilb/swift-DEVELOPMENT-SNAPSHOT-2016-01-25-a-ubuntu14.04/usr/bin/swift: No such file or directory
=====
Update 1: I tried the development and stable builds of Swift from swift.org and the .sig checks out but still getting the same error.
Both the swift executable and my Ubuntu are 64 bit.
It really looks like this is a problem of an architecture mismatch, as indicated by one of the commenters, or a corrupted download. The swift executable is in the path and is picked up by which. Judging from the name of the directory where it is located, it is indeed for Ubuntu 14.04. I would try the following:
file `which swift`
This should tell you it is an ELF 64-bit executable, dynamically linked, etc. If that is not the case, you have a corrupted binary somehow.
Then do
uname -a
which should identify your system as Ubuntu 14, x86_64 among other things. If that is the case, you probably have a corrupted binary. Unpack the downloaded package again and retry. If your system is not x86_64, then you are on a wrong architecture.
Update 2/4/2016:
Based on the additional info you provided about the binary and the architecture, I tend to believe this is a platform mismatch. The output of uname doesn't show it is an Ubuntu box. Besides, the Linux kernel is 4.4.0, and the binary is for 2.6.24. I can successfully run the same binary on an Ubuntu 14.04 installation with a 3.19.0 kernel. The kernel version difference is not necessarily a problem in itself, but an indicator that the platform may not be a standard Ubuntu 14.04 install.
As another check, could you please do cat /etc/os-release and cat /etc/lsb-release? Those files should indicate if the platform is indeed Ubuntu. If it is, then I'm wondering how you ended up with this late kernel version. It is possible some other components of the OS are also too recent and incompatible with the Swift binary. This may be some strange custom Linode image... If you have a machine you can use, virtual or physical, try downloading and installing a standard Ubuntu 14.04.
I am currently stuck in deploying an app into into my phone.
The app is part of this tutorial. Everything concerning the main.py and buildozer.spec files is set according this tutorial. The app works just fine when run in Eclipse (though some console "errors").
My phone is a Samsung GT-15500, Android version 2.2. and i am also running an apk installer and kivy launcher.
Additionally inside my phone files /mnt/sdcard i cant find a /kivy directory in order to place my app and a simple text file as mentioned here.
Anyway, the thing is that both in the tutorial and the kivy docs the following command: buildozer android debug deploy run fails into my machine. The given error is produced:
# Android packaging done!
# APK Kivyapp1-1.2.0-debug.apk available in the bin directory
# Run '/home/user/.buildozer/android/platform/android-sdk-21/platform-tools/adb devices'
# Cwd None
/home/user/.buildozer/android/platform/android-sdk-21/platform-tools/adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
# Command failed: /home/user/.buildozer/android/platform/android-sdk-21/platform-tools/adb devices
I am suspecting there has something to do with my ADT and SDK tools, configuration etc.
Any suggestions??
Oh and thanks in advance for your time.!
Edit: I am running a Linux Mint 16 distro
Edit2: corrected main.app to main.py and added info about the error.
Everything concerning the main.app
Just to be clear, you mean main.py right?
My phone is a Samsung GT-15500, Android version 2.2. and i am also running an apk installer and kivy launcher.
Have you tried kivy programs in the kivy launcher? Do they work? Phones old enough to use android 2.2 can sometimes have some graphics driver problems or bugs even if they technically meet the kivy requirements.
This wouldn't affect the buildozer compilation though, it's just another thing.
The given error is produced:
Could you set your log_level to 2 in buildozer.spec (the video covers this), run the build again, and paste the full log here. It isn't possible to debug from that single line.
==============
Edit: Okay, it looks like the apk is actually built correctly, and you should be able to find it in the 'bin' subfolder of wherever you ran buildozer. Assuming that's the case, you can try copying it to your phone some other way (email or whatever should work).
The step that's actually failing is the 'deploy' part that should push the apk to your device. I don't know what the error is, and I've never seen buildozer complain about curses before, though I guess you could check that you have curses installed?
My best suggestion is to investigate by navigating to the directory with adb in and playing with it manually. You can look up the commands, like adb install ... to install an apk to your phone - that's what buildozer tries to do.
You should also check that adb is enabled on your phone.