Difference between revisions of "Troubleshooting Common Problems"

From PlayOnLinux
Jump to: navigation, search
(Create a symlink (found at http://askubuntu.com/a/384018))
Line 53: Line 53:
  
 
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.
 
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.
 +
 +
== err:winsock:interface_bind Failed to bind to interface ==
 +
 +
=== Error ===
 +
 +
{{Console|err:winsock:interface_bind Failed to bind to interface, receiving broadcast packets will not work on socket ''xxxx''.}}
 +
 +
=== Who might encounter this error? ===
 +
 +
Running a program through POL/Wine that requires winbind, but it is missing from your system.
 +
 +
=== What causes this error? ===
 +
 +
Simply a missing library from your system, ''winbind'', that Wine is trying to communicate with and not finding.
 +
 +
=== Common solutions ===
 +
 +
==== Install Samba ====
 +
 +
Install Samba on your system to install winbind. On a lot of systems, you can usually just install ''winbind'' by itself.

Revision as of 20:35, 18 March 2015

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

Error

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

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

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.

err:winsock:interface_bind Failed to bind to interface

Error

err:winsock:interface_bind Failed to bind to interface, receiving broadcast packets will not work on socket xxxx.

Who might encounter this error?

Running a program through POL/Wine that requires winbind, but it is missing from your system.

What causes this error?

Simply a missing library from your system, winbind, that Wine is trying to communicate with and not finding.

Common solutions

Install Samba

Install Samba on your system to install winbind. On a lot of systems, you can usually just install winbind by itself.