Ubuntu 16.04 64 bit Fusion 8.2 beta won't open

Fusion doesn't run on Ubuntu 16.04 64 bit. if I change to the /opt/Fusion directory and run ./Fusion just get an error about not finding libedit.so.0. my system has libedit.so.2 installed. Fusion never runs just loops through this error non stop.

Fusion doesn't run on Ubuntu 16.04 64 bit. if I change to the /opt/Fusion directory and run ./Fusion just get an error about not finding libedit.so.0. my system has libedit.so.2 installed. Fusion never runs just loops through this error non stop.

as a quick and dirty work around you can uses this command on recent 64bit debian/ubuntu/mint distributions:

Code: Select all

sudo ln -s /usr/lib/x86_64-linux-gnu/libedit.so.2 /usr/lib/x86_64-linux-gnu/libedit.so.0
sudo ldconfig


but it should be fixed by the developers of the application while linking.
but that's the way how beta software helps to fix little annoying bugs and incompatibilities...

That is not not necessarily true. The so called fix means to pretend a newer version of a library is an old one. This is not something that should be done by force during installation. It may work but it may also cause instability (in Fusion or any other application that relies on the library version).

Instead you should rather install the proper version manually (eventually by source) and use a mechanism like LD_LIBRARY_PATH if you do not want to install it next to the other system libraries.

Another alternative is BMD shipped with a fallback library or proper type (it has a license that would allow that).

Like said it really depends on the behavior of the library. If they would be ok with any version they probably rather should link against libedit.so instead of so.0. I assume there is a reasoning. Or not

It is NOT the right way to do it. But the hack it worked for me.
I am using Linux Mint Sarah.
Thanks Martin Schitter

I am also using Ubuntu 16.04 and the hack does not work.

I will not hack my system into thinking a library is an older version just to use a single piece of software. get it fixed and I will try it to evaluate it. I certainly wouldn't buy a piece of software that I was worried would either not function after an upgrade or required system hacks to work properly. I have opted to just not try the software.

I will not hack my system into thinking a library is an older version just to use a single piece of software.

we all do not like this kind of dirty tricks, to work around typical limitations of closed source software.

but you should not overestimate this issue. all software, that comes with your distribution or gets compiled from source, will link to the newer/correct library. you really have to install another stupid commercial black-box and be blessed by a lot of misfortune, to trigger any serious troubles by this workaround.

in fact, this particular library is not used much often in the linux world. there are better free alternatives around. i think, it's only chosen by BMD, because this other well known alternatives are licensed in a more restrictive GNUish tradition.

get it fixed and I will try it to evaluate it. I certainly wouldn't buy a piece of software that I was worried would either not function after an upgrade or required system hacks to work properly. I have opted to just not try the software.

it's always a compromise installing proprietary/unfree software on a well organized linux system.
i usually utilize tools like "checkinstall" to keep the tainting of my systems under control.

the change in the usb hotplug configuration for the protection dongle IMHO should be seen as a much more serious unwanted intervention to your system outside of the /opt-path, than this little library compatibility hack.