Forums

Community: Linux Support 2.0Thread is sticky

Quick find code: 409-410-916-65990459

of 17
EMP0RERTRUMP
Nov Gold Premier Club Member 2017

EMP0RERTRUMP

Posts: 78Iron Posts by user Forum Profile RuneMetrics Profile
Pinguicula said:
For your earlier post about Ubuntu 16.04:

Did you try doing
sudo apt-get -f install
as it suggested?

I'm not sure why you're having dependency problems. You can try
sudo apt install libc6 python2.7-minimal libpython2.7-stdlib libsdl2-2.0-0 libwebkitgtk-1.0-0

to install the dependencies it is having trouble with. Doing that has worked for some people when they had dependency issues.
thats another weird thing it didnt register as a command.

I have even tried using fedora and it was the same thing going on, I took the laptop apart to see if there was an issue nothing plus all the parts came back fine in dell diagnostic, im thinking its either a driver issue or I might not be configuring the bios properly, gonna keep looking for a fix might try nvidias nouveau driver(no nvidia on here but im trying it), heard somewhere it works for internal graphics issues, and apparently now on 18.04 theres no longer that python dependency issue. Ill post the fix if I find or figure it out.
FREE WORLD LEADER

18-Jan-2019 10:23:41 - Last edited on 18-Jan-2019 10:41:17 by EMP0RERTRUMP

HikariKnight
May Member 2011

HikariKnight

Posts: 6,834Rune Posts by user Forum Profile RuneMetrics Profile
Four Ace said:
so has anyone found a workaround for lintel graphics cards... nxt nor flatpak will load

works fine on my test system, it might be that the intel graphics you have are very old.
best solution i can suggest for an intel system is to make sure you have the mesa drivers installed as it works on my i5-7th gen and my laptop having a 2nd or 3rd gen i3

Original message details are unavailable.
sudo apt install mesa-vdpau-drivers mesa-va-drivers mesa-vulkan-drivers libgl1-mesa-glx libegl1-mesa libglx-mesa0
God/Protector of the Penguins.
Developer of the RuneScape Unix Client.
Maintainer of the Linux Tech Support thread

20-Jan-2019 17:19:12

Four Ace
Jun Gold Premier Club Member 2010

Four Ace

Posts: 2,828Adamant Posts by user Forum Profile RuneMetrics Profile
the computer originally had windows 7 and i think the last time they updated the drivers was 2013 but i tried to use the code you gave me but still did not work thanks for tying though Well Here we go again :P

22-Jan-2019 06:13:35

HikariKnight
May Member 2011

HikariKnight

Posts: 6,834Rune Posts by user Forum Profile RuneMetrics Profile
youre welcome, i am sadly not very knowledgeable about the internal workings of the nxt client compared to the java client.

would it be possible for you to try out the rsu client (legacy java client for linux) and see if that will spit out any coherent error in the terminal when you run it from there.

i doubt it will be of any help but there is a very slim chance it could give us some kind of idea if that one also crashes (although my experiences with the older igpus from intel is that they hate opengl in java more than opengl itself when i did actively develop the rsu client).

unless of course the java version runs fine which would then be better than nothing.
God/Protector of the Penguins.
Developer of the RuneScape Unix Client.
Maintainer of the Linux Tech Support thread

23-Jan-2019 23:00:12

[#ZXOK8RQIY]
Dec Member 2018

[#ZXOK8RQIY]

Posts: 12Bronze Posts by user Forum Profile RuneMetrics Profile
I have a Lenovo T500 with Intel GM45 graphics. Trying to run RS from either the .deb itself or from Flatpak results in the game never starting after the launcher, and doing the GL override from 3.0 to 2.1 didn't help. The Java client works though.

Is there a way to get NXT to output some kind of useful error to see what the issue is?

01-Feb-2019 04:26:43

HikariKnight
May Member 2011

HikariKnight

Posts: 6,834Rune Posts by user Forum Profile RuneMetrics Profile
[#ZXOK8RQIY] said:
Is there a way to get NXT to output some kind of useful error to see what the issue is?


Not as far as i know, it might just be that the GM45 is just too old to handle NXT as i know nxt works on intel graphics from 2nd gen (oldest i have that can log into nxt)
God/Protector of the Penguins.
Developer of the RuneScape Unix Client.
Maintainer of the Linux Tech Support thread

01-Feb-2019 09:11:00

[#ZXOK8RQIY]
Dec Member 2018

[#ZXOK8RQIY]

Posts: 12Bronze Posts by user Forum Profile RuneMetrics Profile
On a RX 580, the NXT client (flatpak) seemingly works fine, but sometimes my in-game screen while playing goes black. The game is still running though, and if I move my cursor around, game objects and things can still be interacted with, and text is still visible.

Is there something that can be tried to fix this?

01-Feb-2019 20:17:38

[#ZXOK8RQIY]
Dec Member 2018

[#ZXOK8RQIY]

Posts: 12Bronze Posts by user Forum Profile RuneMetrics Profile
HikariKnight said:
[#ZXOK8RQIY] said:
Is there a way to get NXT to output some kind of useful error to see what the issue is?


Not as far as i know, it might just be that the GM45 is just too old to handle NXT as i know nxt works on intel graphics from 2nd gen (oldest i have that can log into nxt)


Took a bit of trying out different variables, but finally got it :D

For the Flatpak, in order to pass environment variables to it, I had to launch RS from command-line and use the --env flag to pass environment variables to it. I got some relevant information from the MESA_DEBUG=1 flag:

Original message details are unavailable.
flatpak run --env='MESA_DEBUG=1' com.jagex.RuneScape


And it can also have additional variables passed to it as well by just repeating the --env flag:

Original message details are unavailable.
flatpak run --env='MESA_DEBUG=1' --env='LIBGL_DEBUG=verbose' --env='vblank_mode=0' com.jagex.RuneScape


Got two errors with GL_INVALID_ENUM that mentioned GL_MAX_VERTEX_OUTPUT_COMPONENTS and GL_MAX_UNIFORM_BUFFER_BINDINGS. Tried to see if I could figure out if they were GL extensions or what, but didn't find anything with this, but came to a conclusion that it was definitely graphics-related. Using the environment variable LIBGL_ALWAYS_SOFTWARE=1 gave a different set of errors.

But the flag that actually got it running was MESA_GLSL_VERSION_OVERRIDE=450. Not sure if it'll cause any issues later on, but at the very least, it gets the game started, and I can stand around the Rimmington mine no problem. The final command is:

Original message details are unavailable.
flatpak run --env='MESA_GLSL_VERSION_OVERRIDE=450' com.jagex.RuneScape

02-Feb-2019 01:08:46

Quick find code: 409-410-916-65990459Back to Top