Package Details: runescape-launcher 2.2.11-1

Git Clone URL: https://aur.archlinux.org/runescape-launcher.git (read-only, click to copy)
Package Base: runescape-launcher
Description: RuneScape Game Client (NXT)
Upstream URL: https://www.runescape.com/
Keywords: games
Licenses: custom
Submitter: ivan_p
Maintainer: grawity
Last Packager: grawity
Votes: 52
Popularity: 0.003704
First Submitted: 2016-02-19 14:08 (UTC)
Last Updated: 2023-02-09 05:50 (UTC)

Required by (0)

Sources (4)

Pinned Comments

JagexDark commented on 2019-11-13 10:02 (UTC)

The GUI label is intentionally 2.2.4, this is related to it being a Linux-only launcher update, sorry if this causes any confusion

grawity commented on 2017-09-11 17:26 (UTC) (edited on 2020-07-02 08:45 (UTC) by grawity)

Note: It is important to keep PGP signature verification enabled, because this PKGBUILD does not verify sha256sums due to Jagex frequently releasing rebuilds with the same version number.

Don't forget to import the Jagex PGP key if installing for the first time:

gpg --keyserver hkps://keyserver.ubuntu.com --recv-key AAC9264309E4D717441DB9527373B12CE03BEB4B

Latest Comments

« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 Next › Last »

grawity commented on 2016-04-28 12:58 (UTC)

The Java NPAPI plugin is loaded by webkitgtk, which is used to render ads on the login screen.

fusion809 commented on 2016-04-28 12:34 (UTC)

@ivan_p That's strange because on a new Arch Linux installation I ran: optirun runescape-launcher and it returned the output: /usr/share/games/runescape-launcher/runescape: /usr/lib/libcurl.so.3: no version information available (required by /usr/share/games/runescape-launcher/runescape) (runescape:20953): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita", (runescape:20953): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita", (runescape:20953): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita", (runescape:20953): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita", (runescape:20953): Gtk-WARNING **: Theme directory actions/48 of theme breeze has no size field (runescape:20953): Gtk-WARNING **: Theme directory categories/16 of theme breeze has no size field (runescape:20953): Gtk-WARNING **: Theme directory categories/22 of theme breeze has no size field (runescape:20953): Gtk-WARNING **: Theme directory categories/48 of theme breeze has no size field (runescape:20953): Gtk-WARNING **: Theme directory devices/48 of theme breeze has no size field openjdk version "1.8.0_92" OpenJDK Runtime Environment (build 1.8.0_92-b14) OpenJDK 64-Bit Server VM (build 25.92-b14, mixed mode) for some reason it was launching Java and then it crashed.

ivan_p commented on 2016-04-26 14:54 (UTC)

@USA-RedDragon This is NXT. Java is here: https://aur.archlinux.org/packages/unix-runescape-client/

USA-RedDragon commented on 2016-04-26 14:35 (UTC)

So does this install the NXT client or the Older Java client?

ptkato commented on 2016-04-22 02:15 (UTC) (edited on 2016-04-23 01:20 (UTC) by ptkato)

I'm getting an error when I click the auto-setup button, cant get past it: /usr/bin/runescape-launcher.real: line 13: 26377 Segmentation fault (core dumped) /usr/share/games/runescape-launcher/runescape --configURI $configURI $@ Any clues? Edit: I pasted a core dump to pastebin. http://pastebin.com/TaCwaEkj

ivan_p commented on 2016-04-20 11:55 (UTC) (edited on 2016-04-20 11:59 (UTC) by ivan_p)

@All Any crash after the launcher is successfully launched and you seen login screen is an upstream bug. If the launcher does not even launches, it _might_ be issue with the packaging. @fusion809 I can only think now about some outdated orphan packages that somehow interfere, or packages that you did not update as per this update from December: https://www.archlinux.org/news/c-abi-change/ I don't know what else to suggest. Usually "BadMatch" is a bug in the software (the launcher in this case). Edit: may be grapics driver related! What GPU and drivers are you using? Should work with latest propriatary drivers. Have no idea about open-source ones in this case. May have many various problems with old intel cards.

kwilkins commented on 2016-04-19 23:04 (UTC)

Package Updated @ 2016-04-19 6:00 PM Eastern After playing for 5-10 minutes I've consistently seen the client crash. Not sure if this is an upstream issue though. http://pastebin.com/viYXCKJY

fusion809 commented on 2016-04-19 21:49 (UTC)

Sure is, I only just ran `yaourt -Syua` (which is when I received the RS Launcher update).

ivan_p commented on 2016-04-19 21:43 (UTC) (edited on 2016-04-19 21:44 (UTC) by ivan_p)

@fusion809 "/usr/share/games/runescape-launcher/runescape: /usr/lib/libcurl.so.3: no version information available (required by /usr/share/games/runescape-launcher/runescape)" This is not error, but a warning, as far as I understand. It also means, that the correct libcurl.so is loaded, and further tries to preload it are needless. "BadMatch" error from X is indeed a problem. I personally witnessed it only when running some programs inside X that is forwarded over ssh. But, if it's not the case for you, then is your system uptodate?

fusion809 commented on 2016-04-19 21:29 (UTC)

I keep receiving this error since I upgraded to the 2.2.2-2 version of this package: /usr/share/games/runescape-launcher/runescape: /usr/lib/libcurl.so.3: no version information available (required by /usr/share/games/runescape-launcher/runescape) The program 'runescape' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 2602 error_code 8 request_code 42 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) I have tried running: LD_PRELOAD=/usr/lib/libcurl.so.3 /usr/share/games/runescape-launcher/runescape from the command-line instead but it returned the same error.