Adding Image, Camera or DepthCloud as a display type causes rviz to core dump #696
Comments
|
Is this still the case with |
|
I'm not sure. Unfortunately, I'm not in a position to try it out right now. Thanks for responding! On Wed, Feb 12, 2014 at 5:39 PM, William Woodall
Lynn Coddington Gilbert |
|
I have a similar issue with ROS Indigo (running on 32 bit Ubuntu 14.04). I run on a fairly old laptop and use gl software rendering (LIBGL_ALWAYS_SOFTWARE=1). The steps to reproduce are exactly the same as above. However, the stack trace shows a slightly different behavior (see below). It looks like rviz is using Qt4 and trying to load some plugin which is linked against Qt5. And rviz: Qt4 and Qt5 are not allowed to be loaded in the same process, as far as I know. I did install the official ros package (ros-indigo-desktop-full). Any help would be much appreciated. |
|
@whoenig I believe this is an entirely different issue. But, on my machine (Trusty 64-bit) I don't have link entries for But |
|
I have the same problem: as soon as I open a camera or image display in rviz, it segfaults (Ubuntu 14.04). I tried pulling the latest version from github, same problem. I also see a mixup of Qt 4 and 5 when running the gdb stack trace. |
|
I am facing the same problem with rviz (ROS Inidgo) on x64 Ubuntu 14.04. I too observed the Qt4 , Qt5 mixup in the gdb backtrace. |
|
Perhaps having Qt5 installed is enough to have it link against the wrong library at runtime, can any of you try uninstalling Qt5 and running it again? I don't have my Trusty machine handy. |
|
You can't uninstall Qt5 on Ubuntu 14.04, a lot of things depend on it, including unity and bits of ros: |
|
@lorenzoriano that must be some indirect dependency, as far as I know the rqt packages shouldn't directly depend on qt5. I'd have to dig into the dependency structure, but I don't have a trusty machine handy. I'll look into it after the holidays. |
|
@lorenzoriano exactly which package did you try to uninstall to get that message? |
|
Everything with qt5, something like sudo apt-get uninstall libqt5* (don't have a linux box with me know, can't check the exact command) |
|
I have solved the problem(at least on my machine). I am running Ubuntu 14.04 and ROS Indigo on a x64 machine. In my case, I had built Qt5.3.2 from source and OpenCV 2.4.9 from source with Qt support on AND the OpenCV libraries were built against Qt5. Here is what I did:
Then I tried adding views for camera, depthmap and pointcloud2 (with kinect) it all worked fine! No segfaults. I am not totally sure if rviz uses OpenCV libraries for the Camera interface. It could be possible to solve this problem by just uninstalling Qt5 (and building ROS again if it was built from source) as @wjwwood suggested. |
|
Thanks @praveenofpersia, it works! The only difference is that I had to disable Qt support in OpenCV. I saw no option in ccmake to selectively enable QT4 rather than QT5, and cmake kept choosing QT5 by default (even after installing qt4-default). Maybe this issue can be closed? I still see no solution for other users here, and I don't know what to blame (OpenCV? RViz? Qt?). This is an annoying and hard to find bug, and there should be at least a warning when multiple versions of Qt are being mixed. |
|
@lorenzoriano it is also not clear to me which project is to blame, but since disabling Qt support in OpenCV seems to address the issue, I would guess it might be that OpenCV is pullingin Qt5 incorrectly in this case. @vrabaud do you have any insight on this? Maybe it would be possible to roll an |
|
@lorenzoriano : Glad that you got your problem solved. But It's strange why/how Cmake picks up Qt5's qmake when qt4-default is installed. For anybody who are facing the same issue and are unable to solve it using the information above, the following pointers might help: If none of the above works, you can try using a different Cmake version (2.x like 2.8). |
|
I found that some problems with libPythonQt.so could be causing the issues, so try and sourcing the original file, rather than any other you might have. |
I think we can safely say rviz2 is no longer alpha. This change adds in the current version from the package.xml, though this is likely to lag behind when a new release is made. I'm not quite sure how to improve that. While we are in here, also switch from the "ROS 2.0" nomenclature to just "ROS 2". Signed-off-by: Chris Lalancette <clalancette@openrobotics.org>
When I attempt to add an Image, Camera or DepthCloud as a display type, rviz core dumps immediately.
Steps to Recreate
32 bit Ubuntu 12.04 LTS
ROS Groovy
RVIZ opens
Click Add to add a new Display Type.
Select Camera and click OK
Results in the following output
Same happens if I select Image or DepthCloud as well.
Here is the output from the debugger:
I did upgrade
ros-groovy-class-loaderand it still core dumps.Any help would be much appreciated.
The text was updated successfully, but these errors were encountered: