search

kyechou / leagueoflegends

League of Legends install and launch wrapper for Linux
https://www.leagueoflegends.com
GNU General Public License v3.0
290 stars 23 forks source link

Cannot get into a game #83

Closed Gruetzig closed 1 year ago

Gruetzig commented 1 year ago

System information

If your issue is related to graphics display, please attach the output of vulkaninfo --summary. I do not know if it is, but I included vulkaninfo --summary in my pastebin.

Describe the issue

When starting the game, not the launcher, it immediately crashes with an error I attached below, tried both ranked(bruh) and practice tool.

Reinstalled twice with no luck, worked just fine yesterday, never used the lutris version.

Steps to reproduce

https://pastebin.com/BS7yBiru pastebin with vulkaninfo --summary and leagueoflegends -v start

  1. Run command leagueoflegends -v start
  2. Go into a game
  3. See critical error

Screenshots

image

ExistingExpert commented 1 year ago

Check out these threads: https://www.reddit.com/r/leagueoflinux/comments/12c8w4p/last_patch_did_it_again/ https://www.reddit.com/r/leagueoflinux/comments/12cbqeq/update_of_leagueoflegendsgit_script_and_the_aur/ https://old.reddit.com/r/leagueoflinux/comments/12cei7t/patch_137_feedback_megathread_transition_to_64bit/

ademblon commented 1 year ago

