What is wine-compholio?

The Wine "Compholio" Edition is a special patched version of Wine that includes both patches written by our team directly and specific patches by third party developers that we consider good enough for inclusion. This can be seen as a testing version in preparation for patches to be submitted to upstream Wine - don't be surprised if you encounter additional bugs, which are not present in regular wine, and always report such issues to us (via github), so we can improve our fixes even further. Thanks!

Included bugfixes and improvements

Wine-compholio contains fixes for the following Wine bugs:

• ATL IOCS data should not be stored in GWLP_USERDATA (Wine Bug #21767)
• Add Dynamic DST exceptions for Israel Standard Time (Wine Bug #36374)
• Add implementation of WTSEnumerateProcessesW (Wine Bug #29903)
• Allow special characters in pipe names. (Wine Bug #28995)
• Chromium unit test fails in DecryptMessage (Wine Bug #20748)
• Create AppData\LocalLow directory inside the profile directory (Wine Bug #22896)
• Create Saved Games directory inside the profile directory (Wine Bug #28312)
• Fix for ConnectNamedPort return value in overlapped mode (Wine Bug #16550)
• Fix race conditions and deadlocks in strmbase/quartz (Wine Bug #31566)
• GetSecurityInfo returns NULL DACL for process object (Wine Bug #15980)
• Implement a Microsoft Yahei replacement font (Wine Bug #13829)
• Implement an Arial replacement font (Wine Bug #32323)
• Need for Speed 3 installer requires devices in HKEY_DYN_DATA (Wine Bug #7115)
• Return correct IMediaSeeking stream positions in quartz (Wine Bug #23174)
• SHCreateSessionKey not implemented (Wine Bug #35630)
• Support for AllocateAndGetTcpExTableFromStack (Wine Bug #34372)
• Support for GetSystemTimes (Wine Bug #19813)
• Support for Junction Points (Wine Bug #12401)
• Support for PulseAudio backend for audio (Wine Bug #10495)
• Support for TransmitFile (Wine Bug #5048)
• Support for [Get|Set]SystemFileCacheSize (Wine Bug #35886)
• Support for inherited file ACLs (Wine Bug #34406)
• Support for interface change notifications (Wine Bug #32328)
• Support for process ACLs (Wine Bug #22006)
• Support for stored file ACLs (Wine Bug #31858)
• Support for ws2_32.inet_pton (Wine Bug #36713)
• Workaround for TransactNamedPipe not being supported (Wine Bug #17273)

Besides that the following additional changes are included:

• Add default ACLs for user shell folders
• Add support for Dynamic DST (daylight saving time) information in registry
• Lockfree algorithm for filedescriptor cache (improves file access speed)
• Other Pipelight specific enhancements
• Reduced SetTimer minimum value from 10 ms to 5 ms (improves Silverlight framerates)
• Support for GetVolumePathName
• Workaround for shlwapi URLs with relative paths
• XEMBED support for embedding Wine windows inside Linux applications

How to install wine-compholio

Ready-to-use packages for wine-compholio are available for a variety of different Linux distributions directly for download. Just follow the instructions below to install it (and all required dependencies). After the installation, please take a look at the next section for instructions how to use it in order to run your desired application.

Important: If you already have pipelight installed on your system, there is a good chance that you already have wine-compholio. Take a look at the next section on how to find out if this is the case.

If your distribution is not listed below, feel free to add a feature request - if the demand is high enough we might consider packaging it for additional distributions.

Ubuntu / Linux Mint

Please run the following commands from a terminal, one line after each other.

sudo add-apt-repository ppa:pipelight/stable
sudo apt-get update
sudo apt-get install --install-recommends wine-compholio

Arch Linux

As a first step you have to import the key for our repository, and set the trust level to trusted:

sudo pacman-key -r E49CC0415DC2D5CA
sudo pacman-key --lsign-key E49CC0415DC2D5CA

Afterwards you have to add the following lines to /etc/pacman.conf:

[compholio]
Server = http://cdn.fds-team.de/stable/arch/$arch

Now you can install wine-compholio directly using pacman:

sudo pacman -Sy wine-compholio

Debian Jessie/Sid

(Instructions for Debian Wheezy can be found below)

In order to install i386 packages on a 64-bit system, you have to run the following command as a first step:

sudo dpkg --add-architecture i386

Afterwards import the key for our repository:

wget http://repos.fds-team.de/Release.key
sudo apt-key add Release.key

And add our repository at the end of your /etc/apt/sources.list file:

# For Debian Jessie add the following line:
deb http://cdn.fds-team.de/stable/debian/ jessie main

# For Debian Sid this one:
deb http://cdn.fds-team.de/stable/debian/ sid main

Afterwards update the package cache and install it:

sudo apt-get update
sudo apt-get install wine-compholio

Debian Wheezy

In order to install i386 packages on a 64-bit system, you have to run the following command as a first step:

sudo dpkg --add-architecture i386

Afterwards import the key for our repository:

wget http://download.opensuse.org/repositories/home:/DarkPlayer:/Pipelight/Debian_7.0/Release.key
sudo apt-key add Release.key

And add our repository at the end of your /etc/apt/sources.list file:

# For Debian Wheezy add the following line:
deb http://download.opensuse.org/repositories/home:/DarkPlayer:/Pipelight/Debian_7.0/ ./

Afterwards update the package cache and install it:

sudo apt-get update
sudo apt-get install wine-compholio

OpenSUSE

All the following steps have to be executed as root user. As a first step you have to add the repository - this step depends on the openSUSE version you're using.

openSUSE version	Path component
openSUSE 12.2	/openSUSE_12.2/
openSUSE 12.3	/openSUSE_12.3/
openSUSE 13.1	/openSUSE_13.1/
openSUSE Factory	/openSUSE_Factory/
openSUSE Tumbleweed	/openSUSE_Tumbleweed/

The following commandline is an example for openSUSE 13.1, for a different version just replace the path component according to the table above:

zypper ar --refresh http://download.opensuse.org/repositories/home:/DarkPlayer:/Pipelight/openSUSE_13.1/home:DarkPlayer:Pipelight.repo

Afterwards just run the following commands to install it:

zypper ref
zypper install wine-compholio

Fedora

Warning: In contrary to other distributions, its not possible to have both a regular wine version and wine-compholio installed at the same time - using the instructions below will replace your regular version. Moreover it will be installed to /usr/bin/wine in contrary to /opt/wine-compholio/bin/wine.

As a first step you have to add the repository - this step depends on the Fedora version you're using.

Fedora version	Patch component
Fedora 18	/Fedora_18/
Fedora 19	/Fedora_19/
Fedora 20	/Fedora_20/

The following commandline is an example for Fedora 19, for a different version just replace the path component according to the table above:

sudo wget http://download.opensuse.org/repositories/home:/DarkPlayer:/Pipelight/Fedora_19/home:DarkPlayer:Pipelight.repo -O /etc/yum.repos.d/pipelight.repo

Afterwards run the following command to install the package:

sudo yum install wine-compholio

Please note that you might run into trouble if the official Fedora package (without compholio patches) is newer than the one from the repository above, so if something doesn't work, always make sure that you have installed our version. To do that just run:

/usr/bin/wine --patches

When you're using wine-compholio this will show to a list of all patches included, for an unpatched version this command will fail.

Mageia 4

As a first step please add the key for our repository

wget http://repos.fds-team.de/Release.key
rpm --import Release.keyy

If you're using a 32-bit version of Mageia just add the repository for 32-bit packages:

sudo urpmi.addmedia "Compholio 32-bit" http://cdn.fds-team.de/stable/mageia/4/i586/

For a 64-bit version of Mageia you'll need both the 32-bit and the 64-bit repository:

sudo urpmi.addmedia "Compholio 32-bit" http://cdn.fds-team.de/stable/mageia/4/i586/
sudo urpmi.addmedia "Compholio 64-bit" http://cdn.fds-team.de/stable/mageia/4/x86_64/

Afterwards run the following commands to install the package:

sudo urpmi.update -a
sudo urpmi wine-compholio

Using wine-compholio

Since we don't want to duplicate a lot of information here, we recommend to take a look at the official Wine FAQ for general information about how to use Wine. The following part will mainly concentrate on the differences between wine and wine-compholio.

Running wine-compholio

Using multiple Wine versions:* Unless you specify a special WINEPREFIX environment variable, wine-compholio will use the same wineprefix ~/.wine (in your home directory) like regular wine. This allows you to use your already installed programs directly, without much effort or reinstalling them. Often you have both regular wine and wine-compholio installed at the same time, which is absolutely no problem - by typing in either wine (=regular wine) or /opt/wine-compholio/bin/wine you can decide, which wine version you want to run. You can switch between versions as often as you like - just make sure that all Windows programs have terminated before starting them with a different version.

To run wine-compholio always type /opt/wine-compholio/bin/wine, for example:

cd ~/.wine/drive_c/<your path>/
/opt/wine-compholio/bin/wine game.exe

You also have to add /opt/wine-compholio/bin/ when running other wine related programs, here are some additional example:

# Initialize the wine prefix
/opt/wine-compholio/bin/wineboot

# Open the wine configuration
/opt/wine-compholio/bin/winecfg

# Run winepath to convert paths
/opt/wine-compholio/bin/winepath --unix 'c:\Windows'

# Kill the running wineserver instance
/opt/wine-compholio/bin/wineserver -k

...

If you're an experienced user, and always want to use wine-compholio, you can also add /opt/wine-compholio/bin to your bash profile. We will not go into detail here, because such a setup has the big disadvantage, that it hides which version you're using - which is very important for getting support or reporting bugs.

Submitting bugs

Warning: Do not submit bug reports at bugs.winehq.org when using this version!

If you encounter any issues, the first thing you should do is to try it with regular wine. We're only a very small developer team, and although we would like to do that, we probably cannot really solve all your Wine bugs. When it turns out that the official Wine version also doesn't work, you can file a bugreport at the official Wine bugtracker. Feel free to mention that you also tested with wine-compholio, but all bugreport related information (logs, crashdumps, ...) should concentrate only on upstream wine.

If it turns out, that it works with upstream wine, but not with wine-compholio, then it might be a regression caused by our patches. We would like you to report this issue to us, so we can fix it in future versions. You can also report issues, when testing with upstream Wine is impossible or it crashes with a different error (for example much earlier).

When submitting a application related bug here on github, please make sure to include at least the following information. Generally its always a good idea to provide as much information as possible, since this will significantly increase chances to provide support and to fix it.

1. Which application triggers the bug
   • Application name
   • Version number (if available)
   • Download URL (if available)
2. WINEPREFIX settings
   • Recommended: Test it in a new wine prefix, and report if this works
   • Did you install any overrides? (for examples by using winetricks)
   • Did you change any settings by running winecfg?
3. Information about your wine-compholio version
   • Recommended: Test with regular wine, and report if this works
   • Version number (/opt/wine-compholio/bin/wine --version)
   • Patches in your build (/opt/wine-compholio/bin/wine --patches)
   • Installed optional libraries (/opt/wine-compholio/bin/wine --check-libs)

Compiling wine-compholio

Warning: Please note that starting with wine-compholio 1.7.23 it is deprecated to manually apply patches without using the Makefile. To avoid typical pitfalls for package maintainers (like trying to use the patch commandline utility for binary patches or not updating the patchlist) it is highly recommended to use the Makefile in order to apply all patches. This ensures that the the correct patch utility is used, that the list of patches is updated appropriately, and so on. Please note that it is still possible to exclude patches if desired, take a look at the end of this document for more details.

Instructions

The following instructions (based on the Gentoo Wiki) will give a short overview how to compile wine-compholio, but of course not explain all details. Make sure to install all required Wine dependencies before proceeding.

As the first step please grab the latest Wine source:

wget http://prdownloads.sourceforge.net/wine/wine-1.7.23.tar.bz2
wget https://github.com/compholio/wine-compholio-daily/archive/v1.7.23.tar.gz

Extract the archives:

tar xvjf wine-1*.tar.bz2
cd wine-1*
tar xvzf ../v1.7.23.tar.gz --strip-components 1

And apply the patches:

make -C ./patches DESTDIR=$(pwd) install

Afterwards run configure (you can also specify a prefix if you don't want to install wine-compholio system-wide):

./configure --with-xattr

Before you continue you should make sure that ./configure doesn't show any warnings (look at the end of the output). If there are any warnings, this most likely means that you're missing some important header files. Install them and repeat the ./configure step until all problems are fixed.

Afterwards compile it (and grab a cup of coffee):

make

And install it (you only need sudo for a system-wide installation):

sudo make install

Excluding patches

It is also possible to apply only a subset of the patches, for example if you're compiling for a distribution where PulseAudio is not installed, or if you just don't like a specific patchset. Please note that some patchsets depend on each other, and requesting an impossible situation might result in a failure to apply all patches.

Lets assume you want to exclude the patchset in directory DIRNAME, then just invoke the Makefile like this:

make -C ./patches DESTDIR=$(pwd) install -W DIRNAME.ok

Using the same method its also possible to exclude multiple patchsets. If you want to exclude a very large number of patches, it is easier to do specify a list of patches which should be included instead. To apply for example only the patchsets in directory DIRNAME1 and DIRNAME2, you can use:

make -C ./patches DESTDIR=$(pwd) PATCHLIST="DIRNAME1.ok DIRNAME2.ok" install