Package Details: runescape-launcher 2.2.4-3

Git Clone URL: https://aur.archlinux.org/runescape-launcher.git (read-only)
Package Base: runescape-launcher
Description: RuneScape Game Client (NXT)
Upstream URL: https://www.runescape.com/
Keywords: games runescape
Licenses: custom
Conflicts: runescape-launcher-nxt
Provides: runescape-launcher-nxt
Submitter: ivan_p
Maintainer: grawity
Last Packager: grawity
Votes: 31
Popularity: 1.102446
First Submitted: 2016-02-19 14:08
Last Updated: 2017-09-14 09:57

Pinned Comments

grawity commented on 2017-09-11 17:26

Update: The package no longer verifies sha256sums, but only the PGP signature.

As always, if makepkg complains about an "unknown key", you'll have to import it (or skip verification at your own risk):

gpg --recv-key AAC9264309E4D717441DB9527373B12CE03BEB4B

Latest Comments

iagsousa commented on 2018-02-17 14:28

I'm having an issue with firewall when loading the nxt client

There was an error loading the game configuration from the website. If you have a firewall, check that this program is allowed to access the Internet. (7,28)

can someone help me to get it allowed? I can't seem to make it work.

Louis6321 commented on 2018-02-10 18:29

Oh my god, yes! I can also confirm the black screen issue is resolved as of 390.25 :-)

Now it's just the choppy audio issue that remains... but I can live with that.

Endiverge commented on 2018-02-08 20:57

I'm on nvidia driver version 390.25, and I'm not getting the black screen issue anymore. If anyone is still using the 384 drivers to play, it may be worth trying to upgrade.

magnavoid commented on 2018-01-19 05:29

I am having the nvidia black screen issue. I tried rolling back the drivers back to 384.90 and even tried manually installing the nvidia 384.111 drivers from the nvidia website using NVIDIA-Linux-x86_64-384.111.run.

It appears that every nvidia driver higher than 384 will cause this problem. In order to get it working again it appears that the kernel cannot be updated past 4.13. In addition to this the nvidia proprietary drivers can’t be upgraded past 384.90 which are the highest 384 versioned drivers available from the arch archives. With jagex essentially ignoring this issue on the forums there's not much else that can be done.

Here's a list of URLS to the arch archive.

Driver:

https://archive.archlinux.org/packages/n/nvidia/nvidia-384.90-1-x86_64.pkg.tar.xz

DKMS for those who prefer that instead:

https://archive.archlinux.org/packages/n/nvidia-dkms/nvidia-dkms-384.90-1-x86_64.pkg.tar.xz

Extras:

https://archive.archlinux.org/packages/l/lib32-nvidia-utils/lib32-nvidia-utils-384.90-1-x86_64.pkg.tar.xz

https://archive.archlinux.org/packages/n/nvidia-settings/nvidia-settings-384.90-1-x86_64.pkg.tar.xz

https://archive.archlinux.org/packages/n/nvidia-utils/nvidia-utils-384.90-1-x86_64.pkg.tar.xz

For the adventurous: http://us.download.nvidia.com/XFree86/Linux-x86_64/384.111/NVIDIA-Linux-x86_64-384.111.run

This apparently works on 4.14 according to some information I found on the runescape official forums. But I didnt try it.

Hope this is fixed soon.

EDIT:

I downgraded my kernel to 4.13.7-1, installed the related kernel headers, and then downgraded the nvidia drivers to nvidia-dkms-384.90-1. That fixed my issue completely. There's definitely something wrong with the NXT client.

bddenhartog commented on 2018-01-15 06:20

Do we have any idea why the floating loading window never closes?

bddenhartog commented on 2018-01-15 06:18

@Louis6321 that definitely sounds like a driver issue. Are you using the official, proprietary drivers? Have you looked for or filed an issue for the driver version you're using?

Louis6321 commented on 2018-01-05 13:24

Does anyone have a fix for the Nvidia black screen problem? Had it for a few months now and it's a great shame I have to boot into Windows to play on NXT.

grawity commented on 2017-12-03 13:13

Does the issue occur if you manually log out, or manually return to lobby, via the Esc menu?

Either way, better report it to the RS forums instead.

bddenhartog commented on 2017-12-02 20:34

I have a pretty weird, reproducible issue related to world selection and entering the game world.

On first sign-in, everything works great. It's only after automatically being returned to the lobby (afk timer) that this problem occurs - basically, the "world select" tab is empty, and neither of the "play now", or the favorited world buttons actually enter me into the game. The only way to get it working again is to close the client and restart it.

Starting from the command line, there is no error related to the actions of clicking the "play now" or favorited world buttons. I only have the "no version information available" warning from libcurl.so.3 that appears when the client is first started.

Any ideas as to what is causing this, and how to resolve it?

EDIT: Upon testing various auth workflows further, this only appears to happen when authenticating over OAuth via Google.

ArnaudNux commented on 2017-12-02 02:10

#1 --> gpg: key 7373B12CE03BEB4B: "RuneScape Linux <noreply@jagex.com>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1


#2 --> Verifying Release (PGP)...
==> ERROR: PGP signature of 'Release' could not be verified
gpg: Signature made Fri Nov 24 14:22:41 2017 CET
gpg: using RSA key 7373B12CE03BEB4B
gpg: Can't check signature: No public key
==> ERROR: A failure occurred in prepare().
Aborting...


All comments