Could not open the space navigator device. Did you remember to run spacenavd (as root)? - ros

I am running the demo MoveIt Servoing,I am using the following commands
1. roslaunch ur_gazebo ur5.launch
2. roslaunch ur5_moveit_config ur5_moveit_planning_execution.launch sim:=true
3. roslaunch ur5_moveit_config moveit_rviz.launch config:=true
After running the following command
4. roslaunch moveit_servo spacenav_cpp.launch
I am getting the following error Could not open the space navigator device. Did you remember to run spacenavd (as root)? I tried resolving the issue using the [website Link Solution], however I am getting the following error
root#abc-ThinkPad-P17-Gen-2i:/home/abc/ws_moveit# rosrun spacenav spacenavd
Command 'rosrun' not found, but can be installed with:
apt install rosbash
root#abc-ThinkPad-P17-Gen-2i:/home/abc/ws_moveit# sudo apt install rosbash
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
rosbash : Depends: catkin but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
root#abc-ThinkPad-P17-Gen-2i:/home/abc/ws_moveit#
I am using Ubuntu 20.04 and ROS Noetic

Related

yocto populate_sdk has lots of warnings: package is not installable

I'm using yocto 2.6 (thud) to customize my linux image and now I can use bitbake to generate an image with my own applications, the image runs well on the board.
Now I'm trying to populate the sdk and I do:
bitbake dey-image -c populate_sdk
then I have lots of warnings, like
The following packages have unmet dependencies:
apt-dev : Depends: apt (= 1.2.24-r0.1) but it is not going to be installed
Recommends: bash-dev
Recommends: libcurl-dev but it is not installable
hwmoniter-dev : Depends: hwmoniter (= git-r0.7) but it is not going to be installed
Recommends: libmosquitto1-dev but it is not installable
E: Unable to correct problems, you have held broken packages.
Summary: There was 1 WARNING message shown.
It seems that populate_sdk finally succeeded with warnings, the sdk (*.sh) is generate and it can be installed, but I can't find many header files I assumed to be there.
So what do the warnings mean? What's the difference between "not going to be installed" and "not installable"? How can I fix those warnings?
Thanks

Appium) Finishing setting up optional dependencies

First of all, below is required information.
OS: macOS Mojave 10.14.2
Node: 10.13.0
AndroidStudio: 3.1.4
When I run appium doctor, I'am getting two optional dependencies are missing.
1. `opencv4nodejs`
2. `bundletool.jar`
If I try to install opencv4nodejs, but I got warning:
opencv4nodejs#4.14.0 has no binaries
(It seems like auto build failed)
And I have no idea how to add export bundletool.jar as PATH.
I just ran into this myself. Installing opencv4nodejs was pretty easy - for that, I used:
npm -g install opencv4nodejs
There may have been dependencies of 'opencv4nodejs' that I had to install - I can't remember; that may have required me to install 'make' with brew install make
The hard one was the bundletool.jar - here are the steps I followed for that:
Searched for 'bundletool.jar' and found a place to download it from Google - I got 'bundletool-all-0.8.0.jar' from https://github.com/google/bundletool/releases
I renamed this file to just 'bundletool.jar' and placed in my Android SDK folder, under its own sub-folder called 'bundle-tool' - full path: /Users/{USER}/Library/Developer/Android/sdk/bundle-tool
I had to make the bundletool.jar executable with:
chmod +x bundletool.jar
Added the 'bundle-tool' folder to Path with the following addition in my ~/.bashrc file:
PATH="$PATH:$ANDROID_HOME/bundle-tool"
Now running which 'bundletool.jar' is happy and finds it in the 'bundle-tool' folder I created (see step 2)
Running 'appium-doctor' is now satisfied - and doesn't report any missing dependencies.
Hope that helps.
2019-10-31 update:
With MacOS Catalina (specifically 10.15.1) - I ran into a problem with installing opencv4nodejs using the npm command shown above. Opencv4nodejs wants to be built - but using C++ 11 features (from what I read) and has a problem with constexpr on MacOS. So, I first installed OpenCV with Brew - using brew install opencv#4 and then had to set the environment variable to not autobuild OpenCV with export OPENCV4NODEJS_DISABLE_AUTOBUILD=1
Then I was able to install opencv4nodejs with the npm command shown above - and appium-doctor shows that its dependencies are in place.

Erlang installation giving erlang-mode is broken error

