Hi All,
I tried to install ANSYS 14.0 on Ubuntu 12.04 LTS. I followed the steps in post #186 by Klinn5 and managed to get WorkBench to run. The problem is I cannot open the mesh editor or the goeometry editor. I get the following error: /usr/ansys_inc/v140/aisol/CommonFiles/linx64/ansyswbu.exe: symbol lookup error: /usr/lib/x86_64-linux-gnu/libXext.so.6: undefined symbol: _XGetRequest Anyone know what this might mean? Thanks! |
I solved by creating a soft link to libc.so.6 under /lib. I have Fluent v13 running on Ubuntu 11 x64.
This is actually what I did: sudo ln -s /lib/x86_64-linux-gnu/libc.so.6 /lib/libc.so.6 When the error message disappears, it shows you info about your processors. So I GUESS it's OK if you don't fix this at all. Cheers! Quote:
|
Reply
I suppose that is also a solution. ANSYS installs its own set of libraries. The problem with libXext.so.6 was that it was referencing a libX11.so.6 library on my system, but ANSYS was pointing to its own version of libX11.so.6.
Just try: ansys_inc/v140/aisol/.workbench -cmd ldd -r /ansys_inc/v140/aisol/dll/linx64/libans.graphics.gstreamcom.so and it will reveal where ANSYS is looking for its libraries. This resulted in the incompatibility. It is however possible to create a soft link to the libX11.so.6.3.0 library on my system and then I don't get the error anymore. (Changing LD_LIBRARY_PATH would also do the job). I managed to run ANSYS WB, but due to slow performance, and what I think to be hardware incompatibility I am now using Windows. Thanks! Louis |
My solution of DesigModeller problem was in adding libraries libXdamage.so.1.0.0 libXfixes.so.3.1.0 libXxf86vm.so.1.0.0
fedora_VBox_system.ova libGL.so.1.2 libXext.so.6.4.0 libXrender.so.1.3.0 and the soft links to them in the form (libXfixes.so.3; libXxf86vm.so.1; etc.) into the following folder: /yourinstallationpath/v140/commonfiles/MainWin/linx64/mw/lib-amd64_linux_optimized (based on this post: http://ubuntuforums.org/showthread.php?t=1361931&page=2) I copied the libraries from CentOS 5.8 installation. This work for me on Fedora 17 with following packages installed after the fresh installation of OS: compat-gcc-34-3.4.6-24.fc17 xorg-x11-fonts-100dpi-7.5-5.fc17 libXp-1.0.0-17.fc17 xterm-278-1.fc17 xorg-x11-fonts-ISO8859-1-75dpi-7.5-5.fc17 xorg-x11-fonts-cyrillic-7.5-5.fc17 libXaw-1.0.9-3.fc17 mesa-libGLw-6.5.1-10.fc17 gcc-objc-4.7.0-5.fc17 compat-libstdc++-33-3.2.3-68.3 gcc-c++-4.7.0-5.fc17 gcc-4.7.0-5.fc17 binutils-2.22.52.0.1-10.fc17 libstdc++-devel-4.7.0-5.fc17 libobjc-4.7.0-5.fc17 ppl-0.11.2-8.fc17 ppl-pwl-0.11.2-8.fc17 glibc-devel-2.15-51.fc17 cloog-ppl-0.15.11-3.fc17.1 kernel-headers-3.4.6-2.fc17 glibc-headers-2.15-51.fc17 cpp-4.7.0-5.fc17 libmpc-0.9-2.fc17.2 Fluent, Workbench and DesignModeller work well. I was successful also on CentOS 5.8 where all worked well almost out of box (installed only packages recommended for Red Hat system in ANSYS docs). Unfortunately I was not able to get it work on my favorite OS openSUSE 12.1. |
1 Attachment(s)
Someone managed to make Design Modeler and Meshing (ANSYS 14) work in Arch Linux?
I've just follow Jura's hint but was unsuccessful. I got the libraries from CentOS 6.3. I ran ansyswbu.exe in strace and Design Modeller and Meshing always get a SEGV at running from Workbench. The output is attached. BTW, I got Design Modeller working in OpenSuse 12.1 running in Virtual Box. I installed libpng12 and the trivial dependencies. Thank you in advance |
Quote:
Can you pls tel me what are all the dependencies you added with ansys, i too tried to install in CENT os 6.3 , i'm getting ccl validation error Vignesh Ram |
Quote:
http://us.download.nvidia.com/XFree8..._64-304.64.run and then copy the content tu /usr/lib in: - libxfixes3_5.0-4_amd64.deb - libxrender1_0.9.6-2_amd64.deb - libxext6_1.3.0-3_amd64.deb from oneiric repo to: /ansys_inc/v140/commonfiles/MainWin/linx64/mw/lib-amd64_linux_optimized/ then make launcher see reference http://ubuntuforums.org/showthread.php?p=11931248 and its all! |
starting design modeler or meshing tool
Hi,
I have MintLinux 13 which is basically Ubuntu 12.04 LTS in 64bit. I did as described above and using the shell script of the resource mentioned in the post before, but when I double click on DesignModeler or MeshingTool they won't start. In the console I get the following error messages: "/ansys_inc/v140/aisol/.workbench: 103: [: x: unexpected operator /usr/ansys_inc/v140/aisol/CommonFiles/linx64/ansyswbu.exe: symbol lookup error: /usr/lib/x86_64-linux-gnu/libXext.so.6: undefined symbol: _XGetRequest /ansys_inc/v140/aisol/.workbench: 103: [: x: unexpected operator /usr/ansys_inc/v140/aisol/CommonFiles/linx64/ansyswbu.exe: symbol lookup error: /usr/lib/x86_64-linux-gnu/libXext.so.6: undefined symbol: _XGetRequest" Can anyone help me to fix this? - Kevin |
ANSYS Design Modeller 14.5 in Ubuntu 12.04
Quote:
Kevin, The _XGetRequest function is a new function in libX11.so. You can check if its on your system using:
setenv LD_LIBRARY_PATH /usr/lib/x86_64-linux-gnu/:$LD_LIBRARY_PATH Ian |
Hi guys!
My Ubuntu console drops the following after running Workbench with the uname26 stuff: QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QObject: Cannot create children for a parent that is in a different thread. (Parent is QApplication(0x1e44080), parent's thread is QThread(0x1ee2060), current thread is QThread(0x7f932c032480) QObject::setParent: Cannot set parent, new parent is in a different thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::setFont: Painter not active QPixmap: It is not safe to use pixmaps outside the GUI thread QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::setFont: Painter not active QPixmap: It is not safe to use pixmaps outside the GUI thread QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::setFont: Painter not active QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread 2013/03/02 08:26:12 ERROR Could not open log file /home/nts/.ansys/local.log. Exiting. Any ideas? :) Thanks Quote:
|
Quote:
ANSYS v14.5 on Ubuntu 12.04. It looks like there's no need to use uname26 or so. Correct me in case I wrong. But at the end of install process I get warning message about errors in "/usr/ansys_inc/install.err" log file: HTML Code:
Revision: 14.5 HTML Code:
./runwb2: 34: ./runwb2: [[: not found |
I changed to CentOS (OpenSource Redhat) and everything works well. Don't use Ubuntu. Check the following document:
http://www.ansys.com/staticassets/AN...ed-summary.pdf I had much less toruble with CentOS than with other platforms. |
OpenSUSE 11.4 . Running Workbench
Code:
System.DllNotFoundException: Ans.QT.dll |
for the error, System.InvalidOperationException: "UNIX OS version 3 is not recognised"
I found this on a Italian blog, in German http://blog.remoteminds.it/setarch-a...on-vorgaukeln/ setarch x86_64 --uname-2.6 /ansys_inc/v140/Framework/bin/Linux64/runwb2 makes it work on fedora 19 Allen |
Hi,
I'm running Ansys 14.5.7 on CentOS 6.4. I'm able to run workbench with the oglmesa option but when i try to start the geometry editor i get an "unable to start geometry editor" error. It doesn't give any other errors besides unable to start geometry editor. I installed the newest version of mesa ( yum install mesa-libGL-devel mesa-libGLU-devel ) but still no progress. When i run workbench without -oglmesa i got the following error: Code:
================================================================= |
ANSYS 14.5 on Suse 12.3
Hi Reignfire,
I'm finding that ANSYS Workbench etc. works out of the box on OpenSuse 12.3 as long as: * I have updated OpenSuse 12.3 since July 2013 because of a bug in libX11 (v1.5.0-4.7.1) and libXext (v1.3.1-4.4.1) that has been now been fixed. * I have install the "lsb", i.e. Linux Standard Base v 2.0. * I have the offical NVIDIA graphics drivers installed and working well. I suspect its similar for Centos. |
Quote:
|
The nearest I can come to testing this is to run Workbench over an "ssh -X" connection to another Suse 12.3 machine.
I can run "glxgears" fine over the ssh tunnel. "runwb2 -oglmesa" works But, Geometry or Mesh won't start. I don't get a helpful error message. |
I also have similar problems. I have running Workbench 13 on both, Linux Mint 15 and Centos 6.4, but I failed with Workbench 14(.5).
I always got messages like: "A fatal error has occurred within AnsysWBU.exe" and "unable to start geometry editor". :mad: |
Bugs in Linux version of ANSYS 14.5.7
I have recently discovered that after getting Ansys Meshing working on Suse 12.3 that there are bugs in the Linux version that are not present in Windows.
For example, the Cut-Cell meshing produces a perfect mesh of 800,000 cells on my cheap windows desktop (2GB RAM, Core 2 Duo E7500, 32bit Windows 2000). But loading the same project file into Workbench running on Suse Linux 12.3 64-bit, on an 8-core E5-2680 with 64GB Ram, the Cut-Cell meshing always fails at the "Transferring mesh" stage. The error suggests its out of memory but that sounds unlikely. Of course, this is on an unsupported Linux so they are not interested in bug reports. |
All times are GMT -4. The time now is 18:49. |