Please note, we do semi-regular testing with Fedora but even with that testing, we cannot hope to cover everything here. The following instructions are provided as a guildeline to get CrossOver running, your mileage may vary.
Before attempting to install CrossOver 14.1 we brought the system up to date. In terminal:
sudo yum update
With CrossOver 14.1, installation should be simplified. If any libraries are missing, CrossOver will now prompt the user to install them on first launch.
Versions prior to CrossOver 14.1
If manually installing from the terminal, first installing the following packages should resolve most dependency issues: sudo yum install glibc.i686 zlib.i686 libgcc.i686 libICE.i686 libSM.i686 libX11.i686 libXext.i686 libXi.i686 freetype.i686 cups-libs.i686 alsa-lib.i686 mesa-libGL.i686 libXrandr.i686 dbus-libs.i686 fontconfig.i686 mesa-libGLU.i686 libgphoto2.i686 gsm.i686 libjpeg-turbo.i686 openldap.i686 lcms2.i686 openal-soft.i686 libpng.i686 sane-backends-libs.i686 libXcomposite.i686 libXcursor.i686 libXinerama.i686 libxml2.i686 libxslt.i686 openssl-libs.i686 nss-mdns.i686 libgcc.i686 libXext.i686 libv4l.i686 isdn4k-utils.i686 gstreamer-plugins-base.i686 mesa-libOSMesa.i686 gnutls.i686 alsa-plugins-pulseaudio.i686
These are some of the issues we know of with Fedora and CrossOver.
Accented Characters do not work
Accent characters do not work in applications run via CrossOver but work in native applications like Open Office. These characters include but are not limited to:
è ñ ê é á
This is not a regression. It is a new behavior for ibus introduced in Fedora 20. With that version, the workaround was to turn off ibus. With Fedora 21, turning off ibus is no longer a straight forward process. At this time we have a temporary workaround that must be done on each launch of an affected application.
with thanks to Ludovic for assistance in testing and refining these solutions
In terminal, launch the application with an environment variable that turns ibus modifiers off. Give the command:
XMODIFIERS="@im-none" /opt/cxoffice/bin/wine --bottle $BOTTLENAME --cx-app $EXECUTABLE.exe
For Microsoft Word, the command would be:
XMODIFIERS="@im-none" /opt/cxoffice/bin/wine --bottle Microsoft_Office_2007 --cx-app winword.exe
For Microsoft Outlook, a more defined command is needed:
It is possible to modify the launcher for each individual application to reflect the above. The launchers are located at:
Open the specific launcher with a text editor, it should look like this: #!/bin/sh
exec "/opt/cxoffice/bin/wine" --bottle "Microsoft_Office_2007" --check --wait-children --start "C:/users/crossover/Start Menu/Programs/Microsoft Office/Microsoft Outlook 2007.lnk" "$@"
Modify it to look like this: #!/bin/sh
XMODIFIERS="" exec "/opt/cxoffice/bin/wine" --bottle "Microsoft_Office_2007" --check --wait-children --start "C:/users/crossover/Start Menu/Programs/Microsoft Office/Microsoft Office Outlook 2007.lnk" "$@"
We are researching a better solution. For reference, this is bug number 11871.
We're rebels. We're misfits. But mostly, we're software liberators. And we're very, very good at what we do. We have to be. Lots of developers work with open source, but only a tiny fraction of those are good enough to get software that was designed for one platform to work on another one. We invented CrossOver software - a unique approach to cross-platform compatibility that does not require dual-boot or another OS license. We launched PortJump to help app and game developers broaden their market beyond Windows® users. And we launched ExecMode to help organizations solve really ugly technical challenges.