Open cosmicchipsocket-old opened 9 years ago
Linux distro & VM?
Distro is Arch Linux. Architecture is x86_64.
Tried using both jre7 and jre8 to no avail:
Java(TM) SE Runtime Environment (build 1.7.0_72-b14) Java HotSpot(TM) 64-Bit Server VM (build 24.72-b04, mixed mode)
Java(TM) SE Runtime Environment (build 1.8.0_25-b17) Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)
I've been able to use the launcher just fine previously. Vanilla Minecraft launcher also continues to work.
What are the contents of your java options environment variable? I believe there's an equivalent on linux.
_JAVA_OPTIONS=-Dawt.useSystemAAFontSettings=on -Dswing.aatext=true
I set those options a while ago because I was trying to fix issues with text not getting anti-aliased nicely in other apps (mainly IntelliJ IDEA). Strangely, if I clear the variable, the launcher works as expected!
That's what I suspected. If the AA settings aren't right to make the launcher look the best it can, we restart with the correct settings. I didn't think that the OS could stop us from using the settings we need, so there's no limit to the number of times this can happen. :-P I'll fix it.
Fix is live in beta v4.254.
Issue still occurs in Launcher build 4.256.
wtf
...
omg
dattorz
....
dattorz
lollol
dattorz
how do i fix it?
pls help me !! :(
|:O!
i downloaded it what should i do then? :100:
hilft mir helpt me
Selected Pack: Hexxit
Stack Trace:
Exception: IndexOutOfBoundsException
Message: Index: 0, Size: 0
Trace:
java.util.ArrayList.rangeCheck(Unknown Source)
java.util.ArrayList.get(Unknown Source)
org.spoutcraft.launcher.skin.NewsComponent.setupArticles(NewsComponent.java:60)
org.spoutcraft.launcher.skin.NewsComponent.loadArticles(NewsComponent.java:46)
org.spoutcraft.launcher.Launcher$2.run(Launcher.java:105)
System Information:
Operating System: Windows 7
Operating System Version: 6.1
Operating System Architecture: x86
Java version: 1.8.0_51 32 bit
Total Memory: 39 MB
Max Memory: 247 MB
Memory Free: 5 MB
CPU Cores: 4
@DragonHDLP24 Buy the game.
Around December 26th I started getting a strange issue where the launcher would not come up because, according to the logs, it kept launching itself over and over. I used to be able to use a workaround where I would update to the latest launcher from an old, pre-Launcher 4 version, and it would work. However, now it seems that this method doesn't work either.
Getting this result using the latest official launcher on Linux. The log looks like this:
And it goes on and on like this until I manually killall java. No window ever actually appears. It just gets stuck in a loop.
And yes, I launched it from double-clicking /stuff/Games/CrossOS/Minecraft/TechnicLauncher.jar. All it does is launch itself.
I tried deleting ~/.technic and this would bring up the "where do you want your configuration saved" dialog. If I choose either a system config or a portable installation, I get stuck in the loop after the dialog.
I also tried emptying /tmp wondering if there was some file that made it think it was still "in update mode" but that didn't work either.