I followed all the instructions but I can't log in. I unchecked the peer to peer option in the launcher but every time I log in the program crashes. I looked at the debug log and I always get the same error: Code: wine: Unhandled page fault on write access to 0x630020c4 at address 0x77f77316 (thread 003e), starting debugger... I'm trying to run LOL version 3.14 in an openSUSE 13.1 distro with a Radeon X1550 graphic card. Any help?
I have a few questions first: Is openSUSE13.1 the 64-bit version? Did you install the AMD drivers for your Radeon X1550? Can you paste the entire debug starting with the date and everything below? Peer-to-Peer setting seems to only affect some installs. I've seen many different symptoms and bugs for League of Legends on the PlayOnLinux forums. Some can't login, others get a crash when clicking the store...
1. It's the 32-bit version. 2. I have the radeon driver intalled not the proprietary one. 3. Code: [12/11/13 00:14:25] - Running wine-1.7.8 lol.launcher.admin.exe (Working directory : /home/jfons/.PlayOnLinux/wineprefix/leagueoflegends/drive_c/Riot Games/League of Legends) fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33f918 1 C) semi-stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33f758 1 C) semi-stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33f8c4 1 C) semi-stub fixme:ntdll:NtConnectPort (0x5b0c1170,L"\\ThemeApiPort",0x33fadc,(nil),(nil),(nil),0x33faec,0x33fae8),stub! fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot fixme:toolhelp:Heap32ListFirst : stub fixme:ver:GetCurrentPackageId (0x147e9f8 (nil)): stub fixme:win:EnumDisplayDevicesW ((null),0,0x33f748,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x33f744,0x00000000), stub! fixme:win:EnumDisplayDevicesW (L"\\\\.\\DISPLAY1",0,0x33f3fc,0x00000000), stub! fixme:d3d9:Direct3DShaderValidatorCreate9 stub fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:state_zenable Z buffer disabled, but ARB_depth_clamp isn't supported. fixme:d3d:swapchain_gl_present WINED3D_SWAP_EFFECT_FLIP not implemented. fixme:ntdll:NtConnectPort (0x5b0c1170,L"\\ThemeApiPort",0x33f4dc,(nil),(nil),(nil),0x33f4ec,0x33f4e8),stub! fixme:ntdll:RtlAcquireSRWLockShared 0x5de6b680 stub fixme:ntdll:RtlReleaseSRWLockShared 0x5de6b680 stub fixme:ntdll:RtlAcquireSRWLockShared 0x5de6b680 stub fixme:ntdll:RtlReleaseSRWLockShared 0x5de6b680 stub fixme:ntdll:RtlAcquireSRWLockShared 0x5de6b680 stub fixme:ntdll:RtlReleaseSRWLockShared 0x5de6b680 stub fixme:ntdll:RtlAcquireSRWLockExclusive 0x5de6b680 stub fixme:ntdll:RtlReleaseSRWLockExclusive 0x5de6b680 stub fixme:ntdll:RtlAcquireSRWLockExclusive 0x5de6b680 stub fixme:ntdll:RtlReleaseSRWLockExclusive 0x5de6b680 stub fixme:ntdll:RtlAcquireSRWLockShared 0x5de6b680 stub fixme:ntdll:RtlReleaseSRWLockShared 0x5de6b680 stub fixme:ntdll:RtlAcquireSRWLockShared 0x5de6b680 stub fixme:ntdll:RtlReleaseSRWLockShared 0x5de6b680 stub fixme:ntdll:RtlAcquireSRWLockShared 0x5de6b680 stub fixme:ntdll:RtlReleaseSRWLockShared 0x5de6b680 stub fixme:ntdll:RtlAcquireSRWLockShared 0x5de6b680 stub fixme:ntdll:RtlReleaseSRWLockShared 0x5de6b680 stub fixme:ntdll:RtlAcquireSRWLockExclusive 0x5de6b680 stub fixme:ntdll:RtlReleaseSRWLockExclusive 0x5de6b680 stub fixme:ntdll:RtlAcquireSRWLockExclusive 0x5de6b680 stub fixme:ntdll:RtlReleaseSRWLockExclusive 0x5de6b680 stub fixme:ntdll:RtlAcquireSRWLockShared 0x5de6b680 stub fixme:ntdll:RtlReleaseSRWLockShared 0x5de6b680 stub 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. fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046} fixme:lsa:LsaGetLogonSessionData 0x33e3a8 0x33e3b8 stub fixme:win:EnumDisplayDevicesW ((null),0,0x33e6d8,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x33d7bc,0x00000000), stub! fixme:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request: stub fixme:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request: stub fixme:imm:ImmReleaseContext (0x1006e, 0x330dab0): stub wine: Unhandled page fault on write access to 0x630020c4 at address 0x77f77316 (thread 0036), starting debugger... err:dbghelp:pe_load_dbg_file Couldn't find .DBG file "dll\\wininet.dbg" ("\xf0\xe3?\xb7\x01\x80\xad\xfb \xc53") That's it, thanks for the help.
I noticed in the above log I was using wine version 1.7.8 but the same happens when using 1.6-rc4 or 1.5.24-LeagueOfLegendsShop.
Is a very common problem when runing LoL on Linux with Wine or PlayOnLinux There are some long posts on the PlayOnLinux forum about them. I even got the error too. Since you followed my guide that means you set Windows version as Windows XP and installed Internet Explorer 8. Did you install wininet library? Somehow dbghelp is associated with wininet Also, someone mentioned that installing AMD's proprietary 13.10 beta 2 driver fixed the problem for them. You could try that also.
Ok I did some research and I found out the AMD proprietary drivers don't support my graphic card so I don't know what to do. If you don't have any other suggestion I'll just leave it. Thanks for your help anyway.
Do you have a laptop? If thats the case, then yes... might as well try a different game. I have a desktop just for gaming because it has a dedicated video card and I can upgrade later on when games get more demanding. I have an Acer C7 Chromebook running ChUbuntu and it will play a few games. Mostly older ones, but it can play Torchlight. I'm pretty sure it won't play League of Legends because it only has an Intel HD 2000 video chip. So I have to just take what I can.