I just installed kyechou version. (I'm usually using lutris, but I need a working version of lol asap, for a tournament)

I also have the same issues, and many others too as you can see in the second and third link you sent.

My error is 0328:err:seh:dispatch_exception unknown exception (code=c0000420) raised

I also have the error X11DRV_vkCreateWin32SurfaceKHR Failed to allocate client window but I don't know if it's related. This one appears when starting the client, not when starting a game.

Gruetzig commented 1 year ago

@ExistingProgrammer Its nice to see that Im not alone, but why should I check these out? I dont see a solution there, please link a specific comment if I overlooked it.

ceselder commented 1 year ago

Exactly the same issue. version 13.7.1 as well

kyechou commented 1 year ago

@Gruetzig, what's the package version of leagueoflegends-git were you using? Have you tried reinstall league?

kyechou commented 1 year ago

@Gruetzig , @ademblon , @ceselder Also could you run leagueoflegends run which wine and share the output?

ceselder commented 1 year ago

image

ceselder commented 1 year ago

Some people over in the reddit thread have replicated it using the wine-lol package instead of wine-lol-bin.

ceselder commented 1 year ago

@kyechou Can you actually get into game? I have seen noone been able to get into game in any of the reddit threads.

pierrepas commented 1 year ago

I have the same issue even after a fresh install, and the same output for "run which wine" than @ceselder . I get the critical error whenever joining a LoL or TFT game, and it was working fine yesterday, so it is due to the 13.7 update.

salova322 commented 1 year ago

@pierrepas yea same

Gruetzig commented 1 year ago

@Gruetzig, what's the package version of leagueoflegends-git were you using? Have you tried reinstall league?

local/leagueoflegends-git 13.7.1.r0.gfb60c87-1

Gruetzig commented 1 year ago

Like I said, I have tried reinstalling league, but I will try reinstalling once more, wine is also in /opt/wine-lol/bin/wine

Gruetzig commented 1 year ago

reinstalled, same issue, https://pastebin.com/z8AQdbcT log if you need

Gruetzig commented 1 year ago

forgot to do verbose for installing, I can redo with that option if needed.

Bqleine commented 1 year ago

I'm also experiencing this issue after doing a fresh install with wine-lol 7.0.5 manually.

foxyllakora commented 1 year ago

Here is the error I'm getting when the game tries to load in after champ select: 02f0:err:seh:dispatch_exception unknown exception (code=c0000420) raised

That's the only error that shows up using leagueoflegends -v start

OS: EndeavourOS CPU: Ryzen 9 5950x GPU: AMD XFX 6950XT Mobo: ASUS TUF Gaming X570-Plus Ram: G.Skill DDR4 32GB

FlashOnFire commented 1 year ago

Same error as above Arch Linux 6.2.9-arch1-1 Intel Core i5-11400 Nvidia RTX 3060 TI

09ec:err:seh:dispatch_exception unknown exception (code=c0000420) raised

The client works well but i can't get into a game

ademblon commented 1 year ago

image

Exact same for me

Yuanhao-JIANG commented 1 year ago

same issue here, OS: EndeavourOS Linux x86_64 Kernel: 6.2.9-arch1-1 Resolution: 3840x2160 DE: Plasma 5.27.3 WM: kwin CPU: 11th Gen Intel i7-11700K (16) @ 4.900GHz GPU: NVIDIA GeForce RTX 3080 Ti

courgette650 commented 1 year ago

Same here , happens as well with lutris installer wine-ge-lol-5.0-5 Also, I just reinstalled manjaro here. Went from kernel 5.15.104-2 to 6.1.8-1. It was working perfectly fine before reinstalling/upgrading. Don't really know if that could be a problem :/

OS: Manjaro 22.1.0 Talos Kernel: x86_64 Linux 6.1.21-1-MANJARO DE: GNOME 43.5 WM: Mutter CPU: AMD Ryzen 5 2600 Six-Core @ 12x 3.4GHz GPU: NVIDIA GeForce RTX 3060 Ti

kyechou commented 1 year ago

Hi all, thanks for sharing the system and logging information!

Yes, I can reproduce the error as of this morning. And as mentioned by previous comments and logs, this exception is where the game executable fails.

err:seh:dispatch_exception unknown exception (code=c0000420) raised

The issue is confirmed. And it'd be nice to also have people who are more familiar with Wine than I am looking into it.

PalanixYT commented 1 year ago

It's not worth looking into because it's probably a problem on Riot's end and WINE just so happens to be able to trigger it perfectly

kyechou commented 1 year ago

Thanks @PalanixYT! That's good to know.

noah1510 commented 1 year ago

Hi all, thanks for sharing the system and logging information!

Yes, I can reproduce the error as of this morning. And as mentioned by previous comments and logs, this exception is where the game executable fails.

err:seh:dispatch_exception unknown exception (code=c0000420) raised

The issue is confirmed. And it'd be nice to also have people who are more familiar with Wine than I am looking into it.

I can confirm this behavior using my wrapper script on kubuntu 22.10 (See #82) using lutris-wine-ge-7.0-5.

s-b-repo commented 1 year ago

same here on fedora

ghost commented 1 year ago

same on void: OS: Void Linux x86_64 Kernel: 6.1.21_1 AMD ATI Radeon RX 7900 XT AMD Ryzen 5 7600X (12) Throwing this in there. I was concerned it was due to my new hardware. Maybe this will make this issue searchable with similar hardware. :)

s-b-repo commented 1 year ago

tryed new release on fedora

memand commented 1 year ago

Here's the mem dump if anyone would find that useful..

https://kulturforeningenkasimir.dk/nextcloud/s/LoAJox6cdra4idM

BlankSpruce commented 1 year ago

OS: Manjaro DE: KDE CPU: i5-8300H GPU: GTX 1650 Graphics cad drivers: nvidia

Logs collected with WINEDEBUG=+seh+relay+tid related to League of Legends.exe:

0a44:fixme:heap:EnumSystemFirmwareTables (0x4649524d, 0000000000000000, 0)
0a44:err:seh:dispatch_exception unknown exception (code=c0000420) raised
0a44:fixme:process:NtQueryInformationProcess ProcessCookie (0xffffffffffffffff,0x180b30650,0x00000004,(nil)) stub
0a44:fixme:thread:NtSetInformationThread info class 2 not supported yet
0a44:fixme:imm:ImeSetActiveContext (0x3003d0, 1): stub
0a44:fixme:imm:ImmReleaseContext (0000000000020114, 00000000003003D0): stub

The error code (0xc0000420) is related to assertion failure Given that:

it's reasonable to assume that the assertion failure comes due to some recent changes in LOL code. It just so happens that in Wine environment it's easier to fail that mysterious assertion. I'm looking forward to next couple of days since it's possible that there will be some patch to LOL itself to mitigate issue for Windows users at least.

arnaudelub commented 1 year ago 
OS: Manjaro Linux x86_64 
██████████████████  ████████   Host: MS-7B18 1.0 
████████            ████████   Kernel: 5.15.104-2-MANJARO 
████████  ████████  ████████   Uptime: 1 hour, 33 mins 
████████  ████████  ████████   Packages: 1539 (pacman), 5 (flatpak), 3 (snap) 
████████  ████████  ████████   Shell: zsh 5.9 
████████  ████████  ████████   Resolution: 1920x1200, 3840x1600, 1920x1080 
████████  ████████  ████████   DE: GNOME 43.4 
████████  ████████  ████████   WM: Mutter 
████████  ████████  ████████   WM Theme: CustomAccentColors 
████████  ████████  ████████   Theme: Adw-dark [GTK2/3] 
████████  ████████  ████████   Icons: Papirus-Dark-Maia [GTK2/3] 
                               Terminal: terminator 
                               CPU: Intel i9-9900K (16) @ 5.000GHz 
                               GPU: NVIDIA GeForce RTX 2070 
                               Memory: 2079MiB / 64244MiB

same here, with the exact same error. Using lutris with Wine version Lutris-ge-lol-7.0.5-x86_64

leobortolini commented 1 year ago

Same issue here

OS: Zorin OS 16.2 x86_64 Kernel: 5.15.0-69-generic CPU: Intel i7-9750H (12) @ 4.500GHz GPU: NVIDIA GeForce GTX 1660 Ti Mobile wine-8.0 lutris-ge-lol-7.14-1-x86_64

sekwah41 commented 1 year ago

From what I can see it seems to be happening to everyone, is there anyone or does anyone know anyone that this isn't occurring to? Just mentioning this to make sure there isn't a flood of people just saying "doesn't work" with duplicate info.

dykensp commented 1 year ago

same error as OP screenshot through Heroic game launcher + Wine-7.0-GE-5-LoL, was working until todays small lol update

ceselder commented 1 year ago

From what I can see it seems to be happening to everyone, is there anyone or does anyone know anyone that this isn't occurring to? Just mentioning this to make sure there isn't a flood of people just saying "doesn't work" with duplicate info.

I'm 99% sure its working for literally noone on linux

ExistingExpert commented 1 year ago

From what I can see it seems to be happening to everyone, is there anyone or does anyone know anyone that this isn't occurring to? Just mentioning this to make sure there isn't a flood of people just saying "doesn't work" with duplicate info.

I'm 99% sure its working for literally noone on linux

Yup, and it is crashing on windows too with the exact same error. We just have to wait till riot fixes it.

BlankSpruce commented 1 year ago

Riot seems to be aware of the problem: https://old.reddit.com/r/leagueoflegends/comments/12c7qkl/patch_137_bug_megathread/jf1wufh/

laqyx commented 1 year ago

DRIVER | LAYER: Using "AMD Radeon RX 5700 XT 50th Anniversary (RADV NAVI10)" with driver: "/usr/lib32/libvulkan_radeon.so" 06e0:err:vulkan:X11DRV_vkCreateWin32SurfaceKHR Failed to allocate client window for hwnd=0x200f0 0310:err:seh:dispatch_exception unknown exception (code=c0000420) raised

sadly crashing here too

s-b-repo commented 1 year ago

I've been getting the same error 0158:err:seh:dispatch_exception unknown exception (code=c0000420) raised. But what happens just before is that it fails because the amdvlk switchable graphics is the wrong elf class (64bits), then after the error it prints the call stack and unloads amdvlk. And then it prints the seh error: log paste

I don't know enough about wine , so I'm still trying to figure out why is it getting this error, seems like is trying to execute the 64 bit version of amdvlk when expecting 32 bit. And is the same error as the original post of the issue just one is using libvulkan_radeon and the other amdvlk64

the error message indicates that an exception with code "c0000420" was raised and not handled by the SEH mechanism. The SEH mechanism is used by the Windows operating system to manage exceptions and errors in programs. However, without more context, it's difficult to determine the exact cause of this error. It could be related to a problem with Wine, the application being run, or the system environment.

s-b-repo commented 1 year ago

DRIVER | LAYER: Using "AMD Radeon RX 5700 XT 50th Anniversary (RADV NAVI10)" with driver: "/usr/lib32/libvulkan_radeon.so" 06e0:err:vulkan:X11DRV_vkCreateWin32SurfaceKHR Failed to allocate client window for hwnd=0x200f0 0310:err:seh:dispatch_exception unknown exception (code=c0000420) raised

sadly crashing here too

The error message suggests that there is an issue with creating a client window for the Vulkan-based graphics API. Specifically, it seems that there was a failure to allocate a client window for the specified window handle. Additionally, there is a separate error related to an unknown exception being raised with code c0000420.

s-b-repo commented 1 year ago

Logs collected with WINEDEBUG=+seh+relay+tid related to League of Legends.exe:

0a44:fixme:heap:EnumSystemFirmwareTables (0x4649524d, 0000000000000000, 0)
0a44:err:seh:dispatch_exception unknown exception (code=c0000420) raised
0a44:fixme:process:NtQueryInformationProcess ProcessCookie (0xffffffffffffffff,0x180b30650,0x00000004,(nil)) stub
0a44:fixme:thread:NtSetInformationThread info class 2 not supported yet
0a44:fixme:imm:ImeSetActiveContext (0x3003d0, 1): stub
0a44:fixme:imm:ImmReleaseContext (0000000000020114, 00000000003003D0): stub

This log appears to be generated by a Windows application or process. It indicates that an unknown exception with error code c0000420 was raised, which could potentially indicate a critical system error. Additionally, there are several fixme messages which suggest that certain features or functions are not yet fully implemented or supported in the current version of the software.

The first line of the log, "EnumSystemFirmwareTables", appears to be related to enumerating firmware tables in the system, although it is unclear what specific action or purpose triggered this call. The subsequent lines, including the exception and fixme messages, suggest that the application or process may be encountering issues related to memory management, thread information, and input method editor (IME) context activation and release.

Without further context or analysis of the software and system environment in which this log was generated, it is difficult to determine the root cause of these errors and their potential impact on the system. However, it is clear that there are several areas of the software that require further development and debugging to ensure stable and reliable operation.

s-b-repo commented 1 year ago

I just installed kyechou version. (I'm usually using lutris, but I need a working version of lol asap, for a tournament)

I also have the same issues, and many others too as you can see in the second and third link you sent.

My error is 0328:err:seh:dispatch_exception unknown exception (code=c0000420) raised

I also have the error X11DRV_vkCreateWin32SurfaceKHR Failed to allocate client window but I don't know if it's related. This one appears when starting the client, not when starting a game.

The first error is related to Vulkan, a graphics API. The error message indicates that the function "vkCreateWin32SurfaceKHR" failed to allocate a client window for the specified window handle. This error could occur due to a variety of reasons such as incorrect usage of Vulkan functions or issues with the window system.

The second error is related to structured exception handling (SEH), which is a mechanism for handling errors in Windows programs. The error message indicates that an unknown exception with error code "c0000420" was raised, which could indicate an access violation or other type of memory error.

Without more context or information, it is difficult to determine the exact cause of these errors. However, potential solutions could involve checking the code that uses Vulkan functions for errors or debugging memory issues in the program using a tool such as a debugger.

PalanixYT commented 1 year ago

Like I and @BlankSpruce have mentioned before, it's a problem on Riot's end.

s-b-repo commented 1 year ago

Like I and @BlankSpruce have mentioned before, it's a problem on Riot's end.

X11DRV_vkCreate "Win32" SurfaceKHR

win 32 is for 32 bit which they just depracted

PalanixYT commented 1 year ago

X11DRV_vkCreate "Win32" SurfaceKHR win 32 is for 32 bit which they just depracted

That may be the case but it's still a problem on Riot's end https://old.reddit.com/r/leagueoflegends/comments/12c7qkl/patch_137_bug_megathread/jf1wufh/

s-b-repo commented 1 year ago

X11DRV_vkCreate "Win32" SurfaceKHR win 32 is for 32 bit which they just depracted

That may be the case but it's still a problem on Riot's end https://old.reddit.com/r/leagueoflegends/comments/12c7qkl/patch_137_bug_megathread/jf1wufh/

yeah they dont support 32 bit anymore i read it hopefully they rollback the update

zexa commented 1 year ago

There's an interesting post that might help in the league of legends reddit: https://old.reddit.com/r/leagueoflegends/comments/12det14/found_a_fix_for_the_critical_error_crash_so_far/

Funestia commented 1 year ago

It seems to be related. If you enable window mode, while you still can't play a game, wine no longer displays a crash message. Edit: Sometimes it still does.

BlankSpruce commented 1 year ago

I've checked the "Restore defaults" hint that appeared on subreddit and while it doesn't make game playable in any manner seemingly it MIGHT HAVE affected something. In particular, not all League of Legends.exe starts lead to known error. Some either immediately terminate application (no "critical error" dialog) or leave process in zombie state that needs to be manually killed. Out of couple tries I've collected these various logs:

0534:fixme:heap:EnumSystemFirmwareTables (0x4649524d, 0000000000000000, 0)
0534:err:seh:dispatch_exception unknown exception (code=c0000420) raised
0534:fixme:process:NtQueryInformationProcess ProcessCookie (0xffffffffffffffff,0x180b01650,0x00000004,(nil)) stub
0534:err:seh:call_stack_handlers invalid frame 0000000000116BA9 (0000000000022000-0000000000120000)
0534:err:seh:NtRaiseException Exception frame is not in stack limits => unable to dispatch exception.
11fc:fixme:heap:EnumSystemFirmwareTables (0x4649524d, 0000000000000000, 0)
11fc:err:seh:dispatch_exception unknown exception (code=c0000420) raised
11fc:fixme:process:NtQueryInformationProcess ProcessCookie (0xffffffffffffffff,0x180b01650,0x00000004,(nil)) stub
11fc:err:virtual:virtual_setup_exception stack overflow 2384 bytes in thread 11fc addr 0x17005a229 stack 0x206b0 (0x20000-0x21000-0x120000)
0880:fixme:heap:EnumSystemFirmwareTables (0x4649524d, 0000000000000000, 0)
0880:err:seh:dispatch_exception unknown exception (code=c0000420) raised
0880:fixme:process:NtQueryInformationProcess ProcessCookie (0xffffffffffffffff,0x180b01650,0x00000004,(nil)) stub
0880:err:virtual:virtual_setup_exception nested exception on signal stack in thread 0880 addr 0x7f9ff1e459b7 stack 0x67fef3a0
0b30:fixme:heap:EnumSystemFirmwareTables (0x4649524d, 0000000000000000, 0)
0b30:err:seh:dispatch_exception unknown exception (code=c0000420) raised
0b30:fixme:process:NtQueryInformationProcess ProcessCookie (0xffffffffffffffff,0x180b01650,0x00000004,(nil)) stub
0b30:err:seh:NtRaiseException Unhandled exception code c0000005 flags 0 addr 0x141294666

These point to stack overflow and/or segfault kind of errors.

We could eliminate the possibility that "Restore defaults" has any impact at all here if someone tried multiple tries to see if some of the behaviours above are seen also without "Restore defaults". I honestly don't think it should matter at all having in mind that reinstallation should have exact same effect but truthfully before "Restore defaults" I had 100% ratio of appeareance of "Critical error" dialogs and none of the above logs.

s-b-repo commented 1 year ago

I've checked the "Restore defaults" hint that appeared on subreddit and while it doesn't make game playable in any manner seemingly it MIGHT HAVE affected something. In particular, not all League of Legends.exe starts lead to known error. Some either immediately terminate application (no "critical error" dialog) or leave process in zombie state that needs to be manually killed. Out of couple tries I've collected these various logs:

0534:fixme:heap:EnumSystemFirmwareTables (0x4649524d, 0000000000000000, 0)
0534:err:seh:dispatch_exception unknown exception (code=c0000420) raised
0534:fixme:process:NtQueryInformationProcess ProcessCookie (0xffffffffffffffff,0x180b01650,0x00000004,(nil)) stub
0534:err:seh:call_stack_handlers invalid frame 0000000000116BA9 (0000000000022000-0000000000120000)
0534:err:seh:NtRaiseException Exception frame is not in stack limits => unable to dispatch exception.
11fc:fixme:heap:EnumSystemFirmwareTables (0x4649524d, 0000000000000000, 0)
11fc:err:seh:dispatch_exception unknown exception (code=c0000420) raised
11fc:fixme:process:NtQueryInformationProcess ProcessCookie (0xffffffffffffffff,0x180b01650,0x00000004,(nil)) stub
11fc:err:virtual:virtual_setup_exception stack overflow 2384 bytes in thread 11fc addr 0x17005a229 stack 0x206b0 (0x20000-0x21000-0x120000)
0880:fixme:heap:EnumSystemFirmwareTables (0x4649524d, 0000000000000000, 0)
0880:err:seh:dispatch_exception unknown exception (code=c0000420) raised
0880:fixme:process:NtQueryInformationProcess ProcessCookie (0xffffffffffffffff,0x180b01650,0x00000004,(nil)) stub
0880:err:virtual:virtual_setup_exception nested exception on signal stack in thread 0880 addr 0x7f9ff1e459b7 stack 0x67fef3a0
0b30:fixme:heap:EnumSystemFirmwareTables (0x4649524d, 0000000000000000, 0)
0b30:err:seh:dispatch_exception unknown exception (code=c0000420) raised
0b30:fixme:process:NtQueryInformationProcess ProcessCookie (0xffffffffffffffff,0x180b01650,0x00000004,(nil)) stub
0b30:err:seh:NtRaiseException Unhandled exception code c0000005 flags 0 addr 0x141294666

These point to stack overflow and/or segfault kind of errors.

We could eliminate the possibility that "Restore defaults" has any impact at all here if someone tried multiple tries to see if some of the behaviours above are seen also without "Restore defaults". I honestly don't think it should matter at all having in mind that reinstallation should have exact same effect but truthfully before "Restore defaults" I had 100% ratio of appeareance of "Critical error" dialogs and none of the above logs.

its has to do with memory management and firmware

EnumSystemFirmwareTables enumarate sytem firmware tables

Structured Exception Handling

it points some memory or process in the code causing a issue some tpye of heap memory issue