Troubleshooting Common Problems
Here is a list of common errors and possible solutions. Not everything will be here, but this list will get a lot bigger as time goes on, and hopefully, with the help of the community, we can make this list very, very robust.
When trying a possible solution for an issue, please only try ONE solution at a time, and test to see if it worked.
Contents
p11-kit: couldn't load module: ...
Error
Who might encounter this error?
Mostly users of Debian, Ubuntu, Kubuntu, etc., Mint (and derivatives), 64-bit systems.
What causes this error?
The 32-bit version of p11-kit-trust.so is either not installed, or is not located in an area that Wine expected it to be.
Common solutions
Install 32-bit version of p11-kit-trust.so
sudo apt-get install p11-kit-modules:i386
Create a symlink
found at http://askubuntu.com/a/384018
sudo /usr/local/bin/getlibs -p p11-kit:i386 sudo ln -s /usr/lib32/i386-linux-gnu/pkcs11/p11-kit-trust.so /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so
Error in FS_Check
Error
Who might encounter this error?
Anyone trying to run an executable file in Wine/POL that is located on an NTFS filesystem.
What causes this error?
Wine can get grumpy with how NTFS, Linux, and Wine interact with each other. This warning is simply there to alert you to this fact. Most of the time, this error can be ignored.
Common solutions
Move executable to a native Linux filesystem
Simply move the executable file in question to your native Linux filesystem, and this error will go away. It will only appear when trying to execute a file that is located on a FUSE filesystem.
Failed to use ICMP
Error
Who might encounter this error?
Anyone trying to run an application that wants to ping out. On POSIX-compliant systems, ping needs admin rights. NOTE: NEVER run Wine or POL as root.
What causes this error?
When a program tries to send an ICMP packet running through POL/Wine, it will fail, as it needs administrative rights, and we never run POL or Wine as root, do we? ;)
Common solutions
Give rights to POL's WineBuild
In most instances, you will see a command to remedy this. Most of the time, it is missing the final argument, which is the particular instance of Wine that you are running. These solutions work fine for Vanilla Wine, but not POL. For POL, you have to point the particular command to POL's WineBuild for that particular virtual drive.
For instance, AION.
All of POL's WineBuilds are stored in ~/.PlayOnLinux/wine/
Within this folder, you have different sub-folders for architecture, and then Wine version. In the case of AION:
Find out which Wine version your application needs:
- Open the Configuration Window
- In the General tab, when your virtual drive is selected, look at the name of the version of Wine in use.
Now, the command you would want to run is:
NOTE: Do NOT copy and paste these commands. They need to be modified for your particular situation.
or
NOTE: I have seen both bin/wine and bin/wine-preloader shown in examples, so for posterity, I am including both.
Essentially, the syntax for this is as follows:
Replace:
- username with your current username
- Wine Architecture with either linux-x86 (32-bit virtual drive) or linux-amd64 (64-bit virtual drive)
- Wine Version with the EXACT name listed in the Wine dropdown menu in the General tab of the Configuration Window
Error! Files mismatch
Error
Local: md5resultexpected
Server: md5resultdownloaded
Do you want to retry?
Who might encounter this error?
This can happen to any user on any system. It is also architecture agnostic.
What causes this error?
When POL scripts use certain API calls, there is a positional argument for the MD5 hash, to make sure that the downloaded file is intact and is not different than what has been tested. If the server hosting a certain file updates or changes the file in question, or if the download fails, the MD5 will be different, and will throw an error.
Common solutions
File bug report with POL
If this happens, it is something that the POL team should be made aware of. Please let us know so that we can take measures to correct this issue. As long as we can get the new file successfully, we can grab the MD5 hash and change the script so that this error will not pop up again (of course, if the file changes, this will happen again, and should be reported.).
