Troubleshooting Common Problems

2017-06-28T07:12:18Z

Toadjaune: Added a section for the RPM variant of the error

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.

== p11-kit: couldn't load module: ... ==

=== Debian-based variant ===
==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== 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 =====

<pre class='code bash'>
sudo apt-get install p11-kit-modules:i386
</pre>

===== Create a symlink =====

(for systems before multiarch feature?)

''found at http://askubuntu.com/a/384018''

<pre class='code bash'>
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
</pre>

=== RPM-based variant ===

==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/pkcs11/p11-kit-trust.so: /usr/lib/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Users of Fedora, 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.

We need a 32-bit version of the package p11-kit-trust, but as explained [https://bugzilla.redhat.com/show_bug.cgi?id=1060764 here], there is a packaging issue, requiring manual install.

==== Common solutions ====

Go on the web interface of a RPM mirror, and search for `p11-kit-trust`, for i386 architecture. ([https://rpmfind.net/linux/rpm2html/search.php?query=p11-kit-trust&submit=Search+...&system=&arch=i686 this link] does most of the job for you)

Download the package corresponding with your Fedora version, and install it with `dnf install /path/to/downloaded/file`

You may then run into similar errors, but with different files. You can find the missing packages with `dnf provides /path/to/missing/file`, then install them simply with `dnf install package-name`

== Error in FS_Check ==

=== Error ===

{{Console|The following file is located on a fuse filesystem. It might prevent wine from working}}

=== 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 ===

{{Console|err:winediag:IcmpCreateFile Failed to use ICMP (network ping), this requires special permissions.
}}

=== 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 ===

==== Switch to WineBuild ''1.7.45-staging'' or higher ====

There is a fix for this in the Wine-Staging builds found in '''Manage Wine Versions''', so that should be tried first.

==== 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''':

{{Console|/home/username/.PlayOnLinux/wine/linux-x86/1.7.36}}

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.''

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine}}

or

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine-preloader}}

'''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:

{{Console|sudo setcap cap_net_raw+epi /home/'''username'''/.PlayOnLinux/wine/'''WineArchitecture'''/'''WineVersion'''/bin/wine}}

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 ===

{{Console|''someurl''

Error! Files mismatch

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.).

== The application you are trying to install needs administrator rights... ==

=== Error ===

{{Console|The application you are trying to install needs administrator rights to function correctly.}}

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Wine does not implement privileges as some Windows applications may expect, so if a program relies on certain aspects of Windows' user rights that Wine does not or cannot implement, it will fail.

=== Common solutions ===

==== File bug report with WineHQ ====

Anything like this should be reported directly to WineHQ's team, as they would need to troubleshoot and possibly develop a workaround to the permissions issue. You can find their bug system here:

* [https://bugs.winehq.org/ WineHQ's Bugzilla]

== League of Legends Stuck on Logo (after Champ Select) ==

=== Error ===

League of Legends simply stalls at the logo after the champion select dialogue.

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Multiple d3d libraries that come with Wine apparently, according to threads like [https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html this], do not offer the performance that the native d3d libraries do.

=== Common solutions ===

==== Install needed components ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html]

# Install in POL: d3dx10, d3dx11, d3dx9 (only d3dx9, not the other d3dx9_etc) and directx9
# It will break your Adobe Air (already installed in the virtual drive). I really don't know why but it does it, so we have to fix, go to Configure Wine, then select the tab Libraries and add the lib "dnsapi" and set it to "builtin, native"

== PlayOnMac: SECUR32_initNTLMSP ntlm_auth was not found or is outdated ==

=== Error ===

{{Console|err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.}}

=== Who might encounter this error? ===

PlayOnMac users, even if Samba and winbind are installed.

=== What causes this error? ===

PlayOnMac is not reading the correct path for some reason.

=== Common solutions ===

==== Edit PlayOnMac Bash script to properly set path ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html]

# Edit ''/Applications/PlayOnMac.app/Contents/MacOS/playonmac''
# Change ''#!/bin/bash'' to ''#!/bin/bash --login'', save, and try to start PlayOnMac

== No sound (err:module:load_builtin_dll... libasound.so.2...) ==

=== Error ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winealsa.drv": libasound.so.2: cannot open shared object file: No such file or directory.}}

=== Who might encounter this error? ===

Any user on any system may experience this.

=== What causes this error? ===

Missing 32-bit library; in this case, ''libasound2''.

=== Common solutions ===

==== Install the 32-bit version of libasound2 ====

Refer to your distro's docs for the package name for that system. 64-bit systems, because of how Wine/POL works, will almost always need the 32-bit version of libraries used for Wine/POL. Multiarch system's with support for package management with mixed-architectures should check manually if this error is coming up (some distros put things in odd places or don't handle multiarch support very well.).

PlayOnLinux - User contributions [en]

Troubleshooting Common Problems