Het forum

I just upgraded PlayOnLinux to 4.0.18 today and now I can't run anything. Double-click does literally nothing and debug console shows messages like this:

[CODE]
Writting log to /media/sda4/tom/.PlayOnLinux//tmp/errors_Utawarerumono.log.e

[POL_System_CheckFS] Message: Checking filesystem for /media/sda4/tom/.PlayOnLinux/wineprefix/Utawarerumono/drive_c/Utaware/utaware-dvd.exe
[FS_Check] Error: The following file is located on a fuse filesystem.
It might prevent wine from working

/media/sda4/tom/.PlayOnLinux/wineprefix/Utawarerumono/drive_c/Utaware/utaware-dvd.exe
[/CODE]

I should note that /media/sda4/tom/.PlayOnLinux/wineprefix/Utawarerumono/drive_c/Utaware is symbolic link to folder placed on NTFS drive.

Wine has no problem with this setup nor older version of PlayOnLinux had, but  filesystem check simply exits and gives wine no chance to try.

Can't filesystem check yeld warning instead of fatal error?

And how can I disable it completly?

POL_Config_Write NO_FSCHECK TRUE

in PlayOnLinux console should help you. Note that we do not support PlayOnLinux problems when this is enabled

Thanks. Can I ask what problems may occur when I'm running exe from fuse drive?

Read that : http://www.playonlinux.com/fr/issue-728.html

POL_Config_Write NO_FSCHECK TRUE
doesnt work, and by that i mean
it says, order not found or something like that in the console
im using the spanish version, does it have something to do with that?

Did you type it in PlayOnLinux console?
Tools > PlayOnLinux console

i did

PlayOnLinux Console
-------------------

PlayOnLinux: ~/.PlayOnLinux > POL_Config_Write NO_FSCHECK TRUE
[POL_Config_Write] Message: Config write: NO_FSCHECK TRUE
PlayOnLinux: ~/.PlayOnLinux >
Works for me.

PlayOnLinux: ~/.PlayOnLinux > POL_Config_Write NO_FSCHECK TRUE
[POL_Config_Write] Message: no se encontró la orden
PlayOnLinux: ~/.PlayOnLinux > 

"no se encontró la orden"(means order not found in english)
but the point is, it is not working for me -_-
as i said before, does it have something to do with the fact my computer language is in spanish?

I had to be sure, because this is exactly the kind of message you get when typing something not recognized by the shell, like, if you typed it in a standard terminal.

Looking at what you pasted it seems you did the right thing, POL_Config_Write has been called, and POL_Debug_Message called by it to display this standard message from shells...
Which looking at the code, does not seems to make sense...
This is really puzzling

By the way I'm running PlayOnLinux in an environment configured for french language, and ran it in spanish in a VM for testing, and it makes no difference: it just worked

-_-, i will try re-installing it, maybe that will solve the problem