[LouisS]

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!

[lihuang]

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!

Originally Posted by Hìr0

I followed this guide but when I open a case file or msh file I receive this error for each processor:

setting process affinity: failed opening libc

what does it mean? It's important....how do I fix it?

Thank You!!!!

[LouisS]

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

[Jura]

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.

[christianc]

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

[Vigneshramaero]

Originally Posted by ribeiro

Hi Folks

I just installed ANSYS CFX 14 on my CentOS 6.0. I previously installed on dependencies listed in Installation Manual concerning Red Hat 6. NO MORE CCL VALIDATION ERRORS.

I recommend to try that. My computer configuration is as follows:
Notebook Dell Vostro 1310
GeForce 8400 GS (with Nvidia driver 290.10, the latest)
CentOS 6.0 64-bit (with some packages updated due to ANSYS dependencies)

Hope this helps

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

[efirvida]

Originally Posted by LouisS

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 solve this installing the latest nvidia driver
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!

[kevinlipps]

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

[irw]

Originally Posted by kevinlipps

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

Kevin,


The _XGetRequest function is a new function in libX11.so. You can check if its on your system using:

• readelf -s /usr/lib/x86_64-linux-gnu/libX11.so | grep XGetRequest

The requirement for the function is in libXext.so, i.e. there is an UNDefined reference when using:

• readelf -s /usr/lib/x86_64-linux-gnu/libXext.so | grep XGetRequest

To get rid of this error message I had to:

