Created attachment 38357 [details]
message when error happen

Created attachment 38358 [details]
pic of error

Comment on attachment 38357 [details]
message when error happen

>(WARNING)[20:01:08.521] RADS::API::Impl::Main::Main: User kernel is not running, proceeding without that functionality.
>(WARNING)[20:01:08.521] RADS::API::Impl::RuntimeEnvironment::RuntimeEnvironment: Did not find keywords "projects" or "solutions" in path
>(  DEBUG)[20:01:08.521] RADS::API::Impl::RuntimeEnvironment::GenerateFileMap: start building file map
>(  DEBUG)[20:01:08.521] RADS::API::Impl::RuntimeEnvironment::GenerateFileMap: done building file map
>(WARNING)[20:01:08.522] RADS::API::Impl::Main::Main: Could not determine solution or project runtime environment, execution will continue but all files will be treated as unmanaged in the current folder.
>fixme:win:EnumDisplayDevicesW ((null),0,0x33e51c,0x00000000), stub!
>fixme:win:EnumDisplayDevicesW ((null),0,0x33e42c,0x00000000), stub!
>fixme:ddraw:ddraw7_Initialize Ignoring guid {aeb2cdd4-6e41-43ea-941c-8361cc760781}.
>fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category {33d9a760-90c8-11d0-bd43-00a0c911ce86} not found
>fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category {33d9a761-90c8-11d0-bd43-00a0c911ce86} not found
>err:avicap:query_video_device Video 4 Linux support not enabled
>err:avicap:query_video_device Video 4 Linux support not enabled
>err:avicap:query_video_device Video 4 Linux support not enabled
>err:avicap:query_video_device Video 4 Linux support not enabled
>err:avicap:query_video_device Video 4 Linux support not enabled
>err:avicap:query_video_device Video 4 Linux support not enabled
>err:avicap:query_video_device Video 4 Linux support not enabled
>err:avicap:query_video_device Video 4 Linux support not enabled
>err:avicap:query_video_device Video 4 Linux support not enabled
>err:avicap:query_video_device Video 4 Linux support not enabled
>fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category {cc7bfb41-f175-11d1-a392-00e0291f3959} not found
>fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category {cc7bfb46-f175-11d1-a392-00e0291f3959} not found
>fixme:wbemprox:wbem_locator_ConnectServer 0x174418, L"ROOT\\CIMV2", (null), (null), (null), 0x00000000, (null), 0x0, 0x33fd40)
>err:ole:CoUninitialize Mismatched CoUninitialize

This is the exact part when things stop

Created attachment 38375 [details]
wine debugger message

about "League of legends.exe" & msvcr80.dll ?

Does native msvcr80 help? Or perhaps secur32?

