Hide Forgot
Description of problem: I loaded up FTB (Feed The Beast) for MineCraft. Clicked on the Mindcrack mod pack and nothing. It brought up the loading screen with the FTB logo, but then went to a black screen and nothing else happened until it crashed. Version-Release number of selected component: java-1.7.0-openjdk-1.7.0.60-2.4.3.0.fc19 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.3.0.fc19.x86_64/jre/bin/java -Xms256M -Xmx1024M -XX:PermSize=128m -cp /home/callum/.minecraft/FTB_Launcher.jar:/home/callum/.minecraft/MindCrack/instMods/liteloader.zip:/home/callum/.minecraft/MindCrack/instMods/MinecraftForge.zip:/home/callum/.minecraft/MindCrack/minecraft/bin/minecraft.jar:/home/callum/.minecraft/MindCrack/minecraft/bin/lwjgl.jar:/home/callum/.minecraft/MindCrack/minecraft/bin/lwjgl_util.jar:/home/callum/.minecraft/MindCrack/minecraft/bin/jinput.jar net.ftb.mclauncher.MinecraftLauncher /home/callum/.minecraft/MindCrack/minecraft /home/callum/.ftblauncher/ModPacks/MindCrack/FTB_temp.gif MinecraftForge.zip callum603 ce4ce0852dcc438fbb3c99c8e33e731c 'MindCrack Pack v8.3.2' /home/callum/.ftblauncher/ModPacks/MindCrack/logo_minecrack.png crash_function: exit executable: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.3.0.fc19.x86_64/jre/bin/java kernel: 3.11.10-200.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 var_log_messages: Dec 20 15:40:21 callum-pc abrt-hook-ccpp[2730]: Saved core dump of pid 2676 (/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.3.0.fc19.x86_64/jre/bin/java) to /var/tmp/abrt/ccpp-2013-12-20-15:40:12-2676 (751984640 bytes) Truncated backtrace: Thread no. 1 (7 frames) #17 exit at exit.c:99 #18 vm_direct_exit at /usr/src/debug/java-1.7.0-openjdk-1.7.0.60-2.4.3.0.fc19.x86_64/openjdk/hotspot/src/share/vm/runtime/java.cpp:597 #19 VM_Operation::evaluate at /usr/src/debug/java-1.7.0-openjdk-1.7.0.60-2.4.3.0.fc19.x86_64/openjdk/hotspot/src/share/vm/runtime/vm_operations.cpp:71 #20 VMThread::evaluate_operation at /usr/src/debug/java-1.7.0-openjdk-1.7.0.60-2.4.3.0.fc19.x86_64/openjdk/hotspot/src/share/vm/runtime/vmThread.cpp:383 #21 VMThread::loop at /usr/src/debug/java-1.7.0-openjdk-1.7.0.60-2.4.3.0.fc19.x86_64/openjdk/hotspot/src/share/vm/runtime/vmThread.cpp:508 #22 VMThread::run at /usr/src/debug/java-1.7.0-openjdk-1.7.0.60-2.4.3.0.fc19.x86_64/openjdk/hotspot/src/share/vm/runtime/vmThread.cpp:285 #23 java_start at /usr/src/debug/java-1.7.0-openjdk-1.7.0.60-2.4.3.0.fc19.x86_64/openjdk/hotspot/src/os/linux/vm/os_linux.cpp:892 Potential duplicate: bug 947884
Created attachment 839673 [details] File: backtrace
Created attachment 839674 [details] File: cgroup
Created attachment 839675 [details] File: core_backtrace
Created attachment 839676 [details] File: dso_list
Created attachment 839677 [details] File: environ
Created attachment 839678 [details] File: hs_err.log
Created attachment 839679 [details] File: limits
Created attachment 839680 [details] File: maps
Created attachment 839681 [details] File: open_fds
Created attachment 839682 [details] File: proc_pid_status
Looks like an error occured during loading. There is nothing the JVM can do about this. But there are a couple of things: 1. Is this reproducible? 2. Does /run/media/callum/OS/Users/CALLUM.CALLUM-PC/Minecraft/MindCrack/minecraft/bin/natives/liblwjgl64.so exist and is it readable at the time of launch?
Sorry, forgot to reply to this earlier. 1. It is reproducible, you just have to remove liblwjgl64.so from the natives folder. 2. No it didn't exist at the time of launch, but the partition was readable. For anyone having the same problem you need to download the following http://sourceforge.net/projects/java-game-lib/files/ and copy all of the files from inside the Linux folder of that download to your /home/username/.mincraft/bin Allow it to write into and overrite the files already in there and it should work when you reload the game. I forgot to include the Linux files in the Windows folder so I could link the two together. I've closed this as it's not really a bug, just me forgetting to include the correct files.
Ah okay. Thank you for replying back to so quickly and for posting a solution for others!
No problem. Thank you for your help.