• Upgrade my libx11 packages to v1.50 (https://launchpad.net/ubuntu/+source/libx11)
• I also upgraded my libxext package to v1.3.1 (https://launchpad.net/ubuntu/+source/libxext)

To make sure the libX11 library was loaded when I started workbench I used LD_PRELOAD:

• export LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libX11.so:$LD_PRELOAD; runwb2 -oglmesa

It looks like I'll have to play similar games to get glx (i.e. libGL) working, e.g.:
setenv LD_LIBRARY_PATH /usr/lib/x86_64-linux-gnu/:$LD_LIBRARY_PATH



Ian

[NTSbike]

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

Originally Posted by baosr

I found a way to solve this problem，Ansys WB use "uname" command to determine the kernel version, so just use a script change the "uname" output

/* Copyright (C) 2011 Intel Corporation
Author: Andi Kleen
Set 2.6.x personality

uname26 is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public
License as published by the Free Software Foundation; version
2.

uname26 is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
General Public License for more details.

You should find a copy of v2 of the GNU General Public License somewhere
on your Linux system; if not, write to the Free Software Foundation,
Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA */
#include <sys/personality.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <errno.h>
#include <unistd.h>

#define UNAME26 0x0020000

int main(int ac, char **av)
{
if (!av[1]) {
fprintf(stderr, "Usage: uname26 program ...\n"
"Run program with the uname 2.6 personality\n");
exit(1);
}
if (personality(PER_LINUX | UNAME26) < 0)
perror("personality"), exit(1);

execvp(av[1], av + 1);
fprintf(stderr, "Cannot execute %s: %s\n", av[1], strerror(errno));
exit(1);
}

Paste the red script in a new file"uname26.c".
Compiled with：gcc -o uname26 uname26.c
run WB by: ./uname26 /ansys_inc/v140/Framework/bin/Linux64/runwb2
Then we can run WB in a kernel 3.* linux.

[dr-kart]

Originally Posted by irw

Kevin,
...To make sure the libX11 library was loaded when I started workbench I used LD_PRELOAD:

• export LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libX11.so:$LD_PRELOAD; runwb2 -oglmesa

It looks like I'll have to play similar games to get glx (i.e. libGL) working, e.g.:
setenv LD_LIBRARY_PATH /usr/lib/x86_64-linux-gnu/:$LD_LIBRARY_PATH

Ian

Still don't understand what to do

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:

Revision: 14.5
   /usr/ansys_inc/v145/aisol/.workbench: 103: [: x: unexpected operator
   /usr/ansys_inc/v145/aisol/.workbench: 103: [: x: unexpected operator
   /usr/ansys_inc/v145/aisol/.workbench: 103: [: x: unexpected operator
   /usr/ansys_inc/v145/aisol/.workbench: 103: [: x: unexpected operator
   /usr/ansys_inc/v145/aisol/.workbench: 103: [: x: unexpected operator
   /usr/ansys_inc/v145/commonfiles/configs/linx64/config/AnsConfigWB.sh:  152: [:  /usr/ansys_inc/v145/aisol/dll/linx64/libans.common.clrhostmonou.so:  unexpected operator
   /usr/ansys_inc/v145/aisol/.workbench: 103: [: x: unexpected operator
   /usr/ansys_inc/v145/commonfiles/configs/linx64/config/AnsConfigWB.sh:  152: [:  /usr/ansys_inc/v145/aisol/dll/linx64/libans.common.controlsu.so:  unexpected operator
   /usr/ansys_inc/v145/aisol/.workbench: 103: [: x: unexpected operator
   /usr/ansys_inc/v145/commonfiles/configs/linx64/config/AnsConfigWB.sh:  152: [:  /usr/ansys_inc/v145/aisol/dll/linx64/libans.graphics.controlsu.so:  unexpected operator
   /usr/ansys_inc/v145/aisol/.workbench: 103: [: x: unexpected operator
   /usr/ansys_inc/v145/commonfiles/configs/linx64/config/AnsConfigWB.sh:  152: [:  /usr/ansys_inc/v145/aisol/dll/linx64/libans.graphics.graphutilityu.so:  unexpected operator
   /usr/ansys_inc/v145/aisol/.workbench: 103: [: x: unexpected operator
   /usr/ansys_inc/v145/commonfiles/configs/linx64/config/AnsConfigWB.sh:  152: [: /usr/ansys_inc/v145/aisol/dll/linx64/*ud.so: unexpected  operator
   /usr/ansys_inc/v145/commonfiles/configs/linx64/config/AnsConfigWB.sh:  152: [: /usr/ansys_inc/v145/aisol/dll/linx64/*ud.so: unexpected  operator
   /usr/ansys_inc/v145/aisol/.workbench: 103: [: x: unexpected operator
   /usr/ansys_inc/v145/commonfiles/configs/linx64/config/AnsConfigWB.sh:  152: [: /usr/ansys_inc/v145/aisol/dll/linx64/*ud.so: unexpected  operator
   /usr/ansys_inc/v145/aisol/.workbench: 103: [: x: unexpected operator
   /usr/ansys_inc/v145/commonfiles/configs/linx64/config/AnsConfigWB.sh:  152: [: /usr/ansys_inc/v145/aisol/dll/linx64/*ud.so: unexpected  operator
   /usr/ansys_inc/v145/aisol/.workbench: 103: [: x: unexpected operator
   /usr/ansys_inc/v145/commonfiles/configs/linx64/config/AnsConfigWB.sh:  152: [: /usr/ansys_inc/v145/aisol/dll/linx64/*ud.so: unexpected  operator
   /usr/ansys_inc/v145/aisol/.workbench: 103: [: x: unexpected operator
   /usr/ansys_inc/v145/commonfiles/configs/linx64/config/AnsConfigWB.sh:  152: [: /usr/ansys_inc/v145/aisol/dll/linx64/*ud.so: unexpected  operator
   /usr/ansys_inc/v145/aisol/.workbench: 103: [: x: unexpected operator
   /usr/ansys_inc/v145/commonfiles/configs/linx64/config/AnsConfigWB.sh:  152: [: /usr/ansys_inc/v145/aisol/dll/linx64/*ud.so: unexpected  operator
   /usr/ansys_inc/v145/aisol/.workbench: 103: [: x: unexpected operator
   /usr/ansys_inc/v145/commonfiles/configs/linx64/config/AnsConfigWB.sh:  152: [: /usr/ansys_inc/v145/aisol/dll/linx64/*ud.so: unexpected  operator
   /usr/ansys_inc/v145/aisol/.workbench: 103: [: x: unexpected operator
   /usr/ansys_inc/v145/commonfiles/configs/linx64/config/AnsConfigWB.sh:  152: [: /usr/ansys_inc/v145/aisol/dll/linx64/*ud.so: unexpected  operator
   /usr/ansys_inc/v145/aisol/.workbench: 103: [: x: unexpected operator
   ###### Error #######
   Error executing configuration script '/usr/ansys_inc/v145/commonfiles/configs/linx64/config/AnsConfigRSM.sh'
    '"/usr/ansys_inc/v145/commonfiles/configs/linx64/config/AnsConfigRSM.sh"   -installdir "/usr/ansys_inc" -rev 145 -scripttosource  "/usr/ansys_inc/v145/commonfiles/configs/linx64/config/ConfigCommon.tcl"  -sourcedir "/tmp/ans_install_tmp12181" -os_lang en-us -install'  terminated after 1 attempts with the following error(s):
       Unknown error
   readlink: invalid option -- 'p'
   Try `readlink --help' for more information.
   dirname: missing operand
   Try `dirname --help' for more information.
   dirname: missing operand
   Try `dirname --help' for more information.
   dirname: missing operand
   Try `dirname --help' for more information.
   dirname: missing operand
   Try `dirname --help' for more information.
   dirname: missing operand
   Try `dirname --help' for more information.
   /usr/ansys_inc/v145/RSM/Config/tools/linux/rsmconfig: 26:  /usr/ansys_inc/v145/RSM/Config/tools/linux/rsmconfig:  /Framework/bin/Linux64/runwb2: not found

And running "sudo ./runwb2" gives this:

./runwb2: 34: ./runwb2: [[: not found
/usr/ansys_inc/v145/aisol/.workbench: 103: [: x: unexpected operator

[NTSbike]

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.

[dr-kart]

OpenSUSE 11.4 . Running Workbench

System.DllNotFoundException: Ans.QT.dll
  at (wrapper managed-to-native) Ansys.UI.Toolkit.QTC.Application:new_ans_qt_Application ()
  at Ansys.UI.Toolkit.QT.Application..ctor () [0x00000] in <filename unknown>:0 
  at Ansys.UI.Toolkit.QT.UIFactory.newApplication () [0x00000] in <filename unknown>:0 
  at Ansys.UI.Toolkit.UIFactory.newApplication () [0x00000] in <filename unknown>:0 
  at Ansys.UI.Toolkit.Application.InstantiateIApplication () [0x00000] in <filename unknown>:0 
  at Ansys.UI.Toolkit.Application..cctor () [0x00000] in <filename unknown>:0 
--- System.TypeInitializationException: An exception was thrown by the type initializer for Ansys.UI.Toolkit.Application
  at Ansys.UI.UIManager..ctor () [0x00000] in <filename unknown>:0 
  at Ansys.UI.UIManager.get_Instance () [0x00000] in <filename unknown>:0 
  at Ans.Program.Runtime.InitializeSplashScreen () [0x00000] in <filename unknown>:0 
  at Ans.Program.Runtime.Initialize (Ans.Program.RuntimeSettings settings) [0x00000] in <filename unknown>:0 
  at Ans.Program.Executable.Run (Ans.Program.CommandLineParse parser) [0x00000] in <filename unknown>:0 
  at Ans.Program.Executable.Main (System.String[] args) [0x00000] in <filename unknown>:0

Help

[allen-cts]

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

[Reignfire]

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:

=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.
=================================================================

./runwb2: line 244: 11923 Aborted                 (core dumped) $MONO_PREFIX/bin/mono $WBII_ROOT/Framework/bin/$ARCH/AnsysFW.exe $WBIIINTARGS

What can i do to fix this?

[irw]

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.

[Reignfire]

Originally Posted by irw

Hi Reignfire,

I'm finding that ANSYS Workbench etc. works out of the box on Suse 12.3 as long as:
* I have updated Suse 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.

And what if the server doesn't have a NVIDIA graphics card?

[irw]

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.

[Jenne]

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".

[irw]

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.