(In reply to comment #6)
> Does native msvcr80 help? Or perhaps secur32?

replace msvcr80 -> same error
replace secur32 -> cant connect PvP.net

I have the same problem with wine 1.5.5. I compiled wine with gnutls3.

I have the same error, only that its from Arch Linux. Newest wine from git-repo

Thanks to a tip from lahmbi5678 this problem was solved for me. Please make sure that the output of 'hostname' (that is, your hostname) is in /etc/hosts. You can let it resolve to 127.0.0.1 or your internal ip address, either works. That is the usual configuration but sometimes this can go wrong. For example when you change your hostname without editing the hosts file.

Let's keep this bug open so other people with the same problem can find it. I believe wine should be able to help users even in spite of incorrect /etc/hosts configuration, as the hostname is still responds correctly to ping even if you don't have it in /etc/hosts

I guess
http://source.winehq.org/git/wine.git/commit/75be2284e13d327d93a9665eb32cd901cbed7234
wasn't quite a complete fix, then.

(In reply to comment #11)
> I guess
> http://source.winehq.org/git/wine.git/commit/75be2284e13d327d93a9665eb32cd901cbed7234
> wasn't quite a complete fix, then.

Maybe linux could benefit from the patches from this bug too:
http://bugs.winehq.org/show_bug.cgi?id=29756

More specifically this one:
http://source.winehq.org/patches/data/83394

I had this exact same error with same error messages.

Here is what I've done to fix it :

Edited my /etc/hosts and added the name of my PC (can sometimes be found on /etc/hostname) :
instead of : 127.0.0.1	localhost
now it is : 127.0.0.1	localhost nameofmymachine

It fixed the problem...

Is the problem coming from the way some windows components/the game itself are handling this ? Or is it a problem coming from the way wine handling this ?

(In reply to Someone from comment #13)

Please get a +winsock with and without hostname inside /etc/hosts

Created attachment 48513 [details]
winsock debug channel with game crashing without hostname set

> (In reply to Someone from comment #13)
> 
> Please get a +winsock with and without hostname inside /etc/hosts

Sadly, it seems I can't attach the other attachment because it's a tar.gz file and wine bugzilla doesn't seem to like it...

Created attachment 48514 [details]
winsock debug channel with game working with hostname set

(In reply to Bruno Jesus from comment #14)
> (In reply to Someone from comment #13)
> 
> Please get a +winsock with and without hostname inside /etc/hosts

Added as application/tgz, hoping it's supported

Both your logs show:

trace:winsock:WS_gethostname name 0x33fbb4, len 256
trace:winsock:WS_gethostname <- 'alexbox-64'

So I'm not sure you tested without a hostname.

(In reply to Bruno Jesus from comment #19)
> Both your logs show:
> 
> trace:winsock:WS_gethostname name 0x33fbb4, len 256
> trace:winsock:WS_gethostname <- 'alexbox-64'
> 
> So I'm not sure you tested without a hostname.

I'm 100 % sure of it.I did that test dozen of times. My /etc/hostname is always empty and as I explained when /etc/hosts doesn't have the hostname specified on the same line than loopback (127.0.0.1), it doesn't work but it works when I add it.

I did a lot of tests and I can reproduce that bug everytime.

Maybe some components of wine or LoL are looking for the hostname in that specific file (/etc/hosts/) and some others look somewhere else.That would explain why my hostname appears sometimes in some logs.

By the way if you look for 'league of legends crash 127.0.0.1" on a search engine, you'll find hundreds of results like this one :

http://www.playonlinux.com/fr/topic-10056-League_of_Legends_crash_after_champ_select.html

This bug exist from a long time and a lot of people know the workaround.

They only didn't post it here, that's the problem...

Ok, thanks for the explanation again. Now I see the problem in the log, I'll try to add some tests and find out what is happening.

Please try the patch from http://source.winehq.org/patches/data/83394

Created attachment 48574 [details]
patch

Forget my last comment, try this patch instead. It works for me, I'm starting to think that every distro should set the hostname inside /etc/hosts instead of delivering the burden to users. Fortunately debian already does that by setting the hostname to 127.0.1.1.

I've been fighting with this for a long time. Tonight I found something that worked for me, I dont know if it was the dx installation part or the dll override, but the ones having this bug should try it:

Install d3dx10, d3dx11, d3dx9, directx9
add and set the library "dnsapi" as (builtin,native)

Original post: http://www.playonmac.com/en/topic-11344.html

I have a quite similar error... when starting a match I only see a black screen with the cursor, then, after some seconds, LoL tells me I can reconnect, but doing so is useless.

I get a repeated

>err:d3dcompiler:compile_shader HLSL shader parsing failed.

error message.

I tried the solution in comment #13 but still this didn't work.

>err:d3dcompiler:compile_shader HLSL shader parsing failed.

Can only be fixed using some native override, not sure about the file. Maybe 43 compiler.dll

Hello folks,

refining summary and confirming on behalf of others.

A patch from Bruno is available in Wine-Staging here:

https://github.com/wine-compholio/wine-staging/blob/master/patches/ws2_32-getaddrinfo/0001-ws2_32-Try-harder-to-get-the-host-name-address-in-ge.patch

$ wine --version
wine-1.7.43-123-g90ed96a

Regards

Fixed by http://source.winehq.org/git/wine.git/?a=commit;h=18a02d8f41013aa8bf3cdd03750eb706ce52e58c

Closing bugs fixed in 1.7.52.