Closed mortenfc closed 1 year ago
works fine here, tested on both fedora and popos
I have same problem on pop os 22.04 Perhaps a 22.04 ubuntu thing.
There is a problem with the latest wine build and zenity on Ubuntu/Pop 22.04. See: https://github.com/lutris/lutris/issues/4231#issuecomment-1110375795
Can confirm this on my system as well, running Ubuntu 22.04. I have to manually run syscall_check.sh
Make sure to check your path. In my case after some debugging it turned out my script was called, but the file I was attempting to delete resided in "Games" and my path was "games". In linux pathnames are case-sensitive, whereas windows isn't (at least, by default it isnt).
Have this issue on ubuntu 22.04 as well.
You can't be having the same issue because the prelaunch script was completely removed from the installer several months ago due to the fix for the issue being patched directly in wine. I'd recommend performing a clean install if you haven't. As noted there is -no longer- a prelaunch script, it was removed several months ago:
files:
- lol_installer: https://lol.secure.dyn.riotcdn.net/channels/public/x/installer/current/live.na.exe
game:
args: --locale=$INPUT_LOCALE --launch-product=league_of_legends --launch-patchline=live
exe: $GAMEDIR/drive_c/Riot Games/Riot Client/RiotClientServices.exe
prefix: $GAMEDIR
installer:
- input_menu:
description: 'Choose your preferred game''s language:'
id: LOCALE
options:
- cs_CZ: "\u010Ce\u0161tina"
- en_AU: English AUS
- en_GB: English U.K.
- en_US: English U.S.
- fr_FR: "Fran\xE7ais"
- de_DE: Deutsch
- es_ES: "Espa\xF1ol"
- es_MX: "Espa\xF1ol Mexicano"
- it_IT: Italiano
- ja_JP: "\u65E5\u672C\u8A9E"
- hu_HU: Magyar
- pl_PL: Polski
- pt_BR: "Portugu\xEAs do Brasil"
- ro_RO: Romanian
- ru_RU: "\u0440\u0443\u0441\u0441\u043A\u0438\u0439"
- tr_TR: "T\xFCrk\xE7e"
preselect: en_US
- task:
description: Creating Wine prefix
name: create_prefix
prefix: $GAMEDIR
- task:
args: $lol_installer
description: Do not log in during installation, just close the installation client
once it finishes downloading.
executable: $GAMEDIR/drive_c/windows/explorer.exe
include_processes: explorer.exe
name: wineexec
- task:
name: winekill
prefix: $GAMEDIR
- task:
key: GrabFullScreen
name: set_regedit
path: HKEY_CURRENT_USER\Software\Wine\X11 Driver
prefix: $GAMEDIR
value: Y
- task:
key: background
name: set_regedit
path: HKEY_CURRENT_USER\Control Panel\Colors\
prefix: $GAMEDIR
type: REG_SZ
value: 40 40 40
system:
env:
DXVK_LOG_LEVEL: none
DXVK_STATE_CACHE_PATH: $GAMEDIR
STAGING_SHARED_MEMORY: 1
WINE_LARGE_ADDRESS_AWARE: 1
__GL_SHADER_DISK_CACHE: 1
__GL_SHADER_DISK_CACHE_PATH: $GAMEDIR
wine:
MouseWarpOverride: enable
version: lutris-ge-lol-7.0-5-x86_64
Just because the application doesn't set a prelaunch script by default anymore doesn't say it's not possible to configure a prelaunch script.
League is having some issues lately where the cache files are causing client freezes / black screens when loading into the rift. Thus I added a prelaunch script that removes the cache files every time I launch league.
However, I updated my comment as after some debugging I found what was causing my problem.
EDIT: I also didn't know it used to have a prelaunch script, I only recently started playing league again. Guess that didn't help with the confusion here.
@xorinzor This is a problem with the library versions in PoP-OS / Ubuntu 22.04, and was posted back when LoL was dependant on a pre-launch script to set a syscall value. AFAIK it has still not been fixed.
Nope, still not fixed. Confirmed on Pop-OS.
The prelaunch script should no longer be needed on current version of wine
Bug description
Atleast for my setup, using app leagueoflegends , the pre-launch script created in
~/Games/league-of-legends/syscall_check.sh
does not execute.What I tried:
./syscall_check.sh
,The script works when running it manually. The game works flawlessly (I'm impressed), as long as
pkexec sh -c 'echo "abi.vsyscall32 = 0" >> /etc/sysctl.conf && sysctl -p'
has been executed manually.How to Reproduce
Steps to reproduce the behavior:
cat /proc/sys/abi/vsyscall32
does not return 0.Expected behavior
The pre-launch script should run...
Log output
System Information
Media (optional)
No response
Checklist: