Wine is an open source implementation of the Windows API on top of X and OpenGL.
Fedora's Wine packages are split up to allow for smaller installations. The wine meta package will bring with it the most important components of Wine. Expert users may want to pick specific components from the list below:
|ALSA sound support for wine
|Arial fonts provided by wine-staging
|ISDN support for wine
|Color Management for wine
|Common wine files and scripts
|Wine core package
|Wine Courier font family
|Desktop integration features
|Wine development environment
|Filesystem directories and basic configuration for wine
|Wine Fixedsys font family
|Wine font meta package
|LDAP support for wine
|Wine Marlett font family
|Wine MS Sans Serif font family
|OpenAL sound support for wine
|OpenCL support for wine
|PulseAudio support for wine
|Wine Small font family
|Wine Symbol font family
|Systemd configuration for the wine binfmt handler
|Wine System font family
|SysV initscript for the wine binfmt handler
|Wine Tahoma font family
|Wine Tahoma font family system integration
|Twain (image scanning) support for wine
|Wine Wingdings font family
|Wine Wingdings font family system integration
Additional documentation is provided via the wine-docs package.
Fedora applies fixes and features from the wine-staging project. EPEL packages do not use wine-staging patches.
Current versions of Wine in Fedora:
Newer versions may be available in the corresponding updates-testing repositories.
Bugs and problems
Before reporting bugs against Wine please make sure your system is fully up to date.
Also check if a newer version is available in updates-testing.
dnf --enablerepo=updates-testing update wine
If you are using the proprietary graphics drivers please remove them from your system and try again, as they are known to cause problems.
When debugging Wine, your goal is to determine if the issue is one of code functionality or packaging in Fedora.
Check the Wine Application Database to see if your application is supported, or if there are known issues that match yours. Anything that falls into this category is a bug in upstream code functionality.
The next step is to see if the problem persists with a clean ~/.wine folder. To try this without losing your old configuration:
mv ~/.wine ~/.wine-save
Afterwards try to trigger the bug again. Your original wine folder can be restored with:
rm -fr ~/.wine; mv ~/.wine-save ~/.wine
If your application still does not work but has been working in a previous version of wine it is probably a regression. Consider filling a bug in the upstream Wine-staging bug tracking system. Do not file bugs in the Winehq.org bugzilla unless told to do so.
If you really think that your bug is Fedora-related, file a bug against the Wine component in Fedora's bug tracking system.
If you use the version of wine in the updates-testing repository then please log into bodhi and comment on the build, including any problems that may be in the packaging, naming, or elsewhere. The build needs positive karma to be pushed to the updates repository.