Closed xruifan closed 2 years ago
When the client start, manually run
pkexec sh -c 'sysctl -w abi.vsyscall32=0'
before you start a game, if it works for you I'll update the repo
It looks like everything works fine now. I am closing this issue and I think you could update this repo.
gotta say the performance was better than i expected.
I'm getting 200fps initially, now running 60fps stable at 1366x768, mid settings
you just gotta set the screen to boardless, else the mouse will move out of the window
just finished an ARAM round with Riven, gotta say the performance is really good, no lag at all.
But the keyboard works really weird though, when I press q sometimes it does not respond and sometimes it press 2 times.
But that kind of performance, I take it.
FOREVERLY LEAVE rubbish WINDOWS
just finished an ARAM round with Riven, gotta say the performance is really good, no lag at all.
But the keyboard works really weird though, when I press q sometimes it does not respond and sometimes it press 2 times.
But that kind of performance, I take it.
FOREVERLY LEAVE rubbish WINDOWS
you can try english keyboard, maybe fix this error
I am using english keyboard, us layout
I can reproduce it easily. when i click enter to open chat box, it never opens, it clicks 2 times, open and close it
i ran "pkexec sh -c 'sysctl -w abi.vsyscall32=1'", lol.py and then pressed the play button in garena, but it took a while for the client to work, i tried with wine lutris-ge-lol-7.0.1 . if you want to connect to the match, you must set abi.vsyscall32=0
Hi @nxhdev2002 have to do it everytime or only 1 time ?
i ran "pkexec sh -c 'sysctl -w abi.vsyscall32=1'", lol.py and then pressed the play button in garena, but it took a while for the client to work, i tried with wine lutris-ge-lol-7.0.1 . if you want to connect to the match, you must set abi.vsyscall32=0
Hi @nxhdev2002 have to do it everytime or only 1 time ? I have to do it everytime, otherwise the client won't respond. i think we should wait for repo update
i ran "pkexec sh -c 'sysctl -w abi.vsyscall32=1'", lol.py and then pressed the play button in garena, but it took a while for the client to work, i tried with wine lutris-ge-lol-7.0.1 . if you want to connect to the match, you must set abi.vsyscall32=0
Hi @nxhdev2002 have to do it everytime or only 1 time ? I have to do it everytime, otherwise the client won't respond. i think we should wait for repo update
@nhubaotruong
do i have to use lol.py with abi.vsyscall=1 or just use garena launch game directly ?
@khewweifeng It has to be done every time you start LOL client
@longz3r Please use the lol.py
with abi.vsyscall=1
@khewweifeng It has to be done every time you start LOL client @longz3r Please use the
lol.py
withabi.vsyscall=1
@nhubaotruong will you update into appimage / the repo ?
Yes I will, trying to figure out how to make it more convenient for you guys
Splash screen will get color after few mins but it will disappear although abi.vsyscall=1 and lol.py
I edited launchhelper2 and use lol.py with lutris lol 7.0.1
and the game stuck here
tried garena with lutris lol 7.0.1 = garena app will show flickering
I edited launchhelper2 and use lol.py with lutris lol 7.0.1
@khewweifeng
Hi, please accept my apologies for the late reply. Have you fixed the issue? If not, could you try to comment out the line pkexec sh -c 'sysctl -w abi.vsyscall32=0'
in launchhelper2.sh
and directly run pkexec sh -c 'sysctl -w abi.vsyscall32=1'
before you run lol.py
and start league? Don't forget to run pkexec sh -c 'sysctl -w abi.vsyscall32=0'
before any match starts.
how about this part ?
somtimes it will be redirected to riot games lol
im tired of trying get it working im going for dualboot windows 10 ghost spectre and debian
how about this part ?
I think you would need to set it to run league, just click yes.
In my experience, I need to run many times of pkexec sh -c 'sysctl -w abi.vsyscall32=1'
, lol.py
, and click play in Garena after the client fails in lutris log, to get the league client start normally. I am not sure if it has something to do with lanchhelper.sh
in league that deals with ssh and timeout stuff, you will need to be patient with it.
In addition, in my way of understanding what is going on, I would start lutris with lutris -d
to keep tracking the process, Garena runs pretty badly on linux.
Commenting out pkexec sh -c 'sysctl -w abi.vsyscall32=0'
and specify python3 launchhelper2.py
worked for me.
I'm on Ubuntu 20.04 and I have both python2 and python3 on my system.
Running pkexec sh -c 'sysctl -w abi.vsyscall32=1'
does fix the problem after the patch, but I'd only get the client to launch with a success rate of 1/20 or 1/30. Otherwise it'd be like what @longz3r experienced.
how about this part ?
I think you would need to set it to run league, just click yes.
In my experience, I need to run many times of
pkexec sh -c 'sysctl -w abi.vsyscall32=1'
,lol.py
, and click play in Garena after the client fails in lutris log, to get the league client start normally. I am not sure if it has something to do withlanchhelper.sh
in league that deals with ssh and timeout stuff, you will need to be patient with it.In addition, in my way of understanding what is going on, I would start lutris with
lutris -d
to keep tracking the process, Garena runs pretty badly on linux.
for me, i press no everytime and it works. BTW, i'm using lutris lol 7.0.2
Hi,
The client stuck on loading screen as the picture shown below.
The log: log.txt
Lutris Garena runner options:
Lutris LOL runner options:
System: OS: Debian GNU/Linux 11 bullseye Arch: x86_64 Kernel: 5.10.0-15-amd64 Desktop: KDE Display Server: x11
[CPU] Vendor: GenuineIntel Model: Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz Physical cores: 6 Logical cores: 12
[Memory] RAM: 15.5 GB Swap: 1.0 GB
[Graphics] Vendor: Intel OpenGL Renderer: Mesa Intel(R) UHD Graphics 630 (CFL GT2) OpenGL Version: 4.6 (Compatibility Profile) Mesa 20.3.5 OpenGL Core: 4.6 (Core Profile) Mesa 20.3.5 OpenGL ES: OpenGL ES 3.2 Mesa 20.3.5 Vulkan: Supported
I am looking forward to your reply. Fan