The forum

Disable playonlinux logs in each wineprefix

Author Replies
Coriolis Tuesday 9 February 2016 at 0:02
CoriolisAnonymous

I've noticed that POL creates playonlinux.log in each wineprefix. Sometimes, because of harlmess wine errors and "fixme" messages it's getting filled quite quickly. For example, SpaceEngine creates 3 mb of same error message in just 2 minutes. I've tried to put "-all" debug flags in settings, but apparently it only affects debug mode. Is there a way to disable logging at all?

petch Tuesday 9 February 2016 at 7:25
petch
Developer

 

I've noticed that POL creates playonlinux.log in each wineprefix. Sometimes, because of harlmess wine errors and "fixme" messages it's getting filled quite quickly. For example, SpaceEngine creates 3 mb of same error message in just 2 minutes. I've tried to put "-all" debug flags in settings, but apparently it only affects debug mode.

When not in debug mode PlayOnLinux uses -all debug flags, so that's not normal. What is being logged exactly?

Is there a way to disable logging at all?

I didn't have the time to check, I can't guarantee it'll be supported forever (it should work for any 4.x version at least) but you can try:

Configure button > (select shortcut) > Miscellaneous tab > Command to run before the program is launched:

export LOGFILE=/dev/null

 

Coriolis Tuesday 9 February 2016 at 22:26
CoriolisAnonymous

When not in debug mode PlayOnLinux uses -all debug flags, so that's not normal. What is being logged exactly?

Unfortunately I cant provide playonlinux.log from my Space Engine now installation since I'm on a different system now, but I have logs from running world machine on mint 17 installation under virtualbox, and, as I understand, playonlinug.log have logs from both POL itself and wine, so it's still being filled with stuff like logs of running world machine itself every time.

[02/10/16 00:08:01] - Running wine- World Machine.exe (Working directory : /home/shrekit/.PlayOnLinux/wineprefix/WorldMachine/drive_c/Program Files/World Machine 2 Basic)
libGL error: pci id for fd 14: 80ee:beef, driver (null)
 
!!Assertion Failed!!
Expression: RT_SUCCESS_NP(rc)
Location  : /build/buildd/virtualbox-4.3.18-dfsg/src/VBox/Runtime/common/misc/thread.cpp(227) void rtThreadLockRW()

VERR_INVALID_HANDLE (-4) - Invalid loader handle.

it crashes, but it's because I'm running it in virtualbox.

Also, using LOGFILE=/dev/null, does that mean that logfile is still being written to my hard drive and then being removed? I'm using ssd and trying to minimize unnecessary drive I/O as much as possible.

petch Tuesday 9 February 2016 at 23:26
petch
Developer

Unfortunately I cant provide playonlinux.log from my Space Engine now installation since I'm on a different system now, but I have logs from running world machine on mint 17 installation under virtualbox, and, as I understand, playonlinug.log have logs from both POL itself and wine, so it's still being filled with stuff like logs of running world machine itself every time.
[02/10/16 00:08:01] - Running wine- World Machine.exe (Working directory : /home/shrekit/.PlayOnLinux/wineprefix/WorldMachine/drive_c/Program Files/World Machine 2 Basic)
libGL error: pci id for fd 14: 80ee:beef, driver (null)
 
!!Assertion Failed!!
Expression: RT_SUCCESS_NP(rc)
Location  : /build/buildd/virtualbox-4.3.18-dfsg/src/VBox/Runtime/common/misc/thread.cpp(227) void rtThreadLockRW()

VERR_INVALID_HANDLE (-4) - Invalid loader handle.

Ok, so those are logs from PlayOnLinux (first line) and logs from the game itself, none from Wine, as expected with -all flags

Also, using LOGFILE=/dev/null, does that mean that logfile is still being written to my hard drive and then being removed? I'm using ssd and trying to minimize unnecessary drive I/O as much as possible.

If it works no logs will be written.

Edited by petch

Coriolis Tuesday 9 February 2016 at 23:48
CoriolisAnonymous

Thank you for quick response, if I run POL itself with "LOGFILE=/dev/null", will it work for all applications launched from playonlinux?

LOGFILE=/dev/null playonlinux

Also, I have another problem, how exactly does this "Command to run before the program" function work? I have optimus laptop and using bumblebee. On the official FAQ it's stated that I should put "optirun" or "primusrun" commands in that field but it seems that instead of appending the content of that field to start of command, it runs it separately.

How it's supposed to be if I put "primusrun" in that field:

primusrun wine "World Machine.exe"

How it actually is:

primusrun

wine "World Machine.exe"

I've tried to put some random commands into that field (for example, thunar, xfce4-terminal or mousepad) to see if it's actually appending it to start of the command, but instead was getting just empty instances of these applications launched without them opening anything, just like if I run it from start menu.

petch Wednesday 10 February 2016 at 8:13
petch
Developer

 

Thank you for quick response, if I run POL itself with "LOGFILE=/dev/null", will it work for all applications launched from playonlinux?

LOGFILE=/dev/null playonlinux

No, that variable is just set internally before running Wine

Also, I have another problem, how exactly does this "Command to run before the program" function work?

How it's supposed to be if I put "primusrun" in that field:

primusrun wine "World Machine.exe"

How it actually is:

primusrun

wine "World Machine.exe"

PlayOnLinux indeed runs the commands in this field separately; If you want to actually prefix the command with something, use

export BEFORE_WINE='something'

As to how to use it to run primusrun, you tell us, we tried to add support in PlayOnLinux 4.1.0 and had to remove it because it didn't work (and we don't have the hardware to debug the situation)

Edited by petch