League of Legends congela após entrar como usuário no launcher

Olá comunidade Manjaro!

Venho tentando entrar em minha conta do LoL já faz algum tempo, porém toda vez que entro com meus dados no launcher ele congela naquele retângulo preto (que geralmente fica no lugar da logo do League of Legends).

Abaixo estão as infos do sistema e hardware:

inxi -Fazzy
System:
Kernel: 5.10.32-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10-x86_64
root=UUID=4237b0b2-3f6a-4eef-9520-9f16bd2e9731 rw quiet
resume=UUID=750784bc-47f5-4650-a8c1-a94cc8e35d47 udev.log_priority=3
Desktop: KDE Plasma 5.21.4 tk: Qt 5.15.2 wm: kwin_x11 vt: 2 dm: SDDM
Distro: Manjaro Linux base: Arch Linux
Machine:
Type: Laptop System: Hewlett-Packard product: HP Pavilion 15 Notebook PC
v: 0883100000305B10000620100 serial: Chassis: type: 10
serial:
Mobo: Hewlett-Packard model: 1982 v: 01.16 serial: UEFI: Insyde
v: F.39 date: 03/24/2017
CPU:
Info: Quad Core model: AMD A8-5550M APU with Radeon HD Graphics bits: 64
type: MCP arch: Piledriver family: 15 (21) model-id: 13 (19) stepping: 1
microcode: 6001119 cache: L2: 2 MiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
bogomips: 16767
Speed: 1326 MHz min/max: 1400/2100 MHz boost: enabled Core speeds (MHz):
1: 1326 2: 1285 3: 1228 4: 1363
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Full AMD retpoline, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Richland [Radeon HD 8550G] vendor: Hewlett-Packard
driver: radeon v: kernel bus-ID: 00:01.0 chip-ID: 1002:990d class-ID: 0300
Device-2: Suyin HP Truevision HD type: USB driver: uvcvideo bus-ID: 2-4:2
chip-ID: 064e:e266 class-ID: 0e02 serial:
Display: x11 server: X.Org 1.20.11 compositor: kwin_x11 driver:
loaded: ati,radeon unloaded: modesetting alternate: fbdev,vesa
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.2x8.0")
s-diag: 414mm (16.3")
Monitor-1: eDP res: 1366x768 hz: 60 dpi: 101 size: 344x194mm (13.5x7.6")
diag: 395mm (15.5")
OpenGL: renderer: AMD ARUBA (DRM 2.50.0 / 5.10.32-1-MANJARO LLVM 11.1.0)
v: 4.3 Mesa 21.0.3 compat-v: 3.1 direct render: Yes
Audio:
Device-1: AMD Trinity HDMI Audio vendor: Hewlett-Packard
driver: snd_hda_intel v: kernel bus-ID: 00:01.1 chip-ID: 1002:9902
class-ID: 0403
Device-2: AMD FCH Azalia vendor: Hewlett-Packard driver: snd_hda_intel
v: kernel bus-ID: 00:14.2 chip-ID: 1022:780d class-ID: 0403
Sound Server-1: ALSA v: k5.10.32-1-MANJARO running: yes
Sound Server-2: JACK v: 0.125.0 running: no
Sound Server-3: PulseAudio v: 14.2 running: yes
Sound Server-4: PipeWire v: 0.3.26 running: yes
Network:
Device-1: Realtek RTL8188EE Wireless Network Adapter vendor: Hewlett-Packard
driver: rtl8188ee v: kernel port: 3000 bus-ID: 02:00.0 chip-ID: 10ec:8179
class-ID: 0280
IF: wlo1 state: up mac:
Device-2: Realtek RTL810xE PCI Express Fast Ethernet vendor: Hewlett-Packard
driver: r8169 v: kernel port: 2000 bus-ID: 05:00.0 chip-ID: 10ec:8136
class-ID: 0200
IF: eno1 state: down mac:
Drives:
Local Storage: total: 698.64 GiB used: 99.1 GiB (14.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: MQ01ABD075
size: 698.64 GiB block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s
rotation: 5400 rpm serial: rev: 1C scheme: GPT
Partition:
ID-1: / raw-size: 689.54 GiB size: 677.72 GiB (98.29%)
used: 99.1 GiB (14.6%) fs: ext4 dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 312 KiB (0.1%) fs: vfat dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/sda3 maj-min: 8:3
Sensors:
System Temperatures: cpu: 47.2 C mobo: N/A gpu: radeon temp: 47.0 C
Fan Speeds (RPM): N/A
Info:
Processes: 186 Uptime: 26m wakeups: 1 Memory: 6.98 GiB
used: 1.55 GiB (22.2%) Init: systemd v: 247 tool: systemctl Compilers:
gcc: 10.2.0 Packages: pacman: 1629 lib: 473 flatpak: 0 Shell: Bash v: 5.1.0
running-in: konsole inxi: 3.3.04

E aqui o log do Wine quando tento lançar o League of Legends:

lutris-wrapper: League of Legends
Running /home/salinger/.local/share/lutris/runners/wine/lutris-lol-5.5-2-x86_64/bin/wine /home/salinger/Games/league-of-legends/drive_c/Riot Games/League of Legends/LeagueClient.exe --locale=en_US
Initial process has started with pid 3597
Start monitoring process.
000000.001| OKAY| Running from cwd ‘C:\Riot Games\League of Legends’.
000000.001| ALWAYS| Application Version:11.9.372.2066 - CL:3722066 - Build Date:Apr 23 2021 - Build Time:10:27:45
000000.002| OKAY| Initial working directory: “C:\Riot Games\League of Legends”
000000.003| OKAY| Current process: “C:\Riot Games\League of Legends\LeagueClient.exe”
000000.003| OKAY| Command line arguments:
–locale=en_US
000000.007| OKAY| Enabling Data API Dradis collection with endpoint: https://ekg.riotgames.com/messages
000000.023| ALWAYS| The following message is prepared to be sent to dradis:
Event Name: riot__rclient__event
common.os_platform: Windows
common.application_name: LeagueClient
common.application_version: 11.9.372.2066
common.cef_version: 74.1.19+gb62bacf+chromium-74.0.3729.157
common.installation_id: aJ2g0w==
common.locale: en_US
common.os_version_major: 10
common.machine_id: 9rNUPvANnU2QovFlgNAnLw==
common.os_edition: Ultimate N, x86
common.os_version_minor:
common.region: BR
common.session_id: 413402ed-edc9-1849-a24d-7dbdfd76cdee
event_name: startup
crash_reporter: crashpad
000000.023| ALWAYS| Queued Dradis event to be sent.
000000.023| ALWAYS| Direct Launch enabled for league_of_legends.live in environment ‘live’ for app path ‘C:\Riot Games\League of Legends\LeagueClient.exe’ and install dir ‘C:\Riot Games\League of Legends’
000000.024| ALWAYS| Found associated Riot Client install (c:/Riot Games/Riot Client/RiotClientServices.exe)
000000.154| OKAY| Launched Riot Client with process 57
000000.154| ALWAYS| Riot Client started. Exiting with the expectation of being restarted (ExitForDirectLaunch).
000005.887| OKAY| EventCollector: 0 events remaining after thread join
000005.887| OKAY| Shut down EventCollector in 863 milliseconds
Initial process has exited (return code: 0)

Caso precisem que seja feito algum teste extra ou algum outro passo é só me falar que faço e posto os resultados aqui.

Olá!
Encontrei isto no site do Lutris na página sobre o LOL:

Retirado da página mencionada acima
  • Do not connect or launch game during setup, close the client once it finished download
  • This installer is international, the game will be available in your native language after install
  • The game will take a lot of time to launch, after login you will obtain a black rectangle during several minutes. So… wait.
  • If your cursor does not show correct icon, switch to the “Interface” settings and turn the Legacy cursor to “off” and “on”
  • You need to install these packages before launching this installer: zenity, openssl

Segundo o que a página do Lutris sobre o LOL diz, infelizmente, este sintoma é normal (Traduzindo o que eu marquei como negrito, “O jogo vai levar muito tempo para abrir, depois de logar você vai ter um retângulo preto por minutos. Então… espere.” ), e o processo demora mesmo.

Tente fazer isto enquanto faz outras coisas, e se em até… uma hora? Chuto que em menos de uma hora ele descongela, mas… se em até uma hora nada mudar na sua tela do LOL, responda o tópico.

Abraços! Espero que isso tenha te respondido, sofrer é uma sina de nós, usuários de Linux, mas no final vale a pena!

1 Like