I am trying to install Elixir from the elixir website on Ubuntu 14.04. I get the following error when I execute $ sudo apt-get install esl-erlang. Can anyone help me out here ?
$ sudo apt-get install esl-erlang
Reading package lists... Done
Building dependency tree
Reading state information... Done
esl-erlang is already the newest version.
The following packages were automatically installed and are no longer required:
libgconf2-4 python-requests-whl python-setuptools-whl python-six-whl
python-urllib3-whl python-wheel
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 406 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up erlang-mode (1:21.0.5-1) ...
ERROR: erlang-mode is broken - called emacs-package-install as a new-style add-on, but has no compat file.
Install emacsen-common for emacs23
emacsen-common: Handling install of emacsen flavor emacs23
Wrote /etc/emacs23/site-start.d/00debian-vars.elc
Wrote /usr/share/emacs23/site-lisp/debian-startup.elc
Install emacsen-common for emacs24
emacsen-common: Handling install of emacsen flavor emacs24
Wrote /etc/emacs24/site-start.d/00debian-vars.elc
Wrote /usr/share/emacs24/site-lisp/debian-startup.elc
Install erlang-mode for emacs
Install erlang-mode for emacs23
install/erlang: Handling install for emacsen flavor emacs23
Wrote /usr/share/emacs23/site-lisp/erlang/erlang-edoc.elc
Wrote /usr/share/emacs23/site-lisp/erlang/erlang-eunit.elc
Wrote /usr/share/emacs23/site-lisp/erlang/erlang-flymake.elc
Wrote /usr/share/emacs23/site-lisp/erlang/erlang-skels-old.elc
Wrote /usr/share/emacs23/site-lisp/erlang/erlang-skels.elc
Wrote /usr/share/emacs23/site-lisp/erlang/erlang-start.elc
Wrote /usr/share/emacs23/site-lisp/erlang/erlang.elc
Wrote /usr/share/emacs23/site-lisp/erlang/erlang_appwiz.elc
In toplevel form:
erldoc.el:64:1:Error: Cannot open load file: cl-lib
Wrote /usr/share/emacs23/site-lisp/erlang/path.elc
ERROR: install script from erlang-mode package failed
dpkg: error processing package erlang-mode (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
erlang-mode
E: Sub-process /usr/bin/dpkg returned an error code (1)
Thanks
I don't know what is causing your errors, but you could try ASDF with the Elixir plugin. This allows you to install multiple versions of Elixir and its dependencies, and uses your user environment with shims instead of installing to system directories. This avoids many of the dependency and permission problems that comes with performing a single system-level installation.
It looks like you have both emacs23 and emacs24 installed. The failure is happening when trying to build for emacs23. Unless you really want emacs23 for some reason, remove it and then it should install fine:
sudo apt-get remove emacs23
It is possible you might have to delete some of the other emacs23-* packages by hand.
This problem only affects the erlang-mode package, which adds support for editing Erlang code in Emacs. If you're not using Emacs (or not developing Erlang in it), you can just uninstall that package:
sudo apt remove erlang-mode
As noted in Penguin Brian's answer, this happens when installing erlang-mode on a system using Emacs 23, as erlang-mode only supports Emacs 24 or newer. (Looks like this is a bug in the package: it shouldn't try to compile itself for unsupported Emacs versions.) If you do want to use erlang-mode in Emacs, I'd suggest running Emacs 24 and installing the Erlang mode from MELPA.

EEXIST 17 error while installing opencv using conda on windows

I am trying to install opencv using conda on a windows machine. I am running the following command:
conda install --channel https://conda.anaconda.org/menpo opencv
and getting the following error:
Solving environment: done
## Package Plan ##
environment location: C:\ProgramData\Anaconda2
added / updated specs:
- opencv
The following NEW packages will be INSTALLED:
opencv: 2.4.11-py27_1 menpo
Proceed ([y]/n)? y
Preparing transaction: done
Verifying transaction: done
Executing transaction: - WARNING conda.gateways.disk:exp_backoff_fn(49):
Uncaught backoff with errno EEXIST 17
failed
ERROR conda.core.link:_execute(502): An error occurred while installing
package 'None'.
IOError(13, 'Permission denied')
Attempting to roll back.
Rolling back transaction: done
IOError(13, 'Permission denied')
WindowsError(183, 'Cannot create a file when that file already exists')
Other people seem to have similar problems (https://github.com/conda/conda/issues/4393). One of the solutions I found was to downgrade conda. I am currently using conda 4.5.4 and when I try to downgrade using conda install conda=4.2 I get the following error:
The following packages will be DOWNGRADED:
conda: 4.5.4-py27_0 --> 4.2.16-py27_0
conda-build: 3.10.5-py27_0 --> 3.9.2-py27_0
Proceed ([y]/n)? y
Preparing transaction: done
Verifying transaction: done
Executing transaction: failed
ERROR conda.core.link:_execute(502): An error occurred while uninstalling
package 'defaults::conda-build-3.10.5-py27_0'.
WindowsError(5, 'Access is denied')
Attempting to roll back.
Rolling back transaction: done
WindowsError(5, 'Access is denied')
Regarding this issue I found the following similar posts:
conda update conda permission error
Anaconda : Update conda failed because permission error
But the solutions given do not fix my problem.
I also had a problem with installation and usage of the OpenCV library. If you have such а problem, you can try:
uninstall opencv with: conda remove --yes opencv (in case you have an installation but it does not work properly)
install OpenCV through pip: pip install opencv-python
I think this is a problem with opencv that comes from Anaconda channels. I came across this problem four months ago. Тhe problem may be resolved right now.
My guess is that you did not run this command with administrator privileges!

I can't run the "perf" command. Perf is a linux profiler for stack traces

Trying to use the perf profiler. I've installed linux generic tools, but no luck. Here is the message I'm getting:
r#r-K55A:~$ perf
WARNING: perf not found for kernel 3.16.0-45
You may need to install the following packages for this specific kernel:
linux-tools-3.16.0-45-generic
linux-cloud-tools-3.16.0-45-generic
You may also want to install one of the following packages to keep up to date:
linux-tools-generic
linux-cloud-tools-generic
I've tried to install the above packages, but I get the following error:
Unable to locate package linux-tools-3.16.0-45-generic
E: Couldn't find any package by regex 'linux-tools-3.16.0-45-generic'
You can safely use this snippet:
sudo apt install linux-tools-common linux-tools-generic linux-tools-$(uname -r)
I could never get it working. Updated my Kernal to newest stable version and tried to download the above packages from sudo apt-get install. I finally found the packages manually online, and it's working fine.

Resources