[SOLVED] Starting client in Arch Linux with DWM

[aging-goblin]

I downloaded the newest version of XMageMauncher-0.3.0.jar and ran it with "java -jar XMageMauncher-0.3.0.jar". It seemed to install fine, but when I run the client either from the launcher or the command line, I get an error about org.slf4j.impl.StaticLoggerBinder, and the client program windows are all blank. See screenshots and excerpt of error below. What should I do to solve?

Thanks.

Code: Select all

[duck@liver:~]% cd xmage/mage-client
[duck@liver:xmage/mage-client]% chmod 0755 startClient.sh
[duck@liver:xmage/mage-client]% cat startClient.sh
#!/bin/sh

java -Xms256m -Xmx512m -XX:MaxPermSize=256m -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -jar ./lib/mage-client-1.3.0.jar &%                                                                                                         [duck@liver:xmage/mage-client]% ./startClient.sh
[duck@liver:xmage/mage-client]% OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See <<link removed by BB software>> for further details.
ERROR 2015-01-16 12:34:49,154 Error for symbol:0                                                                         =>[AWT-EventQueue-0] ManaSymbols.loadImages
***snip***


[LevelX]

This SLF4J + ManaSymbols error messages can be ignored.

What error message is shown in the client log after the ManaSymbols messages?

[aging-goblin]

It shows nothing besides those errors. I am trying to link to a paste, but the BB software is totally crippling me. This is awful. I will try to PM.

[LevelX]

You need 4 or more posts to be able to add attachments and links.

And the XMage client window does not open?

[aging-goblin]

It does open, but it is blank. You can see the blank window in one of the screenshots with the exit dialog on top.

[aging-goblin]

Also, the settings dialog shows up like this (blank grey box).

[LevelX]

Only thing that seems strange:
[duck@liver:xmage/mage-client]% OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
Looks like the OpenJDK Java version 8.0 is used to run the client.

But in the launcher says the 1.7.0_71 is installed.

Try to run the client with the 1.7 java version. Don't know if this helps, but only point I see.

Maybe some other users that use XMage with Linux can be of more help.

[aging-goblin]

I have tried this with Open JRE/JDK 7 and 8, and the issues are the same. Is Java 1.7 something different than either of those? Did I read that xmage downloads its own version of java?

[LevelX]

The launcher loads and installs its own java version (1.7.0_71 as shown by the launcher) and normally the client is started with this java version of the launcher.

[aging-goblin]

I had kind of a bonehead error with the JRE... For anyone who uses DWM (likely only me), you need to set an environment variable to tell the JRE that you have a nonreparenting window manager. So that fixed the blank dialog boxes. I can now look at settings, version, etc. in the launcher. The client window is still blank, however. I am starting to suspect that this is just an error in displaying the dropdown menus that should be on top? You can see the client window on the bottom right in the screenshot.

[LevelX]

Can you run XMage with another window manager than DWM to check if that's the reason for the blank windows?

[aging-goblin]

I got the client working.

The problem was that I need to use exclusively OpenJDK 7 or 8 (doesn't seem to matter which), and NOT the launcher. I can use the launcher to update the client, but not to start it. If I just descend into xmage/mage-client/ and do ./startClient.sh, it seems like all systems go.

There are some issues that may or may not be related, such as null pointer exceptions when the client tries to play any sound, and some 404 errors when the script tries to download card images, but I think I'll read through what's on github and maybe address those over there if necessary.

Thanks for the help.