https://wiki.playonlinux.com/api.php?action=feedcontributions&user=RoninDusette&feedformat=atomPlayOnLinux - User contributions [en]2024-03-28T16:44:25ZUser contributionsMediaWiki 1.30.0https://wiki.playonlinux.com/index.php?title=Components_and_Functions&diff=876Components and Functions2016-06-17T06:53:26Z<p>RoninDusette: /* AdobeAir */</p>
<hr />
<div>Details, use cases, related errors, and more on each component coming soon...<br />
<br />
== AdobeAir ==<br />
<br />
'''What is it?'''<br />
<br />
"The Adobe AIR runtime enables developers to package the same code into native applications and games for Windows and Mac OS desktops as well as iOS and Android devices, reaching over a billion desktop systems and mobile app stores for over 500 million devices."<br />
<br />
-from http://get.adobe.com/air/<br />
<br />
'''What does it do?'''<br />
<br />
Installs the Adobe Air package.<br />
<br />
'''When would I need it?'''<br />
<br />
Certain Adobe products require this to be installed as a dependency.<br />
<br />
'''Script/Shell command:'''<br />
<br />
<pre class="playonlinux code"><br />
POL_Call POL_Install_AdobeAir<br />
</pre><br />
<br />
'''Links:'''<br />
<br />
http://get.adobe.com/air/<br />
<br />
== amstream ==<br />
<br />
POL_Call POL_Install_amstream<br />
<br />
== ATI_Black-Screen_Fix ==<br />
<br />
POL_Call POL_Install_ATI_Black-Screen_Fix<br />
<br />
== atmlib ==<br />
<br />
POL_Call POL_Install_atmlib<br />
<br />
== cc580 ==<br />
<br />
POL_Call POL_Install_cc580<br />
<br />
== CentralizedUserDirs ==<br />
<br />
POL_Call POL_Install_CentralizedUserDirs<br />
<br />
== corefonts ==<br />
<br />
'''What is it?'''<br />
<br />
"TrueType is an outline font standard developed by Apple and Microsoft in the late 1980s as a competitor to Adobe's Type 1 fonts used in PostScript. It has become the most common format for fonts on both the Mac OS and Microsoft Windows operating systems."<br />
<br />
from http://en.wikipedia.org/wiki/TrueType<br />
<br />
'''What does it do?'''<br />
<br />
Downloads and registers TrueType fonts (TTF). Here is a list of the fonts that will be installed into the given virtual drive:<br />
<br />
* andale mono<br />
* arial black<br />
* arial (bold, italic, bold italic)<br />
* comic sans ms (bold)<br />
* courier new (bold, italic, bold italic)<br />
* georgia (bold, italic, bold italic)<br />
* impact<br />
* times new roman (bold, italic, bold italic)<br />
* trebuchet (bold, italic, bold italic)<br />
* verdana (bold, italic, bold italic)<br />
* webdings<br />
<br />
'''When would I need it?'''<br />
<br />
Any time you experience missing text in an application, this would be the first place you would want to start. This is usually installed by default, though. If this does not work, try '''tahoma''' or '''tahoma2''' from the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Install Components tab], as those are the usual suspects in such acts of font thievery.<br />
<br />
'''Script/Shell command:'''<br />
<br />
<pre class="playonlinux code"><br />
POL_Call POL_Install_corefonts<br />
</pre><br />
<br />
'''Links:'''<br />
<br />
http://en.wikipedia.org/wiki/TrueType<br />
<br />
== crypt32 ==<br />
<br />
'''What is it?'''<br />
<br />
''crypt32'' does quite a few things relating to decrypting/encrypting data. Basic information in the links below.<br />
<br />
'''What does it do?'''<br />
<br />
"It supports encryption, decryption, and manipulation of certificates and related data structures."<br />
<br />
from http://wiki.winehq.org/Crypt32<br />
<br />
'''When would I need it?'''<br />
<br />
Most of this is taken care of within Wine via the ''builtin'' dll. You may run into times when the native dll is needed, in which case the POL debug log will spit out an error saying that it tried to do something with it and it failed (like ''unhandled exception'' or ''cannot find crypt32.dll'', etc.). If you do happen to run into an error like this, we highly encourage you to report it to https://appdb.winehq.org so that the community there can possibly implement a fix that is native to Wine, eliminating the need for the actual Windows dll.<br />
<br />
'''Script/Shell command:'''<br />
<br />
<pre class="playonlinux code"><br />
POL_Call POL_Install_crypt32<br />
</pre><br />
<br />
'''Links:'''<br />
<br />
http://wiki.winehq.org/Crypt32<br />
<br />
== dcom98 ==<br />
<br />
POL_Call POL_Install_dcom98<br />
<br />
== DirectX ==<br />
<br />
=== d3dcompiler_43 ===<br />
<br />
POL_Call POL_Install_d3dcompiler_43<br />
<br />
=== d3dx10 ===<br />
<br />
POL_Call POL_Install_d3dx10<br />
<br />
=== d3dx11 ===<br />
<br />
POL_Call POL_Install_d3dx11<br />
<br />
=== d3dx9 ===<br />
<br />
POL_Call POL_Install_d3dx9<br />
<br />
=== d3dx9_29 ===<br />
<br />
POL_Call POL_Install_d3dx9_29<br />
<br />
=== d3dx9_35 ===<br />
<br />
POL_Call POL_Install_d3dx9_35<br />
<br />
=== d3dx9_36 ===<br />
<br />
POL_Call POL_Install_d3dx9_36<br />
<br />
=== d3dx9_40 ===<br />
<br />
POL_Call POL_Install_d3dx9_40<br />
<br />
=== d3dx9_42 ===<br />
<br />
POL_Call POL_Install_d3dx9_42<br />
<br />
=== d3dx9_43 ===<br />
<br />
POL_Call POL_Install_d3dx9_43<br />
<br />
=== dinput8 ===<br />
<br />
POL_Call POL_Install_dinput8<br />
<br />
=== directmusic ===<br />
<br />
POL_Call POL_Install_directmusic<br />
<br />
=== directplay ===<br />
<br />
POL_Call POL_Install_directplay<br />
<br />
=== directx9 ===<br />
<br />
POL_Call POL_Install_directx9<br />
<br />
=== dinput ===<br />
<br />
POL_Call POL_Install_dinput<br />
<br />
=== dsound ===<br />
<br />
POL_Call POL_Install_dsound<br />
<br />
=== dxdiag ===<br />
<br />
POL_Call POL_Install_dxdiag<br />
<br />
=== dxfullsetup ===<br />
<br />
POL_Call POL_Install_dxfullsetup<br />
<br />
== Desura ==<br />
<br />
POL_Call POL_Install_desura<br />
<br />
== devenum ==<br />
<br />
POL_Call POL_Install_devenum<br />
<br />
== DisableCrashDialog ==<br />
<br />
POL_Call POL_Install_DisableCrashDialog<br />
<br />
== DosboxDrive ==<br />
<br />
POL_Call POL_Install_DosboxDrive<br />
<br />
== .NET ==<br />
<br />
=== POL_Install_dotnet11 ===<br />
<br />
=== POL_Install_dotnet11sp1 ===<br />
<br />
=== POL_Install_dotnet20 ===<br />
<br />
=== POL_Install_dotnet20sp1 ===<br />
<br />
=== POL_Install_dotnet20sp2 ===<br />
<br />
=== POL_Install_dotnet30 ===<br />
<br />
=== POL_Install_dotnet30sp1 ===<br />
<br />
=== POL_Install_dotnet35 ===<br />
<br />
=== POL_Install_dotnet35sp1 ===<br />
<br />
=== POL_Install_dotnet40 ===<br />
<br />
== fakeie6 ==<br />
<br />
POL_Call POL_Install_fakeie6<br />
<br />
== ffdshow ==<br />
<br />
POL_Call POL_Install_ffdshow<br />
<br />
== flashplayer ==<br />
<br />
POL_Call POL_Install_flashplayer<br />
<br />
== Flashplayer_ActiveX ==<br />
<br />
POL_Call POL_Install_Flashplayer_ActiveX<br />
<br />
== FontsSmoothBGR ==<br />
<br />
POL_Call POL_Install_FontsSmoothBGR<br />
<br />
== FontsSmoothGrayScale ==<br />
<br />
POL_Call POL_Install_FontsSmoothGrayScale<br />
<br />
== FontsSmoothRGB ==<br />
<br />
POL_Call POL_Install_FontsSmoothRGB<br />
<br />
== gdiplus ==<br />
<br />
POL_Call POL_Install_gdiplus<br />
<br />
== gecko ==<br />
<br />
POL_Call POL_Install_gecko<br />
<br />
== gfwl ==<br />
<br />
POL_Call POL_Install_gfwl<br />
<br />
== gfwl86 ==<br />
<br />
POL_Call POL_Install_gfwl86<br />
<br />
== HackSteam ==<br />
<br />
POL_Call POL_Install_HackSteam<br />
<br />
== ie6 ==<br />
<br />
POL_Call POL_Install_ie6<br />
<br />
== ie8 ==<br />
<br />
POL_Call POL_Install_ie8<br />
<br />
== iv50 ==<br />
<br />
POL_Call POL_Install_iv50<br />
<br />
== linuxtrack-wine ==<br />
<br />
POL_Call POL_Install_linuxtrack-wine<br />
<br />
== LunaTheme ==<br />
<br />
POL_Call POL_Install_LunaTheme<br />
<br />
== mdac28 ==<br />
<br />
POL_Call POL_Install_mdac28<br />
<br />
== mfc ==<br />
<br />
=== POL_Install_mfc40 ===<br />
<br />
=== POL_Install_mfc42 ===<br />
<br />
== Mono ==<br />
<br />
=== POL_Install_mono210 ===<br />
<br />
=== POL_Install_mono26 ===<br />
<br />
=== POL_Install_mono28 ===<br />
<br />
== msasn1 ==<br />
<br />
POL_Call POL_Install_msasn1<br />
<br />
== msls31 ==<br />
<br />
POL_Call POL_Install_msls31<br />
<br />
== msvc ==<br />
<br />
=== POL_Install_msvc100 ===<br />
<br />
=== POL_Install_msvc80 ===<br />
<br />
=== POL_Install_msvc90 ===<br />
<br />
== msxml ==<br />
<br />
=== POL_Install_msxml3 ===<br />
<br />
=== POL_Install_msxml4 ===<br />
<br />
=== POL_Install_msxml6 ===<br />
<br />
== nop ==<br />
<br />
POL_Call POL_Install_nop<br />
<br />
== physx ==<br />
<br />
POL_Call POL_Install_physx<br />
<br />
== pngfilt ==<br />
<br />
POL_Call POL_Install_pngfilt<br />
<br />
== PrivateUserDirs ==<br />
<br />
POL_Call POL_Install_PrivateUserDirs<br />
<br />
== quartz ==<br />
<br />
POL_Call POL_Install_quartz<br />
<br />
== RegisterFonts ==<br />
<br />
POL_Call POL_Install_RegisterFonts<br />
<br />
== riched20 ==<br />
<br />
=== POL_Install_riched20 ===<br />
<br />
=== POL_Install_riched30 ===<br />
<br />
== rsc ==<br />
<br />
POL_Call POL_Install_rsc<br />
<br />
== steam ==<br />
<br />
'''What is it?'''<br />
<br />
An installer for the game publishing platform Steam.<br />
<br />
'''What does it do?'''<br />
<br />
Downloads and Installs Steam client.<br />
<br />
'''When would I need it?'''<br />
<br />
Any time a game requires Steam to run.<br />
<br />
'''Script/Shell command:'''<br />
<br />
<pre class="playonlinux code"><br />
POL_Call POL_Install_steam<br />
</pre><br />
<br />
'''Links:'''<br />
<br />
http://store.steampowered.com/<br />
<br />
== steam_flags ==<br />
<br />
'''What is it?'''<br />
<br />
A helper script for Steam.<br />
<br />
'''What does it do?'''<br />
<br />
Set registry third-party flags to avoid steam installing them at the game's first launch.<br />
<br />
'''When would I need it?'''<br />
<br />
To avoid Steam reinstalling POL-installed dependencies (Wine sometimes requires some ''wizardry'' to get things working that the stock installers do not do, and can cause the application not to run if the workaround is overwritten or broken by the default installation being triggered by the Steam client.).<br />
<br />
'''Script/Shell command:'''<br />
<br />
<pre class="playonlinux code"><br />
POL_Call POL_Install_steam_flags<br />
</pre><br />
<br />
'''Links:'''<br />
<br />
https://www.playonlinux.com/en/app-927-POL_Install_steam_flags.html<br />
<br />
== tahoma ==<br />
<br />
'''What is it?'''<br />
<br />
An installer for the Microsoft font ''Tahoma''. <br />
<br />
'''What does it do?'''<br />
<br />
Downloads and registers ''Tahoma''.<br />
<br />
'''When would I need it?'''<br />
<br />
Any time the ''Tahoma'' font is needed.<br />
<br />
'''Script/Shell command:'''<br />
<br />
<pre class="playonlinux code"><br />
POL_Call POL_Install_tahoma<br />
</pre><br />
<br />
'''Links:'''<br />
<br />
http://www.microsoft.com/typography/fonts/family.aspx?FID=19<br />
<br />
== tahoma2 ==<br />
<br />
'''What is it?'''<br />
<br />
An alternative installer for the Microsoft font ''Tahoma''. <br />
<br />
'''What does it do?'''<br />
<br />
Downloads and registers Tahoma, but from a different package.<br />
<br />
'''When would I need it?'''<br />
<br />
Any time the ''Tahoma'' font is needed, where the regular ''Tahoma'' installer does not work (like Photoshop CS6).<br />
<br />
'''Script/Shell command:'''<br />
<br />
<pre class="playonlinux code"><br />
POL_Call POL_Install_tahoma2<br />
</pre><br />
<br />
'''Links:'''<br />
<br />
http://www.microsoft.com/typography/fonts/family.aspx?FID=19<br />
<br />
== ubigamelauncher ==<br />
<br />
POL_Call POL_Install_ubigamelauncher<br />
<br />
== vbrun6 ==<br />
<br />
POL_Call POL_Install_vbrun6<br />
<br />
== vcrun ==<br />
<br />
=== POL_Install_vcrun2005 ===<br />
<br />
=== POL_Install_vcrun2008 ===<br />
<br />
=== POL_Install_vcrun2010 ===<br />
<br />
=== POL_Install_vcrun2012 ===<br />
<br />
=== POL_Install_vcrun2013 ===<br />
<br />
=== POL_Install_vcrun6 ===<br />
<br />
== VideoDriver ==<br />
<br />
POL_Call POL_Install_VideoDriver<br />
<br />
== wine64b ==<br />
<br />
POL_Call POL_Install_wine64b<br />
<br />
== wineasio ==<br />
<br />
'''What is it?'''<br />
<br />
WineASIO provides an ASIO driver interface from Wine to jack for low-latency audio and advanced audio/MIDI routing.<br />
<br />
'''What does it do?'''<br />
<br />
Checks for the following:<br />
<br />
* Checks that the virtual drive is 32-bit<br />
<br />
* Makes sure that the user is part of the ''audio'' group<br />
<br />
* Confirms the presence of ''jack'' and ''qjackctl''<br />
<br />
Then, if all checks pass, WineASIO is downloaded and registered into that virtual drive.<br />
<br />
'''When would I need it?'''<br />
<br />
Certain Adobe products require this to be installed as a dependency.<br />
<br />
'''Script/Shell command:'''<br />
<br />
<pre class="playonlinux code"><br />
POL_Call POL_Install_wineasio<br />
</pre><br />
<br />
'''Links:'''<br />
<br />
http://sourceforge.net/projects/wineasio/<br />
<br />
== winhttp ==<br />
<br />
POL_Call POL_Install_winhttp<br />
<br />
== wininet ==<br />
<br />
POL_Call POL_Install_wininet<br />
<br />
== wintrust ==<br />
<br />
POL_Call POL_Install_wintrust<br />
<br />
== wmp10 ==<br />
<br />
POL_Call POL_Install_wmp10<br />
<br />
== wmp9 ==<br />
<br />
POL_Call POL_Install_wmp9<br />
<br />
== wmpcodecs ==<br />
<br />
POL_Call POL_Install_wmpcodecs<br />
<br />
== wsh56 ==<br />
<br />
POL_Call POL_Install_wsh56<br />
<br />
== wsh57 ==<br />
<br />
POL_Call POL_Install_wsh57<br />
<br />
== xact ==<br />
<br />
POL_Call POL_Install_xact<br />
<br />
== xinput ==<br />
<br />
POL_Call POL_Install_xinput<br />
<br />
== xmllite ==<br />
<br />
POL_Call POL_Install_xmllite<br />
<br />
== xna31 ==<br />
<br />
POL_Call POL_Install_xna31<br />
<br />
== xna40 ==<br />
<br />
POL_Call POL_Install_xna40<br />
<br />
== xvid ==<br />
<br />
POL_Call POL_Install_xvid<br />
<br />
== Other Functions ==<br />
<br />
=== POL_Configurator_runparts ===<br />
<br />
POL_Call POL_Configurator_runparts<br />
<br />
=== POL_Download_retry ===<br />
<br />
POL_Call POL_Download_retry<br />
<br />
=== POL_Function_FontsSmoothBGR ===<br />
<br />
POL_Call POL_Function_FontsSmoothBGR<br />
<br />
=== POL_Function_FontsSmoothGrayScale ===<br />
<br />
POL_Call POL_Function_FontsSmoothGrayScale<br />
<br />
=== POL_Function_FontsSmoothRGB ===<br />
<br />
POL_Call POL_Function_FontsSmoothRGB<br />
<br />
=== POL_Function_NoCDWarning ===<br />
<br />
POL_Call POL_Function_NoCDWarning<br />
<br />
=== POL_Function_override_app_dlls ===<br />
<br />
POL_Call POL_Function_override_app_dlls<br />
<br />
=== POL_Function_OverrideDLL ===<br />
<br />
POL_Call POL_Function_OverrideDLL<br />
<br />
=== POL_Function_RootCommand ===<br />
<br />
POL_Call POL_Function_RootCommand<br />
<br />
=== POL_Function_sandbox ===<br />
<br />
POL_Call POL_Function_sandbox<br />
<br />
=== POL_Function_SetNativeExtension ===<br />
<br />
POL_Call POL_Function_SetNativeExtension<br />
<br />
=== POL_Function_simplecdscript ===<br />
<br />
POL_Call POL_Function_simplecdscript<br />
<br />
=== POL_Function_simplescript ===<br />
<br />
POL_Call POL_Function_simplescript<br />
<br />
=== POL_Function_Sleep ===<br />
<br />
POL_Call POL_Function_Sleep<br />
<br />
=== POL_Gamefront_Download ===<br />
<br />
POL_Call POL_Gamefront_Download<br />
<br />
=== POL_GetTool_samba3 ===<br />
<br />
POL_Call POL_GetTool_samba3<br />
<br />
=== POL_GoG_download ===<br />
<br />
POL_Call POL_GoG_download<br />
<br />
=== POL_GoG_Extract ===<br />
<br />
POL_Call POL_GoG_Extract<br />
<br />
=== POL_GoG_install ===<br />
<br />
POL_Call POL_GoG_install<br />
<br />
=== POL_GoG_setup ===<br />
<br />
POL_Call POL_GoG_setup</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Components_and_Functions&diff=875Components and Functions2016-06-17T06:53:02Z<p>RoninDusette: /* AdobeAir */</p>
<hr />
<div>Details, use cases, related errors, and more on each component coming soon...<br />
<br />
== AdobeAir ==<br />
<br />
'''What is it?'''<br />
<br />
"The Adobe AIR runtime enables developers to package the same code into native applications and games for Windows and Mac OS desktops as well as iOS and Android devices, reaching over a billion desktop systems and mobile app stores for over 500 million devices."<br />
<br />
-from http://get.adobe.com/air/<br />
<br />
'''What does it do?'''<br />
<br />
Installs the Adobe Air package.<br />
<br />
'''When would I need it?'''<br />
<br />
Certain Adobe products require this to be installed as a dependency.<br />
<br />
'''Script/Shell command:'''<br />
<br />
<pre class="playonlinux code"><br />
POL_Call POL_Install_AdobeAir<br />
</pre><br />
<br />
'''Links:'''<br />
<br />
<pre class="playonlinux code"><br />
http://get.adobe.com/air/<br />
</pre><br />
<br />
== amstream ==<br />
<br />
POL_Call POL_Install_amstream<br />
<br />
== ATI_Black-Screen_Fix ==<br />
<br />
POL_Call POL_Install_ATI_Black-Screen_Fix<br />
<br />
== atmlib ==<br />
<br />
POL_Call POL_Install_atmlib<br />
<br />
== cc580 ==<br />
<br />
POL_Call POL_Install_cc580<br />
<br />
== CentralizedUserDirs ==<br />
<br />
POL_Call POL_Install_CentralizedUserDirs<br />
<br />
== corefonts ==<br />
<br />
'''What is it?'''<br />
<br />
"TrueType is an outline font standard developed by Apple and Microsoft in the late 1980s as a competitor to Adobe's Type 1 fonts used in PostScript. It has become the most common format for fonts on both the Mac OS and Microsoft Windows operating systems."<br />
<br />
from http://en.wikipedia.org/wiki/TrueType<br />
<br />
'''What does it do?'''<br />
<br />
Downloads and registers TrueType fonts (TTF). Here is a list of the fonts that will be installed into the given virtual drive:<br />
<br />
* andale mono<br />
* arial black<br />
* arial (bold, italic, bold italic)<br />
* comic sans ms (bold)<br />
* courier new (bold, italic, bold italic)<br />
* georgia (bold, italic, bold italic)<br />
* impact<br />
* times new roman (bold, italic, bold italic)<br />
* trebuchet (bold, italic, bold italic)<br />
* verdana (bold, italic, bold italic)<br />
* webdings<br />
<br />
'''When would I need it?'''<br />
<br />
Any time you experience missing text in an application, this would be the first place you would want to start. This is usually installed by default, though. If this does not work, try '''tahoma''' or '''tahoma2''' from the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Install Components tab], as those are the usual suspects in such acts of font thievery.<br />
<br />
'''Script/Shell command:'''<br />
<br />
<pre class="playonlinux code"><br />
POL_Call POL_Install_corefonts<br />
</pre><br />
<br />
'''Links:'''<br />
<br />
http://en.wikipedia.org/wiki/TrueType<br />
<br />
== crypt32 ==<br />
<br />
'''What is it?'''<br />
<br />
''crypt32'' does quite a few things relating to decrypting/encrypting data. Basic information in the links below.<br />
<br />
'''What does it do?'''<br />
<br />
"It supports encryption, decryption, and manipulation of certificates and related data structures."<br />
<br />
from http://wiki.winehq.org/Crypt32<br />
<br />
'''When would I need it?'''<br />
<br />
Most of this is taken care of within Wine via the ''builtin'' dll. You may run into times when the native dll is needed, in which case the POL debug log will spit out an error saying that it tried to do something with it and it failed (like ''unhandled exception'' or ''cannot find crypt32.dll'', etc.). If you do happen to run into an error like this, we highly encourage you to report it to https://appdb.winehq.org so that the community there can possibly implement a fix that is native to Wine, eliminating the need for the actual Windows dll.<br />
<br />
'''Script/Shell command:'''<br />
<br />
<pre class="playonlinux code"><br />
POL_Call POL_Install_crypt32<br />
</pre><br />
<br />
'''Links:'''<br />
<br />
http://wiki.winehq.org/Crypt32<br />
<br />
== dcom98 ==<br />
<br />
POL_Call POL_Install_dcom98<br />
<br />
== DirectX ==<br />
<br />
=== d3dcompiler_43 ===<br />
<br />
POL_Call POL_Install_d3dcompiler_43<br />
<br />
=== d3dx10 ===<br />
<br />
POL_Call POL_Install_d3dx10<br />
<br />
=== d3dx11 ===<br />
<br />
POL_Call POL_Install_d3dx11<br />
<br />
=== d3dx9 ===<br />
<br />
POL_Call POL_Install_d3dx9<br />
<br />
=== d3dx9_29 ===<br />
<br />
POL_Call POL_Install_d3dx9_29<br />
<br />
=== d3dx9_35 ===<br />
<br />
POL_Call POL_Install_d3dx9_35<br />
<br />
=== d3dx9_36 ===<br />
<br />
POL_Call POL_Install_d3dx9_36<br />
<br />
=== d3dx9_40 ===<br />
<br />
POL_Call POL_Install_d3dx9_40<br />
<br />
=== d3dx9_42 ===<br />
<br />
POL_Call POL_Install_d3dx9_42<br />
<br />
=== d3dx9_43 ===<br />
<br />
POL_Call POL_Install_d3dx9_43<br />
<br />
=== dinput8 ===<br />
<br />
POL_Call POL_Install_dinput8<br />
<br />
=== directmusic ===<br />
<br />
POL_Call POL_Install_directmusic<br />
<br />
=== directplay ===<br />
<br />
POL_Call POL_Install_directplay<br />
<br />
=== directx9 ===<br />
<br />
POL_Call POL_Install_directx9<br />
<br />
=== dinput ===<br />
<br />
POL_Call POL_Install_dinput<br />
<br />
=== dsound ===<br />
<br />
POL_Call POL_Install_dsound<br />
<br />
=== dxdiag ===<br />
<br />
POL_Call POL_Install_dxdiag<br />
<br />
=== dxfullsetup ===<br />
<br />
POL_Call POL_Install_dxfullsetup<br />
<br />
== Desura ==<br />
<br />
POL_Call POL_Install_desura<br />
<br />
== devenum ==<br />
<br />
POL_Call POL_Install_devenum<br />
<br />
== DisableCrashDialog ==<br />
<br />
POL_Call POL_Install_DisableCrashDialog<br />
<br />
== DosboxDrive ==<br />
<br />
POL_Call POL_Install_DosboxDrive<br />
<br />
== .NET ==<br />
<br />
=== POL_Install_dotnet11 ===<br />
<br />
=== POL_Install_dotnet11sp1 ===<br />
<br />
=== POL_Install_dotnet20 ===<br />
<br />
=== POL_Install_dotnet20sp1 ===<br />
<br />
=== POL_Install_dotnet20sp2 ===<br />
<br />
=== POL_Install_dotnet30 ===<br />
<br />
=== POL_Install_dotnet30sp1 ===<br />
<br />
=== POL_Install_dotnet35 ===<br />
<br />
=== POL_Install_dotnet35sp1 ===<br />
<br />
=== POL_Install_dotnet40 ===<br />
<br />
== fakeie6 ==<br />
<br />
POL_Call POL_Install_fakeie6<br />
<br />
== ffdshow ==<br />
<br />
POL_Call POL_Install_ffdshow<br />
<br />
== flashplayer ==<br />
<br />
POL_Call POL_Install_flashplayer<br />
<br />
== Flashplayer_ActiveX ==<br />
<br />
POL_Call POL_Install_Flashplayer_ActiveX<br />
<br />
== FontsSmoothBGR ==<br />
<br />
POL_Call POL_Install_FontsSmoothBGR<br />
<br />
== FontsSmoothGrayScale ==<br />
<br />
POL_Call POL_Install_FontsSmoothGrayScale<br />
<br />
== FontsSmoothRGB ==<br />
<br />
POL_Call POL_Install_FontsSmoothRGB<br />
<br />
== gdiplus ==<br />
<br />
POL_Call POL_Install_gdiplus<br />
<br />
== gecko ==<br />
<br />
POL_Call POL_Install_gecko<br />
<br />
== gfwl ==<br />
<br />
POL_Call POL_Install_gfwl<br />
<br />
== gfwl86 ==<br />
<br />
POL_Call POL_Install_gfwl86<br />
<br />
== HackSteam ==<br />
<br />
POL_Call POL_Install_HackSteam<br />
<br />
== ie6 ==<br />
<br />
POL_Call POL_Install_ie6<br />
<br />
== ie8 ==<br />
<br />
POL_Call POL_Install_ie8<br />
<br />
== iv50 ==<br />
<br />
POL_Call POL_Install_iv50<br />
<br />
== linuxtrack-wine ==<br />
<br />
POL_Call POL_Install_linuxtrack-wine<br />
<br />
== LunaTheme ==<br />
<br />
POL_Call POL_Install_LunaTheme<br />
<br />
== mdac28 ==<br />
<br />
POL_Call POL_Install_mdac28<br />
<br />
== mfc ==<br />
<br />
=== POL_Install_mfc40 ===<br />
<br />
=== POL_Install_mfc42 ===<br />
<br />
== Mono ==<br />
<br />
=== POL_Install_mono210 ===<br />
<br />
=== POL_Install_mono26 ===<br />
<br />
=== POL_Install_mono28 ===<br />
<br />
== msasn1 ==<br />
<br />
POL_Call POL_Install_msasn1<br />
<br />
== msls31 ==<br />
<br />
POL_Call POL_Install_msls31<br />
<br />
== msvc ==<br />
<br />
=== POL_Install_msvc100 ===<br />
<br />
=== POL_Install_msvc80 ===<br />
<br />
=== POL_Install_msvc90 ===<br />
<br />
== msxml ==<br />
<br />
=== POL_Install_msxml3 ===<br />
<br />
=== POL_Install_msxml4 ===<br />
<br />
=== POL_Install_msxml6 ===<br />
<br />
== nop ==<br />
<br />
POL_Call POL_Install_nop<br />
<br />
== physx ==<br />
<br />
POL_Call POL_Install_physx<br />
<br />
== pngfilt ==<br />
<br />
POL_Call POL_Install_pngfilt<br />
<br />
== PrivateUserDirs ==<br />
<br />
POL_Call POL_Install_PrivateUserDirs<br />
<br />
== quartz ==<br />
<br />
POL_Call POL_Install_quartz<br />
<br />
== RegisterFonts ==<br />
<br />
POL_Call POL_Install_RegisterFonts<br />
<br />
== riched20 ==<br />
<br />
=== POL_Install_riched20 ===<br />
<br />
=== POL_Install_riched30 ===<br />
<br />
== rsc ==<br />
<br />
POL_Call POL_Install_rsc<br />
<br />
== steam ==<br />
<br />
'''What is it?'''<br />
<br />
An installer for the game publishing platform Steam.<br />
<br />
'''What does it do?'''<br />
<br />
Downloads and Installs Steam client.<br />
<br />
'''When would I need it?'''<br />
<br />
Any time a game requires Steam to run.<br />
<br />
'''Script/Shell command:'''<br />
<br />
<pre class="playonlinux code"><br />
POL_Call POL_Install_steam<br />
</pre><br />
<br />
'''Links:'''<br />
<br />
http://store.steampowered.com/<br />
<br />
== steam_flags ==<br />
<br />
'''What is it?'''<br />
<br />
A helper script for Steam.<br />
<br />
'''What does it do?'''<br />
<br />
Set registry third-party flags to avoid steam installing them at the game's first launch.<br />
<br />
'''When would I need it?'''<br />
<br />
To avoid Steam reinstalling POL-installed dependencies (Wine sometimes requires some ''wizardry'' to get things working that the stock installers do not do, and can cause the application not to run if the workaround is overwritten or broken by the default installation being triggered by the Steam client.).<br />
<br />
'''Script/Shell command:'''<br />
<br />
<pre class="playonlinux code"><br />
POL_Call POL_Install_steam_flags<br />
</pre><br />
<br />
'''Links:'''<br />
<br />
https://www.playonlinux.com/en/app-927-POL_Install_steam_flags.html<br />
<br />
== tahoma ==<br />
<br />
'''What is it?'''<br />
<br />
An installer for the Microsoft font ''Tahoma''. <br />
<br />
'''What does it do?'''<br />
<br />
Downloads and registers ''Tahoma''.<br />
<br />
'''When would I need it?'''<br />
<br />
Any time the ''Tahoma'' font is needed.<br />
<br />
'''Script/Shell command:'''<br />
<br />
<pre class="playonlinux code"><br />
POL_Call POL_Install_tahoma<br />
</pre><br />
<br />
'''Links:'''<br />
<br />
http://www.microsoft.com/typography/fonts/family.aspx?FID=19<br />
<br />
== tahoma2 ==<br />
<br />
'''What is it?'''<br />
<br />
An alternative installer for the Microsoft font ''Tahoma''. <br />
<br />
'''What does it do?'''<br />
<br />
Downloads and registers Tahoma, but from a different package.<br />
<br />
'''When would I need it?'''<br />
<br />
Any time the ''Tahoma'' font is needed, where the regular ''Tahoma'' installer does not work (like Photoshop CS6).<br />
<br />
'''Script/Shell command:'''<br />
<br />
<pre class="playonlinux code"><br />
POL_Call POL_Install_tahoma2<br />
</pre><br />
<br />
'''Links:'''<br />
<br />
http://www.microsoft.com/typography/fonts/family.aspx?FID=19<br />
<br />
== ubigamelauncher ==<br />
<br />
POL_Call POL_Install_ubigamelauncher<br />
<br />
== vbrun6 ==<br />
<br />
POL_Call POL_Install_vbrun6<br />
<br />
== vcrun ==<br />
<br />
=== POL_Install_vcrun2005 ===<br />
<br />
=== POL_Install_vcrun2008 ===<br />
<br />
=== POL_Install_vcrun2010 ===<br />
<br />
=== POL_Install_vcrun2012 ===<br />
<br />
=== POL_Install_vcrun2013 ===<br />
<br />
=== POL_Install_vcrun6 ===<br />
<br />
== VideoDriver ==<br />
<br />
POL_Call POL_Install_VideoDriver<br />
<br />
== wine64b ==<br />
<br />
POL_Call POL_Install_wine64b<br />
<br />
== wineasio ==<br />
<br />
'''What is it?'''<br />
<br />
WineASIO provides an ASIO driver interface from Wine to jack for low-latency audio and advanced audio/MIDI routing.<br />
<br />
'''What does it do?'''<br />
<br />
Checks for the following:<br />
<br />
* Checks that the virtual drive is 32-bit<br />
<br />
* Makes sure that the user is part of the ''audio'' group<br />
<br />
* Confirms the presence of ''jack'' and ''qjackctl''<br />
<br />
Then, if all checks pass, WineASIO is downloaded and registered into that virtual drive.<br />
<br />
'''When would I need it?'''<br />
<br />
Certain Adobe products require this to be installed as a dependency.<br />
<br />
'''Script/Shell command:'''<br />
<br />
<pre class="playonlinux code"><br />
POL_Call POL_Install_wineasio<br />
</pre><br />
<br />
'''Links:'''<br />
<br />
http://sourceforge.net/projects/wineasio/<br />
<br />
== winhttp ==<br />
<br />
POL_Call POL_Install_winhttp<br />
<br />
== wininet ==<br />
<br />
POL_Call POL_Install_wininet<br />
<br />
== wintrust ==<br />
<br />
POL_Call POL_Install_wintrust<br />
<br />
== wmp10 ==<br />
<br />
POL_Call POL_Install_wmp10<br />
<br />
== wmp9 ==<br />
<br />
POL_Call POL_Install_wmp9<br />
<br />
== wmpcodecs ==<br />
<br />
POL_Call POL_Install_wmpcodecs<br />
<br />
== wsh56 ==<br />
<br />
POL_Call POL_Install_wsh56<br />
<br />
== wsh57 ==<br />
<br />
POL_Call POL_Install_wsh57<br />
<br />
== xact ==<br />
<br />
POL_Call POL_Install_xact<br />
<br />
== xinput ==<br />
<br />
POL_Call POL_Install_xinput<br />
<br />
== xmllite ==<br />
<br />
POL_Call POL_Install_xmllite<br />
<br />
== xna31 ==<br />
<br />
POL_Call POL_Install_xna31<br />
<br />
== xna40 ==<br />
<br />
POL_Call POL_Install_xna40<br />
<br />
== xvid ==<br />
<br />
POL_Call POL_Install_xvid<br />
<br />
== Other Functions ==<br />
<br />
=== POL_Configurator_runparts ===<br />
<br />
POL_Call POL_Configurator_runparts<br />
<br />
=== POL_Download_retry ===<br />
<br />
POL_Call POL_Download_retry<br />
<br />
=== POL_Function_FontsSmoothBGR ===<br />
<br />
POL_Call POL_Function_FontsSmoothBGR<br />
<br />
=== POL_Function_FontsSmoothGrayScale ===<br />
<br />
POL_Call POL_Function_FontsSmoothGrayScale<br />
<br />
=== POL_Function_FontsSmoothRGB ===<br />
<br />
POL_Call POL_Function_FontsSmoothRGB<br />
<br />
=== POL_Function_NoCDWarning ===<br />
<br />
POL_Call POL_Function_NoCDWarning<br />
<br />
=== POL_Function_override_app_dlls ===<br />
<br />
POL_Call POL_Function_override_app_dlls<br />
<br />
=== POL_Function_OverrideDLL ===<br />
<br />
POL_Call POL_Function_OverrideDLL<br />
<br />
=== POL_Function_RootCommand ===<br />
<br />
POL_Call POL_Function_RootCommand<br />
<br />
=== POL_Function_sandbox ===<br />
<br />
POL_Call POL_Function_sandbox<br />
<br />
=== POL_Function_SetNativeExtension ===<br />
<br />
POL_Call POL_Function_SetNativeExtension<br />
<br />
=== POL_Function_simplecdscript ===<br />
<br />
POL_Call POL_Function_simplecdscript<br />
<br />
=== POL_Function_simplescript ===<br />
<br />
POL_Call POL_Function_simplescript<br />
<br />
=== POL_Function_Sleep ===<br />
<br />
POL_Call POL_Function_Sleep<br />
<br />
=== POL_Gamefront_Download ===<br />
<br />
POL_Call POL_Gamefront_Download<br />
<br />
=== POL_GetTool_samba3 ===<br />
<br />
POL_Call POL_GetTool_samba3<br />
<br />
=== POL_GoG_download ===<br />
<br />
POL_Call POL_GoG_download<br />
<br />
=== POL_GoG_Extract ===<br />
<br />
POL_Call POL_GoG_Extract<br />
<br />
=== POL_GoG_install ===<br />
<br />
POL_Call POL_GoG_install<br />
<br />
=== POL_GoG_setup ===<br />
<br />
POL_Call POL_GoG_setup</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=POL_%26_POM_Terminology&diff=874POL & POM Terminology2016-03-22T08:02:01Z<p>RoninDusette: /* WineBuild */</p>
<hr />
<div>== Components ==<br />
<br />
A "component" is a dependency, library, set of DLL's, etc., that Wine may need to use to get a program to run. The '''Install Components''' menu has similar functionality to other apps/scripts like ''winetricks''. If you are looking for a dependency from ''winetricks'', you will likely find it in the '''Install Components''' menu.<br />
<br />
== Installer ==<br />
A function or installer for PlayOnLinux/PlayOnMac. When you install a game or application from the '''Install''' menu, a script is downloaded and ran, which will guide you through the installation process. During installation, the installer will automatically use various functions to interact with our server and PlayOnLinux's API to gather everything needed to create a '''Virtual Drive''' to house your game or app.<br />
<br />
== Script ==<br />
<br />
A synonym of [[#installer|Installer]]<br />
<br />
== Virtual drive ==<br />
A virtual drive is simply the name that PlayOnLinux/PlayOnMac uses for a Wine '''WINEPREFIX''', which is essentially a self-contained Wine environment, complete with it's own ''drive_c'' & related folders and everything else. For more information on what a '''WINEPREFIX''' is, read [http://wiki.winehq.org/FAQ#wineprefix here].<br />
<br />
== WineBuild ==<br />
<br />
The name of the service and unofficial name of versions of Wine built specifically by our server, for use in PlayOnLinux/PlayOnMac. Just another name for "Wine version used for a POL/POM virtual drive". WineBuilds can be managed via the [[Managing Wine Versions|Manage Wine Versions]] dialogue.</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=POL_%26_POM_Terminology&diff=873POL & POM Terminology2016-03-22T08:00:24Z<p>RoninDusette: /* Installer */</p>
<hr />
<div>== Components ==<br />
<br />
A "component" is a dependency, library, set of DLL's, etc., that Wine may need to use to get a program to run. The '''Install Components''' menu has similar functionality to other apps/scripts like ''winetricks''. If you are looking for a dependency from ''winetricks'', you will likely find it in the '''Install Components''' menu.<br />
<br />
== Installer ==<br />
A function or installer for PlayOnLinux/PlayOnMac. When you install a game or application from the '''Install''' menu, a script is downloaded and ran, which will guide you through the installation process. During installation, the installer will automatically use various functions to interact with our server and PlayOnLinux's API to gather everything needed to create a '''Virtual Drive''' to house your game or app.<br />
<br />
== Script ==<br />
<br />
A synonym of [[#installer|Installer]]<br />
<br />
== Virtual drive ==<br />
A virtual drive is simply the name that PlayOnLinux/PlayOnMac uses for a Wine '''WINEPREFIX''', which is essentially a self-contained Wine environment, complete with it's own ''drive_c'' & related folders and everything else. For more information on what a '''WINEPREFIX''' is, read [http://wiki.winehq.org/FAQ#wineprefix here].<br />
<br />
== WineBuild ==<br />
<br />
The name of the service and unofficial name of version's of Wine built specifically by our server, for use in PlayOnLinux/PlayOnMac. Just another name for "Wine version used for a POL/POM virtual drive". WineBuilds can be managed via the [[Managing Wine Versions|Manage Wine Versions]] dialogue.</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=POL_%26_POM_Terminology&diff=872POL & POM Terminology2016-03-22T07:59:38Z<p>RoninDusette: /* Installer */</p>
<hr />
<div>== Components ==<br />
<br />
A "component" is a dependency, library, set of DLL's, etc., that Wine may need to use to get a program to run. The '''Install Components''' menu has similar functionality to other apps/scripts like ''winetricks''. If you are looking for a dependency from ''winetricks'', you will likely find it in the '''Install Components''' menu.<br />
<br />
== Installer ==<br />
A function or installer for PlayOnLinux/PlayOnMac. When you install a game or application from the '''Install''' menu, a script is downloaded and ran, which will guide you through the installation process. During installation, the installer will automatically use various installers to interact with our server and PlayOnLinux's API to gather everything needed to create a '''Virtual Drive''' to house your game or app.<br />
<br />
== Script ==<br />
<br />
A synonym of [[#installer|Installer]]<br />
<br />
== Virtual drive ==<br />
A virtual drive is simply the name that PlayOnLinux/PlayOnMac uses for a Wine '''WINEPREFIX''', which is essentially a self-contained Wine environment, complete with it's own ''drive_c'' & related folders and everything else. For more information on what a '''WINEPREFIX''' is, read [http://wiki.winehq.org/FAQ#wineprefix here].<br />
<br />
== WineBuild ==<br />
<br />
The name of the service and unofficial name of version's of Wine built specifically by our server, for use in PlayOnLinux/PlayOnMac. Just another name for "Wine version used for a POL/POM virtual drive". WineBuilds can be managed via the [[Managing Wine Versions|Manage Wine Versions]] dialogue.</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Installing_PlayOnMac&diff=871Installing PlayOnMac2016-03-22T06:57:32Z<p>RoninDusette: </p>
<hr />
<div>PlayOnMac installs on your system very easily. All you have to do is follow these four small steps that are described in the following section.<br />
<br />
=== Installation ===<br />
<br />
# Go [http://www.playonmac.com/en/download.html the download page PlayOnMac]<br />
# Download the latest version of PlayOnMac<br />
# Once download, install 'PlayOnMac_X.XXdmg' 'on your desktop (double click on the file)<br />
# You will find inside an uninstall software (to remove PlayOnMac your computer) and the software. You simply drag-and-drop it in your '' Applications ''<br />
<br />
=== Using GIT Version ===<br />
<br />
The git repository will always have the latest version. It is only recommended for advanced users and programmers. It has the advantage of providing an automatic update button, unlike other versions of the program. To install it on your computer, first you must install and configure git. Once this is done, you can download PlayOnMac using the following command:<br />
<br />
git clone https://github.com/PlayOnLinux/POL-POM-4<br />
<br />
{{Info|This command will download the program to your current folder. Consider making use of 'cd' before running the command to get to where you want the files to be downloaded to. }}Unlike packaged installation, this method won't install PlayOnMac system-wide<br />
<br />
{{Info|On Mac, the easier way to use the development version is to first deploy a stable version of PlayOnMac, then to replace the /Applications/PlayOnMac.app/Contents/Resources/playonlinux folder with a clone of the git repository.}}<br />
<br />
=== Next? ===<br />
Now that you have installed PlayOnMac on your computer, we suggest you read our [[First Use| guide for first use of the software]] which will explain the basics on how to install and uninstall Windows programs with PlayOnMac.</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Graphics_Card_Drivers&diff=835Graphics Card Drivers2015-06-25T18:55:44Z<p>RoninDusette: /* 32-bit Graphics Libraries */</p>
<hr />
<div>In this section, we will try to cover the basics of getting the most out of your AMD, Nvidia, or Intel graphics card on your Linux system, specifically when using Wine/PlayOnLinux. This can get pretty lengthy, so expect this article to get exponentially bigger as time goes on.<br />
<br />
{{Info|This list is going to take a while to get full, so please be patient as we populate everything.}}<br />
<br />
{{Info|Never forget that your distro's documentation will cover this information in far greater detail; it is always good to familiarize yourself with the docs for any Linux distribution or piece of software that you use}}<br />
<br />
For ease of use, we will break these down into different sections for the graphics card manufacturer, and then distro's within those categories. <br />
<br />
== 32-bit Graphics Libraries ==<br />
<br />
By far, the most common issue encountered when trying to run games through POL/POM/Wine has to be graphics drivers. Most people nowadays run 64-bit operating systems, but Wine almost always uses 32-bit Virtual Drives. These 32-bit installations in PlayOnLinux will require 32-bit versions of certain libraries on your system. As an example, if you have a 64-bit Ubuntu installation, and install a 32-bit program from PlayOnLinux (again, almost every single one is 32-bit), the program will tell Wine that it wants to speak to the 32-bit graphics libraries. Without them, they game will be grumpy or otherwise just not work.<br />
<br />
Luckily, installing the 32-bit graphics libraries for your graphics card is easy on every popular distro. [https://www.codeweavers.com/ CodeWeavers] has an excellent, short, concise article on installing these 32-bit libraries on the most popular distros. If you think that you are missing your graphics drivers or even just the 32-bit libraries for them, this is a good place to start:<br />
<br />
* https://www.codeweavers.com/support/wiki/Diag/MissingLibGL<br />
<br />
== NVIDIA ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
Most of the time, the easiest way is using the "Additional Drivers" dialogue. That does not always work though, and it sometimes will offer less-than-ideal versions of drivers for your NVIDIA card. If your card is supported by the current NVIDIA driver, the following command should pull in the required libraries:<br />
<br />
{{Console|sudo apt-get install nvidia-current}}<br />
<br />
You can also install other series of drivers (313.x, 319.x, 331.x, etc.) by appending the version name to them:<br />
<br />
'''Examples:'''<br />
<br />
{{Console|sudo apt-get install nvidia-331}}<br />
<br />
For the '''32-bit''' libraries, as long as ''libgl1-mesa-glx:i386'' and ''multiarch-support'' are installed, it should install them automatically. If, after you install them from the Ubuntu repositories, it does not show up, try to install those packages mentioned previously:<br />
<br />
{{Console|<br />
sudo apt-get install multiarch-support<br />
<br />
sudo apt-get install libgl1-mesa-glx:i386<br />
}}<br />
<br />
The manual installation is a bit more involved, but it is preferred by a lot of users.<br />
<br />
''Will add more later''<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary NVIDIA drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/NvidiaGraphicsDrivers<br />
<br />
==== Fedora ====<br />
<br />
* http://rpmfusion.org/Howto/nVidia<br />
<br />
==== Arch ====<br />
<br />
Arch Linux is pretty straightforward when it comes to this, and their documentation is quite concise. Please use the Arch Linux docs whenever possible for graphics issues:<br />
<br />
* https://wiki.archlinux.org/index.php/NVIDIA<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVidia/nvidia-drivers<br />
<br />
=== Optimus ===<br />
<br />
NVIDIA Optimus technology is a feature in laptops with newer Intel CPU's with integrated GPUs and discrete NVIDIA graphics cards that allows switching between graphics processors on-the-fly, to optimize the performance when needed, and maximizing battery life when not needing the discrete graphics card. More information on Optimus can be found here:<br />
<br />
* http://www.nvidia.com/object/optimus_technology.html<br />
<br />
==== Most distributions ====<br />
<br />
The current working solution is maintained by the '''Bumblebee Project'''. '''PRIME''' is not recommended, as it utilizes the open-source NVIDIA driver (''nouveau''), and will not give the performance desired for most games. The project's website has detailed documentation for most major distributions, so it is recommended to go by that:<br />
<br />
* http://bumblebee-project.org/<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVIDIA_Driver_with_Optimus_Laptops<br />
<br />
=== Open-Source Drivers ===<br />
<br />
Unfortunately, the open-source ''nouveau'' drivers are not really up-to-par on performance yet for gaming. Things are starting to look up, but there are a lot of caveats to running the open-source NVIDIA drivers. More information can be found here:<br />
<br />
* http://nouveau.freedesktop.org/wiki/<br />
<br />
* http://www.phoronix.com/scan.php?page=news_topic&q=Nouveau<br />
<br />
== AMD ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
As of now, the official Ubuntu docs are VERY detailed in the installation of the open-source and proprietary graphics drivers. It is recommended to use their documentation for your AMD card on the Ubuntu distros (Mint should be very similar, if not exactly the same). You can find that information here:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary AMD/ATI drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/ATIProprietary<br />
<br />
==== Fedora ====<br />
<br />
* [https://fedoraproject.org/wiki/Fglrx https://fedoraproject.org/wiki/Fglrx]<br />
<br />
==== Arch ====<br />
<br />
Arch Linux is pretty straightforward when it comes to this, and their documentation is quite concise. Please use the Arch Linux docs whenever possible for graphics issues:<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Fglrx<br />
<br />
=== Open-Source Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
We refer you to the same link:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
The installation of the open source ''radeon'' driver is straightforward, and is likely installed on your system by default. More information on the Debian ''radeon'' driver can be found here:<br />
<br />
* https://wiki.debian.org/AtiHowTo<br />
<br />
==== Fedora ====<br />
<br />
The open-source ''radeon'' driver should already be included in your system by default. If you are on a 64-bit version of Fedora, you would only need to install the 32-bit libraries for your graphics card from the Fedora repo and it should work fine with PlayOnLinux.<br />
<br />
==== Arch ====<br />
<br />
Arch Linux is pretty straightforward when it comes to this, and their documentation is quite concise. Please use the Arch Linux docs whenever possible for graphics issues:<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Radeon<br />
<br />
== Intel ==<br />
<br />
The Intel drivers are developed by the open-source community, so they are by far the easiest to install, as they pretty much will always come with your distro by default. More information on the Intel open-source drivers can be found here:<br />
<br />
* https://01.org/linuxgraphics/<br />
<br />
For the most part, this will cover how to make sure that you have the most up-to-date graphics stack for your Intel chipset. This applies exclusively to pure Intel graphics only. If you have, say, a mixed graphics card environment, like a laptop that has an Intel iGPU and a discrete NVIDIA card, please refer to the '''NVIDIA Optimus''' section<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
If you are already running a '''32-bit''' version of one of these systems, you should have everything that you need installed correctly by default. <br />
<br />
In the case of '''64-bit''' systems, you already have the 64-bit libraries for your graphics hardware. A package called '''multiarch-support''' should pull in the '''32-bit''' libraries, as well as a bunch of others.<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install multiarch-support<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
==== Debian ====<br />
<br />
The drivers should already be installed, but if it is not working with OpenGL or you get complaints about the 32-bit graphics libraries being missing, you can should try to run:<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install ia32-libs<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
If you are still having problems, consult the Debian docs here:<br />
<br />
* https://wiki.debian.org/Multiarch/HOWTO<br />
<br />
==== Fedora ====<br />
<br />
The open-source Intel driver should already be included in your system by default. If you are on a 64-bit version of Fedora, you would only need to install the 32-bit libraries for your graphics card from the Fedora repo and it should work fine with PlayOnLinux.<br />
<br />
==== Arch ====<br />
<br />
Arch Linux is pretty straightforward when it comes to this, and their documentation is quite concise. Please use the Arch Linux docs whenever possible for graphics issues:<br />
<br />
* https://wiki.archlinux.org/index.php/Intel_graphics<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Intel</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Graphics_Card_Drivers&diff=834Graphics Card Drivers2015-06-25T18:54:54Z<p>RoninDusette: </p>
<hr />
<div>In this section, we will try to cover the basics of getting the most out of your AMD, Nvidia, or Intel graphics card on your Linux system, specifically when using Wine/PlayOnLinux. This can get pretty lengthy, so expect this article to get exponentially bigger as time goes on.<br />
<br />
{{Info|This list is going to take a while to get full, so please be patient as we populate everything.}}<br />
<br />
{{Info|Never forget that your distro's documentation will cover this information in far greater detail; it is always good to familiarize yourself with the docs for any Linux distribution or piece of software that you use}}<br />
<br />
For ease of use, we will break these down into different sections for the graphics card manufacturer, and then distro's within those categories. <br />
<br />
== 32-bit Graphics Libraries ==<br />
<br />
By far, the most common issue encountered when trying to run games through POL/POM/Wine has to be graphics drivers. Most people nowadays run 64-bit operating systems, but Wine almost always uses 32-bit Virtual Drives. These 32-bit installations in PlayOnLinux will required 32-bit versions of certain libraries on your system. As an example, if you have a 64-bit Ubuntu installation, and install a 32-bit program from PlayOnLinux (again, almost every single one is 32-bit), the program will tell Wine that it wants to speak to the 32-bit graphics libraries. Without them, they game will be grumpy or otherwise just not work.<br />
<br />
Luckily, installing the 32-bit graphics libraries for your graphics card is easy on every popular distro. [https://www.codeweavers.com/ CodeWeavers] has an excellent, short, concise article on installing these 32-bit libraries on the most popular distros. If you think that you are missing your graphics drivers or even just the 32-bit libraries for them, this is a good place to start:<br />
<br />
* https://www.codeweavers.com/support/wiki/Diag/MissingLibGL<br />
<br />
== NVIDIA ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
Most of the time, the easiest way is using the "Additional Drivers" dialogue. That does not always work though, and it sometimes will offer less-than-ideal versions of drivers for your NVIDIA card. If your card is supported by the current NVIDIA driver, the following command should pull in the required libraries:<br />
<br />
{{Console|sudo apt-get install nvidia-current}}<br />
<br />
You can also install other series of drivers (313.x, 319.x, 331.x, etc.) by appending the version name to them:<br />
<br />
'''Examples:'''<br />
<br />
{{Console|sudo apt-get install nvidia-331}}<br />
<br />
For the '''32-bit''' libraries, as long as ''libgl1-mesa-glx:i386'' and ''multiarch-support'' are installed, it should install them automatically. If, after you install them from the Ubuntu repositories, it does not show up, try to install those packages mentioned previously:<br />
<br />
{{Console|<br />
sudo apt-get install multiarch-support<br />
<br />
sudo apt-get install libgl1-mesa-glx:i386<br />
}}<br />
<br />
The manual installation is a bit more involved, but it is preferred by a lot of users.<br />
<br />
''Will add more later''<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary NVIDIA drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/NvidiaGraphicsDrivers<br />
<br />
==== Fedora ====<br />
<br />
* http://rpmfusion.org/Howto/nVidia<br />
<br />
==== Arch ====<br />
<br />
Arch Linux is pretty straightforward when it comes to this, and their documentation is quite concise. Please use the Arch Linux docs whenever possible for graphics issues:<br />
<br />
* https://wiki.archlinux.org/index.php/NVIDIA<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVidia/nvidia-drivers<br />
<br />
=== Optimus ===<br />
<br />
NVIDIA Optimus technology is a feature in laptops with newer Intel CPU's with integrated GPUs and discrete NVIDIA graphics cards that allows switching between graphics processors on-the-fly, to optimize the performance when needed, and maximizing battery life when not needing the discrete graphics card. More information on Optimus can be found here:<br />
<br />
* http://www.nvidia.com/object/optimus_technology.html<br />
<br />
==== Most distributions ====<br />
<br />
The current working solution is maintained by the '''Bumblebee Project'''. '''PRIME''' is not recommended, as it utilizes the open-source NVIDIA driver (''nouveau''), and will not give the performance desired for most games. The project's website has detailed documentation for most major distributions, so it is recommended to go by that:<br />
<br />
* http://bumblebee-project.org/<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVIDIA_Driver_with_Optimus_Laptops<br />
<br />
=== Open-Source Drivers ===<br />
<br />
Unfortunately, the open-source ''nouveau'' drivers are not really up-to-par on performance yet for gaming. Things are starting to look up, but there are a lot of caveats to running the open-source NVIDIA drivers. More information can be found here:<br />
<br />
* http://nouveau.freedesktop.org/wiki/<br />
<br />
* http://www.phoronix.com/scan.php?page=news_topic&q=Nouveau<br />
<br />
== AMD ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
As of now, the official Ubuntu docs are VERY detailed in the installation of the open-source and proprietary graphics drivers. It is recommended to use their documentation for your AMD card on the Ubuntu distros (Mint should be very similar, if not exactly the same). You can find that information here:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary AMD/ATI drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/ATIProprietary<br />
<br />
==== Fedora ====<br />
<br />
* [https://fedoraproject.org/wiki/Fglrx https://fedoraproject.org/wiki/Fglrx]<br />
<br />
==== Arch ====<br />
<br />
Arch Linux is pretty straightforward when it comes to this, and their documentation is quite concise. Please use the Arch Linux docs whenever possible for graphics issues:<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Fglrx<br />
<br />
=== Open-Source Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
We refer you to the same link:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
The installation of the open source ''radeon'' driver is straightforward, and is likely installed on your system by default. More information on the Debian ''radeon'' driver can be found here:<br />
<br />
* https://wiki.debian.org/AtiHowTo<br />
<br />
==== Fedora ====<br />
<br />
The open-source ''radeon'' driver should already be included in your system by default. If you are on a 64-bit version of Fedora, you would only need to install the 32-bit libraries for your graphics card from the Fedora repo and it should work fine with PlayOnLinux.<br />
<br />
==== Arch ====<br />
<br />
Arch Linux is pretty straightforward when it comes to this, and their documentation is quite concise. Please use the Arch Linux docs whenever possible for graphics issues:<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Radeon<br />
<br />
== Intel ==<br />
<br />
The Intel drivers are developed by the open-source community, so they are by far the easiest to install, as they pretty much will always come with your distro by default. More information on the Intel open-source drivers can be found here:<br />
<br />
* https://01.org/linuxgraphics/<br />
<br />
For the most part, this will cover how to make sure that you have the most up-to-date graphics stack for your Intel chipset. This applies exclusively to pure Intel graphics only. If you have, say, a mixed graphics card environment, like a laptop that has an Intel iGPU and a discrete NVIDIA card, please refer to the '''NVIDIA Optimus''' section<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
If you are already running a '''32-bit''' version of one of these systems, you should have everything that you need installed correctly by default. <br />
<br />
In the case of '''64-bit''' systems, you already have the 64-bit libraries for your graphics hardware. A package called '''multiarch-support''' should pull in the '''32-bit''' libraries, as well as a bunch of others.<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install multiarch-support<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
==== Debian ====<br />
<br />
The drivers should already be installed, but if it is not working with OpenGL or you get complaints about the 32-bit graphics libraries being missing, you can should try to run:<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install ia32-libs<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
If you are still having problems, consult the Debian docs here:<br />
<br />
* https://wiki.debian.org/Multiarch/HOWTO<br />
<br />
==== Fedora ====<br />
<br />
The open-source Intel driver should already be included in your system by default. If you are on a 64-bit version of Fedora, you would only need to install the 32-bit libraries for your graphics card from the Fedora repo and it should work fine with PlayOnLinux.<br />
<br />
==== Arch ====<br />
<br />
Arch Linux is pretty straightforward when it comes to this, and their documentation is quite concise. Please use the Arch Linux docs whenever possible for graphics issues:<br />
<br />
* https://wiki.archlinux.org/index.php/Intel_graphics<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Intel</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Graphics_Card_Drivers&diff=833Graphics Card Drivers2015-06-25T18:46:07Z<p>RoninDusette: /* Debian */</p>
<hr />
<div>In this section, we will try to cover the basics of getting the most out of your AMD, Nvidia, or Intel graphics card on your Linux system, specifically when using Wine/PlayOnLinux. This can get pretty lengthy, so expect this article to get exponentially bigger as time goes on.<br />
<br />
{{Info|This list is going to take a while to get full, so please be patient as we populate everything.}}<br />
<br />
For ease of use, we will break these down into different sections for the graphics card manufacturer, and then distro's within those categories. <br />
<br />
== NVIDIA ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
Most of the time, the easiest way is using the "Additional Drivers" dialogue. That does not always work though, and it sometimes will offer less-than-ideal versions of drivers for your NVIDIA card. If your card is supported by the current NVIDIA driver, the following command should pull in the required libraries:<br />
<br />
{{Console|sudo apt-get install nvidia-current}}<br />
<br />
You can also install other series of drivers (313.x, 319.x, 331.x, etc.) by appending the version name to them:<br />
<br />
'''Examples:'''<br />
<br />
{{Console|sudo apt-get install nvidia-331}}<br />
<br />
For the '''32-bit''' libraries, as long as ''libgl1-mesa-glx:i386'' and ''multiarch-support'' are installed, it should install them automatically. If, after you install them from the Ubuntu repositories, it does not show up, try to install those packages mentioned previously:<br />
<br />
{{Console|<br />
sudo apt-get install multiarch-support<br />
<br />
sudo apt-get install libgl1-mesa-glx:i386<br />
}}<br />
<br />
The manual installation is a bit more involved, but it is preferred by a lot of users.<br />
<br />
''Will add more later''<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary NVIDIA drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/NvidiaGraphicsDrivers<br />
<br />
==== Fedora ====<br />
<br />
* http://rpmfusion.org/Howto/nVidia<br />
<br />
==== Arch ====<br />
<br />
Arch Linux is pretty straightforward when it comes to this, and their documentation is quite concise. Please use the Arch Linux docs whenever possible for graphics issues:<br />
<br />
* https://wiki.archlinux.org/index.php/NVIDIA<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVidia/nvidia-drivers<br />
<br />
=== Optimus ===<br />
<br />
NVIDIA Optimus technology is a feature in laptops with newer Intel CPU's with integrated GPUs and discrete NVIDIA graphics cards that allows switching between graphics processors on-the-fly, to optimize the performance when needed, and maximizing battery life when not needing the discrete graphics card. More information on Optimus can be found here:<br />
<br />
* http://www.nvidia.com/object/optimus_technology.html<br />
<br />
==== Most distributions ====<br />
<br />
The current working solution is maintained by the '''Bumblebee Project'''. '''PRIME''' is not recommended, as it utilizes the open-source NVIDIA driver (''nouveau''), and will not give the performance desired for most games. The project's website has detailed documentation for most major distributions, so it is recommended to go by that:<br />
<br />
* http://bumblebee-project.org/<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVIDIA_Driver_with_Optimus_Laptops<br />
<br />
=== Open-Source Drivers ===<br />
<br />
Unfortunately, the open-source ''nouveau'' drivers are not really up-to-par on performance yet for gaming. Things are starting to look up, but there are a lot of caveats to running the open-source NVIDIA drivers. More information can be found here:<br />
<br />
* http://nouveau.freedesktop.org/wiki/<br />
<br />
* http://www.phoronix.com/scan.php?page=news_topic&q=Nouveau<br />
<br />
== AMD ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
As of now, the official Ubuntu docs are VERY detailed in the installation of the open-source and proprietary graphics drivers. It is recommended to use their documentation for your AMD card on the Ubuntu distros (Mint should be very similar, if not exactly the same). You can find that information here:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary AMD/ATI drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/ATIProprietary<br />
<br />
==== Fedora ====<br />
<br />
* [https://fedoraproject.org/wiki/Fglrx https://fedoraproject.org/wiki/Fglrx]<br />
<br />
==== Arch ====<br />
<br />
Arch Linux is pretty straightforward when it comes to this, and their documentation is quite concise. Please use the Arch Linux docs whenever possible for graphics issues:<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Fglrx<br />
<br />
=== Open-Source Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
We refer you to the same link:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
The installation of the open source ''radeon'' driver is straightforward, and is likely installed on your system by default. More information on the Debian ''radeon'' driver can be found here:<br />
<br />
* https://wiki.debian.org/AtiHowTo<br />
<br />
==== Fedora ====<br />
<br />
The open-source ''radeon'' driver should already be included in your system by default. If you are on a 64-bit version of Fedora, you would only need to install the 32-bit libraries for your graphics card from the Fedora repo and it should work fine with PlayOnLinux.<br />
<br />
==== Arch ====<br />
<br />
Arch Linux is pretty straightforward when it comes to this, and their documentation is quite concise. Please use the Arch Linux docs whenever possible for graphics issues:<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Radeon<br />
<br />
== Intel ==<br />
<br />
The Intel drivers are developed by the open-source community, so they are by far the easiest to install, as they pretty much will always come with your distro by default. More information on the Intel open-source drivers can be found here:<br />
<br />
* https://01.org/linuxgraphics/<br />
<br />
For the most part, this will cover how to make sure that you have the most up-to-date graphics stack for your Intel chipset. This applies exclusively to pure Intel graphics only. If you have, say, a mixed graphics card environment, like a laptop that has an Intel iGPU and a discrete NVIDIA card, please refer to the '''NVIDIA Optimus''' section<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
If you are already running a '''32-bit''' version of one of these systems, you should have everything that you need installed correctly by default. <br />
<br />
In the case of '''64-bit''' systems, you already have the 64-bit libraries for your graphics hardware. A package called '''multiarch-support''' should pull in the '''32-bit''' libraries, as well as a bunch of others.<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install multiarch-support<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
==== Debian ====<br />
<br />
The drivers should already be installed, but if it is not working with OpenGL or you get complaints about the 32-bit graphics libraries being missing, you can should try to run:<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install ia32-libs<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
If you are still having problems, consult the Debian docs here:<br />
<br />
* https://wiki.debian.org/Multiarch/HOWTO<br />
<br />
==== Fedora ====<br />
<br />
The open-source Intel driver should already be included in your system by default. If you are on a 64-bit version of Fedora, you would only need to install the 32-bit libraries for your graphics card from the Fedora repo and it should work fine with PlayOnLinux.<br />
<br />
==== Arch ====<br />
<br />
Arch Linux is pretty straightforward when it comes to this, and their documentation is quite concise. Please use the Arch Linux docs whenever possible for graphics issues:<br />
<br />
* https://wiki.archlinux.org/index.php/Intel_graphics<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Intel</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Graphics_Card_Drivers&diff=832Graphics Card Drivers2015-06-25T15:57:47Z<p>RoninDusette: /* Debian */</p>
<hr />
<div>In this section, we will try to cover the basics of getting the most out of your AMD, Nvidia, or Intel graphics card on your Linux system, specifically when using Wine/PlayOnLinux. This can get pretty lengthy, so expect this article to get exponentially bigger as time goes on.<br />
<br />
{{Info|This list is going to take a while to get full, so please be patient as we populate everything.}}<br />
<br />
For ease of use, we will break these down into different sections for the graphics card manufacturer, and then distro's within those categories. <br />
<br />
== NVIDIA ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
Most of the time, the easiest way is using the "Additional Drivers" dialogue. That does not always work though, and it sometimes will offer less-than-ideal versions of drivers for your NVIDIA card. If your card is supported by the current NVIDIA driver, the following command should pull in the required libraries:<br />
<br />
{{Console|sudo apt-get install nvidia-current}}<br />
<br />
You can also install other series of drivers (313.x, 319.x, 331.x, etc.) by appending the version name to them:<br />
<br />
'''Examples:'''<br />
<br />
{{Console|sudo apt-get install nvidia-331}}<br />
<br />
For the '''32-bit''' libraries, as long as ''libgl1-mesa-glx:i386'' and ''multiarch-support'' are installed, it should install them automatically. If, after you install them from the Ubuntu repositories, it does not show up, try to install those packages mentioned previously:<br />
<br />
{{Console|<br />
sudo apt-get install multiarch-support<br />
<br />
sudo apt-get install libgl1-mesa-glx:i386<br />
}}<br />
<br />
The manual installation is a bit more involved, but it is preferred by a lot of users.<br />
<br />
''Will add more later''<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary NVIDIA drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/NvidiaGraphicsDrivers<br />
<br />
If you are experiencing issues with missing 32-bit graphics libraries, you can check the following link. CodeWeavers has a list of the repo package names for the 64-bit and 32-bit drivers for multiple distros, including Debian:<br />
<br />
* https://www.codeweavers.com/support/wiki/Diag/MissingLibGL<br />
<br />
==== Fedora ====<br />
<br />
* http://rpmfusion.org/Howto/nVidia<br />
<br />
==== Arch ====<br />
<br />
Arch Linux is pretty straightforward when it comes to this, and their documentation is quite concise. Please use the Arch Linux docs whenever possible for graphics issues:<br />
<br />
* https://wiki.archlinux.org/index.php/NVIDIA<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVidia/nvidia-drivers<br />
<br />
=== Optimus ===<br />
<br />
NVIDIA Optimus technology is a feature in laptops with newer Intel CPU's with integrated GPUs and discrete NVIDIA graphics cards that allows switching between graphics processors on-the-fly, to optimize the performance when needed, and maximizing battery life when not needing the discrete graphics card. More information on Optimus can be found here:<br />
<br />
* http://www.nvidia.com/object/optimus_technology.html<br />
<br />
==== Most distributions ====<br />
<br />
The current working solution is maintained by the '''Bumblebee Project'''. '''PRIME''' is not recommended, as it utilizes the open-source NVIDIA driver (''nouveau''), and will not give the performance desired for most games. The project's website has detailed documentation for most major distributions, so it is recommended to go by that:<br />
<br />
* http://bumblebee-project.org/<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVIDIA_Driver_with_Optimus_Laptops<br />
<br />
=== Open-Source Drivers ===<br />
<br />
Unfortunately, the open-source ''nouveau'' drivers are not really up-to-par on performance yet for gaming. Things are starting to look up, but there are a lot of caveats to running the open-source NVIDIA drivers. More information can be found here:<br />
<br />
* http://nouveau.freedesktop.org/wiki/<br />
<br />
* http://www.phoronix.com/scan.php?page=news_topic&q=Nouveau<br />
<br />
== AMD ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
As of now, the official Ubuntu docs are VERY detailed in the installation of the open-source and proprietary graphics drivers. It is recommended to use their documentation for your AMD card on the Ubuntu distros (Mint should be very similar, if not exactly the same). You can find that information here:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary AMD/ATI drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/ATIProprietary<br />
<br />
==== Fedora ====<br />
<br />
* [https://fedoraproject.org/wiki/Fglrx https://fedoraproject.org/wiki/Fglrx]<br />
<br />
==== Arch ====<br />
<br />
Arch Linux is pretty straightforward when it comes to this, and their documentation is quite concise. Please use the Arch Linux docs whenever possible for graphics issues:<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Fglrx<br />
<br />
=== Open-Source Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
We refer you to the same link:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
The installation of the open source ''radeon'' driver is straightforward, and is likely installed on your system by default. More information on the Debian ''radeon'' driver can be found here:<br />
<br />
* https://wiki.debian.org/AtiHowTo<br />
<br />
==== Fedora ====<br />
<br />
The open-source ''radeon'' driver should already be included in your system by default. If you are on a 64-bit version of Fedora, you would only need to install the 32-bit libraries for your graphics card from the Fedora repo and it should work fine with PlayOnLinux.<br />
<br />
==== Arch ====<br />
<br />
Arch Linux is pretty straightforward when it comes to this, and their documentation is quite concise. Please use the Arch Linux docs whenever possible for graphics issues:<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Radeon<br />
<br />
== Intel ==<br />
<br />
The Intel drivers are developed by the open-source community, so they are by far the easiest to install, as they pretty much will always come with your distro by default. More information on the Intel open-source drivers can be found here:<br />
<br />
* https://01.org/linuxgraphics/<br />
<br />
For the most part, this will cover how to make sure that you have the most up-to-date graphics stack for your Intel chipset. This applies exclusively to pure Intel graphics only. If you have, say, a mixed graphics card environment, like a laptop that has an Intel iGPU and a discrete NVIDIA card, please refer to the '''NVIDIA Optimus''' section<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
If you are already running a '''32-bit''' version of one of these systems, you should have everything that you need installed correctly by default. <br />
<br />
In the case of '''64-bit''' systems, you already have the 64-bit libraries for your graphics hardware. A package called '''multiarch-support''' should pull in the '''32-bit''' libraries, as well as a bunch of others.<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install multiarch-support<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
==== Debian ====<br />
<br />
The drivers should already be installed, but if it is not working with OpenGL or you get complaints about the 32-bit graphics libraries being missing, you can should try to run:<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install ia32-libs<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
If you are still having problems, consult the Debian docs here:<br />
<br />
* https://wiki.debian.org/Multiarch/HOWTO<br />
<br />
==== Fedora ====<br />
<br />
The open-source Intel driver should already be included in your system by default. If you are on a 64-bit version of Fedora, you would only need to install the 32-bit libraries for your graphics card from the Fedora repo and it should work fine with PlayOnLinux.<br />
<br />
==== Arch ====<br />
<br />
Arch Linux is pretty straightforward when it comes to this, and their documentation is quite concise. Please use the Arch Linux docs whenever possible for graphics issues:<br />
<br />
* https://wiki.archlinux.org/index.php/Intel_graphics<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Intel</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Troubleshooting_Common_Problems&diff=831Troubleshooting Common Problems2015-06-22T19:37:31Z<p>RoninDusette: /* Common solutions */</p>
<hr />
<div>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.<br />
<br />
When trying a possible solution for an issue, please only try '''ONE''' solution at a time, and test to see if it worked. <br />
<br />
== p11-kit: couldn't load module: ... ==<br />
<br />
=== Error ===<br />
<br />
{{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}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Mostly users of Debian, Ubuntu, Kubuntu, etc., Mint (and derivatives), 64-bit systems.<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== Install 32-bit version of p11-kit-trust.so ====<br />
<br />
<pre class='code bash'><br />
sudo apt-get install p11-kit-modules:i386<br />
</pre><br />
<br />
==== Create a symlink ====<br />
<br />
''found at http://askubuntu.com/a/384018''<br />
<br />
<pre class='code bash'><br />
sudo /usr/local/bin/getlibs -p p11-kit:i386<br />
sudo ln -s /usr/lib32/i386-linux-gnu/pkcs11/p11-kit-trust.so /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so<br />
</pre><br />
<br />
== Error in FS_Check ==<br />
<br />
=== Error ===<br />
<br />
{{Console|The following file is located on a fuse filesystem. It might prevent wine from working}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Anyone trying to run an executable file in Wine/POL that is located on an NTFS filesystem.<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== Move executable to a native Linux filesystem ====<br />
<br />
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.<br />
<br />
== Failed to use ICMP ==<br />
<br />
=== Error ===<br />
<br />
{{Console|err:winediag:IcmpCreateFile Failed to use ICMP (network ping), this requires special permissions.<br />
}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
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.<br />
<br />
=== What causes this error? ===<br />
<br />
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? ;)<br />
<br />
=== Common solutions ===<br />
<br />
==== Switch to WineBuild ''1.7.45-staging'' or higher ====<br />
<br />
There is a fix for this in the Wine-Staging builds found in '''Manage Wine Versions''', so that should be tried first.<br />
<br />
==== Give rights to POL's WineBuild ====<br />
<br />
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.<br />
<br />
For instance, '''AION'''.<br />
<br />
All of POL's WineBuilds are stored in ~/.PlayOnLinux/wine/<br />
<br />
Within this folder, you have different sub-folders for architecture, and then Wine version. In the case of '''AION''':<br />
<br />
{{Console|/home/username/.PlayOnLinux/wine/linux-x86/1.7.36}}<br />
<br />
Find out which Wine version your application needs:<br />
<br />
# Open the Configuration Window<br />
# In the General tab, when your virtual drive is selected, look at the name of the version of Wine in use. <br />
<br />
Now, the command you would want to run is:<br />
<br />
'''NOTE''': ''Do NOT copy and paste these commands. They need to be modified for your particular situation.''<br />
<br />
{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine}}<br />
<br />
or<br />
<br />
{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine-preloader}}<br />
<br />
'''NOTE:''' ''I have seen both bin/wine and bin/wine-preloader shown in examples, so for posterity, I am including both.''<br />
<br />
Essentially, the syntax for this is as follows:<br />
<br />
{{Console|sudo setcap cap_net_raw+epi /home/'''username'''/.PlayOnLinux/wine/'''WineArchitecture'''/'''WineVersion'''/bin/wine}}<br />
<br />
Replace: <br />
<br />
* '''username''' with your current username<br />
<br />
* '''Wine Architecture''' with either '''linux-x86''' (32-bit virtual drive) or '''linux-amd64''' (64-bit virtual drive)<br />
<br />
* '''Wine Version''' with the '''EXACT''' name listed in the '''Wine dropdown menu''' in the '''General tab''' of the ''' Configuration Window'''<br />
<br />
== Error! Files mismatch ==<br />
<br />
=== Error ===<br />
<br />
{{Console|''someurl''<br />
<br />
<br />
Error! Files mismatch<br />
<br />
<br />
Local: ''md5resultexpected''<br />
<br />
Server: ''md5resultdownloaded''<br />
<br />
<br />
<br />
Do you want to retry?<br />
}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
This can happen to any user on any system. It is also architecture agnostic.<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== File bug report with POL ====<br />
<br />
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.).<br />
<br />
== The application you are trying to install needs administrator rights... ==<br />
<br />
=== Error ===<br />
<br />
{{Console|The application you are trying to install needs administrator rights to function correctly.}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Anyone on any distro may see this error<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== File bug report with WineHQ ====<br />
<br />
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:<br />
<br />
* [https://bugs.winehq.org/ WineHQ's Bugzilla]<br />
<br />
== League of Legends Stuck on Logo (after Champ Select) ==<br />
<br />
=== Error ===<br />
<br />
League of Legends simply stalls at the logo after the champion select dialogue.<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Anyone on any distro may see this error<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== Install needed components ====<br />
<br />
Instructions adapted from this thread:<br />
<br />
[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]<br />
<br />
# Install in POL: d3dx10, d3dx11, d3dx9 (only d3dx9, not the other d3dx9_etc) and directx9<br />
# 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"<br />
<br />
== PlayOnMac: SECUR32_initNTLMSP ntlm_auth was not found or is outdated ==<br />
<br />
=== Error ===<br />
<br />
{{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.}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
PlayOnMac users, even if Samba and winbind are installed.<br />
<br />
=== What causes this error? ===<br />
<br />
PlayOnMac is not reading the correct path for some reason.<br />
<br />
=== Common solutions ===<br />
<br />
==== Edit PlayOnMac Bash script to properly set path ====<br />
<br />
Instructions adapted from this thread:<br />
<br />
[https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html]<br />
<br />
# Edit ''/Applications/PlayOnMac.app/Contents/MacOS/playonmac''<br />
# Change ''#!/bin/bash'' to ''#!/bin/bash --login'', save, and try to start PlayOnMac<br />
<br />
== No sound (err:module:load_builtin_dll... libasound.so.2...) ==<br />
<br />
=== Error ===<br />
<br />
{{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.}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Any user on any system may experience this.<br />
<br />
=== What causes this error? ===<br />
<br />
Missing 32-bit library; in this case, ''libasound2''.<br />
<br />
=== Common solutions ===<br />
<br />
==== Install the 32-bit version of libasound2 ====<br />
<br />
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.).</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Building_PlayOnLinux_5&diff=829Building PlayOnLinux 52015-06-09T16:30:18Z<p>RoninDusette: /* On Arch */</p>
<hr />
<div>This page explains how to build PlayOnLinux 5 <br />
<br />
== On Ubuntu 14.10 ==<br />
<br />
=== Dependencies ===<br />
First, install the following dependencies: <br />
* maven2<br />
* openjdk-8-jdk<br />
* openjfx<br />
<br />
=== Compile PlayOnLinux 5===<br />
Clone the repository:{{Console|git clone https://github.com/PlayOnLinux/POL-POM-5}}Use the right Java version:{{Console|1 = export JAVA_HOME="/usr/lib/jvm/java-8-openjdk-amd64"}}Compile PlayOnLinux 5 with Maven: {{Console|cd POL-POM-5}}<br />
{{Console|mvn2 assembly:assembly}}<br />
<br />
{{Info|If you are using Oracle JDK, the home path will be /usr/lib/jvm/java-8-oracle}}<br />
{{Info|On some distributions, mvn2 is simply named mvn}}<br />
<br />
=== Run PlayOnLinux 5 ===<br />
Run the previously built jar file{{Console|java -jar target/playonlinux-5.0-SNAPSHOT-jar-with-dependencies.jar }}<br />
<br />
== On Arch ==<br />
<br />
{{Info|The following has only been tested on 64-bit Arch installs.}}<br />
<br />
=== Dependencies ===<br />
First, install the following dependencies: <br />
* maven<br />
* jdk8-openjdk<br />
* java-openjfx<br />
* gradle-1.8 (AUR)<br />
<br />
<br />
{{Info|You will need to set JAVA_HOME to "/usr/lib/jvm/java-8-openjdk" after installing ''jdk8-openjdk'', but before installing ''openjfx''.}}<br />
<br />
=== Compile PlayOnLinux 5===<br />
<br />
Clone the repository:{{Console|git clone https://github.com/PlayOnLinux/POL-POM-5}}<br />
<br />
Use the right Java version:{{Console|1 = export JAVA_HOME="/usr/lib/jvm/java-8-openjdk"}}<br />
<br />
Compile PlayOnLinux 5 with Maven: <br />
<br />
{{Console|cd POL-POM-5}}<br />
<br />
{{Console|mvn assembly:assembly}}<br />
<br />
{{Info|If you are using Oracle JDK, the home path will be /usr/lib/jvm/java-8-oracle}}<br />
<br />
=== Run PlayOnLinux 5 ===<br />
Run the previously built jar file{{Console|java -jar target/playonlinux-5.0-SNAPSHOT-jar-with-dependencies.jar }}<br />
<br />
[[Category:PlayOnLinux development]]</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Building_PlayOnLinux_5&diff=826Building PlayOnLinux 52015-05-26T21:16:00Z<p>RoninDusette: /* Compile PlayOnLinux 5 */</p>
<hr />
<div>This page explains how to build PlayOnLinux 5 <br />
<br />
== On Ubuntu 14.10 ==<br />
<br />
=== Dependencies ===<br />
First, install the following dependencies: <br />
* maven2<br />
* openjdk-8-jdk<br />
* openjfx<br />
<br />
=== Compile PlayOnLinux 5===<br />
Clone the repository:{{Console|git clone https://github.com/PlayOnLinux/POL-POM-5}}Use the right Java version:{{Console|1 = export JAVA_HOME="/usr/lib/jvm/java-8-openjdk-amd64"}}Compile PlayOnLinux 5 with Maven: {{Console|cd POL-POM-5}}<br />
{{Console|mvn2 assembly:assembly}}<br />
<br />
{{Info|If you are using Oracle JDK, the home path will be /usr/lib/jvm/java-8-oracle}}<br />
{{Info|On some distributions, mvn2 is simply named mvn}}<br />
<br />
=== Run PlayOnLinux 5 ===<br />
Run the previously built jar file{{Console|java -jar target/playonlinux-5.0-SNAPSHOT-jar-with-dependencies.jar }}<br />
<br />
== On Arch ==<br />
<br />
{{Info|The following has only been tested on 64-bit Arch installs.}}<br />
<br />
=== Dependencies ===<br />
First, install the following dependencies: <br />
* maven<br />
* jdk8-openjdk <br />
* gradle-1.8 (AUR)<br />
* openjfx (AUR)<br />
<br />
<br />
{{Info|You will need to set JAVA_HOME to "/usr/lib/jvm/java-8-openjdk" after installing ''jdk8-openjdk'', but before installing ''openjfx''.}}<br />
<br />
=== Compile PlayOnLinux 5===<br />
<br />
Clone the repository:{{Console|git clone https://github.com/PlayOnLinux/POL-POM-5}}<br />
<br />
Use the right Java version:{{Console|1 = export JAVA_HOME="/usr/lib/jvm/java-8-openjdk"}}<br />
<br />
Compile PlayOnLinux 5 with Maven: <br />
<br />
{{Console|cd POL-POM-5}}<br />
<br />
{{Console|mvn assembly:assembly}}<br />
<br />
{{Info|If you are using Oracle JDK, the home path will be /usr/lib/jvm/java-8-oracle}}<br />
<br />
=== Run PlayOnLinux 5 ===<br />
Run the previously built jar file{{Console|java -jar target/playonlinux-5.0-SNAPSHOT-jar-with-dependencies.jar }}<br />
<br />
[[Category:PlayOnLinux development]]</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Main_Page&diff=821Main Page2015-05-22T00:43:12Z<p>RoninDusette: /* PlayOnLinux 5 Development */</p>
<hr />
<div>Welcome to the PlayOnLinux and PlayOnMac wiki. Here you will find tutorials regarding the use of PlayOnLinux or PlayOnMac, and explanations of their various features. You'll also find guides explaining how to create installation scripts, a description of the commands available, API documentation, advanced topics, and more.<br />
<br />
For any additional questions that do not have an answer in this wiki, do not hesitate to go to the [https://www.playonlinux.com/en/forums.html forums].<br />
<br />
== User Documentation ==<br />
* [[Installing PlayOnLinux]]<br />
* [[Installing PlayOnMac]]<br />
* [[First Use|Guide for first use of the software]]<br />
* [[The Configuration Window|The Configuration Window]]<br />
* [[The PlayOnLinux Filesystem|The PlayOnLinux Filesystem]]<br />
* [[The PlayOnMac Filesystem|The PlayOnMac Filesystem]]<br />
* [[Managing Wine Versions|Managing Wine Versions]]<br />
* [[Manual Installations|Manual Installations]]<br />
* [[Components and Functions|Components and Functions]]<br />
* [[FAQ|Frequently Asked Questions]]<br />
<br />
== Troubleshooting ==<br />
* [[Troubleshooting Common Problems|Troubleshooting Common Problems]]<br />
* [[Graphics Card Drivers|Graphics Card Drivers]]<br />
* [[How to Read Debug Logs|How to Read Debug Logs]]<br />
* [[Common Linux Libraries That Wine Might Need|Common Linux Libraries That Wine Might Need]]<br />
<br />
== The Forums, Bug Reports, and Script Contribution ==<br />
* [[How to Post in the Forums|How to Post in the Forums]]<br />
* [[How to Post a Bug Report|How to Post a Bug Report]]<br />
* [[How to Contribute a Script|How to Contribute a Script]]<br />
* [[How to Request a Patched Version of Wine|How to Request a Patched Version of Wine]]<br />
<br />
== Writing a script ==<br />
* [[Scripting - Chapter 1: Getting to know Bash|Chapter 1: Getting to know Bash]]<br />
* [[Scripting - Chapter 2: Basic Functions|Chapter 2: Basic Functions]]<br />
* [[Scripting - Chapter 3: Variables|Chapter 3: Variables]]<br />
* [[Scripting - Chapter 4: Conditions|Chapter 4: Conditions]]<br />
* [[Scripting - Chapter 5: Wine|Chapter 5: Wine]]<br />
* [[Scripting - Chapter 6: The Filesystem|Chapter 6: The Filesystem]]<br />
* [[Scripting - Chapter 7: Installation Media|Chapter 7: Installation Media]]<br />
* [[Scripting - Chapter 8: My First Real Script|Chapter 8: My First Real Script]]<br />
* [[Scripting - Chapter 9: Standardization|Chapter 9: Standardization]]<br />
* [[Scripting - Chapter 10: Script Translation|Chapter 10: Script Translation]]<br />
* [[Scripting - Chapter 11: List of Functions|Chapter 11: List of Functions]]<br />
== Glossary ==<br />
* [[POL & POM Terminology|POL & POM Terminology]]<br />
* [[Wine; what is it?|Wine; what is it?]]<br />
<br />
== Advanced PlayOnLinux ==<br />
* [[How to move PlayOnLinux virtual drives to another disk|How to move PlayOnLinux virtual drives to another disk]]<br />
* [[PlayOnLinux DOSBox support HOWTO]]<br />
* [https://github.com/PlayOnLinux/POL-POM-4 PlayOnLinux/PlayOnMac source code]<br />
* [https://github.com/PlayOnLinux/wine-patches Patch repository]<br />
* [[Setting up WineASIO with PlayOnLinux|Setting up WineASIO with PlayOnLinux]]<br />
<br />
== Advanced PlayOnMac ==<br />
<br />
* [https://github.com/PlayOnLinux/POL-POM-4 PlayOnLinux/PlayOnMac source code]<br />
* [https://github.com/PlayOnLinux/wine-patches Patch repository]<br />
<br />
== PlayOnLinux 5 Development ==<br />
<br />
POL 5 is currently under development, and there are new tools available to track and contribute the code for this new version. Development is very active at the moment, so feel free to check out the following resources to see if there is anything you would like to contribute (or if you just feel like checking out the development process and status).<br />
<br />
* [https://github.com/PlayOnLinux/POL-POM-5/ POL 5 GitHub Repository]<br />
* [http://www.playonlinux.org:8080/ Jenkins Automated Testing Interface]<br />
* [http://www.playonlinux.org:9000/ SonarQube Code-Quality Interface]<br />
* [http://wiki.playonlinux.com/index.php/Building_PlayOnLinux_5 Building PlayOnLinux 5 Development Version]<br />
<br />
== Advanced Wine ==<br />
''' Wine-Wiki '''<br />
<br />
* [http://wine-wiki.org/ Wine-wiki. Somewhat outdated, but covers a LOT of advanced Wine topics]<br />
<br />
''' WineHQ '''<br />
<br />
* [https://www.winehq.org/devel/ Wine development links]<br />
* [http://wiki.winehq.org/DeveloperFaq Wine developer FAQ]<br />
* [https://www.winehq.org/docs/winedev-guide/index Wine developer's guide]<br />
* [http://wiki.winehq.org/Developers-Hints Wine developer hints]<br />
* [http://wiki.winehq.org/HackingTips Wine hacking tips]<br />
<br />
== Advanced WineBuild ==<br />
* [[Cross-compile Wine for OSX on Linux| How to cross-compile Wine for Mac OSX on Linux]]<br />
* [https://github.com/PlayOnLinux/WineBuild POL's WineBuild source code]</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Main_Page&diff=820Main Page2015-05-22T00:42:52Z<p>RoninDusette: /* PlayOnLinux 5 Development */</p>
<hr />
<div>Welcome to the PlayOnLinux and PlayOnMac wiki. Here you will find tutorials regarding the use of PlayOnLinux or PlayOnMac, and explanations of their various features. You'll also find guides explaining how to create installation scripts, a description of the commands available, API documentation, advanced topics, and more.<br />
<br />
For any additional questions that do not have an answer in this wiki, do not hesitate to go to the [https://www.playonlinux.com/en/forums.html forums].<br />
<br />
== User Documentation ==<br />
* [[Installing PlayOnLinux]]<br />
* [[Installing PlayOnMac]]<br />
* [[First Use|Guide for first use of the software]]<br />
* [[The Configuration Window|The Configuration Window]]<br />
* [[The PlayOnLinux Filesystem|The PlayOnLinux Filesystem]]<br />
* [[The PlayOnMac Filesystem|The PlayOnMac Filesystem]]<br />
* [[Managing Wine Versions|Managing Wine Versions]]<br />
* [[Manual Installations|Manual Installations]]<br />
* [[Components and Functions|Components and Functions]]<br />
* [[FAQ|Frequently Asked Questions]]<br />
<br />
== Troubleshooting ==<br />
* [[Troubleshooting Common Problems|Troubleshooting Common Problems]]<br />
* [[Graphics Card Drivers|Graphics Card Drivers]]<br />
* [[How to Read Debug Logs|How to Read Debug Logs]]<br />
* [[Common Linux Libraries That Wine Might Need|Common Linux Libraries That Wine Might Need]]<br />
<br />
== The Forums, Bug Reports, and Script Contribution ==<br />
* [[How to Post in the Forums|How to Post in the Forums]]<br />
* [[How to Post a Bug Report|How to Post a Bug Report]]<br />
* [[How to Contribute a Script|How to Contribute a Script]]<br />
* [[How to Request a Patched Version of Wine|How to Request a Patched Version of Wine]]<br />
<br />
== Writing a script ==<br />
* [[Scripting - Chapter 1: Getting to know Bash|Chapter 1: Getting to know Bash]]<br />
* [[Scripting - Chapter 2: Basic Functions|Chapter 2: Basic Functions]]<br />
* [[Scripting - Chapter 3: Variables|Chapter 3: Variables]]<br />
* [[Scripting - Chapter 4: Conditions|Chapter 4: Conditions]]<br />
* [[Scripting - Chapter 5: Wine|Chapter 5: Wine]]<br />
* [[Scripting - Chapter 6: The Filesystem|Chapter 6: The Filesystem]]<br />
* [[Scripting - Chapter 7: Installation Media|Chapter 7: Installation Media]]<br />
* [[Scripting - Chapter 8: My First Real Script|Chapter 8: My First Real Script]]<br />
* [[Scripting - Chapter 9: Standardization|Chapter 9: Standardization]]<br />
* [[Scripting - Chapter 10: Script Translation|Chapter 10: Script Translation]]<br />
* [[Scripting - Chapter 11: List of Functions|Chapter 11: List of Functions]]<br />
== Glossary ==<br />
* [[POL & POM Terminology|POL & POM Terminology]]<br />
* [[Wine; what is it?|Wine; what is it?]]<br />
<br />
== Advanced PlayOnLinux ==<br />
* [[How to move PlayOnLinux virtual drives to another disk|How to move PlayOnLinux virtual drives to another disk]]<br />
* [[PlayOnLinux DOSBox support HOWTO]]<br />
* [https://github.com/PlayOnLinux/POL-POM-4 PlayOnLinux/PlayOnMac source code]<br />
* [https://github.com/PlayOnLinux/wine-patches Patch repository]<br />
* [[Setting up WineASIO with PlayOnLinux|Setting up WineASIO with PlayOnLinux]]<br />
<br />
== Advanced PlayOnMac ==<br />
<br />
* [https://github.com/PlayOnLinux/POL-POM-4 PlayOnLinux/PlayOnMac source code]<br />
* [https://github.com/PlayOnLinux/wine-patches Patch repository]<br />
<br />
== PlayOnLinux 5 Development ==<br />
<br />
POL 5 is currently under development, and there are new tools available to track and contribute the code for this new version. Development is very active at the moment, so feel free to check out the following resources to see if there is anything you would like to contribute (or if you just feel like checking out the development process and status).<br />
<br />
* [https://github.com/PlayOnLinux/POL-POM-5/ POL 5 GitHub Repository]<br />
* [http://www.playonlinux.org:8080/ Jenkins Automated Testing Interface]<br />
* [http://www.playonlinux.org:9000/ SonarQube Code-Quality Interface]<br />
* [http://wiki.playonlinux.com/index.php/Building_PlayOnLinux_5 Building PlayOnLinux 5]<br />
<br />
== Advanced Wine ==<br />
''' Wine-Wiki '''<br />
<br />
* [http://wine-wiki.org/ Wine-wiki. Somewhat outdated, but covers a LOT of advanced Wine topics]<br />
<br />
''' WineHQ '''<br />
<br />
* [https://www.winehq.org/devel/ Wine development links]<br />
* [http://wiki.winehq.org/DeveloperFaq Wine developer FAQ]<br />
* [https://www.winehq.org/docs/winedev-guide/index Wine developer's guide]<br />
* [http://wiki.winehq.org/Developers-Hints Wine developer hints]<br />
* [http://wiki.winehq.org/HackingTips Wine hacking tips]<br />
<br />
== Advanced WineBuild ==<br />
* [[Cross-compile Wine for OSX on Linux| How to cross-compile Wine for Mac OSX on Linux]]<br />
* [https://github.com/PlayOnLinux/WineBuild POL's WineBuild source code]</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Main_Page&diff=819Main Page2015-05-21T23:49:04Z<p>RoninDusette: </p>
<hr />
<div>Welcome to the PlayOnLinux and PlayOnMac wiki. Here you will find tutorials regarding the use of PlayOnLinux or PlayOnMac, and explanations of their various features. You'll also find guides explaining how to create installation scripts, a description of the commands available, API documentation, advanced topics, and more.<br />
<br />
For any additional questions that do not have an answer in this wiki, do not hesitate to go to the [https://www.playonlinux.com/en/forums.html forums].<br />
<br />
== User Documentation ==<br />
* [[Installing PlayOnLinux]]<br />
* [[Installing PlayOnMac]]<br />
* [[First Use|Guide for first use of the software]]<br />
* [[The Configuration Window|The Configuration Window]]<br />
* [[The PlayOnLinux Filesystem|The PlayOnLinux Filesystem]]<br />
* [[The PlayOnMac Filesystem|The PlayOnMac Filesystem]]<br />
* [[Managing Wine Versions|Managing Wine Versions]]<br />
* [[Manual Installations|Manual Installations]]<br />
* [[Components and Functions|Components and Functions]]<br />
* [[FAQ|Frequently Asked Questions]]<br />
<br />
== Troubleshooting ==<br />
* [[Troubleshooting Common Problems|Troubleshooting Common Problems]]<br />
* [[Graphics Card Drivers|Graphics Card Drivers]]<br />
* [[How to Read Debug Logs|How to Read Debug Logs]]<br />
* [[Common Linux Libraries That Wine Might Need|Common Linux Libraries That Wine Might Need]]<br />
<br />
== The Forums, Bug Reports, and Script Contribution ==<br />
* [[How to Post in the Forums|How to Post in the Forums]]<br />
* [[How to Post a Bug Report|How to Post a Bug Report]]<br />
* [[How to Contribute a Script|How to Contribute a Script]]<br />
* [[How to Request a Patched Version of Wine|How to Request a Patched Version of Wine]]<br />
<br />
== Writing a script ==<br />
* [[Scripting - Chapter 1: Getting to know Bash|Chapter 1: Getting to know Bash]]<br />
* [[Scripting - Chapter 2: Basic Functions|Chapter 2: Basic Functions]]<br />
* [[Scripting - Chapter 3: Variables|Chapter 3: Variables]]<br />
* [[Scripting - Chapter 4: Conditions|Chapter 4: Conditions]]<br />
* [[Scripting - Chapter 5: Wine|Chapter 5: Wine]]<br />
* [[Scripting - Chapter 6: The Filesystem|Chapter 6: The Filesystem]]<br />
* [[Scripting - Chapter 7: Installation Media|Chapter 7: Installation Media]]<br />
* [[Scripting - Chapter 8: My First Real Script|Chapter 8: My First Real Script]]<br />
* [[Scripting - Chapter 9: Standardization|Chapter 9: Standardization]]<br />
* [[Scripting - Chapter 10: Script Translation|Chapter 10: Script Translation]]<br />
* [[Scripting - Chapter 11: List of Functions|Chapter 11: List of Functions]]<br />
== Glossary ==<br />
* [[POL & POM Terminology|POL & POM Terminology]]<br />
* [[Wine; what is it?|Wine; what is it?]]<br />
<br />
== Advanced PlayOnLinux ==<br />
* [[How to move PlayOnLinux virtual drives to another disk|How to move PlayOnLinux virtual drives to another disk]]<br />
* [[PlayOnLinux DOSBox support HOWTO]]<br />
* [https://github.com/PlayOnLinux/POL-POM-4 PlayOnLinux/PlayOnMac source code]<br />
* [https://github.com/PlayOnLinux/wine-patches Patch repository]<br />
* [[Setting up WineASIO with PlayOnLinux|Setting up WineASIO with PlayOnLinux]]<br />
<br />
== Advanced PlayOnMac ==<br />
<br />
* [https://github.com/PlayOnLinux/POL-POM-4 PlayOnLinux/PlayOnMac source code]<br />
* [https://github.com/PlayOnLinux/wine-patches Patch repository]<br />
<br />
== PlayOnLinux 5 Development ==<br />
<br />
POL 5 is currently under development, and there are new tools available to track and contribute the code for this new version. Development is very active at the moment, so feel free to check out the following resources to see if there is anything you would like to contribute (or if you just feel like checking out the development process and status).<br />
<br />
* [https://github.com/PlayOnLinux/POL-POM-5/ POL 5 GitHub Repository]<br />
* [http://www.playonlinux.org:8080/ Jenkins Automated Testing Interface]<br />
* [http://www.playonlinux.org:9000/ SonarQube Code-Quality Interface]<br />
<br />
== Advanced Wine ==<br />
''' Wine-Wiki '''<br />
<br />
* [http://wine-wiki.org/ Wine-wiki. Somewhat outdated, but covers a LOT of advanced Wine topics]<br />
<br />
''' WineHQ '''<br />
<br />
* [https://www.winehq.org/devel/ Wine development links]<br />
* [http://wiki.winehq.org/DeveloperFaq Wine developer FAQ]<br />
* [https://www.winehq.org/docs/winedev-guide/index Wine developer's guide]<br />
* [http://wiki.winehq.org/Developers-Hints Wine developer hints]<br />
* [http://wiki.winehq.org/HackingTips Wine hacking tips]<br />
<br />
== Advanced WineBuild ==<br />
* [[Cross-compile Wine for OSX on Linux| How to cross-compile Wine for Mac OSX on Linux]]<br />
* [https://github.com/PlayOnLinux/WineBuild POL's WineBuild source code]</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Building_PlayOnLinux_5&diff=818Building PlayOnLinux 52015-05-20T06:05:38Z<p>RoninDusette: </p>
<hr />
<div>This page explains how to build PlayOnLinux 5 <br />
<br />
== On Ubuntu 14.10 ==<br />
<br />
=== Dependencies ===<br />
First, install the following dependencies: <br />
* maven2<br />
* openjdk-8-jdk<br />
* openjfx<br />
<br />
=== Compile PlayOnLinux 5===<br />
Clone the repository:{{Console|git clone https://github.com/PlayOnLinux/POL-POM-5}}Use the right Java version:{{Console|1 = export JAVA_HOME="/usr/lib/jvm/java-8-openjdk-amd64"}}Compile PlayOnLinux 5 with Maven: {{Console|cd POL-POM-5<br />
mvn2 assembly:assembly}}<br />
<br />
{{Info|If you are using Oracle JDK, the home path will be /usr/lib/jvm/java-8-oracle}}<br />
{{Info|On some distribution, mvn2 is simply named mvn}}<br />
<br />
=== Run PlayOnLinux 5 ===<br />
Run the previously built jar file{{Console|java -jar target/playonlinux-5.0-SNAPSHOT-jar-with-dependencies.jar }}<br />
<br />
== On Arch ==<br />
<br />
{{Info|The following has only been tested on 64-bit Arch installs.}}<br />
<br />
=== Dependencies ===<br />
First, install the following dependencies: <br />
* maven<br />
* jdk8-openjdk <br />
* gradle-1.8 (AUR)<br />
* openjfx (AUR)<br />
<br />
<br />
{{Info|You will need to set JAVA_HOME to "/usr/lib/jvm/java-8-openjdk" after installing ''jdk8-openjdk'', but before installing ''openjfx''.}}<br />
<br />
=== Compile PlayOnLinux 5===<br />
<br />
Clone the repository:{{Console|git clone https://github.com/PlayOnLinux/POL-POM-5}}<br />
<br />
Use the right Java version:{{Console|1 = export JAVA_HOME="/usr/lib/jvm/java-8-openjdk"}}<br />
<br />
Compile PlayOnLinux 5 with Maven: <br />
<br />
{{Console|cd POL-POM-5}}<br />
<br />
{{Console|mvn assembly:assembly}}<br />
<br />
{{Info|If you are using Oracle JDK, the home path will be /usr/lib/jvm/java-8-oracle}}<br />
<br />
=== Run PlayOnLinux 5 ===<br />
Run the previously built jar file{{Console|java -jar target/playonlinux-5.0-SNAPSHOT-jar-with-dependencies.jar }}<br />
<br />
[[Category:PlayOnLinux development]]</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Troubleshooting_Common_Problems&diff=816Troubleshooting Common Problems2015-05-17T05:02:34Z<p>RoninDusette: /* Who might encounter this error? */</p>
<hr />
<div>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.<br />
<br />
When trying a possible solution for an issue, please only try '''ONE''' solution at a time, and test to see if it worked. <br />
<br />
== p11-kit: couldn't load module: ... ==<br />
<br />
=== Error ===<br />
<br />
{{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}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Mostly users of Debian, Ubuntu, Kubuntu, etc., Mint (and derivatives), 64-bit systems.<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== Install 32-bit version of p11-kit-trust.so ====<br />
<br />
<pre class='code bash'><br />
sudo apt-get install p11-kit-modules:i386<br />
</pre><br />
<br />
==== Create a symlink ====<br />
<br />
''found at http://askubuntu.com/a/384018''<br />
<br />
<pre class='code bash'><br />
sudo /usr/local/bin/getlibs -p p11-kit:i386<br />
sudo ln -s /usr/lib32/i386-linux-gnu/pkcs11/p11-kit-trust.so /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so<br />
</pre><br />
<br />
== Error in FS_Check ==<br />
<br />
=== Error ===<br />
<br />
{{Console|The following file is located on a fuse filesystem. It might prevent wine from working}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Anyone trying to run an executable file in Wine/POL that is located on an NTFS filesystem.<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== Move executable to a native Linux filesystem ====<br />
<br />
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.<br />
<br />
== Failed to use ICMP ==<br />
<br />
=== Error ===<br />
<br />
{{Console|err:winediag:IcmpCreateFile Failed to use ICMP (network ping), this requires special permissions.<br />
}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
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.<br />
<br />
=== What causes this error? ===<br />
<br />
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? ;)<br />
<br />
=== Common solutions ===<br />
<br />
==== Give rights to POL's WineBuild ====<br />
<br />
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.<br />
<br />
For instance, '''AION'''.<br />
<br />
All of POL's WineBuilds are stored in ~/.PlayOnLinux/wine/<br />
<br />
Within this folder, you have different sub-folders for architecture, and then Wine version. In the case of '''AION''':<br />
<br />
{{Console|/home/username/.PlayOnLinux/wine/linux-x86/1.7.36}}<br />
<br />
Find out which Wine version your application needs:<br />
<br />
# Open the Configuration Window<br />
# In the General tab, when your virtual drive is selected, look at the name of the version of Wine in use. <br />
<br />
Now, the command you would want to run is:<br />
<br />
'''NOTE''': ''Do NOT copy and paste these commands. They need to be modified for your particular situation.''<br />
<br />
{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine}}<br />
<br />
or<br />
<br />
{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine-preloader}}<br />
<br />
'''NOTE:''' ''I have seen both bin/wine and bin/wine-preloader shown in examples, so for posterity, I am including both.''<br />
<br />
Essentially, the syntax for this is as follows:<br />
<br />
{{Console|sudo setcap cap_net_raw+epi /home/'''username'''/.PlayOnLinux/wine/'''WineArchitecture'''/'''WineVersion'''/bin/wine}}<br />
<br />
Replace: <br />
<br />
* '''username''' with your current username<br />
<br />
* '''Wine Architecture''' with either '''linux-x86''' (32-bit virtual drive) or '''linux-amd64''' (64-bit virtual drive)<br />
<br />
* '''Wine Version''' with the '''EXACT''' name listed in the '''Wine dropdown menu''' in the '''General tab''' of the ''' Configuration Window'''<br />
<br />
== Error! Files mismatch ==<br />
<br />
=== Error ===<br />
<br />
{{Console|''someurl''<br />
<br />
<br />
Error! Files mismatch<br />
<br />
<br />
Local: ''md5resultexpected''<br />
<br />
Server: ''md5resultdownloaded''<br />
<br />
<br />
<br />
Do you want to retry?<br />
}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
This can happen to any user on any system. It is also architecture agnostic.<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== File bug report with POL ====<br />
<br />
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.).<br />
<br />
== The application you are trying to install needs administrator rights... ==<br />
<br />
=== Error ===<br />
<br />
{{Console|The application you are trying to install needs administrator rights to function correctly.}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Anyone on any distro may see this error<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== File bug report with WineHQ ====<br />
<br />
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:<br />
<br />
* [https://bugs.winehq.org/ WineHQ's Bugzilla]<br />
<br />
== League of Legends Stuck on Logo (after Champ Select) ==<br />
<br />
=== Error ===<br />
<br />
League of Legends simply stalls at the logo after the champion select dialogue.<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Anyone on any distro may see this error<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== Install needed components ====<br />
<br />
Instructions adapted from this thread:<br />
<br />
[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]<br />
<br />
# Install in POL: d3dx10, d3dx11, d3dx9 (only d3dx9, not the other d3dx9_etc) and directx9<br />
# 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"<br />
<br />
== PlayOnMac: SECUR32_initNTLMSP ntlm_auth was not found or is outdated ==<br />
<br />
=== Error ===<br />
<br />
{{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.}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
PlayOnMac users, even if Samba and winbind are installed.<br />
<br />
=== What causes this error? ===<br />
<br />
PlayOnMac is not reading the correct path for some reason.<br />
<br />
=== Common solutions ===<br />
<br />
==== Edit PlayOnMac Bash script to properly set path ====<br />
<br />
Instructions adapted from this thread:<br />
<br />
[https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html]<br />
<br />
# Edit ''/Applications/PlayOnMac.app/Contents/MacOS/playonmac''<br />
# Change ''#!/bin/bash'' to ''#!/bin/bash --login'', save, and try to start PlayOnMac<br />
<br />
== No sound (err:module:load_builtin_dll... libasound.so.2...) ==<br />
<br />
=== Error ===<br />
<br />
{{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.}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Any user on any system may experience this.<br />
<br />
=== What causes this error? ===<br />
<br />
Missing 32-bit library; in this case, ''libasound2''.<br />
<br />
=== Common solutions ===<br />
<br />
==== Install the 32-bit version of libasound2 ====<br />
<br />
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.).</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Troubleshooting_Common_Problems&diff=815Troubleshooting Common Problems2015-05-17T04:59:43Z<p>RoninDusette: /* No sound (err:module:load_builtin_dll...) */</p>
<hr />
<div>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.<br />
<br />
When trying a possible solution for an issue, please only try '''ONE''' solution at a time, and test to see if it worked. <br />
<br />
== p11-kit: couldn't load module: ... ==<br />
<br />
=== Error ===<br />
<br />
{{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}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Mostly users of Debian, Ubuntu, Kubuntu, etc., Mint (and derivatives), 64-bit systems.<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== Install 32-bit version of p11-kit-trust.so ====<br />
<br />
<pre class='code bash'><br />
sudo apt-get install p11-kit-modules:i386<br />
</pre><br />
<br />
==== Create a symlink ====<br />
<br />
''found at http://askubuntu.com/a/384018''<br />
<br />
<pre class='code bash'><br />
sudo /usr/local/bin/getlibs -p p11-kit:i386<br />
sudo ln -s /usr/lib32/i386-linux-gnu/pkcs11/p11-kit-trust.so /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so<br />
</pre><br />
<br />
== Error in FS_Check ==<br />
<br />
=== Error ===<br />
<br />
{{Console|The following file is located on a fuse filesystem. It might prevent wine from working}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Anyone trying to run an executable file in Wine/POL that is located on an NTFS filesystem.<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== Move executable to a native Linux filesystem ====<br />
<br />
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.<br />
<br />
== Failed to use ICMP ==<br />
<br />
=== Error ===<br />
<br />
{{Console|err:winediag:IcmpCreateFile Failed to use ICMP (network ping), this requires special permissions.<br />
}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
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.<br />
<br />
=== What causes this error? ===<br />
<br />
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? ;)<br />
<br />
=== Common solutions ===<br />
<br />
==== Give rights to POL's WineBuild ====<br />
<br />
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.<br />
<br />
For instance, '''AION'''.<br />
<br />
All of POL's WineBuilds are stored in ~/.PlayOnLinux/wine/<br />
<br />
Within this folder, you have different sub-folders for architecture, and then Wine version. In the case of '''AION''':<br />
<br />
{{Console|/home/username/.PlayOnLinux/wine/linux-x86/1.7.36}}<br />
<br />
Find out which Wine version your application needs:<br />
<br />
# Open the Configuration Window<br />
# In the General tab, when your virtual drive is selected, look at the name of the version of Wine in use. <br />
<br />
Now, the command you would want to run is:<br />
<br />
'''NOTE''': ''Do NOT copy and paste these commands. They need to be modified for your particular situation.''<br />
<br />
{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine}}<br />
<br />
or<br />
<br />
{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine-preloader}}<br />
<br />
'''NOTE:''' ''I have seen both bin/wine and bin/wine-preloader shown in examples, so for posterity, I am including both.''<br />
<br />
Essentially, the syntax for this is as follows:<br />
<br />
{{Console|sudo setcap cap_net_raw+epi /home/'''username'''/.PlayOnLinux/wine/'''WineArchitecture'''/'''WineVersion'''/bin/wine}}<br />
<br />
Replace: <br />
<br />
* '''username''' with your current username<br />
<br />
* '''Wine Architecture''' with either '''linux-x86''' (32-bit virtual drive) or '''linux-amd64''' (64-bit virtual drive)<br />
<br />
* '''Wine Version''' with the '''EXACT''' name listed in the '''Wine dropdown menu''' in the '''General tab''' of the ''' Configuration Window'''<br />
<br />
== Error! Files mismatch ==<br />
<br />
=== Error ===<br />
<br />
{{Console|''someurl''<br />
<br />
<br />
Error! Files mismatch<br />
<br />
<br />
Local: ''md5resultexpected''<br />
<br />
Server: ''md5resultdownloaded''<br />
<br />
<br />
<br />
Do you want to retry?<br />
}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
This can happen to any user on any system. It is also architecture agnostic.<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== File bug report with POL ====<br />
<br />
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.).<br />
<br />
== The application you are trying to install needs administrator rights... ==<br />
<br />
=== Error ===<br />
<br />
{{Console|The application you are trying to install needs administrator rights to function correctly.}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Anyone on any distro may see this error<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== File bug report with WineHQ ====<br />
<br />
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:<br />
<br />
* [https://bugs.winehq.org/ WineHQ's Bugzilla]<br />
<br />
== League of Legends Stuck on Logo (after Champ Select) ==<br />
<br />
=== Error ===<br />
<br />
League of Legends simply stalls at the logo after the champion select dialogue.<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Anyone on any distro may see this error<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== Install needed components ====<br />
<br />
Instructions adapted from this thread:<br />
<br />
[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]<br />
<br />
# Install in POL: d3dx10, d3dx11, d3dx9 (only d3dx9, not the other d3dx9_etc) and directx9<br />
# 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"<br />
<br />
== PlayOnMac: SECUR32_initNTLMSP ntlm_auth was not found or is outdated ==<br />
<br />
=== Error ===<br />
<br />
{{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.}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
PlayOnMac users, even if Samba and winbind are installed.<br />
<br />
=== What causes this error? ===<br />
<br />
PlayOnMac is not reading the correct path for some reason.<br />
<br />
=== Common solutions ===<br />
<br />
==== Edit PlayOnMac Bash script to properly set path ====<br />
<br />
Instructions adapted from this thread:<br />
<br />
[https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html]<br />
<br />
# Edit ''/Applications/PlayOnMac.app/Contents/MacOS/playonmac''<br />
# Change ''#!/bin/bash'' to ''#!/bin/bash --login'', save, and try to start PlayOnMac<br />
<br />
== No sound (err:module:load_builtin_dll... libasound.so.2...) ==<br />
<br />
=== Error ===<br />
<br />
{{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.}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Any user on any system may experience this<br />
<br />
=== What causes this error? ===<br />
<br />
Missing 32-bit library; in this case, ''libasound2''.<br />
<br />
=== Common solutions ===<br />
<br />
==== Install the 32-bit version of libasound2 ====<br />
<br />
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.).</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Troubleshooting_Common_Problems&diff=814Troubleshooting Common Problems2015-05-17T04:07:53Z<p>RoninDusette: </p>
<hr />
<div>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.<br />
<br />
When trying a possible solution for an issue, please only try '''ONE''' solution at a time, and test to see if it worked. <br />
<br />
== p11-kit: couldn't load module: ... ==<br />
<br />
=== Error ===<br />
<br />
{{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}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Mostly users of Debian, Ubuntu, Kubuntu, etc., Mint (and derivatives), 64-bit systems.<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== Install 32-bit version of p11-kit-trust.so ====<br />
<br />
<pre class='code bash'><br />
sudo apt-get install p11-kit-modules:i386<br />
</pre><br />
<br />
==== Create a symlink ====<br />
<br />
''found at http://askubuntu.com/a/384018''<br />
<br />
<pre class='code bash'><br />
sudo /usr/local/bin/getlibs -p p11-kit:i386<br />
sudo ln -s /usr/lib32/i386-linux-gnu/pkcs11/p11-kit-trust.so /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so<br />
</pre><br />
<br />
== Error in FS_Check ==<br />
<br />
=== Error ===<br />
<br />
{{Console|The following file is located on a fuse filesystem. It might prevent wine from working}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Anyone trying to run an executable file in Wine/POL that is located on an NTFS filesystem.<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== Move executable to a native Linux filesystem ====<br />
<br />
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.<br />
<br />
== Failed to use ICMP ==<br />
<br />
=== Error ===<br />
<br />
{{Console|err:winediag:IcmpCreateFile Failed to use ICMP (network ping), this requires special permissions.<br />
}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
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.<br />
<br />
=== What causes this error? ===<br />
<br />
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? ;)<br />
<br />
=== Common solutions ===<br />
<br />
==== Give rights to POL's WineBuild ====<br />
<br />
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.<br />
<br />
For instance, '''AION'''.<br />
<br />
All of POL's WineBuilds are stored in ~/.PlayOnLinux/wine/<br />
<br />
Within this folder, you have different sub-folders for architecture, and then Wine version. In the case of '''AION''':<br />
<br />
{{Console|/home/username/.PlayOnLinux/wine/linux-x86/1.7.36}}<br />
<br />
Find out which Wine version your application needs:<br />
<br />
# Open the Configuration Window<br />
# In the General tab, when your virtual drive is selected, look at the name of the version of Wine in use. <br />
<br />
Now, the command you would want to run is:<br />
<br />
'''NOTE''': ''Do NOT copy and paste these commands. They need to be modified for your particular situation.''<br />
<br />
{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine}}<br />
<br />
or<br />
<br />
{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine-preloader}}<br />
<br />
'''NOTE:''' ''I have seen both bin/wine and bin/wine-preloader shown in examples, so for posterity, I am including both.''<br />
<br />
Essentially, the syntax for this is as follows:<br />
<br />
{{Console|sudo setcap cap_net_raw+epi /home/'''username'''/.PlayOnLinux/wine/'''WineArchitecture'''/'''WineVersion'''/bin/wine}}<br />
<br />
Replace: <br />
<br />
* '''username''' with your current username<br />
<br />
* '''Wine Architecture''' with either '''linux-x86''' (32-bit virtual drive) or '''linux-amd64''' (64-bit virtual drive)<br />
<br />
* '''Wine Version''' with the '''EXACT''' name listed in the '''Wine dropdown menu''' in the '''General tab''' of the ''' Configuration Window'''<br />
<br />
== Error! Files mismatch ==<br />
<br />
=== Error ===<br />
<br />
{{Console|''someurl''<br />
<br />
<br />
Error! Files mismatch<br />
<br />
<br />
Local: ''md5resultexpected''<br />
<br />
Server: ''md5resultdownloaded''<br />
<br />
<br />
<br />
Do you want to retry?<br />
}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
This can happen to any user on any system. It is also architecture agnostic.<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== File bug report with POL ====<br />
<br />
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.).<br />
<br />
== The application you are trying to install needs administrator rights... ==<br />
<br />
=== Error ===<br />
<br />
{{Console|The application you are trying to install needs administrator rights to function correctly.}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Anyone on any distro may see this error<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== File bug report with WineHQ ====<br />
<br />
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:<br />
<br />
* [https://bugs.winehq.org/ WineHQ's Bugzilla]<br />
<br />
== League of Legends Stuck on Logo (after Champ Select) ==<br />
<br />
=== Error ===<br />
<br />
League of Legends simply stalls at the logo after the champion select dialogue.<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Anyone on any distro may see this error<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== Install needed components ====<br />
<br />
Instructions adapted from this thread:<br />
<br />
[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]<br />
<br />
# Install in POL: d3dx10, d3dx11, d3dx9 (only d3dx9, not the other d3dx9_etc) and directx9<br />
# 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"<br />
<br />
== PlayOnMac: SECUR32_initNTLMSP ntlm_auth was not found or is outdated ==<br />
<br />
=== Error ===<br />
<br />
{{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.}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
PlayOnMac users, even if Samba and winbind are installed.<br />
<br />
=== What causes this error? ===<br />
<br />
PlayOnMac is not reading the correct path for some reason.<br />
<br />
=== Common solutions ===<br />
<br />
==== Edit PlayOnMac Bash script to properly set path ====<br />
<br />
Instructions adapted from this thread:<br />
<br />
[https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html]<br />
<br />
# Edit ''/Applications/PlayOnMac.app/Contents/MacOS/playonmac''<br />
# Change ''#!/bin/bash'' to ''#!/bin/bash --login'', save, and try to start PlayOnMac<br />
<br />
== No sound (err:module:load_builtin_dll...) ==<br />
<br />
=== Error ===<br />
<br />
{{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.}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Any user on any system may experience this<br />
<br />
=== What causes this error? ===<br />
<br />
Missing 32-bit library; in this case, ''libasound2''.<br />
<br />
=== Common solutions ===<br />
<br />
==== Install the 32-bit version of libasound2 ====<br />
<br />
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.).</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=FAQ&diff=813FAQ2015-05-16T06:44:39Z<p>RoninDusette: /* How can I use the CSMT patch with POL? */</p>
<hr />
<div>== PlayOnLinux and PlayOnMac ==<br />
<br />
=== How do I find out if a game will run on PlayOnLinux/PlayOnMac? ===<br />
Excellent question. Since POL/POM is a front-end for [https://winehq.org/ Wine], the first place to check, besides our [https://www.playonlinux.com/en/supported_apps.html Supported Software section], is WineHQ's [https://appdb.winehq.org/ AppDB]. There are many, many entries for a lot of different types of Windows applications, all submitted to the Wine community by users like yourself. If it is even remotely popular, and people have attempted to use it through Wine, it will likely be listed there.<br />
<br />
=== How do I move PlayOnLinux virtual drives to another disk (with more free space)? ===<br />
Read the advanced topic here:<br />
* [[How to move PlayOnLinux virtual drives to another disk|How to move PlayOnLinux virtual drives to another disk]]<br />
<br />
=== Why isn't PlayOnLinux downloading Photoshop (or whatever retail application) for me? ===<br />
PlayOnLinux/PlayOnMac does not actually provide the applications. It provides the means to install those applications. You actually have to own, say, Photoshop CS6, in order to install Photoshop CS6. POL/POM does not provide any sort of pirated software in any way. This also applies to support regarding pirated software and cracks.<br />
<br />
=== Do I have to install Wine to use PlayOnLinux? ===<br />
Yes. You will want to have a 32-bit version of Wine installed on your system, along with the dependencies it suggests. POL will want to see it, and will use it's dependencies concurrently with POL's WineBuilds. Without getting too technical, POL will need it, so it is best to install it.<br />
<br />
=== Will PlayOnLinux interfere with my current Wine or winetricks installations? ===<br />
No. PlayOnLinux/PlayOnMac keeps all of it's resources, WineBuilds, and virtual drives contained in one folder, and will never interfere with your other WINEPREFIX created by vanilla Wine and winetricks (unless, of course, you start using winetricks for POL virtual drives or try to use vanilla Wine on a POL virtual drive, or something like that.).<br />
<br />
=== The application I am trying to install needs administrator rights to function correctly ===<br />
Wine does not implement privileges, so such message does not make any sense under Wine. Either it cannot be made to work, or emulated Windows version must be changed to some version that does not implement privileges (Win9x for instance) so that the installer changes its expectations.<br />
<br />
=== How do I install Steam, and Steam only? ===<br />
<br />
If you want to only install Steam for Windows into a Virtual Drive, you will need to do a manual installation. It is very simple:<br />
<br />
# Open PlayOnLinux, download and install the WineBuild that you want from [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions].<br />
# Open the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window], click New, and create a new Virtual Drive, naming it what you want, and selecting the WineBuild that you want to use when prompted.<br />
# In the Configuration Window, select your new Virtual Drive, open the Install Components tab, and double-click '''Steam''' in that list. Steam will be installed into the Virtual Drive highlighted on the left side.<br />
# On the General Tab of the Configuration Window, select '''Make a new shortcut from this virtual drive''', and select the Steam executable when shown in the list. This will create a shortcut in the main POL window. <br />
<br />
<br />
{{Info|This is a manual install, and does not guarantee that the game that you install through Steam will work. If it does not work, you should check to see if there is already an installer for that game in our repository, and if not, you will need to check the [https://appdb.winehq.org AppDB at WineHQ] for your game to see if it needs any extra components or settings. As always, for manual installs, feel free to post up for help in the appropriate section of [https://www.playonlinux.com/en/forum-24-Manual_installations.html the forums].''}}<br />
<br />
=== How can I use the CSMT patch with POL? ===<br />
<br />
Up until recently, you would have needed to [http://wiki.playonlinux.com/index.php/How_to_Request_a_Patched_Version_of_Wine request a patched WineBuild]. Now, with the help of the devs at ''[http://www.wine-staging.com/ wine-staging]'', we have WineBuilds with the patchset from ''wine-staging'', which happen to contain the CSMT patch (for now; when patches from ''wine-staging'' get mainlined, they are dropped from the ''-staging'' versions of Wine, as they are now a default feature.).<br />
<br />
Simply go to [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions] and download the WineBuild that you want, with the ''-staging'' suffix, and then use the '''Wine tab''' in the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window] to access '''Wine Configuration'''. You will find a checkbox to enable CSMT in the '''Staging tab'''.<br />
<br />
== Website ==<br />
<br />
=== How can I post a bug report? ===<br />
* [[How to Post a Bug Report|How to Post a Bug Report]]<br />
<br />
=== How can I contribute an installer for an application? ===<br />
First, you would want to read our scripters tutorial here: [[Scripting - Chapter 1: Getting to know Bash|Scripting tutorial]]<br />
<br />
Then once you have written and tested a script, and it is working, follow the instructions here to submit it to us: [[How to Contribute a Script|How to Contribute a Script]]<br />
<br />
=== How do I request a version of Wine with a certain patch? ===<br />
* [[How to Request a Patched Version of Wine|How to Request a Patched Version of Wine]]<br />
<br />
=== Where does PlayOnLinux store it's virtual drives and cache? ===<br />
All virtual drives are created and store here:<br />
<br />
<code>~/.PlayOnLinux/wineprefix/</code><br />
<br />
The other files for Wine versions, resources, and components cache are located in '''~/.PlayOnLinux/'''<br />
<br />
=== How do I run Wine/POL as root or sudo? ===<br />
You don't. You should never, ever run Wine or POL as root or using sudo, or any other privilege escalation mechanism. <br />
<br />
* [http://wiki.winehq.org/FAQ#head-96bebfa287b4288974de0df23351f278b0d41014 WineHQ FAQ regarding root/sudo use]<br />
<br />
=== Is there a list of solutions for common problems? ===<br />
Somewhat, as issues can vary a '''LOT''' between users, systems, Wine versions, graphics cards, etc.. As a start, you should check the following locations:<br />
<br />
* [https://appdb.winehq.org/ appdb.winehq.org]<br />
* [[Troubleshooting Common Problems|Troubleshooting Common Problems]]<br />
* [https://www.playonlinux.com/en/forums.html The POL/POM forums]<br />
* Google, of course<br />
<br />
=== My post was closed with a semi-automated reply? What did I break? ===<br />
Nothing. What that means is that your post is lacking information that we need to troubleshoot, or possibly violates our terms of service. <br />
<br />
Check the following links to make sure that you didn't accidentally violate ToS, and that you are posting the information required:<br />
<br />
* https://www.playonlinux.com/en/terms.html<br />
<br />
* [[How to Post in the Forums|How to Post in the Forums]]<br />
<br />
== I want to contribute ==<br />
<br />
=== Bash; I really want to know more ===<br />
* http://www.gnu.org/software/bash/<br />
<br />
* http://linuxconfig.org/bash-scripting-tutorial<br />
<br />
* http://www.tldp.org/LDP/Bash-Beginners-Guide/html/<br />
<br />
* http://www.tldp.org/LDP/abs/html/<br />
<br />
=== Python; I really want to know more ===<br />
* https://www.python.org/<br />
<br />
* https://docs.python.org/2/tutorial/<br />
<br />
* http://www.learnpython.org/</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=FAQ&diff=812FAQ2015-05-16T06:43:43Z<p>RoninDusette: /* How can I use the CSMT patch with POL? */</p>
<hr />
<div>== PlayOnLinux and PlayOnMac ==<br />
<br />
=== How do I find out if a game will run on PlayOnLinux/PlayOnMac? ===<br />
Excellent question. Since POL/POM is a front-end for [https://winehq.org/ Wine], the first place to check, besides our [https://www.playonlinux.com/en/supported_apps.html Supported Software section], is WineHQ's [https://appdb.winehq.org/ AppDB]. There are many, many entries for a lot of different types of Windows applications, all submitted to the Wine community by users like yourself. If it is even remotely popular, and people have attempted to use it through Wine, it will likely be listed there.<br />
<br />
=== How do I move PlayOnLinux virtual drives to another disk (with more free space)? ===<br />
Read the advanced topic here:<br />
* [[How to move PlayOnLinux virtual drives to another disk|How to move PlayOnLinux virtual drives to another disk]]<br />
<br />
=== Why isn't PlayOnLinux downloading Photoshop (or whatever retail application) for me? ===<br />
PlayOnLinux/PlayOnMac does not actually provide the applications. It provides the means to install those applications. You actually have to own, say, Photoshop CS6, in order to install Photoshop CS6. POL/POM does not provide any sort of pirated software in any way. This also applies to support regarding pirated software and cracks.<br />
<br />
=== Do I have to install Wine to use PlayOnLinux? ===<br />
Yes. You will want to have a 32-bit version of Wine installed on your system, along with the dependencies it suggests. POL will want to see it, and will use it's dependencies concurrently with POL's WineBuilds. Without getting too technical, POL will need it, so it is best to install it.<br />
<br />
=== Will PlayOnLinux interfere with my current Wine or winetricks installations? ===<br />
No. PlayOnLinux/PlayOnMac keeps all of it's resources, WineBuilds, and virtual drives contained in one folder, and will never interfere with your other WINEPREFIX created by vanilla Wine and winetricks (unless, of course, you start using winetricks for POL virtual drives or try to use vanilla Wine on a POL virtual drive, or something like that.).<br />
<br />
=== The application I am trying to install needs administrator rights to function correctly ===<br />
Wine does not implement privileges, so such message does not make any sense under Wine. Either it cannot be made to work, or emulated Windows version must be changed to some version that does not implement privileges (Win9x for instance) so that the installer changes its expectations.<br />
<br />
=== How do I install Steam, and Steam only? ===<br />
<br />
If you want to only install Steam for Windows into a Virtual Drive, you will need to do a manual installation. It is very simple:<br />
<br />
# Open PlayOnLinux, download and install the WineBuild that you want from [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions].<br />
# Open the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window], click New, and create a new Virtual Drive, naming it what you want, and selecting the WineBuild that you want to use when prompted.<br />
# In the Configuration Window, select your new Virtual Drive, open the Install Components tab, and double-click '''Steam''' in that list. Steam will be installed into the Virtual Drive highlighted on the left side.<br />
# On the General Tab of the Configuration Window, select '''Make a new shortcut from this virtual drive''', and select the Steam executable when shown in the list. This will create a shortcut in the main POL window. <br />
<br />
<br />
{{Info|This is a manual install, and does not guarantee that the game that you install through Steam will work. If it does not work, you should check to see if there is already an installer for that game in our repository, and if not, you will need to check the [https://appdb.winehq.org AppDB at WineHQ] for your game to see if it needs any extra components or settings. As always, for manual installs, feel free to post up for help in the appropriate section of [https://www.playonlinux.com/en/forum-24-Manual_installations.html the forums].''}}<br />
<br />
=== How can I use the CSMT patch with POL? ===<br />
<br />
Up until recently, you would have needed to [http://wiki.playonlinux.com/index.php/How_to_Request_a_Patched_Version_of_Wine request a patched WineBuild]. Now, with the help of the devs at ''[http://www.wine-staging.com/ wine-staging]'', we have WineBuilds with the patchset from ''wine-staging'', which happen to contain the CSMT patch (for now; when patches from ''wine-staging'' get mainlined, they are dropped from the ''-staging'' versions of Wine, as they are now a default feature.). You just have to go to [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions] and download the WineBuild that you want, with the ''-staging'' suffix, and then use the '''Wine tab''' in the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window] to access '''Wine Configuration'''. You will find a checkbox to enable CSMT in the '''Staging tab'''.<br />
<br />
== Website ==<br />
<br />
=== How can I post a bug report? ===<br />
* [[How to Post a Bug Report|How to Post a Bug Report]]<br />
<br />
=== How can I contribute an installer for an application? ===<br />
First, you would want to read our scripters tutorial here: [[Scripting - Chapter 1: Getting to know Bash|Scripting tutorial]]<br />
<br />
Then once you have written and tested a script, and it is working, follow the instructions here to submit it to us: [[How to Contribute a Script|How to Contribute a Script]]<br />
<br />
=== How do I request a version of Wine with a certain patch? ===<br />
* [[How to Request a Patched Version of Wine|How to Request a Patched Version of Wine]]<br />
<br />
=== Where does PlayOnLinux store it's virtual drives and cache? ===<br />
All virtual drives are created and store here:<br />
<br />
<code>~/.PlayOnLinux/wineprefix/</code><br />
<br />
The other files for Wine versions, resources, and components cache are located in '''~/.PlayOnLinux/'''<br />
<br />
=== How do I run Wine/POL as root or sudo? ===<br />
You don't. You should never, ever run Wine or POL as root or using sudo, or any other privilege escalation mechanism. <br />
<br />
* [http://wiki.winehq.org/FAQ#head-96bebfa287b4288974de0df23351f278b0d41014 WineHQ FAQ regarding root/sudo use]<br />
<br />
=== Is there a list of solutions for common problems? ===<br />
Somewhat, as issues can vary a '''LOT''' between users, systems, Wine versions, graphics cards, etc.. As a start, you should check the following locations:<br />
<br />
* [https://appdb.winehq.org/ appdb.winehq.org]<br />
* [[Troubleshooting Common Problems|Troubleshooting Common Problems]]<br />
* [https://www.playonlinux.com/en/forums.html The POL/POM forums]<br />
* Google, of course<br />
<br />
=== My post was closed with a semi-automated reply? What did I break? ===<br />
Nothing. What that means is that your post is lacking information that we need to troubleshoot, or possibly violates our terms of service. <br />
<br />
Check the following links to make sure that you didn't accidentally violate ToS, and that you are posting the information required:<br />
<br />
* https://www.playonlinux.com/en/terms.html<br />
<br />
* [[How to Post in the Forums|How to Post in the Forums]]<br />
<br />
== I want to contribute ==<br />
<br />
=== Bash; I really want to know more ===<br />
* http://www.gnu.org/software/bash/<br />
<br />
* http://linuxconfig.org/bash-scripting-tutorial<br />
<br />
* http://www.tldp.org/LDP/Bash-Beginners-Guide/html/<br />
<br />
* http://www.tldp.org/LDP/abs/html/<br />
<br />
=== Python; I really want to know more ===<br />
* https://www.python.org/<br />
<br />
* https://docs.python.org/2/tutorial/<br />
<br />
* http://www.learnpython.org/</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=FAQ&diff=811FAQ2015-05-16T06:42:58Z<p>RoninDusette: /* How can I use the CSMT patch with POL? */</p>
<hr />
<div>== PlayOnLinux and PlayOnMac ==<br />
<br />
=== How do I find out if a game will run on PlayOnLinux/PlayOnMac? ===<br />
Excellent question. Since POL/POM is a front-end for [https://winehq.org/ Wine], the first place to check, besides our [https://www.playonlinux.com/en/supported_apps.html Supported Software section], is WineHQ's [https://appdb.winehq.org/ AppDB]. There are many, many entries for a lot of different types of Windows applications, all submitted to the Wine community by users like yourself. If it is even remotely popular, and people have attempted to use it through Wine, it will likely be listed there.<br />
<br />
=== How do I move PlayOnLinux virtual drives to another disk (with more free space)? ===<br />
Read the advanced topic here:<br />
* [[How to move PlayOnLinux virtual drives to another disk|How to move PlayOnLinux virtual drives to another disk]]<br />
<br />
=== Why isn't PlayOnLinux downloading Photoshop (or whatever retail application) for me? ===<br />
PlayOnLinux/PlayOnMac does not actually provide the applications. It provides the means to install those applications. You actually have to own, say, Photoshop CS6, in order to install Photoshop CS6. POL/POM does not provide any sort of pirated software in any way. This also applies to support regarding pirated software and cracks.<br />
<br />
=== Do I have to install Wine to use PlayOnLinux? ===<br />
Yes. You will want to have a 32-bit version of Wine installed on your system, along with the dependencies it suggests. POL will want to see it, and will use it's dependencies concurrently with POL's WineBuilds. Without getting too technical, POL will need it, so it is best to install it.<br />
<br />
=== Will PlayOnLinux interfere with my current Wine or winetricks installations? ===<br />
No. PlayOnLinux/PlayOnMac keeps all of it's resources, WineBuilds, and virtual drives contained in one folder, and will never interfere with your other WINEPREFIX created by vanilla Wine and winetricks (unless, of course, you start using winetricks for POL virtual drives or try to use vanilla Wine on a POL virtual drive, or something like that.).<br />
<br />
=== The application I am trying to install needs administrator rights to function correctly ===<br />
Wine does not implement privileges, so such message does not make any sense under Wine. Either it cannot be made to work, or emulated Windows version must be changed to some version that does not implement privileges (Win9x for instance) so that the installer changes its expectations.<br />
<br />
=== How do I install Steam, and Steam only? ===<br />
<br />
If you want to only install Steam for Windows into a Virtual Drive, you will need to do a manual installation. It is very simple:<br />
<br />
# Open PlayOnLinux, download and install the WineBuild that you want from [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions].<br />
# Open the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window], click New, and create a new Virtual Drive, naming it what you want, and selecting the WineBuild that you want to use when prompted.<br />
# In the Configuration Window, select your new Virtual Drive, open the Install Components tab, and double-click '''Steam''' in that list. Steam will be installed into the Virtual Drive highlighted on the left side.<br />
# On the General Tab of the Configuration Window, select '''Make a new shortcut from this virtual drive''', and select the Steam executable when shown in the list. This will create a shortcut in the main POL window. <br />
<br />
<br />
{{Info|This is a manual install, and does not guarantee that the game that you install through Steam will work. If it does not work, you should check to see if there is already an installer for that game in our repository, and if not, you will need to check the [https://appdb.winehq.org AppDB at WineHQ] for your game to see if it needs any extra components or settings. As always, for manual installs, feel free to post up for help in the appropriate section of [https://www.playonlinux.com/en/forum-24-Manual_installations.html the forums].''}}<br />
<br />
=== How can I use the CSMT patch with POL? ===<br />
<br />
Up until recently, you would have needed to request a patched WineBuild. Now, with the help of the devs at ''[http://www.wine-staging.com/ wine-staging]'', we have WineBuilds with the patchset from ''wine-staging'', which happen to contain the CSMT patch (for now; when patches from ''wine-staging'' get mainlined, they are dropped from the ''-staging'' versions of Wine, as they are now a default feature.). You just have to go to [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions] and download the WineBuild that you want, with the ''-staging'' suffix, and then use the '''Wine tab''' in the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window] to access '''Wine Configuration'''. You will find a checkbox to enable CSMT in the '''Staging tab'''.<br />
<br />
== Website ==<br />
<br />
=== How can I post a bug report? ===<br />
* [[How to Post a Bug Report|How to Post a Bug Report]]<br />
<br />
=== How can I contribute an installer for an application? ===<br />
First, you would want to read our scripters tutorial here: [[Scripting - Chapter 1: Getting to know Bash|Scripting tutorial]]<br />
<br />
Then once you have written and tested a script, and it is working, follow the instructions here to submit it to us: [[How to Contribute a Script|How to Contribute a Script]]<br />
<br />
=== How do I request a version of Wine with a certain patch? ===<br />
* [[How to Request a Patched Version of Wine|How to Request a Patched Version of Wine]]<br />
<br />
=== Where does PlayOnLinux store it's virtual drives and cache? ===<br />
All virtual drives are created and store here:<br />
<br />
<code>~/.PlayOnLinux/wineprefix/</code><br />
<br />
The other files for Wine versions, resources, and components cache are located in '''~/.PlayOnLinux/'''<br />
<br />
=== How do I run Wine/POL as root or sudo? ===<br />
You don't. You should never, ever run Wine or POL as root or using sudo, or any other privilege escalation mechanism. <br />
<br />
* [http://wiki.winehq.org/FAQ#head-96bebfa287b4288974de0df23351f278b0d41014 WineHQ FAQ regarding root/sudo use]<br />
<br />
=== Is there a list of solutions for common problems? ===<br />
Somewhat, as issues can vary a '''LOT''' between users, systems, Wine versions, graphics cards, etc.. As a start, you should check the following locations:<br />
<br />
* [https://appdb.winehq.org/ appdb.winehq.org]<br />
* [[Troubleshooting Common Problems|Troubleshooting Common Problems]]<br />
* [https://www.playonlinux.com/en/forums.html The POL/POM forums]<br />
* Google, of course<br />
<br />
=== My post was closed with a semi-automated reply? What did I break? ===<br />
Nothing. What that means is that your post is lacking information that we need to troubleshoot, or possibly violates our terms of service. <br />
<br />
Check the following links to make sure that you didn't accidentally violate ToS, and that you are posting the information required:<br />
<br />
* https://www.playonlinux.com/en/terms.html<br />
<br />
* [[How to Post in the Forums|How to Post in the Forums]]<br />
<br />
== I want to contribute ==<br />
<br />
=== Bash; I really want to know more ===<br />
* http://www.gnu.org/software/bash/<br />
<br />
* http://linuxconfig.org/bash-scripting-tutorial<br />
<br />
* http://www.tldp.org/LDP/Bash-Beginners-Guide/html/<br />
<br />
* http://www.tldp.org/LDP/abs/html/<br />
<br />
=== Python; I really want to know more ===<br />
* https://www.python.org/<br />
<br />
* https://docs.python.org/2/tutorial/<br />
<br />
* http://www.learnpython.org/</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=FAQ&diff=810FAQ2015-05-16T06:41:11Z<p>RoninDusette: /* How can I use the CSMT patch with POL? */</p>
<hr />
<div>== PlayOnLinux and PlayOnMac ==<br />
<br />
=== How do I find out if a game will run on PlayOnLinux/PlayOnMac? ===<br />
Excellent question. Since POL/POM is a front-end for [https://winehq.org/ Wine], the first place to check, besides our [https://www.playonlinux.com/en/supported_apps.html Supported Software section], is WineHQ's [https://appdb.winehq.org/ AppDB]. There are many, many entries for a lot of different types of Windows applications, all submitted to the Wine community by users like yourself. If it is even remotely popular, and people have attempted to use it through Wine, it will likely be listed there.<br />
<br />
=== How do I move PlayOnLinux virtual drives to another disk (with more free space)? ===<br />
Read the advanced topic here:<br />
* [[How to move PlayOnLinux virtual drives to another disk|How to move PlayOnLinux virtual drives to another disk]]<br />
<br />
=== Why isn't PlayOnLinux downloading Photoshop (or whatever retail application) for me? ===<br />
PlayOnLinux/PlayOnMac does not actually provide the applications. It provides the means to install those applications. You actually have to own, say, Photoshop CS6, in order to install Photoshop CS6. POL/POM does not provide any sort of pirated software in any way. This also applies to support regarding pirated software and cracks.<br />
<br />
=== Do I have to install Wine to use PlayOnLinux? ===<br />
Yes. You will want to have a 32-bit version of Wine installed on your system, along with the dependencies it suggests. POL will want to see it, and will use it's dependencies concurrently with POL's WineBuilds. Without getting too technical, POL will need it, so it is best to install it.<br />
<br />
=== Will PlayOnLinux interfere with my current Wine or winetricks installations? ===<br />
No. PlayOnLinux/PlayOnMac keeps all of it's resources, WineBuilds, and virtual drives contained in one folder, and will never interfere with your other WINEPREFIX created by vanilla Wine and winetricks (unless, of course, you start using winetricks for POL virtual drives or try to use vanilla Wine on a POL virtual drive, or something like that.).<br />
<br />
=== The application I am trying to install needs administrator rights to function correctly ===<br />
Wine does not implement privileges, so such message does not make any sense under Wine. Either it cannot be made to work, or emulated Windows version must be changed to some version that does not implement privileges (Win9x for instance) so that the installer changes its expectations.<br />
<br />
=== How do I install Steam, and Steam only? ===<br />
<br />
If you want to only install Steam for Windows into a Virtual Drive, you will need to do a manual installation. It is very simple:<br />
<br />
# Open PlayOnLinux, download and install the WineBuild that you want from [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions].<br />
# Open the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window], click New, and create a new Virtual Drive, naming it what you want, and selecting the WineBuild that you want to use when prompted.<br />
# In the Configuration Window, select your new Virtual Drive, open the Install Components tab, and double-click '''Steam''' in that list. Steam will be installed into the Virtual Drive highlighted on the left side.<br />
# On the General Tab of the Configuration Window, select '''Make a new shortcut from this virtual drive''', and select the Steam executable when shown in the list. This will create a shortcut in the main POL window. <br />
<br />
<br />
{{Info|This is a manual install, and does not guarantee that the game that you install through Steam will work. If it does not work, you should check to see if there is already an installer for that game in our repository, and if not, you will need to check the [https://appdb.winehq.org AppDB at WineHQ] for your game to see if it needs any extra components or settings. As always, for manual installs, feel free to post up for help in the appropriate section of [https://www.playonlinux.com/en/forum-24-Manual_installations.html the forums].''}}<br />
<br />
=== How can I use the CSMT patch with POL? ===<br />
<br />
Up until recently, you would have needed to request a patched WineBuild. Now, with the help of the devs at ''[http://www.wine-staging.com/ wine-staging]'', we have WineBuilds with the patchset from ''wine-staging'', which happen to contain the CSMT patch. You just have to go to [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions] and download the WineBuild that you want, with the ''-staging'' suffix, and then use the '''Wine tab''' in the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window] to access '''Wine Configuration'''. You will find a checkbox to enable CSMT in the '''Staging tab'''.<br />
<br />
== Website ==<br />
<br />
=== How can I post a bug report? ===<br />
* [[How to Post a Bug Report|How to Post a Bug Report]]<br />
<br />
=== How can I contribute an installer for an application? ===<br />
First, you would want to read our scripters tutorial here: [[Scripting - Chapter 1: Getting to know Bash|Scripting tutorial]]<br />
<br />
Then once you have written and tested a script, and it is working, follow the instructions here to submit it to us: [[How to Contribute a Script|How to Contribute a Script]]<br />
<br />
=== How do I request a version of Wine with a certain patch? ===<br />
* [[How to Request a Patched Version of Wine|How to Request a Patched Version of Wine]]<br />
<br />
=== Where does PlayOnLinux store it's virtual drives and cache? ===<br />
All virtual drives are created and store here:<br />
<br />
<code>~/.PlayOnLinux/wineprefix/</code><br />
<br />
The other files for Wine versions, resources, and components cache are located in '''~/.PlayOnLinux/'''<br />
<br />
=== How do I run Wine/POL as root or sudo? ===<br />
You don't. You should never, ever run Wine or POL as root or using sudo, or any other privilege escalation mechanism. <br />
<br />
* [http://wiki.winehq.org/FAQ#head-96bebfa287b4288974de0df23351f278b0d41014 WineHQ FAQ regarding root/sudo use]<br />
<br />
=== Is there a list of solutions for common problems? ===<br />
Somewhat, as issues can vary a '''LOT''' between users, systems, Wine versions, graphics cards, etc.. As a start, you should check the following locations:<br />
<br />
* [https://appdb.winehq.org/ appdb.winehq.org]<br />
* [[Troubleshooting Common Problems|Troubleshooting Common Problems]]<br />
* [https://www.playonlinux.com/en/forums.html The POL/POM forums]<br />
* Google, of course<br />
<br />
=== My post was closed with a semi-automated reply? What did I break? ===<br />
Nothing. What that means is that your post is lacking information that we need to troubleshoot, or possibly violates our terms of service. <br />
<br />
Check the following links to make sure that you didn't accidentally violate ToS, and that you are posting the information required:<br />
<br />
* https://www.playonlinux.com/en/terms.html<br />
<br />
* [[How to Post in the Forums|How to Post in the Forums]]<br />
<br />
== I want to contribute ==<br />
<br />
=== Bash; I really want to know more ===<br />
* http://www.gnu.org/software/bash/<br />
<br />
* http://linuxconfig.org/bash-scripting-tutorial<br />
<br />
* http://www.tldp.org/LDP/Bash-Beginners-Guide/html/<br />
<br />
* http://www.tldp.org/LDP/abs/html/<br />
<br />
=== Python; I really want to know more ===<br />
* https://www.python.org/<br />
<br />
* https://docs.python.org/2/tutorial/<br />
<br />
* http://www.learnpython.org/</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Graphics_Card_Drivers&diff=809Graphics Card Drivers2015-05-16T06:14:18Z<p>RoninDusette: /* Arch */</p>
<hr />
<div>In this section, we will try to cover the basics of getting the most out of your AMD, Nvidia, or Intel graphics card on your Linux system, specifically when using Wine/PlayOnLinux. This can get pretty lengthy, so expect this article to get exponentially bigger as time goes on.<br />
<br />
{{Info|This list is going to take a while to get full, so please be patient as we populate everything.}}<br />
<br />
For ease of use, we will break these down into different sections for the graphics card manufacturer, and then distro's within those categories. <br />
<br />
== NVIDIA ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
Most of the time, the easiest way is using the "Additional Drivers" dialogue. That does not always work though, and it sometimes will offer less-than-ideal versions of drivers for your NVIDIA card. If your card is supported by the current NVIDIA driver, the following command should pull in the required libraries:<br />
<br />
{{Console|sudo apt-get install nvidia-current}}<br />
<br />
You can also install other series of drivers (313.x, 319.x, 331.x, etc.) by appending the version name to them:<br />
<br />
'''Examples:'''<br />
<br />
{{Console|sudo apt-get install nvidia-331}}<br />
<br />
For the '''32-bit''' libraries, as long as ''libgl1-mesa-glx:i386'' and ''multiarch-support'' are installed, it should install them automatically. If, after you install them from the Ubuntu repositories, it does not show up, try to install those packages mentioned previously:<br />
<br />
{{Console|<br />
sudo apt-get install multiarch-support<br />
<br />
sudo apt-get install libgl1-mesa-glx:i386<br />
}}<br />
<br />
The manual installation is a bit more involved, but it is preferred by a lot of users.<br />
<br />
''Will add more later''<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary NVIDIA drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/NvidiaGraphicsDrivers<br />
<br />
==== Fedora ====<br />
<br />
* http://rpmfusion.org/Howto/nVidia<br />
<br />
==== Arch ====<br />
<br />
Arch Linux is pretty straightforward when it comes to this, and their documentation is quite concise. Please use the Arch Linux docs whenever possible for graphics issues:<br />
<br />
* https://wiki.archlinux.org/index.php/NVIDIA<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVidia/nvidia-drivers<br />
<br />
=== Optimus ===<br />
<br />
NVIDIA Optimus technology is a feature in laptops with newer Intel CPU's with integrated GPUs and discrete NVIDIA graphics cards that allows switching between graphics processors on-the-fly, to optimize the performance when needed, and maximizing battery life when not needing the discrete graphics card. More information on Optimus can be found here:<br />
<br />
* http://www.nvidia.com/object/optimus_technology.html<br />
<br />
==== Most distributions ====<br />
<br />
The current working solution is maintained by the '''Bumblebee Project'''. '''PRIME''' is not recommended, as it utilizes the open-source NVIDIA driver (''nouveau''), and will not give the performance desired for most games. The project's website has detailed documentation for most major distributions, so it is recommended to go by that:<br />
<br />
* http://bumblebee-project.org/<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVIDIA_Driver_with_Optimus_Laptops<br />
<br />
=== Open-Source Drivers ===<br />
<br />
Unfortunately, the open-source ''nouveau'' drivers are not really up-to-par on performance yet for gaming. Things are starting to look up, but there are a lot of caveats to running the open-source NVIDIA drivers. More information can be found here:<br />
<br />
* http://nouveau.freedesktop.org/wiki/<br />
<br />
* http://www.phoronix.com/scan.php?page=news_topic&q=Nouveau<br />
<br />
== AMD ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
As of now, the official Ubuntu docs are VERY detailed in the installation of the open-source and proprietary graphics drivers. It is recommended to use their documentation for your AMD card on the Ubuntu distros (Mint should be very similar, if not exactly the same). You can find that information here:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary AMD/ATI drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/ATIProprietary<br />
<br />
==== Fedora ====<br />
<br />
* [https://fedoraproject.org/wiki/Fglrx https://fedoraproject.org/wiki/Fglrx]<br />
<br />
==== Arch ====<br />
<br />
Arch Linux is pretty straightforward when it comes to this, and their documentation is quite concise. Please use the Arch Linux docs whenever possible for graphics issues:<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Fglrx<br />
<br />
=== Open-Source Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
We refer you to the same link:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
The installation of the open source ''radeon'' driver is straightforward, and is likely installed on your system by default. More information on the Debian ''radeon'' driver can be found here:<br />
<br />
* https://wiki.debian.org/AtiHowTo<br />
<br />
==== Fedora ====<br />
<br />
The open-source ''radeon'' driver should already be included in your system by default. If you are on a 64-bit version of Fedora, you would only need to install the 32-bit libraries for your graphics card from the Fedora repo and it should work fine with PlayOnLinux.<br />
<br />
==== Arch ====<br />
<br />
Arch Linux is pretty straightforward when it comes to this, and their documentation is quite concise. Please use the Arch Linux docs whenever possible for graphics issues:<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Radeon<br />
<br />
== Intel ==<br />
<br />
The Intel drivers are developed by the open-source community, so they are by far the easiest to install, as they pretty much will always come with your distro by default. More information on the Intel open-source drivers can be found here:<br />
<br />
* https://01.org/linuxgraphics/<br />
<br />
For the most part, this will cover how to make sure that you have the most up-to-date graphics stack for your Intel chipset. This applies exclusively to pure Intel graphics only. If you have, say, a mixed graphics card environment, like a laptop that has an Intel iGPU and a discrete NVIDIA card, please refer to the '''NVIDIA Optimus''' section<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
If you are already running a '''32-bit''' version of one of these systems, you should have everything that you need installed correctly by default. <br />
<br />
In the case of '''64-bit''' systems, you already have the 64-bit libraries for your graphics hardware. A package called '''multiarch-support''' should pull in the '''32-bit''' libraries, as well as a bunch of others.<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install multiarch-support<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
==== Debian ====<br />
<br />
The drivers should already be installed, but if it is not working with OpenGL or you get complaints about the 32-bit graphics libraries being missing, you can should try to run:<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install ia32-libs<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
If you are still having problems, consult the Debian docs here:<br />
<br />
* https://wiki.debian.org/Multiarch/HOWTO<br />
<br />
==== Fedora ====<br />
<br />
The open-source Intel driver should already be included in your system by default. If you are on a 64-bit version of Fedora, you would only need to install the 32-bit libraries for your graphics card from the Fedora repo and it should work fine with PlayOnLinux.<br />
<br />
==== Arch ====<br />
<br />
Arch Linux is pretty straightforward when it comes to this, and their documentation is quite concise. Please use the Arch Linux docs whenever possible for graphics issues:<br />
<br />
* https://wiki.archlinux.org/index.php/Intel_graphics<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Intel</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Graphics_Card_Drivers&diff=808Graphics Card Drivers2015-05-16T06:13:51Z<p>RoninDusette: /* Arch */</p>
<hr />
<div>In this section, we will try to cover the basics of getting the most out of your AMD, Nvidia, or Intel graphics card on your Linux system, specifically when using Wine/PlayOnLinux. This can get pretty lengthy, so expect this article to get exponentially bigger as time goes on.<br />
<br />
{{Info|This list is going to take a while to get full, so please be patient as we populate everything.}}<br />
<br />
For ease of use, we will break these down into different sections for the graphics card manufacturer, and then distro's within those categories. <br />
<br />
== NVIDIA ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
Most of the time, the easiest way is using the "Additional Drivers" dialogue. That does not always work though, and it sometimes will offer less-than-ideal versions of drivers for your NVIDIA card. If your card is supported by the current NVIDIA driver, the following command should pull in the required libraries:<br />
<br />
{{Console|sudo apt-get install nvidia-current}}<br />
<br />
You can also install other series of drivers (313.x, 319.x, 331.x, etc.) by appending the version name to them:<br />
<br />
'''Examples:'''<br />
<br />
{{Console|sudo apt-get install nvidia-331}}<br />
<br />
For the '''32-bit''' libraries, as long as ''libgl1-mesa-glx:i386'' and ''multiarch-support'' are installed, it should install them automatically. If, after you install them from the Ubuntu repositories, it does not show up, try to install those packages mentioned previously:<br />
<br />
{{Console|<br />
sudo apt-get install multiarch-support<br />
<br />
sudo apt-get install libgl1-mesa-glx:i386<br />
}}<br />
<br />
The manual installation is a bit more involved, but it is preferred by a lot of users.<br />
<br />
''Will add more later''<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary NVIDIA drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/NvidiaGraphicsDrivers<br />
<br />
==== Fedora ====<br />
<br />
* http://rpmfusion.org/Howto/nVidia<br />
<br />
==== Arch ====<br />
<br />
Arch Linux is pretty straightforward when it comes to this, and their documentation is quite concise. Please use the Arch Linux docs whenever possible for graphics issues:<br />
<br />
* https://wiki.archlinux.org/index.php/NVIDIA<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVidia/nvidia-drivers<br />
<br />
=== Optimus ===<br />
<br />
NVIDIA Optimus technology is a feature in laptops with newer Intel CPU's with integrated GPUs and discrete NVIDIA graphics cards that allows switching between graphics processors on-the-fly, to optimize the performance when needed, and maximizing battery life when not needing the discrete graphics card. More information on Optimus can be found here:<br />
<br />
* http://www.nvidia.com/object/optimus_technology.html<br />
<br />
==== Most distributions ====<br />
<br />
The current working solution is maintained by the '''Bumblebee Project'''. '''PRIME''' is not recommended, as it utilizes the open-source NVIDIA driver (''nouveau''), and will not give the performance desired for most games. The project's website has detailed documentation for most major distributions, so it is recommended to go by that:<br />
<br />
* http://bumblebee-project.org/<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVIDIA_Driver_with_Optimus_Laptops<br />
<br />
=== Open-Source Drivers ===<br />
<br />
Unfortunately, the open-source ''nouveau'' drivers are not really up-to-par on performance yet for gaming. Things are starting to look up, but there are a lot of caveats to running the open-source NVIDIA drivers. More information can be found here:<br />
<br />
* http://nouveau.freedesktop.org/wiki/<br />
<br />
* http://www.phoronix.com/scan.php?page=news_topic&q=Nouveau<br />
<br />
== AMD ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
As of now, the official Ubuntu docs are VERY detailed in the installation of the open-source and proprietary graphics drivers. It is recommended to use their documentation for your AMD card on the Ubuntu distros (Mint should be very similar, if not exactly the same). You can find that information here:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary AMD/ATI drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/ATIProprietary<br />
<br />
==== Fedora ====<br />
<br />
* [https://fedoraproject.org/wiki/Fglrx https://fedoraproject.org/wiki/Fglrx]<br />
<br />
==== Arch ====<br />
<br />
Arch Linux is pretty straightforward when it comes to this, and their documentation is quite concise. Please use the Arch Linux docs whenever possible for graphics issues:<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Fglrx<br />
<br />
=== Open-Source Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
We refer you to the same link:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
The installation of the open source ''radeon'' driver is straightforward, and is likely installed on your system by default. More information on the Debian ''radeon'' driver can be found here:<br />
<br />
* https://wiki.debian.org/AtiHowTo<br />
<br />
==== Fedora ====<br />
<br />
The open-source ''radeon'' driver should already be included in your system by default. If you are on a 64-bit version of Fedora, you would only need to install the 32-bit libraries for your graphics card from the Fedora repo and it should work fine with PlayOnLinux.<br />
<br />
==== Arch ====<br />
<br />
Arch Linux is pretty straightforward when it comes to this, and their documentation is quite concise. Please use the Arch Linux docs whenever possible for graphics issues:<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Radeon<br />
<br />
== Intel ==<br />
<br />
The Intel drivers are developed by the open-source community, so they are by far the easiest to install, as they pretty much will always come with your distro by default. More information on the Intel open-source drivers can be found here:<br />
<br />
* https://01.org/linuxgraphics/<br />
<br />
For the most part, this will cover how to make sure that you have the most up-to-date graphics stack for your Intel chipset. This applies exclusively to pure Intel graphics only. If you have, say, a mixed graphics card environment, like a laptop that has an Intel iGPU and a discrete NVIDIA card, please refer to the '''NVIDIA Optimus''' section<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
If you are already running a '''32-bit''' version of one of these systems, you should have everything that you need installed correctly by default. <br />
<br />
In the case of '''64-bit''' systems, you already have the 64-bit libraries for your graphics hardware. A package called '''multiarch-support''' should pull in the '''32-bit''' libraries, as well as a bunch of others.<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install multiarch-support<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
==== Debian ====<br />
<br />
The drivers should already be installed, but if it is not working with OpenGL or you get complaints about the 32-bit graphics libraries being missing, you can should try to run:<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install ia32-libs<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
If you are still having problems, consult the Debian docs here:<br />
<br />
* https://wiki.debian.org/Multiarch/HOWTO<br />
<br />
==== Fedora ====<br />
<br />
The open-source Intel driver should already be included in your system by default. If you are on a 64-bit version of Fedora, you would only need to install the 32-bit libraries for your graphics card from the Fedora repo and it should work fine with PlayOnLinux.<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/Intel_graphics<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Intel</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Graphics_Card_Drivers&diff=807Graphics Card Drivers2015-05-16T06:13:29Z<p>RoninDusette: /* Arch */</p>
<hr />
<div>In this section, we will try to cover the basics of getting the most out of your AMD, Nvidia, or Intel graphics card on your Linux system, specifically when using Wine/PlayOnLinux. This can get pretty lengthy, so expect this article to get exponentially bigger as time goes on.<br />
<br />
{{Info|This list is going to take a while to get full, so please be patient as we populate everything.}}<br />
<br />
For ease of use, we will break these down into different sections for the graphics card manufacturer, and then distro's within those categories. <br />
<br />
== NVIDIA ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
Most of the time, the easiest way is using the "Additional Drivers" dialogue. That does not always work though, and it sometimes will offer less-than-ideal versions of drivers for your NVIDIA card. If your card is supported by the current NVIDIA driver, the following command should pull in the required libraries:<br />
<br />
{{Console|sudo apt-get install nvidia-current}}<br />
<br />
You can also install other series of drivers (313.x, 319.x, 331.x, etc.) by appending the version name to them:<br />
<br />
'''Examples:'''<br />
<br />
{{Console|sudo apt-get install nvidia-331}}<br />
<br />
For the '''32-bit''' libraries, as long as ''libgl1-mesa-glx:i386'' and ''multiarch-support'' are installed, it should install them automatically. If, after you install them from the Ubuntu repositories, it does not show up, try to install those packages mentioned previously:<br />
<br />
{{Console|<br />
sudo apt-get install multiarch-support<br />
<br />
sudo apt-get install libgl1-mesa-glx:i386<br />
}}<br />
<br />
The manual installation is a bit more involved, but it is preferred by a lot of users.<br />
<br />
''Will add more later''<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary NVIDIA drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/NvidiaGraphicsDrivers<br />
<br />
==== Fedora ====<br />
<br />
* http://rpmfusion.org/Howto/nVidia<br />
<br />
==== Arch ====<br />
<br />
Arch Linux is pretty straightforward when it comes to this, and their documentation is quite concise. Please use the Arch Linux docs whenever possible for graphics issues:<br />
<br />
* https://wiki.archlinux.org/index.php/NVIDIA<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVidia/nvidia-drivers<br />
<br />
=== Optimus ===<br />
<br />
NVIDIA Optimus technology is a feature in laptops with newer Intel CPU's with integrated GPUs and discrete NVIDIA graphics cards that allows switching between graphics processors on-the-fly, to optimize the performance when needed, and maximizing battery life when not needing the discrete graphics card. More information on Optimus can be found here:<br />
<br />
* http://www.nvidia.com/object/optimus_technology.html<br />
<br />
==== Most distributions ====<br />
<br />
The current working solution is maintained by the '''Bumblebee Project'''. '''PRIME''' is not recommended, as it utilizes the open-source NVIDIA driver (''nouveau''), and will not give the performance desired for most games. The project's website has detailed documentation for most major distributions, so it is recommended to go by that:<br />
<br />
* http://bumblebee-project.org/<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVIDIA_Driver_with_Optimus_Laptops<br />
<br />
=== Open-Source Drivers ===<br />
<br />
Unfortunately, the open-source ''nouveau'' drivers are not really up-to-par on performance yet for gaming. Things are starting to look up, but there are a lot of caveats to running the open-source NVIDIA drivers. More information can be found here:<br />
<br />
* http://nouveau.freedesktop.org/wiki/<br />
<br />
* http://www.phoronix.com/scan.php?page=news_topic&q=Nouveau<br />
<br />
== AMD ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
As of now, the official Ubuntu docs are VERY detailed in the installation of the open-source and proprietary graphics drivers. It is recommended to use their documentation for your AMD card on the Ubuntu distros (Mint should be very similar, if not exactly the same). You can find that information here:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary AMD/ATI drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/ATIProprietary<br />
<br />
==== Fedora ====<br />
<br />
* [https://fedoraproject.org/wiki/Fglrx https://fedoraproject.org/wiki/Fglrx]<br />
<br />
==== Arch ====<br />
<br />
Arch Linux is pretty straightforward when it comes to this, and their documentation is quite concise. Please use the Arch Linux docs whenever possible for graphics issues:<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Fglrx<br />
<br />
=== Open-Source Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
We refer you to the same link:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
The installation of the open source ''radeon'' driver is straightforward, and is likely installed on your system by default. More information on the Debian ''radeon'' driver can be found here:<br />
<br />
* https://wiki.debian.org/AtiHowTo<br />
<br />
==== Fedora ====<br />
<br />
The open-source ''radeon'' driver should already be included in your system by default. If you are on a 64-bit version of Fedora, you would only need to install the 32-bit libraries for your graphics card from the Fedora repo and it should work fine with PlayOnLinux.<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Radeon<br />
<br />
== Intel ==<br />
<br />
The Intel drivers are developed by the open-source community, so they are by far the easiest to install, as they pretty much will always come with your distro by default. More information on the Intel open-source drivers can be found here:<br />
<br />
* https://01.org/linuxgraphics/<br />
<br />
For the most part, this will cover how to make sure that you have the most up-to-date graphics stack for your Intel chipset. This applies exclusively to pure Intel graphics only. If you have, say, a mixed graphics card environment, like a laptop that has an Intel iGPU and a discrete NVIDIA card, please refer to the '''NVIDIA Optimus''' section<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
If you are already running a '''32-bit''' version of one of these systems, you should have everything that you need installed correctly by default. <br />
<br />
In the case of '''64-bit''' systems, you already have the 64-bit libraries for your graphics hardware. A package called '''multiarch-support''' should pull in the '''32-bit''' libraries, as well as a bunch of others.<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install multiarch-support<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
==== Debian ====<br />
<br />
The drivers should already be installed, but if it is not working with OpenGL or you get complaints about the 32-bit graphics libraries being missing, you can should try to run:<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install ia32-libs<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
If you are still having problems, consult the Debian docs here:<br />
<br />
* https://wiki.debian.org/Multiarch/HOWTO<br />
<br />
==== Fedora ====<br />
<br />
The open-source Intel driver should already be included in your system by default. If you are on a 64-bit version of Fedora, you would only need to install the 32-bit libraries for your graphics card from the Fedora repo and it should work fine with PlayOnLinux.<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/Intel_graphics<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Intel</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Graphics_Card_Drivers&diff=806Graphics Card Drivers2015-05-16T06:12:57Z<p>RoninDusette: /* Arch */</p>
<hr />
<div>In this section, we will try to cover the basics of getting the most out of your AMD, Nvidia, or Intel graphics card on your Linux system, specifically when using Wine/PlayOnLinux. This can get pretty lengthy, so expect this article to get exponentially bigger as time goes on.<br />
<br />
{{Info|This list is going to take a while to get full, so please be patient as we populate everything.}}<br />
<br />
For ease of use, we will break these down into different sections for the graphics card manufacturer, and then distro's within those categories. <br />
<br />
== NVIDIA ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
Most of the time, the easiest way is using the "Additional Drivers" dialogue. That does not always work though, and it sometimes will offer less-than-ideal versions of drivers for your NVIDIA card. If your card is supported by the current NVIDIA driver, the following command should pull in the required libraries:<br />
<br />
{{Console|sudo apt-get install nvidia-current}}<br />
<br />
You can also install other series of drivers (313.x, 319.x, 331.x, etc.) by appending the version name to them:<br />
<br />
'''Examples:'''<br />
<br />
{{Console|sudo apt-get install nvidia-331}}<br />
<br />
For the '''32-bit''' libraries, as long as ''libgl1-mesa-glx:i386'' and ''multiarch-support'' are installed, it should install them automatically. If, after you install them from the Ubuntu repositories, it does not show up, try to install those packages mentioned previously:<br />
<br />
{{Console|<br />
sudo apt-get install multiarch-support<br />
<br />
sudo apt-get install libgl1-mesa-glx:i386<br />
}}<br />
<br />
The manual installation is a bit more involved, but it is preferred by a lot of users.<br />
<br />
''Will add more later''<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary NVIDIA drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/NvidiaGraphicsDrivers<br />
<br />
==== Fedora ====<br />
<br />
* http://rpmfusion.org/Howto/nVidia<br />
<br />
==== Arch ====<br />
<br />
Arch Linux is pretty straightforward when it comes to this, and their documentation is quite concise. Please use the Arch Linux docs whenever possible for graphics issues:<br />
<br />
* https://wiki.archlinux.org/index.php/NVIDIA<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVidia/nvidia-drivers<br />
<br />
=== Optimus ===<br />
<br />
NVIDIA Optimus technology is a feature in laptops with newer Intel CPU's with integrated GPUs and discrete NVIDIA graphics cards that allows switching between graphics processors on-the-fly, to optimize the performance when needed, and maximizing battery life when not needing the discrete graphics card. More information on Optimus can be found here:<br />
<br />
* http://www.nvidia.com/object/optimus_technology.html<br />
<br />
==== Most distributions ====<br />
<br />
The current working solution is maintained by the '''Bumblebee Project'''. '''PRIME''' is not recommended, as it utilizes the open-source NVIDIA driver (''nouveau''), and will not give the performance desired for most games. The project's website has detailed documentation for most major distributions, so it is recommended to go by that:<br />
<br />
* http://bumblebee-project.org/<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVIDIA_Driver_with_Optimus_Laptops<br />
<br />
=== Open-Source Drivers ===<br />
<br />
Unfortunately, the open-source ''nouveau'' drivers are not really up-to-par on performance yet for gaming. Things are starting to look up, but there are a lot of caveats to running the open-source NVIDIA drivers. More information can be found here:<br />
<br />
* http://nouveau.freedesktop.org/wiki/<br />
<br />
* http://www.phoronix.com/scan.php?page=news_topic&q=Nouveau<br />
<br />
== AMD ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
As of now, the official Ubuntu docs are VERY detailed in the installation of the open-source and proprietary graphics drivers. It is recommended to use their documentation for your AMD card on the Ubuntu distros (Mint should be very similar, if not exactly the same). You can find that information here:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary AMD/ATI drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/ATIProprietary<br />
<br />
==== Fedora ====<br />
<br />
* [https://fedoraproject.org/wiki/Fglrx https://fedoraproject.org/wiki/Fglrx]<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Fglrx<br />
<br />
=== Open-Source Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
We refer you to the same link:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
The installation of the open source ''radeon'' driver is straightforward, and is likely installed on your system by default. More information on the Debian ''radeon'' driver can be found here:<br />
<br />
* https://wiki.debian.org/AtiHowTo<br />
<br />
==== Fedora ====<br />
<br />
The open-source ''radeon'' driver should already be included in your system by default. If you are on a 64-bit version of Fedora, you would only need to install the 32-bit libraries for your graphics card from the Fedora repo and it should work fine with PlayOnLinux.<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Radeon<br />
<br />
== Intel ==<br />
<br />
The Intel drivers are developed by the open-source community, so they are by far the easiest to install, as they pretty much will always come with your distro by default. More information on the Intel open-source drivers can be found here:<br />
<br />
* https://01.org/linuxgraphics/<br />
<br />
For the most part, this will cover how to make sure that you have the most up-to-date graphics stack for your Intel chipset. This applies exclusively to pure Intel graphics only. If you have, say, a mixed graphics card environment, like a laptop that has an Intel iGPU and a discrete NVIDIA card, please refer to the '''NVIDIA Optimus''' section<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
If you are already running a '''32-bit''' version of one of these systems, you should have everything that you need installed correctly by default. <br />
<br />
In the case of '''64-bit''' systems, you already have the 64-bit libraries for your graphics hardware. A package called '''multiarch-support''' should pull in the '''32-bit''' libraries, as well as a bunch of others.<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install multiarch-support<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
==== Debian ====<br />
<br />
The drivers should already be installed, but if it is not working with OpenGL or you get complaints about the 32-bit graphics libraries being missing, you can should try to run:<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install ia32-libs<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
If you are still having problems, consult the Debian docs here:<br />
<br />
* https://wiki.debian.org/Multiarch/HOWTO<br />
<br />
==== Fedora ====<br />
<br />
The open-source Intel driver should already be included in your system by default. If you are on a 64-bit version of Fedora, you would only need to install the 32-bit libraries for your graphics card from the Fedora repo and it should work fine with PlayOnLinux.<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/Intel_graphics<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Intel</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Main_Page&diff=805Main Page2015-05-16T01:12:49Z<p>RoninDusette: /* User Documentation */</p>
<hr />
<div>Welcome to the PlayOnLinux and PlayOnMac wiki. Here you will find tutorials regarding the use of PlayOnLinux or PlayOnMac, and explanations of their various features. You'll also find guides explaining how to create installation scripts, a description of the commands available, API documentation, advanced topics, and more.<br />
<br />
For any additional questions that do not have an answer in this wiki, do not hesitate to go to the [https://www.playonlinux.com/en/forums.html forums].<br />
<br />
== User Documentation ==<br />
* [[Installing PlayOnLinux]]<br />
* [[Installing PlayOnMac]]<br />
* [[The PlayOnLinux Filesystem|The PlayOnLinux Filesystem]]<br />
* [[The PlayOnMac Filesystem|The PlayOnMac Filesystem]]<br />
* [[First Use|Guide for first use of the software]]<br />
* [[The Configuration Window|The Configuration Window]]<br />
* [[Components and Functions|Components and Functions]]<br />
* [[Managing Wine Versions|Managing Wine Versions]]<br />
* [[Manual Installations|Manual Installations]]<br />
* [[FAQ|Frequently Asked Questions]]<br />
<br />
== Troubleshooting ==<br />
* [[Troubleshooting Common Problems|Troubleshooting Common Problems]]<br />
* [[Graphics Card Drivers|Graphics Card Drivers]]<br />
* [[How to Read Debug Logs|How to Read Debug Logs]]<br />
* [[Common Linux Libraries That Wine Might Need|Common Linux Libraries That Wine Might Need]]<br />
<br />
== The Forums, Bug Reports, and Script Contribution ==<br />
* [[How to Post in the Forums|How to Post in the Forums]]<br />
* [[How to Post a Bug Report|How to Post a Bug Report]]<br />
* [[How to Contribute a Script|How to Contribute a Script]]<br />
* [[How to Request a Patched Version of Wine|How to Request a Patched Version of Wine]]<br />
<br />
== Writing a script ==<br />
* [[Scripting - Chapter 1: Getting to know Bash|Chapter 1: Getting to know Bash]]<br />
* [[Scripting - Chapter 2: Basic Functions|Chapter 2: Basic Functions]]<br />
* [[Scripting - Chapter 3: Variables|Chapter 3: Variables]]<br />
* [[Scripting - Chapter 4: Conditions|Chapter 4: Conditions]]<br />
* [[Scripting - Chapter 5: Wine|Chapter 5: Wine]]<br />
* [[Scripting - Chapter 6: The Filesystem|Chapter 6: The Filesystem]]<br />
* [[Scripting - Chapter 7: Installation Media|Chapter 7: Installation Media]]<br />
* [[Scripting - Chapter 8: My First Real Script|Chapter 8: My First Real Script]]<br />
* [[Scripting - Chapter 9: Standardization|Chapter 9: Standardization]]<br />
* [[Scripting - Chapter 10: Script Translation|Chapter 10: Script Translation]]<br />
* [[Scripting - Chapter 11: List of Functions|Chapter 11: List of Functions]]<br />
== Glossary ==<br />
* [[POL & POM Terminology|POL & POM Terminology]]<br />
* [[Wine; what is it?|Wine; what is it?]]<br />
<br />
== Advanced PlayOnLinux ==<br />
* [[How to move PlayOnLinux virtual drives to another disk|How to move PlayOnLinux virtual drives to another disk]]<br />
* [[PlayOnLinux DOSBox support HOWTO]]<br />
* [https://github.com/PlayOnLinux/POL-POM-4 PlayOnLinux/PlayOnMac source code]<br />
* [https://github.com/PlayOnLinux/wine-patches Patch repository]<br />
* [[Setting up WineASIO with PlayOnLinux|Setting up WineASIO with PlayOnLinux]]<br />
* [[Using Printers with PlayOnLinux|Using Printers with PlayOnLinux]]<br />
<br />
== Advanced PlayOnMac ==<br />
<br />
* [https://github.com/PlayOnLinux/POL-POM-4 PlayOnLinux/PlayOnMac source code]<br />
* [https://github.com/PlayOnLinux/wine-patches Patch repository]<br />
<br />
== Advanced Wine ==<br />
''' Wine-Wiki '''<br />
<br />
* [http://wine-wiki.org/ Wine-wiki. Somewhat outdated, but covers a LOT of advanced Wine topics]<br />
<br />
''' WineHQ '''<br />
<br />
* [https://www.winehq.org/devel/ Wine development links]<br />
* [http://wiki.winehq.org/DeveloperFaq Wine developer FAQ]<br />
* [https://www.winehq.org/docs/winedev-guide/index Wine developer's guide]<br />
* [http://wiki.winehq.org/Developers-Hints Wine developer hints]<br />
* [http://wiki.winehq.org/HackingTips Wine hacking tips]<br />
<br />
== Advanced WineBuild ==<br />
* [[Cross-compile Wine for OSX on Linux| How to cross-compile Wine for Mac OSX on Linux]]<br />
* [https://github.com/PlayOnLinux/WineBuild POL's WineBuild source code]</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Main_Page&diff=804Main Page2015-05-16T01:12:15Z<p>RoninDusette: /* User Documentation */</p>
<hr />
<div>Welcome to the PlayOnLinux and PlayOnMac wiki. Here you will find tutorials regarding the use of PlayOnLinux or PlayOnMac, and explanations of their various features. You'll also find guides explaining how to create installation scripts, a description of the commands available, API documentation, advanced topics, and more.<br />
<br />
For any additional questions that do not have an answer in this wiki, do not hesitate to go to the [https://www.playonlinux.com/en/forums.html forums].<br />
<br />
== User Documentation ==<br />
* [[Installing PlayOnLinux]]<br />
* [[Installing PlayOnMac]]<br />
* [[First Use|Guide for first use of the software]]<br />
* [[The Configuration Window|The Configuration Window]]<br />
* [[Components and Functions|Components and Functions]]<br />
* [[Managing Wine Versions|Managing Wine Versions]]<br />
* [[The PlayOnLinux Filesystem|The PlayOnLinux Filesystem]]<br />
* [[The PlayOnMac Filesystem|The PlayOnMac Filesystem]]<br />
* [[Manual Installations|Manual Installations]]<br />
* [[FAQ|Frequently Asked Questions]]<br />
<br />
== Troubleshooting ==<br />
* [[Troubleshooting Common Problems|Troubleshooting Common Problems]]<br />
* [[Graphics Card Drivers|Graphics Card Drivers]]<br />
* [[How to Read Debug Logs|How to Read Debug Logs]]<br />
* [[Common Linux Libraries That Wine Might Need|Common Linux Libraries That Wine Might Need]]<br />
<br />
== The Forums, Bug Reports, and Script Contribution ==<br />
* [[How to Post in the Forums|How to Post in the Forums]]<br />
* [[How to Post a Bug Report|How to Post a Bug Report]]<br />
* [[How to Contribute a Script|How to Contribute a Script]]<br />
* [[How to Request a Patched Version of Wine|How to Request a Patched Version of Wine]]<br />
<br />
== Writing a script ==<br />
* [[Scripting - Chapter 1: Getting to know Bash|Chapter 1: Getting to know Bash]]<br />
* [[Scripting - Chapter 2: Basic Functions|Chapter 2: Basic Functions]]<br />
* [[Scripting - Chapter 3: Variables|Chapter 3: Variables]]<br />
* [[Scripting - Chapter 4: Conditions|Chapter 4: Conditions]]<br />
* [[Scripting - Chapter 5: Wine|Chapter 5: Wine]]<br />
* [[Scripting - Chapter 6: The Filesystem|Chapter 6: The Filesystem]]<br />
* [[Scripting - Chapter 7: Installation Media|Chapter 7: Installation Media]]<br />
* [[Scripting - Chapter 8: My First Real Script|Chapter 8: My First Real Script]]<br />
* [[Scripting - Chapter 9: Standardization|Chapter 9: Standardization]]<br />
* [[Scripting - Chapter 10: Script Translation|Chapter 10: Script Translation]]<br />
* [[Scripting - Chapter 11: List of Functions|Chapter 11: List of Functions]]<br />
== Glossary ==<br />
* [[POL & POM Terminology|POL & POM Terminology]]<br />
* [[Wine; what is it?|Wine; what is it?]]<br />
<br />
== Advanced PlayOnLinux ==<br />
* [[How to move PlayOnLinux virtual drives to another disk|How to move PlayOnLinux virtual drives to another disk]]<br />
* [[PlayOnLinux DOSBox support HOWTO]]<br />
* [https://github.com/PlayOnLinux/POL-POM-4 PlayOnLinux/PlayOnMac source code]<br />
* [https://github.com/PlayOnLinux/wine-patches Patch repository]<br />
* [[Setting up WineASIO with PlayOnLinux|Setting up WineASIO with PlayOnLinux]]<br />
* [[Using Printers with PlayOnLinux|Using Printers with PlayOnLinux]]<br />
<br />
== Advanced PlayOnMac ==<br />
<br />
* [https://github.com/PlayOnLinux/POL-POM-4 PlayOnLinux/PlayOnMac source code]<br />
* [https://github.com/PlayOnLinux/wine-patches Patch repository]<br />
<br />
== Advanced Wine ==<br />
''' Wine-Wiki '''<br />
<br />
* [http://wine-wiki.org/ Wine-wiki. Somewhat outdated, but covers a LOT of advanced Wine topics]<br />
<br />
''' WineHQ '''<br />
<br />
* [https://www.winehq.org/devel/ Wine development links]<br />
* [http://wiki.winehq.org/DeveloperFaq Wine developer FAQ]<br />
* [https://www.winehq.org/docs/winedev-guide/index Wine developer's guide]<br />
* [http://wiki.winehq.org/Developers-Hints Wine developer hints]<br />
* [http://wiki.winehq.org/HackingTips Wine hacking tips]<br />
<br />
== Advanced WineBuild ==<br />
* [[Cross-compile Wine for OSX on Linux| How to cross-compile Wine for Mac OSX on Linux]]<br />
* [https://github.com/PlayOnLinux/WineBuild POL's WineBuild source code]</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=The_Configuration_Window&diff=803The Configuration Window2015-05-16T00:19:37Z<p>RoninDusette: </p>
<hr />
<div>The configuration window is where most of the action happens when it comes to customization, manual installs, testing, and debugging. Here we will cover all of the different items, tabs, fields, and buttons in detail. Let's get started.<br />
<br />
== The Main Configuration Window ==<br />
<br />
When you first install install PlayOnLinux/PlayOnMac and try to open the '''Configure''' window, it will be blank:<br />
<br />
<br />
https://www.playonlinux.com/images/uploads/239.jpg<br />
<br />
<br />
This is completely normal. It will start getting filled up after you install some software. After you install a few things, you will see more options:<br />
<br />
<br />
https://www.playonlinux.com/images/uploads/241.jpg<br />
<br />
<br />
=== (1) - Virtual Drive/Shortcut List ===<br />
<br />
For each game or application that you install, a virtual drive and a shortcut will be associated with that application. The icon next to the Virtual Drive's name is the architecture of the '''WINEPREFIX'''. It will be either ''32'' or ''64'', indicating whether it is 32-bit or 64-bit.<br />
<br />
=== (2) - General tab ===<br />
<br />
The general tab has a number of options available to customize the virtual drive or the actual shortcut for running the app. This will be covered more in a moment. This is the default tab that you will see when highlighting a virtual drive or a shortcut.<br />
<br />
=== (3) - Wine tab ===<br />
<br />
This tab gives you quite a few options for configuring Wine itself. Any configuration done here is specific to the virtual drive or virtual drive of the shortcut highlighted in the Virtual Drive List. <br />
<br />
=== (4) - Install Components tab ===<br />
<br />
Install Components gives you access to a ton of dependencies that might be need to run applications through Wine. This includes .NET, DirectX, Microsoft Fonts, and much, much more. This list is covered in detail [[Components and Functions|here]].<br />
<br />
=== (5) - Display tab ===<br />
<br />
This is where you will be able to change to modify some of the registry entries for Wine's graphics support without actually going to the registry. Disable/Enable GLSL support, reported video memory size, etc..<br />
<br />
=== (6) - Shortcut button ===<br />
<br />
Clicking this button will search for .exe files in the selected virtual drive, and present you with a list of executables to create a shortcut from. You are also given an option to manually browse for an .exe.<br />
<br />
=== (7) - Miscellaneous tab ===<br />
<br />
Other features that do not fit into other categories. Running an .exe in the selected virtual drive, opening the POL Shell and virtual drive's directory, Mouse warp override options are found here.<br />
<br />
=== (8) - Virtual Drive name ===<br />
<br />
The name of the virtual drive.<br />
<br />
=== (9) - Name of shortcut in virtual drive ===<br />
<br />
The name of a shortcut contained within that virtual drive. You can have as many or as few as you would like. It is not uncommon to have multiple shortcuts, especially for manual installs or virtual drives with multiple apps installed.<br />
<br />
=== (10) - New Virtual Drive button ===<br />
<br />
This button opens a dialogue to create a new virtual drive. Useful for manual installs and testing. Please note that you will need to already have a '''POL WineBuild''' installed ('''Tools -> Manage Wine Versions''') to use this function correctly.<br />
<br />
=== (11) - Remove Virtual Drive button ===<br />
<br />
Click to delete the highlighted virtual drive. Use this with caution, as everything that is in the virtual drive will be deleted.<br />
<br />
=== (12) - Virtual Drive/Shortcut name field ===<br />
<br />
Depending on what you have highlighted (either a shortcut or a virtual drive), this will show you the name of it and allow you to modify it. It is recommended not to alter the virtual drive name once created, though the shortcut name is fine to customize in most cases.<br />
<br />
=== (13) - Wine Version selection ===<br />
<br />
A dropdown menu containing a list of installed Wine versions available for use in this virtual drive. Whichever is listed initially is the Wine versions in use in the highlighted virtual drive. The "plus" button allows you to open the '''Manage Wine Versions''' dialogue directly from this tab.<br />
<br />
=== (14) - Debug Flags ===<br />
<br />
These are debug flags to be used when launching a POL-installed application in '''Debug Mode'''. '''Debug Mode''' is covered in more detail here:<br />
<br />
[[How to Read Debug Logs|How to Read Debug Logs]]<br />
<br />
[http://wiki.playonlinux.com/index.php/Home#Advanced_Wine_Topics Advanced Wine Topics]<br />
<br />
=== (15) - Virtual Drive selection ===<br />
<br />
When a shortcut is highlighted, this will allow you to assign the shortcut to a virtual drive. Whatever is initially listed is the current home of that shortcut. <br />
<br />
=== (16) - Arguments field ===<br />
<br />
When a shortcut is highlighted, this allows you to append command-line arguments to the executable that the shortcut links to. Useful for adding commanding-line options to a game's executable to enable in-game options and things like that.<br />
<br />
== The Wine Tab ==<br />
<br />
https://www.playonlinux.com/images/uploads/242.jpg<br />
<br />
=== (1) - Configure Wine ===<br />
<br />
This opens '''winecfg''' in the selected virtual drive. This is where you can set the version of Windows for the virtual drive, as well as set the virtual desktop settings and disks reported to Wine. For more information, check [http://wiki.winehq.org/winecfg here].<br />
<br />
=== (2) - Registry Editor ===<br />
<br />
Open up the Wine registry editor. Used for manually manipulating the Wine registry. For more information, check [http://wiki.winehq.org/regedit here].<br />
<br />
=== (3) - Windows Reboot ===<br />
<br />
Simply emulate a Windows reboot. Required by some applications during install.<br />
<br />
=== (4) - Repair virtual drive ===<br />
<br />
Essentially runs the process for creating a new virtual drive in the highlighted virtual drive. This is used in case the virtual drive fails to build correctly, or if a component/dependency for Wine fails to install or download correctly.<br />
<br />
=== (5) - Wine uninstaller ===<br />
<br />
A tool for uninstalling certain components out of a virtual drive, like Gecko, wine-mono, etc.. For more information, check [http://wiki.winehq.org/uninstaller here].<br />
<br />
=== (6) - Kill processes ===<br />
<br />
Kills all processes in virtual drive.<br />
<br />
=== (7) - Task manager ===<br />
<br />
Opens the Wine task manager, which is similar to the one found in Windows, in the highlighted virtual drive.<br />
<br />
=== (8) - Command prompt ===<br />
<br />
Opens a command prompt that emulates the Windows command prompt in the highlighted virtual drive. [http://wiki.winehq.org/cmd http://wiki.winehq.org/cmd]<br />
<br />
== Install Components tab ==<br />
<br />
This tab is where you will find dependencies to install. It is very similar to the functions in ''winetricks'', giving you the ability to automatically install dependencies that may be needed by Wine for certain applications. <br />
<br />
The sheer complexity, size, and detail of this tab's content necessitates an entire section unto itself. That section can be viewed here:<br />
<br />
* [[Components and Functions|Components and Functions]]<br />
<br />
== Display tab ==<br />
<br />
The '''Display tab''' gives you access to certain options that usually need to be set in the registry by hand. Off-screen rendering, GLSL support, and other options are found here.<br />
<br />
<br />
https://www.playonlinux.com/images/uploads/249.jpg<br />
<br />
<br />
<br />
=== (1) - GLSL Support ===<br />
<br />
Available options:<br />
<br />
* ''default''<br />
* ''enabled''<br />
* ''disabled''<br />
<br />
=== (2) - Direct Draw Renderer ===<br />
<br />
Available options:<br />
<br />
* ''default''<br />
* ''gdi''<br />
* ''opengl''<br />
<br />
=== (3) - Video memory size ===<br />
<br />
Available options:<br />
<br />
* ''default''<br />
* ''list of common memory sizes''<br />
<br />
=== (4) - Offscreen rendering mode ===<br />
<br />
Available options:<br />
<br />
* ''default''<br />
* ''fbo''<br />
* ''backbuffer''<br />
* ''pbuffer''<br />
<br />
=== (5) - Render target mode lock ===<br />
<br />
Available options:<br />
<br />
* ''default''<br />
* ''disabled''<br />
* ''readdraw''<br />
* ''readtex''<br />
<br />
=== (6) - Multisampling ===<br />
<br />
Available options:<br />
<br />
* ''default''<br />
* ''enabled''<br />
* ''disabled''<br />
<br />
=== (7) - Strict Draw Ordering ===<br />
<br />
Available options:<br />
<br />
* ''default''<br />
* ''enabled''<br />
* ''disabled''<br />
<br />
== Miscellaneous tab ==<br />
<br />
<br />
The '''Miscellaneous tab''' provides functions that otherwise have no other proper place. These include opening up a POL shell in your default terminal, prefixing commands to shortcuts, and more.<br />
<br />
<br />
https://www.playonlinux.com/images/uploads/254.jpg<br />
<br />
<br />
<br />
=== (1) - Mouse warp override ===<br />
<br />
Some games have issues with the mouse. This option has been known to correct this glitch in a lot of games.<br />
<br />
Available options:<br />
<br />
* ''default''<br />
* ''enable''<br />
* ''disable''<br />
* ''force''<br />
<br />
=== (2) - Enter program's virtual drive or directory ===<br />
<br />
Depending on what is highlighted on the left:<br />
<br />
'''A:''' If the virtual drive is highlighted, you can open the virtual drive's directory in your system's default file browser<br />
<br />
''or''<br />
<br />
'''B:''' If the program shortcut is highlighted, you can open up the folder that the shortcut's executable file is located at in your system's default file browser<br />
<br />
=== (3) - Open a shell ===<br />
<br />
Open up your system's default terminal under the context of the virtual drive or program highlighted. You will have full access to the POL scripting API calls from there, as well as already be sandboxed within that virtual drive.<br />
<br />
=== (4) - Run a .exe in this virtual drive ===<br />
<br />
Allows you to run an .exe or .msi file within the context of the virtual drive or program highlighted. Will use whatever WineBuild is attached to that particular virtual drive, as well as sandboxing any action that happens therein. <br />
<br />
=== (5) - Command to exec before running the program ===<br />
<br />
When a program shortcut is highlighted, you can use this box to prefix commands to the shortcut. Handy in, say, the case of laptops with Nvidia and Intel graphics, and you need to use prefix ''primusrun'' or ''optirun'' before starting a particular game.</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Using_Printers_with_PlayOnLinux&diff=802Using Printers with PlayOnLinux2015-05-08T17:08:11Z<p>RoninDusette: Created page with "Coming soon..."</p>
<hr />
<div>Coming soon...</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Main_Page&diff=801Main Page2015-05-08T17:07:54Z<p>RoninDusette: /* Advanced PlayOnLinux */</p>
<hr />
<div>Welcome to the PlayOnLinux and PlayOnMac wiki. Here you will find tutorials regarding the use of PlayOnLinux or PlayOnMac, and explanations of their various features. You'll also find guides explaining how to create installation scripts, a description of the commands available, API documentation, advanced topics, and more.<br />
<br />
For any additional questions that do not have an answer in this wiki, do not hesitate to go to the [https://www.playonlinux.com/en/forums.html forums].<br />
<br />
== User Documentation ==<br />
* [[Installing PlayOnLinux]]<br />
* [[Installing PlayOnMac]]<br />
* [[First Use|Guide for first use of the software]]<br />
* [[The Configuration Window|The Configuration Window]]<br />
* [[The PlayOnLinux Filesystem|The PlayOnLinux Filesystem]]<br />
* [[The PlayOnMac Filesystem|The PlayOnMac Filesystem]]<br />
* [[Managing Wine Versions|Managing Wine Versions]]<br />
* [[Manual Installations|Manual Installations]]<br />
* [[Components and Functions|Components and Functions]]<br />
* [[FAQ|Frequently Asked Questions]]<br />
<br />
== Troubleshooting ==<br />
* [[Troubleshooting Common Problems|Troubleshooting Common Problems]]<br />
* [[Graphics Card Drivers|Graphics Card Drivers]]<br />
* [[How to Read Debug Logs|How to Read Debug Logs]]<br />
* [[Common Linux Libraries That Wine Might Need|Common Linux Libraries That Wine Might Need]]<br />
<br />
== The Forums, Bug Reports, and Script Contribution ==<br />
* [[How to Post in the Forums|How to Post in the Forums]]<br />
* [[How to Post a Bug Report|How to Post a Bug Report]]<br />
* [[How to Contribute a Script|How to Contribute a Script]]<br />
* [[How to Request a Patched Version of Wine|How to Request a Patched Version of Wine]]<br />
<br />
== Writing a script ==<br />
* [[Scripting - Chapter 1: Getting to know Bash|Chapter 1: Getting to know Bash]]<br />
* [[Scripting - Chapter 2: Basic Functions|Chapter 2: Basic Functions]]<br />
* [[Scripting - Chapter 3: Variables|Chapter 3: Variables]]<br />
* [[Scripting - Chapter 4: Conditions|Chapter 4: Conditions]]<br />
* [[Scripting - Chapter 5: Wine|Chapter 5: Wine]]<br />
* [[Scripting - Chapter 6: The Filesystem|Chapter 6: The Filesystem]]<br />
* [[Scripting - Chapter 7: Installation Media|Chapter 7: Installation Media]]<br />
* [[Scripting - Chapter 8: My First Real Script|Chapter 8: My First Real Script]]<br />
* [[Scripting - Chapter 9: Standardization|Chapter 9: Standardization]]<br />
* [[Scripting - Chapter 10: Script Translation|Chapter 10: Script Translation]]<br />
* [[Scripting - Chapter 11: List of Functions|Chapter 11: List of Functions]]<br />
== Glossary ==<br />
* [[POL & POM Terminology|POL & POM Terminology]]<br />
* [[Wine; what is it?|Wine; what is it?]]<br />
<br />
== Advanced PlayOnLinux ==<br />
* [[How to move PlayOnLinux virtual drives to another disk|How to move PlayOnLinux virtual drives to another disk]]<br />
* [[PlayOnLinux DOSBox support HOWTO]]<br />
* [https://github.com/PlayOnLinux/POL-POM-4 PlayOnLinux/PlayOnMac source code]<br />
* [https://github.com/PlayOnLinux/wine-patches Patch repository]<br />
* [[Setting up WineASIO with PlayOnLinux|Setting up WineASIO with PlayOnLinux]]<br />
* [[Using Printers with PlayOnLinux|Using Printers with PlayOnLinux]]<br />
<br />
== Advanced PlayOnMac ==<br />
<br />
* [https://github.com/PlayOnLinux/POL-POM-4 PlayOnLinux/PlayOnMac source code]<br />
* [https://github.com/PlayOnLinux/wine-patches Patch repository]<br />
<br />
== Advanced Wine ==<br />
''' Wine-Wiki '''<br />
<br />
* [http://wine-wiki.org/ Wine-wiki. Somewhat outdated, but covers a LOT of advanced Wine topics]<br />
<br />
''' WineHQ '''<br />
<br />
* [https://www.winehq.org/devel/ Wine development links]<br />
* [http://wiki.winehq.org/DeveloperFaq Wine developer FAQ]<br />
* [https://www.winehq.org/docs/winedev-guide/index Wine developer's guide]<br />
* [http://wiki.winehq.org/Developers-Hints Wine developer hints]<br />
* [http://wiki.winehq.org/HackingTips Wine hacking tips]<br />
<br />
== Advanced WineBuild ==<br />
* [[Cross-compile Wine for OSX on Linux| How to cross-compile Wine for Mac OSX on Linux]]<br />
* [https://github.com/PlayOnLinux/WineBuild POL's WineBuild source code]</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Troubleshooting_Common_Problems&diff=791Troubleshooting Common Problems2015-05-01T15:52:52Z<p>RoninDusette: /* Error */</p>
<hr />
<div>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.<br />
<br />
When trying a possible solution for an issue, please only try '''ONE''' solution at a time, and test to see if it worked. <br />
<br />
== p11-kit: couldn't load module: ... ==<br />
<br />
=== Error ===<br />
<br />
{{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}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Mostly users of Debian, Ubuntu, Kubuntu, etc., Mint (and derivatives), 64-bit systems.<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== Install 32-bit version of p11-kit-trust.so ====<br />
<br />
<pre class='code bash'><br />
sudo apt-get install p11-kit-modules:i386<br />
</pre><br />
<br />
==== Create a symlink ====<br />
<br />
''found at http://askubuntu.com/a/384018''<br />
<br />
<pre class='code bash'><br />
sudo /usr/local/bin/getlibs -p p11-kit:i386<br />
sudo ln -s /usr/lib32/i386-linux-gnu/pkcs11/p11-kit-trust.so /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so<br />
</pre><br />
<br />
== Error in FS_Check ==<br />
<br />
=== Error ===<br />
<br />
{{Console|The following file is located on a fuse filesystem. It might prevent wine from working}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Anyone trying to run an executable file in Wine/POL that is located on an NTFS filesystem.<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== Move executable to a native Linux filesystem ====<br />
<br />
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.<br />
<br />
== Failed to use ICMP ==<br />
<br />
=== Error ===<br />
<br />
{{Console|err:winediag:IcmpCreateFile Failed to use ICMP (network ping), this requires special permissions.<br />
}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
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.<br />
<br />
=== What causes this error? ===<br />
<br />
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? ;)<br />
<br />
=== Common solutions ===<br />
<br />
==== Give rights to POL's WineBuild ====<br />
<br />
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.<br />
<br />
For instance, '''AION'''.<br />
<br />
All of POL's WineBuilds are stored in ~/.PlayOnLinux/wine/<br />
<br />
Within this folder, you have different sub-folders for architecture, and then Wine version. In the case of '''AION''':<br />
<br />
{{Console|/home/username/.PlayOnLinux/wine/linux-x86/1.7.36}}<br />
<br />
Find out which Wine version your application needs:<br />
<br />
# Open the Configuration Window<br />
# In the General tab, when your virtual drive is selected, look at the name of the version of Wine in use. <br />
<br />
Now, the command you would want to run is:<br />
<br />
'''NOTE''': ''Do NOT copy and paste these commands. They need to be modified for your particular situation.''<br />
<br />
{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine}}<br />
<br />
or<br />
<br />
{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine-preloader}}<br />
<br />
'''NOTE:''' ''I have seen both bin/wine and bin/wine-preloader shown in examples, so for posterity, I am including both.''<br />
<br />
Essentially, the syntax for this is as follows:<br />
<br />
{{Console|sudo setcap cap_net_raw+epi /home/'''username'''/.PlayOnLinux/wine/'''WineArchitecture'''/'''WineVersion'''/bin/wine}}<br />
<br />
Replace: <br />
<br />
* '''username''' with your current username<br />
<br />
* '''Wine Architecture''' with either '''linux-x86''' (32-bit virtual drive) or '''linux-amd64''' (64-bit virtual drive)<br />
<br />
* '''Wine Version''' with the '''EXACT''' name listed in the '''Wine dropdown menu''' in the '''General tab''' of the ''' Configuration Window'''<br />
<br />
== Error! Files mismatch ==<br />
<br />
=== Error ===<br />
<br />
{{Console|''someurl''<br />
<br />
<br />
Error! Files mismatch<br />
<br />
<br />
Local: ''md5resultexpected''<br />
<br />
Server: ''md5resultdownloaded''<br />
<br />
<br />
<br />
Do you want to retry?<br />
}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
This can happen to any user on any system. It is also architecture agnostic.<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== File bug report with POL ====<br />
<br />
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.).<br />
<br />
== The application you are trying to install needs administrator rights... ==<br />
<br />
=== Error ===<br />
<br />
{{Console|The application you are trying to install needs administrator rights to function correctly.}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Anyone on any distro may see this error<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== File bug report with WineHQ ====<br />
<br />
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:<br />
<br />
* [https://bugs.winehq.org/ WineHQ's Bugzilla]<br />
<br />
== League of Legends Stuck on Logo (after Champ Select) ==<br />
<br />
=== Error ===<br />
<br />
League of Legends simply stalls at the logo after the champion select dialogue.<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Anyone on any distro may see this error<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== Install needed components ====<br />
<br />
Instructions adapted from this thread:<br />
<br />
[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]<br />
<br />
# Install in POL: d3dx10, d3dx11, d3dx9 (only d3dx9, not the other d3dx9_etc) and directx9<br />
# 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"<br />
<br />
== PlayOnMac: SECUR32_initNTLMSP ntlm_auth was not found or is outdated ==<br />
<br />
=== Error ===<br />
<br />
{{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.}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
PlayOnMac users, even if Samba and winbind are installed.<br />
<br />
=== What causes this error? ===<br />
<br />
PlayOnMac is not reading the correct path for some reason.<br />
<br />
=== Common solutions ===<br />
<br />
==== Edit PlayOnMac Bash script to properly set path ====<br />
<br />
Instructions adapted from this thread:<br />
<br />
[https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html]<br />
<br />
# Edit ''/Applications/PlayOnMac.app/Contents/MacOS/playonmac''<br />
# Change ''#!/bin/bash'' to ''#!/bin/bash --login'', save, and try to start PlayOnMac</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Troubleshooting_Common_Problems&diff=790Troubleshooting Common Problems2015-05-01T15:51:41Z<p>RoninDusette: </p>
<hr />
<div>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.<br />
<br />
When trying a possible solution for an issue, please only try '''ONE''' solution at a time, and test to see if it worked. <br />
<br />
== p11-kit: couldn't load module: ... ==<br />
<br />
=== Error ===<br />
<br />
{{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}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Mostly users of Debian, Ubuntu, Kubuntu, etc., Mint (and derivatives), 64-bit systems.<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== Install 32-bit version of p11-kit-trust.so ====<br />
<br />
<pre class='code bash'><br />
sudo apt-get install p11-kit-modules:i386<br />
</pre><br />
<br />
==== Create a symlink ====<br />
<br />
''found at http://askubuntu.com/a/384018''<br />
<br />
<pre class='code bash'><br />
sudo /usr/local/bin/getlibs -p p11-kit:i386<br />
sudo ln -s /usr/lib32/i386-linux-gnu/pkcs11/p11-kit-trust.so /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so<br />
</pre><br />
<br />
== Error in FS_Check ==<br />
<br />
=== Error ===<br />
<br />
{{Console|The following file is located on a fuse filesystem. It might prevent wine from working}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Anyone trying to run an executable file in Wine/POL that is located on an NTFS filesystem.<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== Move executable to a native Linux filesystem ====<br />
<br />
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.<br />
<br />
== Failed to use ICMP ==<br />
<br />
=== Error ===<br />
<br />
{{Console|err:winediag:IcmpCreateFile Failed to use ICMP (network ping), this requires special permissions.<br />
}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
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.<br />
<br />
=== What causes this error? ===<br />
<br />
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? ;)<br />
<br />
=== Common solutions ===<br />
<br />
==== Give rights to POL's WineBuild ====<br />
<br />
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.<br />
<br />
For instance, '''AION'''.<br />
<br />
All of POL's WineBuilds are stored in ~/.PlayOnLinux/wine/<br />
<br />
Within this folder, you have different sub-folders for architecture, and then Wine version. In the case of '''AION''':<br />
<br />
{{Console|/home/username/.PlayOnLinux/wine/linux-x86/1.7.36}}<br />
<br />
Find out which Wine version your application needs:<br />
<br />
# Open the Configuration Window<br />
# In the General tab, when your virtual drive is selected, look at the name of the version of Wine in use. <br />
<br />
Now, the command you would want to run is:<br />
<br />
'''NOTE''': ''Do NOT copy and paste these commands. They need to be modified for your particular situation.''<br />
<br />
{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine}}<br />
<br />
or<br />
<br />
{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine-preloader}}<br />
<br />
'''NOTE:''' ''I have seen both bin/wine and bin/wine-preloader shown in examples, so for posterity, I am including both.''<br />
<br />
Essentially, the syntax for this is as follows:<br />
<br />
{{Console|sudo setcap cap_net_raw+epi /home/'''username'''/.PlayOnLinux/wine/'''WineArchitecture'''/'''WineVersion'''/bin/wine}}<br />
<br />
Replace: <br />
<br />
* '''username''' with your current username<br />
<br />
* '''Wine Architecture''' with either '''linux-x86''' (32-bit virtual drive) or '''linux-amd64''' (64-bit virtual drive)<br />
<br />
* '''Wine Version''' with the '''EXACT''' name listed in the '''Wine dropdown menu''' in the '''General tab''' of the ''' Configuration Window'''<br />
<br />
== Error! Files mismatch ==<br />
<br />
=== Error ===<br />
<br />
{{Console|''someurl''<br />
<br />
<br />
Error! Files mismatch<br />
<br />
<br />
Local: ''md5resultexpected''<br />
<br />
Server: ''md5resultdownloaded''<br />
<br />
<br />
<br />
Do you want to retry?<br />
}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
This can happen to any user on any system. It is also architecture agnostic.<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== File bug report with POL ====<br />
<br />
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.).<br />
<br />
== The application you are trying to install needs administrator rights... ==<br />
<br />
=== Error ===<br />
<br />
{{Console|The application you are trying to install needs administrator rights to function correctly.}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Anyone on any distro may see this error<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== File bug report with WineHQ ====<br />
<br />
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:<br />
<br />
* [https://bugs.winehq.org/ WineHQ's Bugzilla]<br />
<br />
== League of Legends Stuck on Logo (after Champ Select) ==<br />
<br />
=== Error ===<br />
<br />
League of Legends simply stalls at the logo after the champion select dialogue.<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Anyone on any distro may see this error<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== Install needed components ====<br />
<br />
Instructions adapted from this thread:<br />
<br />
[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]<br />
<br />
# Install in POL: d3dx10, d3dx11, d3dx9 (only d3dx9, not the other d3dx9_etc) and directx9<br />
# 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"<br />
<br />
== PlayOnMac: SECUR32_initNTLMSP ntlm_auth was not found or is outdated ==<br />
<br />
=== Error ===<br />
<br />
{{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.}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
PlayOnMac users, even if Samba and winbind are installed.<br />
<br />
=== What causes this error? ===<br />
<br />
PlayOnMac is not reading the correct path for some reason.<br />
<br />
=== Common solutions ===<br />
<br />
==== Edit PlayOnMac Bash script to properly set path ====<br />
<br />
Instructions adapted from this thread:<br />
<br />
[https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html]<br />
<br />
# Edit ''/Applications/PlayOnMac.app/Contents/MacOS/playonmac''<br />
# Change ''#!/bin/bash'' to ''#!/bin/bash --login'', save, and try to start PlayOnMac</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=FAQ&diff=774FAQ2015-04-23T16:29:57Z<p>RoninDusette: /* My post was closed with a semi-automated reply? What did I break? */</p>
<hr />
<div>== PlayOnLinux and PlayOnMac ==<br />
<br />
=== How do I find out if a game will run on PlayOnLinux/PlayOnMac? ===<br />
Excellent question. Since POL/POM is a front-end for [https://winehq.org/ Wine], the first place to check, besides our [https://www.playonlinux.com/en/supported_apps.html Supported Software section], is WineHQ's [https://appdb.winehq.org/ AppDB]. There are many, many entries for a lot of different types of Windows applications, all submitted to the Wine community by users like yourself. If it is even remotely popular, and people have attempted to use it through Wine, it will likely be listed there.<br />
<br />
=== How do I move PlayOnLinux virtual drives to another disk (with more free space)? ===<br />
Read the advanced topic here:<br />
* [[How to move PlayOnLinux virtual drives to another disk|How to move PlayOnLinux virtual drives to another disk]]<br />
<br />
=== Why isn't PlayOnLinux downloading Photoshop (or whatever retail application) for me? ===<br />
PlayOnLinux/PlayOnMac does not actually provide the applications. It provides the means to install those applications. You actually have to own, say, Photoshop CS6, in order to install Photoshop CS6. POL/POM does not provide any sort of pirated software in any way. This also applies to support regarding pirated software and cracks.<br />
<br />
=== Do I have to install Wine to use PlayOnLinux? ===<br />
Yes. You will want to have a 32-bit version of Wine installed on your system, along with the dependencies it suggests. POL will want to see it, and will use it's dependencies concurrently with POL's WineBuilds. Without getting too technical, POL will need it, so it is best to install it.<br />
<br />
=== Will PlayOnLinux interfere with my current Wine or winetricks installations? ===<br />
No. PlayOnLinux/PlayOnMac keeps all of it's resources, WineBuilds, and virtual drives contained in one folder, and will never interfere with your other WINEPREFIX created by vanilla Wine and winetricks (unless, of course, you start using winetricks for POL virtual drives or try to use vanilla Wine on a POL virtual drive, or something like that.).<br />
<br />
=== The application I am trying to install needs administrator rights to function correctly ===<br />
Wine does not implement privileges, so such message does not make any sense under Wine. Either it cannot be made to work, or emulated Windows version must be changed to some version that does not implement privileges (Win9x for instance) so that the installer changes its expectations.<br />
<br />
=== How do I install Steam, and Steam only? ===<br />
<br />
If you want to only install Steam for Windows into a Virtual Drive, you will need to do a manual installation. It is very simple:<br />
<br />
# Open PlayOnLinux, download and install the WineBuild that you want from [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions].<br />
# Open the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window], click New, and create a new Virtual Drive, naming it what you want, and selecting the WineBuild that you want to use when prompted.<br />
# In the Configuration Window, select your new Virtual Drive, open the Install Components tab, and double-click '''Steam''' in that list. Steam will be installed into the Virtual Drive highlighted on the left side.<br />
# On the General Tab of the Configuration Window, select '''Make a new shortcut from this virtual drive''', and select the Steam executable when shown in the list. This will create a shortcut in the main POL window. <br />
<br />
'''NOTE:''' ''This is a manual install, and does not guarantee that the game that you install through Steam will work. If it does not work, you should check to see if there is already an installer for that game in our repository, and if not, you will need to check the [https://appdb.winehq.org AppDB at WineHQ] for your game to see if it needs any extra components or settings. As always, for manual installs, feel free to post up for help in the appropriate section of [https://www.playonlinux.com/en/forum-24-Manual_installations.html the forums].''<br />
<br />
=== How can I use the CSMT patch with POL? ===<br />
<br />
Up until recently, you would have needed to request a patched WineBuild. Now, with the help of the devs at ''wine-staging'', we have WineBuilds with the patchset from ''wine-staging'', which happen to contain the CSMT patch. You just have to go to [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions] and download the WineBuild that you want, with the ''-staging'' suffix, and then use the '''Wine tab''' in the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window] to access '''Wine Configuration'''. You will find a checkbox to enable CSMT in the '''Staging tab'''.<br />
<br />
== Website ==<br />
<br />
=== How can I post a bug report? ===<br />
* [[How to Post a Bug Report|How to Post a Bug Report]]<br />
<br />
=== How can I contribute an installer for an application? ===<br />
First, you would want to read our scripters tutorial here: [[Scripting - Chapter 1: Getting to know Bash|Scripting tutorial]]<br />
<br />
Then once you have written and tested a script, and it is working, follow the instructions here to submit it to us: [[How to Contribute a Script|How to Contribute a Script]]<br />
<br />
=== How do I request a version of Wine with a certain patch? ===<br />
* [[How to Request a Patched Version of Wine|How to Request a Patched Version of Wine]]<br />
<br />
=== Where does PlayOnLinux store it's virtual drives and cache? ===<br />
All virtual drives are created and store here:<br />
<br />
<code>~/.PlayOnLinux/wineprefix/</code><br />
<br />
The other files for Wine versions, resources, and components cache are located in '''~/.PlayOnLinux/'''<br />
<br />
=== How do I run Wine/POL as root or sudo? ===<br />
You don't. You should never, ever run Wine or POL as root or using sudo, or any other privilege escalation mechanism. <br />
<br />
* [http://wiki.winehq.org/FAQ#head-96bebfa287b4288974de0df23351f278b0d41014 WineHQ FAQ regarding root/sudo use]<br />
<br />
=== Is there a list of solutions for common problems? ===<br />
Somewhat, as issues can vary a '''LOT''' between users, systems, Wine versions, graphics cards, etc.. As a start, you should check the following locations:<br />
<br />
* [https://appdb.winehq.org/ appdb.winehq.org]<br />
* [[Troubleshooting Common Problems|Troubleshooting Common Problems]]<br />
* [https://www.playonlinux.com/en/forums.html The POL/POM forums]<br />
* Google, of course<br />
<br />
=== My post was closed with a semi-automated reply? What did I break? ===<br />
Nothing. What that means is that your post is lacking information that we need to troubleshoot, or possibly violates our terms of service. <br />
<br />
Check the following links to make sure that you didn't accidentally violate ToS, and that you are posting the information required:<br />
<br />
* https://www.playonlinux.com/en/terms.html<br />
<br />
* [[How to Post in the Forums|How to Post in the Forums]]<br />
<br />
== I want to contribute ==<br />
<br />
=== Bash; I really want to know more ===<br />
* http://www.gnu.org/software/bash/<br />
<br />
* http://linuxconfig.org/bash-scripting-tutorial<br />
<br />
* http://www.tldp.org/LDP/Bash-Beginners-Guide/html/<br />
<br />
* http://www.tldp.org/LDP/abs/html/<br />
<br />
=== Python; I really want to know more ===<br />
* https://www.python.org/<br />
<br />
* https://docs.python.org/2/tutorial/<br />
<br />
* http://www.learnpython.org/</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=FAQ&diff=773FAQ2015-04-22T06:49:44Z<p>RoninDusette: /* How can I use the CSMT patch with POL? */</p>
<hr />
<div>== PlayOnLinux and PlayOnMac ==<br />
<br />
=== How do I find out if a game will run on PlayOnLinux/PlayOnMac? ===<br />
Excellent question. Since POL/POM is a front-end for [https://winehq.org/ Wine], the first place to check, besides our [https://www.playonlinux.com/en/supported_apps.html Supported Software section], is WineHQ's [https://appdb.winehq.org/ AppDB]. There are many, many entries for a lot of different types of Windows applications, all submitted to the Wine community by users like yourself. If it is even remotely popular, and people have attempted to use it through Wine, it will likely be listed there.<br />
<br />
=== How do I move PlayOnLinux virtual drives to another disk (with more free space)? ===<br />
Read the advanced topic here:<br />
* [[How to move PlayOnLinux virtual drives to another disk|How to move PlayOnLinux virtual drives to another disk]]<br />
<br />
=== Why isn't PlayOnLinux downloading Photoshop (or whatever retail application) for me? ===<br />
PlayOnLinux/PlayOnMac does not actually provide the applications. It provides the means to install those applications. You actually have to own, say, Photoshop CS6, in order to install Photoshop CS6. POL/POM does not provide any sort of pirated software in any way. This also applies to support regarding pirated software and cracks.<br />
<br />
=== Do I have to install Wine to use PlayOnLinux? ===<br />
Yes. You will want to have a 32-bit version of Wine installed on your system, along with the dependencies it suggests. POL will want to see it, and will use it's dependencies concurrently with POL's WineBuilds. Without getting too technical, POL will need it, so it is best to install it.<br />
<br />
=== Will PlayOnLinux interfere with my current Wine or winetricks installations? ===<br />
No. PlayOnLinux/PlayOnMac keeps all of it's resources, WineBuilds, and virtual drives contained in one folder, and will never interfere with your other WINEPREFIX created by vanilla Wine and winetricks (unless, of course, you start using winetricks for POL virtual drives or try to use vanilla Wine on a POL virtual drive, or something like that.).<br />
<br />
=== The application I am trying to install needs administrator rights to function correctly ===<br />
Wine does not implement privileges, so such message does not make any sense under Wine. Either it cannot be made to work, or emulated Windows version must be changed to some version that does not implement privileges (Win9x for instance) so that the installer changes its expectations.<br />
<br />
=== How do I install Steam, and Steam only? ===<br />
<br />
If you want to only install Steam for Windows into a Virtual Drive, you will need to do a manual installation. It is very simple:<br />
<br />
# Open PlayOnLinux, download and install the WineBuild that you want from [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions].<br />
# Open the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window], click New, and create a new Virtual Drive, naming it what you want, and selecting the WineBuild that you want to use when prompted.<br />
# In the Configuration Window, select your new Virtual Drive, open the Install Components tab, and double-click '''Steam''' in that list. Steam will be installed into the Virtual Drive highlighted on the left side.<br />
# On the General Tab of the Configuration Window, select '''Make a new shortcut from this virtual drive''', and select the Steam executable when shown in the list. This will create a shortcut in the main POL window. <br />
<br />
'''NOTE:''' ''This is a manual install, and does not guarantee that the game that you install through Steam will work. If it does not work, you should check to see if there is already an installer for that game in our repository, and if not, you will need to check the [https://appdb.winehq.org AppDB at WineHQ] for your game to see if it needs any extra components or settings. As always, for manual installs, feel free to post up for help in the appropriate section of [https://www.playonlinux.com/en/forum-24-Manual_installations.html the forums].''<br />
<br />
=== How can I use the CSMT patch with POL? ===<br />
<br />
Up until recently, you would have needed to request a patched WineBuild. Now, with the help of the devs at ''wine-staging'', we have WineBuilds with the patchset from ''wine-staging'', which happen to contain the CSMT patch. You just have to go to [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions] and download the WineBuild that you want, with the ''-staging'' suffix, and then use the '''Wine tab''' in the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window] to access '''Wine Configuration'''. You will find a checkbox to enable CSMT in the '''Staging tab'''.<br />
<br />
== Website ==<br />
<br />
=== How can I post a bug report? ===<br />
* [[How to Post a Bug Report|How to Post a Bug Report]]<br />
<br />
=== How can I contribute an installer for an application? ===<br />
First, you would want to read our scripters tutorial here: [[Scripting - Chapter 1: Getting to know Bash|Scripting tutorial]]<br />
<br />
Then once you have written and tested a script, and it is working, follow the instructions here to submit it to us: [[How to Contribute a Script|How to Contribute a Script]]<br />
<br />
=== How do I request a version of Wine with a certain patch? ===<br />
* [[How to Request a Patched Version of Wine|How to Request a Patched Version of Wine]]<br />
<br />
=== Where does PlayOnLinux store it's virtual drives and cache? ===<br />
All virtual drives are created and store here:<br />
<br />
<code>~/.PlayOnLinux/wineprefix/</code><br />
<br />
The other files for Wine versions, resources, and components cache are located in '''~/.PlayOnLinux/'''<br />
<br />
=== How do I run Wine/POL as root or sudo? ===<br />
You don't. You should never, ever run Wine or POL as root or using sudo, or any other privilege escalation mechanism. <br />
<br />
* [http://wiki.winehq.org/FAQ#head-96bebfa287b4288974de0df23351f278b0d41014 WineHQ FAQ regarding root/sudo use]<br />
<br />
=== Is there a list of solutions for common problems? ===<br />
Somewhat, as issues can vary a '''LOT''' between users, systems, Wine versions, graphics cards, etc.. As a start, you should check the following locations:<br />
<br />
* [https://appdb.winehq.org/ appdb.winehq.org]<br />
* [[Troubleshooting Common Problems|Troubleshooting Common Problems]]<br />
* [https://www.playonlinux.com/en/forums.html The POL/POM forums]<br />
* Google, of course<br />
<br />
=== My post was closed with a semi-automated reply? What did I break? ===<br />
Nothing. What that means is that your post is lacking information that we need to troubleshoot, or possibly violates our terms of service. <br />
<br />
Check the following links to make sure that you didn't accidentally violate ToS, and t haatt you areIinformation required:<br />
<br />
* https://www.playonlinux.com/en/terms.html<br />
<br />
* [[How to Post in the Forums|How to Post in the Forums]]<br />
<br />
== I want to contribute ==<br />
<br />
=== Bash; I really want to know more ===<br />
* http://www.gnu.org/software/bash/<br />
<br />
* http://linuxconfig.org/bash-scripting-tutorial<br />
<br />
* http://www.tldp.org/LDP/Bash-Beginners-Guide/html/<br />
<br />
* http://www.tldp.org/LDP/abs/html/<br />
<br />
=== Python; I really want to know more ===<br />
* https://www.python.org/<br />
<br />
* https://docs.python.org/2/tutorial/<br />
<br />
* http://www.learnpython.org/</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=FAQ&diff=772FAQ2015-04-22T06:48:30Z<p>RoninDusette: /* PlayOnLinux and PlayOnMac */</p>
<hr />
<div>== PlayOnLinux and PlayOnMac ==<br />
<br />
=== How do I find out if a game will run on PlayOnLinux/PlayOnMac? ===<br />
Excellent question. Since POL/POM is a front-end for [https://winehq.org/ Wine], the first place to check, besides our [https://www.playonlinux.com/en/supported_apps.html Supported Software section], is WineHQ's [https://appdb.winehq.org/ AppDB]. There are many, many entries for a lot of different types of Windows applications, all submitted to the Wine community by users like yourself. If it is even remotely popular, and people have attempted to use it through Wine, it will likely be listed there.<br />
<br />
=== How do I move PlayOnLinux virtual drives to another disk (with more free space)? ===<br />
Read the advanced topic here:<br />
* [[How to move PlayOnLinux virtual drives to another disk|How to move PlayOnLinux virtual drives to another disk]]<br />
<br />
=== Why isn't PlayOnLinux downloading Photoshop (or whatever retail application) for me? ===<br />
PlayOnLinux/PlayOnMac does not actually provide the applications. It provides the means to install those applications. You actually have to own, say, Photoshop CS6, in order to install Photoshop CS6. POL/POM does not provide any sort of pirated software in any way. This also applies to support regarding pirated software and cracks.<br />
<br />
=== Do I have to install Wine to use PlayOnLinux? ===<br />
Yes. You will want to have a 32-bit version of Wine installed on your system, along with the dependencies it suggests. POL will want to see it, and will use it's dependencies concurrently with POL's WineBuilds. Without getting too technical, POL will need it, so it is best to install it.<br />
<br />
=== Will PlayOnLinux interfere with my current Wine or winetricks installations? ===<br />
No. PlayOnLinux/PlayOnMac keeps all of it's resources, WineBuilds, and virtual drives contained in one folder, and will never interfere with your other WINEPREFIX created by vanilla Wine and winetricks (unless, of course, you start using winetricks for POL virtual drives or try to use vanilla Wine on a POL virtual drive, or something like that.).<br />
<br />
=== The application I am trying to install needs administrator rights to function correctly ===<br />
Wine does not implement privileges, so such message does not make any sense under Wine. Either it cannot be made to work, or emulated Windows version must be changed to some version that does not implement privileges (Win9x for instance) so that the installer changes its expectations.<br />
<br />
=== How do I install Steam, and Steam only? ===<br />
<br />
If you want to only install Steam for Windows into a Virtual Drive, you will need to do a manual installation. It is very simple:<br />
<br />
# Open PlayOnLinux, download and install the WineBuild that you want from [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions].<br />
# Open the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window], click New, and create a new Virtual Drive, naming it what you want, and selecting the WineBuild that you want to use when prompted.<br />
# In the Configuration Window, select your new Virtual Drive, open the Install Components tab, and double-click '''Steam''' in that list. Steam will be installed into the Virtual Drive highlighted on the left side.<br />
# On the General Tab of the Configuration Window, select '''Make a new shortcut from this virtual drive''', and select the Steam executable when shown in the list. This will create a shortcut in the main POL window. <br />
<br />
'''NOTE:''' ''This is a manual install, and does not guarantee that the game that you install through Steam will work. If it does not work, you should check to see if there is already an installer for that game in our repository, and if not, you will need to check the [https://appdb.winehq.org AppDB at WineHQ] for your game to see if it needs any extra components or settings. As always, for manual installs, feel free to post up for help in the appropriate section of [https://www.playonlinux.com/en/forum-24-Manual_installations.html the forums].''<br />
<br />
=== How can I use the CSMT patch with POL? ===<br />
<br />
Up until recently, you would have needed to request a patched WineBuild. Now, with the help of the devs at ''wine-staging'', we have WineBuilds with the patchset from ''wine-staging'', which happen to contain the CSMT patch. You just have to go to [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions] and download the version of Wine that you want with the ''-staging'' suffix, and then use the '''Wine tab''' in the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window] to access '''Wine Configuration'''. You will find a checkbox to enable CSMT in the '''Staging tab'''.<br />
<br />
== Website ==<br />
<br />
=== How can I post a bug report? ===<br />
* [[How to Post a Bug Report|How to Post a Bug Report]]<br />
<br />
=== How can I contribute an installer for an application? ===<br />
First, you would want to read our scripters tutorial here: [[Scripting - Chapter 1: Getting to know Bash|Scripting tutorial]]<br />
<br />
Then once you have written and tested a script, and it is working, follow the instructions here to submit it to us: [[How to Contribute a Script|How to Contribute a Script]]<br />
<br />
=== How do I request a version of Wine with a certain patch? ===<br />
* [[How to Request a Patched Version of Wine|How to Request a Patched Version of Wine]]<br />
<br />
=== Where does PlayOnLinux store it's virtual drives and cache? ===<br />
All virtual drives are created and store here:<br />
<br />
<code>~/.PlayOnLinux/wineprefix/</code><br />
<br />
The other files for Wine versions, resources, and components cache are located in '''~/.PlayOnLinux/'''<br />
<br />
=== How do I run Wine/POL as root or sudo? ===<br />
You don't. You should never, ever run Wine or POL as root or using sudo, or any other privilege escalation mechanism. <br />
<br />
* [http://wiki.winehq.org/FAQ#head-96bebfa287b4288974de0df23351f278b0d41014 WineHQ FAQ regarding root/sudo use]<br />
<br />
=== Is there a list of solutions for common problems? ===<br />
Somewhat, as issues can vary a '''LOT''' between users, systems, Wine versions, graphics cards, etc.. As a start, you should check the following locations:<br />
<br />
* [https://appdb.winehq.org/ appdb.winehq.org]<br />
* [[Troubleshooting Common Problems|Troubleshooting Common Problems]]<br />
* [https://www.playonlinux.com/en/forums.html The POL/POM forums]<br />
* Google, of course<br />
<br />
=== My post was closed with a semi-automated reply? What did I break? ===<br />
Nothing. What that means is that your post is lacking information that we need to troubleshoot, or possibly violates our terms of service. <br />
<br />
Check the following links to make sure that you didn't accidentally violate ToS, and t haatt you areIinformation required:<br />
<br />
* https://www.playonlinux.com/en/terms.html<br />
<br />
* [[How to Post in the Forums|How to Post in the Forums]]<br />
<br />
== I want to contribute ==<br />
<br />
=== Bash; I really want to know more ===<br />
* http://www.gnu.org/software/bash/<br />
<br />
* http://linuxconfig.org/bash-scripting-tutorial<br />
<br />
* http://www.tldp.org/LDP/Bash-Beginners-Guide/html/<br />
<br />
* http://www.tldp.org/LDP/abs/html/<br />
<br />
=== Python; I really want to know more ===<br />
* https://www.python.org/<br />
<br />
* https://docs.python.org/2/tutorial/<br />
<br />
* http://www.learnpython.org/</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Graphics_Card_Drivers&diff=771Graphics Card Drivers2015-04-18T18:42:12Z<p>RoninDusette: /* Fedora */</p>
<hr />
<div>In this section, we will try to cover the basics of getting the most out of your AMD, Nvidia, or Intel graphics card on your Linux system, specifically when using Wine/PlayOnLinux. This can get pretty lengthy, so expect this article to get exponentially bigger as time goes on.<br />
<br />
{{Info|This list is going to take a while to get full, so please be patient as we populate everything.}}<br />
<br />
For ease of use, we will break these down into different sections for the graphics card manufacturer, and then distro's within those categories. <br />
<br />
== NVIDIA ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
Most of the time, the easiest way is using the "Additional Drivers" dialogue. That does not always work though, and it sometimes will offer less-than-ideal versions of drivers for your NVIDIA card. If your card is supported by the current NVIDIA driver, the following command should pull in the required libraries:<br />
<br />
{{Console|sudo apt-get install nvidia-current}}<br />
<br />
You can also install other series of drivers (313.x, 319.x, 331.x, etc.) by appending the version name to them:<br />
<br />
'''Examples:'''<br />
<br />
{{Console|sudo apt-get install nvidia-331}}<br />
<br />
For the '''32-bit''' libraries, as long as ''libgl1-mesa-glx:i386'' and ''multiarch-support'' are installed, it should install them automatically. If, after you install them from the Ubuntu repositories, it does not show up, try to install those packages mentioned previously:<br />
<br />
{{Console|<br />
sudo apt-get install multiarch-support<br />
<br />
sudo apt-get install libgl1-mesa-glx:i386<br />
}}<br />
<br />
The manual installation is a bit more involved, but it is preferred by a lot of users.<br />
<br />
''Will add more later''<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary NVIDIA drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/NvidiaGraphicsDrivers<br />
<br />
==== Fedora ====<br />
<br />
* http://rpmfusion.org/Howto/nVidia<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/NVIDIA<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVidia/nvidia-drivers<br />
<br />
=== Optimus ===<br />
<br />
NVIDIA Optimus technology is a feature in laptops with newer Intel CPU's with integrated GPUs and discrete NVIDIA graphics cards that allows switching between graphics processors on-the-fly, to optimize the performance when needed, and maximizing battery life when not needing the discrete graphics card. More information on Optimus can be found here:<br />
<br />
* http://www.nvidia.com/object/optimus_technology.html<br />
<br />
==== Most distributions ====<br />
<br />
The current working solution is maintained by the '''Bumblebee Project'''. '''PRIME''' is not recommended, as it utilizes the open-source NVIDIA driver (''nouveau''), and will not give the performance desired for most games. The project's website has detailed documentation for most major distributions, so it is recommended to go by that:<br />
<br />
* http://bumblebee-project.org/<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVIDIA_Driver_with_Optimus_Laptops<br />
<br />
=== Open-Source Drivers ===<br />
<br />
Unfortunately, the open-source ''nouveau'' drivers are not really up-to-par on performance yet for gaming. Things are starting to look up, but there are a lot of caveats to running the open-source NVIDIA drivers. More information can be found here:<br />
<br />
* http://nouveau.freedesktop.org/wiki/<br />
<br />
* http://www.phoronix.com/scan.php?page=news_topic&q=Nouveau<br />
<br />
== AMD ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
As of now, the official Ubuntu docs are VERY detailed in the installation of the open-source and proprietary graphics drivers. It is recommended to use their documentation for your AMD card on the Ubuntu distros (Mint should be very similar, if not exactly the same). You can find that information here:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary AMD/ATI drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/ATIProprietary<br />
<br />
==== Fedora ====<br />
<br />
* [https://fedoraproject.org/wiki/Fglrx https://fedoraproject.org/wiki/Fglrx]<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Fglrx<br />
<br />
=== Open-Source Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
We refer you to the same link:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
The installation of the open source ''radeon'' driver is straightforward, and is likely installed on your system by default. More information on the Debian ''radeon'' driver can be found here:<br />
<br />
* https://wiki.debian.org/AtiHowTo<br />
<br />
==== Fedora ====<br />
<br />
The open-source ''radeon'' driver should already be included in your system by default. If you are on a 64-bit version of Fedora, you would only need to install the 32-bit libraries for your graphics card from the Fedora repo and it should work fine with PlayOnLinux.<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Radeon<br />
<br />
== Intel ==<br />
<br />
The Intel drivers are developed by the open-source community, so they are by far the easiest to install, as they pretty much will always come with your distro by default. More information on the Intel open-source drivers can be found here:<br />
<br />
* https://01.org/linuxgraphics/<br />
<br />
For the most part, this will cover how to make sure that you have the most up-to-date graphics stack for your Intel chipset. This applies exclusively to pure Intel graphics only. If you have, say, a mixed graphics card environment, like a laptop that has an Intel iGPU and a discrete NVIDIA card, please refer to the '''NVIDIA Optimus''' section<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
If you are already running a '''32-bit''' version of one of these systems, you should have everything that you need installed correctly by default. <br />
<br />
In the case of '''64-bit''' systems, you already have the 64-bit libraries for your graphics hardware. A package called '''multiarch-support''' should pull in the '''32-bit''' libraries, as well as a bunch of others.<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install multiarch-support<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
==== Debian ====<br />
<br />
The drivers should already be installed, but if it is not working with OpenGL or you get complaints about the 32-bit graphics libraries being missing, you can should try to run:<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install ia32-libs<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
If you are still having problems, consult the Debian docs here:<br />
<br />
* https://wiki.debian.org/Multiarch/HOWTO<br />
<br />
==== Fedora ====<br />
<br />
The open-source Intel driver should already be included in your system by default. If you are on a 64-bit version of Fedora, you would only need to install the 32-bit libraries for your graphics card from the Fedora repo and it should work fine with PlayOnLinux.<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/Intel_graphics<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Intel</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Graphics_Card_Drivers&diff=770Graphics Card Drivers2015-04-18T18:41:40Z<p>RoninDusette: /* Fedora */</p>
<hr />
<div>In this section, we will try to cover the basics of getting the most out of your AMD, Nvidia, or Intel graphics card on your Linux system, specifically when using Wine/PlayOnLinux. This can get pretty lengthy, so expect this article to get exponentially bigger as time goes on.<br />
<br />
{{Info|This list is going to take a while to get full, so please be patient as we populate everything.}}<br />
<br />
For ease of use, we will break these down into different sections for the graphics card manufacturer, and then distro's within those categories. <br />
<br />
== NVIDIA ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
Most of the time, the easiest way is using the "Additional Drivers" dialogue. That does not always work though, and it sometimes will offer less-than-ideal versions of drivers for your NVIDIA card. If your card is supported by the current NVIDIA driver, the following command should pull in the required libraries:<br />
<br />
{{Console|sudo apt-get install nvidia-current}}<br />
<br />
You can also install other series of drivers (313.x, 319.x, 331.x, etc.) by appending the version name to them:<br />
<br />
'''Examples:'''<br />
<br />
{{Console|sudo apt-get install nvidia-331}}<br />
<br />
For the '''32-bit''' libraries, as long as ''libgl1-mesa-glx:i386'' and ''multiarch-support'' are installed, it should install them automatically. If, after you install them from the Ubuntu repositories, it does not show up, try to install those packages mentioned previously:<br />
<br />
{{Console|<br />
sudo apt-get install multiarch-support<br />
<br />
sudo apt-get install libgl1-mesa-glx:i386<br />
}}<br />
<br />
The manual installation is a bit more involved, but it is preferred by a lot of users.<br />
<br />
''Will add more later''<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary NVIDIA drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/NvidiaGraphicsDrivers<br />
<br />
==== Fedora ====<br />
<br />
* http://rpmfusion.org/Howto/nVidia<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/NVIDIA<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVidia/nvidia-drivers<br />
<br />
=== Optimus ===<br />
<br />
NVIDIA Optimus technology is a feature in laptops with newer Intel CPU's with integrated GPUs and discrete NVIDIA graphics cards that allows switching between graphics processors on-the-fly, to optimize the performance when needed, and maximizing battery life when not needing the discrete graphics card. More information on Optimus can be found here:<br />
<br />
* http://www.nvidia.com/object/optimus_technology.html<br />
<br />
==== Most distributions ====<br />
<br />
The current working solution is maintained by the '''Bumblebee Project'''. '''PRIME''' is not recommended, as it utilizes the open-source NVIDIA driver (''nouveau''), and will not give the performance desired for most games. The project's website has detailed documentation for most major distributions, so it is recommended to go by that:<br />
<br />
* http://bumblebee-project.org/<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVIDIA_Driver_with_Optimus_Laptops<br />
<br />
=== Open-Source Drivers ===<br />
<br />
Unfortunately, the open-source ''nouveau'' drivers are not really up-to-par on performance yet for gaming. Things are starting to look up, but there are a lot of caveats to running the open-source NVIDIA drivers. More information can be found here:<br />
<br />
* http://nouveau.freedesktop.org/wiki/<br />
<br />
* http://www.phoronix.com/scan.php?page=news_topic&q=Nouveau<br />
<br />
== AMD ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
As of now, the official Ubuntu docs are VERY detailed in the installation of the open-source and proprietary graphics drivers. It is recommended to use their documentation for your AMD card on the Ubuntu distros (Mint should be very similar, if not exactly the same). You can find that information here:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary AMD/ATI drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/ATIProprietary<br />
<br />
==== Fedora ====<br />
<br />
* [https://fedoraproject.org/wiki/Fglrx https://fedoraproject.org/wiki/Fglrx]<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Fglrx<br />
<br />
=== Open-Source Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
We refer you to the same link:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
The installation of the open source ''radeon'' driver is straightforward, and is likely installed on your system by default. More information on the Debian ''radeon'' driver can be found here:<br />
<br />
* https://wiki.debian.org/AtiHowTo<br />
<br />
==== Fedora ====<br />
<br />
The open-source ''radeon'' driver should already be included in your system by default. If you are on a 64-bit version of Fedora, you would only need to install the 32-bit libraries for your graphics card from the Fedora repo and it should work fine with PlayOnLinux.<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Radeon<br />
<br />
== Intel ==<br />
<br />
The Intel drivers are developed by the open-source community, so they are by far the easiest to install, as they pretty much will always come with your distro by default. More information on the Intel open-source drivers can be found here:<br />
<br />
* https://01.org/linuxgraphics/<br />
<br />
For the most part, this will cover how to make sure that you have the most up-to-date graphics stack for your Intel chipset. This applies exclusively to pure Intel graphics only. If you have, say, a mixed graphics card environment, like a laptop that has an Intel iGPU and a discrete NVIDIA card, please refer to the '''NVIDIA Optimus''' section<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
If you are already running a '''32-bit''' version of one of these systems, you should have everything that you need installed correctly by default. <br />
<br />
In the case of '''64-bit''' systems, you already have the 64-bit libraries for your graphics hardware. A package called '''multiarch-support''' should pull in the '''32-bit''' libraries, as well as a bunch of others.<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install multiarch-support<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
==== Debian ====<br />
<br />
The drivers should already be installed, but if it is not working with OpenGL or you get complaints about the 32-bit graphics libraries being missing, you can should try to run:<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install ia32-libs<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
If you are still having problems, consult the Debian docs here:<br />
<br />
* https://wiki.debian.org/Multiarch/HOWTO<br />
<br />
==== Fedora ====<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/Intel_graphics<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Intel</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Graphics_Card_Drivers&diff=769Graphics Card Drivers2015-04-18T18:36:57Z<p>RoninDusette: /* Fedora */</p>
<hr />
<div>In this section, we will try to cover the basics of getting the most out of your AMD, Nvidia, or Intel graphics card on your Linux system, specifically when using Wine/PlayOnLinux. This can get pretty lengthy, so expect this article to get exponentially bigger as time goes on.<br />
<br />
{{Info|This list is going to take a while to get full, so please be patient as we populate everything.}}<br />
<br />
For ease of use, we will break these down into different sections for the graphics card manufacturer, and then distro's within those categories. <br />
<br />
== NVIDIA ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
Most of the time, the easiest way is using the "Additional Drivers" dialogue. That does not always work though, and it sometimes will offer less-than-ideal versions of drivers for your NVIDIA card. If your card is supported by the current NVIDIA driver, the following command should pull in the required libraries:<br />
<br />
{{Console|sudo apt-get install nvidia-current}}<br />
<br />
You can also install other series of drivers (313.x, 319.x, 331.x, etc.) by appending the version name to them:<br />
<br />
'''Examples:'''<br />
<br />
{{Console|sudo apt-get install nvidia-331}}<br />
<br />
For the '''32-bit''' libraries, as long as ''libgl1-mesa-glx:i386'' and ''multiarch-support'' are installed, it should install them automatically. If, after you install them from the Ubuntu repositories, it does not show up, try to install those packages mentioned previously:<br />
<br />
{{Console|<br />
sudo apt-get install multiarch-support<br />
<br />
sudo apt-get install libgl1-mesa-glx:i386<br />
}}<br />
<br />
The manual installation is a bit more involved, but it is preferred by a lot of users.<br />
<br />
''Will add more later''<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary NVIDIA drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/NvidiaGraphicsDrivers<br />
<br />
==== Fedora ====<br />
<br />
* http://rpmfusion.org/Howto/nVidia<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/NVIDIA<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVidia/nvidia-drivers<br />
<br />
=== Optimus ===<br />
<br />
NVIDIA Optimus technology is a feature in laptops with newer Intel CPU's with integrated GPUs and discrete NVIDIA graphics cards that allows switching between graphics processors on-the-fly, to optimize the performance when needed, and maximizing battery life when not needing the discrete graphics card. More information on Optimus can be found here:<br />
<br />
* http://www.nvidia.com/object/optimus_technology.html<br />
<br />
==== Most distributions ====<br />
<br />
The current working solution is maintained by the '''Bumblebee Project'''. '''PRIME''' is not recommended, as it utilizes the open-source NVIDIA driver (''nouveau''), and will not give the performance desired for most games. The project's website has detailed documentation for most major distributions, so it is recommended to go by that:<br />
<br />
* http://bumblebee-project.org/<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVIDIA_Driver_with_Optimus_Laptops<br />
<br />
=== Open-Source Drivers ===<br />
<br />
Unfortunately, the open-source ''nouveau'' drivers are not really up-to-par on performance yet for gaming. Things are starting to look up, but there are a lot of caveats to running the open-source NVIDIA drivers. More information can be found here:<br />
<br />
* http://nouveau.freedesktop.org/wiki/<br />
<br />
* http://www.phoronix.com/scan.php?page=news_topic&q=Nouveau<br />
<br />
== AMD ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
As of now, the official Ubuntu docs are VERY detailed in the installation of the open-source and proprietary graphics drivers. It is recommended to use their documentation for your AMD card on the Ubuntu distros (Mint should be very similar, if not exactly the same). You can find that information here:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary AMD/ATI drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/ATIProprietary<br />
<br />
==== Fedora ====<br />
<br />
* [https://fedoraproject.org/wiki/Fglrx https://fedoraproject.org/wiki/Fglrx]<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Fglrx<br />
<br />
=== Open-Source Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
We refer you to the same link:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
The installation of the open source ''radeon'' driver is straightforward, and is likely installed on your system by default. More information on the Debian ''radeon'' driver can be found here:<br />
<br />
* https://wiki.debian.org/AtiHowTo<br />
<br />
==== Fedora ====<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Radeon<br />
<br />
== Intel ==<br />
<br />
The Intel drivers are developed by the open-source community, so they are by far the easiest to install, as they pretty much will always come with your distro by default. More information on the Intel open-source drivers can be found here:<br />
<br />
* https://01.org/linuxgraphics/<br />
<br />
For the most part, this will cover how to make sure that you have the most up-to-date graphics stack for your Intel chipset. This applies exclusively to pure Intel graphics only. If you have, say, a mixed graphics card environment, like a laptop that has an Intel iGPU and a discrete NVIDIA card, please refer to the '''NVIDIA Optimus''' section<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
If you are already running a '''32-bit''' version of one of these systems, you should have everything that you need installed correctly by default. <br />
<br />
In the case of '''64-bit''' systems, you already have the 64-bit libraries for your graphics hardware. A package called '''multiarch-support''' should pull in the '''32-bit''' libraries, as well as a bunch of others.<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install multiarch-support<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
==== Debian ====<br />
<br />
The drivers should already be installed, but if it is not working with OpenGL or you get complaints about the 32-bit graphics libraries being missing, you can should try to run:<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install ia32-libs<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
If you are still having problems, consult the Debian docs here:<br />
<br />
* https://wiki.debian.org/Multiarch/HOWTO<br />
<br />
==== Fedora ====<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/Intel_graphics<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Intel</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Graphics_Card_Drivers&diff=768Graphics Card Drivers2015-04-18T18:36:32Z<p>RoninDusette: /* Fedora */</p>
<hr />
<div>In this section, we will try to cover the basics of getting the most out of your AMD, Nvidia, or Intel graphics card on your Linux system, specifically when using Wine/PlayOnLinux. This can get pretty lengthy, so expect this article to get exponentially bigger as time goes on.<br />
<br />
{{Info|This list is going to take a while to get full, so please be patient as we populate everything.}}<br />
<br />
For ease of use, we will break these down into different sections for the graphics card manufacturer, and then distro's within those categories. <br />
<br />
== NVIDIA ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
Most of the time, the easiest way is using the "Additional Drivers" dialogue. That does not always work though, and it sometimes will offer less-than-ideal versions of drivers for your NVIDIA card. If your card is supported by the current NVIDIA driver, the following command should pull in the required libraries:<br />
<br />
{{Console|sudo apt-get install nvidia-current}}<br />
<br />
You can also install other series of drivers (313.x, 319.x, 331.x, etc.) by appending the version name to them:<br />
<br />
'''Examples:'''<br />
<br />
{{Console|sudo apt-get install nvidia-331}}<br />
<br />
For the '''32-bit''' libraries, as long as ''libgl1-mesa-glx:i386'' and ''multiarch-support'' are installed, it should install them automatically. If, after you install them from the Ubuntu repositories, it does not show up, try to install those packages mentioned previously:<br />
<br />
{{Console|<br />
sudo apt-get install multiarch-support<br />
<br />
sudo apt-get install libgl1-mesa-glx:i386<br />
}}<br />
<br />
The manual installation is a bit more involved, but it is preferred by a lot of users.<br />
<br />
''Will add more later''<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary NVIDIA drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/NvidiaGraphicsDrivers<br />
<br />
==== Fedora ====<br />
<br />
* http://rpmfusion.org/Howto/nVidia<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/NVIDIA<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVidia/nvidia-drivers<br />
<br />
=== Optimus ===<br />
<br />
NVIDIA Optimus technology is a feature in laptops with newer Intel CPU's with integrated GPUs and discrete NVIDIA graphics cards that allows switching between graphics processors on-the-fly, to optimize the performance when needed, and maximizing battery life when not needing the discrete graphics card. More information on Optimus can be found here:<br />
<br />
* http://www.nvidia.com/object/optimus_technology.html<br />
<br />
==== Most distributions ====<br />
<br />
The current working solution is maintained by the '''Bumblebee Project'''. '''PRIME''' is not recommended, as it utilizes the open-source NVIDIA driver (''nouveau''), and will not give the performance desired for most games. The project's website has detailed documentation for most major distributions, so it is recommended to go by that:<br />
<br />
* http://bumblebee-project.org/<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVIDIA_Driver_with_Optimus_Laptops<br />
<br />
=== Open-Source Drivers ===<br />
<br />
Unfortunately, the open-source ''nouveau'' drivers are not really up-to-par on performance yet for gaming. Things are starting to look up, but there are a lot of caveats to running the open-source NVIDIA drivers. More information can be found here:<br />
<br />
* http://nouveau.freedesktop.org/wiki/<br />
<br />
* http://www.phoronix.com/scan.php?page=news_topic&q=Nouveau<br />
<br />
== AMD ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
As of now, the official Ubuntu docs are VERY detailed in the installation of the open-source and proprietary graphics drivers. It is recommended to use their documentation for your AMD card on the Ubuntu distros (Mint should be very similar, if not exactly the same). You can find that information here:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary AMD/ATI drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/ATIProprietary<br />
<br />
==== Fedora ====<br />
<br />
* [https://fedoraproject.org/wiki/Fglrx https://fedoraproject.org/wiki/Fglrx]<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Fglrx<br />
<br />
=== Open-Source Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
We refer you to the same link:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
The installation of the open source ''radeon'' driver is straightforward, and is likely installed on your system by default. More information on the Debian ''radeon'' driver can be found here:<br />
<br />
* https://wiki.debian.org/AtiHowTo<br />
<br />
==== Fedora ====<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Radeon<br />
<br />
== Intel ==<br />
<br />
The Intel drivers are developed by the open-source community, so they are by far the easiest to install, as they pretty much will always come with your distro by default. More information on the Intel open-source drivers can be found here:<br />
<br />
* https://01.org/linuxgraphics/<br />
<br />
For the most part, this will cover how to make sure that you have the most up-to-date graphics stack for your Intel chipset. This applies exclusively to pure Intel graphics only. If you have, say, a mixed graphics card environment, like a laptop that has an Intel iGPU and a discrete NVIDIA card, please refer to the '''NVIDIA Optimus''' section<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
If you are already running a '''32-bit''' version of one of these systems, you should have everything that you need installed correctly by default. <br />
<br />
In the case of '''64-bit''' systems, you already have the 64-bit libraries for your graphics hardware. A package called '''multiarch-support''' should pull in the '''32-bit''' libraries, as well as a bunch of others.<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install multiarch-support<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
==== Debian ====<br />
<br />
The drivers should already be installed, but if it is not working with OpenGL or you get complaints about the 32-bit graphics libraries being missing, you can should try to run:<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install ia32-libs<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
If you are still having problems, consult the Debian docs here:<br />
<br />
* https://wiki.debian.org/Multiarch/HOWTO<br />
<br />
==== Fedora ====<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/Intel_graphics<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Intel</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Graphics_Card_Drivers&diff=767Graphics Card Drivers2015-04-18T18:36:13Z<p>RoninDusette: /* Fedora */</p>
<hr />
<div>In this section, we will try to cover the basics of getting the most out of your AMD, Nvidia, or Intel graphics card on your Linux system, specifically when using Wine/PlayOnLinux. This can get pretty lengthy, so expect this article to get exponentially bigger as time goes on.<br />
<br />
{{Info|This list is going to take a while to get full, so please be patient as we populate everything.}}<br />
<br />
For ease of use, we will break these down into different sections for the graphics card manufacturer, and then distro's within those categories. <br />
<br />
== NVIDIA ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
Most of the time, the easiest way is using the "Additional Drivers" dialogue. That does not always work though, and it sometimes will offer less-than-ideal versions of drivers for your NVIDIA card. If your card is supported by the current NVIDIA driver, the following command should pull in the required libraries:<br />
<br />
{{Console|sudo apt-get install nvidia-current}}<br />
<br />
You can also install other series of drivers (313.x, 319.x, 331.x, etc.) by appending the version name to them:<br />
<br />
'''Examples:'''<br />
<br />
{{Console|sudo apt-get install nvidia-331}}<br />
<br />
For the '''32-bit''' libraries, as long as ''libgl1-mesa-glx:i386'' and ''multiarch-support'' are installed, it should install them automatically. If, after you install them from the Ubuntu repositories, it does not show up, try to install those packages mentioned previously:<br />
<br />
{{Console|<br />
sudo apt-get install multiarch-support<br />
<br />
sudo apt-get install libgl1-mesa-glx:i386<br />
}}<br />
<br />
The manual installation is a bit more involved, but it is preferred by a lot of users.<br />
<br />
''Will add more later''<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary NVIDIA drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/NvidiaGraphicsDrivers<br />
<br />
==== Fedora ====<br />
* http://rpmfusion.org/Howto/nVidia<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/NVIDIA<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVidia/nvidia-drivers<br />
<br />
=== Optimus ===<br />
<br />
NVIDIA Optimus technology is a feature in laptops with newer Intel CPU's with integrated GPUs and discrete NVIDIA graphics cards that allows switching between graphics processors on-the-fly, to optimize the performance when needed, and maximizing battery life when not needing the discrete graphics card. More information on Optimus can be found here:<br />
<br />
* http://www.nvidia.com/object/optimus_technology.html<br />
<br />
==== Most distributions ====<br />
<br />
The current working solution is maintained by the '''Bumblebee Project'''. '''PRIME''' is not recommended, as it utilizes the open-source NVIDIA driver (''nouveau''), and will not give the performance desired for most games. The project's website has detailed documentation for most major distributions, so it is recommended to go by that:<br />
<br />
* http://bumblebee-project.org/<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVIDIA_Driver_with_Optimus_Laptops<br />
<br />
=== Open-Source Drivers ===<br />
<br />
Unfortunately, the open-source ''nouveau'' drivers are not really up-to-par on performance yet for gaming. Things are starting to look up, but there are a lot of caveats to running the open-source NVIDIA drivers. More information can be found here:<br />
<br />
* http://nouveau.freedesktop.org/wiki/<br />
<br />
* http://www.phoronix.com/scan.php?page=news_topic&q=Nouveau<br />
<br />
== AMD ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
As of now, the official Ubuntu docs are VERY detailed in the installation of the open-source and proprietary graphics drivers. It is recommended to use their documentation for your AMD card on the Ubuntu distros (Mint should be very similar, if not exactly the same). You can find that information here:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary AMD/ATI drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/ATIProprietary<br />
<br />
==== Fedora ====<br />
<br />
* [https://fedoraproject.org/wiki/Fglrx https://fedoraproject.org/wiki/Fglrx]<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Fglrx<br />
<br />
=== Open-Source Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
We refer you to the same link:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
The installation of the open source ''radeon'' driver is straightforward, and is likely installed on your system by default. More information on the Debian ''radeon'' driver can be found here:<br />
<br />
* https://wiki.debian.org/AtiHowTo<br />
<br />
==== Fedora ====<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Radeon<br />
<br />
== Intel ==<br />
<br />
The Intel drivers are developed by the open-source community, so they are by far the easiest to install, as they pretty much will always come with your distro by default. More information on the Intel open-source drivers can be found here:<br />
<br />
* https://01.org/linuxgraphics/<br />
<br />
For the most part, this will cover how to make sure that you have the most up-to-date graphics stack for your Intel chipset. This applies exclusively to pure Intel graphics only. If you have, say, a mixed graphics card environment, like a laptop that has an Intel iGPU and a discrete NVIDIA card, please refer to the '''NVIDIA Optimus''' section<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
If you are already running a '''32-bit''' version of one of these systems, you should have everything that you need installed correctly by default. <br />
<br />
In the case of '''64-bit''' systems, you already have the 64-bit libraries for your graphics hardware. A package called '''multiarch-support''' should pull in the '''32-bit''' libraries, as well as a bunch of others.<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install multiarch-support<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
==== Debian ====<br />
<br />
The drivers should already be installed, but if it is not working with OpenGL or you get complaints about the 32-bit graphics libraries being missing, you can should try to run:<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install ia32-libs<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
If you are still having problems, consult the Debian docs here:<br />
<br />
* https://wiki.debian.org/Multiarch/HOWTO<br />
<br />
==== Fedora ====<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/Intel_graphics<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Intel</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Graphics_Card_Drivers&diff=766Graphics Card Drivers2015-04-18T18:35:39Z<p>RoninDusette: /* Fedora */</p>
<hr />
<div>In this section, we will try to cover the basics of getting the most out of your AMD, Nvidia, or Intel graphics card on your Linux system, specifically when using Wine/PlayOnLinux. This can get pretty lengthy, so expect this article to get exponentially bigger as time goes on.<br />
<br />
{{Info|This list is going to take a while to get full, so please be patient as we populate everything.}}<br />
<br />
For ease of use, we will break these down into different sections for the graphics card manufacturer, and then distro's within those categories. <br />
<br />
== NVIDIA ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
Most of the time, the easiest way is using the "Additional Drivers" dialogue. That does not always work though, and it sometimes will offer less-than-ideal versions of drivers for your NVIDIA card. If your card is supported by the current NVIDIA driver, the following command should pull in the required libraries:<br />
<br />
{{Console|sudo apt-get install nvidia-current}}<br />
<br />
You can also install other series of drivers (313.x, 319.x, 331.x, etc.) by appending the version name to them:<br />
<br />
'''Examples:'''<br />
<br />
{{Console|sudo apt-get install nvidia-331}}<br />
<br />
For the '''32-bit''' libraries, as long as ''libgl1-mesa-glx:i386'' and ''multiarch-support'' are installed, it should install them automatically. If, after you install them from the Ubuntu repositories, it does not show up, try to install those packages mentioned previously:<br />
<br />
{{Console|<br />
sudo apt-get install multiarch-support<br />
<br />
sudo apt-get install libgl1-mesa-glx:i386<br />
}}<br />
<br />
The manual installation is a bit more involved, but it is preferred by a lot of users.<br />
<br />
''Will add more later''<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary NVIDIA drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/NvidiaGraphicsDrivers<br />
<br />
==== Fedora ====<br />
* [http://rpmfusion.org/Howto/nVidia http://rpmfusion.org/Howto/nVidia]<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/NVIDIA<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVidia/nvidia-drivers<br />
<br />
=== Optimus ===<br />
<br />
NVIDIA Optimus technology is a feature in laptops with newer Intel CPU's with integrated GPUs and discrete NVIDIA graphics cards that allows switching between graphics processors on-the-fly, to optimize the performance when needed, and maximizing battery life when not needing the discrete graphics card. More information on Optimus can be found here:<br />
<br />
* http://www.nvidia.com/object/optimus_technology.html<br />
<br />
==== Most distributions ====<br />
<br />
The current working solution is maintained by the '''Bumblebee Project'''. '''PRIME''' is not recommended, as it utilizes the open-source NVIDIA driver (''nouveau''), and will not give the performance desired for most games. The project's website has detailed documentation for most major distributions, so it is recommended to go by that:<br />
<br />
* http://bumblebee-project.org/<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVIDIA_Driver_with_Optimus_Laptops<br />
<br />
=== Open-Source Drivers ===<br />
<br />
Unfortunately, the open-source ''nouveau'' drivers are not really up-to-par on performance yet for gaming. Things are starting to look up, but there are a lot of caveats to running the open-source NVIDIA drivers. More information can be found here:<br />
<br />
* http://nouveau.freedesktop.org/wiki/<br />
<br />
* http://www.phoronix.com/scan.php?page=news_topic&q=Nouveau<br />
<br />
== AMD ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
As of now, the official Ubuntu docs are VERY detailed in the installation of the open-source and proprietary graphics drivers. It is recommended to use their documentation for your AMD card on the Ubuntu distros (Mint should be very similar, if not exactly the same). You can find that information here:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary AMD/ATI drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/ATIProprietary<br />
<br />
==== Fedora ====<br />
<br />
* [https://fedoraproject.org/wiki/Fglrx https://fedoraproject.org/wiki/Fglrx]<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Fglrx<br />
<br />
=== Open-Source Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
We refer you to the same link:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
The installation of the open source ''radeon'' driver is straightforward, and is likely installed on your system by default. More information on the Debian ''radeon'' driver can be found here:<br />
<br />
* https://wiki.debian.org/AtiHowTo<br />
<br />
==== Fedora ====<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Radeon<br />
<br />
== Intel ==<br />
<br />
The Intel drivers are developed by the open-source community, so they are by far the easiest to install, as they pretty much will always come with your distro by default. More information on the Intel open-source drivers can be found here:<br />
<br />
* https://01.org/linuxgraphics/<br />
<br />
For the most part, this will cover how to make sure that you have the most up-to-date graphics stack for your Intel chipset. This applies exclusively to pure Intel graphics only. If you have, say, a mixed graphics card environment, like a laptop that has an Intel iGPU and a discrete NVIDIA card, please refer to the '''NVIDIA Optimus''' section<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
If you are already running a '''32-bit''' version of one of these systems, you should have everything that you need installed correctly by default. <br />
<br />
In the case of '''64-bit''' systems, you already have the 64-bit libraries for your graphics hardware. A package called '''multiarch-support''' should pull in the '''32-bit''' libraries, as well as a bunch of others.<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install multiarch-support<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
==== Debian ====<br />
<br />
The drivers should already be installed, but if it is not working with OpenGL or you get complaints about the 32-bit graphics libraries being missing, you can should try to run:<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install ia32-libs<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
If you are still having problems, consult the Debian docs here:<br />
<br />
* https://wiki.debian.org/Multiarch/HOWTO<br />
<br />
==== Fedora ====<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/Intel_graphics<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Intel</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Graphics_Card_Drivers&diff=765Graphics Card Drivers2015-04-18T18:33:45Z<p>RoninDusette: /* Fedora */</p>
<hr />
<div>In this section, we will try to cover the basics of getting the most out of your AMD, Nvidia, or Intel graphics card on your Linux system, specifically when using Wine/PlayOnLinux. This can get pretty lengthy, so expect this article to get exponentially bigger as time goes on.<br />
<br />
{{Info|This list is going to take a while to get full, so please be patient as we populate everything.}}<br />
<br />
For ease of use, we will break these down into different sections for the graphics card manufacturer, and then distro's within those categories. <br />
<br />
== NVIDIA ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
Most of the time, the easiest way is using the "Additional Drivers" dialogue. That does not always work though, and it sometimes will offer less-than-ideal versions of drivers for your NVIDIA card. If your card is supported by the current NVIDIA driver, the following command should pull in the required libraries:<br />
<br />
{{Console|sudo apt-get install nvidia-current}}<br />
<br />
You can also install other series of drivers (313.x, 319.x, 331.x, etc.) by appending the version name to them:<br />
<br />
'''Examples:'''<br />
<br />
{{Console|sudo apt-get install nvidia-331}}<br />
<br />
For the '''32-bit''' libraries, as long as ''libgl1-mesa-glx:i386'' and ''multiarch-support'' are installed, it should install them automatically. If, after you install them from the Ubuntu repositories, it does not show up, try to install those packages mentioned previously:<br />
<br />
{{Console|<br />
sudo apt-get install multiarch-support<br />
<br />
sudo apt-get install libgl1-mesa-glx:i386<br />
}}<br />
<br />
The manual installation is a bit more involved, but it is preferred by a lot of users.<br />
<br />
''Will add more later''<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary NVIDIA drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/NvidiaGraphicsDrivers<br />
<br />
==== Fedora ====<br />
* [http://rpmfusion.org/Howto/nVidia http://rpmfusion.org/Howto/nVidia]<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/NVIDIA<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVidia/nvidia-drivers<br />
<br />
=== Optimus ===<br />
<br />
NVIDIA Optimus technology is a feature in laptops with newer Intel CPU's with integrated GPUs and discrete NVIDIA graphics cards that allows switching between graphics processors on-the-fly, to optimize the performance when needed, and maximizing battery life when not needing the discrete graphics card. More information on Optimus can be found here:<br />
<br />
* http://www.nvidia.com/object/optimus_technology.html<br />
<br />
==== Most distributions ====<br />
<br />
The current working solution is maintained by the '''Bumblebee Project'''. '''PRIME''' is not recommended, as it utilizes the open-source NVIDIA driver (''nouveau''), and will not give the performance desired for most games. The project's website has detailed documentation for most major distributions, so it is recommended to go by that:<br />
<br />
* http://bumblebee-project.org/<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/NVIDIA_Driver_with_Optimus_Laptops<br />
<br />
=== Open-Source Drivers ===<br />
<br />
Unfortunately, the open-source ''nouveau'' drivers are not really up-to-par on performance yet for gaming. Things are starting to look up, but there are a lot of caveats to running the open-source NVIDIA drivers. More information can be found here:<br />
<br />
* http://nouveau.freedesktop.org/wiki/<br />
<br />
* http://www.phoronix.com/scan.php?page=news_topic&q=Nouveau<br />
<br />
== AMD ==<br />
<br />
=== Proprietary Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
As of now, the official Ubuntu docs are VERY detailed in the installation of the open-source and proprietary graphics drivers. It is recommended to use their documentation for your AMD card on the Ubuntu distros (Mint should be very similar, if not exactly the same). You can find that information here:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
Debian, because of the nature of the project, does not include these drivers in their repository by default, so you have to enable the non-free repository to get the proprietary AMD/ATI drivers. You can find that information here:<br />
<br />
* https://wiki.debian.org/ATIProprietary<br />
<br />
==== Fedora ====<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Fglrx<br />
<br />
=== Open-Source Drivers ===<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
We refer you to the same link:<br />
<br />
* https://help.ubuntu.com/community/BinaryDriverHowto/AMD<br />
<br />
==== Debian ====<br />
<br />
The installation of the open source ''radeon'' driver is straightforward, and is likely installed on your system by default. More information on the Debian ''radeon'' driver can be found here:<br />
<br />
* https://wiki.debian.org/AtiHowTo<br />
<br />
==== Fedora ====<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/ATI<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Radeon<br />
<br />
== Intel ==<br />
<br />
The Intel drivers are developed by the open-source community, so they are by far the easiest to install, as they pretty much will always come with your distro by default. More information on the Intel open-source drivers can be found here:<br />
<br />
* https://01.org/linuxgraphics/<br />
<br />
For the most part, this will cover how to make sure that you have the most up-to-date graphics stack for your Intel chipset. This applies exclusively to pure Intel graphics only. If you have, say, a mixed graphics card environment, like a laptop that has an Intel iGPU and a discrete NVIDIA card, please refer to the '''NVIDIA Optimus''' section<br />
<br />
==== Ubuntu/Kubuntu/Xubuntu, Mint, and derivatives ====<br />
<br />
If you are already running a '''32-bit''' version of one of these systems, you should have everything that you need installed correctly by default. <br />
<br />
In the case of '''64-bit''' systems, you already have the 64-bit libraries for your graphics hardware. A package called '''multiarch-support''' should pull in the '''32-bit''' libraries, as well as a bunch of others.<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install multiarch-support<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
==== Debian ====<br />
<br />
The drivers should already be installed, but if it is not working with OpenGL or you get complaints about the 32-bit graphics libraries being missing, you can should try to run:<br />
<br />
'''Command:'''<br />
{{Console|<br />
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade<br />
<br />
sudo apt-get install ia32-libs<br />
}}<br />
<br />
If that does not work, you can also install the package manually:<br />
<br />
{{Console|sudo apt-get install libgl1-mesa-glx:i386}}<br />
<br />
If you are still having problems, consult the Debian docs here:<br />
<br />
* https://wiki.debian.org/Multiarch/HOWTO<br />
<br />
==== Fedora ====<br />
<br />
==== Arch ====<br />
<br />
* https://wiki.archlinux.org/index.php/Intel_graphics<br />
<br />
==== Gentoo ====<br />
<br />
* http://wiki.gentoo.org/wiki/Intel</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=Troubleshooting_Common_Problems&diff=764Troubleshooting Common Problems2015-04-18T16:56:55Z<p>RoninDusette: /* Give rights to POL's WineBuild */</p>
<hr />
<div>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.<br />
<br />
When trying a possible solution for an issue, please only try '''ONE''' solution at a time, and test to see if it worked. <br />
<br />
== p11-kit: couldn't load module: ... ==<br />
<br />
=== Error ===<br />
<br />
{{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}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Mostly users of Debian, Ubuntu, Kubuntu, etc., Mint (and derivatives), 64-bit systems.<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== Install 32-bit version of p11-kit-trust.so ====<br />
<br />
<pre class='code bash'><br />
sudo apt-get install p11-kit-modules:i386<br />
</pre><br />
<br />
==== Create a symlink ====<br />
<br />
''found at http://askubuntu.com/a/384018''<br />
<br />
<pre class='code bash'><br />
sudo /usr/local/bin/getlibs -p p11-kit:i386<br />
sudo ln -s /usr/lib32/i386-linux-gnu/pkcs11/p11-kit-trust.so /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so<br />
</pre><br />
<br />
== Error in FS_Check ==<br />
<br />
=== Error ===<br />
<br />
{{Console|The following file is located on a fuse filesystem. It might prevent wine from working}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Anyone trying to run an executable file in Wine/POL that is located on an NTFS filesystem.<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== Move executable to a native Linux filesystem ====<br />
<br />
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.<br />
<br />
== Failed to use ICMP ==<br />
<br />
=== Error ===<br />
<br />
{{Console|err:winediag:IcmpCreateFile Failed to use ICMP (network ping), this requires special permissions.<br />
}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
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.<br />
<br />
=== What causes this error? ===<br />
<br />
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? ;)<br />
<br />
=== Common solutions ===<br />
<br />
==== Give rights to POL's WineBuild ====<br />
<br />
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.<br />
<br />
For instance, '''AION'''.<br />
<br />
All of POL's WineBuilds are stored in ~/.PlayOnLinux/wine/<br />
<br />
Within this folder, you have different sub-folders for architecture, and then Wine version. In the case of '''AION''':<br />
<br />
{{Console|/home/username/.PlayOnLinux/wine/linux-x86/1.7.36}}<br />
<br />
Find out which Wine version your application needs:<br />
<br />
# Open the Configuration Window<br />
# In the General tab, when your virtual drive is selected, look at the name of the version of Wine in use. <br />
<br />
Now, the command you would want to run is:<br />
<br />
'''NOTE''': ''Do NOT copy and paste these commands. They need to be modified for your particular situation.''<br />
<br />
{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine}}<br />
<br />
or<br />
<br />
{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine-preloader}}<br />
<br />
'''NOTE:''' ''I have seen both bin/wine and bin/wine-preloader shown in examples, so for posterity, I am including both.''<br />
<br />
Essentially, the syntax for this is as follows:<br />
<br />
{{Console|sudo setcap cap_net_raw+epi /home/'''username'''/.PlayOnLinux/wine/'''WineArchitecture'''/'''WineVersion'''/bin/wine}}<br />
<br />
Replace: <br />
<br />
* '''username''' with your current username<br />
<br />
* '''Wine Architecture''' with either '''linux-x86''' (32-bit virtual drive) or '''linux-amd64''' (64-bit virtual drive)<br />
<br />
* '''Wine Version''' with the '''EXACT''' name listed in the '''Wine dropdown menu''' in the '''General tab''' of the ''' Configuration Window'''<br />
<br />
== Error! Files mismatch ==<br />
<br />
=== Error ===<br />
<br />
{{Console|''someurl''<br />
<br />
<br />
Error! Files mismatch<br />
<br />
<br />
Local: ''md5resultexpected''<br />
<br />
Server: ''md5resultdownloaded''<br />
<br />
<br />
<br />
Do you want to retry?<br />
}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
This can happen to any user on any system. It is also architecture agnostic.<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== File bug report with POL ====<br />
<br />
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.).<br />
<br />
== The application you are trying to install needs administrator rights... ==<br />
<br />
=== Error ===<br />
<br />
{{Console|The application you are trying to install needs administrator rights to function correctly.}}<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Anyone on any distro may see this error<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== File bug report with WineHQ ====<br />
<br />
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:<br />
<br />
* [https://bugs.winehq.org/ WineHQ's Bugzilla]<br />
<br />
== League of Legends Stuck on Logo (after Champ Select) ==<br />
<br />
=== Error ===<br />
<br />
League of Legends simply stalls at the logo after the champion select dialogue.<br />
<br />
=== Who might encounter this error? ===<br />
<br />
Anyone on any distro may see this error<br />
<br />
=== What causes this error? ===<br />
<br />
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.<br />
<br />
=== Common solutions ===<br />
<br />
==== Install needed components ====<br />
<br />
Instructions adapted from this thread:<br />
<br />
[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]<br />
<br />
# Install in POL: d3dx10, d3dx11, d3dx9 (only d3dx9, not the other d3dx9_etc) and directx9<br />
# 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"</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=FAQ&diff=763FAQ2015-04-18T16:45:45Z<p>RoninDusette: /* How do I install Steam, and Steam only? */</p>
<hr />
<div>== PlayOnLinux and PlayOnMac ==<br />
<br />
=== How do I find out if a game will run on PlayOnLinux/PlayOnMac? ===<br />
Excellent question. Since POL/POM is a front-end for [https://winehq.org/ Wine], the first place to check, besides our [https://www.playonlinux.com/en/supported_apps.html Supported Software section], is WineHQ's [https://appdb.winehq.org/ AppDB]. There are many, many entries for a lot of different types of Windows applications, all submitted to the Wine community by users like yourself. If it is even remotely popular, and people have attempted to use it through Wine, it will likely be listed there.<br />
<br />
=== How do I move PlayOnLinux virtual drives to another disk (with more free space)? ===<br />
Read the advanced topic here:<br />
* [[How to move PlayOnLinux virtual drives to another disk|How to move PlayOnLinux virtual drives to another disk]]<br />
<br />
=== Why isn't PlayOnLinux downloading Photoshop (or whatever retail application) for me? ===<br />
PlayOnLinux/PlayOnMac does not actually provide the applications. It provides the means to install those applications. You actually have to own, say, Photoshop CS6, in order to install Photoshop CS6. POL/POM does not provide any sort of pirated software in any way. This also applies to support regarding pirated software and cracks.<br />
<br />
=== Do I have to install Wine to use PlayOnLinux? ===<br />
Yes. You will want to have a 32-bit version of Wine installed on your system, along with the dependencies it suggests. POL will want to see it, and will use it's dependencies concurrently with POL's WineBuilds. Without getting too technical, POL will need it, so it is best to install it.<br />
<br />
=== Will PlayOnLinux interfere with my current Wine or winetricks installations? ===<br />
No. PlayOnLinux/PlayOnMac keeps all of it's resources, WineBuilds, and virtual drives contained in one folder, and will never interfere with your other WINEPREFIX created by vanilla Wine and winetricks (unless, of course, you start using winetricks for POL virtual drives or try to use vanilla Wine on a POL virtual drive, or something like that.).<br />
<br />
=== The application I am trying to install needs administrator rights to function correctly ===<br />
Wine does not implement privileges, so such message does not make any sense under Wine. Either it cannot be made to work, or emulated Windows version must be changed to some version that does not implement privileges (Win9x for instance) so that the installer changes its expectations.<br />
<br />
=== How do I install Steam, and Steam only? ===<br />
<br />
If you want to only install Steam for Windows into a Virtual Drive, you will need to do a manual installation. It is very simple:<br />
<br />
# Open PlayOnLinux, download and install the WineBuild that you want from [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions].<br />
# Open the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window], click New, and create a new Virtual Drive, naming it what you want, and selecting the WineBuild that you want to use when prompted.<br />
# In the Configuration Window, select your new Virtual Drive, open the Install Components tab, and double-click '''Steam''' in that list. Steam will be installed into the Virtual Drive highlighted on the left side.<br />
# On the General Tab of the Configuration Window, select '''Make a new shortcut from this virtual drive''', and select the Steam executable when shown in the list. This will create a shortcut in the main POL window. <br />
<br />
'''NOTE:''' ''This is a manual install, and does not guarantee that the game that you install through Steam will work. If it does not work, you should check to see if there is already an installer for that game in our repository, and if not, you will need to check the [https://appdb.winehq.org AppDB at WineHQ] for your game to see if it needs any extra components or settings. As always, for manual installs, feel free to post up for help in the appropriate section of [https://www.playonlinux.com/en/forum-24-Manual_installations.html the forums].''<br />
<br />
== Website ==<br />
<br />
=== How can I post a bug report? ===<br />
* [[How to Post a Bug Report|How to Post a Bug Report]]<br />
<br />
=== How can I contribute an installer for an application? ===<br />
First, you would want to read our scripters tutorial here: [[Scripting - Chapter 1: Getting to know Bash|Scripting tutorial]]<br />
<br />
Then once you have written and tested a script, and it is working, follow the instructions here to submit it to us: [[How to Contribute a Script|How to Contribute a Script]]<br />
<br />
=== How do I request a version of Wine with a certain patch? ===<br />
* [[How to Request a Patched Version of Wine|How to Request a Patched Version of Wine]]<br />
<br />
=== Where does PlayOnLinux store it's virtual drives and cache? ===<br />
All virtual drives are created and store here:<br />
<br />
<code>~/.PlayOnLinux/wineprefix/</code><br />
<br />
The other files for Wine versions, resources, and components cache are located in '''~/.PlayOnLinux/'''<br />
<br />
=== How do I run Wine/POL as root or sudo? ===<br />
You don't. You should never, ever run Wine or POL as root or using sudo, or any other privilege escalation mechanism. <br />
<br />
* [http://wiki.winehq.org/FAQ#head-96bebfa287b4288974de0df23351f278b0d41014 WineHQ FAQ regarding root/sudo use]<br />
<br />
=== Is there a list of solutions for common problems? ===<br />
Somewhat, as issues can vary a '''LOT''' between users, systems, Wine versions, graphics cards, etc.. As a start, you should check the following locations:<br />
<br />
* [https://appdb.winehq.org/ appdb.winehq.org]<br />
* [[Troubleshooting Common Problems|Troubleshooting Common Problems]]<br />
* [https://www.playonlinux.com/en/forums.html The POL/POM forums]<br />
* Google, of course<br />
<br />
=== My post was closed with a semi-automated reply? What did I break? ===<br />
Nothing. What that means is that your post is lacking information that we need to troubleshoot, or possibly violates our terms of service. <br />
<br />
Check the following links to make sure that you didn't accidentally violate ToS, and t haatt you areIinformation required:<br />
<br />
* https://www.playonlinux.com/en/terms.html<br />
<br />
* [[How to Post in the Forums|How to Post in the Forums]]<br />
<br />
== I want to contribute ==<br />
<br />
=== Bash; I really want to know more ===<br />
* http://www.gnu.org/software/bash/<br />
<br />
* http://linuxconfig.org/bash-scripting-tutorial<br />
<br />
* http://www.tldp.org/LDP/Bash-Beginners-Guide/html/<br />
<br />
* http://www.tldp.org/LDP/abs/html/<br />
<br />
=== Python; I really want to know more ===<br />
* https://www.python.org/<br />
<br />
* https://docs.python.org/2/tutorial/<br />
<br />
* http://www.learnpython.org/</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=FAQ&diff=762FAQ2015-04-18T16:45:24Z<p>RoninDusette: /* How do I install Steam, and Steam only? */</p>
<hr />
<div>== PlayOnLinux and PlayOnMac ==<br />
<br />
=== How do I find out if a game will run on PlayOnLinux/PlayOnMac? ===<br />
Excellent question. Since POL/POM is a front-end for [https://winehq.org/ Wine], the first place to check, besides our [https://www.playonlinux.com/en/supported_apps.html Supported Software section], is WineHQ's [https://appdb.winehq.org/ AppDB]. There are many, many entries for a lot of different types of Windows applications, all submitted to the Wine community by users like yourself. If it is even remotely popular, and people have attempted to use it through Wine, it will likely be listed there.<br />
<br />
=== How do I move PlayOnLinux virtual drives to another disk (with more free space)? ===<br />
Read the advanced topic here:<br />
* [[How to move PlayOnLinux virtual drives to another disk|How to move PlayOnLinux virtual drives to another disk]]<br />
<br />
=== Why isn't PlayOnLinux downloading Photoshop (or whatever retail application) for me? ===<br />
PlayOnLinux/PlayOnMac does not actually provide the applications. It provides the means to install those applications. You actually have to own, say, Photoshop CS6, in order to install Photoshop CS6. POL/POM does not provide any sort of pirated software in any way. This also applies to support regarding pirated software and cracks.<br />
<br />
=== Do I have to install Wine to use PlayOnLinux? ===<br />
Yes. You will want to have a 32-bit version of Wine installed on your system, along with the dependencies it suggests. POL will want to see it, and will use it's dependencies concurrently with POL's WineBuilds. Without getting too technical, POL will need it, so it is best to install it.<br />
<br />
=== Will PlayOnLinux interfere with my current Wine or winetricks installations? ===<br />
No. PlayOnLinux/PlayOnMac keeps all of it's resources, WineBuilds, and virtual drives contained in one folder, and will never interfere with your other WINEPREFIX created by vanilla Wine and winetricks (unless, of course, you start using winetricks for POL virtual drives or try to use vanilla Wine on a POL virtual drive, or something like that.).<br />
<br />
=== The application I am trying to install needs administrator rights to function correctly ===<br />
Wine does not implement privileges, so such message does not make any sense under Wine. Either it cannot be made to work, or emulated Windows version must be changed to some version that does not implement privileges (Win9x for instance) so that the installer changes its expectations.<br />
<br />
=== How do I install Steam, and Steam only? ===<br />
<br />
If you want to only install Steam for Windows into a virtual drive, you will need to do a manual installation. It is very simple:<br />
<br />
# Open PlayOnLinux, download and install the WineBuild that you want from [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions].<br />
# Open the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window], click New, and create a new Virtual Drive, naming it what you want, and selecting the WineBuild that you want to use when prompted.<br />
# In the Configuration Window, select your new Virtual Drive, open the Install Components tab, and double-click '''Steam''' in that list. Steam will be installed into the Virtual Drive highlighted on the left side.<br />
# On the General Tab of the Configuration Window, select '''Make a new shortcut from this virtual drive''', and select the Steam executable when shown in the list. This will create a shortcut in the main POL window. <br />
<br />
'''NOTE:''' ''This is a manual install, and does not guarantee that the game that you install through Steam will work. If it does not work, you should check to see if there is already an installer for that game in our repository, and if not, you will need to check the [https://appdb.winehq.org AppDB at WineHQ] for your game to see if it needs any extra components or settings. As always, for manual installs, feel free to post up for help in the appropriate section of [https://www.playonlinux.com/en/forum-24-Manual_installations.html the forums].''<br />
<br />
== Website ==<br />
<br />
=== How can I post a bug report? ===<br />
* [[How to Post a Bug Report|How to Post a Bug Report]]<br />
<br />
=== How can I contribute an installer for an application? ===<br />
First, you would want to read our scripters tutorial here: [[Scripting - Chapter 1: Getting to know Bash|Scripting tutorial]]<br />
<br />
Then once you have written and tested a script, and it is working, follow the instructions here to submit it to us: [[How to Contribute a Script|How to Contribute a Script]]<br />
<br />
=== How do I request a version of Wine with a certain patch? ===<br />
* [[How to Request a Patched Version of Wine|How to Request a Patched Version of Wine]]<br />
<br />
=== Where does PlayOnLinux store it's virtual drives and cache? ===<br />
All virtual drives are created and store here:<br />
<br />
<code>~/.PlayOnLinux/wineprefix/</code><br />
<br />
The other files for Wine versions, resources, and components cache are located in '''~/.PlayOnLinux/'''<br />
<br />
=== How do I run Wine/POL as root or sudo? ===<br />
You don't. You should never, ever run Wine or POL as root or using sudo, or any other privilege escalation mechanism. <br />
<br />
* [http://wiki.winehq.org/FAQ#head-96bebfa287b4288974de0df23351f278b0d41014 WineHQ FAQ regarding root/sudo use]<br />
<br />
=== Is there a list of solutions for common problems? ===<br />
Somewhat, as issues can vary a '''LOT''' between users, systems, Wine versions, graphics cards, etc.. As a start, you should check the following locations:<br />
<br />
* [https://appdb.winehq.org/ appdb.winehq.org]<br />
* [[Troubleshooting Common Problems|Troubleshooting Common Problems]]<br />
* [https://www.playonlinux.com/en/forums.html The POL/POM forums]<br />
* Google, of course<br />
<br />
=== My post was closed with a semi-automated reply? What did I break? ===<br />
Nothing. What that means is that your post is lacking information that we need to troubleshoot, or possibly violates our terms of service. <br />
<br />
Check the following links to make sure that you didn't accidentally violate ToS, and t haatt you areIinformation required:<br />
<br />
* https://www.playonlinux.com/en/terms.html<br />
<br />
* [[How to Post in the Forums|How to Post in the Forums]]<br />
<br />
== I want to contribute ==<br />
<br />
=== Bash; I really want to know more ===<br />
* http://www.gnu.org/software/bash/<br />
<br />
* http://linuxconfig.org/bash-scripting-tutorial<br />
<br />
* http://www.tldp.org/LDP/Bash-Beginners-Guide/html/<br />
<br />
* http://www.tldp.org/LDP/abs/html/<br />
<br />
=== Python; I really want to know more ===<br />
* https://www.python.org/<br />
<br />
* https://docs.python.org/2/tutorial/<br />
<br />
* http://www.learnpython.org/</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=FAQ&diff=761FAQ2015-04-18T16:45:10Z<p>RoninDusette: /* How do I install Steam, and Steam only? */</p>
<hr />
<div>== PlayOnLinux and PlayOnMac ==<br />
<br />
=== How do I find out if a game will run on PlayOnLinux/PlayOnMac? ===<br />
Excellent question. Since POL/POM is a front-end for [https://winehq.org/ Wine], the first place to check, besides our [https://www.playonlinux.com/en/supported_apps.html Supported Software section], is WineHQ's [https://appdb.winehq.org/ AppDB]. There are many, many entries for a lot of different types of Windows applications, all submitted to the Wine community by users like yourself. If it is even remotely popular, and people have attempted to use it through Wine, it will likely be listed there.<br />
<br />
=== How do I move PlayOnLinux virtual drives to another disk (with more free space)? ===<br />
Read the advanced topic here:<br />
* [[How to move PlayOnLinux virtual drives to another disk|How to move PlayOnLinux virtual drives to another disk]]<br />
<br />
=== Why isn't PlayOnLinux downloading Photoshop (or whatever retail application) for me? ===<br />
PlayOnLinux/PlayOnMac does not actually provide the applications. It provides the means to install those applications. You actually have to own, say, Photoshop CS6, in order to install Photoshop CS6. POL/POM does not provide any sort of pirated software in any way. This also applies to support regarding pirated software and cracks.<br />
<br />
=== Do I have to install Wine to use PlayOnLinux? ===<br />
Yes. You will want to have a 32-bit version of Wine installed on your system, along with the dependencies it suggests. POL will want to see it, and will use it's dependencies concurrently with POL's WineBuilds. Without getting too technical, POL will need it, so it is best to install it.<br />
<br />
=== Will PlayOnLinux interfere with my current Wine or winetricks installations? ===<br />
No. PlayOnLinux/PlayOnMac keeps all of it's resources, WineBuilds, and virtual drives contained in one folder, and will never interfere with your other WINEPREFIX created by vanilla Wine and winetricks (unless, of course, you start using winetricks for POL virtual drives or try to use vanilla Wine on a POL virtual drive, or something like that.).<br />
<br />
=== The application I am trying to install needs administrator rights to function correctly ===<br />
Wine does not implement privileges, so such message does not make any sense under Wine. Either it cannot be made to work, or emulated Windows version must be changed to some version that does not implement privileges (Win9x for instance) so that the installer changes its expectations.<br />
<br />
=== How do I install Steam, and Steam only? ===<br />
<br />
If you want to only install Steam for Windows into a virtual drive, you will need to do a manual installation. It is very simple:<br />
<br />
# Open PlayOnLinux, download and install the WineBuild that you want from [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions].<br />
<br />
# Open the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window], click New, and create a new Virtual Drive, naming it what you want, and selecting the WineBuild that you want to use when prompted.<br />
<br />
# In the Configuration Window, select your new Virtual Drive, open the Install Components tab, and double-click '''Steam''' in that list. Steam will be installed into the Virtual Drive highlighted on the left side.<br />
<br />
# On the General Tab of the Configuration Window, select '''Make a new shortcut from this virtual drive''', and select the Steam executable when shown in the list. This will create a shortcut in the main POL window. <br />
<br />
'''NOTE:''' ''This is a manual install, and does not guarantee that the game that you install through Steam will work. If it does not work, you should check to see if there is already an installer for that game in our repository, and if not, you will need to check the [https://appdb.winehq.org AppDB at WineHQ] for your game to see if it needs any extra components or settings. As always, for manual installs, feel free to post up for help in the appropriate section of [https://www.playonlinux.com/en/forum-24-Manual_installations.html the forums].''<br />
<br />
== Website ==<br />
<br />
=== How can I post a bug report? ===<br />
* [[How to Post a Bug Report|How to Post a Bug Report]]<br />
<br />
=== How can I contribute an installer for an application? ===<br />
First, you would want to read our scripters tutorial here: [[Scripting - Chapter 1: Getting to know Bash|Scripting tutorial]]<br />
<br />
Then once you have written and tested a script, and it is working, follow the instructions here to submit it to us: [[How to Contribute a Script|How to Contribute a Script]]<br />
<br />
=== How do I request a version of Wine with a certain patch? ===<br />
* [[How to Request a Patched Version of Wine|How to Request a Patched Version of Wine]]<br />
<br />
=== Where does PlayOnLinux store it's virtual drives and cache? ===<br />
All virtual drives are created and store here:<br />
<br />
<code>~/.PlayOnLinux/wineprefix/</code><br />
<br />
The other files for Wine versions, resources, and components cache are located in '''~/.PlayOnLinux/'''<br />
<br />
=== How do I run Wine/POL as root or sudo? ===<br />
You don't. You should never, ever run Wine or POL as root or using sudo, or any other privilege escalation mechanism. <br />
<br />
* [http://wiki.winehq.org/FAQ#head-96bebfa287b4288974de0df23351f278b0d41014 WineHQ FAQ regarding root/sudo use]<br />
<br />
=== Is there a list of solutions for common problems? ===<br />
Somewhat, as issues can vary a '''LOT''' between users, systems, Wine versions, graphics cards, etc.. As a start, you should check the following locations:<br />
<br />
* [https://appdb.winehq.org/ appdb.winehq.org]<br />
* [[Troubleshooting Common Problems|Troubleshooting Common Problems]]<br />
* [https://www.playonlinux.com/en/forums.html The POL/POM forums]<br />
* Google, of course<br />
<br />
=== My post was closed with a semi-automated reply? What did I break? ===<br />
Nothing. What that means is that your post is lacking information that we need to troubleshoot, or possibly violates our terms of service. <br />
<br />
Check the following links to make sure that you didn't accidentally violate ToS, and t haatt you areIinformation required:<br />
<br />
* https://www.playonlinux.com/en/terms.html<br />
<br />
* [[How to Post in the Forums|How to Post in the Forums]]<br />
<br />
== I want to contribute ==<br />
<br />
=== Bash; I really want to know more ===<br />
* http://www.gnu.org/software/bash/<br />
<br />
* http://linuxconfig.org/bash-scripting-tutorial<br />
<br />
* http://www.tldp.org/LDP/Bash-Beginners-Guide/html/<br />
<br />
* http://www.tldp.org/LDP/abs/html/<br />
<br />
=== Python; I really want to know more ===<br />
* https://www.python.org/<br />
<br />
* https://docs.python.org/2/tutorial/<br />
<br />
* http://www.learnpython.org/</div>RoninDusettehttps://wiki.playonlinux.com/index.php?title=FAQ&diff=760FAQ2015-04-18T16:44:34Z<p>RoninDusette: </p>
<hr />
<div>== PlayOnLinux and PlayOnMac ==<br />
<br />
=== How do I find out if a game will run on PlayOnLinux/PlayOnMac? ===<br />
Excellent question. Since POL/POM is a front-end for [https://winehq.org/ Wine], the first place to check, besides our [https://www.playonlinux.com/en/supported_apps.html Supported Software section], is WineHQ's [https://appdb.winehq.org/ AppDB]. There are many, many entries for a lot of different types of Windows applications, all submitted to the Wine community by users like yourself. If it is even remotely popular, and people have attempted to use it through Wine, it will likely be listed there.<br />
<br />
=== How do I move PlayOnLinux virtual drives to another disk (with more free space)? ===<br />
Read the advanced topic here:<br />
* [[How to move PlayOnLinux virtual drives to another disk|How to move PlayOnLinux virtual drives to another disk]]<br />
<br />
=== Why isn't PlayOnLinux downloading Photoshop (or whatever retail application) for me? ===<br />
PlayOnLinux/PlayOnMac does not actually provide the applications. It provides the means to install those applications. You actually have to own, say, Photoshop CS6, in order to install Photoshop CS6. POL/POM does not provide any sort of pirated software in any way. This also applies to support regarding pirated software and cracks.<br />
<br />
=== Do I have to install Wine to use PlayOnLinux? ===<br />
Yes. You will want to have a 32-bit version of Wine installed on your system, along with the dependencies it suggests. POL will want to see it, and will use it's dependencies concurrently with POL's WineBuilds. Without getting too technical, POL will need it, so it is best to install it.<br />
<br />
=== Will PlayOnLinux interfere with my current Wine or winetricks installations? ===<br />
No. PlayOnLinux/PlayOnMac keeps all of it's resources, WineBuilds, and virtual drives contained in one folder, and will never interfere with your other WINEPREFIX created by vanilla Wine and winetricks (unless, of course, you start using winetricks for POL virtual drives or try to use vanilla Wine on a POL virtual drive, or something like that.).<br />
<br />
=== The application I am trying to install needs administrator rights to function correctly ===<br />
Wine does not implement privileges, so such message does not make any sense under Wine. Either it cannot be made to work, or emulated Windows version must be changed to some version that does not implement privileges (Win9x for instance) so that the installer changes its expectations.<br />
<br />
=== How do I install Steam, and Steam only? ===<br />
<br />
If you want to only install Steam for Windows into a virtual drive, you will need to do a manual installation. It is very simple:<br />
<br />
# Open PlayOnLinux, download and install the WineBuild that you want from [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions].<br />
<br />
# Open the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window], click New, and create a new Virtual Drive, naming it what you want, and selecting the WineBuild that you want to use when prompted.<br />
<br />
# In the Configuration Window, select your new Virtual Drive, open the Install Components tab, and double-click '''Steam''' in that list. Steam will be installed into the Virtual Drive highlighted on the left side.<br />
<br />
# On the General Tab of the Configuration Window, select '''Make a new shortcut from this virtual drive''', and select the Steam executable when shown in the list. This will create a shortcut in the main POL window. <br />
<br />
''NOTE:'' '''This is a manual install, and does not guarantee that the game that you install through Steam will work. If it does not work, you should check to see if there is already an installer for that game in our repository, and if not, you will need to check the [https://appdb.winehq.org AppDB at WineHQ] for your game to see if it needs any extra components or settings. As always, for manual installs, feel free to post up for help in the appropriate section of [https://www.playonlinux.com/en/forum-24-Manual_installations.html the forums]. <br />
<br />
== Website ==<br />
<br />
=== How can I post a bug report? ===<br />
* [[How to Post a Bug Report|How to Post a Bug Report]]<br />
<br />
=== How can I contribute an installer for an application? ===<br />
First, you would want to read our scripters tutorial here: [[Scripting - Chapter 1: Getting to know Bash|Scripting tutorial]]<br />
<br />
Then once you have written and tested a script, and it is working, follow the instructions here to submit it to us: [[How to Contribute a Script|How to Contribute a Script]]<br />
<br />
=== How do I request a version of Wine with a certain patch? ===<br />
* [[How to Request a Patched Version of Wine|How to Request a Patched Version of Wine]]<br />
<br />
=== Where does PlayOnLinux store it's virtual drives and cache? ===<br />
All virtual drives are created and store here:<br />
<br />
<code>~/.PlayOnLinux/wineprefix/</code><br />
<br />
The other files for Wine versions, resources, and components cache are located in '''~/.PlayOnLinux/'''<br />
<br />
=== How do I run Wine/POL as root or sudo? ===<br />
You don't. You should never, ever run Wine or POL as root or using sudo, or any other privilege escalation mechanism. <br />
<br />
* [http://wiki.winehq.org/FAQ#head-96bebfa287b4288974de0df23351f278b0d41014 WineHQ FAQ regarding root/sudo use]<br />
<br />
=== Is there a list of solutions for common problems? ===<br />
Somewhat, as issues can vary a '''LOT''' between users, systems, Wine versions, graphics cards, etc.. As a start, you should check the following locations:<br />
<br />
* [https://appdb.winehq.org/ appdb.winehq.org]<br />
* [[Troubleshooting Common Problems|Troubleshooting Common Problems]]<br />
* [https://www.playonlinux.com/en/forums.html The POL/POM forums]<br />
* Google, of course<br />
<br />
=== My post was closed with a semi-automated reply? What did I break? ===<br />
Nothing. What that means is that your post is lacking information that we need to troubleshoot, or possibly violates our terms of service. <br />
<br />
Check the following links to make sure that you didn't accidentally violate ToS, and t haatt you areIinformation required:<br />
<br />
* https://www.playonlinux.com/en/terms.html<br />
<br />
* [[How to Post in the Forums|How to Post in the Forums]]<br />
<br />
== I want to contribute ==<br />
<br />
=== Bash; I really want to know more ===<br />
* http://www.gnu.org/software/bash/<br />
<br />
* http://linuxconfig.org/bash-scripting-tutorial<br />
<br />
* http://www.tldp.org/LDP/Bash-Beginners-Guide/html/<br />
<br />
* http://www.tldp.org/LDP/abs/html/<br />
<br />
=== Python; I really want to know more ===<br />
* https://www.python.org/<br />
<br />
* https://docs.python.org/2/tutorial/<br />
<br />
* http://www.learnpython.org/</div>RoninDusette