Linux mint 19 Internal error ppy.y 387

Questions about Wine on Linux
Locked
slavikgenes
Newbie
Newbie
Posts: 3
Joined: Tue Jul 10, 2018 2:32 am

Linux mint 19 Internal error ppy.y 387

Post by slavikgenes »

I have a problem with playing Lego The Hobbit under the wine. Games loads normally, gives me ability to choose safe zone (basic gui setting) but when main menu shows up the game crashes with error:

Code: Select all

Internal error (please report) ppy.y 387: Invalid type indicator (0x0001)
wine: Unhandled page fault on write access to 0x2dca1ef5 at address 0xf6bc706a (thread 0033), starting debugger...
AL lib: (EE) alc_cleanup: 1 device not closed
Tried several wine versions - 3.11, 3.0 , 3.0-staging, 2.22-staging, all win32 arch and encountered same problem.

Several other games on wine works normally.

Linux mint 19, kernel from https://github.com/M-Bab/linux-kernel-amdgpu-binaries, Mesa stable from padoka.

Code: Select all

System:    Host: MintHome Kernel: 4.17.2amdgpu.ubuntu.18.06.19+ x86_64
           bits: 64 gcc: 7.3.0
           Desktop: Cinnamon 3.8.7 (Gtk 3.22.30-1ubuntu1)
           Distro: Linux Mint 19 Tara

Graphics:  Card: Advanced Micro Devices [AMD/ATI] Curacao XT / Trinidad XT [Radeon R7 370 / R9 270X/370X]
           bus-ID: 01:00.0
           Display Server: x11 (X.Org 1.19.6 )
           drivers: ati,amdgpu (unloaded: modesetting,fbdev,vesa,radeon)
           Resolution: [email protected]
           OpenGL: renderer: AMD Radeon HD 8800 Series (PITCAIRN, DRM 3.26.0, 4.17.2amdgpu.ubuntu.18.06.19+, LLVM 6.0.0)
           version: 4.5 Mesa 18.1.3 - padoka PPA 
User avatar
DarkShadow44
Level 8
Level 8
Posts: 1207
Joined: Tue Nov 22, 2016 5:39 pm

Re: Linux mint 19 Internal error ppy.y 387

Post by DarkShadow44 »

Related to https://bugs.winehq.org/show_bug.cgi?id=44773, though it's a slightly different log message. However, the games might share an engine.
slavikgenes
Newbie
Newbie
Posts: 3
Joined: Tue Jul 10, 2018 2:32 am

Re: Linux mint 19 Internal error ppy.y 387

Post by slavikgenes »

As proposed in Bug 44773 installing a native d3dcompiler_43 (through winetricks in my case) solves a problem.
Locked