Failed to open BO for returned DRI2 buffer (1366x709, dri2 back buffer, named 14).
This is likely a bug in the X Server that will lead to a crash soon.
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f689a9849cc, pid=4362, tid=140089164502784
#
# JRE version: OpenJDK Runtime Environment (8.0_45-b14) (build 1.8.0_45-b14)
# Java VM: OpenJDK 64-Bit Server VM (25.45-b02 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [i965_dri.so+0x39c9cc]
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/ege/.minecraft/hs_err_pid4362.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Well at least i have idea what is going on, not sure how to fix it thou...
Your system has 2 graphics, integrated Intel on MoBo, and GForce GT620 , Your crash report indicates that game is trying to use Intel integrated graphic graphic, that may have been outdated and not sufficient to run Minecraft versions 1.7.4 and newer, or has a driver issue.
I am not sure how to disable integrated graphic on ArchLinux, but i am sure it can be googled.
Other sudgestions would be to google for solution to force Nvidia graphic to be default, or primary display for apps and Java.
You may want to look at these links to start searhing:
Thank you for your answer. However I was able to play with Intel HD 4000 without any problem(I was getting stable 60 FPS without any settings changed) on any other distro I've tried recently and I was always using Arch, I just reinstalled it yesterday. I guess this is a driver issue then.
Thank you for your answer. However I was able to play with Intel HD 4000 without any problem(I was getting stable 60 FPS without any settings changed) on any other distro I've tried recently and I was always using Arch, I just reinstalled it yesterday. I guess this is a driver issue then.
Yes you should probbably check on Intels web-support if they have propertiary driver for your distro that could possibly work for Minecraft instead of generic driver.
Rollback Post to RevisionRollBack
TAKE CHANCES. TELL THE TRUTH. KISS SLOWLY. DATE SOMEONE TOTALY WRONG FOR YOU.
SAY NO. LOVE DEEPLY. FORGIVE QUICKLY. SPEND ALL YOUR CASH.
GET TO KNOW SOMEONE RANDOM, BE RANDOM. SAY I LOVE YOU. SING OUT LOUD.
FORGET THE PAST. REMMEMBER WHAT IT TOUGHT YOU. LAUGH AT STUPID JOKES.
CRY. APOLOGIZE. TELL SOMEONE HOW MUCH THEY MEAN TO YOU.
TELL A JERK WHAT YOU THINK.LAUGH TILL YOUR STOMACH HURTS.
Can I start by saying that you should never install drivers separate from your package manager if at all possible? It's just begging to break things. These are identical to the drivers in Arch's repositories, just separated from the package manager.
Anyways, this is a bug in Mesa, which needs a workaround for now. Try enabling SNA by doing this. Create a file at /etc/X11/xorg.conf.d/20-intel.conf with the following contents:
I get this crash too on my notebook with Arch x86_64, linux-rt 4.0.5_rt4 and the Intel HD Graphics of my Intel Pentium 2020M processor (which is my only graphics card). Elephant454's suggestion prevents my 1.8 profile with LiteLoader (and a few LiteMods) from crashing during startup, however it still crashes shortly after entering any game, just like Vanilla 1.8.7 does (no matter whether the changed X11 config is active).
Update: I did some additional research (aka trial and error) and after reinstalling Mesa MC 1.8.7 Vanilla runs stably (whyever). However, the modded 1.8 profile still crashes at every startup. Strange.
Update 2: It seems that Vanilla 1.8.7 is acually not stable now - the crashes are just a little bit less often. I still have no clue why though. Maybe it's just random.
Thank you so much!, that seems to work for me as well. I just wish I had been notified about your post; that had made things so much easier for me.
Re crash randomness: I agree that most crashes in released software will be random, but they don’t have to be. My LiteLoader profile, for example, crashed consistently at the end of every startup.
Hello, Minecraft crashes after fresh Arch Linux install.
My system:
hs_err_pid4362.log
http://paste2.org/YU5cwyYm
Thanks all.
Well at least i have idea what is going on, not sure how to fix it thou...
Your system has 2 graphics, integrated Intel on MoBo, and GForce GT620 , Your crash report indicates that game is trying to use Intel integrated graphic graphic, that may have been outdated and not sufficient to run Minecraft versions 1.7.4 and newer, or has a driver issue.
I am not sure how to disable integrated graphic on ArchLinux, but i am sure it can be googled.
Other sudgestions would be to google for solution to force Nvidia graphic to be default, or primary display for apps and Java.
You may want to look at these links to start searhing:
https://wiki.archlinux.org/index.php/Hybrid_graphics
https://bbs.archlinux.org/viewtopic.php?id=112866
http://askubuntu.com/questions/15694/how-do-i-disable-intel-graphics-in-a-hybrid-graphics-setup
Thank you for your answer. However I was able to play with Intel HD 4000 without any problem(I was getting stable 60 FPS without any settings changed) on any other distro I've tried recently and I was always using Arch, I just reinstalled it yesterday. I guess this is a driver issue then.
Yes you should probbably check on Intels web-support if they have propertiary driver for your distro that could possibly work for Minecraft instead of generic driver.
There is no proprietary drivers for Intel GPU. :/ I guess I need to wait for an update to xf86-video-intel.
Might be your lucky day:
https://01.org/linuxgraphics
Can I start by saying that you should never install drivers separate from your package manager if at all possible? It's just begging to break things. These are identical to the drivers in Arch's repositories, just separated from the package manager.
Anyways, this is a bug in Mesa, which needs a workaround for now. Try enabling SNA by doing this. Create a file at /etc/X11/xorg.conf.d/20-intel.conf with the following contents:
Then reboot. Let me know how it goes. I got this from comment 7 here: https://bugs.freedesktop.org/show_bug.cgi?id=84372
Thank you for you answer. But it crashed again. :/
It seems it works for everyone else. Is it because I have Nvidia Optimus?
I get this crash too on my notebook with Arch x86_64, linux-rt 4.0.5_rt4 and the Intel HD Graphics of my Intel Pentium 2020M processor (which is my only graphics card). Elephant454's suggestion prevents my 1.8 profile with LiteLoader (and a few LiteMods) from crashing during startup, however it still crashes shortly after entering any game, just like Vanilla 1.8.7 does (no matter whether the changed X11 config is active).
Update: I did some additional research (aka trial and error) and after reinstalling Mesa MC 1.8.7 Vanilla runs stably (whyever). However, the modded 1.8 profile still crashes at every startup. Strange.
Update 2: It seems that Vanilla 1.8.7 is acually not stable now - the crashes are just a little bit less often. I still have no clue why though. Maybe it's just random.
Crashes must be random. Rarely I can play up to 30 minutes without any crash.
Well, opposite to all suggestions changing sna to uxa seems to fixed it. So far no crash for me. Let me know if it works for you.
/etc/X11/xorg.conf.d/20-intel.conf
Thank you so much!, that seems to work for me as well. I just wish I had been notified about your post; that had made things so much easier for me.
Re crash randomness: I agree that most crashes in released software will be random, but they don’t have to be. My LiteLoader profile, for example, crashed consistently at the end of every startup.
Same crash for me on Kubuntu 15.04 with snapshot 15w32c (Using MultiMC)
Maybe a recent update broke all the things, this didn't happen before?
EDIT: Setting AccelMethod to uxa fixed the problem. Just dont set it to uxa and enable TearFree or you'll have a BAD time.
Failed to open BO for returned DRI2 buffer (1920x1141, dri2 back buffer, named 39).
This is likely a bug in the X Server that will lead to a crash soon.
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fa111e5756d, pid=5298, tid=140330991535872
#
# JRE version: OpenJDK Runtime Environment (8.0_45-b14) (build 1.8.0_45-internal-b14)
# Java VM: OpenJDK 64-Bit Server VM (25.45-b02 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [i965_dri.so+0x3af56d]
#
# Core dump written. Default location: /home/marco/bin/MultiMC/instances/15w32c/minecraft/core or core.5298
#
# An error report file with more information is saved as:
# /home/marco/bin/MultiMC/instances/15w32c/minecraft/hs_err_pid5298.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Coming soon:
-HoverBoat port for 1.7.10 (Old version from ShaRose) - 90%
-TF2-like Killcam - 5%
-Simple Config File Block Adder - 50%
-Ender Pig - 80%
(Damn, I need to finish these!)
My mods:
-Ingame Account Switcher - Lets you change your account info ingame without having to restart Minecraft!
-Crafty Utils - Adds some random useful early-late game content
Arch Linux supporter since 2012!